July 2013 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Technical Decisions for KMP transport Date Submitted: July 17, 2013 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 Management over 4e Multipurpose Frames Abstract: Technical decisions for KMP transport Purpose: To refine our understanding of the transport mechism 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. Slide 1 Robert Moskowitz, Verizon Page 1

Technical Decisions for KMP Transport July 2013 Technical Decisions for KMP Transport Robert Moskowitz Geneva, CH July 17, 2013 Slide 2 Robert Moskowitz, Verizon Page 2

Item 1: Address Format SHOULD use long addresses Short address MAY be used to update existing SAs Why? Short addresses may have been defined is a 'secure' manner? Change to MAY or add additional text? Slide 3 Robert Moskowitz, Verizon Page 3

Item 2: ACK no proof of process March 2013 Item 2: ACK no proof of process The receiver could drop the packet after sending the ACK eg buffer full ACK is indication of receipt, not processing ACTION: ?

Inbound Frame Processing Yes Dup to prior Src Addr, Seq, IE Drop No Error 1 98 Start KMP assembly Chaining flag Multi-purpose 2 to 95 Error 98 Complete KMP Multi-purpose Append KMP 2 to 96 2 to 96 Per Src addr Append to list and complete Robert Moskowitz, Verizon Page 5

Item 3: MACFrameCounter March 2013 Item 3: MACFrameCounter Recommended to rekey at 100 < max Recommend a MLME SAP to set a PIB entry for this threshold ACTION: MACRekeyThreshold will be value

Item 4: Crypto Agility 15.4 really does not have crypto agility March 2013 Item 4: Crypto Agility 15.4 really does not have crypto agility Security levels indicate ICV length Security level CAN be varied by datagram by higher layer KMPs tend to negotiate cipher suites 15.4 would need to be amended to add other cipher suites ISSUE: Should KMP text discuss cipher negotiation or how to not do it?

Item 5: KMP documentation format March 2013 Item 5: KMP documentation format Really not 'technical' but... KMP specific text might be best covered as informative annexes DISCUSS: How to organize KMP specific text

March 2013 Any other ITEMS ???? Open discussion