RFC 3555 (rfc3555) - Page 2 of 45
MIME Type Registration of RTP Payload Formats
Alternative Format: Original Text Document
RFC 3555 MIME Type Registration of RTP Payload Formats July 2003
1. Introduction
The MIME registration procedure described in RFC 2048 [1] was
originally designed for transport of multimedia information via
asynchronous Internet mail, but the MIME namespace now provides
identification for other transport modes as well. This document
defines the procedure to register MIME subtype names for use with the
Real-time Transport Protocol (RTP), RFC 3550 [2], to identify RTP
payload formats.
This document also registers all the RTP payload formats defined in
the RTP Profile for Audio and Video Conferences, RFC 3551 [3], as
MIME subtypes under the "audio" and "video" MIME types.
1.1. IANA Considerations
This document registers the following MIME subtypes:
audio/DVI4
audio/G722
audio/G723
audio/G726-16
audio/G726-24
audio/G726-32
audio/G726-40
audio/G728
audio/G729
audio/G729D
audio/G729E
audio/GSM
audio/GSM-EFR
audio/L8
audio/L16
audio/LPC
audio/MPA
audio/PCMA
audio/PCMU
audio/QCELP
audio/RED
audio/VDVI
video/BT656
video/CelB
video/JPEG
video/H261
video/H263
video/H263-1998
video/H263-2000
video/MPV
Casner & Hoschka Standards Track