[xiph-commits] r14990 - trunk/standards
ivo at svn.xiph.org
ivo at svn.xiph.org
Mon Jun 2 11:28:27 PDT 2008
Author: ivo
Date: 2008-06-02 11:28:27 -0700 (Mon, 02 Jun 2008)
New Revision: 14990
Modified:
trunk/standards/draft-goncalves-rfc3534bis.txt
trunk/standards/draft-goncalves-rfc3534bis.xml
Log:
Reordered references. Added Acknowledgements section. Other corrections.
Modified: trunk/standards/draft-goncalves-rfc3534bis.txt
===================================================================
--- trunk/standards/draft-goncalves-rfc3534bis.txt 2008-06-02 18:27:04 UTC (rev 14989)
+++ trunk/standards/draft-goncalves-rfc3534bis.txt 2008-06-02 18:28:27 UTC (rev 14990)
@@ -5,11 +5,11 @@
Internet-Draft S. Pfeiffer
Obsoletes: 3534 (if approved) C. Montgomery
Intended status: Standards Track Xiph
-Expires: November 27, 2008 May 26, 2008
+Expires: December 4, 2008 June 2, 2008
Ogg Media Types
- draft-goncalves-rfc3534bis-06
+ draft-goncalves-rfc3534bis-07
Status of This Memo
@@ -34,7 +34,7 @@
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
- This Internet-Draft will expire on November 27, 2008.
+ This Internet-Draft will expire on December 4, 2008.
Copyright Notice
@@ -52,9 +52,9 @@
-Goncalves, et al. Expires November 27, 2008 [Page 1]
+Goncalves, et al. Expires December 4, 2008 [Page 1]
-Internet-Draft Ogg Media Types May 2008
+Internet-Draft Ogg Media Types June 2008
Table of Contents
@@ -72,10 +72,11 @@
10.1. application/ogg . . . . . . . . . . . . . . . . . . . . . . 8
10.2. video/ogg . . . . . . . . . . . . . . . . . . . . . . . . . 9
10.3. audio/ogg . . . . . . . . . . . . . . . . . . . . . . . . . 10
- 11. Copying Conditions . . . . . . . . . . . . . . . . . . . . 11
- 12. References . . . . . . . . . . . . . . . . . . . . . . . . 11
- 12.1. Normative References . . . . . . . . . . . . . . . . . . . 11
- 12.2. Informative References . . . . . . . . . . . . . . . . . . 11
+ 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 11
+ 12. Copying Conditions . . . . . . . . . . . . . . . . . . . . 11
+ 13. References . . . . . . . . . . . . . . . . . . . . . . . . 11
+ 13.1. Normative References . . . . . . . . . . . . . . . . . . . 11
+ 13.2. Informative References . . . . . . . . . . . . . . . . . . 12
@@ -107,10 +108,9 @@
-
-Goncalves, et al. Expires November 27, 2008 [Page 2]
+Goncalves, et al. Expires December 4, 2008 [Page 2]
-Internet-Draft Ogg Media Types May 2008
+Internet-Draft Ogg Media Types June 2008
1. Introduction
@@ -129,7 +129,7 @@
general security considerations.
The Ogg container format is known to contain [Theora] or [Dirac]
- video, [Speex] (narrow-band and wide-band speech), [Vorbis] or [FLAC]
+ video, [Speex] (narrow-band and wide-band) speech, [Vorbis] or [FLAC]
audio, and [CMML] timed text/metadata. As Ogg encapsulates binary
data, it is possible to include any other type of video, audio,
image, text or, generally speaking, any time-continuously sampled
@@ -164,9 +164,9 @@
-Goncalves, et al. Expires November 27, 2008 [Page 3]
+Goncalves, et al. Expires December 4, 2008 [Page 3]
-Internet-Draft Ogg Media Types May 2008
+Internet-Draft Ogg Media Types June 2008
An implementation is a software module that supports one of the media
@@ -216,20 +216,20 @@
backward and forward compatibility with existing and future data.
These media types can optionally use the "codecs" parameter described
- in [RFC4281]. Codecs encapsulated in Ogg require an 8 byte text
+ in [RFC4281]. Codecs encapsulated in Ogg require a text identifier
-Goncalves, et al. Expires November 27, 2008 [Page 4]
+Goncalves, et al. Expires December 4, 2008 [Page 4]
-Internet-Draft Ogg Media Types May 2008
+Internet-Draft Ogg Media Types June 2008
- identifier at the beginning of the first header page, hence a
- possible machine-readable method to identify the encapsulated codecs
- would be through this header. The following table illustrates how
- those header values map into strings that SHOULD be used in the
- "codecs" parameter when dealing with Ogg media types.
+ at the beginning of the first header page, hence a machine-readable
+ method to identify the encapsulated codecs would be through this
+ header. The following table illustrates how those header values map
+ into strings that are used in the "codecs" parameter when dealing
+ with Ogg media types.
Codec Identifier | Codecs Parameter
-----------------------------------------------------------
@@ -276,9 +276,9 @@
-Goncalves, et al. Expires November 27, 2008 [Page 5]
+Goncalves, et al. Expires December 4, 2008 [Page 5]
-Internet-Draft Ogg Media Types May 2008
+Internet-Draft Ogg Media Types June 2008
As such, the application/ogg type is the recommended choice to serve
@@ -332,9 +332,9 @@
-Goncalves, et al. Expires November 27, 2008 [Page 6]
+Goncalves, et al. Expires December 4, 2008 [Page 6]
-Internet-Draft Ogg Media Types May 2008
+Internet-Draft Ogg Media Types June 2008
Issues may arise on applications that use Ogg for streaming or file
@@ -388,9 +388,9 @@
-Goncalves, et al. Expires November 27, 2008 [Page 7]
+Goncalves, et al. Expires December 4, 2008 [Page 7]
-Internet-Draft Ogg Media Types May 2008
+Internet-Draft Ogg Media Types June 2008
10. Ogg Media Types
@@ -403,13 +403,15 @@
Required parameters: none
- Optional parameters: codecs, as defined in RFC 4281.
+ Optional parameters: codecs, whose syntax is defined in RFC 4281.
+ See section 4 of RFC XXXX for a list of allowed values.
- Encoding considerations: See section 6.
+ Encoding considerations: See section 6 of RFC XXXX.
- Security considerations: See section 7.
+ Security considerations: See section 7 of RFC XXXX.
- Interoperability considerations: None, as noted in section 8.
+ Interoperability considerations: None, as noted in section 8 of RFC
+ XXXX.
Published specification: RFC 3533
@@ -424,9 +426,9 @@
File extension(s): .ogx
RFC 3534 defined the file extension .ogg for application/ogg,
- which this document obsoletes in favor of .ogx due to concerns
- where, historically, some implementations expect .ogg files to be
- solely Vorbis-encoded audio.
+ which RFC XXXX obsoletes in favor of .ogx due to concerns where,
+ historically, some implementations expect .ogg files to be solely
+ Vorbis-encoded audio.
Macintosh File Type Code(s): OggX
@@ -439,16 +441,17 @@
in situations where it is not appropriate to serve data under the
video/ogg or audio/ogg types. Data served under the application/ogg
type SHOULD use the .ogx file extension and MUST contain an Ogg
- Skeleton logical bitstream to identify all other contained logical
- bitstreams.
-Goncalves, et al. Expires November 27, 2008 [Page 8]
+Goncalves, et al. Expires December 4, 2008 [Page 8]
-Internet-Draft Ogg Media Types May 2008
+Internet-Draft Ogg Media Types June 2008
+ Skeleton logical bitstream to identify all other contained logical
+ bitstreams.
+
Author: See "Authors' Addresses" section.
Change controller: The Xiph.Org Foundation.
@@ -461,13 +464,15 @@
Required parameters: none
- Optional parameters: codecs, as defined in RFC 4281.
+ Optional parameters: codecs, whose syntax is defined in RFC 4281.
+ See section 4 of RFC XXXX for a list of allowed values.
- Encoding considerations: See section 6.
+ Encoding considerations: See section 6 of RFC XXXX.
- Security considerations: See section 7.
+ Security considerations: See section 7 of RFC XXXX.
- Interoperability considerations: None, as noted in section 8.
+ Interoperability considerations: None, as noted in section 8 of RFC
+ XXXX.
Published specification: RFC 3533
@@ -492,19 +497,20 @@
bitstreams containing visual, audio, timed text, or any other type of
material that requires a visual interface. It is intended for
content not complex enough to warrant serving under "application/
+
+
+
+Goncalves, et al. Expires December 4, 2008 [Page 9]
+
+Internet-Draft Ogg Media Types June 2008
+
+
ogg"; for example, a combination of Theora video, Vorbis audio,
Skeleton metadata, and CMML captioning. Data served under the type
"video/ogg" SHOULD contain an Ogg Skeleton logical bitstream.
Implementations interacting with the type "video/ogg" SHOULD support
multiplexed bitstreams.
-
-
-Goncalves, et al. Expires November 27, 2008 [Page 9]
-
-Internet-Draft Ogg Media Types May 2008
-
-
Author: See "Authors' Addresses" section.
Change controller: The Xiph.Org Foundation.
@@ -517,13 +523,15 @@
Required parameters: none
- Optional parameters: codecs, as defined in RFC 4281.
+ Optional parameters: codecs, whose syntax is defined in RFC 4281.
+ See section 4 of RFC XXXX for a list of allowed values.
- Encoding considerations: See section 6.
+ Encoding considerations: See section 6 of RFC XXXX.
- Security considerations: See section 7.
+ Security considerations: See section 7 of RFC XXXX.
- Interoperability considerations: None, as noted in section 8.
+ Interoperability considerations: None, as noted in section 8 of RFC
+ XXXX.
Published specification: RFC 3533
@@ -545,6 +553,14 @@
Intended usage: COMMON
Restrictions on usage: The type "audio/ogg" SHOULD be used when the
+
+
+
+Goncalves, et al. Expires December 4, 2008 [Page 10]
+
+Internet-Draft Ogg Media Types June 2008
+
+
Ogg bitstream predominantly contains audio data. Content served
under the "audio/ogg" type SHOULD have an Ogg Skeleton logical
bitstream when using the default .oga file extension. The .ogg and
@@ -554,32 +570,27 @@
contain only a Vorbis bitstream, while .spx is used for Ogg files
that contain only a Speex bitstream.
+ Author: See "Authors' Addresses" section.
+ Change controller: The Xiph.Org Foundation.
-Goncalves, et al. Expires November 27, 2008 [Page 10]
-
-Internet-Draft Ogg Media Types May 2008
+11. Acknowledgements
+ The authors gratefully acknowledge the contributions of Magnus
+ Westerlund, Alfred Hoenes, and Peter Saint-Andre.
- Author: See "Authors' Addresses" section.
+12. Copying Conditions
- Change controller: The Xiph.Org Foundation.
-
-11. Copying Conditions
-
The authors agree to grant third parties the irrevocable right to
copy, use and distribute the work, with or without modification, in
any medium, without royalty, provided that, unless separate
permission is granted, redistributed modified works do not contain
misleading author, version, name of work, or endorsement information.
-12. References
+13. References
-12.1. Normative References
+13.1. Normative References
- [RFC3533] Pfeiffer, S., "The Ogg Encapsulation Format Version 0",
- RFC 3533, May 2003.
-
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, November 1996.
@@ -587,6 +598,9 @@
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
+ [RFC3533] Pfeiffer, S., "The Ogg Encapsulation Format Version 0",
+ RFC 3533, May 2003.
+
[RFC4281] Gellens, R., Singer, D., and P. Frojdh, "The Codecs
Parameter for "Bucket" Media Types", RFC 4281,
November 2005.
@@ -595,84 +609,79 @@
Registration Procedures", BCP 13, RFC 4288,
December 2005.
-12.2. Informative References
- [Ogg] Xiph.Org Foundation, "Ogg bitstream documentation: Ogg
- logical and physical bitstream overview, Ogg logical
- bitstream framing, Ogg multi-stream multiplexing",
- <http://xiph.org/ogg/doc>.
- [RFC3534] Walleij, L., "The application/ogg Media Type", RFC 3534,
- May 2003.
- [Theora] Xiph.Org Foundation, "Theora Specification",
- October 2007, <http://theora.org/doc/Theora_spec.pdf>.
-
- [Dirac] Dirac Group, "Dirac Specification",
-
-
-
-Goncalves, et al. Expires November 27, 2008 [Page 11]
+Goncalves, et al. Expires December 4, 2008 [Page 11]
-Internet-Draft Ogg Media Types May 2008
+Internet-Draft Ogg Media Types June 2008
- <http://dirac.sourceforge.net/specification.html>.
+13.2. Informative References
- [Speex] Valin, J., "The Speex Codec Manual", February 2002,
- <http://speex.org/docs/manual/speex-manual>.
-
- [Vorbis] Xiph.Org Foundation, "Vorbis I Specification", July 2004,
- <http://xiph.org/vorbis/doc/Vorbis_I_spec.html>.
-
- [FLAC] Coalson, J., "The FLAC Format",
- <http://flac.sourceforge.net/format.html>.
-
[CMML] Pfeiffer, S., Parker, C., and A. Pang, "The Continuous
Media Markup Language (CMML)", March 2006,
<http://annodex.net/TR/cmml.txt>.
- [Skeleton] Pfeiffer, S. and C. Parker, "The Ogg Skeleton Metadata
- Bitstream", November 2007,
- <http://xiph.org/ogg/doc/skeleton.html>.
+ [Dirac] Dirac Group, "Dirac Specification",
+ <http://dirac.sourceforge.net/specification.html>.
- [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data
- Encodings", RFC 4648, October 2006.
+ [FLAC] Coalson, J., "The FLAC Format",
+ <http://flac.sourceforge.net/format.html>.
- [ThRTP] Barbato, L., "RTP Payload Format for Theora Encoded
- Video", July 2006,
- <http://tools.ietf.org/html/
- draft-barbato-avt-rtp-theora>.
+ [libogg] Xiph.Org Foundation, "The libogg API", June 2000,
+ <http://xiph.org/ogg/doc/libogg>.
- [VoRTP] Barbato, L., "RTP Payload Format for Vorbis Encoded
- Audio", November 2007,
- <http://tools.ietf.org/html/draft-ietf-avt-rtp-vorbis>.
+ [Ogg] Xiph.Org Foundation, "Ogg bitstream documentation: Ogg
+ logical and physical bitstream overview, Ogg logical
+ bitstream framing, Ogg multi-stream multiplexing",
+ <http://xiph.org/ogg/doc>.
- [SpRTP] Herlein, G., Valin, J., Heggestad, A., and A. Moizard,
- "RTP Payload Format for the Speex Codec", July 2007,
- <http://tools.ietf.org/html/draft-ietf-avt-rtp-speex>.
+ [RFC3534] Walleij, L., "The application/ogg Media Type", RFC 3534,
+ May 2003.
[RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC
Text on Security Considerations", BCP 72, RFC 3552,
July 2003.
- [libogg] Xiph.Org Foundation, "The libogg API", June 2000,
- <http://xiph.org/ogg/doc/libogg>.
+ [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data
+ Encodings", RFC 4648, October 2006.
+ [Skeleton] Pfeiffer, S. and C. Parker, "The Ogg Skeleton Metadata
+ Bitstream", November 2007,
+ <http://xiph.org/ogg/doc/skeleton.html>.
+ [Speex] Valin, J., "The Speex Codec Manual", February 2002,
+ <http://speex.org/docs/manual/speex-manual>.
+ [SpRTP] Herlein, G., Valin, J., Heggestad, A., and A. Moizard,
+ "RTP Payload Format for the Speex Codec", Work in
+ Progress , July 2007,
+ <http://tools.ietf.org/html/draft-ietf-avt-rtp-speex>.
+ [Theora] Xiph.Org Foundation, "Theora Specification",
+ October 2007, <http://theora.org/doc/Theora_spec.pdf>.
+ [ThRTP] Barbato, L., "RTP Payload Format for Theora Encoded
+ Video", Work in Progress , July 2006,
+ <http://tools.ietf.org/html/
+Goncalves, et al. Expires December 4, 2008 [Page 12]
+
+Internet-Draft Ogg Media Types June 2008
-Goncalves, et al. Expires November 27, 2008 [Page 12]
-
-Internet-Draft Ogg Media Types May 2008
+ draft-barbato-avt-rtp-theora>.
+ [Vorbis] Xiph.Org Foundation, "Vorbis I Specification", July 2004,
+ <http://xiph.org/vorbis/doc/Vorbis_I_spec.html>.
+ [VoRTP] Barbato, L., "RTP Payload Format for Vorbis Encoded
+ Audio", Work in Progress , November 2007,
+ <http://tools.ietf.org/html/draft-ietf-avt-rtp-vorbis>.
+
Authors' Addresses
Ivo Emanuel Goncalves
@@ -715,18 +724,9 @@
-
-
-
-
-
-
-
-
-
-Goncalves, et al. Expires November 27, 2008 [Page 13]
+Goncalves, et al. Expires December 4, 2008 [Page 13]
-Internet-Draft Ogg Media Types May 2008
+Internet-Draft Ogg Media Types June 2008
Full Copyright Statement
@@ -780,5 +780,5 @@
-Goncalves, et al. Expires November 27, 2008 [Page 14]
+Goncalves, et al. Expires December 4, 2008 [Page 14]
Modified: trunk/standards/draft-goncalves-rfc3534bis.xml
===================================================================
--- trunk/standards/draft-goncalves-rfc3534bis.xml 2008-06-02 18:27:04 UTC (rev 14989)
+++ trunk/standards/draft-goncalves-rfc3534bis.xml 2008-06-02 18:28:27 UTC (rev 14990)
@@ -6,7 +6,7 @@
<?rfc symrefs="yes" ?>
<?rfc rfcedstyle="yes" ?>
-<rfc ipr="full3978" docName="draft-goncalves-rfc3534bis-06" obsoletes="3534" category="std" submissionType="IETF" xml:lang="en">
+<rfc ipr="full3978" docName="draft-goncalves-rfc3534bis-07" obsoletes="3534" category="std" submissionType="IETF" xml:lang="en">
<front>
<title>Ogg Media Types</title>
<author initials="I.E." surname="Goncalves" fullname="Ivo Emanuel Goncalves">
@@ -37,7 +37,7 @@
<uri>http://xiph.org</uri>
</address>
</author>
- <date day="26" month="May" year="2008"/>
+ <date day="2" month="June" year="2008"/>
<area>Internet</area>
<keyword>I-D</keyword>
<keyword>Internet-Draft</keyword>
@@ -54,7 +54,7 @@
<section title="Introduction">
<t>This document describes media types for Ogg, a data encapsulation format defined by the Xiph.Org Foundation for public use. Refer to "Introduction" in <xref target="RFC3533"/> and "Overview" in <xref target="Ogg"/> for background information on this container format.</t>
<t>Binary data contained in Ogg, such as Vorbis and Theora, has historically been interchanged using the application/ogg media type as defined by <xref target="RFC3534"/>. This document obsoletes <xref target="RFC3534"/> and defines three media types for different types of content in Ogg to reflect this usage in the IANA media type registry, to foster interoperability by defining underspecified aspects, and to provide general security considerations.</t>
- <t>The Ogg container format is known to contain <xref target="Theora"/> or <xref target="Dirac"/> video, <xref target="Speex"/> (narrow-band and wide-band speech), <xref target="Vorbis"/> or <xref target="FLAC"/> audio, and <xref target="CMML"/> timed text/metadata. As Ogg encapsulates binary data, it is possible to include any other type of video, audio, image, text or, generally speaking, any time-continuously sampled data.</t>
+ <t>The Ogg container format is known to contain <xref target="Theora"/> or <xref target="Dirac"/> video, <xref target="Speex"/> (narrow-band and wide-band) speech, <xref target="Vorbis"/> or <xref target="FLAC"/> audio, and <xref target="CMML"/> timed text/metadata. As Ogg encapsulates binary data, it is possible to include any other type of video, audio, image, text or, generally speaking, any time-continuously sampled data.</t>
<t>While raw packets from these data sources may be used directly by transport mechanisms that provide their own framing and packet-separation mechanisms (such as UDP datagrams or RTP), Ogg is a solution for stream based storage (such as files) and transport (such as TCP streams or pipes). The media types defined in this document are needed to correctly identify such content when it is served over HTTP, included in multi-part documents, or used in other places where <xref target="RFC2045">media types</xref> are used.</t>
</section>
<section title="Changes Since RFC 3534">
@@ -86,7 +86,7 @@
<t>which are intended for common use and SHOULD be used when dealing with video or audio content respectively. This document also obsoletes the <xref target="RFC3534"/> definition of application/ogg and marks it for complex data (e.g. multitrack visual, audio, textual and other time-continuously sampled data), which is not clearly video or audio data and thus not suited for either the video/ogg or audio/ogg types. Refer to the following section for more details.</t>
<t>An Ogg bitstream generally consists of one or more logical bitstreams that each consist of a series of header and data pages packetising time-continuous binary data <xref target="RFC3533"/>. The content types of the logical bitstreams may be identified without decoding the header pages of the logical bitstreams through use of a <xref target="Skeleton"/> bitstream. Using Ogg Skeleton is REQUIRED for content served under the application/ogg type and RECOMMENDED for video/ogg and audio/ogg, as Skeleton contains identifiers to describe the different encapsulated data.</t>
<t>Furthermore, it is RECOMMENDED that implementations that identify a logical bitstream which they cannot decode SHOULD ignore it, while continuing to decode the ones they can. Such precaution ensures backward and forward compatibility with existing and future data.</t>
- <t>These media types can optionally use the "codecs" parameter described in <xref target="RFC4281"/>. Codecs encapsulated in Ogg require an 8 byte text identifier at the beginning of the first header page, hence a possible machine-readable method to identify the encapsulated codecs would be through this header. The following table illustrates how those header values map into strings that SHOULD be used in the "codecs" parameter when dealing with Ogg media types.</t>
+ <t>These media types can optionally use the "codecs" parameter described in <xref target="RFC4281"/>. Codecs encapsulated in Ogg require a text identifier at the beginning of the first header page, hence a machine-readable method to identify the encapsulated codecs would be through this header. The following table illustrates how those header values map into strings that are used in the "codecs" parameter when dealing with Ogg media types.</t>
<figure>
<artwork><![CDATA[
Codec Identifier | Codecs Parameter
@@ -152,17 +152,17 @@
<t>Type name: application</t>
<t>Subtype name: ogg</t>
<t>Required parameters: none</t>
- <t>Optional parameters: codecs, as defined in RFC 4281.</t>
- <t>Encoding considerations: See section 6.</t>
- <t>Security considerations: See section 7.</t>
- <t>Interoperability considerations: None, as noted in section 8.</t>
+ <t>Optional parameters: codecs, whose syntax is defined in RFC 4281. See section 4 of RFC &rfc.number; for a list of allowed values.</t>
+ <t>Encoding considerations: See section 6 of RFC &rfc.number;.</t>
+ <t>Security considerations: See section 7 of RFC &rfc.number;.</t>
+ <t>Interoperability considerations: None, as noted in section 8 of RFC &rfc.number;.</t>
<t>Published specification: RFC 3533</t>
<t>Applications which use this media type: Scientific and otherwise which require various multiplexed signals or streams of data, with or without scriptable control of content.</t>
<t>Additional information:</t>
<t>Magic number(s): The first four bytes, 0x4f 0x67 0x67 0x53, correspond to the string "OggS".</t>
<t>File extension(s): .ogx</t>
<list style="hanging">
- <t>RFC 3534 defined the file extension .ogg for application/ogg, which this document obsoletes in favor of .ogx due to concerns where, historically, some implementations expect .ogg files to be solely Vorbis-encoded audio.</t>
+ <t>RFC 3534 defined the file extension .ogg for application/ogg, which RFC &rfc.number; obsoletes in favor of .ogx due to concerns where, historically, some implementations expect .ogg files to be solely Vorbis-encoded audio.</t>
</list>
<t>Macintosh File Type Code(s): OggX</t>
<t>Person & Email address to contact for further information: See "Authors' Addresses" section.</t>
@@ -175,10 +175,10 @@
<t>Type name: video</t>
<t>Subtype name: ogg</t>
<t>Required parameters: none</t>
- <t>Optional parameters: codecs, as defined in RFC 4281.</t>
- <t>Encoding considerations: See section 6.</t>
- <t>Security considerations: See section 7.</t>
- <t>Interoperability considerations: None, as noted in section 8.</t>
+ <t>Optional parameters: codecs, whose syntax is defined in RFC 4281. See section 4 of RFC &rfc.number; for a list of allowed values.</t>
+ <t>Encoding considerations: See section 6 of RFC &rfc.number;.</t>
+ <t>Security considerations: See section 7 of RFC &rfc.number;.</t>
+ <t>Interoperability considerations: None, as noted in section 8 of RFC &rfc.number;.</t>
<t>Published specification: RFC 3533</t>
<t>Applications which use this media type: Multimedia applications, including embedded, streaming, and conferencing tools.</t>
<t>Additional information:</t>
@@ -195,10 +195,10 @@
<t>Type name: audio</t>
<t>Subtype name: ogg</t>
<t>Required parameters: none</t>
- <t>Optional parameters: codecs, as defined in RFC 4281.</t>
- <t>Encoding considerations: See section 6.</t>
- <t>Security considerations: See section 7.</t>
- <t>Interoperability considerations: None, as noted in section 8.</t>
+ <t>Optional parameters: codecs, whose syntax is defined in RFC 4281. See section 4 of RFC &rfc.number; for a list of allowed values.</t>
+ <t>Encoding considerations: See section 6 of RFC &rfc.number;.</t>
+ <t>Security considerations: See section 7 of RFC &rfc.number;.</t>
+ <t>Interoperability considerations: None, as noted in section 8 of RFC &rfc.number;.</t>
<t>Published specification: RFC 3533</t>
<t>Applications which use this media type: Multimedia applications, including embedded, streaming, and conferencing tools.</t>
<t>Additional information:</t>
@@ -212,22 +212,15 @@
<t>Change controller: The Xiph.Org Foundation.</t>
</section>
</section>
+ <section title="Acknowledgements">
+ <t>The authors gratefully acknowledge the contributions of Magnus Westerlund, Alfred Hoenes, and Peter Saint-Andre.</t>
+ </section>
<section title="Copying Conditions">
<t>The authors agree to grant third parties the irrevocable right to copy, use and distribute the work, with or without modification, in any medium, without royalty, provided that, unless separate permission is granted, redistributed modified works do not contain misleading author, version, name of work, or endorsement information.</t>
</section>
</middle>
<back>
<references title="Normative References">
- <reference anchor="RFC3533">
- <front>
- <title>The Ogg Encapsulation Format Version 0</title>
- <author initials="S." surname="Pfeiffer" fullname="Silvia Pfeiffer">
- <organization abbrev="Xiph">Xiph.Org Foundation</organization>
- </author>
- <date month="May" year="2003"/>
- </front>
- <seriesInfo name="RFC" value="3533"/>
- </reference>
<reference anchor="RFC2045">
<front>
<title>Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
@@ -251,6 +244,16 @@
<seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="2119"/>
</reference>
+ <reference anchor="RFC3533">
+ <front>
+ <title>The Ogg Encapsulation Format Version 0</title>
+ <author initials="S." surname="Pfeiffer" fullname="Silvia Pfeiffer">
+ <organization abbrev="Xiph">Xiph.Org Foundation</organization>
+ </author>
+ <date month="May" year="2003"/>
+ </front>
+ <seriesInfo name="RFC" value="3533"/>
+ </reference>
<reference anchor="RFC4281">
<front>
<title>The Codecs Parameter for "Bucket" Media Types</title>
@@ -281,31 +284,19 @@
</reference>
</references>
<references title="Informative References">
- <reference anchor="Ogg" target="http://xiph.org/ogg/doc">
+ <reference anchor="CMML" target="http://annodex.net/TR/cmml.txt">
<front>
- <title>Ogg bitstream documentation: Ogg logical and physical bitstream overview, Ogg logical bitstream framing, Ogg multi-stream multiplexing</title>
- <author>
- <organization abbrev="Xiph">Xiph.Org Foundation</organization>
+ <title>The Continuous Media Markup Language (CMML)</title>
+ <author initials="S." surname="Pfeiffer" fullname="Silvia Pfeiffer">
+ <organization abbrev="CSIRO">Commonwealth Scientific and Industrial Research Organisation</organization>
</author>
- </front>
- </reference>
- <reference anchor="RFC3534">
- <front>
- <title>The application/ogg Media Type</title>
- <author initials="L." surname="Walleij" fullname="Linus Walleij">
- <organization abbrev="Xiph">Xiph.Org Foundation</organization>
+ <author initials="C.D." surname="Parker" fullname="Conrad D. Parker">
+ <organization abbrev="CSIRO">Commonwealth Scientific and Industrial Research Organisation</organization>
</author>
- <date month="May" year="2003"/>
- </front>
- <seriesInfo name="RFC" value="3534"/>
- </reference>
- <reference anchor="Theora" target="http://theora.org/doc/Theora_spec.pdf">
- <front>
- <title>Theora Specification</title>
- <author>
- <organization abbrev="Xiph">Xiph.Org Foundation</organization>
+ <author initials="A.T." surname="Pang" fullname="Andre T. Pang">
+ <organization abbrev="CSIRO">Commonwealth Scientific and Industrial Research Organisation</organization>
</author>
- <date month="October" year="2007"/>
+ <date month="March" year="2006"/>
</front>
</reference>
<reference anchor="Dirac" target="http://dirac.sourceforge.net/specification.html">
@@ -316,58 +307,54 @@
</author>
</front>
</reference>
- <reference anchor="Speex" target="http://speex.org/docs/manual/speex-manual">
+ <reference anchor="FLAC" target="http://flac.sourceforge.net/format.html">
<front>
- <title>The Speex Codec Manual</title>
- <author initials="J." surname="Valin" fullname="Jean-Marc Valin">
+ <title>The FLAC Format</title>
+ <author initials="J." surname="Coalson" fullname="Josh Coalson">
<organization abbrev="Xiph">Xiph.Org Foundation</organization>
</author>
- <date month="February" year="2002"/>
</front>
</reference>
- <reference anchor="Vorbis" target="http://xiph.org/vorbis/doc/Vorbis_I_spec.html">
+ <reference anchor="libogg" target="http://xiph.org/ogg/doc/libogg">
<front>
- <title>Vorbis I Specification</title>
+ <title>The libogg API</title>
<author>
<organization abbrev="Xiph">Xiph.Org Foundation</organization>
</author>
- <date month="July" year="2004"/>
+ <date month="June" year="2000"/>
</front>
</reference>
- <reference anchor="FLAC" target="http://flac.sourceforge.net/format.html">
+ <reference anchor="Ogg" target="http://xiph.org/ogg/doc">
<front>
- <title>The FLAC Format</title>
- <author initials="J." surname="Coalson" fullname="Josh Coalson">
+ <title>Ogg bitstream documentation: Ogg logical and physical bitstream overview, Ogg logical bitstream framing, Ogg multi-stream multiplexing</title>
+ <author>
<organization abbrev="Xiph">Xiph.Org Foundation</organization>
</author>
</front>
</reference>
- <reference anchor="CMML" target="http://annodex.net/TR/cmml.txt">
+ <reference anchor="RFC3534">
<front>
- <title>The Continuous Media Markup Language (CMML)</title>
- <author initials="S." surname="Pfeiffer" fullname="Silvia Pfeiffer">
- <organization abbrev="CSIRO">Commonwealth Scientific and Industrial Research Organisation</organization>
+ <title>The application/ogg Media Type</title>
+ <author initials="L." surname="Walleij" fullname="Linus Walleij">
+ <organization abbrev="Xiph">Xiph.Org Foundation</organization>
</author>
- <author initials="C.D." surname="Parker" fullname="Conrad D. Parker">
- <organization abbrev="CSIRO">Commonwealth Scientific and Industrial Research Organisation</organization>
- </author>
- <author initials="A.T." surname="Pang" fullname="Andre T. Pang">
- <organization abbrev="CSIRO">Commonwealth Scientific and Industrial Research Organisation</organization>
- </author>
- <date month="March" year="2006"/>
+ <date month="May" year="2003"/>
</front>
+ <seriesInfo name="RFC" value="3534"/>
</reference>
- <reference anchor="Skeleton" target="http://xiph.org/ogg/doc/skeleton.html">
+ <reference anchor="RFC3552">
<front>
- <title>The Ogg Skeleton Metadata Bitstream</title>
- <author initials="S." surname="Pfeiffer" fullname="Silvia Pfeiffer">
- <organization abbrev="Xiph">Xiph.Org Foundation</organization>
+ <title>Guidelines for Writing RFC Text on Security Considerations</title>
+ <author initials="E." surname="Rescorla" fullname="Eric Rescorla">
+ <organization>RTFM, Inc.</organization>
</author>
- <author initials="C.D." surname="Parker" fullname="Conrad D. Parker">
- <organization abbrev="Xiph">Xiph.Org Foundation</organization>
+ <author initials="B." surname="Korver" fullname="Brian Korver">
+ <organization>Xythos Software, Inc.</organization>
</author>
- <date month="November" year="2007"/>
+ <date month="July" year="2003"/>
</front>
+ <seriesInfo name="BCP" value="72"/>
+ <seriesInfo name="RFC" value="3552"/>
</reference>
<reference anchor="RFC4648">
<front>
@@ -379,22 +366,25 @@
</front>
<seriesInfo name="RFC" value="4648"/>
</reference>
- <reference anchor="ThRTP" target="http://tools.ietf.org/html/draft-barbato-avt-rtp-theora">
+ <reference anchor="Skeleton" target="http://xiph.org/ogg/doc/skeleton.html">
<front>
- <title>RTP Payload Format for Theora Encoded Video</title>
- <author initials="L." surname="Barbato" fullname="Luca Barbato">
+ <title>The Ogg Skeleton Metadata Bitstream</title>
+ <author initials="S." surname="Pfeiffer" fullname="Silvia Pfeiffer">
<organization abbrev="Xiph">Xiph.Org Foundation</organization>
</author>
- <date month="July" year="2006"/>
+ <author initials="C.D." surname="Parker" fullname="Conrad D. Parker">
+ <organization abbrev="Xiph">Xiph.Org Foundation</organization>
+ </author>
+ <date month="November" year="2007"/>
</front>
</reference>
- <reference anchor="VoRTP" target="http://tools.ietf.org/html/draft-ietf-avt-rtp-vorbis">
+ <reference anchor="Speex" target="http://speex.org/docs/manual/speex-manual">
<front>
- <title>RTP Payload Format for Vorbis Encoded Audio</title>
- <author initials="L." surname="Barbato" fullname="Luca Barbato">
+ <title>The Speex Codec Manual</title>
+ <author initials="J." surname="Valin" fullname="Jean-Marc Valin">
<organization abbrev="Xiph">Xiph.Org Foundation</organization>
</author>
- <date month="November" year="2007"/>
+ <date month="February" year="2002"/>
</front>
</reference>
<reference anchor="SpRTP" target="http://tools.ietf.org/html/draft-ietf-avt-rtp-speex">
@@ -411,30 +401,46 @@
</author>
<date month="July" year="2007"/>
</front>
+ <seriesInfo name="Work in Progress" value=""/>
</reference>
- <reference anchor="RFC3552">
+ <reference anchor="Theora" target="http://theora.org/doc/Theora_spec.pdf">
<front>
- <title>Guidelines for Writing RFC Text on Security Considerations</title>
- <author initials="E." surname="Rescorla" fullname="Eric Rescorla">
- <organization>RTFM, Inc.</organization>
+ <title>Theora Specification</title>
+ <author>
+ <organization abbrev="Xiph">Xiph.Org Foundation</organization>
</author>
- <author initials="B." surname="Korver" fullname="Brian Korver">
- <organization>Xythos Software, Inc.</organization>
+ <date month="October" year="2007"/>
+ </front>
+ </reference>
+ <reference anchor="ThRTP" target="http://tools.ietf.org/html/draft-barbato-avt-rtp-theora">
+ <front>
+ <title>RTP Payload Format for Theora Encoded Video</title>
+ <author initials="L." surname="Barbato" fullname="Luca Barbato">
+ <organization abbrev="Xiph">Xiph.Org Foundation</organization>
</author>
- <date month="July" year="2003"/>
+ <date month="July" year="2006"/>
</front>
- <seriesInfo name="BCP" value="72"/>
- <seriesInfo name="RFC" value="3552"/>
+ <seriesInfo name="Work in Progress" value=""/>
</reference>
- <reference anchor="libogg" target="http://xiph.org/ogg/doc/libogg">
+ <reference anchor="Vorbis" target="http://xiph.org/vorbis/doc/Vorbis_I_spec.html">
<front>
- <title>The libogg API</title>
+ <title>Vorbis I Specification</title>
<author>
<organization abbrev="Xiph">Xiph.Org Foundation</organization>
</author>
- <date month="June" year="2000"/>
+ <date month="July" year="2004"/>
</front>
</reference>
+ <reference anchor="VoRTP" target="http://tools.ietf.org/html/draft-ietf-avt-rtp-vorbis">
+ <front>
+ <title>RTP Payload Format for Vorbis Encoded Audio</title>
+ <author initials="L." surname="Barbato" fullname="Luca Barbato">
+ <organization abbrev="Xiph">Xiph.Org Foundation</organization>
+ </author>
+ <date month="November" year="2007"/>
+ </front>
+ <seriesInfo name="Work in Progress" value=""/>
+ </reference>
</references>
</back>
</rfc>
\ No newline at end of file
More information about the commits
mailing list