From 61c699c3fc12b37365b63cf6279a758ffdea69f3 Mon Sep 17 00:00:00 2001 From: ivo Date: Sun, 18 Nov 2007 00:17:40 +0000 Subject: [PATCH] a bunch of tiny fixes svn path=/trunk/vorbis/; revision=14178 --- doc/draft-ietf-avt-rtp-vorbis-08.xml | 98 ++++++++++++++++++------------------ 1 file changed, 49 insertions(+), 49 deletions(-) diff --git a/doc/draft-ietf-avt-rtp-vorbis-08.xml b/doc/draft-ietf-avt-rtp-vorbis-08.xml index f3b6afb..9b66079 100644 --- a/doc/draft-ietf-avt-rtp-vorbis-08.xml +++ b/doc/draft-ietf-avt-rtp-vorbis-08.xml @@ -1,18 +1,19 @@ - - + + - + + - + -draft-ietf-avt-rtp-vorbis-08 +RTP Payload Format for Vorbis Encoded Audio -Xiph.Org +Xiph.Org Foundation
lu_zero@gentoo.org -http://www.xiph.org/ +http://xiph.org/
@@ -74,12 +75,11 @@ For the purposes of RTP transport, this layer is unnecessary, and so raw Vorbis packets are used in the payload. -
+
- -The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" -in this document are to be interpreted as described in RFC 2119 . - +The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, and indicate requirement levels for compliant implementations. Requirements apply to all implementations unless otherwise stated. +An implementation is a software module that supports one of the media types defined in this document. Software modules may support multiple media types, but conformance is considered individually for each type. +Implementations that fail to satisfy one or more "MUST" requirements are considered non-compliant. Implementations that satisfy all "MUST" requirements, but fail to satisfy one or more "SHOULD" requirements, are said to be "conditionally compliant". All other implementations are "unconditionally compliant".
@@ -435,7 +435,7 @@ The RTP timestamp value MUST reflect the transmission time of the next data pack A Vorbis Packed Configuration is indicated with the Vorbis Data Type field set to 1. Of the three headers defined in the Vorbis I specification, the -Identification and the Setup MUST be packed as they are, while the comment header MAY be replaced with a dummy one. The packed configuration follows a generic way to store xiph codec configurations: The first field stores the number of the following packets minus one (count field), the next ones represent the size of the headers (length fields), the headers immediately follow the list of length fields. The size of the last header is implicit. +Identification and the Setup MUST be packed as they are, while the comment header MAY be replaced with a dummy one. The packed configuration follows a generic way to store Xiph codec configurations: The first field stores the number of the following packets minus one (count field), the next ones represent the size of the headers (length fields), the headers immediately follow the list of length fields. The size of the last header is implicit. The count and the length fields are encoded using the following logic: the data is in network byte order, every byte has the most significant bit used as flag and the following 7 used to store the value. The first N bit are to be taken, where N is number of bits needed to represent the value, taken modulo 7, and stored in the first byte. If there are more bits, the flag bit is set to 1 and the subsequent 7bit are stored in the following byte, if there are remaining bits set the flag to 1 and the same procedure is repeated. The ending byte has the flag bit set to 0. In order to decode it is enough to iterate over the bytes until the flag bit set to 0, for every byte the data is added to the accumulated value multiplied by 128. @@ -854,7 +854,7 @@ None RFC XXXX [RFC Editor: please replace by the RFC number of this memo, when published] -Ogg Vorbis I specification: Codec setup and packet decode. Available from the Xiph website, http://www.xiph.org +Ogg Vorbis I specification: Codec setup and packet decode. Available from the Xiph website, http://xiph.org @@ -1187,7 +1187,7 @@ continuation of draft-short-avt-rtp-vorbis-mime-00.txt. -Thanks to the AVT, Ogg Vorbis Communities / Xiph.org including Steve Casner, +Thanks to the AVT, Vorbis Communities / Xiph.Org Foundation including Steve Casner, Aaron Colwell, Ross Finlayson, Fluendo, Ramon Garcia, Pascal Hennequin, Ralph Giles, Tor-Einar Jarnbjo, Colin Law, John Lazzaro, Jack Moffitt, Christopher Montgomery, Colin Perkins, Barry Short, Mike Smith, Phil Kerr, Michael Sparks, @@ -1210,7 +1210,7 @@ Ridolfo, Francesco Varano, Giampaolo Mancini, Dario Gallucci, Juan Carlos De Mar - + @@ -1235,51 +1235,51 @@ Ridolfo, Francesco Varano, Giampaolo Mancini, Dario Gallucci, Juan Carlos De Mar - + -Uniform Resource Identifier (URI): Generic Syntax - +Uniform Resource Identifier (URI): Generic Syntax + - + - + - + - + - + SDP: Session Description Protocol - + - + - + - + - - + + - + Path MTU discovery - + Digital Equipment Corporation (DEC) , Western Research Laboratory
mogul@decwrl.dec.com
 - + Xerox Palo Alto Research Center
deering@xerox.com
 - + - - + + @@ -1297,7 +1297,7 @@ Ridolfo, Francesco Varano, Giampaolo Mancini, Dario Gallucci, Juan Carlos De Mar - + @@ -1327,9 +1327,9 @@ Ridolfo, Francesco Varano, Giampaolo Mancini, Dario Gallucci, Juan Carlos De Mar -libvorbis: Available from the dedicated website, http://www.vorbis.com +libvorbis: Available from the dedicated website, http://vorbis.com - + @@ -1341,24 +1341,24 @@ Ridolfo, Francesco Varano, Giampaolo Mancini, Dario Gallucci, Juan Carlos De Mar - + RTP Retransmission Payload Format - + - + - + - + - + - + - - + + - + \ No newline at end of file -- 2.7.4