IETF Logo Mail Archive

Re: [Pce] IPR on draft-ietf-pce-rfc6006bis

Dhruv Dhody <dhruv.dhody@huawei.com> Mon, 24 April 2017 15:38 UTC

Return-Path: <dhruv.dhody@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56961131730; Mon, 24 Apr 2017 08:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 2fIbqqZpAv_V; Mon, 24 Apr 2017 08:38:46 -0700 (PDT)
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 73A9C129557; Mon, 24 Apr 2017 08:38:45 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DFK90953; Mon, 24 Apr 2017 15:38:43 +0000 (GMT)
Received: from BLREML405-HUB.china.huawei.com (10.20.4.41) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 24 Apr 2017 16:38:41 +0100
Received: from BLREML501-MBB.china.huawei.com ([10.20.5.200]) by BLREML405-HUB.china.huawei.com ([10.20.4.41]) with mapi id 14.03.0301.000; Mon, 24 Apr 2017 21:08:28 +0530
From: Dhruv Dhody <dhruv.dhody@huawei.com>
To: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>, "draft-ietf-pce-rfc6006bis@ietf.org" <draft-ietf-pce-rfc6006bis@ietf.org>
CC: "pce@ietf.org" <pce@ietf.org>
Thread-Topic: IPR on draft-ietf-pce-rfc6006bis
Thread-Index: AdKx68AoklYGDFcxQ0CNG+sbXZs/yALJNPwA
Date: Mon, 24 Apr 2017 15:38:27 +0000
Message-ID: <23CE718903A838468A8B325B80962F9B8CACDD44@blreml501-mbb>
References: <BY2PR0201MB1910F4126306434397A0BF6A84010@BY2PR0201MB1910.namprd02.prod.outlook.com>
In-Reply-To: <BY2PR0201MB1910F4126306434397A0BF6A84010@BY2PR0201MB1910.namprd02.prod.outlook.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.195.40.44]
Content-Type: multipart/alternative; boundary="_000_23CE718903A838468A8B325B80962F9B8CACDD44blreml501mbb_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.58FE1C03.0154, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: e0277bffc0c3e46d0c8e1b3d99f34cbe
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/RZnxlrEPU2RSnpbrTD8FpKfY-IQ>
Subject: Re: [Pce] IPR on draft-ietf-pce-rfc6006bis
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 15:38:53 -0000

Hi,

Yes, I am aware of IPR and has been disclosed and updated in the IPR system.

Regards,
Dhruv

From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Jonathan Hardwick
Sent: 10 April 2017 17:10
To: draft-ietf-pce-rfc6006bis@ietf.org
Cc: pce@ietf.org
Subject: [Pce] IPR on draft-ietf-pce-rfc6006bis

Hi authors

I have a few actions that I need you to take on IPR before I can submit this draft for publication.

I see that there were two IPR disclosures against RFC 6006.  I assume that these also apply to draft-ietf-pce-rfc6006bis.  Please could you update the IPR system to reflect that?

Please could you confirm whether you are aware of any other IPR that applies to this draft, and if so, that a disclosure has been made?

When I run idnits on the draft, it spits out this warning:

== The document seems to contain a disclaimer for pre-RFC5378 work, but was
     first submitted on or after 10 November 2008.  The disclaimer is usually
     necessary only for documents that revise or obsolete older RFCs, and that
     take significant amounts of text from those RFCs.  If you can contact all
     authors of the source material and they are willing to grant the BCP78
     rights to the IETF Trust, you can and should remove the disclaimer.
     Otherwise, the disclaimer is needed and you can ignore this comment.
     (See the Legal Provisions document at
     http://trustee.ietf.org/license-info for more information.)

Please could you each confirm that you are willing to grant the BCP78 rights to the IETF trust?  Then we can remove the boilerplate and squash the warning.

Please CC the PCE mailing list with your replies.

Best regards
Jon

v2.23.0 | Report a Bug | By Email