[prev in list] [next in list] [prev in thread] [next in thread]
List: wireshark-dev
Subject: Re: [Wireshark-dev] Link type proposal, IEEE 802.1Qbu Frame Preemption Protocol
From: Anton Glukhov <anton.a.glukhov () gmail ! com>
Date: 2017-11-30 10:27:50
Message-ID: CAE2L+hx6TY=7Jyb90JgPR1wML4hZ5vRTPteupw4kCjvb5e3=+w () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
1. You are right, I'm not subscribed there. I will fix this problem)
2. I'd like to have completely separate LinkType number and this is
not LINKTYPE_ETHERNET,
because preamble must be shown with specific SMD bytes, and CRC or mCRC
must be also shown.
This linktype will show both regular and preemption traffic, with preamble
and CRC for both of these types. So, my point of view, is to assign the new
linktype which not related to LINKTYPE_ETHERNET or regular Ethernet traffic.
Thank you!
2017-11-30 11:10 GMT+01:00 Guy Harris <guy@alum.mit.edu>:
> On Nov 30, 2017, at 1:42 AM, Anton Glukhov <anton.a.glukhov@gmail.com>
> 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.
> ____________________________________________________________
> _______________
> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@wireshark.org?subject=
> unsubscribe
[Attachment #5 (text/html)]
<div dir="ltr"><div><div><div>1. You are right, I'm not subscribed there. I will \
fix this problem)<br></div>2. I'd like to have completely separate LinkType \
number and this is not <span class="gmail-im"></span>LINKTYPE_ETHERNET, because \
preamble must be shown with specific SMD bytes, and CRC or mCRC must be also \
shown.<br></div>This linktype will show both regular and preemption traffic, with \
preamble and CRC for both of these types. So, my point of view, is to assign the new \
linktype which not related to <span class="gmail-im"></span>LINKTYPE_ETHERNET or \
regular Ethernet traffic.<br><br></div><div>Thank \
you!<br></div><div><div><div><div><br><div><div><div><div \
class="gmail_extra"><br><div class="gmail_quote">2017-11-30 11:10 GMT+01:00 Guy \
Harris <span dir="ltr"><<a href="mailto:guy@alum.mit.edu" \
target="_blank">guy@alum.mit.edu</a>></span>:<br><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><span class="gmail-">On Nov 30, 2017, at 1:42 AM, \
Anton Glukhov <<a \
href="mailto:anton.a.glukhov@gmail.com">anton.a.glukhov@gmail.com</a>> wrote:<br> \
<br> > 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 <a \
href="mailto:tcpdump-workers@lists.tcpdump.org">tcpdump-workers@lists.tcpdump.<wbr>org</a>, \
but unfortunately no response.<br> <br>
</span>It's hard to respond to a message that was never delivered. :-)<br>
<br>
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.)<br> <br>
It's not a very busy list, so you won't get flooded by e-mail if you \
subscribe. According to the archives:<br> <br>
<a href="http://seclists.org/tcpdump/" rel="noreferrer" \
target="_blank">http://seclists.org/tcpdump/</a><br> <br>
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.<br> <br>
Instructions on subscribing can be found at<br>
<br>
<a href="http://www.tcpdump.org/#mailing-lists" rel="noreferrer" \
target="_blank">http://www.tcpdump.org/#<wbr>mailing-lists</a><br> <br>
I"m CCing the tcpdump-workers list.<br>
<span class="gmail-"><br>
> 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:<br> > - protocol uses non-standard ethernet \
preamble, user must see the type of frame/fragment<br> <br>
</span>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.<br> <br>
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?<br> <span class="gmail-"><br>
> - protocol uses specific CRC sum. It's called mCRC and depends on preamble, \
which means the type of frame/fragment<br> <br>
</span>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.<br> \
______________________________<wbr>______________________________<wbr>_______________<br>
Sent via: Wireshark-dev mailing list <<a \
href="mailto:wireshark-dev@wireshark.org">wireshark-dev@wireshark.org</a>><br>
Archives: <a href="https://www.wireshark.org/lists/wireshark-dev" \
rel="noreferrer" target="_blank">https://www.wireshark.org/<wbr>lists/wireshark-dev</a><br>
Unsubscribe: <a href="https://www.wireshark.org/mailman/options/wireshark-dev" \
rel="noreferrer" target="_blank">https://www.wireshark.org/<wbr>mailman/options/wireshark-dev</a><br>
mailto:<a href="mailto:wireshark-dev-request@wireshark.org">wireshark-dev-request@<w \
br>wireshark.org</a>?subject=<wbr>unsubscribe</blockquote></div><br></div></div></div></div></div></div></div></div></div>
[Attachment #6 (text/plain)]
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic