Uniform 802.11e Admissions Control Signaling for HCF and EDCF doc.: IEEE 802.11-02/678r0 January 2003 Uniform 802.11e Admissions Control Signaling for HCF and EDCF Bob Meier, Liwen Wu, Mark Bilstad Cisco Systems January 15, 2003 bilstad@cisco.com Mark Bilstad, Cisco Systems Bob Meier, Cisco Systems

Considerations/Issues doc.: IEEE 802.11-02/678r0 January 2003 Considerations/Issues There is a recognized need for Explicit Admissions Control Signaling, independent of the access method Explicit EDCF Admissions Control enables infrastructure policy and policing For example, it may be desirable to limit QoS bandwidth for “guest” users in an enterprise network. Mark Bilstad, Cisco Systems Bob Meier, Cisco Systems

Considerations/Issues January 2003 Considerations/Issues The current TSPEC Status Codes are insufficient. A QSTA cannot determine if a TSPEC is rejected because 1) resources are not available, or 2) HCF Polling is not enabled for the traffic type. Admission schemes can co-exist, but explicit admissions control is not useful if all of its resources can be consumed by distributed admissions control Per the current draft, the HC can reserve resources for explicit admissions control by advertising reduced TXOPBudgets in the QoS Parameters IE Mark Bilstad, Cisco Systems

Summary of proposed changes January 2003 Summary of proposed changes TSPEC Add Access Method bits to TSinfo field of TSPEC IE Add new TSPEC status code Delete text that prohibits EDCF access for stations with admitted TSPECs Mark Bilstad, Cisco Systems

Allocate 2 bits in the TSPEC TSInfo Field in Figure 42.8 January 2003 Allocate 2 bits in the TSPEC TSInfo Field in Figure 42.8 B13 B14 Polled access Contention-based access 1 QSTA indicates its capabilities in the ADDTS request HC responds with what will be used in the ADDTS response Mark Bilstad, Cisco Systems

January 2003 Add text to section 7.3.2.15 A QSTA sets the TSInfo access fields in an ADDTS request to indicate to the HC the access methods that it will accept for the traffic stream and to indicate its access method capabilities. The fields are set in an ADDTS Request as follows: The Polled Access field is set to 1 if the QSTA will accept access via HCF polling. The Contention-based Access field is set to 1 if the QSTA will accept EDCF as the access method. An HC uses the TSInfo access fields in an ADDTS Response to establish the access method used for the traffic stream for an accepted TSPEC. The HC cannot establish an access method where the QSTA has indicated that it will NOT accept the access method. The HC sets exactly one of these bits to 1 to indicate which type of access has been accepted for the request. Mark Bilstad, Cisco Systems

Remove restrictions in text January 2003 Remove restrictions in text Delete the following paragraph in 9.10.2.3: “HCF contention-based channel access shall not be used to transmit MSDUs belonging to traffic streams for which the traffic specification as furnished to/by the HC has a specified minimum data rate and a specified delay bound, except as may be necessary to obtain the first polled TXOP from the HC for a newly added or modified traffic stream.” Mark Bilstad, Cisco Systems

New TSPEC Status Code Status Code Result Code Definition doc.: IEEE 802.11-02/678r0 January 2003 New TSPEC Status Code Table 20.5 – Status Codes Status Code Result Code Definition 5 NOT_ENABLED The TS has not been created because the requested access method is not enabled for the traffic type. 6-255 reserved Mark Bilstad, Cisco Systems Bob Meier, Cisco Systems

January 2003 Straw Poll Do you support the use of TSPECs to admit flows of either access method? Do you support the specific changes in this proposal (678r2)? Mark Bilstad, Cisco Systems