metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 4855: Media Type Registration of RTP Payload Formats

Still current, but amended. Parts of this document are changed or extended by RFC 8851. Read both.

In plain English — editorial summary, not part of the RFC

This document specifies the procedure to register RTP payload formats as audio, video, or other media subtype names. This is useful in a text-based format description or control protocol to identify the type of an RTP transmission. [STANDARDS-TRACK]

Document record

Document ID
RFC4855
Published
February 2007
Authors
S. Casner
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
11
Also known as
—
Obsoletes:
RFC 3555
Updated by:
RFC 8851

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 3555 (2003)
  2. RFC 4855 (2007)
  3. RFC 4856 (2007) ✓

Read the full history of Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences →

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/4855-media-type-registration-of-rtp-payload-formats