PSK Treatment Options Date: 19 September 2005 Authors: September 2005

Slides:



Advertisements
Similar presentations
Use of KCK for TGr Management Frame Protection
Advertisements

LB84 General AdHoc Group Sept. Closing TGn Motions
LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
London TGu Motions Authors: January 2007 Date: Month Year
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
March 2014 Election Results
TGp Closing Report Date: Authors: July 2005 Month Year
TGp Closing Report Date: Authors: July 2007 Month Year
TGr Security Architecture
Attendance and Documentation for the March 2007 Plenary
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
[ Policies and Procedure Summary]
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
3GPP liaison report July 2006
[place presentation subject title text here]
Fast Transition Mobility (FTM) Domain
JTC1 Chair’s Closing Report
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
Contribution on Location Privacy
JTC1 Ad Hoc Mid-week Report
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
Experimental DTV Sensor
TGu Closing Report Date: Authors: September 2005
ADS Study Group Mid-week Report
Attendance for July 2006 Date: Authors: July 2006
Selection Procedure Recommendation
IEEE P Wireless RANs Date:
TGw Selection Process Date: 19 July 2005 Authors: July 2005 Month Year
Attendance for November 2006
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
TGp Closing Report Date: Authors: March 2007 Month Year
Attendance for July 2006 Date: Authors: July 2006
TGr Proposed Draft Revision Notice
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
Beamforming and Link Adaptation Motions
Draft P802.11s D1.03 WordConversion
Questions to the Contention-based Protocol (CBP) Study Group
Motion to go to Letter Ballot
TGu-changes-from-d0-04-to-d0-05
2-Level Key Hierarchy Date: 19 July 2005 Authors: July 2005 Month Year
Transition Nowhere Date: Authors: Sept 2005 Sept 2005
TGw Selection Process Date: 19 July 2005 Authors: July 2005 Month Year
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
11k Public Awareness Program
Attendance for November 2006
PSMP Adhoc Oct TGn Adhoc
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Use of KCK for TGr Management Frame Protection
Use of KCK for TGr Management Frame Protection
Use of Nonces in Fast Transitioning Flows
TGr Proposed Draft Revision Notice
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

PSK Treatment Options Date: 19 September 2005 Authors: September 2005 Month Year doc.: IEEE 802.11-yy/xxxxr0 September 2005 PSK Treatment Options Date: 19 September 2005 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>. K. Sood, N Cam-Winget John Doe, Some Company

Goals and Motivation Define use of Pre-Shared Keys in TGr Month Year doc.: IEEE 802.11-yy/xxxxr0 September 2005 Goals and Motivation Define use of Pre-Shared Keys in TGr Email thread on Issue #8 on PSK treatment options Multiple options are being listed here for discussion, followed by adoption. K. Sood, N Cam-Winget John Doe, Some Company

Option 1: Use 2-Level Key Hierarchy September 2005 Option 1: Use 2-Level Key Hierarchy Basic Methodology: Substitute PSK for MSK in the key derivation steps Pros Key derivation remains unchanged Independent of AKM Fast transition advertisements and capabilities symmetric to 802.1X based mechanisms. Cons Extra computations with no crypto benefits Steps needed to make it work Include an 802.1X key management component for using the R0KH-ID as the PSK “group”. Each R0KH has its own “PSK” K. Sood, N Cam-Winget

Option 2: Use PSK as PMK-R1 September 2005 Option 2: Use PSK as PMK-R1 Basic Methodology: Substitute PSK for PMK-R1 keys. PMK-R0 not needed. Pros A single layered key hierarchy No extra compute cycles necessary Cons Key hierarchy is dependent on the AKM Steps needed to make it work Implementations must use appropriate key derivation mechanism Implementations must change advertisements dependent on AKM. K. Sood, N Cam-Winget

Proposed Recommendation September 2005 Proposed Recommendation Adopt Option 1 for simplicity and symmetry Straw-Poll: “Interest in pursuing Option #1 as a recommended option for treating pre-shared keys” Quote: [A Security Architect] While I don’t like PSK...I like this proposal!!  K. Sood, N Cam-Winget