RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 5215, "RTP Payload Format for Vorbis Encoded Audio", August 2008

Source of RFC: avt (rai)

Errata ID: 1659
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2009-01-26
Held for Document Update by: Cullen Jennings

Section 2.2, pg.6 says:

   This field specifies the kind of Vorbis data stored in this RTP
   packet.  There are currently three different types of Vorbis
   payloads.  Each packet MUST contain only a single type of Vorbis
   packet (e.g., you must not aggregate configuration and comment
   packets in the same RTP payload).

      0 = Raw Vorbis payload

      1 = Vorbis Packed Configuration payload

      2 = Legacy Vorbis Comment payload

      3 = Reserved

It should say:

   This field specifies the kind of Vorbis data stored in this RTP
|  payload.  There are currently three different types of Vorbis
|  packets.  Each RTP payload MUST contain only a single type of Vorbis
   packet (e.g., you must not aggregate configuration and comment
   packets in the same RTP payload).

|     0 = Raw Vorbis packet

|     1 = Vorbis Packed Configuration packet

|     2 = Legacy Vorbis Comment packet

      3 = Reserved

Notes:

Rationale:

The RFC is about an RTP *payload* format, and, according to
section 1 of the RFC, deals with Vorbis *packets* -- to be
encapsulated in the RTP payload.

Section 2.2 explains the RTP Payload Header vor Vorbis. Thus,
the use of "payload" and "packet" in the Original Text does
not match these definitions and hence might well be confusing.
The Corrected Text aims at placing the proper terms there.

Report New Errata