Guy Harris <ghar...@sonic.net> wrote:
    > On Aug 12, 2024, at 5:03 AM, Michael Richardson <mcr+i...@sandelman.ca> 
wrote:

    >> I wish we set the pcap"ng" version field to "3", following from pcap v2 
being
    >> the last.  It could be done perhaps, and pcap"ng" could be version pcap3.

    > I wish we'd avoided using the string "pcap" in the name of the
    > extensible capture file format, as the extensible capture file format

I'm open to avoiding those four letters too.
I just figured we couldn't get away with that, and I just want useful nouns
that can be used to describe things.

    > I.e., the extensible capture file format would not have been "pcapv3"
    > even if the initial major version number value were 3.  It's a
    > different format from pcap that inherits a few concepts from pcap

Yes, I agree.

    > So maybe just call it "extensible capture fie format".  Sadly, .ecf is 
already in use:

    > 
https://learn.microsoft.com/en-us/answers/questions/552563/fxsext-ecf-windows-10-file

    > and so is .xcf:

    > https://en.wikipedia.org/wiki/XCF_(file_format)

    > but a quick Google search doesn't pop up any obvious .ecff extension.
    > Or maybe we should have something other than "capture", as Falco:

ecff.
Do I pronounce it with a lot of raspberry? "ec-pfffth"
Seems like it might be a colour:
https://www.colorhexa.com/0e0cff  - Blue
https://www.colorhexa.com/e0c0ff  - Pale Violet

    > But there are already a lot of files in that format with .pcapng as the 
extension.

    > (And, speaking of version numbers, it's perhaps unfortunate that the
    > extensible capture file format has version numbers - if it has to be
    > changed so incompatibly that the version number has to be changed,
    > that's a sign that the extensibility failed. But removing it would
    > *itself* require a major version number change, as old code won't be
    > able to read the new files.  A major goal of the extensibility is to
    > allow old code to read new files, albeit with a loss of information.)

Yes.

--
Michael Richardson <mcr+i...@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

Attachment: signature.asc
Description: PGP signature

_______________________________________________
OPSAWG mailing list -- opsawg@ietf.org
To unsubscribe send an email to opsawg-le...@ietf.org

Reply via email to