Hi Joe，
Many thanks for your review! All comments were accepted and updated in the new
version.
A diff from the previous version is available
at:https://author-tools.ietf.org/iddiff?url2=draft-ietf-lsr-anycast-flag-05
Please confirm if your concerns have been addressed.
BR,
Ran
Original
From: JoeClarkeviaDatatracker <[email protected]>
To: [email protected] <[email protected]>;
Cc: [email protected]
<[email protected]>;[email protected]
<[email protected]>;[email protected] <[email protected]>;
Date: 2025年09月03日 07:34
Subject: [Last-Call] draft-ietf-lsr-anycast-flag-04 ietf last call Yangdoctors
review
Document: draft-ietf-lsr-anycast-flag
Title: OSPFv2 Anycast Property Advertisement
Reviewer: Joe Clarke
Review result: Almost Ready
I have been asked to review this draft on behalf of YANG Doctors. The YANG
module provided by this draft is rather short, and serves to add anycast prefix
support to OSPFv2 via an augmentation and an additional identity. Overall, I
didn't find much wrong.
To be consistent with RFC9129, I recommend you rename the "AC-flag" identity,
"ac-flag" (this need only be done in the YANG module itself, not in the
document text description of the flag). I don't typically see many uppercase
identifiers anyway, and RFC9129 uses "a-flag" for "Attach flag".
Ran: Agreed. Thanks.
Please update the IANA considerations to match the template from RFC8407bis.
We've been pushing the new guidelines there since that document is almost
published.
Ran: Agreed. Thanks
--
last-call mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
Lsr mailing list -- [email protected]
To unsubscribe send an email to [email protected]
