The Ogg Encapsulation Format Version 0

The information below is for an old version of the document that is already published as an RFC
Document Type RFC Internet-Draft (tsv)
Author Silvia Pfeiffer 
Last updated 2015-10-14 (latest revision 2003-03-07)
Stream Independent Submission
Formats plain text pdf htmlized bibtex
Stream ISE state (None)
Consensus Boilerplate Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 3533 (Informational)
Telechat date
Responsible AD Allison Mankin
IESG note Updated version is clearer about codec-specific information - Harald okays -02 when it pops out.
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3533

        Title:      The Ogg Encapsulation Format Version 0
        Author:     S. Pfeiffer
        Date:       May 2003
        Pages:      15
        Characters: 32045
        Updates/Obsoletes/SeeAlso: None

        I-D Tag:    draft-pfeiffer-ogg-fileformat-02.txt


This document describes the Ogg bitstream format version 0, which is a
general, freely-available encapsulation format for media streams.  It
is able to encapsulate any kind and number of video and audio encoding
formats as well as other data streams in a single bitstream.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.