Hi Zahed, The -04 version of the draft should address your comments. Cheers.
p.s. Due to some confusion, the -03 version of the draft only partially addressed some of the comments received during IESG review. > On Apr 6, 2022, at 10:44 AM, Zaheduzzaman Sarker > <[email protected]> wrote: > > > From: Mahesh Jethanandani <[email protected]> > Sent: Wednesday, April 6, 2022 7:31 PM > To: Zaheduzzaman Sarker <[email protected]> > Cc: The IESG <[email protected]>; [email protected] > <[email protected]>; [email protected] > <[email protected]>; rtg-bfd@ietf. org <[email protected]>; Jeffrey Haas > <[email protected]> > Subject: Re: Zaheduzzaman Sarker's Discuss on draft-ietf-bfd-rfc9127-bis-02: > (with DISCUSS) > > Hi Zahed, > > See inline. > >> On Apr 6, 2022, at 9:40 AM, Zaheduzzaman Sarker via Datatracker >> <[email protected] <mailto:[email protected]>> wrote: >> >> Zaheduzzaman Sarker has entered the following ballot position for >> draft-ietf-bfd-rfc9127-bis-02: 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/ >> <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-bfd-rfc9127-bis/ >> <https://datatracker.ietf.org/doc/draft-ietf-bfd-rfc9127-bis/> >> >> >> >> ---------------------------------------------------------------------- >> DISCUSS: >> ---------------------------------------------------------------------- >> >> Thanks for this specification. >> >> I have noticed couple of potentially normative missing references hence the >> discuss ballot. >> >> * iana-bfd-types is imported from RFC9127 but missing in the normative >> reference. > > Added. > >> * ietf-key-chain is imported from RFC8177 but missing in the normative >> reference. > > This is already referenced (-02 of the draft) in the normative section. Am I > missing something?? > > ZS: Nope , I missed 8177 for some reason. I see now it is in the right place. > > //Zahed > >> >> I hope a revised ID would solve this. >> >> >> >> >> > > > Mahesh Jethanandani > [email protected] <mailto:[email protected]> > > > > > > Mahesh Jethanandani [email protected]
