[pcap-ng-format] [tcpdump-workers] New Version Notification for draft-tuexen-opsawg-pcapng-02.txt

Michael Tuexen tuexen at fh-muenster.de
Mon Sep 28 21:20:06 UTC 2020



> On 28. Sep 2020, at 23:08, Guy Harris <gharris at sonic.net> wrote:
> 
> On Sep 28, 2020, at 2:00 PM, Michael Tuexen <tuexen at fh-muenster.de> wrote:
> 
>> On 28. Sep 2020, at 22:48, Guy Harris <gharris at sonic.net> wrote:
>> 
>>> On Sep 28, 2020, at 1:42 PM, Michael Tuexen <tuexen at fh-muenster.de> wrote:
>>> 
>>>> Shouldn't we write up (I can work on an initial version) of
>>>> a specification for .pcap.
>>> 
>>> 	https://github.com/pcapng/pcapng/blob/master/draft-gharris-opsawg-pcap.xml
>> 
>> Cool. Do you want to publish it as an RFC?
> 
> At some point.
> 
> Currently, I view it as "up for review by the community", and there have been pull requests from the community applied.
> 
> Should its publication coincide with the introduction of an IANA registry of link-layer data types (replacing the tcpdump.org one)?
I would say: yes.
> 
> Should we publish one RFC for the pcap format and one RFC that includes the current content of the registry?  (The latter would probably be much bigger than the former....)
No. I would suggest to describe the registry in the IANA Considerations. One part of the discussion would be the initial contents.

If you want to publish that soon (for whatever meaning), I would be willing to read the document and provide
feedback, if you want with the perspective of publication. Just let me know.

Best regards
Michael

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5257 bytes
Desc: not available
URL: <http://www.winpcap.org/pipermail/pcap-ng-format/attachments/20200928/c691eb5e/attachment-0001.bin>


More information about the pcap-ng-format mailing list