1. TGu Requirements Check
Month Year
doc.: IEEE yy/xxxxr0
November 2006
TGu Requirements Check
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
Necati Canpolat, Intel Corporation
John Doe, Some Company

2. Month Year
doc.: IEEE yy/xxxxr0
November 2006
Abstract
This document provides verification on TGu requirements coverage in the confirmed proposals and identifies the open issues.
Necati Canpolat, Intel Corporation
John Doe, Some Company

3. Overview TGu has primarily 5 groups of requirements namely:
Month Year
doc.: IEEE yy/xxxxr0
November 2006
Overview
TGu has primarily 5 groups of requirements namely:
Network Selection
MIH Support
Online Enrolment
Emergency Call Support
SSPN interfaces
Each one of the above requirement has also sub entries.
We have 5 confirmed proposals that overall cover the requirements however, some of the sub items have not been addressed.
The purpose of this review is to highlight the ones that we need to address and bring a closure to them
Necati Canpolat, Intel Corporation
John Doe, Some Company

4. Network Selection Cluster
Month Year
doc.: IEEE yy/xxxxr0
November 2006
Network Selection Cluster
Reference
Requirement
Requirement Class
R12N1
Define functionality by which a STA can determine whether its subscription to an SSPN would allow it to access a particular AN before actually joining a BSS within that AN. Proposals must describe their consideration of scalability.
Required
R12N2
The mechanism described in requirement R12N1 must allow a STA that has multiple credentials with an SSPN to select the correct credentials when authenticating with a Local Network.
R12N3
Define functionality to support authentication with multiple SSPNs through a single AP.
R12N4
Define functionality by which a STA can determine which interworking services are available before joining a BSS.
R12N5
Functionality shall be provided by which APs can advertise (before connection) the charges that will be made for use of the network if connection is authorized based on an SSPN subscription.
Not Required – Optional
R12N6
Functionality shall be provided by which during the connection process a STA can be informed of the actual charges to be applied to this session.
Not Required – Out of Scope
R12N7
It should be possible to inform a STA about unbroadcasted SSIDs without causing the STA to probe for each preferred SSID.
Not Required – Complete
R12N8
Define functionality by which the STA is able to determine what online enrolment (also called online subscription) methods are supported by the local network.
Optional
Addressed
NOT addressed
Optional/out of scope
Necati Canpolat, Intel Corporation
John Doe, Some Company

5. SSPN Interface Cluster
Month Year
doc.: IEEE yy/xxxxr0
November 2006
SSPN Interface Cluster
Reference
Requirement
Requirement Class
R12S1
Define the Authorization Information (originated from the SSPN) that shall be provided to the MAC and associated functionality.
Required
R12S2
Define how the information defined in R12S1 will be used.
R12S3
Define functionality by which the information defined in R12S1 can be modified (by the SSPN).
Not Required – Optional
R12S4
Make accessible accounting information for transfer to the SSPN. This shall include information about accepted TSPECs, their duration, and about actual traffic flows.
Not Required – Out of Scope
Necati Canpolat, Intel Corporation
John Doe, Some Company

6. MIH Support November 2006 Necati Canpolat, Intel Corporation Reference
Requirement
Requirement Class
R12H1
Provide a mechanism to support Media Independent Handoff capability.
Required
Necati Canpolat, Intel Corporation

7. Emergency Call Support
November 2006
Emergency Call Support
Reference
Requirement
Requirement Class
R12I1
Define IEEE TM functionality which would be required to support an Emergency Call (e.g. E911) service as part of an overall, multi-layer solution. Specifically: Capability Advertisement and Authentication issues
Required
R12I2
Define functionality by which Aps can provide information which will enable a STA to determine whether or not roaming to a candidate AP would require re-configuration (automatic or manual) of layer 3 networking.
Not Required – Out of Scope
Necati Canpolat, Intel Corporation

8. User Plane Cluster November 2006 Necati Canpolat, Intel Corporation
Reference
Requirement
Requirement Class
R12U1
Proposals shall allow a STA (subscription permitting) to access multiple Destination Networks at the same time.
Not Required – Optional
R12U2
Functionality shall be provided by which traffic destined for a particular Destination Network can be segregated from traffic destined for other Destination Networks.
Not Required – Out of Scope
R12U3
Provide mapping from external QoS information, e.g. DSCP, to specific parameters.
Required
Necati Canpolat, Intel Corporation

9. Month Year
doc.: IEEE yy/xxxxr0
November 2006
Conclusion
Overall all requirement clusters have been addressed by the confirmed proposals.
Only item R12N8 has not been addressed by any proposal.
TGu needs to finalize the decision on R12N8 requirement and move forward.
Note: TGu has discussed the above mentioned issue and decided to make this requirement optional. It will also ask to provide support for it since it aligns better with scope.
Necati Canpolat, Intel Corporation
John Doe, Some Company

10. Feedback? November 2006 Month Year doc.: IEEE 802.11-yy/xxxxr0
Necati Canpolat, Intel Corporation
John Doe, Some Company