MIME Type Registration of RTP Payload Formats
RFC 3555, “MIME Type Registration of RTP Payload Formats”, is a Proposed Standard document published in July 2003 by S. Casner, P. Hoschka. It has since been updated by RFC 3625, RFC 4629. It has been obsoleted by RFC 4855, RFC 4856 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
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. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3555 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3554 On the Use of Stream Control Transmission Protocol with IPsec
- RFC 3556 Session Description Protocol Bandwidth Modifiers for RTP Control Protocol Bandwidth
- RFC 3553 An IETF URN Sub-namespace for Registered Protocol Parameters
- RFC 3557 RTP Payload Format for European Telecommunications Standards Institute European Standard ES 201 108 Distributed Speech Recognition Encoding
- RFC 3552 Guidelines for Writing RFC Text on Security Considerations
- RFC 3558 RTP Payload Format for Enhanced Variable Rate Codecs and Selectable Mode Vocoders
- RFC 3551 RTP Profile for Audio and Video Conferences with Minimal Control
- RFC 3559 Multicast Address Allocation MIB