Hi Matthew,
I am not aware of any IPR related to this draft.

As a co-author, I support publication of this document.

Regards,
Greg

On Wed, Oct 15, 2025 at 8:16 AM Matthew Bocci (Nokia) <matthew.bocci=
[email protected]> wrote:

> Hello Working Group,
>
>
>
>  This email starts a Working Group Last Call for
> draft-ietf-bess-evpn-bfd-12 (draft-ietf-bess-evpn-bfd-12 - EVPN Network
> Layer Fault Management
> <https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-bfd/>).
>
>  Please review the draft and post any comments to the BESS list, and
> whether or not you support progressing with publication of this draft as a
> standards track RFC.
>
>
>
> This WG LC notice has also been CC’d to the BFD working group list. BFD
> participants: please can you respond to the BESS WG list as this will
> greatly help in judging consensus.
>
>
>
> This poll runs until 31st  October 2025.
>
>
>
>  We are also polling for knowledge of any undisclosed IPR that applies to
> this document, to ensure that IPR has been disclosed in compliance with
> IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).
>
> If you are listed as an Author or a Contributor of this document, please
> respond to this email and indicate if you are aware of any relevant
> undisclosed IPR.
>
> There is no IPR currently disclosed.
>
> If you are not listed as an Author or a Contributor, then please
> explicitly respond only if you are aware of any IPR that has not yet been
> disclosed in conformance with IETF rules.
>
>
>
> We are also polling for any existing implementations as per [bess]
> Conclusion on the "one implementation policy"
> <https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw/>.
> Please reply to this email or directly to the BESS chairs if you are aware
> of any implementations of the draft.
>
>
>
> Best regards
>
>
>
> Matthew (on behalf of the BESS chairs).
>
>
>
>
>
>
>
>
>
_______________________________________________
BESS mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to