errata logo graphic

Found 3 records.

Status: Held for Document Update (3)

RFC3711, "The Secure Real-time Transport Protocol (SRTP)", March 2004

Source of RFC: avt (rai)

Errata ID: 3420

Status: Held for Document Update
Type: Technical

Reported By: Matthias Schertler
Date Reported: 2012-11-28
Held for Document Update by: Gonzalo Camarillo

Section 3.1. says:

   The "Encrypted Portion" of an SRTP packet consists of the encryption
   of the RTP payload (including RTP padding when present) of the
   equivalent RTP packet.

It should say:

   The "Encrypted Portion" of an SRTP packet consists of the encryption
   of the RTP payload (including RTP padding and RTP pad count when present)
   of the equivalent RTP packet.  

Notes:

In Figure 1 "RTP padding" and "RTP pad count" are different things. The text should use the same terminology in order to make clear that the padding count is encrypted.


Errata ID: 3712

Status: Held for Document Update
Type: Technical

Reported By: Christian S Oien
Date Reported: 2013-08-27
Held for Document Update by: Richard Barnes
Date Held: 2014-02-15

Section 4.3.2 says:

Replace the SRTP index by the 32-bit quantity: 0 || SRTCP index
 (i.e., excluding the E-bit, replacing it with a fixed 0-bit), and use
<label> = 0x03 for the SRTCP encryption key, <label> = 0x04 for the
SRTCP authentication key, and, <label> = 0x05 for the SRTCP salting
key.

It should say:

Replace the SRTP index by the 48-bit quantity: 000...0 || 0 || SRTCP
index (i.e., excluding the E-bit, replacing it with a fixed 0-bit and
padding the result so that it becomes 48 bits wide to match the size
of the SRTP index). Since this quantity and the SRTP index are both
48 bits wide, the labels are all located in the same octet in the IV.
The labels for the derivations of the SRTCP keys are as follows:   
<label> = 0x03 for the SRTCP encryption key, <label> = 0x04 for the 
SRTCP authentication key, and, <label> = 0x05 for the SRTCP salting 
key.

Notes:

Replacing with a 32-bit quantity means that the DIV operator will
yield a 32-bit quantity. Following the specification of key_id for SRTCP
the <label> will have 32 bits to its right when XOR'ing with master_salt.

The majority of implementations, including libsrtp, invokes this XOR with the
<label> at the same position as for SRTP. According to the specification
this should be done 16 bits to the right of this, when invoking for SRTCP.


Errata ID: 1958

Status: Held for Document Update
Type: Editorial

Reported By: Jaap Keuter
Date Reported: 2009-12-10
Held for Document Update by: Robert Sparks

Section 1 says:

   This document describes the Secure Real-time Transport Protocol
   (SRTP), a profile of the Real-time Transport Protocol (RTP), which
   can provide confidentiality, message authentication, and replay
   protection to the RTP traffic and to the control traffic for RTP,
   RTCP (the Real-time Transport Control Protocol) [RFC3350].

It should say:

   This document describes the Secure Real-time Transport Protocol
   (SRTP), a profile of the Real-time Transport Protocol (RTP), which
   can provide confidentiality, message authentication, and replay
   protection to the RTP traffic and to the control traffic for RTP,
   RTCP (the Real-time Transport Control Protocol) [RFC3550].

Notes:

Reference is made to the RFC pertaining RTP, which is 3550, not 3350.


Report New Errata