I have, I think (errors may have been made, please check) created a new document:
Name: draft-richardson-opsawg-pcaplinktype title: PCAP and PCAPNG LINKTYPE Registry (just fixed it) Html: https://www.ietf.org/archive/id/draft-richardson-opsawg-pcaplinktype-00.html This document just contains IANA Considerations to create the LINKTYPE Registry. I will remove the BCP14 text, as I don't think it is needed. This document needs to be adopted and passed through a standards track process in order to create the registry. Name: draft-ietf-opsawg-pcap Title: PCAP Capture File Format Html: https://www.ietf.org/archive/id/draft-ietf-opsawg-pcap-01.html This document was partially adopted, but should perhaps be returned to be an individual draft. It has been changed to remove the registry into the above document. Name: draft-tuexen-opsawg-pcapng Title: PCAP Next Generation (pcapng) Capture File Format Html: https://www.ietf.org/archive/id/draft-tuexen-opsawg-pcapng-05.html This document has been minimally changed to point at linktypes rather than at pcap. ** With these changes, draft-ietf-opsawg-pcap (renamed back) and ** draft-tuexen-opsawg-pcapng can be sent for either AD Sponsor or ISE or WG ** processing as Historic and Informational (respectively). I suggest that this requires some clear discussion by this WG. -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
