Greetings all, Jeffrey, thanks for your reply.
Authors, we note that you opted in to the do AUTH48 in GitHub. We will relaunch AUTH48 with updated instructions later today. Apologies for the error on our end. Thanks, Sandy Ginoza RFC Production Center > On May 8, 2026, at 8:24 AM, Jeffrey Haas <[email protected]> wrote: > > Editors, > > Minor comments from me wearing my chair hat. The authors should respond to > the majority of these items. > > > >> On May 7, 2026, at 19:03, [email protected] wrote: >> >> 6) <!-- [rfced] Does "BFD Meticulous" refer "Meticulous Keyed MD5", as >> registered by IANA? Should the text be udpated to refer to march the IANA >> name? See >> <https://www.iana.org/assignments/bfd-parameters/bfd-parameters.xhtml#bfd-parameters-2>. >> >> >> Original: >> BFD stability measurement requires that a BFD Meticulous >> Authentication type is configured. >> --> > > No, it refers to the class of meticulous authentication types. To help > harmonize the documents, see draft-ietf-bfd-secure-sequence-numbers-27 > section 1.1. This document is largely independent from that document (i.e., > they don't have to be in the same cluster), but that document is the one > clarifying the style of authentication. > > >> >> 15) <!-- [rfced] Please review the following questions and changes >> regarding the terminology used in this document: >> >> a) Should instances of "NULL Auth" be updated to "NULL authentication type" >> (i.e., spell out "Authentication") for clarity and consistency with other >> uses in the document? >> >> NULL Auth type >> NULL Auth Type >> NULL Auth >> >> Note that "authentication type" (lowercase) is used except where the text >> explicitly refers to the field (Auth Type field or Authentication Type >> field). >> >> Please let us know if any updates are needed. > > It is critical that the identity in the YANG module referring to this be > appropriately consistent with the decision above. > > Thanks. > > -- Jeff > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
