RFC Errata
Found 2 records.
Status: Verified (1)
RFC 5939, "Session Description Protocol (SDP) Capability Negotiation", September 2010
Note: This RFC has been updated by RFC 6871
Source of RFC: mmusic (rai)
Errata ID: 3545
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Dale Worley
Date Reported: 2013-03-11
Verifier Name: Gonzalo Camarillo
Date Verified: 2013-04-03
Section 3.4.1 says:
a=acap:2 a=pcfg:1 t=1 a=1 ;Not allowed to embed "pcfg"
It should say:
a=acap:2 pcfg:1 t=1 a=1 ;Not allowed to embed "pcfg"
Notes:
The existing text, with "a=" before "pcfg", is outright syntactically incorrect per the syntax in the first paragraph of the section. The correction is needed for the text to be the intended demonstration of a semantic error.
Status: Reported (1)
RFC 5939, "Session Description Protocol (SDP) Capability Negotiation", September 2010
Note: This RFC has been updated by RFC 6871
Source of RFC: mmusic (rai)
Errata ID: 5042
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Typo in example
Date Reported: 2017-06-16
Section 4.2 says:
m=audio 59000 UDP/TLS/RTP/AVP 98
It should say:
m=audio 59000 UDP/TLS/RTP/SAVP 98
Notes:
The example missed an S in the mine type. The list of allowed types is at https://www.iana.org/assignments/sdp-parameters/sdp-parameters.xhtml#sdp-parameters-2 and UDP/TLS/RTP/AVP is not a registered device. Because this is over TLS, it is a SRTP (not RTP) and should use SAVP not AVP.