In some email I received from Michael Richardson, sie wrote: > > >>>>> "Darren" == Darren Reed <[EMAIL PROTECTED]> writes: > >> Are we sure that enough people will be asking for data types that we > >> can't just say "ask us for a type value, we'll give one to you"? That > >> seems to have worked pretty well for DLT_ values so far. If they > >> *truly* want it to be private, they can just ask for a number and we'll > >> give it to them, just as we give out private-use DLT_ values such as > >> the ones used by Cisco, Juniper, and IBM. > > Darren> I suppose I'm not so much concerned about it being "private" as it > Darren> being unique. > > Darren> Maybe a vendor field and vendor sub-type field would be useful ? > Darren> That'd give flexibility in an SNMP kind of way. > > okay, divide the 32-bit space into two 16-bit spaces. > vendor 0 will be reserved. > tcpdump.org will be vendor 1. > > vendor 0xffff will be reserved (for the NSA).
Why not make both 32bit ? I say that because design requirements are different, today, than they were 15 years ago. Darren - This is the TCPDUMP workers list. It is archived at http://www.tcpdump.org/lists/workers/index.html To unsubscribe use mailto:[EMAIL PROTECTED]
