RFC 2736: Guidelines for Writers of RTP Payload Format Specifications
In plain English — editorial summary, not part of the RFC
This document provides general guidelines aimed at assisting the authors of RTP Payload Format specifications in deciding on good formats. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC2736
- Published
- December 1999
- Authors
- M. Handley; C. Perkins
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- rai
- Pages
- 10
- Also known as
- BCP36
- Updated by:
- RFC 8088
Topics
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.
- RFC 9134RTP Payload Format for ISO/IEC 21122 (JPEG XS)Current
October 2021
- RFC 2793RTP Payload for Text ConversationObsoleted
May 2000
- RFC 4103RTP Payload for Text ConversationUpdated
June 2005
- RFC 3096Requirements for robust IP/UDP/RTP header compressionCurrent
July 2001
- RFC 3759RObust Header Compression (ROHC): Terminology and Channel Mapping ExamplesCurrent
April 2004
- RFC 5334Ogg Media TypesUpdated
September 2008
- RFC 2862RTP Payload Format for Real-Time PointersCurrent
June 2000
- RFC 2429RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+)Obsoleted
October 1998
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?