[Teas] RE:Regarding IPR on draft-wdbsp-teas-nrp-yang-01

chen.ran@zte.com.cn Mon, 18 September 2023 01:26 UTC

Return-Path: <chen.ran@zte.com.cn>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 12F7EC14CF18 for <teas@ietfa.amsl.com>; Sun, 17 Sep 2023 18:26:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.903
X-Spam-Status: No, score=-6.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id qFySWb8QHyvC for <teas@ietfa.amsl.com>; Sun, 17 Sep 2023 18:26:04 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 675CCC14F721 for <teas@ietf.org>; Sun, 17 Sep 2023 18:26:03 -0700 (PDT)
Received: from mse-fl2.zte.com.cn (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4RpnDl50wBz4xPYZ; Mon, 18 Sep 2023 09:25:59 +0800 (CST)
Received: from njy2app04.zte.com.cn ([]) by mse-fl2.zte.com.cn with SMTP id 38I1Peb6048008; Mon, 18 Sep 2023 09:25:40 +0800 (+08) (envelope-from chen.ran@zte.com.cn)
Received: from mapi (njy2app01[null]) by mapi (Zmail) with MAPI id mid203; Mon, 18 Sep 2023 09:25:41 +0800 (CST)
Date: Mon, 18 Sep 2023 09:25:41 +0800
X-Zmail-TransId: 2af96507a715704-d35d7
X-Mailer: Zmail v1.0
Message-ID: <202309180925412247871@zte.com.cn>
Mime-Version: 1.0
From: chen.ran@zte.com.cn
To: xufeng.liu.ietf@gmail.com, daniele.ceccarelli@ericsson.com, chen.ran@zte.com.cn, luismiguel.contrerasmurillo@telefonica.com, chengying10@chinaunicom.cn, lana.wubo@huawei.com, dhruv.ietf@gmail.com, vbeeram@juniper.net, tsaad.net@gmail.com, peng.shaofu@zte.com.cn, teas@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 38I1Peb6048008
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6507A727.001/4RpnDl50wBz4xPYZ
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/-_vMPAEadB9CYLDy8NXb35TtWrg>
Subject: [Teas] RE:Regarding IPR on draft-wdbsp-teas-nrp-yang-01
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Sep 2023 01:26:10 -0000

No, I'm not aware of any IPR that applies to this draft.




-----Original Message-----From: Lou Berger <lberger@labn.net> Sent: Tuesday, August 22, 2023 8:54 PMTo: Xufeng Liu <xufeng.liu.ietf@gmail.com>; Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>; chen.ran@zte.com.cn; Luis Miguel Contreras Murillo <luismiguel.contrerasmurillo@telefonica.com>; chengying10@chinaunicom.cn; chengying10@chinaunicom.cn; Wubo (lana) <lana.wubo@huawei.com>; Dhruv Dhody <dhruv.ietf@gmail.com>; Vishnu Beeram <vbeeram@juniper.net>; Tarek Saad <tsaad.net@gmail.com>; peng.shaofu@zte.com.cnCc: TEAS WG Chairs <teas-chairs@ietf.org>; TEAS WG <teas@ietf.org>Subject: Regarding IPR on draft-wdbsp-teas-nrp-yang-01Authors, Contributors, WG,In preparation for WG AdoptionAre you aware of any IPR that applies to drafts identified above?Please state either:"No, I'm not aware of any IPR that applies to this draft"or"Yes, I'm aware of IPR that applies to this draft"If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3669, 5378 and 8179 for more details)?If yes to the above, please state either:"Yes, the IPR has been disclosed in compliance with IETF IPR rules"or"No, the IPR has not been disclosed"If you answer no, please provide any additional details you think appropriate. If you are listed as a document author or contributor please answer the above by responding to this email regardless of whether or not you are aware of any relevant IPR. This document will not advance to the next stage until a response has been received from each author.NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S TO LINES.If you are on the WG email list or attend WG meetings but are not listed as an author or contributor, we remind you of your obligations under the IETF IPR rules which encourages you to notify the IETF if you are aware of IPR of others on an IETF contribution, or to refrain from participating in any contribution or discussion related to your undisclosed IPR. For more information, please see https://www.ietf.org/standards/ipr/Thank you,Lou (Co-Chair)PS Please include all listed in the headers of this message in your response.