RFC 3625: The QCP File Format and Media Types for Speech Data
In plain English — editorial summary, not part of the RFC
RFC 2658 specifies the streaming format for 3GPP2 13KK vocoder (High Rate Speech Service Option 17 for Wideband Spread Spectrum Communications Systems, also known as QCELP 13K vocoder) data, but does not specify a storage format. Many implementations have been using the "QCP" file format (named for its file extension) for exchanging QCELP 13K data as well as Enhanced Variable Rate Coder (EVRC) and Selectable Mode Vocoders (SMV) data. (For example, Eudora(r), QuickTime(r), and cmda2000(r) handsets). This document specifies the QCP file format and updates the audio/qcelp media registration to specify this format for storage, and registers the audio/evrc-qcp and audio/smv-qcp media types for EVRC and SMV (respectively) data stored in this format.
Document record
- Document ID
- RFC3625
- Published
- October 2003
- Authors
- R. Gellens; H. Garudadri
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 15
- Also known as
- —
- Updates:
- RFC 3555
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- 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 3533The Ogg Encapsulation Format Version 0Current
May 2003
- RFC 3802Toll Quality Voice - 32 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM) MIME Sub-type RegistrationCurrent
June 2004
- RFC 3389Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN)Current
October 2002
- RFC 2557MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)Current
March 1999
- RFC 2361WAVE and AVI Codec RegistriesCurrent
June 1998
- RFC 2231MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and ContinuationsCurrent
November 1997
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?