IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-09-00xx-00-sec Title: IEEE 802.11r Fast BSS Transition – A Study Date Submitted: September 21, 2009 Present.

Slides:



Advertisements
Similar presentations
sec1 IEEE MEDIA INDEPENDENT HANDOVER DCN: sec Title: Security SG Opening Notes Date Submitted: May 13, 2008 Presented.
Advertisements

IEEE MEDIA INDEPENDENT HANDOVER DCN: sec Title: Security TG Closing Note Date Submitted: January 22, 2009 Presented at IEEE
IEEE MEDIA INDEPENDENT HANDOVER DCN: hwnm Title: HWN Mgmt. SG Closing Report Date Submitted: July 15, 2010 Presented at IEEE
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec Title: The Role of a Media Independent Authenticator Date Submitted: December 30, 2009.
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec Title: Initiate An Exercise for Generating a 21a Document Date Submitted: September 21, 2009.
DAIDALOS /11 IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: DVB-H Motion Date Submitted: March, 2008 Presented.
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Your Title Here Date Submitted: Month, NN, 200x Presented at IEEE.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MEDIA INDEPENDENT HANDOVER – Heterogeneous-RAT Mobility within.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Report on Potential Link Sync Events for IEEE r Date Submitted:
Doc.: IEEE /xxxxr0 Submission March 2007 Srinivas Sreemanthula Slide 1 IEEE MEDIA INDEPENDENT HANDOVER DCN: SSID-info-MIH-IS.ppt.
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Security SG Notes Date Submitted: September, 19, 2007 Presented at IEEE
xxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx Title: Proposal for adding a key hierarchy based approach in the security.
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec Title: Q & A for Discussion Date Submitted: Aug 17, 2010 Presented at IEEE a Teleconference.
es IEEE MEDIA INDEPENDENT HANDOVER DCN: es Title: Response to ES PAR and 5C Comments Date Submitted: March.
IEEE DCN: Title: TG Opening Note Date Submitted: November 11, 2013 IEEE session #59 in Dallas, TX, USA Authors or Source(s):
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: SB Recirculation-2 Summary Date Submitted: January 2008 Presented.
21-08-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: XXXX Title: MIH_MN_HO_Commit Revisited Date Submitted: March, 2008 Presented.
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: More Discussion on “MGW vs. MIH-PoS” in IEEE c Date Submitted: Sept. 19 th,
support_for_comment_res1 IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Length Encoding Example Date Submitted:
ES-CS-Adhoc-Rep.ppt IEEE MEDIA INDEPENDENT HANDOVER DCN: ES-CS-Adhoc-Rep.ppt Title: ES/CS Ad-hoc Discussions.
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec Title: Key Hierarchy Discussion Date Submitted: January 5, 2009 Present at a Future IEEE.
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: sec Title: Message Flow Date Submitted: March 1, 2011 Authors or Source(s): Fernando Bernal-Hidalgo,
IEEE MEDIA INDEPENDENT HANDOVER DCN: 100 Title: Cross Domain Trigger and Handover Talking Points Date Submitted: July 13, 2004.
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-0sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Your Title Here
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
Presentation transcript:

IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec Title: IEEE r Fast BSS Transition – A Study Date Submitted: September 21, 2009 Present at IEEE meeting in September of 2009 Authors: Lily Chen (NIST) Abstract: This document reviews IEEE r solution in Fast BSS Transition. The purpose is to pursue a proper approach in accommodating different authentication options in media independent handover xx-00-sec

2 IEEE presentation release statements This document has been prepared to assist the IEEE Working Group. 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. 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 IEEEs name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEEs 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 The contributor is familiar with IEEE patent policy, as stated in Section 6 of the IEEE-SA Standards Board bylaws and in Understanding Patent Issues During IEEE Standards Development Section 6 of the IEEE-SA Standards Board bylawshttp://standards.ieee.org/guides/bylaws/sect6-7.html#6http://standards.ieee.org/board/pat/faq.pdf

IEEE Network MAC PHY IEEE Not

Fast BSS Transition xx-00-sec4 Network (not ) Transition

IEEE Way Handshake STA-PMKAP-PMK EAPOL-Key (..., …, ANonce) EAPOL-Key (..., …, SNonce, STA RSN IE, MIC) EAPOL-Key (..., …, ANonce, AP RSN IE, MIC) Generate ANonce Generate SNonce Drive PTK EAPOL-Key (..., …, MIC) Install TK Peer EAP ServerAuthenticator MSK EAP (Full Auth, Pre-Auth, or Re-Auth) IEEE NOT IEEE

IEEE r Key Hierarchy It introduces two level of PMKs PMK-R0 derived from MSK (or PSK) PMK-R1s derived from PMK-R0.

IEEE r – Fast BSS Transition STA Current AP- PMK_R1 A Target AP-PMK_R1 B Secure session and data Auth Req (FT … FIIE(SNonce …)) Auth Res (FT … FIIE(SNonce, ANonce …)) PTK B Generated Re-association Req (….) Re-association Res (….) (New) Secure session and data

IEEE r Key Distribution The R0KH and the R1KH are assumed to have a secure channel between them that can be used to exchange cryptographic keys without exposure to any intermediate parties. The cryptographic strength of the secure channel between the R0KH and R1KH is assumed to be greater than or equal to the cryptographic strength of the channels for which the keys will be used. This standard assumes that the key transfer includes the PMK-R1, the PMK-R1 PMKSA, the PMK-R1 context, and the associated key authorizations. The protocol for distribution of keying material from the R0KH to the R1KH is outside the scope of this standard. - IEEE r, Clause 11A.2.2

What do we learn? Key distribution is not a part of IEEE r. A specific EAP method is not a part of IEEE It is independent to whether it is a Pre-authentication; Re-authentication; or Full-authentication.

What we should ask? Do we have to introduce specific EAP methods in IEEE a? Shall MIHF or any IEEE entities handle specific authentication? If it is in EAP layer or above, then we will need to add function of a peer, an authenticator, or a server to 21 the 21 entity. If it is a low layer, then it cannot be media independent.

Things to clarify In contribution 144, Alternative I: Work with and to introduce pre-authentication architecture. Pre-authentication is out of the scope of This alternative obviously does not apply (For , further study is needed.)