errata logo graphic

Found 1 record.

Status: Held for Document Update (1)

RFC4856, "Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences", February 2007

Source of RFC: avt (rai)

Errata ID: 1042

Status: Held for Document Update
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2007-03-07
Held for Document Update by: Robert Sparks

Section 5.1 says:

   [6]  Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson,
        "RTP:  A Transport Protocol for Real-Time Applications", RFC
        3550, July 2003.

...

   [8]  Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson,
        "RTP:  A Transport Protocol for Real-Time Applications", RFC
        3550, July 2003.

It should say:

   [6]  Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson,
        "RTP:  A Transport Protocol for Real-Time Applications", STD
        64, RFC 3550, July 2003.

Notes:

I find two Normative References, [6] and [8],
that *both* point to RFC 3550, the RTP specification.

I first thought there might something have gone wrong,
e.g., another ref. intended. Yet, it doesn't look like
that from the quotations in the text, in Section 2.1.1
and Section 4.

Furthermore, the ref. tag [6] in Section 2.1.1 is embedded
in an IANA registration template, where such ref. tags should
be avoided generally (as has been done in all similar cases
in the text: in Sections 2.1.2 - 2.1.19 and 2.2.1).
Removing that spurious tag orphans ref. [6] in RFC 4856 entirely.

Perhaps, it would have been better to add a formal ref. to RFC 3550
at the very beginning of the RFC, in the first sentence of Section 1:

This document updates the media type registrations initially
specified in RFC 3555 for the Real-time Transport Protocol (RTP)
payload formats defined in the RTP Profile for Audio and Video
Conferences, RFC 3551 [1], as subtypes under the "audio" and "video"
media types. [...]
--- vvvv
This document updates the media type registrations initially
| specified in RFC 3555 for the Real-time Transport Protocol (RTP) [8]
payload formats defined in the RTP Profile for Audio and Video
Conferences, RFC 3551 [1], as subtypes under the "audio" and "video"
media types. [...]

BTW:
The usual RFC references include the 'special series' names
as well; has there been a particular reason to omit "STD64, "
from the ref. to RFC 3550?
In RFC 4855, this observation also holds, for RFC 3550 and
for RFC 3551 (STD 65) as well.


Report New Errata