rfc-2422

Toll Quality Voice - 32 kbit/s ADPCM MIME Sub-type Registration

G. Vaudreuil, G. Parsons
date1998-09 streamLegacy statusPROPOSED STANDARD pages6 canonicalhttps://www.rfc-editor.org/rfc/rfc2422 doi10.17487/RFC2422
This document describes the registration of the MIME sub-type audio/32KADPCM for toll quality audio. [STANDARDS-TRACK]

obsoleted by

obsoletes

Extracted elements (10)

design-rationale §3.1

The choice of little endian ordering for the 4-bit code words is derived from ITU-T Recommendation X.420, which defines the equivalent ordering for the X.400 body part carrying this audio encoding. This alignment with X.400 facilitates interoperability with existing voice messaging infrastructure.

realtime

interoperability-note §3.2

In VPIM usage (RFC 2421), only little endian bit ordering is valid for audio/32KADPCM. Implementations using this sub-type in a VPIM context must adhere to the VPIM specification for proper usage.

realtime, email

interoperability-note §4

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

realtime

normative-requirement §4 RECOMMENDED

It is preferred that the voice sample be extended with silence so the encoded value comprises an even number of code words. If the 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/32KADPCM audio data.

realtime

normative-requirement §4 MUST

The 4-bit code words of G.726 encoding MUST be packed into octets using the little endian ordering described in the IANA registration, with the first code word 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.

realtime

registry §4

This document registers the MIME media type audio/32KADPCM for binary audio data encoded in 32 kbit/s ADPCM as defined by ITU-T Recommendation G.726. No required or optional parameters are defined; intended usage is COMMON.

registry, realtime

security-consideration §4

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 a security vulnerability.

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 an octet (A0 in bit 0), and the second code word (B) occupies the four most significant bits (B3 in bit 7). Subsequent pairs follow the same pattern in successive octets.

realtime