Submit an Internet-Draft

idnits 2.17.00 (12 Aug 2021)

/a/www/www6s/staging/draft-ietf-avtcore-rtp-v3c-00.txt:

  Showing Errors (**), Flaws (~~), Warnings (==), and Comments (--).
  Errors MUST be fixed before draft submission.  Flaws SHOULD be fixed before draft submission.

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  https://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

     No issues found here.

  Running in submission checking mode -- *not* checking nits according to
  https://www.ietf.org/id-info/checklist .
  ----------------------------------------------------------------------------


     No nits found.

avtcore                                                         L. Ilola
Internet-Draft                                                L. Kondrad
Intended status: Standards Track                      Nokia Technologies
Expires: 12 May 2023                                     8 November 2022


   RTP Payload Format for Visual Volumetric Video-based Coding (V3C)
                     draft-ietf-avtcore-rtp-v3c-00

Abstract

   This memo describes an RTP payload format for visual volumetric
   video-based coding (V3C) [ISO.IEC.23090-5].  A V3C bitstream is
   composed of V3C units that contain V3C video sub-bitstreams, V3C
   atlas sub-bitstreams, or a V3C parameter set.  The RTP payload format
   for V3C video sub-bitstreams is defined by appropriate Internet
   Standards for the applicable video codec.  The RTP payload format for
   V3C atlas sub-bitstreams is described by this memo.  The RTP payload
   format allows for packetization of one or more V3C Network
   Abstraction Layer (NAL) units in a RTP packet payload as well as
   fragmentation of a V3C NAL unit into multiple RTP packets.  The memo
   also describes the mechanisms for grouping RTP streams of V3C
   component sub-bitstreams, providing a complete solution for streaming
   V3C bitstream.

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 12 May 2023.

Copyright Notice

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





Ilola & Kondrad            Expires 12 May 2023                  [Page 1]
Internet-Draft         RTP payload format for V3C          November 2022


   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
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Definitions, and Abbreviations  . . . . . . . . . . . . . . .   4
     3.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   4
       3.1.1.  General . . . . . . . . . . . . . . . . . . . . . . .   4
       3.1.2.  Definitions from the V3C Specification  . . . . . . .   4
       3.1.3.  Definitions Specific to This Memo . . . . . . . . . .   6
     3.2.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Media Format Description  . . . . . . . . . . . . . . . . . .   6
     4.1.  Overview of the V3C codec . . . . . . . . . . . . . . . .   7
     4.2.  V3C parameter set . . . . . . . . . . . . . . . . . . . .   8
     4.3.  V3C atlas and video components  . . . . . . . . . . . . .   8
       4.3.1.  General . . . . . . . . . . . . . . . . . . . . . . .   8
       4.3.2.  Atlas NAL units . . . . . . . . . . . . . . . . . . .  11
     4.4.  Systems and transport interfaces  . . . . . . . . . . . .  12
   5.  V3C Atlas RTP payload format  . . . . . . . . . . . . . . . .  12
     5.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .  12
     5.2.  RTP Header  . . . . . . . . . . . . . . . . . . . . . . .  12
     5.3.  RTP payload header  . . . . . . . . . . . . . . . . . . .  14
     5.4.  Transmission modes  . . . . . . . . . . . . . . . . . . .  15
     5.5.  Payload structures  . . . . . . . . . . . . . . . . . . .  15
       5.5.1.  General . . . . . . . . . . . . . . . . . . . . . . .  16
       5.5.2.  Single NAL unit packet  . . . . . . . . . . . . . . .  16
       5.5.3.  Aggregation packet  . . . . . . . . . . . . . . . . .  18
       5.5.4.  Fragmentation unit  . . . . . . . . . . . . . . . . .  20
     5.6.  Decoding Order Number . . . . . . . . . . . . . . . . . .  22
   6.  Packetization and de-packetization rules  . . . . . . . . . .  23
   7.  Payload Examples  . . . . . . . . . . . . . . . . . . . . . .  24
     7.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .  24
     7.2.  V3C fragmentation unit  . . . . . . . . . . . . . . . . .  24
   8.  Payload Format Parameters . . . . . . . . . . . . . . . . . .  26
     8.1.  Media Type Definition . . . . . . . . . . . . . . . . . .  26
   9.  Congestion Control Considerations . . . . . . . . . . . . . .  30
   10. Session Description Protocol  . . . . . . . . . . . . . . . .  30
     10.1.  Mapping of payload type parameters to SDP  . . . . . . .  30
       10.1.1.  For V3C atlas components . . . . . . . . . . . . . .  30
       10.1.2.  For V3C video components . . . . . . . . . . . . . .  31



Ilola & Kondrad            Expires 12 May 2023                  [Page 2]