[Teas] 回复： [Internet]Re: Regarding IPR on draft-ietf-teas-pcecc-use-cases-09
"kinghe(何泽坤)" <kinghe@tencent.com> Tue, 07 June 2022 00:32 UTC
Return-Path: <kinghe@tencent.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 B6305C15AAD3 for <teas@ietfa.amsl.com>; Mon, 6 Jun 2022 17:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tencent.com
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 vqdM1XHJA9ak for <teas@ietfa.amsl.com>; Mon, 6 Jun 2022 17:32:32 -0700 (PDT)
Received: from smtpbg516.qq.com (smtpbg516.qq.com [203.205.250.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8A43C15AAC0 for <teas@ietf.org>; Mon, 6 Jun 2022 17:32:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tencent.com; s=s201512; t=1654561934; bh=scb2oTGWF+i76Ej0ipRAWTiycnTSg6LMzqUSjnYyTio=; h=From:To:Subject:Mime-Version:Date:Message-ID; b=fTndA9UyJHGdKWCPgVo/Z0zmQut0hWo9m6suxxRnbbgMmU6VCCteMwwB+nmKXJBGB aBqKzoON29nG4LY6JrZKoatKDHKG3CPZSU1V/ZRFvbilOF4bDGot9spgUyqQRanPHz R1BNAw67JyloBfTNwEPaKdzLFdYzUuKmsTV7nGmg=
X-QQ-GoodBg: 0
X-QQ-SSF: 0050000000000040
X-QQ-FEAT: y0KbYqNOTlVHD6L5ijggALW0Gl8EJRdIsXTJXqhLHMWwGvgJNJrvpmhUux6Jd yuVxxrcayqagxZlJ+uvS2FXLa4Lm+kh7BrDbRmdeR7nv6TdCAF3PTEshdHA1E21QyhrBM5p /BTp7cL+yY8iCA7yOToE1qkut/z87GdGs1PF4j3V/0177IIVfsOKKroPIpH8hA9qyq98p/0 fyBCuzeKveO0KkJ5sI50dJ5zEIyQ4PvKKNloGKr/EgN3rzn3eAJ22fL+/GYq2z9kcggDWVO xcbe4fEe6KJEEgdloT311lXxgrtebxjsSFm+8w6/MSHPmfAOkHx4VTqfdK3+cki5xjBxN15 CQhN2D3T8HWMerwcczLOPsZxySouA==
X-QQ-BUSINESS-ORIGIN: 2
X-Originating-IP: 59.37.20.149
X-QQ-STYLE:
X-QQ-mid: logic637t1654561932t6333417
From: "kinghe(何泽坤)" <kinghe@tencent.com>
To: vishnupavan <vishnupavan@gmail.com>, lizhenbin <lizhenbin@huawei.com>, "dhruv.ietf" <dhruv.ietf@gmail.com>, qzhao <qzhao@ethericnetworks.com>, bhassanov <bhassanov@yahoo.com>, luyuanf <luyuanf@gmail.com>, chaozhou_us <chaozhou_us@yahoo.com>, "Boris.zhang" <Boris.zhang@telus.com>, arachitskiy <arachitskiy@mts.by>, "anton.gulida" <anton.gulida@life.com.by>
Cc: teas <teas@ietf.org>, teas-chairs <teas-chairs@ietf.org>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_629E9C8B_1B1AF8D8_25266A18"
Content-Transfer-Encoding: 8bit
Date: Tue, 07 Jun 2022 08:32:11 +0800
X-Priority: 3
Message-ID: <tencent_041BA5745E6C247133304E62@qq.com>
X-QQ-MIME: TCMime 1.0 by Tencent
X-Mailer: QQMail 2.x
X-QQ-Mailer: QQMail 2.x
X-QQ-ReplyHash: 1364700835
X-QQ-SENDSIZE: 520
Received: from qq.com (unknown [127.0.0.1]) by smtp.qq.com (ESMTP) with SMTP id ; Tue, 07 Jun 2022 08:32:13 +0800 (CST)
Feedback-ID: logic:tencent.com:qybgforeign:qybgforeign4
X-QQ-Bgrelay: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/v-Q52_gfbCfWqczyjCQFog6ZXPw>
Subject: [Teas] 回复： [Internet]Re: Regarding IPR on draft-ietf-teas-pcecc-use-cases-09
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: Tue, 07 Jun 2022 00:32:39 -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.
发自我的企业微信
----------回复的邮件信息----------
Vishnu Pavan Beeram<vishnupavan@gmail.com> 在2022年5月18日(星期三) 凌晨4:02写道：
Missing responses from:kinghe@tencent.com
Boris.zhang@telus.com
anton.gulida@life.com.by
Regards,
-Pavan
On Fri, May 6, 2022 at 10:41 PM Vishnu Pavan Beeram <vishnupavan@gmail.com> wrote:
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.