Early Review of draft-ietf-bess-evpn-bfd-10
review-ietf-bess-evpn-bfd-10-genart-early-gurbani-2025-05-20-00
| Request | Review of | draft-ietf-bess-evpn-bfd |
|---|---|---|
| Requested revision | No specific revision (document currently at 13) | |
| Type | Early Review | |
| Team | General Area Review Team (Gen-ART) (genart) | |
| Deadline | 2025-05-23 | |
| Requested | 2025-04-24 | |
| Requested by | Matthew Bocci | |
| Authors | Vengada Prasad Govindan , Ali Sajassi , Mudigonda Mallik , Greg Mirsky , Donald E. Eastlake 3rd | |
| I-D last updated | 2026-03-27 (Latest revision 2026-03-27) | |
| Completed reviews |
Rtgdir Early review of -07
by Mohamed Boucadair
(diff)
Genart Early review of -10 by Vijay K. Gurbani (diff) |
|
| Assignment | Reviewer | Vijay K. Gurbani |
| State | Completed | |
| Request | Early review on draft-ietf-bess-evpn-bfd by General Area Review Team (Gen-ART) Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/gen-art/n8qXUbhyKGEXdo9H0YLTInvCPf0 | |
| Reviewed revision | 10 (document currently at 13) | |
| Result | Ready w/nits | |
| Completed | 2025-05-20 |
review-ietf-bess-evpn-bfd-10-genart-early-gurbani-2025-05-20-00
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at <https://wiki.ietf.org/en/group/gen/GenArtFAQ>. Document: draft-ietf-bess-evpn-bfd-10 Reviewer: Vijay K. Gurbani Review Date: 2025-05-20 IETF LC End Date: Not known IESG Telechat date: Not scheduled for a telechat Summary: This I-D is ready to be published as a standards document. Major issues: 0 Minor issues: 0 Nits: 3 Nits: 1. Section 1: s/that is to say between/that is, between/ 2. Section 3: "Continuity testing at each layer SHOULD, if possible,..." Here, isn't the "if possible" redundant? After all, then normative strength is SHOULD which loosely implies "if possible". 3. Section 7: "...could affect the packet load on the network..." Would it be possible to expand on how could the document affect the packet load on the network? For instance, is the network affected because the packet size becomes large, and therefore requires more processing at the endpoints and intermediaries? Or is the network load affected due the expected large number of EVIs once this standard is implemented? Or are there other reasons inherent in the implementation of the document that would increase the network load?