RFC 7798 on RTP Payload Format for High Efficiency Video Coding (HEVC)
rfc-editor@rfc-editor.org Wed, 23 March 2016 00:49 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AD0E12D1BF; Tue, 22 Mar 2016 17:49:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9VXbS8J36WTR; Tue, 22 Mar 2016 17:49:07 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DD2B12D0DA; Tue, 22 Mar 2016 17:49:06 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0DB6A180004; Tue, 22 Mar 2016 17:48:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7798 on RTP Payload Format for High Efficiency Video Coding (HEVC)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160323004858.0DB6A180004@rfc-editor.org>
Date: Tue, 22 Mar 2016 17:48:58 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/kgqtkSrBRiIGQLln-QSEw3CRM2A>
Cc: drafts-update-ref@iana.org, payload@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2016 00:49:09 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7798
Title: RTP Payload Format for High
Efficiency Video Coding (HEVC)
Author: Y.-K. Wang, Y. Sanchez,
T. Schierl, S. Wenger,
M. M. Hannuksela
Status: Standards Track
Stream: IETF
Date: March 2016
Mailbox: yekui.wang@gmail.com,
yago.sanchez@hhi.fraunhofer.de,
thomas.schierl@hhi.fraunhofer.de,
stewe@stewe.org,
miska.hannuksela@nokia.com
Pages: 86
Characters: 209680
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-payload-rtp-h265-15.txt
URL: https://www.rfc-editor.org/info/rfc7798
DOI: http://dx.doi.org/10.17487/RFC7798
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 stream as well as multiple RTP streams.
When multiple RTP streams are used, a single transport or multiple
transports may be utilized. The payload format has wide
applicability in videoconferencing, Internet video streaming, and
high-bitrate entertainment-quality video, among others.
This document is a product of the Audio/Video Transport Payloads Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC