Re: [tcpdump-workers] Request for link-layer header type (XRA)

On Jan 31, 2018, at 6:07 AM, Bruno Verstuyft wrote: > can I already commit the dissector code for the XRA header to wireshark, or > is it best to wait for finalization of the spec details? At this point, I don't have any further questions; are there any more changes

Re: [tcpdump-workers] Request for link-layer header type (XRA)

2018-01-19 23:21 GMT+01:00 Guy Harris : > On Jan 19, 2018, at 5:03 AM, Bruno Verstuyft > wrote: > > > 2018-01-19 10:10 GMT+01:00 Guy Harris : > > > >> Is the Burst ID just a sequence of octets? > > > > For the moment, the Burst ID

Re: [tcpdump-workers] Request for link-layer header type (XRA)

On Jan 19, 2018, at 5:03 AM, Bruno Verstuyft wrote: > 2018-01-19 10:10 GMT+01:00 Guy Harris : > >> Is the Burst ID just a sequence of octets? > > For the moment, the Burst ID is a uint64_t. Should this not be not enough > in future

Re: [tcpdump-workers] Request for link-layer header type (XRA)

2018-01-19 10:10 GMT+01:00 Guy Harris : > On Jan 4, 2018, at 5:47 AM, Bruno Verstuyft > wrote: > > > are any more clarifications needed for the XRA header spec? > > How is the Symbol ID used for timing calculations? > DOCSIS 3.1 PLC (PHY Link

Re: [tcpdump-workers] Request for link-layer header type (XRA)

On Jan 4, 2018, at 5:47 AM, Bruno Verstuyft wrote: > are any more clarifications needed for the XRA header spec? How is the Symbol ID used for timing calculations? Is the Burst ID just a sequence of octets? What does the Burst ID Reference field contain? Another

Re: [tcpdump-workers] Request for link-layer header type (XRA)

Hi, are any more clarifications needed for the XRA header spec? Best regards, Bruno 2017-12-12 11:17 GMT+01:00 Bruno Verstuyft : > > > 2017-12-11 22:31 GMT+01:00 Guy Harris : > >> On Dec 5, 2017, at 4:47 AM, Bruno Verstuyft

Re: [tcpdump-workers] Request for link-layer header type (XRA)

2017-12-11 22:31 GMT+01:00 Guy Harris : > On Dec 5, 2017, at 4:47 AM, Bruno Verstuyft > wrote: > > > 2017-12-04 22:21 GMT+01:00 Guy Harris : > > > >> On Nov 16, 2017, at 1:21 AM, Bruno Verstuyft > > >>

Re: [tcpdump-workers] Request for link-layer header type (XRA)

On Dec 5, 2017, at 4:47 AM, Bruno Verstuyft wrote: > 2017-12-04 22:21 GMT+01:00 Guy Harris : > >> On Nov 16, 2017, at 1:21 AM, Bruno Verstuyft >> wrote: >> >>> we put the specification of the XRA header online. >> >>

Re: [tcpdump-workers] Request for link-layer header type (XRA)

Updated the specification with clarifications below. 2017-12-05 13:47 GMT+01:00 Bruno Verstuyft : > > > 2017-12-04 22:21 GMT+01:00 Guy Harris : > >> On Nov 16, 2017, at 1:21 AM, Bruno Verstuyft >> wrote: >> >> > we put the

Re: [tcpdump-workers] Request for link-layer header type (XRA)

2017-12-04 22:21 GMT+01:00 Guy Harris : > On Nov 16, 2017, at 1:21 AM, Bruno Verstuyft > wrote: > > > we put the specification of the XRA header online. > > The MAC document speaks of "logical" upstream and downstream channels; are > those what the

Re: [tcpdump-workers] Request for link-layer header type (XRA)

On Nov 16, 2017, at 1:21 AM, Bruno Verstuyft wrote: > we put the specification of the XRA header online. The MAC document speaks of "logical" upstream and downstream channels; are those what the "Downstream Channel ID" and "Upstream Channel ID" TLVs refer to? To

Re: [tcpdump-workers] Request for link-layer header type (XRA)

2017-12-01 18:25 GMT+01:00 Guy Harris : > On Dec 1, 2017, at 3:34 AM, Bruno Verstuyft > wrote: > > >> Type 75 is still labeled as "ODMA REQ" rather than "OFDMA REQ". Also, > it > >> says "ODMA REQ (75): as described by section 7.4.8 "REQ Messages"

Re: [tcpdump-workers] Request for link-layer header type (XRA)

2017-12-01 5:09 GMT+01:00 Guy Harris : > On Nov 29, 2017, at 5:57 AM, Bruno Verstuyft > wrote: > > > thanks for the remarks. The specification is now updated with more > > clarifications > > So "Segment Header Present" is 1 if it's present and 0 if

Re: [tcpdump-workers] Request for link-layer header type (XRA)

On Nov 29, 2017, at 5:57 AM, Bruno Verstuyft wrote: > thanks for the remarks. The specification is now updated with more > clarifications So "Segment Header Present" is 1 if it's present and 0 if it's absent? Type 75 is still labeled as "ODMA REQ" rather than "OFDMA

Re: [tcpdump-workers] Request for link-layer header type (XRA)

Hi, thanks for the remarks. The specification is now updated with more clarifications Best Regards, Bruno 2017-11-23 0:08 GMT+01:00 Guy Harris : > On Nov 21, 2017, at 6:34 AM, Bruno Verstuyft > wrote: > > > we updated the XRA header specification

Re: [tcpdump-workers] Request for link-layer header type (XRA)

Hi, we updated the XRA header specification with more clarifications. Best Regards, Bruno 2017-11-16 22:30 GMT+01:00 Guy Harris : > On Nov 16, 2017, at 1:21 AM, Bruno Verstuyft > wrote: > > > we put the specification of the XRA header online. > >

Re: [tcpdump-workers] Request for link-layer header type (XRA)

On Nov 14, 2017, at 1:35 AM, Bruno Verstuyft wrote: > thanks a lot. Is there any other action needed from our side to be added to > the online linktype list (http://www.tcpdump.org/linktypes.html)? Other than completing the specification at

Re: [tcpdump-workers] Request for link-layer header type (XRA)

Bruno Verstuyft wrote: > we are putting the last hand to the Xra header specification. The > specification will be put on http://www.xra31.com/xra-header when > completed. I meant to ACK that I added that link to comments. -- ] Never tell me

[tcpdump-workers] Request for link-layer header type (XRA)

Hi, at Excentis we are developing a DOCSIS 3.1 RF sniffer (XRA-31). Packets are saved in pcap format with an XRA header. This is a pseudo header that contains extra information on the sniffed DOCSIS packets, e.g. the MER (modulation error rate), SID on which the packets was sniffed, ... Is it