RFC 4733, "RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals", December 2006

Note: This RFC has been updated by RFC 4734, RFC 5244

Errata ID: 984
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-12-19
Verifier Name: Tom Taylor
Date Verified: 2006-12-19

Section 7 says:

   Legal event codes range from 0 to 255.  The initial registry content
   is shown in Table 7, and consists of the sixteen events defined in
   Section 3 of this document.  The remaining codes have the following
   disposition:

   o  codes 17-22, 50-51, 90-95, 113-120, 169, and 206-255 are available
      for assignment;

   o  codes 23-40, 49, and 52-63 are reserved for events defined in
      [16];

   o  codes 121-137 and 174-205 are reserved for events defined in [17];

   o  codes 16, 41-48, 64-88, 96-112, 138-168, and 170-173 are reserved
      in the first instance for specifications reviving the
      corresponding RFC 2833 events, and in the second instance for
      general assignment after all other codes have been assigned.

It should say:

   Legal event codes range from 0 to 255.  The initial registry content
   is shown in Table 7, and consists of the sixteen events defined in
   Section 3 of this document.  The remaining codes have the following
   disposition:

|  o  codes 17-22, 50-51, 90-95, 113-120, 169, and 212-255 are available
      for assignment;
                                                   ^^^

   o  codes 23-40, 49, and 52-63 are reserved for events defined in
      [16];

|  o  codes 121-137, 144-159, and 174-211 are reserved for events
      defined in [17];
                   ^^^^^^^^^^         ^^^
                          vv             vvvvvvvvvv
|  o  codes 16, 41-48, 64-89, 96-112, 138-143, 160-168, and 170-173 are
      reserved in the first instance for specifications reviving the
      corresponding RFC 2833 events, and in the second instance for
      general assignment after all other codes have been assigned.

Notes:

Section 7 of RFC 4733, in the lower half of page 39,
specifies the initial content of the IANA maintained
audio-telephone-event-registry subregistry, as intended
for after publication of RFC 4733 -- see (1a) below.

Additionally, in Appendix A, on page 47, RFC 4733 restates this
information and summarizes the disposition of the legacy event
code assignments from the obsoleted RFC 2833, in particular,
Table 8 represents the current assignments and dispositions,
as per RFC 4733 -- see (1b) below.

Unfortunately, there are significant inconsistencies between
these two text blocks. Looking into Ref. [17] of RFC 4733,
the ietf-avt-rfc2833biscas draft, it turns out that both
text blocks are also inconsistent with that future RFC.
Consequently, the current IANA file is also affected.

from pending

Report New Errata