The application/ogg Media Type
obsoleted by
- rfc-5334 — Ogg Media Types
Extracted elements (9)
The application/ogg type is used rather than a more specific subtype because it is intended for cases where no further knowledge of the bitstream content exists; content-specific types (e.g., for Vorbis audio) are handled by the respective subcodecs.
Raw packets from Ogg codecs may be used directly by transport mechanisms that provide their own framing and packet-separation (such as UDP datagrams). For RTP streaming, a separate RTP wrapping mechanism should be used rather than application/ogg.
The Ogg bitstream format is not patented and can be implemented by third parties without patent considerations. A broadly portable BSD-licensed reference implementation is available.
The Ogg bitstream format is binary data and MUST be encoded for non-binary transport; Base64 encoding is suitable for Email, and binary encoding may also be used.
The application/ogg MIME type refers to stream-based Ogg bitstream content, providing framing/sync, sync recapture after error, seeking landmarks, and packet boundary separation without relying on decoding.
The Ogg bitstream magic number consists of the first four bytes 0x4f 0x67 0x67 0x53, corresponding to the ASCII string 'OggS'. The file extension is .ogg and the Macintosh File Type Code is OggS.
This document registers the MIME media type application/ogg for the Ogg Bitstream Format, intended for use when transporting Ogg bitstream content across the Internet with no further knowledge of the bitstream content.
Ogg bitstream files are not signed or encrypted; external security mechanisms must be added if content confidentiality and authenticity are required.
The primary security concern for receiving applications is to ensure that manipulated Ogg packages cannot cause buffer overflows. Executable content can be encapsulated in the bitstream, requiring additional security considerations for such uses.