Skip to main content

Last Call Review of draft-ietf-bess-evpn-irb-extended-mobility-18
review-ietf-bess-evpn-irb-extended-mobility-18-genart-lc-bryant-2024-11-12-00

Request Review of draft-ietf-bess-evpn-irb-extended-mobility
Requested revision No specific revision (document currently at 20)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2024-11-19
Requested 2024-10-29
Authors Neeraj Malhotra , Ali Sajassi , Aparna Pattekar , Jorge Rabadan , Avinash Reddy Lingala , John Drake
I-D last updated 2024-11-12
Completed reviews Rtgdir Early review of -10 by Donald E. Eastlake 3rd (diff)
Genart Last Call review of -18 by Stewart Bryant (diff)
Secdir Last Call review of -18 by Robert Sparks (diff)
Tsvart Last Call review of -18 by Dr. Joseph D. Touch (diff)
Opsdir Last Call review of -18 by Susan Hares (diff)
Intdir Telechat review of -18 by Brian Haberman (diff)
Assignment Reviewer Stewart Bryant
State Completed
Request Last Call review on draft-ietf-bess-evpn-irb-extended-mobility by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/6YGP602qjFnyJKSV4x7x5Xoy8TI
Reviewed revision 18 (document currently at 20)
Result Ready
Completed 2024-11-12
review-ietf-bess-evpn-irb-extended-mobility-18-genart-lc-bryant-2024-11-12-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-irb-extended-mobility-18
Reviewer: Stewart Bryant
Review Date: 2024-11-12
IETF LC End Date: 2024-11-19
IESG Telechat date: Not scheduled for a telechat

Summary:This is a well written document ready for publication.

Major issues:None

Not an issue but an observation. The difficulty of sequence number management
is central to this text, particularly in distributed systems. I wonder why in
this modern age of accurate time distribution, time is not used as a method of
indicating the currency of a protocol item in our designs.

Minor issues:None

Nits/editorial comments: Nits produces the following warning:
The draft header indicates that this document updates RFC7432, but the abstract
doesn't seem to directly say this.