RFC Errata
Found 2 records.
Status: Verified (1)
RFC 6184, "RTP Payload Format for H.264 Video", May 2011
Source of RFC: avt (rai)
Errata ID: 3318
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Xiaohui Wei (Joanne)
Date Reported: 2012-08-14
Verifier Name: Gonzalo Camarillo
Date Verified: 2013-05-22
Section 8.1 says:
On page 46 start from line 7: "When max-dpb is signaled, the receiver MUST be able to decode NAL unit streams that conform to the signaled highest level, with the exception that the MaxDpbMbs value in Table A-1 of [1] for the signaled highest level is replaced with the value of max-dpb * 3 / 8. Consequently, a receiver that signals max-dpb ^^^^^ MUST be capable of storing the following number of decoded frames, complementary field pairs, and non-paired fields in its decoded picture buffer: Min(max-dpb * 3 / 8 / ( PicWidthInMbs * FrameHeightInMbs), ^^^^^ 16)"
It should say:
When max-dpb is signaled, the receiver MUST be able to decode NAL unit streams that conform to the signaled highest level, with the exception that the MaxDpbMbs value in Table A-1 of [1] for the signaled highest level is replaced with the value of max-dpb * 8 / 3. Consequently, a receiver that signals max-dpb ^^^^^ MUST be capable of storing the following number of decoded frames, complementary field pairs, and non-paired fields in its decoded picture buffer: Min(max-dpb * 8 / 3 / ( PicWidthInMbs * FrameHeightInMbs), ^^^^^ 16)
Status: Reported (1)
RFC 6184, "RTP Payload Format for H.264 Video", May 2011
Source of RFC: avt (rai)
Errata ID: 4713
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Iñaki Baz Castillo
Date Reported: 2016-06-17
Section 8.1 says:
profile-level-id: A base16 [7] (hexadecimal) representation of the following three bytes in the sequence parameter
It should say:
profile-level-id: A base16 [7] (hexadecimal) representation of the following six bytes in the sequence parameter
Notes:
profile-level-id is composed of three 2-byte length fields.