WAVE and AVI Codec Registries (RFC2361)
Original Publication Date: 1998-Jun-01
Included in the Prior Art Database: 2000-Sep-13
Internet Society Requests For Comment (RFCs)
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.
Network Working Group E. Fleischman
Request for Comments: 2361 Microsoft Corporation
Category: Informational June 1998
WAVE and AVI Codec Registries
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright (C) The Internet Society (1998). All Rights Reserved.
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.
Internet-oriented multimedia applications reference multimedia
content via predefined mechanisms (e.g., ). In the general case,
this content was created primarily for the use of these Internet-
oriented applications. Unfortunately, this Internet-oriented
multimedia content represents a small minority of the total amount of
multimedia content that has been created to date.
For this reason, a growing interest is forming in establishing
mechanisms by which the repertoire of multimedia content available to
Internet-oriented applications(e.g., for RTSP ) may be greatly
extended to include multimedia content that has been created outside
of distinctly Internet contexts. For this to occur, a mechanism must
be created for Internet protocols (e.g., , , ) to be able to
identify the codecs by which this so-called "traditional" multimedia
content has been encoded.
Unfortunately, several distinct encoding systems exist for
traditional multimedia content. Each system has its own registry to
ensure unique and stable codec identifications within that system.
Perhaps the best known of these registries are Microsoft (for WAVE
and AVI content) and Apple (for QuickTime content).
The purpose of this paper is to establish a mechanism by which codecs
registered within Microsoft's WAVE and AVI Registries may be
referenced within the IANA Namespace by Internet applications.
2 References to Registries within the IANA Vendor Tree
Reference  specifies that the IANA Namespace encompasses several
trees. Discussions within the IETF-Types mailing list concluded that
the most appropriate tree in which to reference codecs, which had
already been registered by non-IANA Registries, is the Vendor Tree.
As a res...