Hi Michael, Agree with your proposal (1) below.
I think that we can avoid the "ng" mentions in the Historical doc. I sent you a PR right now with some few changes: https://github.com/IETF-OPSAWG-WG/draft-ietf-opsawg-pcap/pull/187#pullrequestreview-3033954886. Thanks for the continuous effort put on this IDs set. Cheers, Med (as contributor) > -----Message d'origine----- > De : Michael Richardson <mcr+i...@sandelman.ca> > Envoyé : vendredi 18 juillet 2025 11:51 > À : opsawg@ietf.org > Objet : [OPSAWG]some questions to the WG about *pcap* > > > (0. Somewhere I had an email asking of I had IPR, and I can't find > that email, so here is my public statement that I have none.) > > 1. In draft-ietf-opsawg-pcap we suggest that we are going to fill > the > contributors section in with the contents of > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi > thub.com%2Fthe-tcpdump- > group%2Flibpcap%2Fblob%2Fmaster%2FCREDITS&data=05%7C02%7Cmohamed.bou > cadair%40orange.com%7C6a18431da4974fbd0d4508ddc5e0a369%7C90c7a20af34 > b40bfbc48b9253b6f5d20%7C0%7C0%7C638884290782185577%7CUnknown%7CTWFpb > GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsI > kFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=LYmpbSlixv64q8kHr > Xbzi9jjnlXfn0OX%2Fssz9lIMT0g%3D&reserved=0 > > Is the WG okay with this? I propose names, not email addresses. > I propose using the XML mechanism for contributors, not free-form. > > 2. I've made some minor edits around the endian clue from the magic > number, which are now: > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi > thub.com%2FIETF-OPSAWG-WG%2Fdraft-ietf-opsawg- > pcap%2Fpull%2F187&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C6a > 18431da4974fbd0d4508ddc5e0a369%7C90c7a20af34b40bfbc48b9253b6f5d20%7C > 0%7C0%7C638884290782216674%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiO > nRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf > Q%3D%3D%7C0%7C%7C%7C&sdata=5e62GsrxBVN4nUNWzuRZLkO1X3alB5vYFXRutWSjx > %2F4%3D&reserved=0 > Also that version numbers are independent. > > 3. I clarified document to say it's intention is historical. > > 4. I'd really like to rename pcapng -> ecap. > Since pcap refers to it as "new" work, it needs to know the name. > pcapng^Wecap would be published as Informational, because IETF > can not > make significant changes to it. > If there energy to revise ecap, then we would do the normal "2.0" > > > -- > Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works > -= IPv6 IoT consulting =- *I*LIKE*TRAINS* > > ____________________________________________________________________________________________________________ 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 To unsubscribe send an email to opsawg-le...@ietf.org
