Re: [Teas] Regarding IPR on draft-ietf-teas-pcecc-use-cases-09

Lizhenbin <lizhenbin@huawei.com> Mon, 09 May 2022 15:57 UTC

Return-Path: <lizhenbin@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83FC1C15E6D7; Mon, 9 May 2022 08:57:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id URCO4-lq5lOb; Mon, 9 May 2022 08:57:43 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6411C15E3EB; Mon, 9 May 2022 08:57:37 -0700 (PDT)
Received: from fraeml745-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Kxm1w5XYnz685b0; Mon, 9 May 2022 23:54:12 +0800 (CST)
Received: from dggpemm100008.china.huawei.com (7.185.36.125) by fraeml745-chm.china.huawei.com (10.206.15.226) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Mon, 9 May 2022 17:57:33 +0200
Received: from dggpemm500008.china.huawei.com (7.185.36.136) by dggpemm100008.china.huawei.com (7.185.36.125) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Mon, 9 May 2022 23:57:31 +0800
Received: from dggpemm500008.china.huawei.com ([7.185.36.136]) by dggpemm500008.china.huawei.com ([7.185.36.136]) with mapi id 15.01.2375.024; Mon, 9 May 2022 23:57:31 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>, Dhruv Dhody <dhruv.ietf@gmail.com>, "qzhao@ethericnetworks.com" <qzhao@ethericnetworks.com>, "kinghe@tencent.com" <kinghe@tencent.com>, "bhassanov@yahoo.com" <bhassanov@yahoo.com>, Luyuan Fang <luyuanf@gmail.com>, "chaozhou_us@yahoo.com" <chaozhou_us@yahoo.com>, "Boris.zhang@telus.com" <Boris.zhang@telus.com>, "arachitskiy@mts.by" <arachitskiy@mts.by>, "anton.gulida@life.com.by" <anton.gulida@life.com.by>
CC: TEAS WG <teas@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>
Thread-Topic: Regarding IPR on draft-ietf-teas-pcecc-use-cases-09
Thread-Index: AQHYYWxusNJcjze7O0mZFzVel4Mbxq0Wt7Ng
Date: Mon, 09 May 2022 15:57:31 +0000
Message-ID: <79668e2aeaa5477e966a36bc01cb98e3@huawei.com>
References: <CA+YzgTvDZeAxJT+kASDBBZDuPGjft4=LGrv9hxx7hu2GSsc8uw@mail.gmail.com>
In-Reply-To: <CA+YzgTvDZeAxJT+kASDBBZDuPGjft4=LGrv9hxx7hu2GSsc8uw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.52.213.8]
Content-Type: multipart/alternative; boundary="_000_79668e2aeaa5477e966a36bc01cb98e3huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/EiPu6dqziCaZt9-xrfwpLhz9k2M>
Subject: Re: [Teas] Regarding IPR on draft-ietf-teas-pcecc-use-cases-09
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.34
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, 09 May 2022 15:57:44 -0000

Hi All,

Yes, I'm aware of IPR that applies to this draft.
Yes, the IPR has been disclosed in compliance with IETF IPR rules.

Best Regards,
Zhenbin (Robin)



From: Vishnu Pavan Beeram [mailto:vishnupavan@gmail.com]
Sent: Saturday, May 7, 2022 1:12 AM
To: Lizhenbin <lizhenbin@huawei.com>; Dhruv Dhody <dhruv.ietf@gmail.com>; qzhao@ethericnetworks.com; kinghe@tencent.com; bhassanov@yahoo.com; Luyuan Fang <luyuanf@gmail.com>; chaozhou_us@yahoo.com; Boris.zhang@telus.com; arachitskiy@mts.by; anton.gulida@life.com.by
Cc: TEAS WG <teas@ietf.org>; TEAS WG Chairs <teas-chairs@ietf.org>
Subject: Regarding IPR on draft-ietf-teas-pcecc-use-cases-09

Authors, Contributors, WG,

As part of WG Last Call:

Are 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 the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
Pavan and Lou

PS Please include all listed in the headers of this message in your
response.