I did giggle when I heard we adopted one but not the other previously I agree we need to proceed and adopt all 3 drafts as proposed
Thanks Anthony Somerset > On 12 Nov 2022, at 06:07, Michael Richardson <mcr+i...@sandelman.ca> wrote: > > > Based upon the three minute discussion on Wednesday morning, and the many many > emails over the past few years(!), do the chairs feel that we have WG > consensus to go with the plan outlined in: > > https://datatracker.ietf.org/meeting/115/materials/slides-115-opsawg-pcappcapng-and-pcap-link-types-revised-proposal-00 > > Specifically: > 1) Adopt draft-richardson-opsawg-pcaplinktype as a WG document, on > Standards Track (so it can create the right registries). > [It really is a boring document] > > 2) Adopt draft-gharris-opsawg-pcap as a WG document to be published as > *Historic* > 3) Adopt draft-tuexen-opsawg-pcap as a WG document to be published as > *Informational* > > (note that there was some half-adoption that occured three IETFs ago, so you > may find there is already draft-ietf-opsawg-FOO) > > For (2) and (3) the alternative is AD Sponsor or ISE, but the AD expressed > preference for the WG to process the document. > > All three documents can be found at: https://github.com/pcapng/pcapng > if there are pull requests that someone would like to make when they do their > review. > > -- > Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works > -= IPv6 IoT consulting =- > > > > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg This email disclaimer applies to the original email, all attachments and any subsequent emails sent by Liquid Telecom. This email contains valuable business information that is privileged, confidential and/or otherwise protected from disclosure, intended only for the named person or entity to which it is addressed. If you are not the intended recipient of this email and you received this e-mail in error, any review, use, dissemination, distribution, printing or copying of this e-mail is strictly prohibited and may be unlawful and/or an infringement of copyright. Please notify us immediately of the error and permanently delete the email from your system, retaining no copies in any media. No employee or agent is authorized to conclude any binding agreement on behalf of Liquid Telecom with another party or give any warranty by email without the express written confirmation by an authorized representative or a director of Liquid Telecom. Nothing in this email shall be construed as a lega lly binding agreement or warranty or an offer to contract. Liquid Telecom will not be responsible for any damages suffered by the recipient as a result of the recipient not taking cognizance of this principle. Liquid Telecom accepts no liability of whatever nature for any loss, liability, damage or expense resulting directly or indirectly from the access of any files which are attached to this message. Any email addressed to Liquid Telecom shall only be deemed to have been received once receipt is confirmed by Liquid Telecom orally or in writing. An automated acknowledgment of receipt will not suffice as proof of receipt by the Liquid Telecom. This email disclaimer shall be governed by the laws of South Africa. _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
