Re: [tcpdump-workers] [OPSAWG] draft-gharris-opsawg-pcap.txt --- FCS length description

2020-12-21 Thread Michael Richardson via tcpdump-workers
--- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Carsten Bormann wrote: > On 2020-12-22, at 01:31, Michael Richardson wrote: >> >> #define LT_FCS_LENGTH(x) (((x) & 0xF000) >> 28) >> #define LT_FCS_DATALINK_EXT(x) x) & 0xF) << 28) |

Re: [tcpdump-workers] [pcap-ng-format] draft-gharris-opsawg-pcap.txt --- IANA considerations

2020-12-21 Thread Guy Harris via tcpdump-workers
--- Begin Message --- (Resent, from the correct address this time.) On Dec 21, 2020, at 5:51 PM, Michael Richardson wrote: > The short of it is: > > 1) reserve bits 16:28 of linktype as zero. In pcap files, presumably; you have only bits 0:15 in pcapng IDBs. Note that the registry is for both

[tcpdump-workers] draft-gharris-opsawg-pcap.txt --- IANA considerations

2020-12-21 Thread Michael Richardson via tcpdump-workers
--- Begin Message --- The short of it is: 1) reserve bits 16:28 of linktype as zero. 2) lower 32K Specification Required (any document), upper 32K First Come First Served Details: The Registry has three sections according to {{RFC8126}}: * values from 0 to 32767 are marked as Specificatio

[tcpdump-workers] draft-gharris-opsawg-pcap.txt --- FCS length description

2020-12-21 Thread Michael Richardson via tcpdump-workers
--- Begin Message --- {resend due to problems with PGP signatures vs mailman} Hi, I have reworked the document that Guy put into XML describing the *PCAP* (not NG) format. I found the text for LinkType to be confusing, and frankly, I think wrong. * LinkType (32 bits): an unsigned value tha

[tcpdump-workers] man pages... what's cool now? (fwd) Michael Richardson: man pages... what's cool now?

2020-12-21 Thread Michael Richardson via tcpdump-workers
--- Begin Message --- I forgot not to PGP sign. --- End Message --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers