[email protected] 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://datatracker.ietf.org/meeting/115/materials/slides-115-opsawg-pcappcapng-and-pcap-link-types-revised-proposal-00

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 <[email protected]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide




Attachment: signature.asc
Description: PGP signature

_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg

Reply via email to