MIME Type Registration of RTP Payload Formats
RFC 3555
|
| Document |
Type |
|
RFC - Proposed Standard
(July 2003; No errata)
|
|
Last updated |
|
2013-03-02
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 3555 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Allison Mankin
|
|
IESG note |
|
Responsible: RFC Editor
|
|
Send notices to |
|
<csp@csperkins.org>, <magnus.westerlund@ericsson.com>
|
Network Working Group S. Casner
Request for Comments: 3555 Packet Design
Category: Standards Track P. Hoschka
W3C/INRIA/MIT
July 2003
MIME Type Registration of RTP Payload Formats
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
This document defines the procedure to register RTP Payload Formats
as audio, video or other MIME subtype names. This is useful in a
text-based format or control protocol to identify the type of an RTP
transmission. This document also registers all the RTP payload
formats defined in the RTP Profile for Audio and Video Conferences as
MIME subtypes. Some of these may also be used for transfer modes
other than RTP.
Table of Contents
1. Introduction .................................................. 2
1.1. IANA Considerations ...................................... 2
1.2. Terminology .............................................. 3
2. Procedure For Registering MIME Types for RTP Payload Types .... 3
3. Mapping to SDP Parameters ..................................... 5
4. Registrations for "Audio/Video Profile" ....................... 6
4.1. Audio Type Registrations ................................. 6
4.2. Video Type Registrations ................................. 30
5. Security Considerations ....................................... 42
6. Normative References .......................................... 43
7. Authors' Addresses ............................................ 44
8. Full Copyright Statement ...................................... 45
Casner & Hoschka Standards Track [Page 1]
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 [Page 2]
RFC 3555 MIME Type Registration of RTP Payload Formats July 2003
video/MP2T
video/MP1S
video/MP2P
video/BMPEG
video/nv
MIME subtype audio/L16 has already been registered via RFC 2586 for
transports other than RTP. That registration is incorporated here
and augmented with additional information for RTP transport.
1.2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [4] and
indicate requirement levels for implementations compliant with this
specification.
2. Procedure For Registering MIME Types for RTP Payload Types
Registering an RTP payload type as a MIME type follows the same
procedures as described in RFC 2048 and uses the registration
template shown in Section 2.8 of RFC 2048. Some additional
parameters are required to specify how a particular payload format is
transported over RTP:
Published specification
A description of the encoding and a specification of the
payload format must be provided, usually by reference to an RTP
payload format specification RFC. That RFC may be separate, or
Show full document text