Search RFCs

RFC Editor

Found 5 records.

Status:Verified (1)

RFC 3264, "An Offer/Answer Model with Session Description Protocol (SDP)", June 2002

Note: This RFC has been updated byRFC 6157, RFC 8843, RFC 9143

Errata ID:3818
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Jörgen Axell
Date Reported: 2013-12-02
Verifier Name: Gonzalo Camarillo
Date Verified: 2013-12-03

Section 4 says:

   The agent receiving the offer MAY generate an answer, or it MAY   reject the offer.  The means for rejecting an offer are dependent on   the higher layer protocol.  The offer/answer exchange is atomic; if   the answer is rejected, the session reverts to the state prior to the   offer (which may be absence of a session).

It should say:

   The agent receiving the offer MAY generate an answer, or it MAY   reject the offer.  The means for rejecting an offer are dependent on   the higher layer protocol.  The offer/answer exchange is atomic; if   the offer is rejected, the session reverts to the state prior to the   offer (which may be absence of a session).

Notes:

You can't reject an answer. When the answer is received the SDP negotiation is completed.

Status:Held for Document Update (2)

RFC 3264, "An Offer/Answer Model with Session Description Protocol (SDP)", June 2002

Note: This RFC has been updated byRFC 6157, RFC 8843, RFC 9143

Errata ID:2098
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Parveen Verma
Date Reported: 2010-03-30
Held for Document Update by: Robert Sparks

Section 10 says:

10.1 Basic Exchange   Assume that the caller, Alice, has included the following description   in her offer.  It includes a bidirectional audio stream and two   bidirectional video streams, using H.261 (payload type 31) and MPEG   (payload type 32).  The offered SDP is:   v=0   o=alice 2890844526 2890844526 IN IP4 host.anywhere.com   s=   c=IN IP4 host.anywhere.com   t=0 0   m=audio 49170 RTP/AVP 0   a=rtpmap:0 PCMU/8000   m=video 51372 RTP/AVP 31   a=rtpmap:31 H261/90000   m=video 53000 RTP/AVP 32   a=rtpmap:32 MPV/90000

It should say:

10.1 Basic Exchange   Assume that the caller, Alice, has included the following description   in her offer.  It includes a bidirectional audio stream and two   bidirectional video streams, using H.261 (payload type 31) and MPEG   (payload type 32).  The offered SDP is:   v=0   o=alice 2890844526 2890844526 IN IP4 host.anywhere.com   s=-   c=IN IP4 host.anywhere.com   t=0 0   m=audio 49170 RTP/AVP 0   a=rtpmap:0 PCMU/8000   m=video 51372 RTP/AVP 31   a=rtpmap:31 H261/90000   m=video 53000 RTP/AVP 32   a=rtpmap:32 MPV/90000

Notes:

The s= session name must have some values as per RFC 4566 Sec 5.3.
----------------------------------------------------------------
RFC 4566
5.3. Session Name ("s=")

s=<session name>

The "s=" field is the textual session name. There MUST be one and
only one "s=" field per session description. The "s=" field MUST NOT
be empty and SHOULD contain ISO 10646 characters (but see also the
"a=charset" attribute). If a session has no meaningful name, the
value "s= " SHOULD be used (i.e., a single space as the session name).
----------------------------------------------------------------
RFC 3264 also states in Section 5
"Unfortunately, SDP does not allow the "s=" line to be empty."

Even if we put "s= " , it becomes a bit difficult to read/understand in soft/printed copy.

The same error applies to all SDP examples given in Section 10

Errata ID:2099
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Brett Tate
Date Reported: 2010-03-30
Held for Document Update by: Robert Sparks

Section 9 says:

   v=0   o=carol 28908764872 28908764872 IN IP4 100.3.6.6   s=-   t=0 0   c=IN IP4 192.0.2.4   m=audio 0 RTP/AVP 0 1 3   a=rtpmap:0 PCMU/8000   a=rtpmap:1 1016/8000   a=rtpmap:3 GSM/8000   m=video 0 RTP/AVP 31 34   a=rtpmap:31 H261/90000   a=rtpmap:34 H263/90000   Figure 1: SDP Indicating Capabilities

It should say:

   v=0   o=carol 28908764872 28908764872 IN IP4 100.3.6.6   s=-   c=IN IP4 192.0.2.4   t=0 0   m=audio 0 RTP/AVP 0 1 3   a=rtpmap:0 PCMU/8000   a=rtpmap:1 1016/8000   a=rtpmap:3 GSM/8000   m=video 0 RTP/AVP 31 34   a=rtpmap:31 H261/90000   a=rtpmap:34 H263/90000   Figure 1: SDP Indicating Capabilities

Notes:

Location of "c=" line is invalid per RFC 2327 and RFC 4566. The corrected text reflects the "c=" line within a valid location.

Status:Rejected (2)

RFC 3264, "An Offer/Answer Model with Session Description Protocol (SDP)", June 2002

Note: This RFC has been updated byRFC 6157, RFC 8843, RFC 9143

Errata ID:5177
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Sandeep Kumar Aitha
Date Reported: 2017-11-03
Rejected by: Orie Steele
Date Rejected: 2024-05-09

Section 5.1 says:

Section 5.1 says:However, for sendonly and sendrecv streams, the answer might indicatedifferent payload type numbers for the same codecs, in which case,the offerer MUST send with the payload type numbers from the answer.Section 6.2 says:In the case of RTP, if a particular codec was referenced with aspecific payload type number in the offer, that same payload typenumber SHOULD be used for that codec in the answer.

It should say:

Only one of the above statements can be correct.

Notes:

Above two statements are conflicting.
The answerer should be able to either map the payload type to a different codec or not.
--VERIFIER NOTES--
See https://mailarchive.ietf.org/arch/msg/mmusic/HRD7ISwLIwiHOA73mc2KW680xAg/

Errata ID:7597
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Hugo Tunius
Date Reported: 2023-08-11
Rejected by: Orie Steele
Date Rejected: 2024-05-09

Section 6.1 says:

   The interpretation of fmtp parameters in an offer depends on the   parameters.  In many cases, those parameters describe specific   configurations of the media format, and should therefore be processed   as the media format value itself would be.  This means that the same   fmtp parameters with the same values MUST be present in the answer if   the media format they describe is present in the answer.  Other fmtp   parameters are more like parameters, for which it is perfectly   acceptable for each agent to use different values.  In that case, the   answer MAY contain fmtp parameters, and those MAY have the same   values as those in the offer, or they MAY be different.  SDP   extensions that define new parameters SHOULD specify the proper   interpretation in offer/answer.

It should say:

   The interpretation of fmtp parameters in an offer depends on the   parameters.  In many cases, those parameters describe specific   configurations of the media format, and should therefore be processed   as the media format value itself would be.  This means that the same   fmtp parameters with the same values MUST be present in the answer if   the media format they describe is present in the offer.  Other fmtp   parameters are more like parameters, for which it is perfectly   acceptable for each agent to use different values.  In that case, the   answer MAY contain fmtp parameters, and those MAY have the same   values as those in the offer, or they MAY be different.  SDP   extensions that define new parameters SHOULD specify the proper   interpretation in offer/answer.

Notes:

This indicated that the same fmtp parameters with the same values MUST be present in the answer if the media format they describe is present in the **answer**.

I believe the second instance of **answer** should be replace with **offer**, otherwise the quoted text does not makes sense I think.
--VERIFIER NOTES--
See https://mailarchive.ietf.org/arch/msg/mmusic/jDXva6XmGQ4Z6_PUW_TxhZp0-Hc/

Report New Errata