Abstract
+
+1. Intended Status (To Be Removed Upon Publication)
+
+ The intended status of this document is Proposed Standard.
+
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.
-
- Also included within this memo are media type registrations, and the
- details necessary for the use of Vorbis with the Session Description
- Protocol (SDP).
Internet-Draft draft-ietf-avt-rtp-vorbis-02 April 2007
+ information.
+
+ Also included within this memo are media type registrations, and the
+ details necessary for the use of Vorbis with the Session Description
+ Protocol (SDP).
+
Editors Note
All references to RFC XXXX are to be replaced by references to the
Table of Contents
- 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
- 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
- 2. Payload Format . . . . . . . . . . . . . . . . . . . . . . . . 3
- 2.1. RTP Header . . . . . . . . . . . . . . . . . . . . . . . . 3
- 2.2. Payload Header . . . . . . . . . . . . . . . . . . . . . . 5
- 2.3. Payload Data . . . . . . . . . . . . . . . . . . . . . . . 6
- 2.4. Example RTP Packet . . . . . . . . . . . . . . . . . . . . 7
- 3. Configuration Headers . . . . . . . . . . . . . . . . . . . . 8
- 3.1. In-band Header Transmission . . . . . . . . . . . . . . . 9
- 3.1.1. Packed Configuration . . . . . . . . . . . . . . . . . 9
- 3.2. Out of Band Transmission . . . . . . . . . . . . . . . . . 10
- 3.2.1. Packed Headers . . . . . . . . . . . . . . . . . . . . 11
- 3.3. Loss of Configuration Headers . . . . . . . . . . . . . . 13
- 4. Comment Headers . . . . . . . . . . . . . . . . . . . . . . . 13
- 5. Frame Packetization . . . . . . . . . . . . . . . . . . . . . 14
- 5.1. Example Fragmented Vorbis Packet . . . . . . . . . . . . . 15
- 5.2. Packet Loss . . . . . . . . . . . . . . . . . . . . . . . 17
- 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
- 7. SDP related considerations . . . . . . . . . . . . . . . . . . 20
- 7.1. Mapping MIME Parameters into SDP . . . . . . . . . . . . . 20
- 7.1.1. SDP Example . . . . . . . . . . . . . . . . . . . . . 20
- 7.2. Usage with the SDP Offer/Answer Model . . . . . . . . . . 21
- 8. Congestion Control . . . . . . . . . . . . . . . . . . . . . . 21
- 9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
- 9.1. Stream Radio . . . . . . . . . . . . . . . . . . . . . . . 22
- 10. Security Considerations . . . . . . . . . . . . . . . . . . . 22
- 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22
- 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
- 12.1. Normative References . . . . . . . . . . . . . . . . . . . 23
- 12.2. Informative References . . . . . . . . . . . . . . . . . . 24
+ 1. Intended Status (To Be Removed Upon Publication) . . . . . . . 1
+ 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
+ 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
+ 3. Payload Format . . . . . . . . . . . . . . . . . . . . . . . . 3
+ 3.1. RTP Header . . . . . . . . . . . . . . . . . . . . . . . . 3
+ 3.2. Payload Header . . . . . . . . . . . . . . . . . . . . . . 5
+ 3.3. Payload Data . . . . . . . . . . . . . . . . . . . . . . . 6
+ 3.4. Example RTP Packet . . . . . . . . . . . . . . . . . . . . 7
+ 4. Configuration Headers . . . . . . . . . . . . . . . . . . . . 8
+ 4.1. In-band Header Transmission . . . . . . . . . . . . . . . 9
+ 4.1.1. Packed Configuration . . . . . . . . . . . . . . . . . 9
+ 4.2. Out of Band Transmission . . . . . . . . . . . . . . . . . 10
+ 4.2.1. Packed Headers . . . . . . . . . . . . . . . . . . . . 11
+ 4.3. Loss of Configuration Headers . . . . . . . . . . . . . . 13
+ 5. Comment Headers . . . . . . . . . . . . . . . . . . . . . . . 13
+ 6. Frame Packetization . . . . . . . . . . . . . . . . . . . . . 14
+ 6.1. Example Fragmented Vorbis Packet . . . . . . . . . . . . . 15
+ 6.2. Packet Loss . . . . . . . . . . . . . . . . . . . . . . . 17
+ 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
+ 8. SDP related considerations . . . . . . . . . . . . . . . . . . 20
+ 8.1. Mapping MIME Parameters into SDP . . . . . . . . . . . . . 20
+ 8.1.1. SDP Example . . . . . . . . . . . . . . . . . . . . . 20
+ 8.2. Usage with the SDP Offer/Answer Model . . . . . . . . . . 21
+ 9. Congestion Control . . . . . . . . . . . . . . . . . . . . . . 21
+ 10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
+ 10.1. Stream Radio . . . . . . . . . . . . . . . . . . . . . . . 22
+ 11. Security Considerations . . . . . . . . . . . . . . . . . . . 22
+ 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22
+ 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
+ 13.1. Normative References . . . . . . . . . . . . . . . . . . . 23
+ 13.2. Informative References . . . . . . . . . . . . . . . . . . 24
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 24
Intellectual Property and Copyright Statements . . . . . . . . . . 25
-
-
-
-
-
-
-
Barbato Expires October 8, 2007 [Page 2]
\f
Internet-Draft draft-ietf-avt-rtp-vorbis-02 April 2007
-1. Introduction
+2. Introduction
Vorbis is a general purpose perceptual audio codec intended to allow
maximum encoder flexibility, thus allowing it to scale competitively
quadraphonic, 5.1, ambisonic, or up to 255 discrete channels).
Vorbis encoded audio is generally encapsulated within an Ogg format
- bitstream [1], which provides framing and synchronization. For the
+ bitstream [11], 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.
-1.1. Terminology
+2.1. Terminology
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 [2].
+ document are to be interpreted as described in RFC 2119 [1].
-2. Payload Format
+3. Payload Format
For RTP based transport of Vorbis encoded audio the standard RTP
header is followed by a 4 octets payload header, then the payload
bitstream information. There are 3 types of Vorbis payload data, an
RTP packet MUST contain just one of them at time.
-2.1. RTP Header
+3.1. RTP Header
- The format of the RTP header is specified in [3] and shown in Figure
+ The format of the RTP header is specified in [2] and shown in Figure
Figure 1. This payload format uses the fields of the header in a
manner consistent with that specification.
Figure 1: RTP Header
The RTP header begins with an octet of fields (V, P, X, and CC) to
- support specialized RTP uses (see [3] and [4] for details). For
+ support specialized RTP uses (see [2] and [3] for details). For
Vorbis RTP, the following values are used.
Version (V): 2 bits
Padding (P): 1 bit
Padding MAY be used with this payload format according to section 5.1
- of [3].
+ of [2].
Extension (X): 1 bit
- The Extension bit is used in accordance with [3].
+ The Extension bit is used in accordance with [2].
CSRC count (CC): 4 bits
- The CSRC count is used in accordance with [3].
+ The CSRC count is used in accordance with [2].
Marker (M): 1 bit
Set to zero. Audio silence suppression not used. This conforms to
- section 4.1 of [14].
+ section 4.1 of [13].
Payload Type (PT): 7 bits
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 [3].
+ packet sequence. This field is detailed further in [2].
Timestamp: 32 bits
SSRC/CSRC identifiers:
These two fields, 32 bits each with one SSRC field and a maximum of
- 16 CSRC fields, are as defined in [3].
+ 16 CSRC fields, are as defined in [2].
-2.2. Payload Header
+3.2. Payload Header
The 4 octets following the RTP Header section are the Payload Header.
This header is split into a number of bitfields detailing the format
the payload. If the packet contains fragmented data the number of
packets MUST be set to 0.
-2.3. Payload Data
+3.3. Payload Data
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 [13] typically produces
+ kilobytes). The reference implementation [12] 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
The payload packing of the Vorbis data packets MUST follow the
- guidelines set-out in [4] where the oldest packet occurs immediately
+ guidelines set-out in [3] where the oldest packet occurs immediately
after the RTP packet header. Subsequent packets, if any, MUST follow
in temporal order.
Channel mapping of the audio is in accordance with the Vorbis I
- Specification [14].
+ Specification [13].
-2.4. Example RTP Packet
+3.4. Example RTP Packet
Here is an example RTP packet containing two Vorbis packets.
decode the packets is the one indexed by the ident value.
-3. Configuration Headers
+4. Configuration Headers
Unlike other mainstream audio codecs Vorbis has no statically
configured probability model. Instead, it packs all entropy decoding
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 Vorbis I specification [14]
+ the compressed data. In addition, the Vorbis I specification [13]
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.
The delivery vectors in use are specified by an SDP attribute to
indicate the method and the optional URI where the Vorbis Packed
- Configuration (Section 3.1.1) Packets could be fetched. Different
+ Configuration (Section 4.1.1) 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 method is inline the Packed Configuration (Section 3.1.1) in
- the SDP as explained in the IANA considerations (Section 7.1)
+ delivery method is inline the Packed Configuration (Section 4.1.1) in
+ the SDP as explained in the IANA considerations (Section 8.1)
section.
The 24 bit Ident field is used to map which Configuration will be
information it MUST NOT decode the raw Vorbis data associated until
it fetches the correct Configuration.
-3.1. In-band Header Transmission
+4.1. In-band Header Transmission
- The Packed Configuration (Section 3.1.1) Payload is sent in-band with
+ The Packed Configuration (Section 4.1.1) 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.
-3.1.1. Packed Configuration
+4.1.1. Packed Configuration
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 [14], the identification and the setup will be packed
+ specification [13], the identification and the setup will be packed
together, the comment header is completely suppressed. Is up to the
client to provide a minimal size comment header to the decoder if
required by the implementation.
set to 0 since the packet bears the full Packed configuration, the
number of packet is set to 1.
-3.2. Out of Band Transmission
+4.2. Out of Band Transmission
This section, as stated above, does not cover all the possible out-
of-band delivery methods since they rely on different protocols and
Internet-Draft draft-ietf-avt-rtp-vorbis-02 April 2007
-3.2.1. Packed Headers
+4.2.1. Packed Headers
As mentioned above the RECOMMENDED delivery vector for Vorbis
configuration data is via a retrieval method that can be performed
Internet-Draft draft-ietf-avt-rtp-vorbis-02 April 2007
-3.2.1.1. Packed Headers IANA Considerations
+4.2.1.1. Packed Headers IANA Considerations
The following IANA considerations MUST only be applied to the packed
headers.
IETF AVT Working Group
-3.3. Loss of Configuration Headers
+4.3. Loss of Configuration Headers
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
decoding.
-4. Comment Headers
+5. Comment Headers
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 Vorbis documentation [14].
+ be found in the Vorbis documentation [13].
fragmented.
-5. Frame Packetization
+6. Frame Packetization
Each RTP packet contains either one Vorbis packet fragment, or an
integer number of complete Vorbis packets (up to a maximum of 15
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. Path MTU is detailed in
- [6] and [7].
+ [5] and [6].
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
packets. The length field shows the fragment length.
-5.1. Example Fragmented Vorbis Packet
+6.1. Example Fragmented Vorbis Packet
Here is an example fragmented Vorbis packet split over three RTP
packets. Each packet contains the standard RTP headers as well as
the timestamp remains set to the first packet in the sequence and the
sequence number has been incremented.
-5.2. Packet Loss
+6.2. Packet Loss
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
Loss of any of the Configuration fragment will result in the loss of
the full Configuration packet with the result detailed in the Loss of
- Configuration Headers (Section 3.3) section.
+ Configuration Headers (Section 4.3) section.
Internet-Draft draft-ietf-avt-rtp-vorbis-02 April 2007
-6. IANA Considerations
+7. IANA Considerations
MIME media type name: audio
rate: indicates the RTP timestamp clock rate as described in RTP
Profile for Audio and Video Conferences with Minimal Control.
- [4]
+ [3]
channels: indicates the number of audio channels as described in
RTP Profile for Audio and Video Conferences with Minimal
- Control. [4]
+ Control. [3]
delivery-method: indicates the delivery methods in use, the
possible values are: inline, in_band, out_band/specific_name
Where "specific_name" is the name of the out of band delivery
method.
- configuration: the base64 [9] representation of the Packed
- Headers (Section 3.2.1).
+ configuration: the base64 [8] representation of the Packed
+ Headers (Section 4.2.1).
Optional Parameters:
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 bzip2
- [12] or gzip [10]. A sha1 [11] checksum MAY be provided for
+ [10] or gzip [14]. A sha1 [9] checksum MAY be provided for
aggregates. In this latter case the URI will end with the
aggregate name, followed by its compressed extension if
- applies, a "!" and the base64 [9] representation of the
+ applies, a "!" and the base64 [8] representation of the
sha1hash of the above mentioned compressed aggregated as in:
"protocol://path/to/resource/aggregated.bz2!sha1hash". The
trailing '/' discriminates which of two methods are in use.
Restriction on usage:
This media type depends on RTP framing, and hence is only defined
- for transfer via RTP [3]
+ for transfer via RTP [2]
Author:
Internet-Draft draft-ietf-avt-rtp-vorbis-02 April 2007
-7. SDP related considerations
+8. SDP related considerations
The following paragraphs defines the mapping of the parameters
described in the IANA considerations section and their usage in the
- Offer/Answer Model [8].
+ Offer/Answer Model [7].
-7.1. Mapping MIME Parameters into SDP
+8.1. Mapping MIME Parameters into SDP
The information carried in the MIME media type specification has a
specific mapping to fields in the Session Description Protocol (SDP)
- [5], which is commonly used to describe RTP sessions. When SDP is
+ [4], which is commonly used to describe RTP sessions. When SDP is
used to specify sessions the mapping are as follows:
o The MIME type ("audio") goes in SDP "m=" as the media name.
specified in the rtpmap attribute MUST match the Vorbis sample rate
value. An example is found below.
-7.1.1. SDP Example
+8.1.1. SDP Example
The following example shows a basic SDP single stream. The first
configuration packet is inlined in the sdp, other configurations
Internet-Draft draft-ietf-avt-rtp-vorbis-02 April 2007
- The inline base64 [9] configuration string is omitted because of the
+ The inline base64 [8] configuration string is omitted because of the
lenght.
- c=IN IP4 192.0.0.1
+ c=IN IP4 192.0.2.1
m=audio RTP/AVP 98
a=rtpmap:98 vorbis/44100/2
a=fmtp:98 delivery-method=in_band; configuration=base64string;
being case sensitive. The a=fmtp line is a single line even if it is
presented broken because of clarity.
-7.2. Usage with the SDP Offer/Answer Model
+8.2. Usage with the SDP Offer/Answer Model
The offer, as described in An Offer/Answer Model Session Description
- Protocol [8], may contain a large number of delivery methods per
+ Protocol [7], 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.
-8. Congestion Control
+9. Congestion Control
Vorbis clients SHOULD send regular receiver reports detailing
congestion. A mechanism for dynamically downgrading the stream,
if one is available.
-9. Examples
+10. Examples
The following examples are common usage patterns that MAY be applied
in such situations, the main scope of this section is to explain
Internet-Draft draft-ietf-avt-rtp-vorbis-02 April 2007
-9.1. Stream Radio
+10.1. Stream Radio
This is one of the most common situation: one single server streaming
content in multicast, the clients may start a session at random time.
already known.
-10. Security Considerations
+11. Security Considerations
RTP packets using this payload format are subject to the security
- considerations discussed in the RTP specification [3]. This implies
+ considerations discussed in the RTP specification [2]. 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 the
taken to prevent buffer overflows in the client applications.
-11. Acknowledgments
+12. Acknowledgments
This document is a continuation of draft-moffitt-vorbis-rtp-00.txt
Ridolfo, Francesco Varano, Giampaolo Mancini, Juan Carlos De Martin.
-12. References
+13. References
-12.1. Normative References
+13.1. Normative References
- [1] Pfeiffer, S., "The Ogg Encapsulation Format Version 0",
- RFC 3533.
-
- [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
+ [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119.
- [3] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,
+ [2] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,
"RTP: A Transport Protocol for real-time applications",
RFC 3550.
- [4] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video
+ [3] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video
Conferences with Minimal Control.", RFC 3551.
- [5] Handley, M. and V. Jacobson, "SDP: Session Description
- Protocol", RFC 2327.
+ [4] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
+ Description Protocol", RFC 4566, July 2006.
- [6] Mogul et al., J., "Path MTU Discovery", RFC 1063.
+ [5] Mogul, J. and S. Deering, "Path MTU discovery", RFC 1191,
+ November 1990.
- [7] McCann et al., J., "Path MTU Discovery for IP version 6",
+ [6] McCann et al., J., "Path MTU Discovery for IP version 6",
RFC 1981.
- [8] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with
+ [7] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with
Session Description Protocol (SDP)", RFC 3264.
- [9] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings",
+ [8] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings",
RFC 3548.
- [10] Deutsch, P., "GZIP file format specification version 4.3",
- RFC 1952.
+ [9] National Institute of Standards and Technology, "Secure Hash
+ Standard", May 1993.
+
+ [10] Seward, J., "libbz2 and bzip2".
+
- [11] National Institute of Standards and Technology, "Secure Hash
Internet-Draft draft-ietf-avt-rtp-vorbis-02 April 2007
- Standard", May 1993.
-
- [12] Seward, J., "libbz2 and bzip2".
+13.2. Informative References
-12.2. Informative References
+ [11] Pfeiffer, S., "The Ogg Encapsulation Format Version 0",
+ RFC 3533.
- [13] "libvorbis: Available from the Xiph website,
+ [12] "libvorbis: Available from the Xiph website,
http://www.xiph.org".
- [14] "Ogg Vorbis I specification: Codec setup and packet decode.
+ [13] "Ogg Vorbis I specification: Codec setup and packet decode.
Available from the Xiph website, http://www.xiph.org".
+ [14] Deutsch, P., "GZIP file format specification version 4.3",
+ RFC 1952.
+
[15] Friedman, T., Caceres, R., and A. Clark, "RTP Control Protocol
Extended Reports (RTCP XR)", RFC 3611, November 2003.
-
-
Barbato Expires October 8, 2007 [Page 24]
\f
Internet-Draft draft-ietf-avt-rtp-vorbis-02 April 2007
<keyword>RTP</keyword>
<abstract>
+
+<section title="Intended Status (To Be Removed Upon Publication)">
+<t>The intended status of this document is Proposed Standard.</t>
+</section>
+
<t>
This document describes an RTP payload format for transporting Vorbis encoded
audio. It details the RTP encapsulation mechanism for raw Vorbis data and
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.
-Path MTU is detailed in <xref target="rfc1063"></xref> and <xref target="rfc1981"></xref>.
+Path MTU is detailed in <xref target="rfc1191"></xref> and <xref target="rfc1981"></xref>.
</t>
<t>
<t>
The information carried in the MIME media type specification has a specific
-mapping to fields in the Session Description Protocol (SDP) <xref target="rfc2327"></xref>, which is commonly used to describe RTP sessions. When SDP is used
+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:
</t>
the lenght.</t>
<list style="empty">
-<t>c=IN IP4 192.0.0.1</t>
+<t>c=IN IP4 192.0.2.1</t>
<t>m=audio RTP/AVP 98</t>
<t>a=rtpmap:98 vorbis/44100/2</t>
<t>a=fmtp:98 delivery-method=in_band; configuration=base64string; delivery-method=out_band/rtsp; configuration-uri=rtsp://path/to/the/resource; delivery-method=out_band/http; configuration-uri=http://another/path/to/resource/aggregate.bz2!8b6237eb5154a0ea12811a94e8e2697b3312bc6c;</t>
<references title="Normative References">
-<reference anchor="rfc3533">
-<front>
-<title>The Ogg Encapsulation Format Version 0</title>
-<author initials="S." surname="Pfeiffer" fullname="Silvia Pfeiffer"></author>
-</front>
-<seriesInfo name="RFC" value="3533" />
-</reference>
-
<reference anchor="rfc2119">
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels </title>
<date month="July" year="2003" />
<seriesInfo name="RFC" value="3551" />
</reference>
-
-<reference anchor="rfc2327">
+
+<reference anchor='rfc4566'>
+
<front>
<title>SDP: Session Description Protocol</title>
-<author initials="M." surname="Handley" fullname="Mark Handley"></author>
-<author initials="V." surname="Jacobson" fullname="Van Jacobson"></author>
+<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' />
</front>
-<seriesInfo name="RFC" value="2327" />
-</reference>
-<reference anchor="rfc1063">
+<seriesInfo name='RFC' value='4566' />
+<format type='TXT' octets='108820' target='ftp://ftp.isi.edu/in-notes/rfc4566.txt' />
+</reference>
+
+<reference anchor='rfc1191'>
+
<front>
-<title>Path MTU Discovery</title>
-<author initials="J." surname="Mogul et al." fullname="J. Mogul et al."></author>
+<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' />
</front>
-<seriesInfo name="RFC" value="1063" />
-</reference>
+
+<seriesInfo name='RFC' value='1191' />
+<format type='TXT' octets='47936' target='ftp://ftp.isi.edu/in-notes/rfc1191.txt' />
+</reference>
<reference anchor="rfc1981">
<front>
<author initials="S." surname="Josefsson" fullname="Simon Josefsson"></author>
</front>
<seriesInfo name="RFC" value="3548" />
-</reference>
-
-<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>
-
<reference anchor="FIPS180">
<front>
<title>Secure Hash Standard</title>
<date month="May" year="1993"/>
</front>
</reference>
+</references>
-<reference anchor="BZ2">
+<references title="Informative References">
+
+<reference anchor="rfc3533">
<front>
-<title>libbz2 and bzip2</title>
-<author initials="J" surname="Seward" fullname="Julian Seward" />
+<title>The Ogg Encapsulation Format Version 0</title>
+<author initials="S." surname="Pfeiffer" fullname="Silvia Pfeiffer"></author>
</front>
+<seriesInfo name="RFC" value="3533" />
</reference>
-
-</references>
-
-<references title="Informative References">
<reference anchor="libvorbis">
<front>
<title>libvorbis: Available from the Xiph website, http://www.xiph.org</title>
</front>
</reference>
+<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>
+
<reference anchor="RFC3611">
<front>
<title>RTP Control Protocol Extended Reports (RTCP XR)</title>
</front>
<seriesInfo name="RFC" value="3611"/>
</reference>
+<reference anchor="BZ2">
+<front>
+
+<title>libbz2 and bzip2</title>
+<author initials="J" surname="Seward" fullname="Julian Seward" />
+</front>
+</reference>
</references>
</back>
</rfc>
projects / platform / upstream / libvorbis.git / commitdiff