Doc.: IEEE 802.11-05/0667r0 Submission July 2005 Mike Moreton, STMicroelectronicsSlide 1 Multiple Networks Notice: This document has been prepared to assist.

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0866r1 Submission September 2005 Michael Montemurro, Chantry NetworksSlide 1 Mobility Domain Definition and Description Notice: This.
Advertisements

Doc.: IEEE /90r0 Submission Nov., 2012 NICTSlide b NICT Proposal IEEE P Wireless RANs Date: Authors: Notice: This document.
Doc.: IEEE /0930r0 Submission July 2006 Nancy Cam-Winget, Cisco Slide 1 Editor Updates since Jacksonville Notice: This document has been prepared.
Doc.: IEEE /1867r1 Submission November r Security TeamSlide 1 TGr Security Requirements Notice: This document has been prepared to.
Doc.: IEEE /0094r0 Submission November 2009 Steve Shellhammer, QualcommSlide 1 Comments on PAR Notice: This document has been prepared.
Doc.: IEEE /1138r1 Submission November 2005 Cheng Hong, PanasonicSlide 1 Authorization Information in interworking Notice: This document has been.
Doc.: IEEE /1138r0 Submission November 2005 Cheng Hong, PanasonicSlide 1 Authorization Information in interworking Notice: This document has been.
Doc.: IEEE /2237r0 Submission July 2007 Emily Qi, Intel CorporationSlide 1 TGv Redline D1.0 Insert and Deletion Notice: This document has been.
Doc.: IEEE /1212r0 Submission TGT and MEF Liaison Notice: This document has been prepared to assist IEEE It is offered as a basis for.
Doc.: IEEE /86r2 Submission March, 2010 Gabor BajkoSlide 1 Location Proxy Notice: This document has been prepared to assist IEEE It is.
Doc.: IEEE /0028r0 Submission January 2005 Eleanor Hepworth, Siemens Roke ManorSlide 1 Definitions and Terminology Notice: This document has been.
Doc.: IEEE /0460r1 Submission March 2006 Fujio Watanabe, DoCoMo USA LabsSlide 1 Japanese Emergency Call Regulation Notice: This document has been.
Doc.: IEEE /0136r0 Submission January 2007 Dave Stephenson, Cisco Systems, Inc.Slide 1 Input to Information Model Date: Notice:
Doc.: IEEE /0652r1 Submission May 2007 Emily Qi, Intel CorporationSlide 1 TGv Redline D0.12 Insert and Deletion Notice: This document has been.
Service Access Contexts
[ Interim Meetings 2006] Date: Authors: July 2005
Service Access Contexts
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
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]
[ Policies and Procedure Summary]
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]
(Presentation name) For (Name of group) (Presenter’s name,title)
TGp Closing Report Date: Authors: March 2006 Month Year
On Coexistence Mechanisms
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
Proposed Changes to Requirements
On Coexistence Mechanisms
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
ADS Study Group Mid-week Report
IEEE P Wireless RANs Date:
Authentication Cluster
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
Authentication Cluster
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]
TGu Motions Date: Authors: May 2006 May 2006
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
EC Motions – July 2005 Plenary
TGu-changes-from-d0-04-to-d0-05
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
Multiple Networks Date: Authors: July 2005 July 2005
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGr Proposed Draft Revision Notice
Presentation transcript:

doc.: IEEE /0667r0 Submission July 2005 Mike Moreton, STMicroelectronicsSlide 1 Multiple Networks 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, 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. Date: Authors:

doc.: IEEE /0667r0 Submission July 2005 Mike Moreton, STMicroelectronicsSlide 2 Abstract This submission describes some issues relating to the handling of multiple destination networks within 11u.

doc.: IEEE /0667r0 Submission July 2005 Mike Moreton, STMicroelectronicsSlide 3 Assumed Architecture DSM AP Gateway DS AS Wn Wa

doc.: IEEE /0667r0 Submission July 2005 Mike Moreton, STMicroelectronicsSlide 4 Multiple Networks Imagine a local network run by one company, and an SSPN run by another. –Access to the Local Network is provided based on the relationship between the SSPN and the STA, and the SSPN and the Local Network. Does traffic go directly to the Internet, or does it go via the network of the SSPN? –The answer is both! –Some services may only be accessible via the SSPN, but that doesn’t mean all data has to go via the SSPN.

doc.: IEEE /0667r0 Submission July 2005 Mike Moreton, STMicroelectronicsSlide 5 Multiple SSPNs Why shouldn’t a STA be able to simultaneously access the football results service of one operator, and the travel service of a different one? –Allows the model of virtual service providers to reach its logical extreme –The equivalent of GPRS’s PDP context? PDP context provides scope of IP addresses

doc.: IEEE /0667r0 Submission July 2005 Mike Moreton, STMicroelectronicsSlide 6 Frame Context Define a frame context: –A frame context is initiated by a STA, and authorised by a single SSPN. –Frames from one context are isolated from frames in other frame contexts. –A frame context provides direct access to the services in a single destination network –It’s possible for a single SSPN subscription to authorise access to multiple frame contexts One or more SSPN based services Direct Internet access via the Local Network

doc.: IEEE /0667r0 Submission July 2005 Mike Moreton, STMicroelectronicsSlide 7 How do we Manage and Maintain Frame Contexts? Between the STA and the AP (e.g. VLANs) By tunnels to/through the Gateway - The key question is how much we want to involve the AP in: –Policy enforcement –Traffic segmentation VLANs mean that the AP can do much more, but also that the AP has to change more.

doc.: IEEE /0667r0 Submission July 2005 Mike Moreton, STMicroelectronicsSlide 8 MAC Address Anonymity Does the network know the real MAC address? –Does the Gateway know? –Does the AP know? If the AP knows, then it’s just an local issue –Maybe add something to 4 way handshake to indicate real MAC address If the AP doesn’t know, then Frame Contexts can be implemented by MAC Anonymity –STA just associates multiple times with different addresses. If the AP doesn’t know then temporary address should be allocated by Gateway, and VLANs should be used. –But, remember gateway could be integrated with AP in a real device

doc.: IEEE /0667r0 Submission July 2005 Mike Moreton, STMicroelectronicsSlide 9 Summary u needs to provide a mechanism by which a STA can be a member of multiple networks at once Access to each logical network is authorised by an SSPN. Call this concept a “frame context”