doc.: IEEE /0136r0 Submission January 2007 Dave Stephenson, Cisco Systems, Inc.Slide 1 Input to Information Model Date: 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. Authors:

doc.: IEEE /0136r0 Submission January 2007 Dave Stephenson, Cisco Systems, Inc.Slide 2 Level of Abstraction It is desirable to abstract the information model to the network level –Smaller database, easier to synchronize with WLAN infrastructure configuration –Smaller amount of data to deliver to STAs Abstraction dependent on having consistent configuration of all APs in a wireless network This presentation provides definition of terms and conditions to provide this consistency

doc.: IEEE /0136r0 Submission January 2007 Dave Stephenson, Cisco Systems, Inc.Slide 3 Concepts and Definitions An wireless network is identified by the following duple: WNID = {HESSID, SSID} The information model provides the binding between SSPN and WNID –This information is not provided by access network –STA queries IS to learn WNID with which to associate in order to obtain service from a given SSPN HESS (homogeneous extended service set) defines the physical infrastructure having a common configuration and common DS connectivity SSID defines a logical network operating on the physical infrastructure; there may be multiple SSIDs configured on a single HESS

doc.: IEEE /0136r0 Submission January 2007 Dave Stephenson, Cisco Systems, Inc.Slide 4 Concepts and Definitions (cont.) HESSID: HESS identifier. Identifier for a set of APs wherein: –Each AP provides identical DS connectivity to one or more VLANs, and –Each AP provides an identical set of corresponding SSIDs, and –Any specific SSID’s configuration is identical, and –All APs are members of the same mobility domain, if one is present.

doc.: IEEE /0136r0 Submission January 2007 Dave Stephenson, Cisco Systems, Inc.Slide 5 Concepts and Definitions (cont.) HESSID notes: –Abstraction assumes that there is a one-to-one correspondence between VLAN and connectivity to a particular SSPN access network is not aware of this binding. It just bridges frames from a specific SSID to the corresponding VLAN. –The “SSID configuration” is meant to include the services supported –Different subscribers on the same SSID may have different services (or levels of service) due to AAA permissions

doc.: IEEE /0136r0 Submission January 2007 Dave Stephenson, Cisco Systems, Inc.Slide 6 Other issues: How is location abstracted to the network level? –Geospatial coordinates for APs is easy to understand –Radio coverage of network can be difficult to describe –Possible topic for Ad Hoc meeting?