1136 8.4.2.170f 95 "provided in Association Review all "Association Accept Response when Response" and ensure dot11S1GSectorizationActivated" it is followed by " the station in the Association "frame". Response message." Also insert missing article in first cited An "Association Response sentence. frame" is always exactly that. Not a message, not a empty Review all <name of <type of thing>. 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. 2325 8.4.2.170f 94 The format of the Sector Change to, "The format Accept Operation element has two of the Sector Operation descriptions depending on element is as sectorization type. The sentence presented in Figure here, refering to only one type, is or as presented confusing. in Figure 8-401cw, depending on the setting of the Sectorization Type field." 2326 8.4.2.170f 94 The sentence "When the Change sentence to, Revise Sectorization Type is "The Sectorization set to 0, it indicates group Type field is set to 0 to sectorization operation" seems indicate group like only a partial description, sectorization operation, and is confusing. and the use of this format for the Sector Operation element." 2327 8.4.2.170f 94 Format this "Note" sentence as a Format in the style of Accept Note. "NOTE -- ..." 2328 8.4.2.170f 95 Format this "Note" sentence as a Format in the style of Accept Note. "NOTE -- ..." 2839 8.4.2.170f 94 The unit of sector duration set to Please clarify this issue Reject 10 ms is too long since each or change the design. sector in the 3-sectors BSS has a chance of transmission on every 30 ms. It will impact the latency of QoS services. 2840 8.4.2.170f 95 "Period duration" is not defined. Suggest to change Accept "Period duration" to "Period field" CID1134
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
11-14-0147-01-00ah-lb200-clause-8-4-2-170f-comment-resolution.docx