[xiph-commits] r10224 - trunk/theora/doc
lu_zero at svn.xiph.org
lu_zero at svn.xiph.org
Fri Oct 21 06:53:11 PDT 2005
Author: lu_zero
Date: 2005-10-21 06:53:08 -0700 (Fri, 21 Oct 2005)
New Revision: 10224
Modified:
trunk/theora/doc/draft-barbato-avt-rtp-theora-00.txt
trunk/theora/doc/draft-barbato-avt-rtp-theora-00.xml
Log:
Minor changes
Modified: trunk/theora/doc/draft-barbato-avt-rtp-theora-00.txt
===================================================================
--- trunk/theora/doc/draft-barbato-avt-rtp-theora-00.txt 2005-10-21 13:52:46 UTC (rev 10223)
+++ trunk/theora/doc/draft-barbato-avt-rtp-theora-00.txt 2005-10-21 13:53:08 UTC (rev 10224)
@@ -78,12 +78,12 @@
3. Configuration Headers . . . . . . . . . . . . . . . . . . . . 8
3.1. In-band Header Transmission . . . . . . . . . . . . . . . 9
3.1.1. Packed Configuration . . . . . . . . . . . . . . . . . 9
- 3.2. Packed Headers Delivery . . . . . . . . . . . . . . . . . 10
- 3.2.1. Packed Headers IANA Considerations . . . . . . . . . . 11
+ 3.2. Out of Band Transmission . . . . . . . . . . . . . . . . . 10
+ 3.2.1. Packed Headers . . . . . . . . . . . . . . . . . . . . 10
3.3. Loss of Configuration Headers . . . . . . . . . . . . . . 12
4. Comment Headers . . . . . . . . . . . . . . . . . . . . . . . 12
5. Frame Packetizing . . . . . . . . . . . . . . . . . . . . . . 13
- 5.1. Example Fragmented Theora Packet . . . . . . . . . . . . . 13
+ 5.1. Example Fragmented Theora Packet . . . . . . . . . . . . . 14
5.2. Packet Loss . . . . . . . . . . . . . . . . . . . . . . . 16
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
6.1. Mapping MIME Parameters into SDP . . . . . . . . . . . . . 18
@@ -481,7 +481,7 @@
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Ident | 0 | 1 | 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- | Setup length | Identification ..
+ | length | Identification ..
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
.. Identification ..
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -489,14 +489,14 @@
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
.. Identification |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- .. | Setup ..
+ .. | Setup ..
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
.. Setup ..
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
.. Setup |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- Figure 6: Setup Header
+ Figure 6: Packed Configuration Figure
@@ -511,8 +511,16 @@
set to 0 since the packet bears the full Packed configuration, the
number of packet is set to 1.
-3.2. Packed Headers Delivery
+3.2. Out of Band Transmission
+ This section, as stated before, won't cover all the possible out-of-
+ band delivery methods since they rely to different protocols and be
+ linked to a specific application. The following packet definition
+ SHOULD be used in out-of-band delivery and MUST be used when
+ Configuration is inlined in the SDP.
+
+3.2.1. Packed Headers
+
As mentioned above the RECOMMENDED delivery vector for Theora
configuration data is via a retrieval method that can be performed
using a reliable transport protocol. As the RTP headers are not
@@ -535,9 +543,25 @@
Figure 7: Packed Headers Overview
Since the Configuration Ident and the Identification Header are fixed
- lenght there is only a 2 byte Setup Lenght tag to define the lenght
- of the Setup header.
+ lenght there is only a 2 byte Lenght tag to define the lenght of the
+ packed headers.
+
+
+
+
+
+
+
+
+
+
+
+Barbato Expires April 18, 2006 [Page 10]
+
+Internet-Draft draft-barbato-avt-rtp-theora-00 October 2005
+
+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -554,18 +578,10 @@
Figure 8: Packed Headers Detail
-
-
-
-Barbato Expires April 18, 2006 [Page 10]
-
-Internet-Draft draft-barbato-avt-rtp-theora-00 October 2005
-
-
The key difference between the in-band format is there is no need for
the payload header octet.
-3.2.1. Packed Headers IANA Considerations
+3.2.1.1. Packed Headers IANA Considerations
The following IANA considerations MUST only be applied to the packed
headers.
@@ -595,6 +611,13 @@
Published specification:
+
+
+Barbato Expires April 18, 2006 [Page 11]
+
+Internet-Draft draft-barbato-avt-rtp-theora-00 October 2005
+
+
See RFC XXXX for details.
Applications which use this media type:
@@ -611,13 +634,6 @@
Author/Change controller:
-
-
-Barbato Expires April 18, 2006 [Page 11]
-
-Internet-Draft draft-barbato-avt-rtp-theora-00 October 2005
-
-
Author: Luca Barbato
Change controller: IETF AVT Working Group
@@ -642,6 +658,22 @@
completely. The details on the format of the comments can be found
in the Theora documentation [12].
+
+
+
+
+
+
+
+
+
+
+
+Barbato Expires April 18, 2006 [Page 12]
+
+Internet-Draft draft-barbato-avt-rtp-theora-00 October 2005
+
+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -666,14 +698,6 @@
Figure 9: Comment Packet
-
-
-
-Barbato Expires April 18, 2006 [Page 12]
-
-Internet-Draft draft-barbato-avt-rtp-theora-00 October 2005
-
-
The 2 bytes length field is necessary since this packet could be
fragmented.
@@ -698,6 +722,14 @@
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
+
+
+
+Barbato Expires April 18, 2006 [Page 13]
+
+Internet-Draft draft-barbato-avt-rtp-theora-00 October 2005
+
+
packets.
5.1. Example Fragmented Theora Packet
@@ -706,30 +738,6 @@
packets. Each packet contains the standard RTP headers as well as
the 4 octet Theora headers.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Barbato Expires April 18, 2006 [Page 13]
-
-Internet-Draft draft-barbato-avt-rtp-theora-00 October 2005
-
-
Packet 1:
0 1 2 3
@@ -773,14 +781,6 @@
-
-
-
-
-
-
-
-
Barbato Expires April 18, 2006 [Page 14]
Internet-Draft draft-barbato-avt-rtp-theora-00 October 2005
@@ -921,7 +921,7 @@
values are:inline, in_band, out_band/specific-method
configuration: the base16 [15] (hexadecimal) representation of the
- Packed Headers (Section 3.2).
+ Packed Headers (Section 3.2.1).
Optional Parameters:
@@ -1001,7 +1001,7 @@
location where all of the Configuration Packets needed for the life
of the session reside.
- Example:
+ The answer to any offer, [5], MUST NOT change the URI specified in
@@ -1010,17 +1010,18 @@
Internet-Draft draft-barbato-avt-rtp-theora-00 October 2005
+ the configuration-uri attribute. The Configuration inlined in the
+ configuration parameter COULD change.
+
+ Example:
+
c=IN IP4/6
m=video RTP/AVP 98
a=rtpmap:98 theora/90000
a=fmtp:98 sampling=YCbCr-4:2:2; width=1280; height=720; delivery-
method=inline; configuration=base16string1;
- The answer to any offer, [5], MUST NOT change the URI specified in
- the configuration-uri attribute. The Configuration inlined in the
- configuration parameter COULD change.
-
7. Security Considerations
RTP packets using this payload format are subject to the security
@@ -1057,7 +1058,6 @@
RFC 3550.
[4] Schulzrinne, H. and S. Casner, "RTP Profile for video and Video
- Conferences with Minimal Control.", RFC 3551.
@@ -1066,6 +1066,8 @@
Internet-Draft draft-barbato-avt-rtp-theora-00 October 2005
+ Conferences with Minimal Control.", RFC 3551.
+
[5] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with
Session Description Protocol (SDP)", RFC 3264.
@@ -1115,8 +1117,6 @@
-
-
Barbato Expires April 18, 2006 [Page 20]
Internet-Draft draft-barbato-avt-rtp-theora-00 October 2005
Modified: trunk/theora/doc/draft-barbato-avt-rtp-theora-00.xml
===================================================================
--- trunk/theora/doc/draft-barbato-avt-rtp-theora-00.xml 2005-10-21 13:52:46 UTC (rev 10223)
+++ trunk/theora/doc/draft-barbato-avt-rtp-theora-00.xml 2005-10-21 13:53:08 UTC (rev 10224)
@@ -341,7 +341,7 @@
A Theora Packed Configuration is indicated with the payload type field set to 1. Of the three headers, defined in the <xref target="theora-spec-ref">Theora I specification</xref>, the identification and the setup will be packed together, the comment header is completely suppressed. Is up to the client provide a minimal size comment header to the decoder if required by the implementation.
</t>
-<figure anchor="Setup Header Figure" title="Setup Header">
+<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
@@ -358,7 +358,7 @@
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Ident | 0 | 1 | 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- | Setup length | Identification ..
+ | length | Identification ..
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
.. Identification ..
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -366,7 +366,7 @@
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
.. Identification |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- .. | Setup ..
+ .. | Setup ..
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
.. Setup ..
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -382,9 +382,16 @@
</section>
-<section anchor="Packed Headers Delivery" title="Packed Headers Delivery">
+<section anchor="Out of Band Transmission" title="Out of Band Transmission">
+
<t>
+This section, as stated before, won't cover all the possible out-of-band delivery methods since they rely to different protocols and be linked to a specific application. The following packet definition SHOULD be used in out-of-band delivery and MUST be used when Configuration is inlined in the SDP.
+</t>
+
+<section anchor="Packed Headers" title="Packed Headers">
+
+<t>
As mentioned above the RECOMMENDED delivery vector for Theora 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 starts with a 32 bit count field which details the number of packed headers that are contained in the bundle. Next is the Packed header payload for each chained Theora stream.
</t>
@@ -403,7 +410,7 @@
</figure>
<t>
-Since the Configuration Ident and the Identification Header are fixed lenght there is only a 2 byte Setup Lenght tag to define the lenght of the Setup header.
+Since the Configuration Ident and the Identification Header are fixed lenght there is only a 2 byte Lenght tag to define the lenght of the packed headers.
</t>
<figure anchor="Packed Headers Detail Figure" title="Packed Headers Detail">
@@ -492,6 +499,7 @@
</section>
</section>
+</section>
<section anchor="Loss of Configuration Headers" title="Loss of Configuration Headers">
@@ -690,7 +698,7 @@
delivery-method: indicates the delivery methods in use, the possible values are:inline, in_band, out_band/specific-method
</t>
<t>
-configuration: the <xref target="rfc3548">base16</xref> (hexadecimal) representation of the <xref target="Packed Headers Delivery">Packed Headers</xref>.
+configuration: the <xref target="rfc3548">base16</xref> (hexadecimal) representation of the <xref target="Packed Headers">Packed Headers</xref>.
</t>
<t>
@@ -771,6 +779,9 @@
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>
+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>
<t>Example:</t>
<vspace blankLines="1" />
@@ -782,9 +793,6 @@
<t>a=fmtp:98 sampling=YCbCr-4:2:2; width=1280; height=720; delivery-method=inline; configuration=base16string1;</t>
</list>
-<t>
-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>
More information about the commits
mailing list