Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [802SEC] Response to Commentors on 802.15 KMP PAR

Thanks for addressing 802.21 comments. Our members accept all the resolutions
except the following one:

Current text: “Are there other standards or projects with a similar
scope?: No”
Comment: This is not correct. For example, ZigBee IP uses PANA (RFC
5191) as the KMP to provide MAC keys for 802.15.4 based HAN in ZigBee
Smart Energy Profile 2.0 (SEP2.0), where UDP/IP is used as the
transport of the PANA KMP.

802.15 Response:
We believe this is the correct answer. Within the context of IEEE 802,
this is true. The ZigBee example is limited to supporting ZigBee IP
usage, and does not support other uses of 802.15.4 or 802.15.7. It
also does not support securing the IPv6 neighbor discovery (that is
the start of IPv6) within ZigBee IP."

802.21 response:
We understand that the scope is not exactly the same as ZigBee IP, however,
the scope is similar in the sense that both ZigBee IP and the proposed PAR
are used to provide MAC keys for 802.15.4. We believe that this similarity needs
to be mentioned in the PAR, together with the difference described in
the above response.


On 11/9/2011 4:47 PM, Bob Heile wrote:

We received five sets of comments on the KMP PAR and 5C. They were from:
* 802.15.6 Task Group
* 802.11 Working Group
* 802.21 Working Group
* IEEE 802.1 Working Group
* Rene Struik 802.15 voting member
Attached are three documents, a word doc containing all the comments received and responses to them, a redline of the PAR and a revised copy of the 5C reflecting those responses. I will send a redline of the 5C once I track it down.



Bob Heile, Ph.D
Chairman, ZigBee Alliance
Chair, IEEE 802.15 Working Group on Wireless Personal Area Networks
Co-Chair IEEE P2030 Task Force 3 on Smartgrid Communications
11 Robert Toner Blvd
Suite 5-301
North Attleboro, MA 02763 USA
Mobile: +1-781-929-4832

This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.

This email is sent from the 802 Executive Committee email reflector.  This list is maintained by Listserv.