What is u? Date: Authors: January 2006 January 2006

Slides:



Advertisements
Similar presentations
Emergency Call Support
Advertisements

LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
Motions Date: Authors: January 2006
TGu/TGv Joint Session Date: Authors: July 2005 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
TGu Closing Report Date: Authors: November 2005
March 2014 Election Results
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
3GPP Extended Date: Authors: July 2005 July 2005
[ Policies and Procedure Summary]
TGu Pre-Proposal Presentations
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
Protected SSIDs Date: Authors: March 2005 March 2005
3GPP liaison report July 2006
[place presentation subject title text here]
Motions Date: Authors: January 2006
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
Emergency Call Motion Date: Authors: January 2006
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
TGu Pre-Proposal Presentations
TGu Pre-Proposal Presentations
Proposed Changes to Requirements
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
TGu Closing Report Date: Authors: September 2005
Solution for comment 32 Date: Authors: July, 2008
ADS Study Group Mid-week Report
TGu Timeline Date: Authors: July 2005 July 2005
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
What is u? Date: Authors: January 2006 January 2006
Secure Network Selection
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
Proposed Changes to Requirements
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
Document Motions Date: Authors: November 2005 November 2005
Proposed Changes to Requirements
TGr Proposed Draft Revision Notice
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
3GPP2 Liaison Report Date: Authors: May 2006 May 2006
May 2005 CAPWAP AHC Closing Report
Liaison Report From Date: Authors: Month Year
TGu Closing Report Date: Authors: January 2006 January 2006
Draft P802.11s D1.03 WordConversion
Questions to the Contention-based Protocol (CBP) Study Group
TGu-changes-from-d0-04-to-d0-05
Transition Nowhere Date: Authors: Sept 2005 Sept 2005
TGu-changes-from-d0-03-to-d0-04
TGu Timeline Date: Authors: January 2005 January 2005
TGu Motions Date: Authors: May 2006 May 2006
Multiple Networks Date: Authors: July 2005 July 2005
TGu Timeline Date: Authors: May 2005 May 2005
Shared Infrastructure
TGu Timeline Date: Authors: July 2005 July 2005
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGu Timeline Date: Authors: July 2005 July 2005
TGr Proposed Draft Revision Notice
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

What is 802.11u? Date: 2006-01-06 Authors: January 2006 January 2006 doc.: IEEE 802.11-06/0013r0 January 2006 What is 802.11u? Date: 2006-01-06 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>. Mike Moreton, STMicroelectronics Mike Moreton, STMicroelectronics

January 2006 doc.: IEEE 802.11-06/0013r0 January 2006 Abstract This document gives a brief personal overview of the aims of 802.11u. As we’re still at the call for proposals stage, at this point we can’t be explicit about how these aims will be achieved. Mike Moreton, STMicroelectronics Mike Moreton, STMicroelectronics

January 2006 doc.: IEEE 802.11-06/0013r0 January 2006 802.11u in a Nutshell IEEE 802.11 currently assumes that you are pre-authorised to use the IEEE 802.11 network When you come to connect, you already have all the security credentials you need (if any) IEEE 802.11u considers the case when you don’t You could enrol with the network (e.g. Wi-Fi’s UAM) You could use the network to get access to one that you do have credentials for Hot spot roaming Enterprise Virtual Networks You could find a network that is advertising it will give you the service you need without credentials “Free” services Emergency call (E911) support Local information services that don’t provide general Internet access Mike Moreton, STMicroelectronics Mike Moreton, STMicroelectronics

January 2006 doc.: IEEE 802.11-06/0013r0 January 2006 A User Perspective You turn on your laptop in your hotel room, and it detects 15 different SSIDs that you’ve never heard of: tsunami, Loadsadrone, linksys, OhNo, CoffeeToGo, SouthernKnocker, Uneec, Eighty4Tea, HighRateHotels , AlmostGroped, AlmostGroped2, RealAlmostGroped, GenuineAlmostGropedDontTrustTheOthersBecauseTheyreHackers What do you do? With 802.11u you’ll know which networks provide free service, which networks you can use based on your home subscriptions which networks you could enrol with which networks don’t provide any public service (so you can’t use them) Mike Moreton, STMicroelectronics Mike Moreton, STMicroelectronics

January 2006 doc.: IEEE 802.11-06/0013r0 January 2006 IEEE 802.11u – Why Bother? Question: Hotspots exist, roaming agreements exist, so why do we need TGu? Some existing solutions assume no MAC layer changes But can be klunky, inefficient and unscalable as a result Some existing solutions assume proprietary MAC extensions E.g. multiple SSIDs in a Beacon or Probe Response But these are non-standard, and hence risky and often will not scale to larger networks. Some existing solutions use layer 3 and above (i.e. IP family) techniques to overcome problems Assume trusted relationship between AP and network Problems with scalability and inefficiency No layer 2 fast roaming (TGr) TGu exists to “do it right” Stop hacking, and fix the problems properly Do the bits that have to be done at L2, and leave the rest to others Mike Moreton, STMicroelectronics Mike Moreton, STMicroelectronics