Key Hierarchy Merge Status Month Year doc.: IEEE 802.11-yy/xxxxr0 March 2005 Key Hierarchy Merge Status Date: 2005-03-14 Authors: Notice: This document has been prepared to assist IEEE 802.11. 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 grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <stuart.kerry@philips.com> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. Nancy Cam-Winget et al John Doe, Some Company

TAP and JIT Key Hierarchies Agenda March 2005 TAP and JIT Key Hierarchies Agenda Focus of analysis is to highlight areas of similarities and differences in the TAP and JIT Key Hierarchies Status of current progress Nancy Cam-Winget et al

Key Hierarchy goals TAP & JIT common goals March 2005 Key Hierarchy goals TAP & JIT common goals Obviate need to do full EAP authentication Enable different backend architectures for keying TAP only goals JIT only goals Obviate need for state cache Enable key hierarchy to be reused by others Enable STA to precompute all keys before critical path Enable STA to precompute all keys before any contact with target APs Nancy Cam-Winget et al

Similar Key Distribution Architecture March 2005 Similar Key Distribution Architecture TAP JIT Nancy Cam-Winget et al

TAP & JIT Similar Levels March 2005 TAP & JIT Similar Levels TAP Key Hierarchy JIT Key Hierarchy PMK D-PMK DA-PMK PTK RSK LSK PMK PTK Nancy Cam-Winget et al

Differing Key Constructions March 2005 Differing Key Constructions PMK (e.g. MSK) RSK (e.g. MSK) LCKn || LSKn = KDF-256(MSK, n || SID || LPSID || SupplicantID || “LSKey derivation” || 256) D-PMK = PRF-256(PMK, "D-PMK", SPA || KCID) DA-PMK = PRF-256(D-PMK, "DA-PMK", SPA || BSSID) PCKm || PMKm = KDF-256(LSK, m || SupplicantID || AuthenticatorID || “PMKey derivation”, 256) PTK PTK SPA = STA MAC Address KCID = Key Circle Identifier LPSID = Local Policy server Identifier Supplicant ID = EAP Identity Authenticator ID = NAS ID SID = Session ID as defined by EAP Nancy Cam-Winget et al

Current Status of Key Hierarchy Merge March 2005 Current Status of Key Hierarchy Merge Working towards a new merged key hierarchy: Provide two methods for generating keys to address: Minimal impact on current deployments and NIST requirements Except for the PTK, all keys remain constant for the lifetime of the session Nancy Cam-Winget et al