RFC 3534 (rfc3534) - Page 2 of 6
The application/ogg Media Type
Alternative Format: Original Text Document
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
