Hi Chris, Thanks for the review and for double checking that your initial review was addressed. The use of the nonce in the document is consistent with its usage in other LISP specs, especially RFC9301. If there is any change, this would be in these authoritative documents. I appreciate that you ACK that this has no operational problem. Cheers, Med > -----Message d'origine----- > De : Chris Lonvick via Datatracker <noreply@xxxxxxxx> > Envoyé : vendredi 27 janvier 2023 02:07 > À : secdir@xxxxxxxx > Cc : draft-ietf-lisp-pubsub.all@xxxxxxxx; last-call@xxxxxxxx; > lisp@xxxxxxxx > Objet : Secdir last call review of draft-ietf-lisp-pubsub-10 > > Reviewer: Chris Lonvick > Review result: Has Nits > > Hi, > > I have reviewed this document as part of the security > directorate's ongoing effort to review all IETF documents being > processed by the IESG. These comments were written primarily for > the benefit of the security area directors. Document editors and > WG chairs should treat these comments just like any other last > call comments. > > It appears that the issue that I brought up in my early review of > the draft has not been addressed. The draft continues to use the > term nonce in a way that is not consistent with RFC 4949. This is > likely not an operational problem as the rules defined for using > it are well described in the document. This could be addressed by > stating that a nonce is generated in the Map-Request, and the > value of the nonce is used in subsequent exchanges. > > The TSVART reviewer of the draft seems to be much more familiar > with LISP than I, and brings up a lot of security issues. I would > like to see those issues addressed. > > Regards, > Chris > _________________________________________________________________________________________________________________________ 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
