On Aug 6, 2024, at 10:59 AM, Michael Richardson <mcr+i...@sandelman.ca> wrote:
> Hi, I believe that pcaplinktype is ready for WGLC as Standards Track document. What does "last call" mean in this context? The current version has a number of link-layer types that need to have better descriptions, where "better" means "make the description in the table short, and give a reference to a document giving a more detailed description". I've done that for some link-layer types, such as LINKTYPE_NULL, in the current version, but it needs more. Currently, many of the description pages are hosted on the tcpdump.org Web site; is there a better place to host them, such as the GitHub site for these documents? > I would dearly like to call it anything other than pcap *NG*, because 15 > years later, it's not "Next" anymore. pcapv2 would satisfy me. After 15 years, it's probably an uphill climb to get people to stop calling it "pcapng" and using ".pcapng" as a file extension. A new name could be used in the document, but it'll take a while for it to catch on. And, given that both pcap classic and pcap extensible have version numbers (in the file header for pcap classic, in the Section Header Block for pcap extensible), calling it "pcapv2", with the implication that pcap classic is "pcapv1", might be a bit confusing, given that the current version number for pcap classic is 2.4 and the current version number for pcap extensible is 1.0. > This leaves open the future possibility of a fully IETF designed pcapv3, Or perhaps a name that doesn't include a version number. > or a series of pcapv2 extensions that does effectively the same thing, At one point I thought that, once the specifications were all RFCs, with a process for filing new I-Ds/RFCs for new link-layer types, of filing an April 1 RFC for a link-layer type called LINKTYPE_PCAP_BLOCK, in which the "packet data" is a pcap extensible block (i.e., pcapng inside a pcap file). _______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
