1. Robert Moskowitz, Verizon
May 2011
Project: IEEE P 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) ,
Re: Key Managementn over 4e Multipurpose Frames
Abstract: Closing report for HIPIG May 2001 session
Purpose: To inform members on progress
Notice: This document has been prepared to assist the IEEE P 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 P
Robert Moskowitz, Verizon

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

3. Resolution 1 Work is on Key Management Protocol support for 802.15
May 2011
Resolution 1
Work is on Key Management Protocol support for
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
Robert Moskowitz, Verizon

4. May 2011
Resolution 2
The Multipurpose Frame from e 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
Robert Moskowitz, Verizon

5. May 2011
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.
Robert Moskowitz, Verizon

6. May 2011
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
Robert Moskowitz, Verizon

7. May 2011
Resolution 5
only defines single hop operations even though the concept of multi-hop is defined
Any 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)
Robert Moskowitz, Verizon

8. May 2011
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
Robert Moskowitz, Verizon

9. May 2011
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
Robert Moskowitz, Verizon