RFC 4424: Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Extension Audio Codec
In plain English — editorial summary, not part of the RFC
This document is an addendum to RFC 4348, which specifies the RTP payload format for the Variable-Rate Multimode Wideband (VMR-WB) speech codec. This document specifies some updates in RFC 4348 to enable support for the new operating mode of VMR-WB standard (i.e., VMR-WB mode 4). These updates do not affect the existing modes of VMR-WB already specified in RFC 4348. The payload formats and their associated parameters, as well as all provisions, restrictions, use cases, features, etc., that are specified in RFC 4348 are applicable to the new operating mode with no exception. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4424
- Published
- February 2006
- Authors
- S. Ahmadi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 8
- Also known as
- —
- Updates:
- RFC 4348
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5993RTP Payload Format for Global System for Mobile Communications Half Rate (GSM-HR)Current
October 2010
- RFC 6569Guidelines for Development of an Audio Codec within the IETFCurrent
March 2012
- RFC 4425RTP Payload Format for Video Codec 1 (VC-1)Current
February 2006
- RFC 4421RTP Payload Format for Uncompressed Video: Additional Colour Sampling ModesCurrent
February 2006
- RFC 4415IANA Registration for Enumservice VoiceUpdated
February 2006
- RFC 4414An ENUM Registry Type for the Internet Registry Information Service (IRIS)Current
February 2006
- RFC 4412Communications Resource Priority for the Session Initiation Protocol (SIP)Updated
February 2006
- RFC 4411Extending the Session Initiation Protocol (SIP) Reason Header for Preemption EventsCurrent
February 2006
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?