Hi Stewart,
Thanks for the review and comments. Have uploaded rev19 to address comments received from you and other reviewers.
Please see inline for details.
On Tue, Nov 12, 2024 at 8:59 AM Stewart Bryant via Datatracker <noreply@xxxxxxxx> wrote:
Reviewer: Stewart Bryant
Review result: Ready
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.
[NM]: ack. Given that this document is an enhancement on top of RFC 7432 and RFC 9135, mechanisms other than sequence numbers were not considered in the scope of this document.
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.
[NM]: discussed with co-authors and concluded that while this enhances mobility procedures in RFC7432 to cover additional scenarios, it does not necessarily update RFC7432. We decided to remove "updates RFC7432" from the header in rev19.
Thanks,
Neeraj
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
