11-11-0377-01-00ae-lb172-clause-10-2-comment-resolutions

March 2011 doc.: IEEE 802.11-11/0377r1

IEEE P802.11

Wireless LANs

Overview

This document updates TGae 2.0 Clause 10.2 to resolved comments received from LB 172. Submission page 1

March 2011 doc.: IEEE 802.11-11/0377r1

REV HISTORY:

R0 – initial revision

Submission page 2

March 2011 doc.: IEEE 802.11-11/0377r1 On receipt of this primitive, the SME evaluates the result code.

Modify the changes to this sub-clause as follows:

8.4.2.ae1 Management Frame QoS Policy element(11n)

The Management Frame QoS Policy element defines access categories of management frames and is used to advertise and exchange management frame QoS policy between STAs. The use of the Mangament Frame QoS Policy element is given in clause 10.ae1. See Figure 8-4ae1 (Management Frame QoS Policy element format).

Figure 8-4ae1—Management Frame QoS Policy element format

The Element ID field is equal to the Management Frame QoS Policy value in Table 8-50.

The value of the length field is between 1 and 255.

The MFQ Policy Information field indicates properties of the MFQ policy. See Figure 8-4ae1a

Figure 8-4ae1a — MFQ Policy Information Field format

The MFQ Policy Identifier field identifies the policy advertised by the AP. The MFQ Policy Type field identifies whether the MFQ Policy is partial or complete.

The Access Category Assignment Count field indicates the number of Access Category Assignment field(s) included in this information element.

Submission page 3

March 2011 doc.: IEEE 802.11-11/0377r1 The List of Access Category Assignment fields contains zero or more Access Category Assignment fields.(11n)

The Access Category Assignment field specifies a group of management frames and their associated access categories. See Figure 8-4ae2 (Access Category Assignment Field format).

Figure 8-4ae2—Access Category Assignment Field format

The format of the AC Assignment Header subfield of the Access Category Assignment field is defined in Figure 8-4ae3 (AC Assignment Header subfield).

Figure 8-4ae3 – AC Assignment Header subfield

The Access Category Assignment Field Type subfield is 2 bits in length and defines the structure of the Access Category Assignment field. It is set to 0. Values 1, 2, and 3 are reserved.

The Access Category Assignment Field Length subfield is 6 bits in length and defines the length in octets of the Access Category Assignment field excluding the AC Assignment Header subfield. Modify these sub-clauses as follows:

10.ae1.2 Management frame QoS policy advertisement and configuration procedures

Management frame QoS policies are exchanged and implemented between two MFQ STAs. The ACI classification by transmitting STA for every MFQ frame is governed by the MFQ policy Submission page 4

March 2011 doc.: IEEE 802.11-11/0377r1 obtained from the receiving STA. The MFQ policy is either advertised by the receiving STA or obtained through the exchange of an MFQ Policy frame or MFQ Policy Change frame.MFQ Policy is communicated through the MFQ Policy element as described in 8.4.2.ae1. A STA shall not transmit an MFQ Policy element that sets I=0 and G=0 in any of the included QACM subfields.

A QMF STA shall use the default QMF policy if it has not received a QoS Policy frame from a peer QMF STA. A MFQ STA shall always apply the MFQ policy received in a MFQ Policy frame.

The MFQ Policy that the MLME uses following an MLME-START.request or MLME-

JOIN.request shall be the default MFQ policy, until overridden by an explicit MLME-MFQPOLICYSET.request. (See 6.3.ae1.6).

The ACI classification for any management frame can be reconfigured, for example, vendor-specific and vendor-specific protected management frames may be reconfigured to suit the vendor application requirements.

There are two types of transmitted MFQ policy: the complete MFQ policy or the partial MFQ policy. Complete MFQ policy includes a transmission access category for each management frame that is not transmitted using the default MFQ policy access category defined in Table 10-ae1. Partial MFQ policy includes a transmission access category for State 1 and State 2 management frames that are not transmitted using the default MFQ access categories defined in Table 10-ae1.

STAs may indicate either a partial MFQ or a complete MFQ policy in Beacon frames to advertise the MFQ policy. STAs shall not indicate partial MFQ policy in a management frame that contains the MFQ Policy element and is not a Beacon frame.

The MFQ Policy Type sub-field indicates whether the MFQ Policy is complete or partial. When the MFQ Polcy Type sub-field in the MFQ Policy Information field is set to 0, the MFQ Policy Element defines a complete MFQ policy. When the MFQ Policy Type sub-field in the MFQ Policy Information field is set to 1, the non-AP STA shall interpret the MFQ Policy Element as the partial MFQ policy.

10.ae1.2.1 Management frame QoS policy communication in a BSS, IBSS or MBSS

The MFQ Policy frame is sent by an MFQ STA to configure a MFQ policy at the peer MFQ STA in a BSS, IBSS, or MBSS..The MFQ Policy Change frame is sent by an MFQ STA to request a change to its MFQ Policy for the peer MFQ STA in a BSS, IBSS, or MBSS.

A non-AP QMF STA operating in a BSS shall not transmit an MFQ Policy frame to an AP. A STA may send an MFQ Policy Change frame to request a change in MFQ Policy at a peer STA.

A non-AP STA that receives a MFQ Policy Change frame may either accept or reject the request. The AP shall respond to an MFQ Policy Change frame with an MFQ Policy frame. If the Reconfiguration field is set to 0 in the extended capabilities element in the beacon frame, the AP that receives a MFQ Policy Change frame shall shall respond with an MFQ Policy frame, with the current MFQ Policy element and StatusCode set to 37 (“The request has been declined”). If the Reconfiguration field is set to 1 in the extended capabilities element in the beacon frame, the AP that receives a MFQ Policy Change frame shall evaluate the MFQ Policy included in the frame, and shall respond to the request with the resulting MFQ Policy element and StatusCode Submission page 5

March 2011 doc.: IEEE 802.11-11/0377r1 set to 0 (“success) if it accepts the policy change, or 37 (“The request has been declined”) if it rejects the policy change.

If an accept status is received in the MFQ Policy frame within dot11MFQPolicyChangeTimeout, then both MFQ STAs shall transmit management frames to each other in accordance with the changes to the MFQ policy that were indicated in the MFQ Policy frame.

If a reject status is received, then the configuration change request is rejected and both STAs continue to transmit frames according to the previously configured MFQ policy. The requesting STA shall not retry the same configuration change request within

dot11MFQPolicyChangeTimeout from the time the requesting STA receives the rejection frame.

If the requesting STA does not receive a MFQ Policy frame in response to a MFQ Policy Change frame in dot11MFQPolicyChangeTimeout, then the requesting STA shall continue to transmit frames according to the previously configured MFQ policy.

If an MFQ STA has received an Extended Capabilities element with MFQReconfiguration subfield equal to 0 or has not received an Extended Capabilities element from a destination MFQ STA, the MFQ STA shall not transmit an MFQ Policy Config Request frame to the destination MFQ STA.

An MFQ AP may send an MFQ Policy Config Request frame to an associated MFQ STA. The associated MFQ STA may send an MFQ Policy Config Request to the MFQ AP in its BSS only if the most recently received Extended Capabilities element from the AP has its MFQReconfiguration subfield set to 1. The AP may accept or reject this request. If the AP rejects the request, the associated MFQ STA shall not request the same policy reconfiguration from the AP within the lifetime of its association.

An MFQ AP, an MFQ STA in an MBSS, or an MFQ STA in an IBSS may set

dot11MFQReconfigurationActivated to true or false. A non-AP MFQ STA in an infrastructure BSS shall set dot11MFQReconfigurationActivated to true and shall set the MFQReconfiguation subfield to 1 in transmitted (re)association requests. An MFQ non-AP STA with

dot11ReconfiguationActivated true shall accept any received MFQ Policy Configuration Response from its associated AP.

The MFQReconfiguration bit shall be set to 1 in the Extended Capabilities element when

dot11MFQReconfigurationActivated is true. The MFQReconfiguration bit shall be set to 0 in the Extended Capabilities element when dot11MFQReconfigurationActivated is false.

The SME of a peer MFQ STA uses the MLME-MFQPOLICY primitives (See 6.3.ae1.2 to

6.3.ae1.5) to send a MFQ Policy frame to a peer STA. The SME of a peer STA uses the MLME-QMFPOLICY.request primitive to send an MFQ Policy frame to a peer STA.

Submission page 6

March 2011 doc.: IEEE 802.11-11/0377r1 The SME of a peer MFQ STA uses the MLME-MFQPOLICYCONFIG primitives (See 6.3.ae1.2 to 6.3.ae1.5) to exchange the MFQ Policy Change and MFQ Policy frames. The SME of a peer STA uses the MLME-QMFPOLICYCONFIG.request primitive to send an MFQ Policy Change frame to a peer STA. The SME of the peer STA evaluates the MFQ policy and uses the MLME-MFQPOLICYCONIF.response primitive to send a MFQ Policy frame to the STA including the result of the MFQ policy change along with resulting MFQ Policy.

When the MFQ STA SME receives the MLME-MFQPOLICYCHANGE.response with status set to 0 (success), it shall set the new MFQ Policy using the MFQPOLICYSET.request.

10.ae1.2.2 Management frame QoS policy configuration in a BSS

The partial MFQ Policy shall only be transmitted in Beacon frames.

A QMF AP shall include the MFQ Policy element in Beacon frames that it transmits. Non-AP MFQ STAs acquire management frame QoS policy configuration information from MFQ Policy elements received in Beacon, Association Response, Reassociation Response, Probe Response, and MFQ Policy Config response frames. The interpretation of the MFQ Policy element is described in 10.ae1.3 (Interpreting management frame QoS access categories).

All associated MFQ STAs transmitting management frames to an MFQ AP shall transmit those frames in accordance with the MFQ policy received in following order of precedence, from highest to lowest::

- MFQ Policy defined in the most recently received MFQ Policy element in a successful MFQ Policy Config Request/Response transaction;

- MFQ Policy defined in the MFQ Policy element received in the successful (re-)Association Response frame;

- MFQ Policy defined in the most recently received MFQ Policy element the last received Beacon frame from the AP.

All associated MFQ STAs transmitting group address management frames shall transmit those frames as MMFQ frames in accordance to the MFQ Policy received from its associated AP in following order of precedence:

- defined in the most recently received MFQ Policy element in a successful MFQ Policy Config Request/Response transaction;

- defined in the QMF Policy element received in the (re-)Association Response frame.

All unassociated MFQ STAs transmitting management frames to an QMF AP shall transmit those frames to the AP in accordance with the QMF Policy in the most recently received Beacon or Probe Response frame from that AP . If no frame containing an QMF Policy element has been received from the AP prior to the transmission of the management frame(s), then the management frame(s) shall be sent using the default QMF policy access categories defined in Table 10-ae1. All group addressed management frames transmitted by a non-assoicated QMF STA shall be transmitted as GQMF frame at default QMF policy access categories defined in Table 10-ae1.

Note that an QMFQMF STA transmits all management frames that are inpidually addressed to non-QMFQMF STAs using access category AC_VO. An QMF AP shall transmit all inpidually addressed management frames to a non-QMF STA using access category AC_VO.QMFQMF. Submission page 7

March 2011 doc.: IEEE 802.11-11/0377r1 All group addressed management frames transmitted by an QMF STA to QMF STAs across multiple ESSs shall be transmitted using the default QMF policy access categories defined in Table 10-ae1.

If the QMFReconfigurationActivated field is set to 1 in the Extended Capabilities element of the Beacon or Probe Response frame transmitted by the AP, QMF, an associated QMF STA may use the QMF Policy Config Request/Response to request a change in the existing QMF policy. 10.ae1.2.3 Management frame QoS policy configuration in an IBSS

A STA shall not include the QMF Policy element in a Beacon transmitted with the IBSS subfield of the Capability field equal to 1.QMF. The QMF policy shall be set on a per link basis between two QMF STAs within the IBSS. QMF

The QMF Policy Config Request and QMF Policy Config Response are used by QMF STAs in an IBSS to configure management frame QoS policy. QMFQMFQMFQMFQMFQMFQMFQMFQMFSee 10.ae1.2.1.

If an QMF STA does not receive a QMF Policy Config Request from a peer QMF STA, it shall transmit management frames to that peer QMF STA using the default QMF Policy. If the QMF STA accepts a QMF Policy Config Request, it shall respond with Status Code set to 0 (success) and shall transmit all inpidually addressed management frames destined to the requesting STA using the received management frame QoS policy. QMFQMFQMFQMFQMFQMF

QMF STAs in an IBSS shall use the default policy for all group-addressed management frames transmitted to other QMF STAs within the IBSS. QMF STAs in an IBSS shall not include policies for group addressed management frames in the QMF Policy Config Request.

10.ae1.2.4 Management frame QoS policy configuration in an MBSS

A QMF =STA operating in an MBSS shall set the QMFQMFActivated subfield in Extended Capabilities element to true. The Mesh Beacon shall not include an QMF Policy element. Within the MBSS, The QMF policy shall be set on a per link basis between two QMF Mesh STAs QMF. The QMF Policy Config Request and QMF Policy Config Response are used by QMF STAs in an MBSS to configure QMF QoS policy. See 10.ae1.2.1. QMFQMFQMFQMFQMFQMFQMFQMFQMF

If an QMF STA does not receive a QMF Policy Config Request from a peer QMF STA, it shall transmit management frames to that peer QMF STA using the default QMF policy. An QMF STA that accepts a QMF policy Config Request shall transmit all inpidually addressed management frames destined to the requesting QMF STA using the received management frame QoS policy.QMFQMFQMFQMFIf the QMF STA accepts a QMF Policy Config Request, it shall respond with Status Code set to 0 (success) and shall transmit all inpidually addressed Submission page 8

March 2011 doc.: IEEE 802.11-11/0377r1 management frames destined to the requesting STA using the received QMF QoS

policy.QMFQMF.

QMF STAs in an MBSS shall use the default policy for all group-addressed management frames transmitted to other QMF STAs within the MBSS. QMF STAs in an MBSS shall not include policies for group addressed management frames in the QMF Policy Config Request. QMFQMFQMFQMFQMFQMFQMFQMFQMFQMFQMFQMFQMFQMFQMFQMFQMFQM FQMFQMFQMFQMFQMFQMFQMFQMFQMF

Submission page 9

本文来源：https://www.bwwdw.com/article/n32l.html