Hi Tero, Thanks for the review. We can update Section 6.1 with another example. Please see https://author-tools.ietf.org/api/iddiff?url_1=https://boucadair.github.io/ipfix-tcpoptions-and-v6eh/draft-ietf-opsawg-ipfix-tcpo-v6eh.txt&url_2=https://boucadair.github.io/ipfix-tcpoptions-and-v6eh/boucadair-patch-9/draft-ietf-opsawg-ipfix-tcpo-v6eh.txt Cheers, Med Orange Restricted > -----Message d'origine----- > De : Tero Kivinen via Datatracker <noreply@xxxxxxxx> > Envoyé : jeudi 13 juin 2024 13:40 > À : secdir@xxxxxxxx > Cc : draft-ietf-opsawg-ipfix-tcpo-v6eh.all@xxxxxxxx; last- > call@xxxxxxxx; opsawg@xxxxxxxx > Objet : Secdir last call review of draft-ietf-opsawg-ipfix-tcpo- > v6eh-15 > > > Reviewer: Tero Kivinen > Review result: Has Nits > > This is the re-review of the document. There are still several > places where the draft uses [RFC1234] without giving any > indication what document that is, requiring readers to have the > mapping from RFC numbers to names. This will cause extra effort > for new people who try to understand the this protocol. > I know it is annoying for the author to have to add those things, > but hopefully this document will have more readers than authors, > so the one time cost of adding them will help multiple readers > while reading the document. I know that there are RFCs where the > number of authors is about the same than number of readers, but I > hope this is not one of them... > > There is still no example in section 6.1 with multi-octet > options, having such example would make it easier for readers to > know which byte is sent first and so on. > > ____________________________________________________________________________________________________________ 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 To unsubscribe send an email to last-call-leave@xxxxxxxx
