Hi Michael, OK, thanks. Publishing the doc as Info would be OK then.
I sent you right now a PR with some minor edits. For the specification required range, you may consider adding some guidance for DEs. The initial table does not mirror the current values in https://www.tcpdump.org/linktypes.html. Also, some descriptions in the table does not match exactly what is in that table. Not sure if it is worth explaining the diff. You may indicate that the procedure for assigning new codes as detailed in https://www.tcpdump.org/linktypes.html won't be followed anymore. Some assigned types seem to be used for private use while these types fall now under a specification required range. I don't know if it is worth to have some consistency here and consider a range for future specification required type, e.g., 300-32767 that won't be mixed with the historic ones. Cheers, Med > -----Message d'origine----- > De : Michael Richardson <mcr+i...@sandelman.ca> > Envoyé : lundi 24 juillet 2023 09:58 > À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>; > opsawg@ietf.org > Objet : Re: [OPSAWG] PCAP documents (was Re: I-D Action: draft- > ietf-opsawg-pcap-03.txt) > > > mohamed.boucad...@orange.com wrote: > >> draft-ietf-opsawg-pcaplinktype needs to be standards track > to > >> establish the needed registries. The document does very > little else. > > > I used to know that IANA registries can be created also for > Info > > documents, including ISE published documents (see, e.g., > > https://www.iana.org/assignments/iax-parameters/iax- > parameters.xhtml). > > Well, I was told this by the previous ISE. > > My understanding is that a non-standards track document can not > use 7. RFC > Required,8. IETF Review,9. Standards Action, or 10. IESG > Approval. > > Now, linktypes "highest" level is Specification Required. > > -- > Michael Richardson <mcr+i...@sandelman.ca> . o O ( IPv6 IøT > consulting ) > Sandelman Software Works Inc, Ottawa and Worldwide > > > ____________________________________________________________________________________________________________ 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. _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
