Re: [payload] I-D Action: draft-ietf-payload-rtp-h265-07.txt
"Wang, Ye-Kui" <yekuiw@qti.qualcomm.com> Mon, 08 December 2014 22:06 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 3237E1A88B5 for <payload@ietfa.amsl.com>; Mon, 8 Dec 2014 14:06:55 -0800 (PST)
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 QWQaYRI540g8 for <payload@ietfa.amsl.com>; Mon, 8 Dec 2014 14:06:52 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 558B61A1B8D for <payload@ietf.org>; Mon, 8 Dec 2014 14:06:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1418076412; x=1449612412; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=+OPI01RLhFSupm0TO8sTb1P5K7+LOQtJopNpuPvxing=; b=ZznOfLF7iLBY3yjq3P+B5FVqSK3nZwXzQJXCYOeratgaSMRzwDKv2M5l yXDe1MiZTVII6FtMy2fOJ2xOPogLJELIiihhlmm2I6gTBDmS4BtPCbWLC h4cp/xdZKk7q7DiAbX2HEwRhgLirsEhbDeqAaorvrJUKcFw3lw9Edi1uk E=;
X-IronPort-AV: E=McAfee;i="5600,1067,7646"; a="80428982"
Received: from ironmsg06-lv.qualcomm.com ([10.47.202.185]) by sabertooth02.qualcomm.com with ESMTP; 08 Dec 2014 14:06:51 -0800
X-IronPort-AV: E=Sophos;i="5.07,540,1413270000"; d="scan'208";a="16705342"
Received: from nalasexr01e.na.qualcomm.com ([10.49.56.51]) by Ironmsg06-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 08 Dec 2014 14:06:51 -0800
Received: from NALASEXR01H.na.qualcomm.com (10.49.56.54) by nalasexr01e.na.qualcomm.com (10.49.56.51) with Microsoft SMTP Server (TLS) id 15.0.913.22; Mon, 8 Dec 2014 14:06:29 -0800
Received: from NALASEXR01H.na.qualcomm.com ([10.49.56.54]) by NALASEXR01H.na.qualcomm.com ([10.49.56.54]) with mapi id 15.00.0913.011; Mon, 8 Dec 2014 14:06:17 -0800
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-07.txt
Thread-Index: AQHQEzCWbH7+OTMcD0G8I+ezrcWVb5yGOtwQ
Date: Mon, 08 Dec 2014 22:06:17 +0000
Message-ID: <27a957b15c0e4d448cdc0069d0d0a810@NALASEXR01H.na.qualcomm.com>
References: <20141208214712.10744.43119.idtracker@ietfa.amsl.com>
In-Reply-To: <20141208214712.10744.43119.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.70.6]
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/OpTifk1vbjpZXdorKXJ9IRvNNcY
Subject: Re: [payload] I-D Action: draft-ietf-payload-rtp-h265-07.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: Mon, 08 Dec 2014 22:06:55 -0000
Compared to version -06, the changes are as follows: - Aligned some terminology with I-D.ietf-avtcore-rtp-multi-stream, I-D.ietf-mmusic-sdp-bundle-negotiation, and I-D.ietf-avtext-rtp-grouping-taxonomy, particularly including the use of the following: MRMT Multiple RTP streams on Multiple Transports MRST Multiple RTP streams on a Single Transport SRST Single RTP stream on a Single Transport - Clarified that the use of MRST with SDP Offer/Answer is currently not fully specified, and in particular currently MRST can only be used only when the RTP streams utilize distinct payload types, and more options would be available when the RFCs for [I-D.ietf-avtcore-rtp-multi-stream] and [I-D.ietf-mmusic-sdp-bundle-negotiation] are available. - Clarified that the required support of MRMT by receivers does not imply that multicast must be supported by receivers. - Other minor editorial clarifications. The authors would like to particularly thank Bernard Aboba for his valuable and constructive suggestions. BR, YK -----Original Message----- From: payload [mailto:payload-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: Monday, December 08, 2014 1:47 PM To: i-d-announce@ietf.org Cc: payload@ietf.org Subject: [payload] I-D Action: draft-ietf-payload-rtp-h265-07.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-07.txt Pages : 100 Date : 2014-12-08 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-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-payload-rtp-h265-07 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
- [payload] I-D Action: draft-ietf-payload-rtp-h265… internet-drafts
- Re: [payload] I-D Action: draft-ietf-payload-rtp-… Wang, Ye-Kui