[payload] FW: New Version Notification for draft-wenger-payload-h265-payload-header-extension-00.txt

Stephan Wenger <stewe@stewe.org> Thu, 26 September 2013 20:18 UTC

Return-Path: <stewe@stewe.org>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CF6821F9343 for <payload@ietfa.amsl.com>; Thu, 26 Sep 2013 13:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_EXTNSN=2.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uCMMRDv1oMFy for <payload@ietfa.amsl.com>; Thu, 26 Sep 2013 13:18:38 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0244.outbound.protection.outlook.com [207.46.163.244]) by ietfa.amsl.com (Postfix) with ESMTP id 8853A21E80B1 for <payload@ietf.org>; Thu, 26 Sep 2013 13:18:38 -0700 (PDT)
Received: from CO1PR07MB363.namprd07.prod.outlook.com (10.141.75.22) by CO1PR07MB362.namprd07.prod.outlook.com (10.141.75.21) with Microsoft SMTP Server (TLS) id 15.0.775.9; Thu, 26 Sep 2013 20:18:35 +0000
Received: from CO1PR07MB363.namprd07.prod.outlook.com ([169.254.3.183]) by CO1PR07MB363.namprd07.prod.outlook.com ([169.254.3.3]) with mapi id 15.00.0775.005; Thu, 26 Sep 2013 20:18:35 +0000
From: Stephan Wenger <stewe@stewe.org>
To: "payload@ietf.org" <payload@ietf.org>
Thread-Topic: New Version Notification for draft-wenger-payload-h265-payload-header-extension-00.txt
Thread-Index: AQHOuvWTBG5KaPm+6ESXmTTaE/l+pA==
Date: Thu, 26 Sep 2013 20:18:34 +0000
Message-ID: <CE69E255.A721B%stewe@stewe.org>
In-Reply-To: <20130926200808.29653.4083.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [71.202.147.60]
x-forefront-prvs: 0981815F2F
x-forefront-antispam-report: SFV:NSPM; SFS:(199002)(51704005)(189002)(24454002)(164054003)(377424004)(53754006)(77096001)(74502001)(50986001)(47976001)(49866001)(54356001)(56816003)(46102001)(81686001)(81816001)(76796001)(76176001)(76786001)(561944002)(4396001)(53806001)(47446002)(79102001)(56776001)(76482001)(77982001)(54316002)(63696002)(59766001)(31966008)(83072001)(74662001)(47736001)(65816001)(66066001)(36756003)(81342001)(69226001)(74876001)(74366001)(19580405001)(80976001)(80022001)(51856001)(81542001)(15975445006)(83322001)(74706001)(19580395003)(42262001); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR07MB362; H:CO1PR07MB363.namprd07.prod.outlook.com; CLIP:71.202.147.60; FPR:; RD:InfoNoRecords; A:0; MX:1; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-ID: <DF71865F5E25474386C7021AEA6775E3@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: Jonathan Lennox <jonathan@vidyo.com>, Jill Boyce <jill@vidyo.com>
Subject: [payload] FW: New Version Notification for draft-wenger-payload-h265-payload-header-extension-00.txt
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 26 Sep 2013 20:18:43 -0000

Hi all,

In Berlin's payload session presentation of the H.265 payload format
(graciously hosted by AVTcore), I mentioned that we want to include
support for temporal scalability in the draft H.265 payload format.
Attached a quick draft showing how this could be done--basically a (we
believe) improved variant of the PACSI NAL unit of RFC 6190.  There are
two alternative proposals in the draft, trading off alignment with design
principles of H.265 one one side and efficiency on the other.

Vidyo has IPR on this draft, which we will make available under terms like
this: https://datatracker.ietf.org/ipr/1622/.  I believe that the concepts
of this draft should be included in the H.265 payload format itself,
rather than being stand-alone.  Once that happens, or if the group decides
the draft to stay stand-alone, we will file the official IPR disclosure
against the then-current and appropriate document, so not to clutter the
database.  

Comments welcome.

Thanks,
Stephan



On 9.26.2013 13:08 , "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>A new version of I-D,
>draft-wenger-payload-h265-payload-header-extension-00.txt
>has been successfully submitted by Stephan Wenger and posted to the
>IETF repository.
>
>Filename:	 draft-wenger-payload-h265-payload-header-extension
>Revision:	 00
>Title:		 H.265 Payload Header Extension and Temporal Scalability Support
>Creation date:	 2013-09-26
>Group:		 Individual Submission
>Number of pages: 10
>URL:             
>http://www.ietf.org/internet-drafts/draft-wenger-payload-h265-payload-head
>er-extension-00.txt
>Status:          
>http://datatracker.ietf.org/doc/draft-wenger-payload-h265-payload-header-e
>xtension
>Htmlized:        
>http://tools.ietf.org/html/draft-wenger-payload-h265-payload-header-extens
>ion-00
>
>
>Abstract:
>   Proposed are the allocation of a NAL unit type from the
>   "unspecified" set of NAL units of H.265 [HEVC] for the purpose of
>   payload header extensions, a generic syntax for the use of that
>   pseudo NAL unit, and one application for it: the signaling of
>   temporal scalability support information.  Two alternative designs
>   are included.  The content of this draft is intended for
>   incorporation into the H.265 RTP payload [h265-payload].
>
>
>
>                  
>        
>
>
>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.
>
>The IETF Secretariat
>