[ntar-workers] Use of the application-specific blocks in thepcap-ng file specification

[LEGO]

On 5/12/06, Gianluca Varenni <gianluca.varenni at cacetech.com> wrote:
>
> ----- Original Message -----
> From: "LEGO" <luis.ontanon at gmail.com>
> To: <ntar-workers at winpcap.org>
> Sent: Thursday, May 11, 2006 10:41 AM
> Subject: Re: [ntar-workers] Use of the application-specific blocks in
> thepcap-ng file specification
>
>
> > What about a specific block, like the one for interfaces, to introduce
> > type block numbers by an with application-specific name?
>
> Do you mean something like a block that describes the app-specific block
> type codes used within the file with a name? Something like
>
> APP_SPEC_BLOCKS_DESCRIPTION_BLOCK
>
> Block type code = X  name="This is block with code X created by company Foo"
> Block type code = Y  name="This is block with code Y created by the same
> company Foo"
> .....
> end of APP_SPEC_BLOCKS_DESCRIPTION_BLOCK


Yes, That's what I mean

>
> If so, my first reaction is that it doesn't help too much in solving the
> problem: maybe I'm completely wrong, but it seems to me we are just moving
> the problem from the uniqueness of block codes to the uniqueness of the
> names describing the codes.

Yes, but conflicts are much less probable.

And, if we come out with a naming schema (like
"enterprise_name.this_or_that" )  it would become almost impossible.

L

-- 
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan