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

2020-12-22 Thread Michael Richardson
Guy Harris wrote: > On Dec 22, 2020, at 8:36 AM, Michael Richardson wrote: >> Guy Harris wrote: >> >>> And, as per my idea of using 65535 to mean "custom linktype", similar >>> to pcapng custom blocks and options, with either: >> >> I'm happy with this proposal, bu

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

2020-12-22 Thread Adrian Farrel
Hi, I'm pitching in here as Independent Submissions Editor (ISE). I really should use the proper email for this (rfc-...@rfc-editor.org) but I'm sticking with this address as it is already subscribed to the OPSAWG list. Responding to this particular email because (I think) it is the first one t

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

2020-12-22 Thread Guy Harris
On Dec 22, 2020, at 8:36 AM, Michael Richardson wrote: > Guy Harris wrote: > >> And, as per my idea of using 65535 to mean "custom linktype", similar >> to pcapng custom blocks and options, with either: > > I'm happy with this proposal, but isn't it pcapng specific? No - it's *cleaner* to imp

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

2020-12-22 Thread Michael Richardson
wrote: >> -Message d'origine- >> De : OPSAWG [mailto:opsawg-boun...@ietf.org] De la part de Michael >> Richardson >> Envoyé : mardi 22 décembre 2020 17:36 >> À : Guy Harris >> Cc : Pcap-ng file format ; >> opsawg@ietf.org; tcpdump-workers >> Objet : Re: [

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

2020-12-22 Thread mohamed.boucadair
Hi Michael, One comment inline. Cheers, Med > -Message d'origine- > De : OPSAWG [mailto:opsawg-boun...@ietf.org] De la part de Michael > Richardson > Envoyé : mardi 22 décembre 2020 17:36 > À : Guy Harris > Cc : Pcap-ng file format ; > opsawg@ietf.org; tcpdump-workers > Objet : Re: [O

Re: [OPSAWG] [pcap-ng-format] draft-gharris-opsawg-pcap.txt --- FCS length description

2020-12-22 Thread Michael Richardson
<#secure method=pgp mode=sign> Guy Harris wrote: > a 6-bit "extension" field, storing information about the > capture, such an indication of whether the packets include an > FCS and, if so, how many bytes of FCS are present. > So what NetBSD had was a convention where a capture

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

2020-12-22 Thread Michael Richardson
<#secure method=pgp mode=sign> Guy Harris 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. Yes. That's why I changed the illustration of the packet so that only 16 bits were in t

Re: [OPSAWG] [pcap-ng-format] draft-gharris-opsawg-pcap.txt --- FCS length description

2020-12-22 Thread Guy Harris
On Dec 22, 2020, at 1:01 AM, Guy Harris wrote: > They were originally intended for use with some stuff NetBSD was doing (I'd > have to look into the history of the NetBSD code), but I think NetBSD stopped > doing that. The commit message for the change that added the macros was: commit afbb1c

Re: [OPSAWG] [pcap-ng-format] draft-gharris-opsawg-pcap.txt --- FCS length description

2020-12-22 Thread Guy Harris
On Dec 21, 2020, at 4:31 PM, Michael Richardson wrote: > 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 that defines, in