The application/ogg Media Type
RFC 3534
| Document | Type |
RFC - Proposed Standard
(May 2003; No errata)
Obsoleted by RFC 5334
Was draft-walleij-ogg-mediatype (individual in tsv area)
|
|
|---|---|---|---|
| Author | Linus Walleij | ||
| Last updated | 2018-07-18 | ||
| Stream | Internent Engineering Task Force (IETF) | ||
| Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 3534 (Proposed Standard) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Allison Mankin | ||
| IESG note |
This was approved 2003-01-23 and announced. It had an RFC-Editor note to reference the i-d name for the documentation of the format, which is still in review but should get approved shortly. |
||
| Send notices to | (None) | ||
Network Working Group L. Walleij
Request for Comments: 3534 The Ogg Vorbis Community
Category: Standards Track May 2003
The application/ogg Media Type
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
The Ogg Bitstream Format aims at becoming a general, freely-available
standard for transporting multimedia content across computing
platforms and networks. The intention of this document is to define
the MIME media type application/ogg to refer to this kind of content
when transported across the Internet. It is the intention of the Ogg
Bitstream Format developers that it be usable without intellectual
property concerns.
Conventions used in this Document
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 RFC 2119 [2].
1. The Ogg Bitstream Format
The Ogg Bitstream format has been developed as a part of a larger
project aimed at creating a set of components for the coding and
decoding of multimedia content (codecs) which are to be freely
available and freely re-implementable both in software and in
hardware for the computing community at large, including the Internet
community.
Raw packets from these codecs may be used directly by transport
mechanisms that provide their own framing and packet-separation
mechanisms (such as UDP datagrams).
Walleij Standards Track [Page 1]
RFC 3534 The application/ogg Media Type May 2003
One such framing and content-separation mechanism is the real-time
transport protocol (RTP). RTP allows the streaming of synchronous
lossy data for broadcasting and similar purposes. If this function
is desired then a separate RTP wrapping mechanism should be used. A
wrapping mechanism is currently under development.
For stream based storage (such as files) and transport (such as TCP
streams or pipes), Ogg codecs use the Ogg Bitstream Format to provide
framing/sync, sync recapture after error, landmarks during seeking,
and enough information to properly separate data back into packets at
the original packet boundaries without relying on decoding to find
packet boundaries. The application/ogg MIME type refers to this kind
of bitstreams, when no further knowledge of the bitstream content
exists.
The bitstream format in itself is documented in [1].
2. Registration Information
To: ietf-types@iana.org
Subject: Registration of MIME media type application/ogg
MIME media type name: application
MIME subtype name: ogg
Required parameters: none
Optional parameters: none
Encoding Considerations:
The Ogg bitstream format is binary data, and must be encoded for
non-binary transport; the Base64 encoding is suitable for Email.
Binary encoding could also be used.
Security Considerations:
As the Ogg bitstream file is a container format and only a carrier of
content (such as Vorbis audio) with a very rigid definition (see
[1]), this format in itself is not more vulnerable than any other
content framing mechanism. The main security consideration for the
receiving application is to ensure that manipulated packages can not
cause buffer overflows and the like. It is possible to encapsulate
even executable content in the bitstream, so for such uses additional
security considerations must be taken.
Walleij Standards Track [Page 2]
RFC 3534 The application/ogg Media Type May 2003
Ogg bitstream files are not signed or encrypted using any applicable
encryption schemes. External security mechanisms must be added if
content confidentiality and authenticity is to be achieved.
Interoperability considerations:
The Ogg bitstream format has proved to be widely implementable across
different computing platforms. A broadly portable reference
implementation is available under a BSD license.
The Ogg bitstream format is not patented and can be implemented by
third parties without patent considerations.
Published specification:
See [1].
Applications which use this media type:
Any application that implements the specification will be able to
encode or decode Ogg bitstream files. Specifically, the format is
Show full document text