IEEE P802.11 Wireless LANs Comment Resolutions for 9.30.3 Date: 2014-09-02 Author(s): Name Affiliation Address Phone email Chu Marvell Abstract This submission proposes comment resolutions for subclause 9.30.3: 3036, 3487, 3488, 3489, 3490, 3491, 3787. 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 Num P L Comment Propose Change Resolution 9.30.3 60 " HT Control which can be used" - ungrammatical. In the general case, confusion between "which" and "that" can change the meaning. Please review the English grammar for "that vs which". Good: "receives an Review all use of "which" (generally 'that' is OK) and replace "which" with ", which" or "that" when not preceded by a preposition. Revise Discussion: generally with the comment. Comment 3486 already remove “which” from the sentence. So no further change is required here Refer to CID 3486 9 6
RTS, which causes a CTS to be sent", "receives an RTS in which the A1 field is ..." See 275.04 for an example of the other class of error. 9.30.3 1 For link adaptation procedure between two S1G STAs the same behavior that is described throughout this subclause is valid with the following qualifications:": this is the beginning of a set of instructions that would turn sections of the standard into a instruction booklet of changes needed to create new sections, rather than text providing the sections themselves. Not only is this process rife with problems (some of which are noted in other comments), but it would make a mockery of an IEEE standard. Remove all of these instructions from the proposed text and create the new sections and the (proposed) text for them. Remove all editing instructions that are proposed to be included inside the standard's text and replace them with the actual proposed normative text. See the prpoosed text for 9.30.3 and 9.33.5 (new subclauses 11mc 9.31.3, 9.34.5 and 9.34.7) in document 11-14-0784-01. Revise Discussion: generally agree with the comment. However moving whole S1G link adaptation to a new subclause creates duplication and potential error. TGah editor makes the changes indicated in under CID 3487 9.30.3 7 since "bidirectional" is one word, "BDT" isn't a clear acronym. 11mc already has a defined acronym "BT"; but that acronym is not used anywhere in 11mc and will be deleted, so there will be no conflict. However, the way "BDT" is used in this text is odd Change either the definiton of the S1G Capabilities Info field or the instructions here (better: change the related text in document 11-14-0478) to make this subclause and 8.4.2.170j.2 consistent. Revise Discussion: The comment wrong reference (P270L7 has nothing to do with bidirectional feautre). However, P270L39 seems what the comment try to deal with. TACK, STACK should be refered to TWT TGah editor the changes indicated in under CID 3488, 3787 0 0