RTP Payload Format for Versatile Video Coding (VVC)
draft-ietf-avtcore-rtp-vvc-01

Document Type Active Internet-Draft (avtcore WG)
Last updated 2020-03-30
Replaces draft-zhao-avtcore-rtp-vvc
Stream IETF
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
avtcore                                                          S. Zhao
Internet-Draft                                                 S. Wenger
Intended status: Standards Track                                 Tencent
Expires: October 1, 2020                                      Y. Sanchez
                                                          Fraunhofer HHI
                                                          March 30, 2020

          RTP Payload Format for Versatile Video Coding (VVC)
                     draft-ietf-avtcore-rtp-vvc-01

Abstract

   This memo describes an RTP payload format for the video coding
   standard ITU-T Recommendation [H.266] and ISO/IEC International
   Standard [ISO23090-3], both also known as Versatile Video Coding
   (VVC) and 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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 1, 2020.

Copyright Notice

   Copyright (c) 2020 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

Zhao, et al.             Expires October 1, 2020                [Page 1]
Internet-Draft         RTP payload format for VVC             March 2020

   (https://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 VVC Codec . . . . . . . . . . . . . . . .   3
       1.1.1.  Coding-Tool Features (informative)  . . . . . . . . .   3
       1.1.2.  Systems and Transport Interfaces  . . . . . . . . . .   6
       1.1.3.  Parallel Processing Support (informative) . . . . . .  10
       1.1.4.  NAL Unit Header . . . . . . . . . . . . . . . . . . .  10
     1.2.  Overview of the Payload Format  . . . . . . . . . . . . .  12
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .  12
   3.  Definitions and Abbreviations . . . . . . . . . . . . . . . .  12
     3.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .  12
       3.1.1.  Definitions from the VVC Specification  . . . . . . .  13
       3.1.2.  Definitions Specific to This Memo . . . . . . . . . .  16
     3.2.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .  16
   4.  RTP Payload Format  . . . . . . . . . . . . . . . . . . . . .  17
     4.1.  RTP Header Usage  . . . . . . . . . . . . . . . . . . . .  18
     4.2.  Payload Header Usage  . . . . . . . . . . . . . . . . . .  19
     4.3.  Payload Structures  . . . . . . . . . . . . . . . . . . .  20
       4.3.1.  Single NAL Unit Packets . . . . . . . . . . . . . . .  20
       4.3.2.  Aggregation Packets (APs) . . . . . . . . . . . . . .  21
       4.3.3.  Fragmentation Units . . . . . . . . . . . . . . . . .  25
     4.4.  Decoding Order Number . . . . . . . . . . . . . . . . . .  28
   5.  Packetization Rules . . . . . . . . . . . . . . . . . . . . .  29
   6.  De-packetization Process  . . . . . . . . . . . . . . . . . .  30
   7.  Payload Format Parameters . . . . . . . . . . . . . . . . . .  32
   8.  Use with Feedback Messages  . . . . . . . . . . . . . . . . .  32
     8.1.  Picture Loss Indication (PLI) . . . . . . . . . . . . . .  32
     8.2.  Slice Loss Indication (SLI) . . . . . . . . . . . . . . .  32
     8.3.  Reference Picture Selection Indication (RPSI) . . . . . .  33
     8.4.  Full Intra Request (FIR)  . . . . . . . . . . . . . . . .  33
   9.  Frame marking . . . . . . . . . . . . . . . . . . . . . . . .  33
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  33
Show full document text