Expires: April 18, 2006 October 15, 2005
- draft-ietf-avt-vorbis-rtp-01
+ draft-kerr-avt-vorbis-rtp-05
RTP Payload Format for Vorbis Encoded Audio
Status of this Memo
Barbato Expires April 18, 2006 [Page 1]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
use of Vorbis with MIME and Session Description Protocol (SDP).
Barbato Expires April 18, 2006 [Page 2]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
1. Introduction
Barbato Expires April 18, 2006 [Page 3]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
0 1 2 3
Barbato Expires April 18, 2006 [Page 4]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
Sequence number: 16 bits
Barbato Expires April 18, 2006 [Page 5]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
This field sets the packet payload type for the Vorbis data. There
Barbato Expires April 18, 2006 [Page 6]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
[14].
Barbato Expires April 18, 2006 [Page 7]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
3. Configuration Headers
Barbato Expires April 18, 2006 [Page 8]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
3.1. In-band Header Transmission
Barbato Expires April 18, 2006 [Page 9]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
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
+ number of packet is set to 1.
3.2. Packed Headers Delivery
Barbato Expires April 18, 2006 [Page 10]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
The key difference between the in-band format is there is no need for
Barbato Expires April 18, 2006 [Page 11]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
Author: Luca Barbato
Barbato Expires April 18, 2006 [Page 12]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
The 2 bytes length field is necessary since this packet could be
Barbato Expires April 18, 2006 [Page 13]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
Packet 1:
Barbato Expires April 18, 2006 [Page 14]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
Packet 2:
Barbato Expires April 18, 2006 [Page 15]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
Packet 3:
Barbato Expires April 18, 2006 [Page 16]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
- Loss of any of the configuration headers, detailed below, is dealt
- with in the Loss of Configuration Headers Section later.
+ 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.
6. IANA Considerations
Additional information: none
- Person & email address to contact for further information:
Barbato Expires April 18, 2006 [Page 17]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
+
+ Person & email address to contact for further information:
Luca Barbato: <lu_zero@gentoo.org>
known in advance, the Configuration Packet for each file SHOULD be
passed to the client using the configuration attribute.
- The Vorbis configuration 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.
+ 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.
The port value is specified by the server application bound to the
address specified in the c attribute. The bitrate value and channels
specified in the rtpmap attribute MUST match the Vorbis sample rate
value. An example is found below.
- c=IN IP4/6
-
Barbato Expires April 18, 2006 [Page 18]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
+ c=IN IP4/6
m=audio RTP/AVP 98
a=rtpmap:98 VORBIS/44100/2
a=delivery:out_band/http
being case sensitive.
The answer to any offer, [8], MUST NOT change the URI specified in
- the configuration-uri attribute.
+ the configuration-uri attribute. The Configuration inlined in the
+ configuration parameter COULD change.
7. Congestion Control
The content itself could be a mix of live stream as the dj's speech
and stored streams as the music she plays.
- In this situation we don't know in advance how many codebooks we will
- use and. The clients can join anytime and users expect to start
Barbato Expires April 18, 2006 [Page 19]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
+ In this situation we don't know in advance how many codebooks we will
+ use and. The clients can join anytime and users expect to start
listening to the content in a short time
On join the client will receive the current Configuration necessary
Mike Smith, Phil Kerr, Michael Sparks, Magnus Westerlund, David
Barrett, Silvia Pfeiffer, Politecnico di Torino (LS)^3/IMG Group in
particular Federico Ridolfo, Francesco Varano, Giampaolo Mancini,
- Juan Carlos De Martin.
-
Barbato Expires April 18, 2006 [Page 20]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
+
+
+ Juan Carlos De Martin.
11. References
Available from the Xiph website, http://www.xiph.org".
[13] "Ogg Vorbis I specification: Comment field and header
- specification. Available from the Xiph website,
- http://www.xiph.org".
-
Barbato Expires April 18, 2006 [Page 21]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
+ specification. Available from the Xiph website,
+ http://www.xiph.org".
+
[14] "ITU (1992-1994) ITU-R Recommendation BS. 775-1 Multi-channel
stereophonic sound system with or without accompanying
picture. International Telecommunications Union. Available from
-
-
-
Barbato Expires April 18, 2006 [Page 22]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
Author's Address
Barbato Expires April 18, 2006 [Page 23]
\f
-Internet-Draft draft-ietf-avt-vorbis-rtp-01 October 2005
+Internet-Draft draft-kerr-avt-vorbis-rtp-05 October 2005
Intellectual Property Statement
<rfc ipr="full3667" docName="RTP Payload Format for Vorbis Encoded Audio">
<front>
-<title>draft-ietf-avt-vorbis-rtp-01</title>
+<title>draft-kerr-avt-vorbis-rtp-05</title>
<author initials="L" surname="Barbato" fullname="Luca Barbato">
<organization>Xiph.Org</organization>
]]></artwork>
</figure>
-<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>
+<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>
</section>
</t>
<t>
-Loss of any of the configuration headers, detailed below, is dealt with in the Loss of Configuration Headers Section later.
+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.
</t>
</section>
</t>
<t>
-The Vorbis configuration 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.
+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.
</t>
<t>
</t>
<t>
-The answer to any offer, <xref target="rfc3264"></xref>, MUST NOT change the URI specified in the configuration-uri attribute.
+The answer to any offer, <xref target="rfc3264"></xref>, MUST NOT change the URI specified in the configuration-uri attribute. The Configuration inlined in the configuration parameter COULD change.
</t>
</section>
<section anchor="Congestion Control" title="Congestion Control">
<t>
-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.
+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.
</t>
<t>
-If a particular multicast session has a large number of participants care must be taken to prevent an RTCP feedback implosion,
-<xref target="rtcp-feedback"></xref>, in the event of congestion.
+If a particular multicast session has a large number of participants care must be taken to prevent an RTCP feedback implosion, <xref target="rtcp-feedback"></xref>, in the event of congestion.
</t>
</section>