RFC 2361: WAVE and AVI Codec Registries
In plain English — editorial summary, not part of the RFC
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. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2361
- Published
- June 1998
- Authors
- E. Fleischman
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 71
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3533The Ogg Encapsulation Format Version 0Current
May 2003
- RFC 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 6849An Extension to the Session Description Protocol (SDP) and Real-time Transport Protocol (RTP) for Media LoopbackCurrent
February 2013
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 2343RTP Payload Format for Bundled MPEGCurrent
May 1998
- RFC 2326Real Time Streaming Protocol (RTSP)Obsoleted
April 1998
- RFC 2736Guidelines for Writers of RTP Payload Format SpecificationsUpdated
December 1999
- RFC 2793RTP Payload for Text ConversationObsoleted
May 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?