Jim: Hi!
Thanks for your comments and review! We submitted -07 to address your concerns. Please take a look. Alvaro. On May 8, 2023 at 4:15:04 PM, Jim Guichard via Datatracker (nore...@ietf.org<mailto:nore...@ietf.org>) wrote: Jim Guichard has entered the following ballot position for draft-ietf-lsr-ospf-terminology-06: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-lsr-ospf-terminology/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Section 2 "Updates to RFC2328" is missing reference to section 10.3. "The Neighbor state machine" of RFC 2328. Non-inclusive language is used for the "State(s): Init, Event: 2-WayReceived" and "State(s): Exchange or greater, Event: SeqNumberMismatch". ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Nits: Section 2 uses both leader/follower and Leader/Follower. Use one or the other. Section 5 text is referring to Figure 2 of RFC4811 and should probably say this in the text to be more specific. Section 8 the text " Figure 1: RFC 5838, Section 2.4 - Updated First Paragraph" - is this meant to be here as there is no figure? _______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
_______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
