Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

1. Robert Moskowitz, Verizon Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: HIPIG Agenda LAX 2011 Date Submitted: January 17, 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: HIP IG Opening Report for January 2011 Session Abstract: Opening report for the HIP IG Session. Purpose: To focus activities during the meeting 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. Los Angeles January 20, 2011 HIPIG Agenda /Opening Report Robert Moskowitz, Verizon

3. Robert Moskowitz, Verizon Abstract • To provide for a Key Management Protocol for 802.15.4 • Minimally to support HIP • Allow for other KMPs • To present use scenarios and how a KMP facilitates security in those scenarios.

4. Robert Moskowitz, Verizon Meeting Protocol Please announce your affiliation when you first address the group during a meeting slot

5. Attendance https://murphy.events.ieee.org/imat/attendance/index Register Indicate attendance

6. Attendance https://murphy.events.ieee.org/imat/attendance/index • Register • Indicate attendance

7. Participants, Patents, and Duty to Inform January 2011 All participants in this meeting have certain obligations under the IEEE-SA Patent Policy. Participants: • “Shall inform the IEEE (or cause the IEEE to be informed)” of the identity of each “holder of any potential Essential Patent Claims of which they are personally aware” if the claims are owned or controlled by the participant or the entity the participant is from, employed by, or otherwise represents • “Personal awareness” means that the participant “is personally aware that the holder may have a potential Essential Patent Claim,” even if the participant is not personally aware of the specific patents orpatent claims • “Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of such potential Essential Patent Claims” (that is, third parties that are not affiliated with the participant, with the participant’s employer, or with anyone else that the participant is from or otherwise represents) • The above does not apply if the patentclaim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) under consideration by this group Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6.2 • Early identification of holders of potential Essential Patent Claims is strongly encouraged • No duty to perform a patent search Slide 7 Hiroshi Mano (Root Inc.)

8. Patent Related Links January 2011 All participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development. Patent Policy is stated in these sources: IEEE-SA Standards Boards Bylaws http://standards.ieee.org/guides/bylaws/sect6-7.html#6 IEEE-SA Standards Board Operations Manual http://standards.ieee.org/guides/opman/sect6.html#6.3 Material about the patent policy is available at http://standards.ieee.org/board/pat/pat-material.html If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee.org or visit http://standards.ieee.org/board/pat/index.html This slide set is available at http://standards.ieee.org/board/pat/pat-slideset.ppt Slide 8 Hiroshi Mano (Root Inc.)

9. Call for Potentially Essential Patents January 2011 If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance: • Either speak up now or • Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible or • Cause an LOA to be submitted Slide 9 Hiroshi Mano (Root Inc.)

10. Goals • Produce a Recommended Practice • Use 'existing' frames to carry KMP • Avoid long time line for amendment • Dependencies • TG4e Information Elements • ? TG4g large datagrams • Else need chaining of IEs across datagrams

11. Discussion • Base scenario – Static star, KMP at join • What frames carry KMP? • Assume IEs via 4e • What frames carry KMP updates? • End to End KMP? • Mesh via multiple controllers • End to End KMP?

12. Discussion • Information Elements • How many IE IDs needed? • What is max size of value pre 4g? • What is max size post 4g? • How to support chaining • IE format for support • Frame flow for support

13. Discussion • Information Elements • Value format • If KMP designed on IP (e.g. IKE & HIP) start with IP protocol # ? • Other points to discuss

14. Next Steps • How to prepare text for next session • Singapore? • Scenario text • Other?