Hi Michael, For this part:
> 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). I'm reacting to this because this is the second message from you that I read recently with this argument (drip-reg I-d :-)), so I'm interested to hear if there were changes in IANA practices to require a PS doc. Thank you. Cheers, Med > -----Message d'origine----- > De : OPSAWG <opsawg-boun...@ietf.org> De la part de Michael > Richardson > Envoyé : dimanche 23 juillet 2023 17:04 > À : opsawg@ietf.org > Objet : [OPSAWG] PCAP documents (was Re: I-D Action: draft-ietf- > opsawg-pcap-03.txt) > > > internet-dra...@ietf.org wrote: > > Title : PCAP Capture File Format Authors : > > Filename : draft-ietf-opsawg-pcap-03.txt > > > Title : PCAP Next Generation (pcapng) Capture File > Format > > Filename : draft-ietf-opsawg-pcapng-01.txt > > > Title : Link-Layer Types for PCAP and PCAPNG > Capture File Formats > > Filename : draft-ietf-opsawg-pcaplinktype-01.txt > > To remind: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F > datatracker.ietf.org%2Fmeeting%2F115%2Fmaterials%2Fslides-115- > opsawg-pcappcapng-and-pcap-link-types-revised-proposal- > 00&data=05%7C01%7Cmohamed.boucadair%40orange.com%7C4bd45b85b2d04a0 > e0e9d08db8bd97f6c%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638 > 257538483426599%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIj > oiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bya > R%2Fax8Oy2N23%2FvXuZ87fHcBEIvqd%2BoYbkXe5gm98g%3D&reserved=0 > > draft-ietf-opsawg-pcaplinktype needs to be standards track to > establish the needed registries. The document does very little > else. > It can and should be WGLC already. > > We agreed that PCAP would be published as HISTORICAL. > We also agreed that PCAPNG would be published as Informational, > and could be revised to standards track under IETF change control. > (When we started this work back in 2012, the story for pcapng was > different) > > I would like to rename "PCAP NG" as something less "NG". > I'd suggest PCAP 2022 or something like that. > > -- > 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
