IEEE P802.11 Wireless LANs LB203 MAC Comment Resolution on Sectorization Date: 2014-09-15 Author(s): Name Affiliation Address Phone James Wang Mediatek 2860 Junction Ave. San Jose, CA 95134 +1 408 526 1899 - 88109 This document provides resolutions for MAC CIDs on Sectorization. CID 3212, 3381, 3449, 3450, 3451, 3452, 3495, 3496, 3665, 3666, 3886, 4138, 4203, 3043, 4129, 3020, 3464, 3465, 3466, 3467, 3468, 3721 CID Commenter Clause Page Comment Proposed Change Resolution 3212 Alfred Asterjadhi 4.3.12b.6 10.49 For consistency, throughout the draft, use the already defined terminology "STA" (see 4.2.2) to refer to a wireless station. Replace "Station(s)" and "station(s)" with "STA(s)" throughout the draft except for their occurrences in subclause 3. Accept 3381 Bo Sun 4.3.12b.6 10.63 We have "Beacon" defined, not "beacon". replace all "beacon" with "Beacon" or "Beacon frame" all over the spec draft. Accept 3449 David Hunter 4.3.12b.6 11.18 "reuse" is the correct spelling in American English. Replace "re-use" with "reuse" here and on page 296 line 62, Accept 3450 David Hunter 4.3.12b.6 11.19 "Spatially Orthogonal" is not the name of a frame, field, etc., so does not take initial caps. Replace "Spatially Orthogonal" with "spatially orthogonal" here and on page 297 line 23 and page 300 lines 37 and 39. Accept 3451 David Hunter 4.3.12b.6 11.19 In "frame exchange which can lead Replace "exchange which can" with Revised. Agree in principle.
to significant increase of the overall network capacity." the subclause following 'which' is a side comment, so needs to be separated from the main senten by a comma. "exchane, which can". Instruct TGah editor editor to replace “exchange which can” with “exchange, which can”. 3452 David Hunter 4.3.12b.6 11.23 "Sectorization is not the name of a field, etc., so does not take the initial cap. Replace "Sectorization" with "sectorization". Accept CID Commenter Clause Page Comment Proposed Change Resolution 3495 David Hunter 9.48.4 Sectorization" is not the name of a frame, Replace "Group Sectorization" with "group sectorization". Accept 4
field, etc., so does not include initial caps. 3496 David Hunter 9.48.4 "indicates ... that it can cancel its NAV and its RID setting if ...": Huh? Otherwise it cannot ever cancel its NAV or RID? How is it able to do that in these circumstances, whe it could not possibly to such previously? Either change "can" with "might" or replace this description with one that explains why the receiver OBSS STAs would be interested in what the transmitter can possibly to. Accept CID Commenter Clause Page Comment Proposed Change Resolution 3665 kaiying Lv 9.48.4 The time point for an OBSS non-AP STA or OBSS AP to reset its NAV/RID is not clear. A minimum sensing time should be defined for an OBSS non-AP STA or OBSS AP to determine that it can't observe the subsequent beamformed transmission. The minimum sensing time could be the length of STF. Please change the text such as " not observing the subsequent sectorized beam preamble transmission from the AP during the time for transmitting STF after the of the long preamble ". And change the text for SO frame exchange sequence 3 and accordingly. Revised. in principle. Instruct TGah editor editor to make changes under the heading of CID3665 in the Document 3666 kaiying Lv 9.48.4 A minimum sensing time should be defined for an OBSS non-AP STA or OBSS AP to Please change the text such as" not observing the subsequent sectorized beam transmission from the AP for a PIFS Revised. Agree in principle. Instruct TGah editor editor to make 6
determine that it can't observing the subsequent beamformed minimum sensing time could be the PIFS interval. interval after the omni-beam transmission from the AP ". And also change the text for SO frame exchange sequence 3 and 4 accordingly. changes under the heading of CID3665 in the Document 3886 Matthew Fischer 9.48.4 what is the meaning of "protected duration"? provide a meaning for the term "protected duration" - see also p297 L40 and several other locations in this subclause Revised. Agree in principle. Instruct TGah editor editor to make changes under the heading of CID3665 in the Document 4138 Tom 9.48.4 delete undefined term delete the term "protected Revised. See CID 3886
will turn into a dark grey that will render the text below unreadable. 4129 Stephen Mccann 9.48.4 298.7 Figure 9-37 has some colour features. These should be changed to black and white to ease printing of the amendment. Edit the figure (and others) so they can be printed in black and white. Revised. See CID 3043. Supply figures with color removed. CID Commenter Clause Page Comment Proposed Change Resolution 3020 Adrian Stephens "The Period field has bit length" -- this is already normatively specified in the figure. Remove any such statements of length throughout the that duplicate material defined normatively elsewhere, such as in figures and tables. Revised. Instruct the editor to make the following changes “ The period has 6 but length and specifies the …” to “The period field specifies the …” and other bit lengths for the fields in this clause.
valuable sentence components. with: "indicates that the format of the S1G Sector Operation element is structured for the TXOP-based sectorization operation." 3467 David Hunter 135.8 "number of beacon Intervals in which": but "Interval" is not the name of a frame, field, etc., so does not use an initial cap. Replace "Intervals" with "intervals". Accept 3468 David Hunter 135 "is set to the remaining beacon intervals before": how can a be set to any beacon interval, much less several of them? Replace "is set to the remaining beacon intervals before" with "is set to the number of beacon intervals remaining before". Accept 3721 Liwen Chu 134.1 When Omni bit is 1, shouldn't this field be reserved? As proposed Revised. Instruct the editor to replace P134.1“The Sector ID is 3 bit length and identifies the ID of the