Hello BESS WG and authors, I have one comment on Appendix A of draft-ietf-bess-evpn-bfd-17 and just saw 2 or 3 superior versions published and applicable to those as well.
Section 3 says that the document covers unicast traffic, BUM traffic using ingress replication, BUM traffic using P2MP tunnels, and both MPLS and VXLAN encapsulations. Appendix A presently asks only for BFD bootstrap, state transitions, and teardown between two independently implemented PEs. That confirms basic BFD interoperability, but it does not show which of the forwarding and encapsulation cases specified by the document were interoperable. I suggest following or similar text for Appendix A: "For each forwarding and encapsulation case implemented, an implementation report must record successful bootstrap, maintenance including Up to Down to Up transitions, and teardown of EVPN BFD sessions between independently implemented PEs. The report must identify the traffic class, tunnel type, encapsulation, BFD session mode, injected fault, and the BFD state observed at each endpoint. The report must cover unicast and BUM traffic, ingress replication and P2MP forwarding where implemented, and MPLS and VXLAN where implemented." This helps to keep implementation aligned, while giving a later standards track decision evidence that the mechanisms in Sections 5 through 7 were tested rather than only the common BFD session lifecycle. Thanks, Saumya. From: Vengada Prasad Govindan (venggovi) <[email protected]> Date: Monday, 17 August 2026 at 1:24 PM To: [email protected] <[email protected]> Cc: '[email protected]' <[email protected]> Subject: [bess] Re: Experiment criteria for draft-ietf-bess-evpn-bfd Hello WG, draft-ietf-bess-evpn-bfd-15 has been submitted with the proposed text for success criteria in the Appendix. The scope section calls out this reference as well. Chairs, I hope this should help progress the document forward in exp track. Please let me know if any more edits are required. Thanks Prasad ________________________________ From: Vengada Prasad Govindan (venggovi) <[email protected]> Sent: Tuesday, July 28, 2026 10:40 PM To: [email protected] <[email protected]> Subject: [bess] Experiment criteria for draft-ietf-bess-evpn-bfd Hello WG, During the IETF-126, there was a suggestion that the draft-ietf-bess-evpn-bfd be moved to exp track (from std) to progress it further towards RFC. It was also required to define the criteria based on which the document could progress to STD track at a later date. To satisfy the comment, the following text is proposed. Comments are welcome: [cid:[email protected]] Thanks Prasad
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
