RTP Payload Format for Essential Video Coding (EVC)
draft-zhao-avtcore-rtp-evc-01

Document Type Active Internet-Draft (individual)
Last updated 2020-03-11
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            S. Zhao
Internet-Draft                                                 S. Wenger
Intended status: Standards Track                                 Tencent
Expires: September 11, 2020                               March 10, 2020

          RTP Payload Format for Essential Video Coding (EVC)
                     draft-zhao-avtcore-rtp-evc-01

Abstract

   This memo describes an RTP payload format for the video coding
   standard ISO/IEC International Standard 23094-1 [ISO23094-1], also
   known as Essential Video Coding [EVC] and developed by ISO/IEC
   JTC1/SC29/WG11.  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 September 11, 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
   (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

Zhao & Wenger          Expires September 11, 2020               [Page 1]
Internet-Draft         RTP payload format for EVC             March 2020

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