num-rates = UINT32
; this is the number of possible rate octets
; used in the packets in the data chunk
rate-map-table = 8rate-map-entry
; any unused entries SHOULD be filled with
; %d0 %d0
rate-map-entry = rate-size rate-octet
; this maps a possible rate octet for a packet
; to the size of the rest of the packet having
; that value for the rate octet
rate-size = OCTET
; this is the size of a packet, excluding the
; value for the rate octet
rate-octet = OCTET
; this is the first octet of a packet in the
; data chunk, when the var-rate-flag set for
; the file indicates the file is variable rate
UINT32 = 4OCTET
; this field contains a 32-bit integer stored
; as a sequence of four octets, in
; little-endian order (least significant
; octet first)
UINT16 = 2OCTET
; this field contains a 16-bit integer stored
; as a sequence of two octets, in
; little-endian order (least significant
; octet first)
OCTET = %x00-FF
; an octet, also called a byte - any possible
; combination of eight bits, forming a single
; integer or part of a larger integer having
; more than eight bits
RIFF = %x52 %x49 %x46 %x46
QLCM = %x51 %x4C %x43 %x4D
FMT = %x66 %x6D %x74 %x20
LABL = %x6C %x61 %x62 %x6C
OFFS = %x6F %x66 %x66 %x73
DATA = %x64 %x61 %x74 %x61
CNFG = %x63 %x6E %x66 %x67
TEXT = %x74 %x65 %x78 %x74
4. IANA Considerations
IANA has updated the audio/qcelp and audio/vnd.qcelp registrations
and has added the audio/evrc-qcp and audio/smv-qcp registrations as
specified here.
4.1. Update of Media Type Audio/qcelp
The audio/qcelp media registration has been updated to indicate that
this specification is to be used for storage.
4.2. Update of Media Type Audio/vnd.qcelp
The audio/vnd.qcelp media registration has been updated to indicate
that use of this media type is deprecated and to note that the media
type audio/qcelp should be used instead.
4.3. Registration of Audio/EVRC-QCP
Media Type Name: audio
Media Subtype Name: evrc-qcp
Required Parameter: none
Optional parameters: none
Encoding considerations:
The storage format specified in this document may be used with
any transport mechanism.
Security considerations:
See Section 5 "Security Considerations" of this document.
Public specification: this document
Additional information: no
Magic number: First four octets: RIFF
Octets 9-12: QLCM
(Note: octets 5-8 constitute the riff-size field, which is the
size of the file minus the RIFF header. Since this could be
anything, it is not fixed and thus can not be used as part of the
magic number.)
File extensions: qcp, QCP
Macintosh file type code: none
Object identifier or OID: none
Intended usage:
COMMON. This file format is already in wide use in Internet
email user agents, multimedia authoring and playing software,
and cdma2000(r) handsets.
Person & email address to contact for further information:
Harinath Garudadri hgarudad@qualcomm.com
Change controller:
The IETF
4.4. Registration of Audio/SMV-QCP
Media Type Name: audio
Media Subtype Name: smv-qcp
Required Parameter: none
Optional parameters: none
Encoding considerations:
The storage format specified in this document may be used with
any transport mechanism.
Security considerations:
See Section 5 "Security Considerations" of this document.
Public specification: this document
Additional information: no
Magic number: First four octets: RIFF
Octets 9-12: QLCM
(Note: octets 5-8 constitute the riff-size field, which is the
size of the file minus the RIFF header. Since this could be
anything, it is not fixed and thus can not be used as part of the
magic number.)
File extensions: qcp, QCP
Macintosh file type code: none
Object identifier or OID: none
Intended usage:
COMMON. This file format is already in wide use in Internet
email user agents, multimedia authoring and playing software,
and cdma2000(r) handsets.
Person & email address to contact for further information:
Harinath Garudadri hgarudad@qualcomm.com
Change controller:
The IETF
5. Security Considerations
This document specifies a file format only, not a streaming protocol
payload format, nor a transfer method. As such, it introduces no
security risks aside from those associated with any audio codec or
media file format (for example, denial of service by transmitting a
file larger than the receiver can handle). Note that those security
concerns should be understood before using the file format specified
here.
6. Acknowledgements
Richard Walters created the ABNF notation for this specification and
proof-read the text, among other helpful tasks.
The qcp file format was originally developed by others within
Qualcomm. The editor would like to thank Chuck Han and Livingstone
Song for their contributions leading to this specification.
7. References
7.1. Normative References
[ABNF] Crocker, D., Ed. and P. Overell, "Augmented BNF for
Syntax Specifications: ABNF", RFC 2234, November 1997.
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[QCELP] 3GPP2 C.S0020 "High Rate Speech Service Option 17 for
Wideband Spread Spectrum Communications Systems".
[EVRC] 3GPP2 C.S0014 "Enhanced Variable Rate Codec, Speech
Service Option 3 for Wideband Spread Spectrum Digital
Systems ". (Used to be TIA/EIA/IS-127)
[PureVoice] McKay, K., "RTP Payload Format for PureVoice(tm) Audio",
RFC 2658, August 1999.
[SMV] 3GPP2 C.S0030 "Selectable Mode Vocoder, Service Option
for Wideband Spread Spectrum Communication Systems".
7.2. Informative References
[EVRC-SMV] Li, A., "RTP Payload Format for Enhanced Variable Rate
Codecs (EVRC) and Selectable Mode Vocoders (SMV)", RFC
3558, July 2003.
8. Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF’s procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
9. Editors’ Addresses
Randall Gellens
QUALCOMM Incorporated
5775 Morehouse Drive
San Diego, CA 92121
USA
EMail: randy@qualcomm.com
Harinath Garudadri
QUALCOMM Incorporated
5775 Morehouse Drive
San Diego, CA 92121
USA
EMail: hgarudad@qualcomm.com
10. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.