RFC 4856 · PROPOSED STANDARD · 2007
WED · 29 JUL 2026
Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences
Overview
RFC 4856, “Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences”, is a Proposed Standard document published in February 2007 by S. Casner. It obsoletes RFC 3555. The canonical text is published by the RFC Editor.
Abstract
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]
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.
Read this RFC
The canonical text of RFC 4856 is hosted at rfc-editor.org. Available in TXT,HTML.
Relationships to other RFCs
Other RFCs from 2007
- RFC 4855 Media Type Registration of RTP Payload Formats
- RFC 4857 Mobile IPv4 Regional Registration
- RFC 4854 A Uniform Resource Name Namespace for Extensions to the Extensible Messaging and Presence Protocol
- RFC 4858 Document Shepherding from Working Group Last Call to Publication
- RFC 4853 Cryptographic Message Syntax Multiple Signer Clarification
- RFC 4859 Codepoint Registry for the Flags Field in the Resource Reservation Protocol-Traffic Engineering Session Attribute Object
- RFC 4852 IPv6 Enterprise Network Analysis - IP Layer 3 Focus
- RFC 4860 Generic Aggregate Resource ReSerVation Protocol Reservations