Found 2 records.

Status: Verified (1)

RFC 8851, "RTP Payload Format Restrictions", January 2021

Errata ID: 7132
Status: Verified
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Byron Campen
Date Reported: 2022-09-14
Verifier Name: Murray Kucherawy
Date Verified: 2022-10-13

Section 10 says:

rid-id            = 1*(alpha-numeric / "-" / "_")

It should say:

rid-id            = 1*255(alpha-numeric)

Notes:

The BNF should be consistent with the rules for the RtpStreamId/RepairedRtpStreamId SDES from RFC 8852 section 3:

"As with all SDES items, RtpStreamId and RepairedRtpStreamId are limited to a total of 255 octets in length. RtpStreamId and RepairedRtpStreamId are constrained to contain only alphanumeric characters. For avoidance of doubt, the only allowed byte values for these IDs are decimal 48 through 57, 65 through 90, and 97 through 122."

Status: Reported (1)

RFC 8851, "RTP Payload Format Restrictions", January 2021

Errata ID: 8833
Status: Reported
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Aron Rosenberg
Date Reported: 2026-03-17

Section 8.2.2 says:

The H.264 "MaxBR" parameter (and its equivalent "max-br" format
   parameter) corresponds to the "max-bps" restriction defined in this
   specification, by way of a conversion factor of 1000 or 1200; see
   [RFC6184] for details regarding which factor gets used under
   differing circumstances.

It should say:

The H.264 "MaxBR" parameter (and its equivalent "max-br" format
   parameter) corresponds to the "max-br" restriction defined in this
   specification, by way of a conversion factor of 1000 or 1200; see
   [RFC6184] for details regarding which factor gets used under
   differing circumstances.

Notes:

Incorrectly refers to a previous name used for the max-br parameter. There is no value called max-bps in this spec, it is now called max-br.

Report New Errata