RTP Payload Format for VC-2 High Quality (HQ) Profile
RFC 8450
Document | Type | RFC - Proposed Standard (October 2018; No errata) | |
---|---|---|---|
Author | James Weaver | ||
Last updated | 2018-12-19 | ||
Replaces | draft-weaver-payload-rtp-vc2hq | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Ali Begen | ||
Shepherd write-up | Show (last changed 2018-01-23) | ||
IESG | IESG state | RFC 8450 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Ben Campbell | ||
Send notices to | ali.begen@networked.media | ||
IANA | IANA review state | IANA OK - Actions Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) J. Weaver Request for Comments: 8450 BBC Category: Standards Track October 2018 ISSN: 2070-1721 RTP Payload Format for VC-2 High Quality (HQ) Profile Abstract This memo describes an RTP payload format for the High Quality (HQ) profile of Society of Motion Picture and Television Engineers 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 is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8450. Weaver Standards Track [Page 1] RFC 8450 VC-2 HQ RTP Payload October 2018 Copyright Notice Copyright (c) 2018 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 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 2. Conventions, Definitions, and Acronyms . . . . . . . . . . . 3 3. Media Format Description . . . . . . . . . . . . . . . . . . 3 4. Payload Format . . . . . . . . . . . . . . . . . . . . . . . 4 4.1. RTP Header Usage . . . . . . . . . . . . . . . . . . . . 10 4.2. Payload Header . . . . . . . . . . . . . . . . . . . . . 11 4.3. The Choice of Parse Codes (Informative) . . . . . . . . . 13 4.4. Stream Constraints . . . . . . . . . . . . . . . . . . . 14 4.5. Payload Data . . . . . . . . . . . . . . . . . . . . . . 15 4.5.1. Reassembling the Data . . . . . . . . . . . . . . . . 16 5. Forward Error Correction (FEC) Considerations . . . . . . . . 18 6. Congestion Control Considerations . . . . . . . . . . . . . . 18 7. Payload Format Parameters . . . . . . . . . . . . . . . . . . 19 7.1. Media Type Definition . . . . . . . . . . . . . . . . . . 19 7.2. Mapping to the Session Description Protocol (SDP) . . . . 21 7.3. Offer/Answer Considerations . . . . . . . . . . . . . . . 21 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 9. Security Considerations . . . . . . . . . . . . . . . . . . . 21 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 10.1. Normative References . . . . . . . . . . . . . . . . . . 22 10.2. Informative References . . . . . . . . . . . . . . . . . 23 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 24 Weaver Standards Track [Page 2] RFC 8450 VC-2 HQ RTP Payload October 2018 1. Introduction This memo specifies an RTP payload format for the video coding standard Society of Motion Picture and Television Engineers ST 2042-1:2017 [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 have a low level of complexity and potentially 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 similarShow full document text