Matthew and all, ++ BFD WG Chairs and Prasad. I have held a series of discussions with Prasad (as the representative of the authors) to clarify the scope of the draft and its applicability.. As the result of these discussions the draft has underwent substantial (from my POV) changes:
1. The notion of the EVPN Network Layer has been clarified 2. The case of EVPN that implements VLAN-aware Bundle service interface and uses per MAC-VRF Label allocation scheme (allowed in EVPN-MPLS but not in EVPN-VxLAN) has been explicitly left out of scope of the draft. Since peer PEs that participate in an EVPN that implements VLAN-aware Bundle Service interface cannot identify the label allocation mode for this EVPN instance in the peer PEs, this effectively means that VLAN-aware Bundle service interface is left out of scope 3. The draft explicitly recognizes that, in the case of EVPN-MPLS, certain EVPN Network Layer failures cannot be detected by the proposed mechanism 4. Usage of failure of EVPN BFD sessions as a trigger for restoration of affected traffic has been explicitly left out of scope of the draft. The only action in this case is report to the operator/management systems. I think that proposed reuse of the Destination UDP Port 3784 (reserved in RFC 5881 for single-hop IP BFD) in the draft is problematic: * AFAIK, all existing BFD flavors that rely on UDP encapsulation use dedicated destination UPD Ports * I think this issue deserves special attention of the BFD WG * I have not discussed this point with the authors in any detail. Hopefully these notes will be useful. Regards, Sasha From: Matthew Bocci (Nokia) <[email protected]> Sent: Wednesday, October 15, 2025 6:16 PM To: 'BESS' <[email protected]> Cc: [email protected]; '[email protected]' <[email protected]> Subject: [EXTERNAL] WG LC, IPR and Implementation Poll for draft-ietf-bess-evpn-bfd-12 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). Disclaimer This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
