RFC 3555: MIME Type Registration of RTP Payload Formats
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4855, RFC 4856.
Current document in this lineage: RFC 4855 — Media Type Registration of RTP Payload Formats; RFC 4856 — Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC3555
- Published
- July 2003
- Authors
- S. Casner; P. Hoschka
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 45
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3555 (2003)
- RFC 4855 (2007)
- RFC 4856 (2007) ✓
Referenced by
4 later RFCs formally update or obsolete part of this document.
- RFC 3625The QCP File Format and Media Types for Speech DataCurrent
October 2003
- RFC 4629RTP Payload Format for ITU-T Rec. H.263 VideoCurrent
January 2007
- RFC 4855Media Type Registration of RTP Payload FormatsUpdated
February 2007
- RFC 4856Media Type Registration of Payload Formats in the RTP Profile for Audio and Video ConferencesCurrent
February 2007
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3556Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) BandwidthCurrent
July 2003
- RFC 3557RTP Payload Format for European Telecommunications Standards Institute (ETSI) European Standard ES 201 108 Distributed Speech Recognition EncodingCurrent
July 2003
- RFC 3558RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)Updated
July 2003
- RFC 3611RTP Control Protocol Extended Reports (RTCP XR)Current
November 2003
- RFC 3640RTP Payload Format for Transport of MPEG-4 Elementary StreamsUpdated
December 2003
- RFC 3420Internet Media Type message/sipfragCurrent
November 2002
- RFC 3464An Extensible Message Format for Delivery Status NotificationsUpdated
January 2003
- RFC 3745MIME Type Registrations for JPEG 2000 (ISO/IEC 15444)Current
April 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?