Thanks. I will address these comments, and the updated text will be available in the next revision of the document.
> On Mar 20, 2025, at 7:22 AM, Ben Niven-Jenkins via Datatracker > <nore...@ietf.org> wrote: > > Reviewer: Ben Niven-Jenkins > Review result: Ready > > Hello, > > I have been selected as the Routing Directorate reviewer for this draft. The > Routing Directorate seeks to review all routing or routing-related drafts as > they pass through IETF last call and IESG review, and sometimes on special > request. The purpose of the review is to provide assistance to the Routing > ADs. > For more information about the Routing Directorate, please see > https://wiki.ietf.org/en/group/rtg/RtgDir > > Although these comments are primarily for the use of the Routing ADs, it would > be helpful if you could consider them along with any other IETF Last Call > comments that you receive, and strive to resolve them through discussion or by > updating the draft. > > Document: draft-ietf-bfd-secure-sequence-numbers-18 > Reviewer: Ben Niven-Jenkins > Review Date: 2025-03-20 > Intended Status: Experimental > > Summary: No issues found. This document is ready for publication. > > Comments: The document is easy to read and follow. > > Major Issues: No major issues found. > > Minor Issues: No minor issues found. > > Nits: > > Section 3: s/This document describes an experimental updates/This document > describes an experimental update/ > > Section 3, bfd.XmitAuthSeq: s/sequence number for for the Authentication > Section/sequence number for the Authentication Section/ > > Section 8: s/that adminsitrators different Secret Keys for each Auth > Type./that > administrators use different Secret Keys for each Auth Type. > >
