RFC Errata
Found 4 records.
Status: Verified (1)
RFC 3264, "An Offer/Answer Model with Session Description Protocol (SDP)", June 2002
Source of RFC: mmusic (rai)
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: Reported (1)
RFC 3264, "An Offer/Answer Model with Session Description Protocol (SDP)", June 2002
Source of RFC: mmusic (rai)
Errata ID: 5177
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Sandeep Kumar Aitha
Date Reported: 2017-11-03
Section 5.1 says:
Section 5.1 says: However, for sendonly and sendrecv streams, the answer might indicate different 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 a specific payload type number in the offer, that same payload type number 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.
Status: Held for Document Update (2)
RFC 3264, "An Offer/Answer Model with Session Description Protocol (SDP)", June 2002
Source of RFC: mmusic (rai)
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.