[spring] Re: IPR Declarations for draft-ietf-spring-bfd

Mach Chen <mach.chen@huawei.com> Wed, 04 December 2024 06:51 UTC

Return-Path: <mach.chen@huawei.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0056C13739A; Tue, 3 Dec 2024 22:51:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=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, 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 2GE2PtidrK4i; Tue, 3 Dec 2024 22:51:02 -0800 (PST)
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 15C69C33818F; Tue, 3 Dec 2024 22:50:06 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Y37MK01VQz6FH1h; Wed, 4 Dec 2024 14:45:49 +0800 (CST)
Received: from lhrpeml500009.china.huawei.com (unknown [7.191.174.84]) by mail.maildlp.com (Postfix) with ESMTPS id 7E696140A34; Wed, 4 Dec 2024 14:50:03 +0800 (CST)
Received: from kwepemf100004.china.huawei.com (7.202.181.218) by lhrpeml500009.china.huawei.com (7.191.174.84) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Wed, 4 Dec 2024 06:50:02 +0000
Received: from kwepemf100006.china.huawei.com (7.202.181.220) by kwepemf100004.china.huawei.com (7.202.181.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Wed, 4 Dec 2024 14:50:00 +0800
Received: from kwepemf100006.china.huawei.com ([7.202.181.220]) by kwepemf100006.china.huawei.com ([7.202.181.220]) with mapi id 15.02.1544.011; Wed, 4 Dec 2024 14:50:00 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, "draft-ietf-spring-bfd@ietf.org" <draft-ietf-spring-bfd@ietf.org>
Thread-Topic: IPR Declarations for draft-ietf-spring-bfd
Thread-Index: AQHbRPKXAXTCp3ajikG+8/Qyi+DP47LS152AgALPgzA=
Date: Wed, 04 Dec 2024 06:50:00 +0000
Message-ID: <f1a533344b6a4f20b57a2928cc5a7468@huawei.com>
References: <CAMMESsy_cCjX12DGDw9mu+Owjuh3Jrubqn5tETQwAFnu8y8jnw@mail.gmail.com> <CAMMESsya2GTs0STMy8e3oTpcCi0GH6MzQE6cyK11wpzPD5x6tg@mail.gmail.com>
In-Reply-To: <CAMMESsya2GTs0STMy8e3oTpcCi0GH6MzQE6cyK11wpzPD5x6tg@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.110.46.250]
Content-Type: multipart/alternative; boundary="_000_f1a533344b6a4f20b57a2928cc5a7468huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: H4DQY5AO24GOFSTCAIQAWUBGTOYBODP5
X-Message-ID-Hash: H4DQY5AO24GOFSTCAIQAWUBGTOYBODP5
X-MailFrom: mach.chen@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spring.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "spring-chairs@ietf.org" <spring-chairs@ietf.org>, "spring@ietf.org" <spring@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [spring] Re: IPR Declarations for draft-ietf-spring-bfd
List-Id: "Source Packet Routing in NetworkinG (SPRING)" <spring.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/-PzSDx4uaJrX19ITvy-ksQJK2wU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Owner: <mailto:spring-owner@ietf.org>
List-Post: <mailto:spring@ietf.org>
List-Subscribe: <mailto:spring-join@ietf.org>
List-Unsubscribe: <mailto:spring-leave@ietf.org>

Hi Alvaro,

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

Best regards,
Mach

From: Alvaro Retana <aretana.ietf@gmail.com>
Sent: Tuesday, December 3, 2024 3:53 AM
To: draft-ietf-spring-bfd@ietf.org
Cc: rtg-bfd@ietf.org; spring-chairs@ietf.org; spring@ietf.org
Subject: Re: IPR Declarations for draft-ietf-spring-bfd

[Sorry ofr the bad formatting. :-( ]


[cc'ing the bfd WG]


Dear authors and contributors:

Are you aware of any IPR that applies to this draft?

If so, has it been disclosed in compliance with IETF IPR rules (see BCP78 and BCP79 for more details)?  For any undisclosed IPR, please provide any additional information 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 only advance to the next stage once a response is received from each listed author and contributor.


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 encourage you to notify the IETF if you are aware of IPR that may be related to this document 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,

Alvaro (for the spring-chairs)



On December 2, 2024 at 2:43:54 PM, Alvaro Retana (aretana.ietf@gmail.com<mailto:aretana.ietf@gmail.com>) wrote:
[cc'ing the bfd WG]Dear authors and contributors:Are you aware of any IPR that applies to this draft? If so, has it been disclosed in compliance with IETF IPR rules (see BCP78 and BCP79 for more details)?  For any undisclosed IPR, please provide any additional information 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 only advance to the next stage once a response is received from each listed author and contributor. 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 encourage you to notify the IETF if you are aware of IPR that may be related to this document 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, Alvaro (for the spring-chairs)