IETF Logo Mail Archive

Re: [payload] Stephen Farrell's Discuss on draft-ietf-payload-rtp-h265-14: (with DISCUSS and COMMENT)

"Wang, Ye-Kui" <yekuiw@qti.qualcomm.com> Wed, 02 September 2015 22:52 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 2EA6B1B3959; Wed, 2 Sep 2015 15:52:04 -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 VzVY2H_Tv87B; Wed, 2 Sep 2015 15:51:58 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F29871B5858; Wed, 2 Sep 2015 15:50:54 -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=1441234254; x=1472770254; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=vNM3zfttx/+DH/YKRy5aEXBKvCxA6IJ0ONVz0c+BFBY=; b=fu41/vVoOhk3Ob0af3f/+v+BwmuYDCjEsV2Y2iuXG85lLa8UJvfh57Hf 0cSayUezaXAXBNKPUn+W9Odjk+aWBy0psJ0L4D4QufNX+/F8koFcLpuYT zHGABHSmeFYNGYaAC8UsayJ2HRjXLetXJYjuEM+jhPglPCAabuBybva36 4=;
X-IronPort-AV: E=McAfee;i="5700,7163,7912"; a="136467715"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by wolverine01.qualcomm.com with ESMTP; 02 Sep 2015 15:50:54 -0700
X-IronPort-AV: E=Sophos;i="5.17,457,1437462000"; d="scan'208";a="33568326"
Received: from nalasexr01d.na.qualcomm.com ([10.49.56.24]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 02 Sep 2015 15:50:52 -0700
Received: from NALASEXR01H.na.qualcomm.com (10.49.56.54) by NALASEXR01D.na.qualcomm.com (10.49.56.24) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Wed, 2 Sep 2015 15:50:52 -0700
Received: from NALASEXR01H.na.qualcomm.com ([10.49.56.54]) by NALASEXR01H.na.qualcomm.com ([10.49.56.54]) with mapi id 15.00.1076.010; Wed, 2 Sep 2015 15:50:52 -0700
From: "Wang, Ye-Kui" <yekuiw@qti.qualcomm.com>
To: Ben Campbell <ben@nostrum.com>, "payload-chairs@ietf.org" <payload-chairs@ietf.org>, "payload@ietf.org" <payload@ietf.org>, "draft-ietf-payload-rtp-h265@ietf.org" <draft-ietf-payload-rtp-h265@ietf.org>
Thread-Topic: Stephen Farrell's Discuss on draft-ietf-payload-rtp-h265-14: (with DISCUSS and COMMENT)
Thread-Index: AQHQ5bvQ644RVKsMa0q9W3NeNKDIGZ4p1tQQ
Date: Wed, 02 Sep 2015 22:50:51 +0000
Message-ID: <7716c02481654eed90dc8ff754efb7b3@NALASEXR01H.na.qualcomm.com>
References: <20150901124947.6862.19178.idtracker@ietfa.amsl.com> <3145A183-A9DA-47FD-A8F3-2708365D7FFD@nostrum.com>
In-Reply-To: <3145A183-A9DA-47FD-A8F3-2708365D7FFD@nostrum.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.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/26AYoa6MENV2OjyZNnEmmQikknc>
Cc: "art-ads@ietf.org" <art-ads@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [payload] Stephen Farrell's Discuss on draft-ietf-payload-rtp-h265-14: (with DISCUSS and COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Sep 2015 22:52:04 -0000

Hi Ben, All,

The authors are discussing on how to address Stephen Farrell's DISCUSS and Barry Leiba's comments. We will send our collectively responses once they are ready. 

However, for the one related to the Nokia IPR statement, per Miska Hannuksela, the co-author who works for Nokia, the (so-called late) Nokia IPR statement (http://datatracker.ietf.org/ipr/2508/) re-iterates the IPR statement that was submitted against draft-schierl-payload-rtp-h265 (https://datatracker.ietf.org/ipr/1753/). Hence, the WG should have been aware of the situation since 00 version of the Schierl draft.

I therefore request to check whether it is possible not to delay the progress of this document because of this. Thanks!

BR, YK

-----Original Message-----
From: Ben Campbell [mailto:ben@nostrum.com] 
Sent: Wednesday, September 02, 2015 1:13 PM
To: payload-chairs@ietf.org; payload@ietf.org; draft-ietf-payload-rtp-h265@ietf.org
Cc: art-ads@ietf.org; Stephen Farrell
Subject: Re: Stephen Farrell's Discuss on draft-ietf-payload-rtp-h265-14: (with DISCUSS and COMMENT)

Hi,

Stephen's discuss item 2 pointed out that we had a late IPR disclosure on this draft after the publication request. I am in discussions with the chairs on how to handle this.  I have removed it from the agenda for the September 3 telechat. I hope to put it on a future telechat once we agree on a way forward.

Thanks!

Ben.

On 1 Sep 2015, at 7:49, Stephen Farrell wrote:

> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------

[...]

>
>
> (2) This is just a process nit probably. The shepherd write-up doesn't 
> mention the Nokia IPR declaration.  Were the WG also ok with that one? 
> The write-up seems to pre-date that latest IPR declaration, which is 
> from a company that seems to employ one of the authors. That is odd 
> timing really so can someone explain the sequence of events and why 
> all is well?

[...]

v2.23.0 | Report a Bug | By Email