RTP Payload Format for High Efficiency Video Coding (HEVC)
RFC 7798

Document Type RFC - Proposed Standard (March 2016; No errata)
Last updated 2016-03-22
Replaces draft-schierl-payload-rtp-h265
Stream IETF
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Roni Even
Shepherd write-up Show (last changed 2014-09-13)
IESG IESG state RFC 7798 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Ben Campbell
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                        Y.-K. Wang
Request for Comments: 7798                                      Qualcomm
Category: Standards Track                                     Y. Sanchez
ISSN: 2070-1721                                               T. Schierl
                                                          Fraunhofer HHI
                                                               S. Wenger
                                                                   Vidyo
                                                        M. M. Hannuksela
                                                                   Nokia
                                                              March 2016

       RTP Payload Format for High Efficiency Video Coding (HEVC)

Abstract

   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7798.

Wang, et al.                 Standards Track                    [Page 1]
RFC 7798               RTP Payload Format for HEVC            March 2016

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Introduction ....................................................3
      1.1. Overview of the HEVC Codec .................................4
           1.1.1. Coding-Tool Features ................................4
           1.1.2. Systems and Transport Interfaces ....................6
           1.1.3. Parallel Processing Support ........................11
           1.1.4. NAL Unit Header ....................................13
      1.2. Overview of the Payload Format ............................14
   2. Conventions ....................................................15
   3. Definitions and Abbreviations ..................................15
      3.1. Definitions ...............................................15
           3.1.1.  Definitions from the HEVC Specification ...........15
           3.1.2.  Definitions Specific to This Memo .................17
      3.2. Abbreviations .............................................19
   4. RTP Payload Format .............................................20
      4.1. RTP Header Usage ..........................................20
      4.2. Payload Header Usage ......................................22
      4.3. Transmission Modes ........................................23
      4.4. Payload Structures ........................................24
           4.4.1. Single NAL Unit Packets ............................24
           4.4.2. Aggregation Packets (APs) ..........................25
           4.4.3. Fragmentation Units ................................29
           4.4.4. PACI Packets .......................................32
                  4.4.4.1. Reasons for the PACI Rules (Informative) ..34
                  4.4.4.2. PACI Extensions (Informative) .............35
Show full document text