Hello Med: WFM 😊 My understanding of normative references is a moving target. At the moment, I understand it means everything that is necessary to understand the spec, even if the spec does not MUST a behaviour or a format in the ref. And for things like architectures and problem statements, that means a lawful downref that the ADs will accept. That happened to me recently. But I'm fine either way, just asking. Take care, Pascal > -----Original Message----- > From: mohamed.boucadair@xxxxxxxxxx <mohamed.boucadair@xxxxxxxxxx> > Sent: lundi 16 mai 2022 18:36 > To: Pascal Thubert (pthubert) <pthubert@xxxxxxxxx>; int-dir@xxxxxxxx > Cc: draft-ietf-drip-rid.all@xxxxxxxx; last-call@xxxxxxxx; tm-rid@xxxxxxxx > Subject: RE: Intdir last call review of draft-ietf-drip-rid-26 > > Hi Pascal, > > Many thanks for this detailed review. Much appreciated. > > I trust Rob will reply to your various comments SOON. Please see one specific > comment inline. > > Cheers, > Med > > > -----Message d'origine----- > > De : Pascal Thubert via Datatracker <noreply@xxxxxxxx> Envoyé : lundi > > 16 mai 2022 15:30 À : int-dir@xxxxxxxx Cc : > > draft-ietf-drip-rid.all@xxxxxxxx; last-call@xxxxxxxx; tm- rid@xxxxxxxx > > Objet : Intdir last call review of draft-ietf-drip-rid-26 > > > > Reviewer: Pascal Thubert > > Review result: Ready with Nits > > > > > [snip] > > > > > > > > > 10.2. Informative References > > > > unmanned-aerial-systems-serial-numbers>. > > > > > [drip-architecture] > > > > Shouldn't be normative? > > [Med] I understand the arch is a useful reading but, technically speaking, > the arch I-D is not required to implement DETs. > > > > > > [drip-authentication] > > > > Same, and then for registries? > > > > > > [Med] No normative language is used when calling out these two I-Ds. These > are provided for illustration purposes, hence the use of "e.g." or "in > practice". Thank you. > > > _____________________________________________________________________________ > ____________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc pas etre diffuses, > exploites ou copies sans autorisation. Si vous avez recu ce message par > erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les > pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; they should not be distributed, > used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
