Fwd: draft-ietf-bfd-unaffiliated-echo WGLC and IPR check

Jeffrey Haas <jhaas@pfrc.org> Mon, 24 April 2023 13:25 UTC

Return-Path: <jhaas@pfrc.org>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E0E75C152D85 for <rtg-bfd@ietfa.amsl.com>; Mon, 24 Apr 2023 06:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id AtNfumr_vr1R for <rtg-bfd@ietfa.amsl.com>; Mon, 24 Apr 2023 06:25:13 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org []) by ietfa.amsl.com (Postfix) with ESMTP id D74C3C15155A for <rtg-bfd@ietf.org>; Mon, 24 Apr 2023 06:25:12 -0700 (PDT)
Received: from smtpclient.apple (104-10-90-238.lightspeed.livnmi.sbcglobal.net []) by slice.pfrc.org (Postfix) with ESMTPSA id E39181E037; Mon, 24 Apr 2023 09:25:10 -0400 (EDT)
From: Jeffrey Haas <jhaas@pfrc.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_213C3EEE-50D8-4E99-BDBB-0259D1E8BAC5"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.\))
Date: Mon, 24 Apr 2023 09:25:10 -0400
Subject: Fwd: draft-ietf-bfd-unaffiliated-echo WGLC and IPR check
References: <SA1PR05MB87531F4DDED80B1489EC8986B39A9@SA1PR05MB8753.namprd05.prod.outlook.com>
To: rtg-bfd WG <rtg-bfd@ietf.org>
Message-Id: <6D03833D-2C09-4445-8BE3-B81856F092AC@pfrc.org>
X-Mailer: Apple Mail (2.3696.
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/esD26TKSjvRFJSm0qbcAJ-7EKvo>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2023 13:25:17 -0000

For whatever reason, Raj's attestation didn't make it into the BFD archives.  So, a resend.

-- Jeff

> Begin forwarded message:
> From: Raj Chetan Boddireddy <rchetan@juniper.net>
> Subject: Re: draft-ietf-bfd-unaffiliated-echo WGLC and IPR check
> Date: April 11, 2023 at 9:18:59 AM EDT
> To: Jeffrey Haas <jhaas@pfrc.org>, "draft-ietf-bfd-unaffiliated-echo@ietf.org" <draft-ietf-bfd-unaffiliated-echo@ietf.org>
> Cc: rtg-bfd WG <rtg-bfd@ietf.org>
> I am not aware of any IPR disclosures applicable to this document.
> Thanks & Regards,
> Raj Chetan
> From: Jeffrey Haas <jhaas@pfrc.org <mailto:jhaas@pfrc.org>>
> Date: Monday, 10 April 2023 at 8:57 PM
> To: draft-ietf-bfd-unaffiliated-echo@ietf.org <mailto:draft-ietf-bfd-unaffiliated-echo@ietf.org> <draft-ietf-bfd-unaffiliated-echo@ietf.org <mailto:draft-ietf-bfd-unaffiliated-echo@ietf.org>>
> Cc: rtg-bfd WG <rtg-bfd@ietf.org <mailto:rtg-bfd@ietf.org>>
> Subject: draft-ietf-bfd-unaffiliated-echo WGLC and IPR check
> [External Email. Be cautious of content]
> https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-ietf-bfd-unaffiliated-echo__;!!NEt6yMaO-gk!EjoTAw5NjwurOf5C-nX-pWzjHov0h8Td00L8sN39lR8wetMhrXZfgZTsZS2NfFYGjcUnIkmvwmVB$ <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-ietf-bfd-unaffiliated-echo__;!!NEt6yMaO-gk!EjoTAw5NjwurOf5C-nX-pWzjHov0h8Td00L8sN39lR8wetMhrXZfgZTsZS2NfFYGjcUnIkmvwmVB$>
> Working Group,
> The Working Group Last Call for draft-ietf-bfd-unaffiliated-echo has completed.  My judgment is that it has weak, but positive support to proceed to publication.  This isn't atypical of BFD work at this point in the BFD Working Group's life.
> The next steps for the document:
> 1. Please continue to iterate through the issues raised during last call.  I will be summarizing them in the original WGLC thread.  I suspect we can reach conclusion for them shortly.
> 2. Each of the authors needs to make an attestation as to whether they're aware of any additional IPR applicable to this document.  The rest of the Working Group, as per BCP 78/79[1] should also disclose of any applicable IPR if they're aware of it.
> One thing that makes this document particularly interesting is that this work is covered partially under work done in BBF in TR-146.  This will be noted in the shepherd writeup.
> -- Jeff
> [1] https://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc8179.html*section-5.1__;Iw!!NEt6yMaO-gk!EjoTAw5NjwurOf5C-nX-pWzjHov0h8Td00L8sN39lR8wetMhrXZfgZTsZS2NfFYGjcUnIlbXqmPa$ <https://urldefense.com/v3/__https:/www.rfc-editor.org/rfc/rfc8179.html*section-5.1__;Iw!!NEt6yMaO-gk!EjoTAw5NjwurOf5C-nX-pWzjHov0h8Td00L8sN39lR8wetMhrXZfgZTsZS2NfFYGjcUnIlbXqmPa$>
> Juniper Business Use Only