draft-walleij-ogg-mediatype

Last Version:	draft-walleij-ogg-mediatype-08.txt		Tracker Entry
Date:	29-Mar-2004
Disposition:	RFC3534 (diff)
Previous Versions:	draft-walleij-ogg-mediatype-08.txt (diff)    - 19-May-2003
	draft-walleij-ogg-mediatype-07.txt (diff)    - 09-Jan-2003
	draft-walleij-ogg-mediatype-06.txt (diff)    - 07-Dec-2002
	draft-walleij-ogg-mediatype-05.txt (diff)    - 11-May-2002
	draft-walleij-ogg-mediatype-04.txt (diff)    - 17-Feb-2002
	draft-walleij-ogg-mediatype-03.txt (diff)    - 16-Aug-2001
	draft-walleij-ogg-mediatype-02.txt (diff)    - 24-Jul-2001
	draft-walleij-ogg-mediatype-01.txt (diff)    - 23-Jun-2001
	draft-walleij-ogg-mediatype-00.txt (diff)    - 08-Apr-2002

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:    [email protected]
        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 [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[email protected].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.