The application/ogg Media Type
draft-walleij-ogg-mediatype-08

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3534.
Author Linus Walleij
Last updated 2018-07-18 (Latest revision 2003-01-08)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats
txt htmlized pdf bibtex bibxml
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3534 (Proposed Standard)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Allison J. Mankin
IESG note ** No value found for 'doc.notedoc.note' **
Send notices to (None)
Email authors IPR References Referenced by Nits Search email archive
draft-walleij-ogg-mediatype-08 
A new Request for Comments is now available in online RFC libraries.

        RFC 3534

        Title:      The application/ogg Media Type
        Author:     L. Walleij
        Date:       May 2003
        Mailbox:    triad@df.lth.se
        Pages:      6
        Characters: 10013
        Updates/Obsoletes/SeeAlso: None

        I-D Tag:    draft-walleij-ogg-mediatype-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3534.txt

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.

This is now a Proposed Standard Protocol.

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.

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
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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.