RTP Payload Format for Essential Video Coding (EVC)
draft-ietf-avtcore-rtp-evc-00

Document Type Active Internet-Draft (avtcore WG)
Authors Shuai Zhao  , Stephan Wenger 
Last updated 2021-01-03
Stream IETF
Intended RFC status (None)
Formats plain text xml 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: 11 June 2021                                    8 December 2020

          RTP Payload Format for Essential Video Coding (EVC)
                     draft-ietf-avtcore-rtp-evc-00

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 11 June 2021.

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 to this document.  Code Components

Zhao & Wenger             Expires 11 June 2021                  [Page 1]
Internet-Draft         RTP payload format for EVC          December 2020

   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  . . . . . . . . . . . . . . . . . . . .  15
     4.2.  Payload Header Usage  . . . . . . . . . . . . . . . . . .  16
     4.3.  Payload Structures  . . . . . . . . . . . . . . . . . . .  17
       4.3.1.  Single NAL Unit Packets . . . . . . . . . . . . . . .  17
       4.3.2.  Aggregation Packets (APs) . . . . . . . . . . . . . .  18
       4.3.3.  Fragmentation Units . . . . . . . . . . . . . . . . .  22
     4.4.  Decoding Order Number . . . . . . . . . . . . . . . . . .  25
   5.  Packetization Rules . . . . . . . . . . . . . . . . . . . . .  26
   6.  De-packetization Process  . . . . . . . . . . . . . . . . . .  27
   7.  Payload Format Parameters . . . . . . . . . . . . . . . . . .  29
     7.1.  Media Type Registration . . . . . . . . . . . . . . . . .  29
     7.2.  SDP Parameters  . . . . . . . . . . . . . . . . . . . . .  29
       7.2.1.  Mapping of Payload Type Parameters to SDP . . . . . .  29
       7.2.2.  Usage with SDP Offer/Answer Model . . . . . . . . . .  30
       7.2.3.  SDP Example . . . . . . . . . . . . . . . . . . . . .  30
   8.  Use with Feedback Messages  . . . . . . . . . . . . . . . . .  30
     8.1.  Picture Loss Indication (PLI) . . . . . . . . . . . . . .  30
     8.2.  Full Intra Request (FIR)  . . . . . . . . . . . . . . . .  30
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  30
Show full document text