RFC Errata
Found 3 records.
Status: Verified (2)
RFC 3108, "Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer Connections", May 2001
Source of RFC: mmusic (rai)
Errata ID: 332
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Rajesh Kumar
Date Reported: 2002-05-22
Section 5.6 says:
The base specification for SDP, RFC 2327 [1], allows the definition f new attributes. In keeping with this spirit, some of the attributes defined in this document can also be used in SDP descriptions of IP nd other non-ATM sessions. For example, the 'vsel', 'dsel' and 'fsel' attributes defined below refer generically to codec-s. These can be bed for service-specific codec negotiation and assignment in non-ATM s well as ATM applications.
It should say:
The base specification for SDP, RFC 2327 [1], allows the definition of new attributes. In keeping with this spirit, some of the attributes defined in this document can also be used in SDP descriptions of IP and other non-ATM sessions. For example, the 'vsel', 'dsel' and 'fsel' attributes defined below refer generically to codecs. These can be used for service-specific codec negotiation and assignment in non-ATM as well as ATM applications.
Notes:
In Section 5.6.3: (First, Second and Third Bulleted items in List)
* The 'silenceSupp' attribute, used to indicate the use of of
voice activity detection for silence suppression, and to
optionally parameterize the silence suppression function.
* The 'ecan' attribute, used to indicate the use of of echo
cancellation, and to parameterize the this function.
* The 'gc' attribute, used to indicate the use of of gain
control, and to parameterize the this function.
Should be:
* The 'silenceSupp' attribute, used to indicate the use of
voice activity detection for silence suppression, and to
optionally parameterize the silence suppression function.
* The 'ecan' attribute, used to indicate the use of echo
cancellation, and to parameterize the this function.
* The 'gc' attribute, used to indicate the use of gain
control, and to parameterize the this function.
In Section 5.6.3.3:
When present, the 'ecan' attribute s is used to indicate the use or
non-use of echo cancellation. There can be several 'ecan' lines in
an SDP description.
Should be:
When present, the 'ecan' attribute is used to indicate the use or
non-use of echo cancellation. There can be several 'ecan' lines in
an SDP description.
In Section 5.6.6: (First numbered item)
(1) The originating media gateway controller (OMGC) initiates
service-level call establishment by sending the appropriate
controlsmessage to the originating media gateway (OMG).
Should be:
(1) The originating media gateway controller (OMGC) initiates
service-level call establishment by sending the appropriate
control message to the originating media gateway (OMG).
In Section 6: (Sixth definition from top)
<vci> Virtual Circui t Decimal or hex equivalent
Identifier of 16 bits
Should be:
<vci> Virtual Circuit Decimal or hex equivalent
Identifier of 16 bits
Errata ID: 8446
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Robert Hanton
Date Reported: 2025-06-03
Verifier Name: Andy Newton
Date Verified: 2025-11-01
Section 5.6.3.2 says:
When present, the 'silenceSupp' attribute is used to indicate the use or non-use of silence suppression. The format of the 'silenceSupp' media attribute line is as follows: a=silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse> <fxnslevel>
It should say:
When present, the 'silenceSupp' attribute is used to indicate the use or non-use of silence suppression. The format of the 'silenceSupp' media attribute line is as follows: a=silenceSupp:<silenceSuppEnable> <silenceTimer> <suppPref> <sidUse> <fxnslevel>
Notes:
There is a space after the colon in the format of the 'silenceSupp' attribute. This does not match the a=<attribute>:<value> format specified in RFC2327 (which would have been normative at the time) or the two RFCs that superceded it, or the corresponding ABNF.
It also does not match the ABNF given for the attribute itself in section 9 of the RFC (RFC3108), which is "silenceSupp" ":" silenceSuppEnable space silenceTimer space suppPref space sidUse space fxnslevel / .
While I am submitting this errata as an example of the issue for review, a considerable number of other attributes in the document also exhibit this same issue in their format definitions. If this errata is accepted I can file matching errata for all other similar errors.
Status: Held for Document Update (1)
RFC 3108, "Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer Connections", May 2001
Source of RFC: mmusic (rai)
Errata ID: 8452
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Dale R. Worley
Date Reported: 2025-06-05
Held for Document Update by: Andy Newton
Date Held: 2025-11-01
Section 9 says:
See detailed discussion below.
It should say:
See detailed discussion below.
Notes:
This is an extension of erratum 8446.
There seems to be a technical problem with some of the ABNF. In
section 9, the definition of "atm-attribute" includes these clauses,
which generate trailing spaces in the a-lines. I doubt that this is
intended.
"profileDesc" ":" aal2-transport space profile space
1*(profile-row) /
"vsel" ":" 1*(encoding-name space packet-length space
packet-time space) /
"dsel" ":" fxIncl space
1*(encoding-name space packet-length space
packet-time space) /
"fsel" ":" 1*(encoding-name space packet-length space
packet-time space) /
"onewaySel" ":" serviceType space directionFlag space
1*(encoding-name space packet-length space
packet-time space) /
The clause for "profileDesc" refers to this definition:
profile-row = uuiCodeRange space encoding-name space packet-length
space packet-time space
These revisions seem to be unexceptionable:
"profileDesc" ":" aal2-transport space profile
1*(profile-row) /
profile-row = space uuiCodeRange space encoding-name space packet-length
space packet-time
"dsel" ":" fxIncl
1*(space encoding-name space packet-length space
packet-time) /
"onewaySel" ":" serviceType space directionFlag
1*(space encoding-name space packet-length space
packet-time) /
The rules for vsel and fsel require a little more care:
"vsel" ":" encoding-name space packet-length space
packet-time
0*(space encoding-name space packet-length space
packet-time) /
"fsel" ":" encoding-name space packet-length space
packet-time
0*(space encoding-name space packet-length space
packet-time) /
but perhaps we want to break out a separate nonterminal for the
repeated parts of vsel and fsel. Indeed, "space encoding-name space
packet-length space packet-time" appears in dsel, onewaySel, vsel, and
fsel. That would give
sel-encoding = encoding-name space packet-length space packet-time
"vsel" ":" sel-encoding 0*(space sel-encoding) /
"dsel" ":" fxIncl 1*(space sel-encoding) /
"fsel" ":" sel-encoding 0*(space sel-encoding) /
"onewaySel" ":" serviceType space directionFlag
1*(space sel-encoding) /
In addition, there are some editorial problems with the illustrations
of the attributes. In some of them, there is an extraneous space
shown after the initial colon. In others, a mandatory space between
fields is not shown. Specifically, these lines should be revised,
either to remove the space shown after the colon, or to add spaces
between fields:
a=atmQOSparms:<directionFlag><cdvType><acdv><ccdv><eetd><cmtd><aclr>
a=atmTrfcDesc:<directionFlag><clpLvl>
<pcr><scr><mbs><cdvt><mcr><mfs><fd><te>
a=abrParms:<directionFlag><nrm><trm><cdf><adtf>
a=abrSetup:<ficr><bicr><ftbe><btbe><crmrtt><frif><brif><frdf><brdf>
a=bearerType: <bearerType> <localInitiation>
a=lij: <sci><lsn>
a=anycast: <atmGroupAddress> <cdStd> <conScpTyp> <conScpSel>
a=cache:<cacheEnable><cacheTimer>
a=bearerSigIE: <bearerSigIEType> <bearerSigIELng> <bearerSigIEVal>
a=aalApp: <appClass> <oui> <appId>
a=cbrRate: <cbrRate>
a=structure: <structureEnable> <blksz>
a=cpsSDUsize:<directionFlag><cpcs>
a=aal2CPS:<cidLowerLimit><cidUpperLimit><timerCU> <simplifiedCPS>
a=aal2CPSSDUrate: <fSDUrate><bSDUrate>
a=aal2sscs3661unassured: <ted> <rastimer> <fsssar> <bsssar>
a=aal2sscs3661assured: <rastimer> <fsssar> <bsssar> <fsscopsdu>
<bsscopsdu><fsscopuu> <bsscopuu>
a=aal2sscs3662: <sap> <circuitMode> <frameMode> <faxDemod>
<cas> <dtmf> <mfall> <mfr1> <mfr2>
<PCMencoding> <fmaxFrame> <bmaxFrame>
a=aal5sscop: <fsscopsdu> <bsscopsdu> <fsscopuu> <bsscopuu>
a=silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse>
<fxnslevel>
a=ecan:<directionFlag><ecanEnable><ecanType>
a=gc:<directionFlag><gcEnable><gcLvl>
a=profileDesc: <aal2transport> <profile> <uuiCodeRange#1>
<encodingName#1> <packetLength#1> <packetTime#1>
<uuiCodeRange#2> <encodingName#2> <packetLength#2>
<packetTime#2>... <uuiCodeRange#N> <encodingName#N>
<packetLength#N> <packetTime#N>
a=vsel:<encodingName #1> <packetLength #1><packetTime #1>
<encodingName #2> <packetLength #2><packetTime #2>
...
<encodingName #N> <packetLength #N><packetTime #N>
a=dsel:<fxIncl> <encodingName #1> <packetLength #1><packetTime #1>
<encodingName #2> <packetLength #2><packetTime #2>
...
<encodingName #N> <packetLength #N><packetTime #N>
a=fsel:<encodingName #1> <packetLength #1><packetTime #1>
<encodingName #2> <packetLength #2><packetTime #2>
...
<encodingName #N> <packetLength #N><packetTime #N>
a=onewaySel:<serviceType> <directionFlag>
<encodingName #1> <packetLength #1><packetTime #1>
<encodingName #2> <packetLength #2><packetTime #2>
...
<encodingName #N> <packetLength #N><packetTime #N>
And this line has extraneous single-quotes:
a='uiLayer1_Prot':<uiLayer1Prot>