Hi Reese, Thanks for your review. We've fixed the nits that you advertised in the latest version of the draft that has just been posted.
https://datatracker.ietf.org/doc/html/draft-ietf-lsr-ospfv3-srv6-extensions-12 Thanks, Ketan On Thu, May 11, 2023 at 2:04 AM Reese Enghardt via Datatracker < nore...@ietf.org> wrote: > Reviewer: Reese Enghardt > 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-lsr-ospfv3-srv6-extensions-11 > Reviewer: Reese Enghardt > Review Date: 2023-05-10 > IETF LC End Date: 2023-05-15 > IESG Telechat date: Not scheduled for a telechat > > Summary: The document is clear, concise, and well-written. It is ready for > publication as a Proposed Standard. > > Major issues: None. > > Minor issues: None. > > Nits/editorial comments: > > 5. SRv6 SIDs and Reachability > "if the locator associated with SRv6 SID advertisements is the longest > prefix match installed in the forwarding plane for those SIDs" > > Please capitalize the beginning of the paragraph > > 9. Advertisement of SRv6 SIDs Associated with Adjacencies > > "although it MAY omit doing so if features like traffic engineering or > Topology-Independent Loop Free Alternate (TI-LFA) that requires it > are not in use" > requires -> require? > I'm not 100% sure what "it" refers to, but I'll assume it refers to a > unique > SRv6 End.X SID. > > The HTML version of the document looks different from most other recent > documents. Was the most recent tooling used here? If not, please consider > updating the XML format or tooling. > > >
_______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
