Re: [tcpdump-workers] [Wireshark-dev] Link type proposal, IEEE 802.1Qbu Frame Preemption Protocol

2017-11-30 Thread Guy Harris 
On Nov 30, 2017, at 1:42 AM, Anton Glukhov  wrote:

> I've been working for IEEE802.1Qbu Frame Preemption Protocol and now it's 
> part of TSN set of protocols. I would like to propose the new link type and 
> sent this proposal to tcpdump-workers@lists.tcpdump.org, but unfortunately no 
> response.

It's hard to respond to a message that was never delivered. :-)

If you're not subscribed to tcpdump-workers, a message you send to the list is 
put in a moderation queue; your message might be in the queue, and the 
moderator might not have gotten around to releasing it.  (I don't know how to 
manage the moderation queue; I found an e-mail message indicating that I'd 
received the moderation password, but I couldn't find anything on how 
moderation was done, and have long since forgotten both the password and the 
procedure for releasing messages.)

It's not a very busy list, so you won't get flooded by e-mail if you subscribe. 
 According to the archives:

http://seclists.org/tcpdump/

in the busiest 3-month period since 2002, 377 messages arrived, for an average 
of a little more than 4 messages per day.  Recently, it's been more like 30-60 
messages in a 3-month period, which is less than one message per day.

Instructions on subscribing can be found at

http://www.tcpdump.org/#mailing-lists

I"m CCing the tcpdump-workers list.

> I'm working for Frame Preemption Protocol(IEEE 802.1Qbu), which is part of 
> Time-Sensitive Networking(TSN) set of standards. The protocol has very 
> interesting extension of standard Ethernet frame and I'd like to propose to 
> add the new link-layer type. Here are the reasons:
> - protocol uses non-standard ethernet preamble, user must see the type of 
> frame/fragment

LINKTYPE_ETHERNET frames don't include the preamble, so a preempting frame with 
a different preamble would look, in an LINKTYPE_ETHERNET capture, exactly like 
a non-preempting frame.

Are you saying that you want a variant of LINKTYPE_ETHERNET, in which the MAC 
header is preceded by something that indicates whether this is a regular or a 
preempting frame, so that captures with this link-layer header type can include 
both regular and preempting frames?

> - protocol uses specific CRC sum. It's called mCRC and depends on preamble, 
> which means the type of frame/fragment

LINKTYPE_ETHERNET may, but aren't guaranteed to, include the CRC; to properly 
check the CRC, the additional metadata giving the frame type would be required, 
so it knows whether it's a regular or modified CRC.
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

[tcpdump-workers] Pull request # 615.

2017-11-30 Thread alice-cyberreboot 
Hi there!

I finally got around to fixing my cloned repo again to get the TravisCI compile 
tests working, and have added some tests for my requested flags. I was 
wondering if I could get feedback on my branch, or if it was good to be pulled. 
It’s been merged with the latest version of your master branch.

Thanks!

Best,
Alice
---
🙋 al...@cyberreboot.org
👾 Cyber Reboot Software Engineer @ In-Q-Tel




"This e-mail, and any attachments hereto, may contain information that is 
privileged, proprietary, confidential and/or exempt from disclosure under law 
and are intended only for the designated addressee(s). If you are not the 
intended recipient of this message, or a person authorized to receive it on 
behalf of the intended recipient, you are hereby notified that you must not 
use, disseminate, copy in any form, or take any action based upon the email or 
information contained therein. If you have received this email in error, please 
permanently and immediately delete it and any copies of it, including any 
attachments, and promptly notify the sender at In-Q-Tel by reply e-mail, fax: 
703-248-3001, or phone: 703-248-3000. Thank you for your cooperation."
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

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

2017-11-30 Thread 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 it's absent?

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" of the DOCSIS 3.1 
Physical Layer Specification. This is the "REQ message in MAC" in figure 7-11 
(56 bits).", but I don't see a figure numbered 7-11 in the DOCSIS 3.1 Physical 
Layer Specification (CM-SP-PHYv3.1-I12-171026) - is this from another version 
of that document?
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

Re: [tcpdump-workers] Link type proposal, IEEE 802.1Qbu Frame Preemption Protocol

2017-11-30 Thread Guy Harris 
On Nov 30, 2017, at 2:27 AM, Anton Glukhov  wrote:

> 1. You are right, I'm not subscribed there. I will fix this problem)

OK, I'm moving the discussion to tcpdump-workers.

> 2. I'd like to have completely separate LinkType number and this is not 
> LINKTYPE_ETHERNET, because preamble must be shown

So for the new link-layer header type will the frame begin with metadata 
indicating the frame type, followed by, preamble/SFD bytes, followed by the MAC 
header, rather than beginning with the MAC header, without the preamble and SFD 
bytes as LINKTYPE_ETHERNET frames do?
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers