RFC 2361 on WAVE and AVI Codec Registries
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RFC 2361 on WAVE and AVI Codec Registries



A new Request for Comments is now available in online RFC libraries.


        RFC 2361:

        Title:      WAVE and AVI Codec Registries
	Author(s):  E. Fleischman
	Status:     Informational
	Date:       June 1998
        Mailbox:    Eric.Fleischman at PSS.Boeing.com
	Pages:      71
        Characters: 97796
        Updates/Obsoletes: None


        URL:        ftp://ftp.isi.edu/in-notes/rfc2361.txt


Internet applications may reference specific codecs within the WAVE
and AVI registries as follows:

* video/vnd.avi; codec=XXX identifies a specific video codec (i.e.,
  XXX) within the AVI Registry.
* audio/vnd.wave; codec=YYY identifies a specific audio codec
  (i.e., YYY) within the WAVE Registry.
 
Appendix A and Appendix B provides an authoritative reference for the 
interpretation of the required "codec" parameter. That is, the current
set of audio codecs that are registered within the WAVE Registry are 
enumerated in Appendix A. Appendix B enumerates the current set of 
video codecs that have been registered to date within the AVI Registry.

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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at ISI.EDU.

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

        To: rfc-info at ISI.EDU
        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 at ISI.EDU.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at ISI.EDU.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
<ftp://ftp.isi.edu/in-notes/rfc2361.txt>

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.