RTP Payload Format for VC-2 HQ Profile Video
draft-ietf-payload-rtp-vc2hq-02

Document Type Active Internet-Draft (payload WG)
Last updated 2017-04-05
Replaces draft-weaver-payload-rtp-vc2hq
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state In WG Last Call (wg milestone: May 2017 - submit RTP Payload F... )
Document shepherd Ali Begen
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to ali.begen@networked.media
Payload Working Group                                          J. Weaver
Internet-Draft                                                       BBC
Intended status: Standards Track                           April 4, 2017
Expires: October 6, 2017

              RTP Payload Format for VC-2 HQ Profile Video
                    draft-ietf-payload-rtp-vc2hq-02

Abstract

   This memo describes an RTP Payload format for the High Quality (HQ)
   profile of SMPTE Standard ST 2042-1 known as VC-2.  This document
   describes the transport of HQ Profile VC-2 in RTP packets and has
   applications for low-complexity, high-bandwidth streaming of both
   lossless and lossy compressed video.

   The HQ profile of VC-2 is intended for low latency video compression
   (with latency potentially on the order of lines of video) at high
   data rates (with compression ratios on the order of 2:1 or 4:1).

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 http://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 6, 2017.

Copyright Notice

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

Weaver                   Expires October 6, 2017                [Page 1]
Internet-Draft              Abbreviated Title                 April 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions, Definitions and Acronyms . . . . . . . . . . . .   3
   3.  Media Format Description  . . . . . . . . . . . . . . . . . .   3
   4.  Payload format  . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  RTP Header Usage  . . . . . . . . . . . . . . . . . . . .   9
     4.2.  Payload Header  . . . . . . . . . . . . . . . . . . . . .  10
     4.3.  The Choice of Parse Codes (Informative) . . . . . . . . .  12
     4.4.  Payload Data  . . . . . . . . . . . . . . . . . . . . . .  12
       4.4.1.  Reassembling the Data . . . . . . . . . . . . . . . .  13
   5.  Congestion Control Considerations . . . . . . . . . . . . . .  14
   6.  Payload Format Parameters . . . . . . . . . . . . . . . . . .  15
     6.1.  Media Type Definition . . . . . . . . . . . . . . . . . .  15
     6.2.  Mapping to SDP  . . . . . . . . . . . . . . . . . . . . .  16
       6.2.1.  Offer/Answer Considerations . . . . . . . . . . . . .  16
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   9.  RFC Editor Considerations . . . . . . . . . . . . . . . . . .  17
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  17
     10.2.  Informative References . . . . . . . . . . . . . . . . .  18
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  19

1.  Introduction

   This memo specifies an RTP payload format for the video coding
   standard SMPTE ST 2042-1:2012 [VC2] also known as VC-2

   The VC-2 codec is a wavelet-based codec intended primarily for
   professional video use with high bit-rates and only low levels of
   compression.  It has been designed to be low-complexity, and
   potentially have a very low latency through both encoder and decoder:
   with some choices of parameters this latency may be as low as a few
   lines of video.

   The low level of complexity in the VC-2 codec allows for this low
   latency operation but also means that it lacks many of the more
   powerful compression techniques used in other codecs.  As such it is
   suitable for low compression ratios that produce coded data rates
   around half to a quarter of that of uncompressed video, at a similar
Show full document text