RTP Payload Format for High Efficiency Video Coding
draft-ietf-payload-rtp-h265-08
Network Working Group Y.-K. Wang
Internet Draft Qualcomm
Intended status: Standards track Y. Sanchez
Expires: October 2015 T. Schierl
Fraunhofer HHI
S. Wenger
Vidyo
M. M. Hannuksela
Nokia
April 10, 2015
RTP Payload Format for High Efficiency Video Coding
draft-ietf-payload-rtp-h265-08.txt
Abstract
This memo describes an RTP payload format for the video coding
standard ITU-T Recommendation H.265 and ISO/IEC International
Standard 23008-2, both also known as High Efficiency Video Coding
(HEVC) and developed by the Joint Collaborative Team on Video
Coding (JCT-VC). 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. Furthermore, it supports transmission of
an HEVC bitstream over a single as well as multiple RTP streams.
When multiple RTP streams are used, a single or multiple
transports may be utilized. The payload format has wide
applicability in videoconferencing, Internet video streaming, and
high bit-rate entertainment-quality video, among others.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79.
Wang, et al Expires October 10, 2015 [Page 1]
Internet-Draft RTP Payload Format for HEVC April 10, 2015
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 10, 2015.
Copyright and License Notice
Copyright (c) 2015 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 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.
Wang, et al Expires October 10, 2015 [Page 2]
Internet-Draft RTP Payload Format for HEVC April 10, 2015
Table of Contents
Abstract.........................................................1
Status of this Memo..............................................1
Table of Contents................................................3
1 Introduction...................................................5
1.1 Overview of the HEVC Codec................................5
1.1.1 Coding-Tool Features.................................5
1.1.2 Systems and Transport Interfaces.....................7
1.1.3 Parallel Processing Support.........................14
1.1.4 NAL Unit Header.....................................16
1.2 Overview of the Payload Format...........................18
2 Conventions...................................................18
3 Definitions and Abbreviations.................................19
3.1 Definitions..............................................19
3.1.1 Definitions from the HEVC Specification.............19
3.1.2 Definitions Specific to This Memo...................21
3.2 Abbreviations............................................23
4 RTP Payload Format............................................25
4.1 RTP Header Usage.........................................25
4.2 Payload Header Usage.....................................27
4.3 Payload Structures.......................................27
Show full document text