Errata Search
RFC Number:		Errata ID:
Source of RFC		Status:	All/Any Verified+Reported Verified Reported Held for Document Update Rejected
Area Acronym:	All/Any app art gen int ops rai rtg sec tsv wit	Type:	All/Any Editorial Technical
WG Acronym:		Submitter Name:
Other:	All/Any IAB INDEPENDENT IRTF Legacy Editorial	Date Submitted:
Summary Table Full Records

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: 6013
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Dai Rees
Date Reported: 2020-03-10

Section 3.3 says:

For example, MPEG-4 Visual Simple Profile Level 0 has the value 9, so a complete string for MPEG-4 Visual Simple Profile Level 0 would be "mp4v.20.9".

[...]

Content-Type: video/3gpp2; codecs="mp4v.20.9, mp4a.E1"
    (MPEG-4 Visual Simple Profile Level 0 plus 13K voice)

It should say:

For example, MPEG-4 Part 2 Visual "Simple Profile" Level 0 has the value 8, so a complete string for MPEG-4 Part 2 Visual "Simple Profile" Level 0 would be "mp4v.20.8".

[...]

Content-Type: video/3gpp2; codecs="mp4v.20.8, mp4a.E1"
    (MPEG-4 Visual Simple Profile Level 0 plus 13K voice)

Notes:

The MPEG-4 Visual Part 2, Annex G table G.1 lists the "Simple Profile/Level 0" profile-and-level indication code as 00001000 (decimal 8), and states that the indication code 00001001 (decimal 9) is Reserved.

RFC6381 gives an example stating "MPEG-4 Visual Simple Profile Level 0 has the value 9" - but this is incorrect because the specification states the value 9 is reserved and that Simple Profile with Level 0 is 8.

Report New Errata