RFC 7798: RTP Payload Format for High Efficiency Video Coding (HEVC)
In plain English — editorial summary, not part of the RFC
This memo describes an RTP payload format for the video coding standard ITU-T Recommendation H.265 and ISO/IEC International Standard 23008-2, both also known as High Efficiency Video Coding (HEVC) and developed by the Joint Collaborative Team on Video Coding (JCT-VC). The RTP payload format allows for packetization of one or more Network Abstraction Layer (NAL) units in each RTP packet payload as well as fragmentation of a NAL unit into multiple RTP packets. Furthermore, it supports transmission of an HEVC bitstream over a single stream as well as multiple RTP streams. When multiple RTP streams are used, a single transport or multiple transports may be utilized. The payload format has wide applicability in videoconferencing, Internet video streaming, and high-bitrate entertainment-quality video, among others.
Document record
- Document ID
- RFC7798
- Published
- March 2016
- Authors
- Y.-K. Wang; Y. Sanchez; T. Schierl; S. Wenger; M. M. Hannuksela
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 86
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9626Video Frame Marking RTP Header ExtensionCurrent
March 2025
- RFC 7790Mapping Characters for Classes of the Preparation, Enforcement, and Comparison of Internationalized Strings (PRECIS)Current
February 2016
- RFC 7807Problem Details for HTTP APIsObsoleted
March 2016
- RFC 7808Time Zone Data Distribution ServiceCurrent
March 2016
- RFC 7809Calendaring Extensions to WebDAV (CalDAV): Time Zones by ReferenceCurrent
March 2016
- RFC 7825A Network Address Translator (NAT) Traversal Mechanism for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
December 2016
- RFC 7826Real-Time Streaming Protocol Version 2.0Current
December 2016
- RFC 7764Guidance on Markdown: Design Philosophies, Stability Strategies, and Select RegistrationsCurrent
March 2016
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?