IEEE P802.11 Wireless LANs LB 200 clause 8.4.2.170f comment resolution Date: 2014-01-23 Author(s): Name Affiliation Address Phone email George Calcev Huawei James Wang MediaTek Cheong ETRI Yongho Seok LGE Younghoon Kwon Huawei Interpretation of a Motion to Adopt A motion to approve this submission means that the editing instructions and any changed or added material are actioned in the TGah Draft. This introduction is not part of the adopted material. Editing instructions formatted like this are intended to be copied into the TGah Draft (i.e. they are instructions to the 802.11 editor on how to merge the text with the baseline documents). TGah Editor: Editing instructions preceded by “TGah Editor” are instructions to the TGah editor to modify existing material in the TGah draft. As a result of adopting the changes, the TGah editor will execute the instructions rather than copy them to the TGah Draft. CID Clause Page Comment Proposed Change Resolution 1134 8.4.2.170f 94 "Sector Operation element" 802.11ad has a lot of to do with sectors. This is a completely different kind of model. Rename element "S1G Sector Operation element" Review the names of all S1G elements, and prefix with "SIG" where they relate to concepts specific to S1G. Accept 1135 8.4.2.170f 94 ".. the duration of the current sector transmissions and it is measured in 10 milliseconds time units." Somewhat awkward. Also doesn't follow style for a value/unit pair. Replace with " the duration of the current sector transmissions, in units of 10 ms" Change 94.45 to match. Accept
1136 8.4.2.170f 95 "provided in Association Response when dot11S1GSectorizationActivated" " the station in the Association Response message." An "Association Response frame" is always exactly that. Not a message, not a empty <type of thing>. Review all "Association Response" and ensure it is followed by "frame". Also insert missing article in first cited sentence. Review all <name of frame> used in the draft (e.g. RTS, CTS, Ack, Beacon, Association Request, Probe Request ...) and ensure: 1. They are initial capitals 2. That they are followed by "frame", and remove any "message" following. Accept 2325 8.4.2.170f 94 The format of the Sector Operation element has two descriptions depending on sectorization type. The sentence here, refering to only one type, is confusing. Change to, "The format of the Sector Operation element is as presented in Figure or as presented in Figure 8-401cw, depending on the setting of the Sectorization Type field." Accept 2326 8.4.2.170f 94 The sentence "When the Sectorization Type is set to 0, it indicates group sectorization operation" seems like only a partial description, and is confusing. Change sentence to, "The Sectorization Type field is set to 0 to indicate group sectorization operation, and the use of this format for the Sector Operation element." Revise 2327 8.4.2.170f 94 Format this "Note" sentence as a Note. Format in the style of "NOTE -- ..." Accept 2328 8.4.2.170f 95 Format this "Note" sentence as a Note. Format in the style of "NOTE -- ..." Accept 2839 8.4.2.170f 94 The unit of sector duration set to 10 ms is too long since each sector in the 3-sectors BSS has a chance of transmission on every 30 ms. It will impact the latency of QoS services. Please clarify this issue or change the design. Reject 2840 8.4.2.170f 95 "Period duration" is not defined. Suggest to change "Period duration" to "Period field" Accept CID1134