metasystema.org
CurrentPROPOSED STANDARDIETF stream

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 specifies media type registrations for the RTP payload formats defined in the RTP Profile for Audio and Video Conferences. Some of these may also be used for transfer modes other than RTP. [STANDARDS-TRACK]

Document record

Document ID
RFC4856
Published
February 2007
Authors
S. Casner
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
29
Also known as
—
Obsoletes:
RFC 3555

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 →

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/4856-media-type-registration-of-payload-formats-in-the-rtp-profile-for-audio-and-vide