RFC 9328: RTP Payload Format for Versatile Video Coding (VVC)
In plain English — editorial summary, not part of the RFC
This memo describes an RTP payload format for the Versatile Video Coding (VVC) specification, which was published as both ITU-T Recommendation H.266 and ISO/IEC International Standard 23090-3. VVC was developed by the Joint Video Experts Team (JVET). 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. The payload format has wide applicability in videoconferencing, Internet video streaming, and high-bitrate entertainment-quality video, among other applications.
Document record
- Document ID
- RFC9328
- Published
- December 2022
- Authors
- S. Zhao; S. Wenger; Y. Sanchez; Y.-K. Wang; M. M Hannuksela
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 54
- Also known as
- —
Topics
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 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 8331RTP Payload for Society of Motion Picture and Television Engineers (SMPTE) ST 291-1 Ancillary DataCurrent
February 2018
- RFC 7081CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP)Current
November 2013
- RFC 6849An Extension to the Session Description Protocol (SDP) and Real-time Transport Protocol (RTP) for Media LoopbackCurrent
February 2013
- RFC 6416RTP Payload Format for MPEG-4 Audio/Visual StreamsCurrent
October 2011
- RFC 6381The 'Codecs' and 'Profiles' Parameters for "Bucket" Media TypesCurrent
August 2011
- RFC 6185RTP Payload Format for H.264 Reduced-Complexity Decoding Operation (RCDO) VideoCurrent
May 2011
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?