[xiph-commits] r10562 - trunk/vorbis/doc

lu_zero at svn.xiph.org lu_zero at svn.xiph.org
Wed Dec 7 07:11:51 PST 2005


Author: lu_zero
Date: 2005-12-07 07:11:48 -0800 (Wed, 07 Dec 2005)
New Revision: 10562

Modified:
   trunk/vorbis/doc/draft-ietf-avt-vorbis-rtp-00.txt
   trunk/vorbis/doc/draft-ietf-avt-vorbis-rtp-00.xml
Log:
References updated, WKC section still present for now

Modified: trunk/vorbis/doc/draft-ietf-avt-vorbis-rtp-00.txt
===================================================================
--- trunk/vorbis/doc/draft-ietf-avt-vorbis-rtp-00.txt	2005-12-07 14:53:36 UTC (rev 10561)
+++ trunk/vorbis/doc/draft-ietf-avt-vorbis-rtp-00.txt	2005-12-07 15:11:48 UTC (rev 10562)
@@ -210,7 +210,7 @@
    Marker (M): 1 bit
 
    Set to zero.  Audio silence suppression not used.  This conforms to
-   section 4.1 of [12].
+   section 4.1 of [15].
 
    Payload Type (PT): 7 bits
 
@@ -300,7 +300,7 @@
    Raw Vorbis packets are unbounded in length currently, although at
    some future point there will likely be a practical limit placed on
    them.  Typical Vorbis packet sizes are from very small (2-3 bytes) to
-   quite large (8-12 kilobytes).  The reference implementation [11]
+   quite large (8-12 kilobytes).  The reference implementation [14]
    typically produces packets less than ~800 bytes, except for the setup
    header packets which are ~4-12 kilobytes.  Within an RTP context the
    maximum packet size, including the RTP and payload headers, SHOULD be
@@ -338,7 +338,7 @@
 Internet-Draft        draft-kerr-avt-vorbis-rtp-05          October 2005
 
 
-   Specification [12].
+   Specification [15].
 
 2.4.  Example RTP Packet
 
@@ -409,7 +409,7 @@
 
    Thus these two codebook header packets must be received by the
    decoder before any audio data can be interpreted.  In addition, the
-   Vorbis I specification [12] requires the presense of a comment header
+   Vorbis I specification [15] requires the presense of a comment header
    packet which gives simple metadata about the stream.  This
    requirement poses problems in RTP, which is often used over
    unreliable transports.
@@ -461,7 +461,7 @@
 
    A Vorbis Packed Configuration is indicated with the payload type
    field set to 1.  Of the three headers, defined in the Vorbis I
-   specification [12], the identification and the setup will be packed
+   specification [15], 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.
@@ -674,13 +674,12 @@
 Internet-Draft        draft-kerr-avt-vorbis-rtp-05          October 2005
 
 
-   {FIXME: reference to bzip2, gz, and sha1sum} This off band delivery
-   method MUST be signaled as "out_band/wkc/list_name" using the
-   mandated parameter delivery-method.  An optional configuration-uri
-   MAY point to a location where to fetch it.  The list is in the form
-   of Packed Headers (Section 3.2.1), that MAY be compressed using bzip2
-   or gz algorithms as further explained in the IANA Considerations
-   (Section 6) section.
+   This off band delivery method MUST be signaled as "out_band/wkc/
+   list_name" using the mandated parameter delivery-method.  An optional
+   configuration-uri MAY point to a location where to fetch it.  The
+   list is in the form of Packed Headers (Section 3.2.1), that MAY be
+   compressed using bzip2 [13] or gzip [11] as further explained in the
+   IANA Considerations (Section 6) section.
 
    Only one list MUST be used at time.  During SDP Offer/Answer [8]
    client and server MAY agree on a specific list, that subject will be
@@ -705,7 +704,7 @@
    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 [12].
+   in the Vorbis documentation [15].
 
 
 
@@ -725,6 +724,7 @@
 
 
 
+
 Barbato                  Expires April 24, 2006                [Page 13]
 
 Internet-Draft        draft-kerr-avt-vorbis-rtp-05          October 2005
@@ -982,9 +982,9 @@
          "protocol://path/to/resource/".  Depending on the specific
          method the single ident packet could be retrived by their
          number, or aggregated in a single stream, aggregates MAY be
-         compressed using gz or bzip2 and an sha1 checksum MAY be
-         provided in the form of "protocol://path/to/resource/!
-         sha1hash"
+         compressed using bzip2 [13] or gzip [11] and an sha1 [12]
+         checksum MAY be provided in the form of
+         "protocol://path/to/resource/! sha1hash"
 
    Encoding considerations:
 
@@ -1256,15 +1256,23 @@
          Internet Draft (draft-ietf-avt-rtcp-feedback-11: Work in
          progress).
 
+   [11]  Deutsch, P., "GZIP file format specification version 4.3",
+         RFC 1952.
+
+   [12]  National Institute of Standards and Technology, "Secure Hash
+         Standard", May 1993.
+
+   [13]  Seward, J., "libbz2 and bzip2".
+
 11.2.  Informative References
 
-   [11]  "libvorbis: Available from the Xiph website,
+   [14]  "libvorbis: Available from the Xiph website,
          http://www.xiph.org".
 
-   [12]  "Ogg Vorbis I specification:  Codec setup and packet decode.
+   [15]  "Ogg Vorbis I specification:  Codec setup and packet decode.
          Available from the Xiph website, http://www.xiph.org".
 
-   [13]  "Ogg Vorbis I specification:  Comment field and header
+   [16]  "Ogg Vorbis I specification:  Comment field and header
          specification.  Available from the Xiph website,
          http://www.xiph.org".
 
@@ -1277,14 +1285,6 @@
 
 
 
-
-
-
-
-
-
-
-
 Barbato                  Expires April 24, 2006                [Page 23]
 
 Internet-Draft        draft-kerr-avt-vorbis-rtp-05          October 2005

Modified: trunk/vorbis/doc/draft-ietf-avt-vorbis-rtp-00.xml
===================================================================
--- trunk/vorbis/doc/draft-ietf-avt-vorbis-rtp-00.xml	2005-12-07 14:53:36 UTC (rev 10561)
+++ trunk/vorbis/doc/draft-ietf-avt-vorbis-rtp-00.xml	2005-12-07 15:11:48 UTC (rev 10562)
@@ -590,8 +590,7 @@
 </t>
 
 <t>
-{FIXME: reference to bzip2, gz, and sha1sum}
-This off band delivery method MUST be signaled as "out_band/wkc/list_name" using the mandated parameter delivery-method. An optional configuration-uri MAY point to a location where to fetch it. The list is in the form of <xref target="Packed Headers">Packed Headers</xref>, that MAY be compressed using bzip2 or gz algorithms as further explained in the <xref target="IANA Considerations">IANA Considerations</xref> section.
+This off band delivery method MUST be signaled as "out_band/wkc/list_name" using the mandated parameter delivery-method. An optional configuration-uri MAY point to a location where to fetch it. The list is in the form of <xref target="Packed Headers">Packed Headers</xref>, that MAY be compressed using <xref target="BZ2">bzip2</xref> or <xref target="rfc1952">gzip</xref> as further explained in the <xref target="IANA Considerations">IANA Considerations</xref> section.
 </t>
 
 <t>
@@ -824,7 +823,7 @@
 <vspace blankLines="1" />
 
 <list style="hanging">
-<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 the single ident packet could be retrived by their number, or aggregated in a single stream, aggregates MAY be compressed using gz or bzip2 and an sha1 checksum MAY be provided in the form of "protocol://path/to/resource/! sha1hash"</t>
+<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 the single ident packet could be retrived by their number, or aggregated in a single stream, aggregates MAY be compressed using <xref target="BZ2">bzip2</xref> or <xref target="rfc1952">gzip</xref> and an <xref target="FIPS180">sha1</xref> checksum MAY be provided in the form of "protocol://path/to/resource/! sha1hash"</t>
 </list>
 </t>
 
@@ -1128,7 +1127,32 @@
 <seriesInfo name="Internet Draft" value="(draft-ietf-avt-rtcp-feedback-11: Work in progress)" />
 </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>
+<author>
+<organization>National Institute of Standards and Technology</organization>
+</author>
+<date month="May" year="1993"/>
+</front>
+</reference>
+
+<reference anchor="BZ2">
+<front>
+<title>libbz2 and bzip2</title>
+<author initials="J" surname="Seward" fullname="Julian Seward" />
+</front>
+</reference>
+
+
 </references>
 
 <references title="Informative References">



More information about the commits mailing list