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

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

3. July 2005
What’s the Point of TGu?
Interworking with external networks is possible
There are plenty of hot spots out there already…
We need to make things significantly better
Easier to use
Easier to configure
Significant extra functionality
Mike Moreton, STMicroelectronics

4. Assumed Architecture Wa Wn AS DSM DS AP Gateway July 2005
Mike Moreton, STMicroelectronics

5. July 2005
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.
Mike Moreton, STMicroelectronics

6. July 2005
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
Mike Moreton, STMicroelectronics

7. Frame Context Define a frame context:
July 2005
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
Mike Moreton, STMicroelectronics

8. How do we Manage and Maintain Frame Contexts?
July 2005
How do we Manage and Maintain Frame Contexts?
Between the STA and the AP (e.g. VLANs)
Or 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 that means that the AP has to change more.
Mike Moreton, STMicroelectronics

9. MAC Address Anonymity Does the network know the real MAC address?
July 2005
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
Mike Moreton, STMicroelectronics

10. July 2005
Summary
802.11u 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”
Mike Moreton, STMicroelectronics