1. doc.: IEEE 802.11-05/0239r0 Submission March 2005 Montemurro, Smith, Edney, KumarSlide 1 Resource pre-allocation and commmunication adhoc report 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, 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 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at.http:// ieee802.org/guides/bylaws/sb-bylaws.pdfstuart.kerry@philips.compatcom@ieee.org Date: 2005-03-17 Authors:

2. doc.: IEEE 802.11-05/0239r0 Submission March 2005 Montemurro, Smith, Edney, KumarSlide 2 Abstract Provides an update on adhoc activities for resource pre-allocation Provides an update on activities for “over the air”/ “over the DS” communications

3. doc.: IEEE 802.11-05/0239r0 Submission March 2005 Montemurro, Smith, Edney, KumarSlide 3 Is Query Needed ? Yes, for three reasons : –helps in AP Selection – better than AAC in QBSS Load IE –may help in priming the pump for potential subsequent reservation –may help in capabilities you don’t know otherwise – HCCA, UPSD etc

4. doc.: IEEE 802.11-05/0239r0 Submission March 2005 Montemurro, Smith, Edney, KumarSlide 4 Query/Reservation through Action Frame Use of action frame for query and reservation request –Management frame are VI AC; doesn’t require any TS to be established Body of the action frame contains –some “dialog id” to maintain the context –IE list of resources as defined by RIC

5. doc.: IEEE 802.11-05/0239r0 Submission March 2005 Montemurro, Smith, Edney, KumarSlide 5 Security Action frame needs security protection –For current AP PTK available –For new AP issue how to secure ( and thus over the air reservation is TBD ). Consider waiting for TGw

6. doc.: IEEE 802.11-05/0239r0 Submission March 2005 Montemurro, Smith, Edney, KumarSlide 6 Over-the-air/Over-the-DS communications Both “over the air” and “over the DS” mechanisms should be available for communications. The AP will always support the “over the air” mechanism The AP will advertise whether it supports “over the DS” mechanism for communications “Over the Air” mechanisms could use the 802.11 Authentication Frame as transport.

7. doc.: IEEE 802.11-05/0239r0 Submission March 2005 Montemurro, Smith, Edney, KumarSlide 7 Mobility Domain Mobility domain defines the bounds for roaming for a STA. Guarantees reachability over the DS. Mobility domain and the Security domain are the same by default. Mobility domain could be advertised as a subset of the security domain. ESS Security Domain Mobility Domain

8. doc.: IEEE 802.11-05/0239r0 Submission March 2005 Montemurro, Smith, Edney, KumarSlide 8 Broker versus non-Broker AP Should a STA address its Query/Resv Request to the current AP or the target AP? In Broker Method, the STA addresses the current AP where as in Direct method the STA addresses the target AP; the current AP just bridges the frame to the target AP. Broker sends body of the frame ( RIC etc. ) to the target AP in a data frame.

9. doc.: IEEE 802.11-05/0239r0 Submission March 2005 Montemurro, Smith, Edney, KumarSlide 9 Broker vs Direct Use of broker enables implementation of policy management Different levels of policy management possible –simple counter –advanced context based policy Policy management not needed in all cases –But use of “Null broker” still needed for conversion from Action frame to data frame 3 levels of broker complexity are proposed (informative). These are transparent to the station

10. doc.: IEEE 802.11-05/0239r0 Submission March 2005 Montemurro, Smith, Edney, KumarSlide 10 Null broker option STA AP TargetAP Current Dest = AP Target STA direct negotiation No policy enforcement Simplest approach Converts Action frame to data frame

11. doc.: IEEE 802.11-05/0239r0 Submission March 2005 Montemurro, Smith, Edney, KumarSlide 11 Simple broker option STA AP TargetAP Current Dest = AP Current (AP Target in request) Broker is forwarder Basic policy enforcement (counter) Simple approach SME

12. doc.: IEEE 802.11-05/0239r0 Submission March 2005 Montemurro, Smith, Edney, KumarSlide 12 Query/Reservation to multiple APs Extend basic query/reservation mechanism such that STA can send request to multiple APs in one message STA can receive response as separate responses or ask AP to send a single, aggregated response Current AP could fan out request to multiple target APs and optionally collate the results before it responds to the STA

13. doc.: IEEE 802.11-05/0239r0 Submission March 2005 Montemurro, Smith, Edney, KumarSlide 13 Powerful broker option STA AP TargetAP Current Dest = AP Current (LIST of AP Targets in request) Broker is forwarder Smart policy enforcement (spoofing) flexible approach SMEAP Target

14. doc.: IEEE 802.11-05/0239r0 Submission March 2005 Montemurro, Smith, Edney, KumarSlide 14 Message Format Message format of Action frame is the same regardless of level of brokering the current AP implements Message format is the same regardless of over-the-air or over-the-wire option.