Re: [xrblock] after the IPR Disclosure related to draft-ietf-xrblock-rtcp-xr-video-lc

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Fri, 08 January 2016 03:25 UTC

Return-Path: <rachel.huang@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFCD21ACCEF for <xrblock@ietfa.amsl.com>; Thu, 7 Jan 2016 19:25:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.229
X-Spam-Level:
X-Spam-Status: No, score=0.229 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, 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 SPz5QG4kCmV4 for <xrblock@ietfa.amsl.com>; Thu, 7 Jan 2016 19:25:46 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91BEA1ACCED for <xrblock@ietf.org>; Thu, 7 Jan 2016 19:25:44 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CGM99014; Fri, 08 Jan 2016 03:25:41 +0000 (GMT)
Received: from LHREML706-CAH.china.huawei.com (10.201.5.182) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 8 Jan 2016 03:25:40 +0000
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 8 Jan 2016 03:25:40 +0000
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.252]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Fri, 8 Jan 2016 11:25:37 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: Alan Clark <alan.d.clark@telchemy.com>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: [xrblock] after the IPR Disclosure related to draft-ietf-xrblock-rtcp-xr-video-lc
Thread-Index: AdE38D9G6xGjB4mWRa6CeaSXXvzLEwPxHFnA///5lgCAATdsAIAAHA0A//1SepA=
Date: Fri, 8 Jan 2016 03:25:36 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB86E78FCC@nkgeml513-mbx.china.huawei.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA6BEC8D0F@AZ-FFEXMB04.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA6BEDD449@AZ-FFEXMB04.global.avaya.com> <568C223A.6050009@telchemy.com> <9904FB1B0159DA42B0B887B7FA8119CA6BEDE582@AZ-FFEXMB04.global.avaya.com> <568D3F00.7060609@telchemy.com>
In-Reply-To: <568D3F00.7060609@telchemy.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.46.4.48]
Content-Type: multipart/alternative; boundary="_000_51E6A56BD6A85142B9D172C87FC3ABBB86E78FCCnkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.568F2C36.0086, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.252, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: c20254af28a64de182d38f7c07084615
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/87YbPf88zpl5n8pGOmsPq4g-KvA>
Subject: Re: [xrblock] after the IPR Disclosure related to draft-ietf-xrblock-rtcp-xr-video-lc
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xrblock/>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2016 03:25:50 -0000

Hi all,

Sorry for the late response. I¡¯m in a business trip these two weeks with sporadic email access. So I may not respond timely.
This IPR is from another department so I¡¯m not quite familiar with it. I¡¯ll invite the colleague who¡¯s the IPR holder or responsible for the IPR disclosure to clarify in the mailing list. Hope we can find some way to solve this issue.

BR,
Rachel

·¢¼þÈË: xrblock [mailto:xrblock-bounces@ietf.org] ´ú±í Alan Clark
·¢ËÍʱ¼ä: 2016Äê1ÔÂ7ÈÕ 0:21
ÊÕ¼þÈË: Romascanu, Dan (Dan); xrblock@ietf.org<mailto:xrblock@ietf.org>
Ö÷Ìâ: Re: [xrblock] after the IPR Disclosure related to draft-ietf-xrblock-rtcp-xr-video-lc

Hi Dan

Within the IETF patent policy there is no requirement that I'm aware of that requires a disclosing company to prove that the patent they reference does in fact apply to the draft/RFC, which means that companies could make disclosure statements that don't actually apply to the referenced draft/RFC. In many larger companies the IPR/legal team may be distant from the engineering team and I've seen cases in which allegations of infringement were made based on a text match rather than a technical analysis. If, as WG members, we feel that a disclosure may be inappropriate based on a technical understanding of the draft/RFC and the patent then IMHO we should be willing to politely point this out - if the disclosing company wants to keep the disclosure anyway then we have to leave it to individual implementers to obtain their own legal advice; my view is that as WG members and authors we should try and keep the IPR situation as clear as possible.

I've encountered exactly this situation - my company develops software that analyzes voice/ audio/ video stream performance and as part of this we model the performance of a wide range of voice/ audio and video codecs. We have been contacted numerous times by companies that have codec IPR and who see that we analyze streams encoded with the G.xyz codec - we then have to explain that we don't actually implement the codec, only a parametric model.

So - my position is that we should ask Rachel, as an author and a representative of the disclosing company, to request that Huawei verify that their disclosure does, in their opinion, apply.

Regards

Alan

On 1/6/16 9:40 AM, Romascanu, Dan (Dan) wrote:
Hi Alan,

The statement that was posted a few weeks back explicitly refers to this I-D ¨C see https://datatracker.ietf.org/ipr/2725/. Of course, anybody can comment within the rules, but the fact that the disclosing company considers the IPR related to this I-D is public information.

What is your position as WG participant and as co-author of the document? What should the WG do?

Thanks and Regards,

Dan



From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of Alan Clark
Sent: Tuesday, January 05, 2016 10:06 PM
To: xrblock@ietf.org<mailto:xrblock@ietf.org>
Subject: Re: [xrblock] after the IPR Disclosure related to draft-ietf-xrblock-rtcp-xr-video-lc

I reviewed the patent that the disclosure related to - this appears to describe a method for video coding that uses loss concealment and not a method of reporting the effectiveness of loss concealment. It is of course the responsibility of the IPR holder to verify that their patent does in fact apply to the Draft/RFC to which their disclosure statement applies.  I suggest that the WG chairs ask the participants from the disclosing company to check to see if this disclosure is in fact relevant to the draft.

Regards

Alan


On 1/5/16 7:34 AM, Romascanu, Dan (Dan) wrote:
Hi,

There were no responses to this query. Please express your opinions on the mail list whether we should continue as planned with the approval for this I-D.

Possible options (other may apply):


1.       Continue as planned

2.       Do not continue

3.       Continue, but first do ¡­

Thanks and Regards,

Dan


From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Wednesday, December 16, 2015 12:55 PM
To: xrblock@ietf.org<mailto:xrblock@ietf.org>
Subject: [xrblock] after the IPR Disclosure related to draft-ietf-xrblock-rtcp-xr-video-lc

Hi,


As you may have seen an IPR disclosure that pertains to draft-ietf-xrblock-rtcp-xr-video-lc was submitted recently. The announcement on the XRBLOCK mail list with  more information can be read at http://www.ietf.org/mail-archive/web/xrblock/current/msg01914.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ietf.org_mail-2Darchive_web_xrblock_current_msg01914.html&d=BQMFAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=JT0PNFMVTwcCOwfJFWR9rPXwWO3aXrz-8hcAnDMibu4&s=Y212mtSrLAN6yGGEigFnx-qwjZv_a0r5MpWucZswumg&e=>jZv_a0r5MpWucZswumg&e=>.



This I-D was on the agenda of the IESG telechat this Thursday 12/17. Our AD decided to defer this I-D to the next telechat scheduled for January 7, 2016 and asked us to confirm on the mail list that the WG still plans to proceed with the I-D.



Taking into account this new information ¨C do the participants in the WG want to proceed with the approval of this Internet-Draft? Please state your opinions on the WG mail list until Monday January 4, 2016.



Thanks and Regards,



Dan








_______________________________________________

xrblock mailing list

xrblock@ietf.org<mailto:xrblock@ietf.org>

https://www.ietf.org/mailman/listinfo/xrblock<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_xrblock&d=BQMD-g&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=QnXfHHtrCWuOTN6ltI1OQl5JKpT1vIEt5lm6yyUl-K0&s=ZDjj6FP8ei9wzWsi7L54u3cKecOhJxcBl4LP8yojwBQ&e=>