Re: [Pce] Last IPR check for draft-ietf-pce-stateful-pce-app

Dhruv Dhody <dhruv.dhody@huawei.com> Tue, 28 June 2016 14:31 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 712F712D1A6; Tue, 28 Jun 2016 07:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.646
X-Spam-Level:
X-Spam-Status: No, score=-5.646 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=-1.426, 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 UBYPiVFsz3o5; Tue, 28 Jun 2016 07:31:12 -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 1D2B812D181; Tue, 28 Jun 2016 07:31:10 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CMV00668; Tue, 28 Jun 2016 14:31:08 +0000 (GMT)
Received: from BLREML408-HUB.china.huawei.com (10.20.4.47) by lhreml708-cah.china.huawei.com (10.201.5.202) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 28 Jun 2016 15:31:07 +0100
Received: from BLREML501-MBB.china.huawei.com ([10.20.5.200]) by BLREML408-HUB.china.huawei.com ([10.20.4.47]) with mapi id 14.03.0235.001; Tue, 28 Jun 2016 20:00:59 +0530
From: Dhruv Dhody <dhruv.dhody@huawei.com>
To: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>, "draft-ietf-pce-stateful-pce-app@ietf.org" <draft-ietf-pce-stateful-pce-app@ietf.org>
Thread-Topic: Last IPR check for draft-ietf-pce-stateful-pce-app
Thread-Index: AdHRRLU7whFuinfpRSy4jW780IPc/wABOrGQ
Date: Tue, 28 Jun 2016 14:30:58 +0000
Message-ID: <23CE718903A838468A8B325B80962F9B8C8AC6F9@blreml501-mbb>
References: <BLUPR0201MB190821B2C6527DDE61210DCA84220@BLUPR0201MB1908.namprd02.prod.outlook.com>
In-Reply-To: <BLUPR0201MB190821B2C6527DDE61210DCA84220@BLUPR0201MB1908.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.18.77.237]
Content-Type: multipart/alternative; boundary="_000_23CE718903A838468A8B325B80962F9B8C8AC6F9blreml501mbb_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090201.57728A2D.0142, 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: dc7f4447b91916c66574b5c9594ee3a7
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/HH8vcN1sHCmLi3HYN4EIDgnMedk>
Cc: "pce@ietf.org" <pce@ietf.org>, "pce-chairs@ietf.org" <pce-chairs@ietf.org>
Subject: Re: [Pce] Last IPR check for draft-ietf-pce-stateful-pce-app
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 28 Jun 2016 14:31:14 -0000

I am not aware of any IPR that applies to this draft

Regards,
Dhruv

From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Jonathan Hardwick
Sent: 28 June 2016 19:27
To: draft-ietf-pce-stateful-pce-app@ietf.org
Cc: pce@ietf.org; pce-chairs@ietf.org
Subject: [Pce] Last IPR check for draft-ietf-pce-stateful-pce-app

Dear authors,

Please could you confirm (on the mailing list) whether you are aware of any IPR that applies to draft-ietf-pce-stateful-pce-app, and if so, if it has been disclosed in compliance with IETF IPR rules? (See RFCs 3979, 4879, 3669 and 5378 for more details.)  If you are not aware of any IPR that applies to this draft, please reply saying "I am not aware of any IPR that applies to this draft".

Best regards,

Jon, JP & Julien