draft-ietf-avt-rtp-vorbis-04.xml 51.2 KB
Newer Older
lu_zero's avatar
lu_zero committed
1 2 3 4 5 6 7 8
<?xml version='1.0'?>
<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
<?rfc toc="yes" ?>
<?rfc compact='yes'?>

<rfc ipr="full3978" docName="RTP Payload Format for Vorbis Encoded Audio">

<front>
lu_zero's avatar
lu_zero committed
9
<title>draft-ietf-avt-rtp-vorbis-04</title>
lu_zero's avatar
lu_zero committed
10 11 12 13 14 15 16 17 18

<author initials="L" surname="Barbato" fullname="Luca Barbato">
<organization>Xiph.Org</organization>
<address>
<email>lu_zero@gentoo.org</email>
<uri>http://www.xiph.org/</uri>
</address>
</author>

lu_zero's avatar
lu_zero committed
19
<date day="04" month="May" year="2007" />
lu_zero's avatar
lu_zero committed
20 21 22 23 24 25 26 27 28 29

<area>General</area>
<workgroup>AVT Working Group</workgroup>
<keyword>I-D</keyword>

<keyword>Internet-Draft</keyword>
<keyword>Vorbis</keyword>
<keyword>RTP</keyword>

<abstract>
lu_zero's avatar
lu_zero committed
30

lu_zero's avatar
lu_zero committed
31
<t>
lu_zero's avatar
lu_zero committed
32 33 34 35
This document describes an RTP payload format for transporting Vorbis encoded
audio. It details the RTP encapsulation mechanism for raw Vorbis data and 
details the delivery mechanisms for the decoder probability model, referred to
as a codebook and other setup information.
lu_zero's avatar
lu_zero committed
36 37 38
</t>

<t>
lu_zero's avatar
lu_zero committed
39 40
Also included within this memo are media type registrations, and the details
necessary for the use of Vorbis with the Session Description Protocol (SDP).
lu_zero's avatar
lu_zero committed
41 42 43 44 45 46
</t>

</abstract>

<note title="Editors Note">
<t>
lu_zero's avatar
lu_zero committed
47 48
All references to RFC XXXX are to be replaced by references to the RFC number
of this memo, when published.
lu_zero's avatar
lu_zero committed
49 50 51 52 53 54 55 56 57 58 59 60 61 62
</t>
</note>

</front>

<middle>

<section anchor="Introduction" title="Introduction">

<t>
Vorbis is a general purpose perceptual audio codec intended to allow 
maximum encoder flexibility, thus allowing it to scale competitively 
over an exceptionally wide range of bitrates. At the high 
quality/bitrate end of the scale (CD or DAT rate stereo, 16/24 bits), it 
63 64
is in the same league as AAC.
Vorbis is also intended for lower and higher sample rates (from 
lu_zero's avatar
lu_zero committed
65 66 67 68 69 70
8kHz telephony to 192kHz digital masters) and a range of channel 
representations (monaural, polyphonic, stereo, quadraphonic, 5.1, 
ambisonic, or up to 255 discrete channels).
</t>

<t>
lu_zero's avatar
lu_zero committed
71 72 73 74
Vorbis encoded audio is generally encapsulated within an Ogg format bitstream
<xref target="rfc3533"></xref>, which provides framing and synchronization.
For the purposes of RTP transport, this layer is unnecessary, and so raw Vorbis
packets are used in the payload.
lu_zero's avatar
lu_zero committed
75 76 77 78 79 80 81 82 83 84 85 86 87 88 89
</t>

<section anchor="Terminology" title="Terminology">

<t>
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 <xref target="rfc2119"></xref>.
</t>

</section>
</section>

<section anchor="Payload Format" title="Payload Format">

<t>
lu_zero's avatar
lu_zero committed
90 91 92 93 94 95
For RTP based transport of Vorbis encoded audio the standard RTP header is
followed by a 4 octets payload header, then the payload data. The payload
headers are used to associate the Vorbis data with its associated decoding
codebooks as well as indicating if the following packet contains fragmented
Vorbis data and/or the number of whole Vorbis data frames. The payload data
contains the raw Vorbis bitstream information. There are 3 types of Vorbis
lu_zero's avatar
lu_zero committed
96
payload data, an RTP packet MUST contain just one of them at a time.
lu_zero's avatar
lu_zero committed
97 98 99 100 101
</t>

<section anchor="RTP Header" title="RTP Header">

<t>
lu_zero's avatar
lu_zero committed
102 103 104
The format of the RTP header is specified in <xref target="rfc3550"></xref>
and shown in Figure <xref target="RTP Header Figure"/>.  This payload format
uses the fields of the header in a manner consistent with that specification.
lu_zero's avatar
lu_zero committed
105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126
</t>

<t>
<figure anchor="RTP Header Figure" title="RTP Header">
<artwork><![CDATA[
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |V=2|P|X|  CC   |M|     PT      |       sequence number         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           timestamp                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronization source (SSRC) identifier            |
   +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
   |            contributing source (CSRC) identifiers             |
   |                              ...                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>

<t>
lu_zero's avatar
lu_zero committed
127 128 129 130
The RTP header begins with an octet of fields (V, P, X, and CC) to support
specialized RTP uses (see <xref target="rfc3550"></xref> and 
<xref target="rfc3551"></xref> for details). For Vorbis RTP, the following
values are used.
lu_zero's avatar
lu_zero committed
131 132 133 134 135
</t>

<t>
Version (V): 2 bits</t>
<t>
lu_zero's avatar
lu_zero committed
136 137
This field identifies the version of RTP. The version used by this
specification is two (2).
lu_zero's avatar
lu_zero committed
138 139 140 141 142
</t>

<t>
Padding (P): 1 bit</t>
<t>
lu_zero's avatar
lu_zero committed
143 144
Padding MAY be used with this payload format according to section 5.1 of
<xref target="rfc3550"></xref>.
lu_zero's avatar
lu_zero committed
145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161
</t>

<t>
Extension (X): 1 bit</t>
<t>
The Extension bit is used in accordance with <xref target="rfc3550"></xref>.
</t>

<t>
CSRC count (CC): 4 bits</t>
<t>
The CSRC count is used in accordance with <xref target="rfc3550"></xref>.
</t>

<t>
Marker (M): 1 bit</t>
<t>
lu_zero's avatar
lu_zero committed
162 163
Set to zero.  Audio silence suppression not used.  This conforms to section 4.1
of <xref target="vorbis-spec-ref"></xref>.
lu_zero's avatar
lu_zero committed
164 165 166 167 168
</t>

<t>
Payload Type (PT): 7 bits</t>
<t>
lu_zero's avatar
lu_zero committed
169 170 171
An RTP profile for a class of applications is expected to assign a payload type
for this format, or a dynamically allocated payload type SHOULD be chosen which
designates the payload as Vorbis.
lu_zero's avatar
lu_zero committed
172 173 174 175 176
</t>

<t>
Sequence number: 16 bits</t>
<t>
lu_zero's avatar
lu_zero committed
177 178 179
The sequence number increments by one for each RTP data packet sent, and may be
used by the receiver to detect packet loss and to restore packet sequence. This
field is detailed further in <xref target="rfc3550"></xref>.
lu_zero's avatar
lu_zero committed
180 181 182 183 184
</t>

<t>
Timestamp: 32 bits</t>
<t>
lu_zero's avatar
lu_zero committed
185 186
A timestamp representing the sampling time of the first sample of the first
Vorbis packet in the RTP packet. The clock frequency MUST be set to the sample
lu_zero's avatar
lu_zero committed
187
rate of the encoded audio data and is conveyed out-of-band (e.g. as a SDP parameter).
lu_zero's avatar
lu_zero committed
188 189 190 191 192
</t>

<t>
SSRC/CSRC identifiers: </t>
<t>
lu_zero's avatar
lu_zero committed
193 194
These two fields, 32 bits each with one SSRC field and a maximum of 16 CSRC
fields, are as defined in <xref target="rfc3550">
lu_zero's avatar
lu_zero committed
195 196 197 198 199 200 201 202
</xref>.  
</t>

</section>

<section anchor="Payload Header" title="Payload Header">

<t>
lu_zero's avatar
lu_zero committed
203 204 205
The 4 octets following the RTP Header section are the Payload Header. This
header is split into a number of bitfields detailing the format of the
following payload data packets.
lu_zero's avatar
lu_zero committed
206 207 208 209 210 211 212 213 214 215 216 217 218 219 220
</t>

<figure anchor="Payload Header Figure" title="Payload Header">
<artwork><![CDATA[
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                     Ident                     | F |VDT|# pkts.|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>

<t>
Ident: 24 bits</t>
<t>
lu_zero's avatar
lu_zero committed
221 222
This 24 bit field is used to associate the Vorbis data to a decoding
Configuration. It is stored as network byte order integer.
lu_zero's avatar
lu_zero committed
223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240
</t>

<t>
Fragment type (F): 2 bits</t>
<t>
This field is set according to the following list
</t>
<vspace blankLines="1" />
<list style="empty">
<t>      0 = Not Fragmented</t>
<t>      1 = Start Fragment</t>
<t>      2 = Continuation Fragment</t>
<t>      3 = End Fragment</t>
</list>

<t>
Vorbis Data Type (VDT): 2 bits</t>
<t>
lu_zero's avatar
lu_zero committed
241
This field specifies the kind of Vorbis data stored in this RTP packet. There
lu_zero's avatar
lu_zero committed
242
are currently three different types of Vorbis payloads. Each packet MUST contain only a single type of Vorbis payload (e.g. you MUST not aggregate configuration and comment payload in the same packet)
lu_zero's avatar
lu_zero committed
243 244 245 246 247 248 249 250 251 252
</t>

<vspace blankLines="1" />
<list style="empty">
<t>      0 = Raw Vorbis payload</t>
<t>      1 = Vorbis Packed Configuration payload</t>
<t>      2 = Legacy Vorbis Comment payload</t>
<t>      3 = Reserved</t>
</list>

253
<t> The packets with a VDT of value 3 MUST be ignored </t>
lu_zero's avatar
lu_zero committed
254 255

<t>
lu_zero's avatar
lu_zero committed
256 257 258
The last 4 bits represent the number of complete packets in this payload. This
provides for a maximum number of 15 Vorbis packets in the payload. If the
packet contains fragmented data the number of packets MUST be set to 0.
lu_zero's avatar
lu_zero committed
259 260 261 262 263 264 265
</t>

</section>

<section anchor="Payload Data" title="Payload Data">

<t>
lu_zero's avatar
lu_zero committed
266 267 268 269 270 271
Raw Vorbis packets are currently unbounded in length, application profiles will
likely define a practical limit. Typical Vorbis packet sizes range from very
small (2-3 bytes) to quite large (8-12 kilobytes). The reference implementation
<xref target="libvorbis"></xref> typically produces packets less than ~800
bytes, except for the setup header packets which are ~4-12 kilobytes. Within an
RTP context, to avoid fragmentation, the Vorbis data packet size SHOULD be kept
lu_zero's avatar
lu_zero committed
272
sufficiently small so that after adding the RTP and payload headers, the
lu_zero's avatar
lu_zero committed
273
complete RTP packet is smaller than the path MTU.
lu_zero's avatar
lu_zero committed
274 275 276 277 278 279 280 281 282 283 284 285 286
</t>

<figure anchor="Payload Data Figure" title="Payload Data Header">
<artwork><![CDATA[
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            length             |       vorbis packet data     ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>

<t>
lu_zero's avatar
lu_zero committed
287 288
Each Vorbis payload packet starts with a two octet length header, which is used
to represent the size in bytes of the following data payload, followed by the
lu_zero's avatar
lu_zero committed
289
raw Vorbis data padded to the nearest byte boundary, as explained by the <xref target="vorbis-spec-ref">vorbis specification</xref>. The length value is stored
lu_zero's avatar
lu_zero committed
290
as network byte order integer.
lu_zero's avatar
lu_zero committed
291 292 293
</t>

<t>
lu_zero's avatar
lu_zero committed
294 295 296
For payloads which consist of multiple Vorbis packets the payload data consists
of the packet length followed by the packet data for each of the Vorbis packets
in the payload.
lu_zero's avatar
lu_zero committed
297 298 299
</t>

<t>
lu_zero's avatar
lu_zero committed
300 301
The Vorbis packet length header is the length of the Vorbis data block only and
does not count the length field.
lu_zero's avatar
lu_zero committed
302 303 304
</t>

<t>
lu_zero's avatar
lu_zero committed
305 306 307 308
The payload packing of the Vorbis data packets MUST follow the guidelines
set-out in <xref target="rfc3551"></xref> where the oldest packet occurs
immediately after the RTP packet header. Subsequent packets, if any, MUST
follow in temporal order.
lu_zero's avatar
lu_zero committed
309 310 311
</t>

<t>
lu_zero's avatar
lu_zero committed
312 313
Channel mapping of the audio is in accordance with the
<xref target="vorbis-spec-ref">Vorbis I Specification</xref>.
lu_zero's avatar
lu_zero committed
314 315 316 317 318 319 320 321 322 323 324 325 326 327
</t>

</section>

<section anchor="Example RTP Packet" title="Example RTP Packet">

<t>
Here is an example RTP packet containing two Vorbis packets.
</t>

<t>
RTP Packet Header:
</t>

lu_zero's avatar
lu_zero committed
328
<figure anchor="Example Raw Vorbis Packet" title="Example Raw Vorbis Packet">
lu_zero's avatar
lu_zero committed
329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344
<artwork><![CDATA[
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | 2 |0|0|  0    |0|      PT     |       sequence number         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               timestamp (in sample rate units)                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronisation source (SSRC) identifier            |
   +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
   |            contributing source (CSRC) identifiers             |
   |                              ...                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                     Ident                     | 0 | 0 | 2 pks |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
lu_zero's avatar
lu_zero committed
345
   |            length             |          vorbis data         ..
lu_zero's avatar
lu_zero committed
346 347 348 349 350
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                        vorbis data                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            length             |   next vorbis packet data    ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
lu_zero's avatar
lu_zero committed
351
   ..                        vorbis data                          ..
lu_zero's avatar
lu_zero committed
352
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
lu_zero's avatar
lu_zero committed
353 354
   ..               vorbis data                    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
lu_zero's avatar
lu_zero committed
355 356 357 358
]]></artwork>
</figure>

<t>
lu_zero's avatar
lu_zero committed
359 360 361 362 363
The payload data section of the RTP packet begins with the 24 bit Ident field
followed by the one octet bitfield header, which has the number of Vorbis
frames set to 2.  Each of the Vorbis data frames is prefixed by the two octets
length field. The Packet Type and Fragment Type are set to 0. The Configuration
that will be used to decode the packets is the one indexed by the ident value.
lu_zero's avatar
lu_zero committed
364 365 366 367 368 369 370 371 372 373 374 375
</t>

</section>
</section>



<section anchor="Configuration Headers" title="Configuration Headers">

<t>
Unlike other mainstream audio codecs Vorbis has no statically 
configured probability model. Instead, it packs all entropy decoding 
lu_zero's avatar
lu_zero committed
376 377 378
configuration, Vector Quantization and Huffman models into a data block
that must be transmitted to the decoder along with the compressed data.
A decoder also requires information detailing the number of audio 
lu_zero's avatar
lu_zero committed
379 380 381 382 383 384 385 386 387 388 389 390
channels, bitrates and similar information to configure itself for a 
particular compressed data stream. These two blocks of information are 
often referred to collectively as the "codebooks" for a Vorbis stream,
and are nominally included as special "header" packets at the start 
of the compressed data. In addition,
the <xref target="vorbis-spec-ref">Vorbis I specification</xref>
requires the presence of a comment header packet which gives simple
metadata about the stream, but this information is not required for 
decoding the frame sequence.
</t>

<t>
lu_zero's avatar
lu_zero committed
391 392
Thus these two codebook header packets must be received by the decoder before
any audio data can be interpreted. These requirements pose problems in RTP,
lu_zero's avatar
lu_zero committed
393 394 395 396 397 398 399 400
which is often used over unreliable transports.
</t>

<t>
Since this information must be transmitted reliably and, as the RTP 
stream may change certain configuration data mid-session, there are 
different methods for delivering this configuration data to a 
client, both in-band and out-of-band which is detailed below. SDP 
lu_zero's avatar
lu_zero committed
401 402 403
delivery is typically used to set up an initial state for the client 
application. The changes may be due to different codebooks as well as 
different bitrates of the stream.
lu_zero's avatar
lu_zero committed
404 405 406
</t>

<t>
lu_zero's avatar
lu_zero committed
407
The delivery vectors in use can be specified by an SDP attribute to indicate the
lu_zero's avatar
lu_zero committed
408 409 410 411 412 413
method and the optional URI where the Vorbis
<xref target="Packed Configuration">Packed Configuration</xref> Packets could
be fetched. Different delivery methods MAY be advertised for the same session.
The in-band Configuration delivery SHOULD be considered as baseline,
out-of-band delivery methods that don't use RTP will not be described in this
document. For non chained streams, the Configuration recommended delivery
lu_zero's avatar
lu_zero committed
414
method is inline the <xref target="Packed Configuration">Packed Configuration</xref> in the SDP as explained in the <xref target="Mapping Media Type Parameters into SDP"> IANA considerations</xref>.
lu_zero's avatar
lu_zero committed
415 416 417
</t>

<t>
lu_zero's avatar
lu_zero committed
418 419 420 421 422 423
The 24 bit Ident field is used to map which Configuration will be used to
decode a packet. When the Ident field changes, it indicates that a change in
the stream has taken place. The client application MUST have in advance the
correct configuration and if the client detects a change in the Ident value and
does not have this information it MUST NOT decode the raw Vorbis data
associated until it fetches the correct Configuration.
lu_zero's avatar
lu_zero committed
424 425 426 427 428
</t>

<section anchor="In-band Header Transmission" title="In-band Header Transmission">

<t>
lu_zero's avatar
lu_zero committed
429 430 431 432
The <xref target="Packed Configuration">Packed Configuration</xref> Payload is
sent in-band with the packet type bits set to match the Vorbis Data Type.
Clients MUST be capable of dealing with fragmentation and periodic
re-transmission of the configuration headers.
lu_zero's avatar
lu_zero committed
433 434 435 436 437
</t>

<section anchor="Packed Configuration" title="Packed Configuration">

<t>
lu_zero's avatar
lu_zero committed
438 439 440
A Vorbis Packed Configuration is indicated with the Vorbis Data Type field set
to 1. Of the three headers, defined in the
<xref target="vorbis-spec-ref">Vorbis I specification</xref>, the
441 442
identification and the setup MUST be packed together 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 byte stores the number of following packets minus one, the next bytes represent the size of the packets, every byte set to 0xff means that the next byte has to be add to the current sum in order to have the complete size; the headers immediately follows the list of sizes. The headers are packed in the same order they are present in ogg: identification, comment, setup.
lu_zero's avatar
lu_zero committed
443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461
</t>

<figure anchor="Packed Configuration Figure" title="Packed Configuration Figure">
<artwork><![CDATA[
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |V=2|P|X|  CC   |M|     PT      |             xxxx              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                             xxxxx                             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronization source (SSRC) identifier            |
   +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
   |            contributing source (CSRC) identifiers             |
   |                              ...                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                      Ident                    | 0 | 1 |      1|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
462 463 464
   |           length              | n. of headers |    length1    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    length2    |                  Identification              ..
lu_zero's avatar
lu_zero committed
465 466 467 468 469 470 471
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                        Identification                       ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                        Identification                       ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                        Identification                       ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
472 473 474 475 476 477 478 479 480
   ..               Identification                 |    Comment   ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                            Comment                          ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                            Comment                          ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                            Comment                          ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..           Comment            |             Setup            ..
lu_zero's avatar
lu_zero committed
481 482 483
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                            Setup                            ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
484
   ..                            Setup                            ..
lu_zero's avatar
lu_zero committed
485 486 487 488
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>

lu_zero's avatar
lu_zero committed
489 490 491
<t>The Ident field is set with the value that will be used by the Raw Payload
Packets to address this Configuration. The Fragment type is set to 0 since the
packet bears the full Packed configuration, the number of packet is set to 1.</t>
lu_zero's avatar
lu_zero committed
492 493 494 495 496 497
</section>
</section>

<section anchor="Out of Band Transmission" title="Out of Band Transmission">

<t>
lu_zero's avatar
lu_zero committed
498 499 500 501
This section, as stated above, does not cover all the possible out-of-band
delivery methods since they rely on different protocols and are linked to
specific applications. The following packet definition SHOULD be used in
out-of-band delivery and MUST be used when Configuration is inlined in the SDP.
lu_zero's avatar
lu_zero committed
502 503 504 505 506
</t>

<section anchor="Packed Headers" title="Packed Headers"> 

<t>
lu_zero's avatar
lu_zero committed
507 508 509 510
As mentioned above the RECOMMENDED delivery vector for Vorbis configuration
data is via a retrieval method that can be performed using a reliable transport
protocol. As the RTP headers are not required for this method of delivery the
structure of the configuration data is slightly different. The packed header
lu_zero's avatar
lu_zero committed
511 512 513
starts with a 32 bit (network ordered) count field which details the number of
packed headers that are contained in the bundle. Next is the Packed header
payload for each chained Vorbis stream.
lu_zero's avatar
lu_zero committed
514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530
</t>

<figure anchor="Packed Headers Overview Figure" title="Packed Headers Overview">
<artwork><![CDATA[
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                     Number of packed headers                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                          Packed header                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                          Packed header                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>

<t>
lu_zero's avatar
lu_zero committed
531 532
Since the Configuration Ident and the Identification Header are fixed length
there is only a 2 byte length tag to define the length of the packed headers.
lu_zero's avatar
lu_zero committed
533 534 535 536 537 538 539
</t>

<figure anchor="Packed Headers Detail Figure" title="Packed Headers Detail">
<artwork><![CDATA[
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
540 541 542
   |                   Ident                       |    length1    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      0xff     |    length2    |    Identification Header     ..
lu_zero's avatar
lu_zero committed
543
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
544
   .................................................................
lu_zero's avatar
lu_zero committed
545 546 547
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                    Identification Header                     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
548 549 550 551 552 553
   |                     Configuration Header                     ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   .................................................................
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                    Configuration Header                      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
lu_zero's avatar
lu_zero committed
554 555 556 557 558 559 560
   |                          Setup Header                        ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                         Setup Header                         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
<t>
lu_zero's avatar
lu_zero committed
561
The key difference between the in-band format and this one, is there is no need
562
for the payload header octet. In this figure the comment has a size bigger than 255 bytes.
lu_zero's avatar
lu_zero committed
563 564 565 566 567 568 569 570
</t>
</section>

</section>

<section anchor="Loss of Configuration Headers" title="Loss of Configuration Headers"> 

<t>
lu_zero's avatar
lu_zero committed
571 572 573
Unlike the loss of raw Vorbis payload data, loss of a configuration header can
lead to a situation where it will not be possible to successfully decode the
stream.
lu_zero's avatar
lu_zero committed
574 575 576
</t>

<t>
lu_zero's avatar
lu_zero committed
577
Loss of Configuration Packet results in the halting of stream decoding.
lu_zero's avatar
lu_zero committed
578 579 580 581 582 583 584 585 586
</t>

</section>

</section>

<section anchor="Comment Headers" title="Comment Headers">

<t>
lu_zero's avatar
lu_zero committed
587 588 589 590 591
With the Vorbis Data Type flag set to 2, this indicates that the packet contain
the comment metadata, such as artist name, track title and so on. These
metadata messages are not intended to be fully descriptive but to offer basic
track/song information. Clients MAY ignore it completely. The details on the
format of the comments can be found in the <xref target="vorbis-spec-ref">Vorbis documentation</xref>.
lu_zero's avatar
lu_zero committed
592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618
</t>
<figure anchor="Comment Packet Figure" title="Comment Packet">
<artwork><![CDATA[
    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |V=2|P|X|  CC   |M|     PT      |             xxxx              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                             xxxxx                             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronization source (SSRC) identifier            |
   +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
   |            contributing source (CSRC) identifiers             |
   |                              ...                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                      Ident                    | 0 | 2 |      1|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            length             |            Comment           ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                           Comment                           ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                           Comment                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>

lu_zero's avatar
lu_zero committed
619 620 621
<t>
The 2 bytes length field is necessary since this packet could be fragmented.
</t>
lu_zero's avatar
lu_zero committed
622 623 624 625 626

</section>
<section anchor="Frame Packetization" title="Frame Packetization">

<t>
lu_zero's avatar
lu_zero committed
627 628 629
Each RTP packet contains either one Vorbis packet fragment, or an integer
number of complete Vorbis packets (up to a maximum of 15 packets, since the
number of packets is defined by a 4 bit value).
lu_zero's avatar
lu_zero committed
630 631 632
</t>

<t>
lu_zero's avatar
lu_zero committed
633 634 635
Any Vorbis data packet that is less than path MTU SHOULD be bundled in the RTP
packet with as many Vorbis packets as will fit, up to a maximum of 15, except
when such bundling would exceed an application's desired transmission latency.
lu_zero's avatar
lu_zero committed
636
Path MTU is detailed in <xref target="rfc1191"></xref> and <xref target="rfc1981"></xref>.
lu_zero's avatar
lu_zero committed
637 638 639
</t>

<t>
lu_zero's avatar
lu_zero committed
640 641 642 643 644 645 646 647
A fragmented packet has a zero in the last four bits of the payload header.
The first fragment will set the Fragment type to 1. Each fragment after the
first will set the Fragment type to 2 in the payload header.  The RTP packet
containing the last fragment of the Vorbis packet will have the Fragment type
set to 3.  To maintain the correct sequence for fragmented packet reception
the timestamp field of fragmented packets MUST be the same as the first packet
sent, with the sequence number incremented as normal for the subsequent RTP
packets. The length field shows the fragment length.
lu_zero's avatar
lu_zero committed
648 649 650 651 652
</t>

<section anchor="Example Fragmented Vorbis Packet" title="Example Fragmented Vorbis Packet">

<t>
lu_zero's avatar
lu_zero committed
653 654 655
Here is an example fragmented Vorbis packet split over three RTP packets.
Each packet contains the standard RTP headers as well as the 4 octets Vorbis
headers.
lu_zero's avatar
lu_zero committed
656 657 658 659 660 661 662 663 664 665 666
</t>

<figure anchor="Example Fragmented Packet (Packet 1)" title="Example Fragmented Packet (Packet 1)">
<artwork><![CDATA[
   Packet 1:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |V=2|P|X|  CC   |M|     PT      |           1000                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
lu_zero's avatar
lu_zero committed
667
   |                            12345                              |
lu_zero's avatar
lu_zero committed
668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronization source (SSRC) identifier            |
   +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
   |            contributing source (CSRC) identifiers             |
   |                              ...                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                       Ident                   | 1 | 0 |      0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             length            |            vorbis data       ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                        vorbis data                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>

<t>
lu_zero's avatar
lu_zero committed
685
In this packet the initial sequence number is 1000 and the timestamp is 12345.  The Fragment type is set to 1, the number of packets field is set to 0, and as
lu_zero's avatar
lu_zero committed
686
the payload is raw Vorbis data the VDT field is set to 0.
lu_zero's avatar
lu_zero committed
687 688 689 690 691 692 693 694 695 696 697
</t>

<figure anchor="Example Fragmented Packet (Packet 2)" title="Example Fragmented Packet (Packet 2)">
<artwork><![CDATA[
   Packet 2:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |V=2|P|X|  CC   |M|     PT      |           1001                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
lu_zero's avatar
lu_zero committed
698
   |                             12345                             |
lu_zero's avatar
lu_zero committed
699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronization source (SSRC) identifier            |
   +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
   |            contributing source (CSRC) identifiers             |
   |                              ...                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                       Ident                   | 2 | 0 |      0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             length            |          vorbis data         ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                        vorbis data                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>

<t>
lu_zero's avatar
lu_zero committed
716 717 718 719 720
The Fragment type field is set to 2 and the number of packets field is set to 0.
For large Vorbis fragments there can be several of these type of payload 
packets. The maximum packet size SHOULD be no greater than the path MTU,
including all RTP and payload headers. The sequence number has been incremented
by one but the timestamp field remains the same as the initial packet.
lu_zero's avatar
lu_zero committed
721 722 723 724 725 726 727 728 729 730 731
</t>

<figure anchor="Example Fragmented Packet (Packet 3)" title="Example Fragmented Packet (Packet 3)">
<artwork><![CDATA[
   Packet 3:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |V=2|P|X|  CC   |M|     PT      |           1002                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
lu_zero's avatar
lu_zero committed
732
   |                             12345                             |
lu_zero's avatar
lu_zero committed
733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronization source (SSRC) identifier            |
   +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
   |            contributing source (CSRC) identifiers             |
   |                              ...                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                      Ident                    | 3 | 0 |      0|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             length            |          vorbis data         ..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ..                        vorbis data                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>

<t>
lu_zero's avatar
lu_zero committed
750 751 752 753
This is the last Vorbis fragment packet.  The Fragment type is set to 3 and the
packet count remains set to 0. As in the previous packets the timestamp remains
set to the first packet in the sequence and the sequence number has been
incremented.
lu_zero's avatar
lu_zero committed
754 755 756 757 758 759
</t>
</section>

<section anchor="Packet Loss" title="Packet Loss">

<t>
lu_zero's avatar
lu_zero committed
760 761 762 763 764 765 766 767 768 769
As there is no error correction within the Vorbis stream, packet loss will
result in a loss of signal. Packet loss is more of an issue for fragmented
Vorbis packets as the client will have to cope with the handling of the
Fragment Type. In case of loss of fragments the client MUST discard all the
remaining fragments and decode the incomplete packet. If we use the fragmented
Vorbis packet example above and the first packet is lost the client MUST detect
that the next packet has the packet count field set to 0 and the Fragment type
2 and MUST drop it. The next packet, which is the final fragmented packet, MUST
be dropped in the same manner. If the missing packet is the last, the received
two fragments will be kept and the incomplete vorbis packet decoded.
lu_zero's avatar
lu_zero committed
770 771 772
</t>

<t>
lu_zero's avatar
lu_zero committed
773 774
Loss of any of the Configuration fragment will result in the loss of the full
Configuration packet with the result detailed in the <xref target="Loss of Configuration Headers">Loss of Configuration Headers</xref> section.
lu_zero's avatar
lu_zero committed
775 776 777 778 779 780 781
</t>

</section>
</section>
<section anchor="IANA Considerations" title="IANA Considerations"> 

<vspace blankLines="1" />
lu_zero's avatar
lu_zero committed
782
<list style="hanging">
lu_zero's avatar
lu_zero committed
783
<t hangText="Type name:"> audio </t>
lu_zero's avatar
lu_zero committed
784 785
<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
786
<t hangText="Subtype name:"> vorbis </t>
lu_zero's avatar
lu_zero committed
787 788
<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
789
<t hangText="Required parameters:">
lu_zero's avatar
lu_zero committed
790 791 792

<vspace blankLines="1" />

793
<list style="hanging">
lu_zero's avatar
lu_zero committed
794
<t hangText="rate:"> indicates the RTP timestamp clock rate as described in <xref target="rfc3551">RTP Profile for Audio and Video Conferences with Minimal Control.</xref>
795 796 797
</t>
<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
798
<t hangText="channels:"> indicates the number of audio channels as described in <xref target="rfc3551">RTP Profile for Audio and Video Conferences with Minimal Control.</xref>
799 800 801 802
</t>

<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
803
<t hangText="delivery-method:"> indicates the delivery methods in use, the possible values are: inline, in_band, out_band, MAY be included multiple times
lu_zero's avatar
lu_zero committed
804 805 806 807
</t>

<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
808
<t hangText="configuration:"> the <xref target="rfc3548">base64</xref> representation of the <xref target="Packed Headers">Packed Headers</xref>. It MUST follow the associated delivery-method parameter ("inline").
lu_zero's avatar
lu_zero committed
809 810 811 812 813 814
</t>
</list>
</t>

<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
815
<t hangText="Optional parameters:">
lu_zero's avatar
lu_zero committed
816 817 818 819

<vspace blankLines="1" />

<list style="hanging">
lu_zero's avatar
lu_zero committed
820 821 822 823 824 825 826 827
<t hangText="configuration-uri:"> the URI of the configuration headers in case
of out of band transmission. In the form of "protocol://path/to/resource/".
Depending on the specific method, a single configuration packet could be
retrived by its number, or multiple packets could be aggregated in a single
stream. Such aggregates MAY be compressed using either
<xref target="BZ2">bzip2</xref> or <xref target="rfc1952">gzip</xref>.
A <xref target="FIPS180">sha1</xref> checksum MAY be provided for aggregates.
In this latter case the URI will end with the aggregate name, followed by its
lu_zero's avatar
lu_zero committed
828 829
compressed extension if applies, a "!" and the <xref target="rfc3548">base64</xref> representation of the sha1hash of the above mentioned compressed aggregated
as in: "protocol://path/to/resource/aggregated.bz2!sha1hash".
lu_zero's avatar
lu_zero committed
830 831 832
The trailing '/' discriminates which of two methods are in use.
It MUST follow the associated delivery method parameter (either "in_band" or "out_band").
</t>
lu_zero's avatar
lu_zero committed
833 834 835 836 837 838 839 840 841 842 843 844
</list>
</t>

<vspace blankLines="1" />

<t hangText="Encoding considerations:">
<vspace blankLines="1" />
This media type is framed and contains binary data.
</t>

<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
845
<t hangText="Security considerations:">
lu_zero's avatar
lu_zero committed
846
<vspace blankLines="1" />
lu_zero's avatar
lu_zero committed
847
See Section 10 of RFC XXXX.</t>
lu_zero's avatar
lu_zero committed
848 849 850 851 852 853 854 855 856 857

<vspace blankLines="1" />
<t hangText="Interoperability considerations:">
<vspace blankLines="1" />
None</t>

<vspace blankLines="1" />
<t hangText="Published specification:">

<vspace blankLines="1" />
lu_zero's avatar
lu_zero committed
858
RFC XXXX [RFC Editor: please replace by the RFC number of  this memo, when published]
lu_zero's avatar
lu_zero committed
859
<vspace blankLines="1" />
lu_zero's avatar
lu_zero committed
860
Ogg Vorbis I specification:  Codec setup and packet decode. Available from the Xiph website, http://www.xiph.org
lu_zero's avatar
lu_zero committed
861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880
</t>

<vspace blankLines="1" />

<t hangText="Applications which use this media type:">
<vspace blankLines="1"/>
Audio streaming and conferencing tools </t>

<vspace blankLines="1" />

<t hangText="Additional information:">
<vspace blankLines="1" />
None </t>

<vspace blankLines="1" />

<t hangText="Person &amp; email address to contact for further information:">

<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
881 882
Luca Barbato: &lt;lu_zero@gentoo.org&gt;<br/>
IETF Audio/Video Transport Working Group
lu_zero's avatar
lu_zero committed
883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904

</t>

<vspace blankLines="1" />

<t hangText="Intended usage:">
<vspace blankLines="1" />
COMMON</t>

<vspace blankLines="1" />

<t hangText="Restriction on usage:">
<vspace blankLines="1" />
This media type depends on RTP framing, and hence is only defined for transfer via <xref target="rfc3550">RTP</xref></t>

<vspace blankLines="1" />

<t hangText="Author:">
<vspace blankLines="1"/>Luca Barbato</t>

<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
905 906
<t hangText="Change controller:">
<vspace blankLines="1"/>IETF AVT Working Group delegated from the IESG</t>
lu_zero's avatar
lu_zero committed
907 908 909

<vspace blankLines="1" />
</list>
lu_zero's avatar
lu_zero committed
910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927

<section anchor="Packed Headers IANA Considerations" title="Packed Headers IANA Considerations"> 

<t>
The following IANA considerations MUST only be applied to the packed headers.
</t>

<vspace blankLines="1" />

<list style="hanging">
<t hangText="Type name:"> audio </t>

<vspace blankLines="1" />

<t hangText="Subtype name:"> vorbis-config </t>

<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
928
<t hangText="Required parameters:">
lu_zero's avatar
lu_zero committed
929 930 931 932 933 934
<vspace blankLines="1" />
None
</t>

<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
935
<t hangText="Optional parameters:">
lu_zero's avatar
lu_zero committed
936 937 938 939 940 941 942 943 944 945 946 947 948
<vspace blankLines="1" />
None
</t>

<vspace blankLines="1" />

<t hangText="Encoding considerations:">
<vspace blankLines="1" />
This media type contains binary data.
</t>

<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
949
<t hangText="Security considerations:">
lu_zero's avatar
lu_zero committed
950
<vspace blankLines="1" />
lu_zero's avatar
lu_zero committed
951
See Section 10 of RFC XXXX.
lu_zero's avatar
lu_zero committed
952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019
</t>

<vspace blankLines="1" />

<t hangText="Interoperability considerations:">
<vspace blankLines="1" />
None
</t>

<vspace blankLines="1" />

<t hangText="Published specification:">
<vspace blankLines="1" />
RFC XXXX [RFC Editor: please replace by the RFC number of  this memo,
       when published]
</t>

<vspace blankLines="1" />

<t hangText="Applications which use this media type:">
<vspace blankLines="1" />
Vorbis encoded audio, configuration data.
</t>

<vspace blankLines="1" />

<t hangText="Additional information:"> 
<vspace blankLines="1" />
None
</t>

<vspace blankLines="1" />

<t hangText="Person &amp; email address to contact for further information:">
<vspace blankLines="1" />
Luca Barbato: &lt;lu_zero@gentoo.org&gt;
<vspace blankLines="0" />
IETF Audio/Video Transport Working Group
</t>

<vspace blankLines="1" />

<t hangText="Intended usage:">
COMMON
</t>

<vspace blankLines="1" />

<t hangText="Restriction on usage:">
<vspace blankLines="1" />
This media type doesn't depend on the transport.
</t>

<vspace blankLines="1" />

<t hangText="Author:">
<vspace blankLines="1" />
Luca Barbato</t>

<vspace blankLines="1" />

<t hangText="Change controller:">
<vspace blankLines="1" />
IETF AVT Working Group delegated from the IESG</t>
</list>

</section>

lu_zero's avatar
lu_zero committed
1020 1021 1022 1023 1024 1025
</section>

<section anchor="SDP related considerations" title="SDP related considerations">
<t>
The following paragraphs defines the mapping of the parameters described in the IANA considerations section and their usage in the <xref target="rfc3264">Offer/Answer Model</xref>.
</t>
lu_zero's avatar
lu_zero committed
1026

lu_zero's avatar
lu_zero committed
1027
<section anchor="Mapping Media Type Parameters into SDP" title="Mapping MIME Parameters into SDP"> 
lu_zero's avatar
lu_zero committed
1028 1029

<t>
lu_zero's avatar
lu_zero committed
1030 1031 1032 1033
The information carried in the Media Type media type specification has a
specific mapping to fields in the <xref target="rfc4566">Session Description
Protocol (SDP)</xref>, which is commonly used to describe RTP sessions.
When SDP is used to specify sessions the mapping are as follows:
lu_zero's avatar
lu_zero committed
1034 1035 1036 1037 1038
</t>

<vspace blankLines="1" />
<list style="symbols">

lu_zero's avatar
lu_zero committed
1039
<t>The type name ("audio") goes in SDP "m=" as the media name.</t>
lu_zero's avatar
lu_zero committed
1040 1041
<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
1042
<t>The subtype name ("vorbis") goes in SDP "a=rtpmap" as the encoding name.</t>
lu_zero's avatar
lu_zero committed
1043 1044 1045 1046 1047 1048 1049 1050
<vspace blankLines="1" />

<t>The parameter "rate" also goes in "a=rtpmap" as clock rate.</t>
<vspace blankLines="1" />

<t>The parameter "channels" also goes in "a=rtpmap" as channel count.</t>
<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
1051
<t>The mandated parameters "delivery-method" and "configuration" MUST be
lu_zero's avatar
lu_zero committed
1052
included in the SDP "a=fmtp" attribute.</t>
lu_zero's avatar
lu_zero committed
1053 1054
<vspace blankLines="1" />

lu_zero's avatar
lu_zero committed
1055
<t>The optional parameter "configuration-uri", when present,  MUST be included
lu_zero's avatar
lu_zero committed
1056
in the SDP "a=fmtp" attribute and MUST follow the delivery-method that applies.</t>
lu_zero's avatar
lu_zero committed
1057 1058 1059 1060

</list>

<t>
lu_zero's avatar
lu_zero committed
1061 1062 1063
If the stream comprises chained Vorbis files and all of them are known in
advance, the Configuration Packet for each file SHOULD be passed to the client
using the configuration attribute.
lu_zero's avatar
lu_zero committed
1064 1065 1066
</t>

<t>
lu_zero's avatar
lu_zero committed
1067 1068 1069
The URI specified in the configuration-uri attribute MUST point to a location
where all of the Configuration Packets needed for the life of the session
reside.
lu_zero's avatar
lu_zero committed
1070 1071 1072
</t>

<t>
lu_zero's avatar
lu_zero committed
1073
The port value is specified by the server application bound to the address
lu_zero's avatar
lu_zero committed
1074
specified in the c= line. The bitrate value and channels specified in the
lu_zero's avatar
lu_zero committed
1075 1076
rtpmap attribute MUST match the Vorbis sample rate value.  An example is found
below.
lu_zero's avatar
lu_zero committed
1077 1078 1079
</t>

<section anchor="SDP Example" title="SDP Example">
lu_zero's avatar
lu_zero committed
1080 1081 1082 1083
<t>The following example shows a basic SDP single stream. The first
configuration packet is inlined in the sdp, other configurations could be
fetched at any time from the first provided uri using or all the known
configuration could be downloaded using the second uri. The inline
lu_zero's avatar
lu_zero committed
1084
<xref target="rfc3548">base64</xref> configuration string is omitted because of
lu_zero's avatar
lu_zero committed
1085
the length.</t>
lu_zero's avatar
lu_zero committed
1086 1087

<list style="empty">
lu_zero's avatar
lu_zero committed
1088
<t>c=IN IP4 192.0.2.1</t>
lu_zero's avatar
lu_zero committed
1089 1090
<t>m=audio  RTP/AVP 98</t>
<t>a=rtpmap:98 vorbis/44100/2</t>
lu_zero's avatar
lu_zero committed
1091
<t>a=fmtp:98 delivery-method=in_band; configuration=base64string; delivery-method=out_band; configuration-uri=rtsp://path/to/the/resource; delivery-method=out_band; configuration-uri=http://another/path/to/resource/aggregate.bz2!8b6237eb5154a0ea12811a94e8e2697b3312bc6c;</t>
lu_zero's avatar
lu_zero committed
1092 1093 1094 1095 1096
</list>
</section>


<t>
lu_zero's avatar
lu_zero committed
1097 1098 1099 1100 1101 1102 1103
Note that the payload format (encoding) names are commonly shown in upper case.
MIME subtypes are commonly shown in lower case. These names are
case-insensitive in both places.  Similarly, parameter names are
case-insensitive both in MIME types and in the default mapping to the SDP
a=fmtp attribute. The exception regarding case sensitivity is the
configuration-uri URI which MUST be regarded as being case sensitive. The
a=fmtp line is a single line even if it is presented broken because of clarity.
lu_zero's avatar
lu_zero committed
1104 1105 1106 1107 1108 1109 1110
</t>

</section>

<section anchor="Usage with the SDP Offer/Answer Mode" title="Usage with the SDP Offer/Answer Model">

<t>
lu_zero's avatar
lu_zero committed
1111 1112 1113 1114 1115 1116
The only paramenter negotiable is the delivery method. All the others are
declarative: the offer, as described in <xref target="rfc3264">An Offer/Answer
Model Session Description Protocol</xref>, may contain a large number of
delivery methods per single fmtp attribute, the answerer MUST remove every
delivery-method and configuration-uri not supported. All the parameters MUST
not be altered on answer otherwise.
lu_zero's avatar
lu_zero committed
1117 1118 1119 1120 1121 1122 1123 1124 1125
</t>

</section>

</section>

<section anchor="Congestion Control" title="Congestion Control"> 

<t>
lu_zero's avatar
lu_zero committed
1126 1127 1128 1129 1130
Vorbis clients SHOULD send regular receiver reports detailing congestion. A
mechanism for dynamically downgrading the stream, known as bitrate peeling,
will allow for a graceful backing off of the stream bitrate. This feature is
not available at present so an alternative would be to redirect the client to
a lower bitrate stream if one is available.
lu_zero's avatar
lu_zero committed
1131 1132 1133 1134 1135 1136 1137
</t>

</section> 

<section anchor="Examples" title="Examples">

<t>
lu_zero's avatar
lu_zero committed
1138 1139 1140
The following examples are common usage patterns that MAY be applied in such
situations, the main scope of this section is to explain better usage of the
transmission vectors.
lu_zero's avatar
lu_zero committed
1141 1142 1143 1144
</t>

<section anchor="Stream Radio" title="Stream Radio">

lu_zero's avatar
lu_zero committed
1145 1146 1147 1148
<t>This is one of the most common situation: one single server streaming
content in multicast, the clients may start a session at random time. The
content itself could be a mix of live stream, as the wj's voice, and stored
streams as the music she plays.</t>
lu_zero's avatar
lu_zero committed
1149

lu_zero's avatar
lu_zero committed
1150 1151 1152
<t>In this situation we don't know in advance how many codebooks we will use.
The clients can join anytime and users expect to start listening to the content
in a short time.</t>
lu_zero's avatar
lu_zero committed
1153

lu_zero's avatar
lu_zero committed
1154 1155 1156
<t>On join the client will receive the current Configuration necessary to
decode the current stream inlined in the SDP so that the decoding will start
immediately after.</t>
lu_zero's avatar
lu_zero committed
1157

lu_zero's avatar
lu_zero committed
1158 1159 1160 1161
<t>When the streamed content changes the new Configuration is sent in-band
before the actual stream, and the Configuration that has to be sent inline in
the SDP updated. Since the in-band method is unreliable, an out of band
fallback is provided.</t>
lu_zero's avatar
lu_zero committed
1162

lu_zero's avatar
lu_zero committed
1163
<t>The client could choose to fetch the Configuration from the alternate source
lu_zero's avatar
lu_zero committed
1164
as soon as it discovers a Configuration packet got lost in-band or use
lu_zero's avatar
lu_zero committed
1165 1166
<xref target="RFC3611">selective retransmission</xref>, if the server supports
the feature.</t>
lu_zero's avatar
lu_zero committed
1167

lu_zero's avatar
lu_zero committed
1168 1169 1170
<t>A serverside optimization would be to keep an hash list of the
Configurations per session to avoid packing all of them and send the same
Configuration with different Ident tags</t>
lu_zero's avatar
lu_zero committed
1171

lu_zero's avatar
lu_zero committed
1172 1173
<t>A clientside optimization would be to keep a tag list of the Configurations
per session and don't process configuration packets already known.</t>
lu_zero's avatar
lu_zero committed
1174 1175 1176 1177 1178 1179

</section>
</section>

<section anchor="Security Considerations" title="Security Considerations"> 
<t>
lu_zero's avatar
lu_zero committed
1180 1181 1182 1183 1184
RTP packets using this payload format are subject to the security
considerations discussed in the RTP specification 
<xref target="rfc3550"></xref>.  This implies that the confidentiality of the
media stream is achieved by using encryption. Because the data compression used
with this payload format is applied end-to-end, encryption may be performed on
lu_zero's avatar
lu_zero committed
1185 1186 1187 1188
the compressed data. Additional care MAY be needed for delivery methods that
point to external resources, using secure protocols to fetch the configuration
payloads. Where the size of a data block is set, care MUST be taken to prevent
buffer overflows in the client applications.
lu_zero's avatar
lu_zero committed
1189 1190 1191 1192 1193 1194 1195
</t>

</section> 

<section anchor="Acknowledgments" title="Acknowledgments"> 

<t>
lu_zero's avatar
lu_zero committed
1196 1197 1198
This document is a continuation of draft-moffitt-vorbis-rtp-00.txt and
draft-kerr-avt-vorbis-rtp-04.txt.  The MIME type section is a continuation of
draft-short-avt-rtp-vorbis-mime-00.txt.
lu_zero's avatar
lu_zero committed
1199 1200 1201
</t>

<t>
lu_zero's avatar
lu_zero committed
1202 1203 1204 1205 1206 1207 1208
Thanks to the AVT, Ogg Vorbis Communities / Xiph.org 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,
Magnus Westerlund, David Barrett, Silvia Pfeiffer, Stefan Ehmann, Alessandro
Salvatori. Politecnico di Torino (LS)³/IMG Group in particular Federico
Ridolfo, Francesco Varano, Giampaolo Mancini, Juan Carlos De Martin.
lu_zero's avatar
lu_zero committed
1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246
</t>

</section> 

</middle>

<back>

<references title="Normative References">

<reference anchor="rfc2119">
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels </title>
<author initials="S." surname="Bradner" fullname="Scott Bradner"></author>
</front>
<seriesInfo name="RFC" value="2119" />
</reference>   

<reference anchor="rfc3550">
<front>
<title>RTP: A Transport Protocol for real-time applications</title>
<author initials="H." surname="Schulzrinne" fullname=""></author>
<author initials="S." surname="Casner" fullname=""></author>
<author initials="R." surname="Frederick" fullname=""></author>
<author initials="V." surname="Jacobson" fullname=""></author>
</front>
<seriesInfo name="RFC" value="3550" />
</reference> 

<reference anchor="rfc3551">
<front>
<title>RTP Profile for Audio and Video Conferences with Minimal Control.</title>
<author initials="H." surname="Schulzrinne" fullname=""></author>
<author initials="S." surname="Casner" fullname=""></author>
</front>
<date month="July" year="2003" />
<seriesInfo name="RFC" value="3551" />
</reference> 
lu_zero's avatar
lu_zero committed
1247 1248 1249

<reference anchor='rfc4566'>

lu_zero's avatar
lu_zero committed
1250 1251
<front>
<title>SDP: Session Description Protocol</title>
lu_zero's avatar
lu_zero committed
1252 1253 1254 1255 1256 1257 1258
<author initials='M.' surname='Handley' fullname='M. Handley'>
<organization /></author>
<author initials='V.' surname='Jacobson' fullname='V. Jacobson'>
<organization /></author>
<author initials='C.' surname='Perkins' fullname='C. Perkins'>
<organization /></author>
<date year='2006' month='July' />
lu_zero's avatar
lu_zero committed
1259 1260
</front>

lu_zero's avatar
lu_zero committed
1261 1262 1263 1264 1265 1266
<seriesInfo name='RFC' value='4566' />
<format type='TXT' octets='108820' target='ftp://ftp.isi.edu/in-notes/rfc4566.txt' />
</reference>

<reference anchor='rfc1191'>

lu_zero's avatar
lu_zero committed
1267
<front>
lu_zero's avatar
lu_zero committed
1268 1269 1270 1271 1272 1273 1274 1275 1276 1277
<title>Path MTU discovery</title>
<author initials='J.' surname='Mogul' fullname='Jeffrey Mogul'>
<organization>Digital Equipment Corporation (DEC) , Western Research Laboratory</organization>
<address>
<email>mogul@decwrl.dec.com</email></address></author>
<author initials='S.' surname='Deering' fullname='Steve Deering'>
<organization>Xerox Palo Alto Research Center</organization>
<address>
<email>deering@xerox.com</email></address></author>
<date year='1990' day='1' month='November' />
lu_zero's avatar
lu_zero committed
1278
</front>
lu_zero's avatar
lu_zero committed
1279 1280 1281 1282

<seriesInfo name='RFC' value='1191' />
<format type='TXT' octets='47936' target='ftp://ftp.isi.edu/in-notes/rfc1191.txt' />
</reference>
lu_zero's avatar
lu_zero committed
1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316

<reference anchor="rfc1981">
<front>
<title>Path MTU Discovery for IP version 6</title>
<author initials="J." surname="McCann et al." fullname="J. McCann et al."></author>
</front>
<seriesInfo name="RFC" value="1981" />
</reference>   

<reference anchor="rfc3264">
<front>
<title>An Offer/Answer Model with Session Description Protocol (SDP)</title>
<author initials="J." surname="Rosenberg" fullname="Jonathan Rosenberg"></author>
<author initials="H." surname="Schulzrinne" fullname="Henning Schulzrinne"></author>
</front>
<seriesInfo name="RFC" value="3264" />
</reference>   

<reference anchor="rfc3548">
<front>
<title>The Base16, Base32, and Base64 Data Encodings</title>
<author initials="S." surname="Josefsson" fullname="Simon Josefsson"></author>
</front>
<seriesInfo name="RFC" value="3548" />
</reference>
<reference anchor="FIPS180">
<front>
<title>Secure Hash Standard</title>
<author>
<organization>National Institute of Standards and Technology</organization>
</author>
<date month="May" year="1993"/>
</front>
</reference>
lu_zero's avatar
lu_zero committed
1317
</references>
lu_zero's avatar
lu_zero committed
1318

lu_zero's avatar
lu_zero committed
1319 1320 1321
<references title="Informative References">

<reference anchor="rfc3533">
lu_zero's avatar
lu_zero committed
1322
<front>
lu_zero's avatar
lu_zero committed
1323 1324
<title>The Ogg Encapsulation Format Version 0</title>
<author initials="S." surname="Pfeiffer" fullname="Silvia Pfeiffer"></author>
lu_zero's avatar
lu_zero committed
1325
</front>
lu_zero's avatar
lu_zero committed
1326
<seriesInfo name="RFC" value="3533" />
lu_zero's avatar
lu_zero committed
1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339
</reference>

<reference anchor="libvorbis">
<front>
<title>libvorbis: Available from the Xiph website, http://www.xiph.org</title>
</front>
</reference>   

<reference anchor="vorbis-spec-ref">
<front>
<title>Ogg Vorbis I specification:  Codec setup and packet decode.  Available from the Xiph website, http://www.xiph.org</title>
</front>
</reference>   
lu_zero's avatar
lu_zero committed
1340

lu_zero's avatar
lu_zero committed
1341 1342 1343 1344 1345 1346 1347 1348
<reference anchor="rfc1952">
<front>
<title>GZIP file format specification version 4.3</title>
<author initials="P" surname="Deutsch" fullname="L. Peter Deutsch"></author>
</front>
<seriesInfo name="RFC" value="1952" />
</reference>

lu_zero's avatar
lu_zero committed
1349 1350 1351 1352 1353 1354 1355 1356 1357 1358
<reference anchor="RFC3611">
<front>
<title>RTP Control Protocol Extended Reports (RTCP XR)</title>
<author initials="T." surname="Friedman" fullname="T. Friedman" />
<author initials="R." surname="Caceres" fullname="R. Caceres" />
<author initials="A." surname="Clark" fullname="A. Clark" />
<date year="2003" month="November"/>
</front>
<seriesInfo name="RFC" value="3611"/>
</reference>
lu_zero's avatar
lu_zero committed
1359 1360 1361 1362 1363 1364 1365
<reference anchor="BZ2">
<front>

<title>libbz2 and bzip2</title>
<author initials="J" surname="Seward" fullname="Julian Seward" />
</front>
</reference>
lu_zero's avatar
lu_zero committed
1366 1367 1368
</references>
</back>
</rfc>