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 Remove all editing Revise 7 0 procedure between instructions that are two S1G STAs the proposed to be included Discussion: generally agree same behavior that inside the standard's text with the comment. is described and replace them with the However moving whole throughout this actual proposed S1G link adaptation to a subclause is valid normative text. See the new subclause creates with the following prpoosed text for 9.30.3 duplication and potential qualifications:": this and 9.33.5 (new error. is the beginning of a subclauses 11mc 9.31.3, set of instructions 9.34.5 and 9.34.7) in TGah editor makes the that would turn document 11-14-0784-01. changes indicated in sections of the under CID 3487 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. 9.30.3 since "bidirectional" Change either the Revise 0 is one word, "BDT" definiton of the S1G isn't a clear Capabilities Info field or Discussion: The comment acronym. 11mc the instructions here wrong reference already has a (better: change the (P270L7 has nothing to do defined acronym related text in document with bidirectional feautre). "BT"; but that 11-14-0478) to make this However, P270L39 seems acronym is not used subclause and what the comment try to anywhere in 11mc 8.4.2.170j.2 consistent. deal with. TACK, STACK and will be deleted, should be refered to TWT so there will be no conflict. However, TGah editor the the way "BDT" is changes indicated in used in this text is under CID odd 3488, 3787
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
11-14-1245-02-00ah-lb230-comment-resolution-for-9-30-3.docx