[pcap-ng-format] reserving blocks

[Loris Degioanni]

I need 6 blocks, that have to do with capturing system events in a new open
source tool that I'm about to release. Here they are:

MACHINE INFO BLOCK
PROCESS LIST BLOCK
FD LIST BLOCK
EVENT BLOCK
INTERFACE LIST BLOCK
USER LIST BLOCK

The exact block structures are still work in progress, but I will release
the code that implements them.

So if it's ok with you I will use block numbers 0x201->0x206.

Loris


On Fri, Feb 7, 2014 at 12:19 PM, Jasper Bongertz <jasper at packet-foo.com>wrote:

>  Hello Loris,
>
> I don't think there is a real process for that right now. A group of
> developers met last year at Sharkfest at my request to see how to proceed
> with the existing design specifications. The idea at the moment is to make
> an RFC out of it, but that is still in progress. We also did not yet define
> how to add new block types, but we agreed that the existing specification
> minus the experimental block types should become the 1.0 specification. So
> anything added on top of that will be in a later official RFC (if we get it
> to be accepted as an RFC, that is).
>
> What kind of blocks do you need? The hone project added additional block
> types like 0x101 and 0x102 on their own, so maybe you could go with
> something like x201, x202 etc. up for the time being? If that's okay just
> let me know the block types and structures so I can keep track of them.
>
> Cheers,
> Jasper
>
>
> Friday, February 7, 2014, 8:47:49 PM, you wrote:
>
>
>  I need to reserve some pcap-ng block types for a project I'm working on.
> Can anyone remind me the process I need to follow?
>
>  <jasper at packet-foo.com>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winpcap.org/pipermail/pcap-ng-format/attachments/20140207/418d46b0/attachment.html>