RFC 3558: RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)
In plain English — editorial summary, not part of the RFC
This document describes the RTP payload format for Enhanced Variable Rate Codec (EVRC) Speech and Selectable Mode Vocoder (SMV) Speech. Two sub-formats are specified for different application scenarios. A bundled/interleaved format is included to reduce the effect of packet loss on speech quality and amortize the overhead of the RTP header over more than one speech frame. A non-bundled format is also supported for conversational applications. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3558
- Published
- July 2003
- Authors
- A. Li
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 23
- Also known as
- —
- Updated by:
- RFC 4788
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3557RTP Payload Format for European Telecommunications Standards Institute (ETSI) European Standard ES 201 108 Distributed Speech Recognition EncodingCurrent
July 2003
- RFC 3556Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) BandwidthCurrent
July 2003
- RFC 3555MIME Type Registration of RTP Payload FormatsObsoleted
July 2003
- RFC 3611RTP Control Protocol Extended Reports (RTCP XR)Current
November 2003
- RFC 3640RTP Payload Format for Transport of MPEG-4 Elementary StreamsUpdated
December 2003
- RFC 3550RTP: A Transport Protocol for Real-Time ApplicationsUpdated
July 2003
- RFC 3497RTP Payload Format for Society of Motion Picture and Television Engineers (SMPTE) 292M VideoCurrent
March 2003
- RFC 3389Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN)Current
October 2002
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?