RFC 8088: How to Write an RTP Payload Format
In plain English — editorial summary, not part of the RFC
This document contains information on how best to write an RTP payload format specification. It provides reading tips, design practices, and practical tips on how to produce an RTP payload format specification quickly and with good results. A template is also included with instructions.
Document record
- Document ID
- RFC8088
- Published
- May 2017
- Authors
- M. Westerlund
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 65
- Also known as
- —
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 7825A Network Address Translator (NAT) Traversal Mechanism for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
December 2016
- RFC 7741RTP Payload Format for VP8 VideoCurrent
March 2016
- RFC 8450RTP Payload Format for VC-2 High Quality (HQ) ProfileCurrent
October 2018
- RFC 7656A Taxonomy of Semantics and Mechanisms for Real-Time Transport Protocol (RTP) SourcesCurrent
November 2015
- RFC 7604Comparison of Different NAT Traversal Techniques for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
September 2015
- RFC 8723Double Encryption Procedures for the Secure Real-Time Transport Protocol (SRTP)Current
April 2020
- RFC 8843Negotiating Media Multiplexing Using the Session Description Protocol (SDP)Obsoleted
January 2021
- RFC 8858Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)Current
January 2021
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?