https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16102
Bug ID: 16102
Summary: IEEE 802.15.4e: add support via ieee802154 dissector
Product: Wireshark
Version: Git
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: Enhancement
Priority: Low
Component: Dissection engine (libwireshark)
Assignee: bugzilla-ad...@wireshark.org
Reporter: dev...@davisinstruments.com
Target Milestone: ---
Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
IEEE 802.15.4-2015 integrated some of the definitions introduced in IEEE
802.15.4e-2012. There are some differences, but in many cases, the dissector
code for 802.15.4e-2012 and 802.15.4-2015 can be shared.
This bug tracks some of the differences that would need to be addressed to use
the existing ieee802154 dissector to handle IEEE 802.15.4e-2012:
1. Multipurpose frame support (see also bug #16101)
This is not fully implemented in the ieee802154 dissector, as multipurpose
frames have a different FCF field definition.
See IEEE 802.15.4-2015 section 7.3.5 for details.
2. Special IEEE 802.15.4e PAN ID compression rules
IEEE 802.15.4-2015 has additional rules for PAN ID compression when short
addresses are used that are not defined in IEEE 802.15.4e-2012. As a result,
some combinations that are permitted by IEEE 802.15.4e-2012 are not permitted
in 802.15.4-2015 and would need to be parsed differently than normal.
See IEEE 802.15.4e-2012 section 5.2.1.1.5 and IEEE 802.15.4-2015 section
7.2.1.5 for details.
3. Special IEEE 802.15.4e wake-up frames (section 5.2.2.8)
IEEE 802.15.4e defines a special cases of multipurpose frames called LE wakeup
frames. It prescribes the use of a one-byte long FCF field that doesn't have
enough bits to fully describe some of the fields that are present. It must be
parsed as a special case.
See IEEE 802.15.4e-2012 section 5.2.2.8 for details.
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
