Re: [payload] I-D Action: draft-ietf-payload-rtp-h265-08.txt

"Wang, Ye-Kui" <yekuiw@qti.qualcomm.com> Fri, 10 April 2015 23:35 UTC

Return-Path: <yekuiw@qti.qualcomm.com>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE3DD1B2EA7 for <payload@ietfa.amsl.com>; Fri, 10 Apr 2015 16:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.011
X-Spam-Level:
X-Spam-Status: No, score=-7.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 P2HFhQ8zCgYZ for <payload@ietfa.amsl.com>; Fri, 10 Apr 2015 16:35:42 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D0161B2E8F for <payload@ietf.org>; Fri, 10 Apr 2015 16:35:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1428708934; x=1460244934; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=6ORsLjNzS2sCfRGbR8EQvbSBRnD857BgwReMSPjyqNk=; b=a0MTslTAFdvwB79ujAvF3A0Bm4jYRW2KjisKovMhtiSlKyg4vEO/nWFD kOA8FDa9IWiquJhJGDi1cmzdIyZf50t8djrVH89R3BkK14n9+BsFAmhU9 JnySKUqyPH6INLHnfnVjQADu6gVovj8s9kccrN3tpnQWuMGn8iXuiwdhD g=;
X-IronPort-AV: E=McAfee;i="5700,7163,7767"; a="86728320"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by sabertooth01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Apr 2015 16:35:23 -0700
X-IronPort-AV: E=Sophos;i="5.11,559,1422950400"; d="scan'208";a="892242526"
Received: from nasanexm01b.na.qualcomm.com ([10.85.0.82]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 10 Apr 2015 16:35:23 -0700
Received: from NASANEXM01H.na.qualcomm.com (10.85.0.34) by NASANEXM01B.na.qualcomm.com (10.85.0.82) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Fri, 10 Apr 2015 16:35:23 -0700
Received: from NASANEXM01H.na.qualcomm.com ([10.85.0.34]) by NASANEXM01H.na.qualcomm.com ([10.85.0.34]) with mapi id 15.00.1044.021; Fri, 10 Apr 2015 16:35:23 -0700
From: "Wang, Ye-Kui" <yekuiw@qti.qualcomm.com>
To: "payload@ietf.org" <payload@ietf.org>
Thread-Topic: [payload] I-D Action: draft-ietf-payload-rtp-h265-08.txt
Thread-Index: AQHQc+RjceP5zldIe0mPqRLfsaLVl51G49ww
Date: Fri, 10 Apr 2015 23:35:22 +0000
Message-ID: <d13fede5e8184365a826b84be0176619@NASANEXM01H.na.qualcomm.com>
References: <20150410231601.909.23579.idtracker@ietfa.amsl.com>
In-Reply-To: <20150410231601.909.23579.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.80.80.8]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/payload/ugj4Pe72unRKFYWczjN97_NMfNM>
Subject: Re: [payload] I-D Action: draft-ietf-payload-rtp-h265-08.txt
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/payload/>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 23:35:45 -0000

This version ONLY includes a technical change that was proposed by Mo Zanaty and Stephan Wenger, to enable de-packetization of multiple received RTP streams based on NTP timestamps instead of on decoding order numbers. The proponents and the authors (with Stephan being both) discussed and worked out the text changes together, targeting enabling the feature with minimal text changes.

Please review and let us know if you have any comments on these changes.

Next, we will make all the editorial changes agreed earlier on the reflector in discussing Richard Barnes' AD review, as soon as possible.

BR, YK

-----Original Message-----
From: payload [mailto:payload-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Friday, April 10, 2015 4:16 PM
To: i-d-announce@ietf.org
Cc: payload@ietf.org
Subject: [payload] I-D Action: draft-ietf-payload-rtp-h265-08.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Audio/Video Transport Payloads Working Group of the IETF.

        Title           : RTP Payload Format for High Efficiency Video Coding
        Authors         : Ye-Kui Wang
                          Yago Sanchez
                          Thomas Schierl
                          Stephan Wenger
                          Miska M. Hannuksela
	Filename        : draft-ietf-payload-rtp-h265-08.txt
	Pages           : 101
	Date            : 2015-04-10

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.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-payload-rtp-h265/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-payload-rtp-h265-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-payload-rtp-h265-08


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
payload mailing list
payload@ietf.org
https://www.ietf.org/mailman/listinfo/payload