July 2010Doc.: IEEE 802.11 10-0999-00-00Ad CID175 Resolution

July 2010doc.: IEEE 802.11--10-0999-00-00ad_CID175_Resolution.

IEEE P802.11
Wireless LANs

D0.1 comment resolution part 3
Date: 2010-08-26
Author(s):
Name / Company / Address / Phone / email
Chao-Chun Wang / MediaTek /
Carlos Cordeiro / Intel /
175 / 7.3.2.30 / 61 / 11 / TR / "may" sounds like normative language. 11mb has gone to great lengths to remove normative language from clause 7, and this does not help. / Search clause 7 for shall and may, and find a home for this normative material in clauses 9 or 11. Also, related language such as "must be", "required", etc

Discussion: many of the normative statements in Clause 7 are already present in either Clause 8, 9 or 11. Therefore, in most cases it is just a matter of making these statements informative.

Resolution: Accept

7.1.3.5.8A-MSDU Present subfield

Editor Instruction: replace one instance of “may” by “can”

7.2.4.1mmWave Beacon

Editor instruction: change the 2 instances of “may” by “can”

7.3.2.21.12Directional Channel Quality request

Editor instruction: Change the 4th para as follows:

The AID indicates the Target STA. If the Requested STA is already beamformed with the Target STA, then the measurement shall beis carried out employing the same receive antenna configuration as is used by the Requested STA when receiving frames from the Target STA. If the AID is set to the broadcast AID or an unknown AID, then the Requested STA shall performs the measurements using an quasi-omni antenna pattern.

Editor instruction: Change the 6th para as follows:

The Measurement Start Time field is set to the TSF timer at the time at which the requested measurement shall starts. A value of 0 indicates that the measurement starts immediately.

7.3.2.21.13Directional Measurement request

Editor instruction: Change the 4th para as follows:

The Measurement Start Time field is set to the TSF timer at the time at which the requested measurement shall starts. A value of 0 indicates that the measurement starts immediately.

7.3.2.21.14Directional Statistics request

Editor instruction: Change the 4th para as follows:

The Measurement Start Time field is set to the TSF timer at the time at which the requested measurement shall starts. A value of 0 indicates that the measurement starts immediately.

7.3.2.25.1Cipher suites

Editor instruction: change the para below as follows:

The cipher suite selector 00-0F-AC:<ANA> (GCMP) shall beis the only cipher suite value for an mSTAoperating in the DBand (8.3.1).

Editor instruction: move the following paragraph to become the last para in subclause (8.4.12 Multi-band RSNA):

If a pair of multi-band capable mSTAssupport GCMP in a band other than the DBand, GCMP shall be the only valid option for the mSTA pair in that band.

7.3.2.30TSPEC element

Editor instruction: change the indicated paras as follows:

In a PTP TSPEC the TSID subfield is 4 bits in length and contains a value that is a TSID. The combination of the TSID, Source STA AID, Destination STA AID and Direction subfields identify the TS, in the context of the non-AP STA, to which the TSPEC applies. A non-AP STA as a Source STA may can use the TSID subfield value for an uplink PTP TSPEC and at the same time the non-AP STA as a Destination STA may can use the same TSID subfield value for a downlink PTP TSPEC. A bidirectional link request is equivalent to a downlink TS and an uplink TS, each with the same TSID and parameters.

When this field is included in the ADDTS request frame and the direction is set to downlink, and when this field is included in the ADDTS response frame and the direction field is set to uplink, then the value in this field represents the receiver expectation of the PERper specific TSID.This information is provided by the SME using the MLME-ADDTS.request primitive and MLME-ADDTS.response primitives. Together with the Link Margin (9.27) and other implementation specific information, the value may can be used by the transmitter to estimate the MCS to be used for this particular TS.

7.3.2.46Multiple BSSID element

Editor Instruction: change the indicated para as follows:

When the Multiple BSSID element is transmitted in a Beacon, mmWave Beacon, or Probe Response frame, the reference BSSID is the BSSID of the frame. More than one Multiple BSSID element maycan be included in a Beacon or mmWave Beacon frame. The AP/mSTA determines the number of Multiple BSSID elements. The AP/mSTA does not fragment a non-transmitted BSSID profile subelement for a single BSSID across two Multiple BSSID elements unless the length of the non-transmitted BSSID profile subelement exceeds 255 octets. When the Multiple BSSID element is transmitted as a subelement in a Neighbor Report element, the reference BSSID is the BSSID field in the Neighbor Report element.

7.3.2.90mmWave Capabilities element

Editor Instruction: in the first para, replace “may” by “can”

7.3.2.91.2 mmWave PCP/AP Capability Information field

Editor Instruction: Change the 3rd para as follows:

The Pseudo-static allocations field is set to 1 if the STA, while operating as a PCP/AP, is capable of providing pseudo-static allocations as defined in 9.23.6.3 Pseudo-static allocations and is set to 0 otherwise. The Pseudo-static allocations field may beis set to 1 only if the TDDTT field in the mmWave PCP/AP Capability Information field is set to 1. The Pseudo-static allocations field is reserved if the TDDTT field in the mmWave PCP/AP Capability Information field is set to 0.

7.3.2.91mmWave Operation element

Editor Instruction: Change the 4th para as follows:

The Pseudo-static allocations field is set to 1 if the PCP/AP provides pseudo-static allocations as defined in 9.23.6.3 Pseudo-static allocations and is set to 0 otherwise. The Pseudo-static allocations field may beis set to 1 only if the TDDTT field in the mmWave Operation Information field is set to 1. The Pseudo-static allocations field is reserved if the TDDTT field in the mmWave Operation Information field is set to 0.

7.3.2.92mmWave Beam refinement element

Editor Instruction: replace “shall be” by “is” in Table 13 – FBCK-TYPE field

7.3.2.93Extended Schedule element

Editor Instruction: change the first para as indicated

The Extended Schedule element is formatted as illustrated in Figure 39. Because the length parameter supports only 255 octets of payload in an element, the PCP/AP may can split the Allocation fields into more than one Extended Schedule element entry in the same mmWave Beacon or ATAnnounce frame.Despite this splitting, the set of Extended Schedule element entries conveyed within a mmWave Beacon and Announce frame is considered to be a single schedule for the BI, and in this specification referred to simply as Extended Schedule element unless otherwise noted. The Allocation fields shall beare ordered by increasing allocation start time with allocations beginning at the same time arbitrarily ordered.

Editor Instruction: insert the following sentence in the 3rd para of 9.23.6: “The same Allocation field shall not appear more than once in the Extended Schedule element transmitted in a BI.”

7.3.2.94Extended mmWave TSPEC element

Editor Instruction: replace “shall be” by “is” in the para starting with “For asynchronous requests, Maximum Allocation field is reserved and the Allocation Period, Minimum Allocation and Minimum SP Duration fields are set as follows…”

7.3.2.95Channel measurement feedback element

Editor Instruction: replace “shall be” by “is” in the para starting with “Each channel measurement contains Ntaps channel impulse taps. The channel impulse response reported for all Nmeas measurements correspond to a common set of relative tap delays. If the Tap Delay subfield is not present …”

7.3.2.96ADDBA extension element

Editor Instruction: replace the 2 instances of “may” by “can” in this subclause

7.3.2.97Session Transition element

Editor Instruction: change the indicated paragraph as follows

When the Session type field is set to IBSS and the STA Role field within the Multi-band element is set to IBSS STA, the BSSID field within the Multi-band element containsthe MAC address of the BSSID of the IBSS. This indicates It means that the transmitting STA is not associated in with an AP on the band and channel indicated in the Multi-band element and it may want to perform IBSS mode with the peer STA.

7.3.2.98Quiet period request element

Editor Instruction: replace all 5 instances of “shall be” by “is”

7.3.2.99Quiet period response element

Editor Instruction: replace 1 instance of “shall be” by “is”

7.3a.1 Sector Sweep field

Editor Instruction: replace 1 instance of “shall be” by “is”

7.3a.5 Beamforming Control field

Editor Instruction: replace 2 instances of “shall be” by “is”

7.4.13.1Announce

Editor Instruction: replace 1 instance of “may” by “can” in Table 29 - Announce

7.4.13.2Beam Refinement (BRP)

Editor Instruction: change the indicated para as follows:

The Beam Refinement frame contains more than one Channel measurement feedback element if the measurement information exceeds 254 bytes. The content of each Channel measurement feedback element that follows the first one in a single Beam Refinement frame is a continuation of the content in the previous element. The Channel measurement subfield and the Sector ID subfield may can be split between several elements. Each Channel measurement feedback element that is not the last Channel measurement feedback element in the frame shall beis 256 bytes long. Channel measurement information for a single channel measurement is always contained within a single Beam Refinement frame.

7.4.13.3Relay search request

Editor Instruction: replace one instance of “shall be” by “is”

7.4.13.4Relay search response

Editor Instruction: replace one instance of “shall be” by “is”

7.4.13.5Multi-relays channel measurement request

Editor Instruction: replace one instance of “shall be” by “is”

7.4.13.6Multi-relays channel measurement report

Editor Instruction: replace two instances of “shall be” by “is”

7.4.13.7RLS request