rfc-3802

Toll Quality Voice - 32 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM) MIME Sub-type Registration

G. Vaudreuil, G. Parsons
date2004-06 streamIETF areaapp wgvpim statusDRAFT STANDARD pages7 canonicalhttps://www.rfc-editor.org/rfc/rfc3802 doi10.17487/RFC3802
This document describes the registration of the MIME sub-type audio/32KADPCM Adaptive Differential Pulse Code Modulation for toll quality audio. This audio encoding is defined by the ITU-T in Recommendation G.726. [STANDARDS-TRACK]

obsoletes

Extracted elements (10)

design-rationale §3.1

The choice of little endian ordering for 4-bit code words is adopted from ITU-T Recommendation X.420, which defines the equivalent ordering for the X.400 body part. This alignment ensures consistency with the existing X.400 voice messaging ecosystem that VPIM targets.

realtime, email

interoperability-note §3.2

In VPIM usage, only the little endian bit ordering is valid for audio/32KADPCM. The Content-Description and Content-Disposition headers are used to describe the audio body contents.

email, realtime

interoperability-note §4

The four-bit code word ordering within a byte may differ between existing implementations of G.726 codecs. Since audio/32KADPCM only permits little endian ordering, codecs that support the opposite (big endian) ordering must reorder the code words before storing to or retrieving from this content type.

realtime

normative-requirement §4 SHOULD

It is preferred that the voice sample be extended with silence so the encoded value comprises an even number of code words. If the voice sample comprises an odd number of code words, the last code word shall be discarded.

realtime

normative-requirement §3.1 MUST NOT

No header information shall be included as part of the audio data in the audio/32KADPCM content type.

email, realtime

normative-requirement §4 MUST

The 4-bit code words of the G.726 encoding MUST be packed into octets using little endian ordering, with the first code word of each pair in the least significant four bits of each octet.

realtime

protocol-element §3.1

The MIME sub-type audio/32KADPCM holds binary audio data encoded in 32 kbit/s ADPCM exactly as defined by ITU-T Recommendation G.726. No header information shall be included as part of the audio data. Content transfer encoding is typically binary or base64.

email, realtime

registry §4

IANA registration of MIME media type audio/32KADPCM for 32 kbit/s G.726 ADPCM audio with no required or optional parameters, little endian bit ordering, and file extension .726.

registry, email, realtime

security-consideration §5

There are no known security risks with the sending or playing of raw audio data. Audio data is typically interpreted only by an audio codec, and unintended information introduced into the data stream will result in noise rather than exploitable behavior.

security, realtime

wire-format §4

G.726 4-bit code words are packed into octets in little endian order: the first code word (A) occupies the four least significant bits of each octet (A0 in bit 0), and the second code word (B) occupies the four most significant bits (B3 in bit 7). Subsequent code word pairs are packed the same way into successive octets.

realtime