RFC Errata
Found 6 records.
Status: Verified (5)
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
Source of RFC: avt (rai)
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
Errata ID: 985
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
Appendix A, Table 8, says:
+-------------+---------------------------------------+-------------+ | Event Codes | RFC 2833 Description | Disposition | +-------------+---------------------------------------+-------------+ | 0-15 | DTMF digits | RFC 4733 | | 16 | Line flash (deprecated) | Reserved | | 23-31 | Unused | [16] | | 32-40 | Data and fax | [16] | | 41-48 | Data and fax (V.8bis, deprecated) | Reserved | | 52-63 | Unused | [16] | | 64-89 | E.182 line events (deprecated) | Reserved | | 96-112 | Country-specific line events | Reserved | | | (deprecated) | | | 121-127 | Unused | [17] | | 128-137 | Trunks: MF 0-9 | [17] | | 138-143 | Trunks: other MF (deprecated) | Reserved | | 144-159 | Trunks: ABCD signalling | [17] | | 160-168 | Trunks: various (deprecated) | Reserved | | 170-173 | Trunks: various (deprecated) | Reserved | | 174-205 | Unused | [17] | +-------------+---------------------------------------+-------------+
It should say:
+-------------+---------------------------------------+-------------+ | Event Codes | RFC 2833 Description | Disposition | +-------------+---------------------------------------+-------------+ | 0-15 | DTMF digits | RFC 4733 | | 16 | Line flash (deprecated) | Reserved | | 23-31 | Unused | [16] | | 32-40 | Data and fax | [16] | | 41-48 | Data and fax (V.8bis, deprecated) | Reserved | | | 49 | Calling Tone | [16] | | 52-63 | Unused | [16] | | 64-89 | E.182 line events (deprecated) | Reserved | | 96-112 | Country-specific line events | Reserved | | | (deprecated) | | | 121-127 | Unused | [17] | | 128-137 | Trunks: MF 0-9 | [17] | | 138-143 | Trunks: other MF (deprecated) | Reserved | | 144-159 | Trunks: ABCD signalling | [17] | | 160-168 | Trunks: various (deprecated) | Reserved | | 170-173 | Trunks: various (deprecated) | Reserved | | | 174-211 | Unused | [17] | +-------------+---------------------------------------+-------------+
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
Errata ID: 3489
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Xavier Marjou
Date Reported: 2013-02-18
Verifier Name: Gonzalo Camarillo
Date Verified: 2013-04-18
Section 2.1 says:
Named telephone events are carried as part of the audio stream and MUST use the same sequence number and timestamp base as the regular audio channel to simplify the generation of audio waveforms at a gateway.
It should say:
Named telephone events are carried as part of the audio stream and if they use the same SSRC (therefore the same timing and sequence number space), they MUST use the same timestamp clock rate as the regular audio channel.
Notes:
RFC4733 was written in a way to avoid the multiple clock-rate problem by mandating the use of the same SSRC for DTMF and audio. However it's not explicitly written, which brings an ambiguity. It was commented that RFC4733 needs to be updated. (c.f. http://tools.ietf.org/wg/avtext/minutes?item=minutes-85-avtext.html). This errata obsoletes the previous proposed errata (ID: 3451).
Errata ID: 986
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-12-19
Section 2.6.2 says:
the current duration of tone signal
It should say:
the current duration of a tone signal
Notes:
from pending
Errata ID: 987
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-12-19
Section 8 says:
Magnus Westerland
It should say:
Magnus Westerlund
Notes:
from pending
Status: Rejected (1)
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
Source of RFC: avt (rai)
Errata ID: 3451
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Xavier Marjou
Date Reported: 2013-01-11
Rejected by: Gonzalo Camarillo
Date Rejected: 2013-04-04
Section 2.1 says:
Named telephone events are carried as part of the audio stream and MUST use the same sequence number and timestamp base as the regular audio channel to simplify the generation of audio waveforms at a gateway.
It should say:
Named telephone events are carried as part of the audio stream and MUST use the same SSRC (therefore the same timing and sequence number space) and the same timestamp clock rate as the regular audio channel to simplify the generation of audio waveforms at a gateway.
Notes:
RFC4733 was written in a way to avoid the multiple clock-rate problem by mandating the use of the same SSRC for DTMF and audio. However it's not explicitly written, which brings an ambiguity. It was commented that RFC4733 needs to be updated. (c.f. http://tools.ietf.org/wg/avtext/minutes?item=minutes-85-avtext.html)
--VERIFIER NOTES--
Discussions around this erratum resulted in the updated 3489 erratum.