[xiph-commits] r14780 - trunk/standards
silvia at svn.xiph.org
silvia at svn.xiph.org
Sun Apr 20 06:36:19 PDT 2008
Author: silvia
Date: 2008-04-20 06:36:18 -0700 (Sun, 20 Apr 2008)
New Revision: 14780
Modified:
trunk/standards/draft-goncalves-rfc3534bis.txt
trunk/standards/draft-goncalves-rfc3534bis.xml
Log:
changed typo of rfc3543 to rfc3534 and made further small textual changes
Modified: trunk/standards/draft-goncalves-rfc3534bis.txt
===================================================================
--- trunk/standards/draft-goncalves-rfc3534bis.txt 2008-04-19 13:38:11 UTC (rev 14779)
+++ trunk/standards/draft-goncalves-rfc3534bis.txt 2008-04-20 13:36:18 UTC (rev 14780)
@@ -36,10 +36,6 @@
This Internet-Draft will expire on October 21, 2008.
-Copyright Notice
-
- Copyright (C) The IETF Trust (2008).
-
Abstract
This document describes the registration of media types for the Ogg
@@ -52,6 +48,10 @@
+
+
+
+
Goncalves, et al. Expires October 21, 2008 [Page 1]
Internet-Draft Ogg Media Types April 2008
@@ -60,8 +60,8 @@
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3
- 2. Changes since RFC 3543 . . . . . . . . . . . . . . . . . . 3
- 3. Conformance and Document Conventions . . . . . . . . . . . 3
+ 2. Changes since RFC 3534 . . . . . . . . . . . . . . . . . . 3
+ 3. Conformance and Document Conventions . . . . . . . . . . . 4
4. Deployed Media Types and Compatibility . . . . . . . . . . 4
5. Relation Between the Media Types . . . . . . . . . . . . . 5
6. Encoding Considerations . . . . . . . . . . . . . . . . . . 5
@@ -73,8 +73,8 @@
10.2. video/ogg . . . . . . . . . . . . . . . . . . . . . . . . . 8
10.3. audio/ogg . . . . . . . . . . . . . . . . . . . . . . . . . 9
11. Copying Conditions . . . . . . . . . . . . . . . . . . . . 10
- 12. References . . . . . . . . . . . . . . . . . . . . . . . . 10
- 12.1. Normative References . . . . . . . . . . . . . . . . . . . 10
+ 12. References . . . . . . . . . . . . . . . . . . . . . . . . 11
+ 12.1. Normative References . . . . . . . . . . . . . . . . . . . 11
12.2. Informative References . . . . . . . . . . . . . . . . . . 11
@@ -144,31 +144,39 @@
HTTP, included in multi-part documents, or used in other places where
media types [RFC2045] are used.
-2. Changes since RFC 3543
+2. Changes since RFC 3534
o The type "application/ogg" is redefined.
+
o The types "video/ogg" and "audio/ogg" are defined.
+
o New file extensions are defined.
+
o New Macintosh file type codes are defined.
+
o The codecs parameter is defined for optional use.
+
o The Ogg Skeleton extension becomes a recommended addition for
content served under the new types.
-3. Conformance and Document Conventions
- 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 BCP 14, [RFC2119] and
- indicate requirement levels for compliant implementations.
- Requirements apply to all implementations unless otherwise stated.
+
Goncalves, et al. Expires October 21, 2008 [Page 3]
Internet-Draft Ogg Media Types April 2008
+3. Conformance and Document Conventions
+
+ 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 BCP 14, [RFC2119] and
+ indicate requirement levels for compliant implementations.
+ Requirements apply to all implementations unless otherwise stated.
+
An implementation is a software module that supports one of the media
types defined in this document. Software modules may support
multiple media types, but conformance is considered individually for
@@ -190,6 +198,7 @@
audio content. This document thus defines the media types,
o video/ogg
+
o audio/ogg
which are intended for common use and SHOULD be used when dealing
@@ -207,7 +216,15 @@
pages of the logical bitstreams through use of a [Skeleton]
bitstream. Using Ogg Skeleton is REQUIRED for content served under
the application/ogg type and RECOMMENDED for video/ogg and audio/ogg,
- as it is a type of identifier space used to describe the different
+ as Skeleton contains identifiers to describe the different
+
+
+
+Goncalves, et al. Expires October 21, 2008 [Page 4]
+
+Internet-Draft Ogg Media Types April 2008
+
+
encapsulated data.
Furthermore, it is RECOMMENDED that implementations that identify a
@@ -218,22 +235,17 @@
These media types can optionally use the codecs parameter described
in [RFC4281]. Possible examples include:
+ o application/ogg; codecs="theora, cmml, ecmascript"
+ o video/ogg; codecs="theora, vorbis"
-Goncalves, et al. Expires October 21, 2008 [Page 4]
-
-Internet-Draft Ogg Media Types April 2008
-
-
- o application/ogg; codecs="theora, cmml, ecmascript"
- o video/ogg; codecs="theora, vorbis"
o audio/ogg; codecs=speex
5. Relation Between the Media Types
As stated in the previous section, this document describes three
media types which are targeted at different data encapsulated in Ogg.
- Since Ogg is capable of encapsulate any kind of data, the multiple
+ Since Ogg is capable of encapsulating any kind of data, the multiple
usage scenarios have revealed interoperability issues between
implementations when dealing with content served solely under the
application/ogg type.
@@ -261,26 +273,29 @@
Binary: The content consists of an unrestricted sequence of octets.
+
+
+
+Goncalves, et al. Expires October 21, 2008 [Page 5]
+
+Internet-Draft Ogg Media Types April 2008
+
+
Note:
+
o Ogg encapsulated content is binary data and should be transmitted
in a suitable encoding without CR/LF conversion, 7-bit stripping,
etc.; base64 [RFC4648] is generally preferred for binary-to-text
encoding.
+
o Media types described in this document are used for stream based
storage (such as files) and transport (such as TCP streams or
- pipes); separate types are used for real-time transfer, such as
- for the RTP payload formats of Theora [ThRTP] video, and Vorbis
- [VoRTP] or Speex [SpRTP] audio, as well as for identification of
- the encapsulated data within Ogg.
+ pipes); separate types are used to identify codecs such as in
+ real-time applications for the RTP payload formats of Theora
+ [ThRTP] video, and Vorbis [VoRTP] or Speex [SpRTP] audio. These
+ mime types are also used in Skeleton for identification of the
+ encapsulated data within Ogg.
-
-
-
-Goncalves, et al. Expires October 21, 2008 [Page 5]
-
-Internet-Draft Ogg Media Types April 2008
-
-
7. Security Considerations
Refer to [RFC3552] for a discussion of terminology used in this
@@ -314,6 +329,14 @@
kind of attack.
Ogg has an extensible structure, so that it is theoretically possible
+
+
+
+Goncalves, et al. Expires October 21, 2008 [Page 6]
+
+Internet-Draft Ogg Media Types April 2008
+
+
that metadata fields or media formats might be defined in the future
which might be used to induce particular actions on the part of the
recipient, thus presenting additional security risks. However, this
@@ -326,17 +349,6 @@
or sensitive information; such failure constitutes an unknown factor
and is thus considered out of the scope of this document.
-
-
-
-
-
-
-Goncalves, et al. Expires October 21, 2008 [Page 6]
-
-Internet-Draft Ogg Media Types April 2008
-
-
8. Interoperability Considerations
The Ogg container format is device-, platform- and vendor-neutral and
@@ -373,6 +385,14 @@
Encoding considerations: See section 6.
+
+
+
+Goncalves, et al. Expires October 21, 2008 [Page 7]
+
+Internet-Draft Ogg Media Types April 2008
+
+
Security considerations: See section 7.
Interoperability considerations: None, as noted in section 8.
@@ -385,18 +405,11 @@
Additional information:
-
-
-
-Goncalves, et al. Expires October 21, 2008 [Page 7]
-
-Internet-Draft Ogg Media Types April 2008
-
-
Magic number(s): The first four bytes, 0x4f 0x67 0x67 0x53,
correspond to the string "OggS".
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
@@ -428,6 +441,14 @@
Required parameters: none
+
+
+
+Goncalves, et al. Expires October 21, 2008 [Page 8]
+
+Internet-Draft Ogg Media Types April 2008
+
+
Optional parameters: codecs, as defined in RFC 4281.
Encoding considerations: See section 6.
@@ -441,14 +462,6 @@
Applications which use this media type: Multimedia applications,
including embedded, streaming, and conferencing tools.
-
-
-
-Goncalves, et al. Expires October 21, 2008 [Page 8]
-
-Internet-Draft Ogg Media Types April 2008
-
-
Additional information:
Magic number(s): The first four bytes, 0x4f 0x67 0x67 0x53,
@@ -485,6 +498,13 @@
Required parameters: none
+
+
+Goncalves, et al. Expires October 21, 2008 [Page 9]
+
+Internet-Draft Ogg Media Types April 2008
+
+
Optional parameters: codecs, as defined in RFC 4281.
Encoding considerations: See section 6.
@@ -498,13 +518,6 @@
Applications which use this media type: Multimedia applications,
including embedded, streaming, and conferencing tools.
-
-
-Goncalves, et al. Expires October 21, 2008 [Page 9]
-
-Internet-Draft Ogg Media Types April 2008
-
-
Additional information:
Magic number(s): The first four bytes, 0x4f 0x67 0x67 0x53,
@@ -525,8 +538,11 @@
bitstream if they use the .oga extension. The .ogg and .spx file
extensions are a specialization that require no Skeleton due to
concerns of backwards-compatibility with existing implementations.
- Use of the .oga file extension is the preferred method of
- distributing audio data under the "audio/ogg" type.
+ In particular, .ogg is used for Ogg files that contain only a Vorbis
+ track (see [Vorbis] I specification), while .spx files are used for
+ Ogg files that contain only a Speex track (see [Speex]). Use of the
+ .oga file extension is the preferred method of distributing audio
+ data under the "audio/ogg" type.
Author: See "Authors' Addresses" section.
@@ -537,6 +553,14 @@
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
+
+
+
+Goncalves, et al. Expires October 21, 2008 [Page 10]
+
+Internet-Draft Ogg Media Types April 2008
+
+
permission is granted, redistributed modified works do not contain
misleading author, version, name of work, or endorsement information.
@@ -554,13 +578,6 @@
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
-
-
-Goncalves, et al. Expires October 21, 2008 [Page 10]
-
-Internet-Draft Ogg Media Types April 2008
-
-
[RFC4281] Gellens, R., Singer, D., and P. Frojdh, "The Codecs
Parameter for "Bucket" Media Types", RFC 4281,
November 2005.
@@ -592,6 +609,14 @@
<http://xiph.org/vorbis/doc/Vorbis_I_spec.html>.
[FLAC] Coalson, J., "The FLAC Format",
+
+
+
+Goncalves, et al. Expires October 21, 2008 [Page 11]
+
+Internet-Draft Ogg Media Types April 2008
+
+
<http://flac.sourceforge.net/format.html>.
[CMML] Pfeiffer, S., Parker, C., and A. Pang, "The Continuous
@@ -610,13 +635,6 @@
<http://tools.ietf.org/html/
draft-barbato-avt-rtp-theora>.
-
-
-Goncalves, et al. Expires October 21, 2008 [Page 11]
-
-Internet-Draft Ogg Media Types April 2008
-
-
[VoRTP] Barbato, L., "RTP Payload Format for Vorbis Encoded
Audio", November 2007,
<http://tools.ietf.org/html/draft-ietf-avt-rtp-vorbis>.
@@ -644,11 +662,22 @@
URI: xmpp:justivo at gmail.com
+
+
+
+
+
+
+Goncalves, et al. Expires October 21, 2008 [Page 12]
+
+Internet-Draft Ogg Media Types April 2008
+
+
Silvia Pfeiffer
Xiph.Org Foundation
- Phone: +61 2 8012 0937
EMail: silvia at annodex.net
+ URI: http://annodex.net/
Christopher Montgomery
@@ -668,7 +697,34 @@
-Goncalves, et al. Expires October 21, 2008 [Page 12]
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Goncalves, et al. Expires October 21, 2008 [Page 13]
Internet-Draft Ogg Media Types April 2008
@@ -713,10 +769,7 @@
this standard. Please address the information to the IETF at
ietf-ipr at ietf.org.
-Acknowledgement
- Funding for the RFC Editor function is provided by the IETF
- Administrative Support Activity (IASA).
@@ -724,5 +777,8 @@
-Goncalves, et al. Expires October 21, 2008 [Page 13]
+
+
+
+Goncalves, et al. Expires October 21, 2008 [Page 14]
Modified: trunk/standards/draft-goncalves-rfc3534bis.xml
===================================================================
--- trunk/standards/draft-goncalves-rfc3534bis.xml 2008-04-19 13:38:11 UTC (rev 14779)
+++ trunk/standards/draft-goncalves-rfc3534bis.xml 2008-04-20 13:36:18 UTC (rev 14780)
@@ -26,8 +26,8 @@
<author initials="S." surname="Pfeiffer" fullname="Silvia Pfeiffer">
<organization abbrev="Xiph">Xiph.Org Foundation</organization>
<address>
- <phone>+61 2 8012 0937</phone>
<email>silvia at annodex.net</email>
+ <uri>http://annodex.net/</uri>
</address>
</author>
<author initials="C." surname="Montgomery" fullname="Christopher Montgomery">
@@ -57,7 +57,7 @@
<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 3543">
+ <section title="Changes since RFC 3534">
<t>
<list style="symbols">
<t>The type "application/ogg" is redefined.</t>
@@ -84,7 +84,7 @@
</list>
</t>
<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 it is a type of identifier space used to describe the different encapsulated data.</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"/>. Possible examples include:</t>
<t>
@@ -96,7 +96,7 @@
</t>
</section>
<section title="Relation Between the Media Types">
- <t>As stated in the previous section, this document describes three media types which are targeted at different data encapsulated in Ogg. Since Ogg is capable of encapsulate any kind of data, the multiple usage scenarios have revealed interoperability issues between implementations when dealing with content served solely under the application/ogg type.</t>
+ <t>As stated in the previous section, this document describes three media types which are targeted at different data encapsulated in Ogg. Since Ogg is capable of encapsulating any kind of data, the multiple usage scenarios have revealed interoperability issues between implementations when dealing with content served solely under the application/ogg type.</t>
<t>While this document does redefine the earlier definition of application/ogg, this media type will continue to embrace the widest net possible of content with the video/ogg and audio/ogg types being smaller subsets of it. However, the video/ogg and audio/ogg types take precedence in a subset of the usages, specifically when serving multimedia content that is not complex enough to warrant the use of application/ogg. Following this line of thought, the audio/ogg type is an even smaller subset within video/ogg, as it is not intended to refer to visual content.</t>
<t>As such, the application/ogg type is the recommended choice to serve content aimed at scientific and other applications that require various multiplexed signals or streams of continuous data. For bitstreams containing visual, timed text, or any other type of material that requires a visual interface, but which is not complex enough to warrant serving under application/ogg, the video/ogg type is recommended. In situations where the Ogg bitstream predominantly contains audio data, it is recommended to use the audio/ogg type.</t>
</section>
@@ -105,7 +105,7 @@
<t>Note:</t>
<list style="symbols">
<t>Ogg encapsulated content is binary data and should be transmitted in a suitable encoding without CR/LF conversion, 7-bit stripping, etc.; <xref target="RFC4648">base64</xref> is generally preferred for binary-to-text encoding.</t>
- <t>Media types described in this document are used for stream based storage (such as files) and transport (such as TCP streams or pipes); separate types are used for real-time transfer, such as for the RTP payload formats of <xref target="ThRTP">Theora</xref> video, and <xref target="VoRTP">Vorbis</xref> or <xref target="SpRTP">Speex</xref> audio, as well as for identification of the encapsulated data within Ogg.</t>
+ <t>Media types described in this document are used for stream based storage (such as files) and transport (such as TCP streams or pipes); separate types are used to identify codecs such as in real-time applications for the RTP payload formats of <xref target="ThRTP">Theora</xref> video, and <xref target="VoRTP">Vorbis</xref> or <xref target="SpRTP">Speex</xref> audio. These mime types are also used in Skeleton for identification of the encapsulated data within Ogg.</t>
</list>
</section>
<section title="Security Considerations">
@@ -186,7 +186,7 @@
<t>Macintosh File Type Code(s): OggA</t>
<t>Person & Email address to contact for further information: See "Authors' Addresses" section.</t>
<t>Intended usage: COMMON</t>
- <t>Restrictions on usage: The type "audio/ogg" SHOULD be used when the Ogg bitstream predominantly contains audio data. Content served under the "audio/ogg" type SHOULD have an Ogg Skeleton logical bitstream if they use the .oga extension. The .ogg and .spx file extensions are a specialization that require no Skeleton due to concerns of backwards-compatibility with existing implementations. Use of the .oga file extension is the preferred method of distributing audio data under the "audio/ogg" type.</t>
+ <t>Restrictions on usage: The type "audio/ogg" SHOULD be used when the Ogg bitstream predominantly contains audio data. Content served under the "audio/ogg" type SHOULD have an Ogg Skeleton logical bitstream if they use the .oga extension. The .ogg and .spx file extensions are a specialization that require no Skeleton due to concerns of backwards-compatibility with existing implementations. In particular, .ogg is used for Ogg files that contain only a Vorbis track (see [Vorbis] I specification), while .spx files are used for Ogg files that contain only a Speex track (see [Speex]). Use of the .oga file extension is the preferred method of distributing audio data under the "audio/ogg" type.</t>
<t>Author: See "Authors' Addresses" section.</t>
<t>Change controller: The Xiph.Org Foundation.</t>
</section>
@@ -416,4 +416,4 @@
</reference>
</references>
</back>
-</rfc>
\ No newline at end of file
+</rfc>
More information about the commits
mailing list