RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Reported (2)

RFC 6381, "The 'Codecs' and 'Profiles' Parameters for "Bucket" Media Types", August 2011

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 5473
Status: Reported
Type: Technical

Reported By: Peter Occil
Date Reported: 2018-08-20

Section 3.2 says:

   The 'codecs' parameter takes either of two forms.  The first form is
   used when the value does not contain any octets that require
   encoding.  The second form uses [RFC2231] to allow arbitrary octets
   to be encoded.  With either form, quotes allow for commas and other
   characters in <tspecials> (quotes MAY be used even when not
   required).

 [...]

   The BNF syntax is as follows:

 [...]

      fancy-list  := DQUOTE [charset] "'" [language] "'" id-list DQUOTE
                  ; Parsers MAY ignore <language>
                  ; Parsers MAY support only US-ASCII and UTF-8

It should say:

   The 'codecs' parameter takes either of two forms.  The first form is
   used when the value does not contain any octets that require
   encoding.  The second form uses [RFC2231] to allow arbitrary octets
   to be encoded.  With the first form only, quotes allow for commas and other
   characters in <tspecials> (quotes MAY be used even when not
   required).

 [...]

   The BNF syntax is as follows:

 [...]

      fancy-list  := [charset] "'" [language] "'" fancy-id-list
                  ; Parsers MAY ignore <language>
                  ; Parsers MAY support only US-ASCII and UTF-8
      fancy-id-list     := id-encoded *( "%2c" id-encoded )


Notes:

RFC 6381's definition of "codecs" (and "profiles") conflicts with the generic syntax for RFC 2231 section 4 character set and language information. Notably, RFC 2231 (which changes the syntax in RFC 2045 in a manner relevant here) disallows quoted strings as the attribute value if a parameter name ends with an asterisk (see the productions "extended-initial-value" and "extended-other-values" in RFC 2231). Thus, for example, the example

codecs*="''%25%20xz, gork"

is ill-formed under RFC 2231, since it uses a quoted-string in a parameter name ending in "*".

This erratum shows the correction only in section 3.1, but conforming corrections may need to be made elsewhere in the document.

Errata ID: 5524
Status: Reported
Type: Technical

Reported By: Alex Converse
Date Reported: 2018-10-12

Section 3.3 says:

   One of the OTI values for 'mp4a' is 40 (identifying MPEG-4 audio).
   For this value, the third element identifies the audio
   ObjectTypeIndication (OTI) as defined in [MP4A] (including
   amendments), expressed as a decimal number.

It should say:

   One of the OTI values for 'mp4a' is 40 (identifying MPEG-4 audio).
   For this value, the third element identifies the AudioObjectType 
   (AOT) as defined in [MP4A] (including amendments), expressed as a 
   decimal number.

Notes:

[MP4A] "Information technology--Coding of audio-visual objects -- 3: Audio", ISO/IEC 14496-3:2009. Only speaks of ObjectTypeIndications in the context of systems OTIs in the previous paragraph and never mentions "audio ObjectTypeIndication". In the example that follows the third element is an "AudioObjectType".

Report New Errata