RFC Errata
Found 5 records.
Status: Verified (1)
RFC 4566, "SDP: Session Description Protocol", July 2006
Note: This RFC has been obsoleted by RFC 8866
Source of RFC: mmusic (rai)
Errata ID: 1089
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Colin Perkins
Date Reported: 2007-12-06
Verifier Name: Cullen Jennings
Date Verified: 2009-01-08
Section 9 says:
IP6-multicast = hexpart [ "/" integer ] IP6-address = hexpart [ ":" IP4-address ] hexpart = hexseq / hexseq "::" [ hexseq ] / "::" [ hexseq ] hexseq = hex4 *( ":" hex4) hex4 = 1*4HEXDIG
It should say:
IP6-multicast = IP6-address [ "/" integer ] IP6-address = 6( h16 ":" ) ls32 / "::" 5( h16 ":" ) ls32 / [ h16 ] "::" 4( h16 ":" ) ls32 / [ *1( h16 ":" ) h16 ] "::" 3( h16 ":" ) ls32 / [ *2( h16 ":" ) h16 ] "::" 2( h16 ":" ) ls32 / [ *3( h16 ":" ) h16 ] "::" h16 ":" ls32 / [ *4( h16 ":" ) h16 ] "::" ls32 / [ *5( h16 ":" ) h16 ] "::" h16 / [ *6( h16 ":" ) h16 ] "::" h16 = 1*4HEXDIG ls32 = ( h16 ":" h16 ) / IP4-address
Notes:
Correct IPv6 ABNF.
Status: Reported (4)
RFC 4566, "SDP: Session Description Protocol", July 2006
Note: This RFC has been obsoleted by RFC 8866
Source of RFC: mmusic (rai)
Errata ID: 5595
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Gavin Scallan
Date Reported: 2019-01-08
Section 5 says:
An example SDP description is: v=0 o=jdoe 2890844526 2890842807 IN IP4 10.47.16.5 s=SDP Seminar i=A Seminar on the session description protocol u=http://www.example.com/seminars/sdp.pdf e=j.doe@example.com (Jane Doe) c=IN IP4 224.2.17.12/127 t=2873397496 2873404696 a=recvonly m=audio 49170 RTP/AVP 0 m=video 51372 RTP/AVP 99 a=rtpmap:99 h263-1998/90000
It should say:
An example SDP description is: v=0 o=jdoe 2890844526 2890842807 IN IP4 10.47.16.5 s=SDP Seminar i=A Seminar on the session description protocol u=http://www.example.com/seminars/sdp.pdf e=j.doe@example.com (Jane Doe) c=IN IP4 224.2.17.12/127 a=recvonly t=2873397496 2873404696 m=audio 49170 RTP/AVP 0 m=video 51372 RTP/AVP 99 a=rtpmap:99 h263-1998/90000
Notes:
In section 5 it indicates that the SDP lines MUST appear in the exact order given at the top of Page 9.
The order that is shown indicates that the Session Attributes appear before the Time Description.
However in the example included in this section which explains that Media Attributes have precedence over Session Attributes for a media stream contradicts the order as the Session Attribute of sendonly is included below the Time Description.
Either the example is incorrect, or the normative description is poorly explained and some variability in the order of lines in the SDP is allowed.
Errata ID: 6022
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Megan Ruggiero
Date Reported: 2020-03-16
Section 9 says:
; sub-rules of 'e=', see RFC 2822 for definitions email-address = address-and-comment / dispname-and-address / addr-spec address-and-comment = addr-spec 1*SP "(" 1*email-safe ")" dispname-and-address = 1*email-safe 1*SP "<" addr-spec ">" ; sub-rules of 'p=' phone-number = phone *SP "(" 1*email-safe ")" / 1*email-safe "<" phone ">" / phone
It should say:
; sub-rules of 'e=', see RFC 2822 for definitions email-address = address-and-comment / dispname-and-address / addr-spec address-and-comment = addr-spec 1*SP "(" 1*email-safe ")" dispname-and-address = 1*email-safe 1*SP "<" addr-spec ">" ; sub-rules of 'p=' phone-number = phone *SP "(" 1*email-safe ")" / 1*email-safe 1*SP "<" phone ">" / phone
Notes:
There's an inconsistency between the definitions of dispname-and-address and phone-number. I am not sure if this is intentional or not, and in practice this doesn't change what's matched (as email-safe includes spaces), but I thought it'd be worth mentioning since I myself got tripped up when translating the grammar.
Alternatively, perhaps 1*SP should be removed from dispname-and-address.
Errata ID: 4903
Status: Reported
Type: Editorial
Publication Format(s) : TEXT
Reported By: Jxck
Date Reported: 2017-01-12
Section 9 says:
; SDP Syntax session-description = proto-version origin-field session-name-field information-field uri-field email-fields phone-fields connection-field bandwidth-fields time-fields key-field attribute-fields media-descriptions connection-field = [%x63 "=" nettype SP addrtype SP connection-address CRLF] ;a connection field must be present ;in every media description or at the ;session-level media-descriptions = *( media-field information-field *connection-field bandwidth-fields key-field attribute-fields )
It should say:
; SDP Syntax session-description = proto-version origin-field session-name-field information-field uri-field email-fields phone-fields [connection-field] bandwidth-fields time-fields key-field attribute-fields media-descriptions connection-field = %x63 "=" nettype SP addrtype SP connection-address CRLF ;a connection field must be present ;in every media description or at the ;session-level media-descriptions = *( media-field information-field *connection-field bandwidth-fields key-field attribute-fields )
Notes:
in BNF of SDP,
connection-field itself is optional [0, 1], but media-description has multiple [0,) connection-field.
it seems conflict, because multiple of optional fields doesn't finish because multiple filed can't find when to end.
so change connection-field itself not optional (remove []) and, replace session-descriptions connection-field as optional.
Errata ID: 5183
Status: Reported
Type: Editorial
Publication Format(s) : TEXT
Reported By: no space before encoding parameter in rtpmap value
Date Reported: 2017-11-14
Section 6. SDP Attr says:
a=rtpmap:<payload type> <encoding name>/<clock rate> [/<encoding parameters>]
It should say:
a=rtpmap:<payload type> <encoding name>/<clock rate>[/<encoding parameters>]
Notes:
rtpmap requires format below
a=rtpmap:97 L16/8000
a=rtpmap:98 L16/11025/2
no space between clock rate and optional parameter