Guy Harris <ghar...@sonic.net> wrote:
>> I am much less concerned about getting the exact information in than you
are,
>> and more concerned that we get over this hump.
> I am predominantly concerned that a vague description will lead people
> to write out files that don't match what tcpdump, Wireshark
> etc. expect, leading to pleas for command-line
> options/preferences/etc. to choose how to interpret LINKTYPE_XYZZY.
I understand your concern, and I agree that some descriptions are not as good
as others. But, We, The Tcpdump Group, never promised _Specification
Required_ when we did this ourselves. yes, we often pushed for stable,
public references. So it's a bit confusing since those values are within the
Specification Required category, not easily renumbered.
Yes, I would hate to see command-line driven variants!
Maybe we should swap the two reservation areas?!?
However, I'm not convinced that in this case, better is the enemy of good
enough. I think we could spend a lot of cycles on a lot of obscure cases
that nobody will care about.
https://en.wikipedia.org/wiki/Perfect_is_the_enemy_of_good
(Ah, Voltaire again)
> If the goal is to get the registry created, perhaps the answer is to
> remove all descriptions that aren't good enough and just mark those
> entries as "Reserved for XXX", with later I-Ds -> RFCs specifying them.
> That lets us get something done quickly for the most important
> link-layer types.
I'd rather just leave them there, and if we a better reference document for
some linktype, then the people involved can write it later, updating the
registry to point to that document.
I'm not sure if updates in place (to https://www.tcpdump.org/linktypes/ are
wise.
As for the table width disaster: we can change this to a different
arrangement, like series of:
name: LINKTYPE_LINUX_IRDA,
reference: [LINKTYPE_LINUX_IRDA]
value: 144
description: Linux-IrDA packets
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Description: PGP signature
_______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
