[xiph-commits] r13810 - experimental/ivo/drafts
ivo at svn.xiph.org
ivo at svn.xiph.org
Sat Sep 15 14:31:19 PDT 2007
Author: ivo
Date: 2007-09-15 14:31:18 -0700 (Sat, 15 Sep 2007)
New Revision: 13810
Modified:
experimental/ivo/drafts/draft-xiph-rfc3534bis.txt
Log:
a truckload of changes, additions and removals that I can't be bothered to describe; currently lacking clear information on what application/ogg is
Modified: experimental/ivo/drafts/draft-xiph-rfc3534bis.txt
===================================================================
--- experimental/ivo/drafts/draft-xiph-rfc3534bis.txt 2007-09-15 11:20:11 UTC (rev 13809)
+++ experimental/ivo/drafts/draft-xiph-rfc3534bis.txt 2007-09-15 21:31:18 UTC (rev 13810)
@@ -3,10 +3,8 @@
+ Ogg Media Types
-
- Ogg Multimedia Media Types
-
Status of This Memo
This memo provides information for the Internet community. It does
@@ -38,16 +36,6 @@
9.1. Normative References ......................................13
9.2. Informative References ....................................13
-
-
-
-
-
-
-
-
-
-
1. Introduction
This memo describes media types for the Ogg container format.
@@ -98,13 +86,17 @@
which are also defined in this document, are intended for common use
and should be used when dealing with video and/or audio content.
+ Updates of this document may introduce optional parameters;
+ implementations MUST consider the impact of such an update.
+
X. Encoding Considerations
- Ogg content is binary data, and must be encoded for non-binary
- transport; the base64 [RFC2397] encoding is suitable for EMail.
+ Ogg encapsulated content is binary data, and must be encoded for
+ non-binary transport; the base64 [RFC2397] encoding is suitable
+ for EMail.
- Note that Ogg content does not compress easily using traditional
- lossless compression schemes.
+ Note that most Ogg encapsulated content does not compress easily
+ using traditional lossless compression schemes.
5. Security Considerations
@@ -149,6 +141,21 @@
or sensitive information; such failure constitutes an unknown factor
and is thus considered out of the scope of this document.
+X. Interoperability Considerations
+
+ The Ogg container format is device-, platform- and vendor-neutral
+ and has proved to be widely implementable across different computing
+ platforms, including through a wide range of encoders and decoders.
+ A broadly portable reference implementation [libogg] is available
+ under a BSD license.
+
+ The Ogg container format is not patented and may be implemented by
+ third parties without patent considerations.
+
+ The Xiph.Org Foundation has defined the specification,
+ interoperability, and conformance, and conducts regular
+ interoperability testing.
+
6. IANA Considerations
This document registers two new media types and redefines the
@@ -162,11 +169,11 @@
Subtype name: ogg
Required parameters: none
Optional parameters: none
- Encoding considerations: n/a
+ Encoding considerations: See section X.
Security considerations: See section 5.
Interoperability considerations:
- None, except as noted in other sections of this document.
+ None, except as noted in section X.
Published specification: [Ogg]
Applications which use this media type:
@@ -177,14 +184,20 @@
Magic number(s): The first four bytes, 0x4f 0x67 0x67
0x53, correspond to the string OggS.
File extension(s): .ogx
+
+ NOTE
+
+ [RFC3534] defines the file extension .ogg for application/ogg,
+ which this document obsoletes in favor of .ogx.
+
Macintosh File Type Code(s): OggS
Person & email address to contact for further information:
- See Authors' Addresses section.
+ See Author's Address section.
Intended usage: COMMON
Restrictions on usage: n/a
- Author: See Authors' Addresses section.
+ Author: See Author's Address section.
Change controller: The Xiph.Org Foundation.
@@ -214,15 +227,15 @@
Subtype name: ogg
Required parameters: none
Optional parameters: none
- Encoding considerations: n/a
+ Encoding considerations: See section X.
Security considerations: See section 5.
Interoperability considerations:
- None, except as noted in other sections of this document.
+ None, except as noted in section X.
Published specification: [Ogg]
Applications which use this media type:
- Script interpreters as discussed in this document.
+ Audio and video streaming and conferencing tools.
Additional information:
@@ -232,11 +245,11 @@
Macintosh File Type Code(s): OggS
Person & email address to contact for further information:
- See Authors' Addresses section.
+ See Author's Address section.
Intended usage: COMMON
Restrictions on usage: n/a
- Author: See Authors' Addresses section.
+ Author: See Author's Address section.
Change controller: The Xiph.Org Foundation.
@@ -268,15 +281,15 @@
Subtype name: ogg
Required parameters: none
Optional parameters: none
- Encoding considerations: n/a
+ Encoding considerations: See section X.
Security considerations: See section 5.
Interoperability considerations:
- None, except as noted in other sections of this document.
+ None, except as noted in section X.
Published specification: [Ogg]
Applications which use this media type:
- Script interpreters as discussed in this document.
+ Audio and video streaming and conferencing tools.
Additional information:
@@ -285,12 +298,21 @@
File extension(s): .oga, .ogg, .spx
Macintosh File Type Code(s): OggS
+ NOTE
+
+ Only Vorbis-encoded audio SHOULD use the .ogg file extension.
+ Only Speex-encoded audio SHOULD use the .spx file extension.
+ This requirement is to ensure backwards-compatibility with
+ existing applications. Other audio formats encapsulated in
+ Ogg MUST use the .oga file extension, even when multiplexed
+ with Vorbis or Speex-encoded audio.
+
Person & email address to contact for further information:
- See Authors' Addresses section.
+ See Author's Address section.
Intended usage: COMMON
Restrictions on usage: n/a
- Author: See Authors' Addresses section.
+ Author: See Author's Address section.
Change controller: The Xiph.Org Foundation.
@@ -315,75 +337,10 @@
9. References
-9.1. Normative References
- [CHARSETS] IANA, "Assigned character sets",
- <http://www.iana.org/assignments/character-sets>.
- [ECMA] European Computer Manufacturers Association,
- "ECMAScript Language Specification 3rd Edition",
- December 1999, <http://www.ecma-international.org/
- publications/standards/Ecma-262.htm>
+Author's Address
- [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
- Requirement Levels", BCP 14, RFC 2119, March 1997.
-
- [RFC2978] Freed, N. and J. Postel, "IANA Charset Registration
- Procedures", BCP 19, RFC 2978, October 2000.
-
- [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
- Types", RFC 3023, January 2001.
-
- [RFC3536] Hoffman, P., "Terminology Used in Internationalization
- in the IETF", RFC 3536, May 2003.
-
- [RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing
- RFC Text on Security Considerations", BCP 72, RFC
- 3552, July 2003.
-
- [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
- 10646", STD 63, RFC 3629, November 2003.
-
-9.2. Informative References
-
- [E4X] European Computer Manufacturers Association,
- "ECMAScript for XML (E4X)", June 2004,
- <http://www.ecma-international.org/
- publications/standards/Ecma-357.htm>
-
- [EcmaCompact] European Computer Manufacturers Association,
- "ECMAScript 3rd Edition Compact Profile", June 2001,
- <http://www.ecma-international.org/
- publications/standards/Ecma-327.htm>
-
- [JS15] Netscape Communications Corp., "Core JavaScript
- Reference 1.5", September 2000,
- <http://web.archive.org/*/http://
- devedge.netscape.com/library/manuals/2000
- /javascript/1.5/reference/>.
-
-
-
-
-
- [RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397,
- August 1998.
-
- [RFC3236] Baker, M. and P. Stark, "The 'application/xhtml+xml'
- Media Type", RFC 3236, January 2002.
-
- [RFC3875] Robinson, D. and K. Coar, "The Common Gateway
- Interface (CGI) Version 1.1", RFC 3875, October 2004.
-
- [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter,
- "Uniform Resource Identifier (URI): Generic Syntax",
- STD 66, RFC 3986, January 2005.
-
- [RFC3987] Duerst, M. and M. Suignard, "Internationalized
- Resource Identifiers (IRIs)", RFC 3987, January 2005.
-
-Authors' Addresses
-
Ivo Emanuel Goncalves
EMail: justivo at gmail.com
URI: http://spreadopenmedia.org
@@ -436,39 +393,12 @@
permission is granted, redistributed modified works do not contain
misleading author, version, name of work, or endorsement information.
-Intellectual Property
- The IETF takes no position regarding the validity or scope of any
- Intellectual Property Rights or other rights that might be claimed to
- pertain to the implementation or use of the technology described in
- this document or the extent to which any license under such rights
- might or might not be available; nor does it represent that it has
- made any independent effort to identify any such rights. Information
- on the procedures with respect to rights in RFC documents can be
- found in BCP 78 and BCP 79.
- Copies of IPR disclosures made to the IETF Secretariat and any
- assurances of licenses to be made available, or the result of an
- attempt made to obtain a general license or permission for the use of
- such proprietary rights by implementers or users of this
- specification can be obtained from the IETF on-line IPR repository at
- http://www.ietf.org/ipr.
- The IETF invites any interested party to bring to its attention any
- copyrights, patents or patent applications, or other proprietary
- rights that may cover technology that may be required to implement
- 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).
-
-
-
-
Xiph.Org Foundation Informational [Page 15]
More information about the commits
mailing list