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

1. Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Cipher Suite Framework Presentation] Date Submitted: [January, 2002] Source: [Ari Singer, Principal Engineer & Daniel Bailey, Product Manager for Wireless Networks] Company [NTRU] Address [5 Burlington Woods] Voice:[(781) 418-2500], FAX: [(781) 418-2532], E-Mail:[asinger@ntru.com] Re: [Doc. IEEE 802.15-02/045r0 (Cipher Suite Framework Proposal), Draft P802.15.3/D09] Abstract: [This presentation summarizes NTRU’s proposal for the cipher suite framework (included in a separate submission).] Purpose: [To familiarize the working group with the proposed cipher suite framework.] 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. Purpose of Document • Improve security design from P802.15.3 D09 • Provide additional text for 802.15.3 security section • Clearly spell out requirements for cipher suites • Provide a straw man design for cipher suite submission

3. Document Contents • Security model description • Functional security description • Protocol diagrams • Additional information elements • Revised commands • Cipher suite specification description • Evaluation criteria (to be filled in)

4. Security Model • Mandatory piconet mutual authentication • Recommended piconet payload protection • Optional peer-to-peer security • same services as group security • Defines use of public keys and symmetric keys

5. Security Model (2) • Trust of public keys is determined • DEVs perform mutual auth. with PNC • PNC ensures that each DEV obtains piconet keys • Piconet data is protected by piconet keys DEV A DEV B PNC DEV C Key Piconet Key(s) Peer-to-peer Keys DEV D Each pair of DEVs may optionally create their own secure connection DEV E

6. Security Services • Services offered • mutual authentication (mandatory) • key establishment • data encryption • data integrity/source authentication • Key authenticity verification (mandatory) • Optionally implemented for peer-to-peer security • Each cipher suite defines which services it offers

7. Protocols • Mutual authentication protocol includes challenge-response • Key distribution protocol • Key request protocol • Peer-to-peer protocols for authentication, key distribution and key request • Set peer cipher suite protocol • Set peer (public) key protocol • Request peer (public) key protocol

8. Information Elements • Most security information elements are variable length (defined by each cipher suite) • Common information elements listed • Information elements are formatted to be flexible within commands since they each include an element ID and length field

9. Commands • Simple command structure • Command operations defined within cipher suites, not in the standard • Command formats each include a variable list of information elements

10. Cipher Suite Specification • Document describes required content for candidate cipher suites • Requirements • object identifier • security services provided • formats for commands and information elements • actions required in order to implement protocols (including cryptographic operations) • security considerations

11. Evaluation Criteria • None included in this draft • These need to be determined by the working group and included in the call for cipher suite proposals

12. Contact Information Daniel BaileyProduct Manager for Wireless Networks NTRU dbailey@ntru.com Ari SingerPrincipal Engineer NTRU asinger@ntru.com