1. Robert Moskowitz, Verizon Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: HIPIG Closing Report for May 2011 Date Submitted: May 10, 2011 Source: Robert Moskowitz, Verizon Address 1000 Bent Creek Blvd, MechanicsBurg, PA, USA Voice:+1 (248) 968-9809, e-mail: rgm@labs.htt-consult.com Re: Key Managementn over 4e Multipurpose Frames Abstract: Closing report for HIPIG May 2001 session Purpose: To inform 802.15 members on progress Notice: This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.

2. Robert Moskowitz Palm Springs May 10, 2011 HIPIG Closing Report for May 2011 Robert Moskowitz, Verizon

3. Robert Moskowitz, Verizon Resolution 1 • Work is on Key Management Protocol support for 802.15 • For which it is preferred that the default is HIP DEX • Study group SHOULD be named • WPAN KMP SG • And we are ready for a Study Group

4. Robert Moskowitz, Verizon Resolution 2 • The Multipurpose Frame from 802.15.4e provides the needed MAC framework for a KMP and basic MAC changes are not needed for KMP support by using it. • KMP will be via a specific IE in a Multipurpose Frame exchange

5. Robert Moskowitz, Verizon Resolution 3 • The KMP will assume the MTU is large enough for the KMP payloads. It will be up to the IE encapsulating component to manage 'fragmentation' through a 'frame chaining' process. • The MAC has better knowledge of what size MTUs can successfully be transmitted at any given time.

6. Robert Moskowitz, Verizon Resolution 4 • The KMP SHOULD be capable of determining and assigning the WPAN short addresses • For example the HIT's (Host Identity Tag) lower 16 bits so R1 and on can be over short addresses • Collision resolution WILL be included

7. Robert Moskowitz, Verizon Resolution 5 • 802.15.4 only defines single hop operations even though the concept of multi-hop is defined • Any 802.15 KMP recommended practice can only define a single hop KMP, as there is no MAC frame forwarding mechanism. End-to-end KMP for meshes MUST be defined elsewhere (e.g. IETF core or roll wg)

8. Robert Moskowitz, Verizon Resolution 5a • Multi-hop KMP can be specified via a liasoning process with the IETF • We tell them how to use the KMP IE, they provide us with some parameter values

9. Robert Moskowitz, Verizon Conclusion • A document will be prepared for the July Plenary session fleshing out these items to be used to for a KMP Study Group that will produce the KMP PAR