1. TGr Security Architecture
Month Year
doc.: IEEE yy/xxxxr0
May 2006
TGr Security Architecture
Date:
Authors:
Notice: This document has been prepared to assist IEEE 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
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < 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 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 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
Sood, Walker, Cam-Winget, Calhoun
John Doe, Some Company

2. Month Year
doc.: IEEE yy/xxxxr0
May 2006
TGr Security Design
Instrument this design in context of state machines and in relation to 802.1X
Sood, Walker, Cam-Winget, Calhoun
John Doe, Some Company

3. TGr Security Architecture
Month Year
doc.: IEEE yy/xxxxr0
May 2006
TGr Security Architecture
Sood, Walker, Cam-Winget, Calhoun
John Doe, Some Company

4. TGr Key Hierarchy 4 keys: KEK, KCK-11, KCK-1X, TK
Month Year
doc.: IEEE yy/xxxxr0
May 2006
TGr Key Hierarchy
4 keys: KEK, KCK-11, KCK-1X, TK
KEK and KCK-11 are consumed by SME: .11 driver used to wrap KDEs and MIC 11r frames
KCK-1X is consumed by .1X used to MIC .1X frames
KCK-1X authenticates GTK updates and TKIP countermeasures
Sood, Walker, Cam-Winget, Calhoun
John Doe, Some Company

5. TGr Initial Association
Month Year
doc.: IEEE yy/xxxxr0
May 2006
TGr Initial Association
Sood, Walker, Cam-Winget, Calhoun
John Doe, Some Company

6. TGr FT Reassociation May 2006 Month Year doc.: IEEE 802.11-yy/xxxxr0
Sood, Walker, Cam-Winget, Calhoun
John Doe, Some Company

7. FT Reassociation No EAPoL Key in any 11r messages
May 2006
FT Reassociation
No EAPoL Key in any 11r messages
Plumbing PTK: TK, KEK-11 and KCK-11 are plumbed in SME, KCK-1X is plumbed in 802.1X
Doing wrapping in SME allows for better centralization of crypto function
Sood, Walker, Cam-Winget, Calhoun

8. GTK Updates Message format and flow remains the same
May 2006
GTK Updates
Message format and flow remains the same
802.1X requests SME to wrap KDEs, and originates the GTK update messages
Supplicant asks SME to unwrap and plumb GTK
Sood, Walker, Cam-Winget, Calhoun