Is this sentence outcome between the suggested and meaningful? Doesn't it end the existed text is the same, BRP the same with "may be frame can be sent with any MCS transmitted with any MCS"? 1566 10.7.7.5 An EDMG BRP packet is Change "EDMG BRP Accepted a concept of PHY packet " to " EDMG BRP frame" 1567 10.7.7.5 EDMG BRP frame is insert "2.16GHz" Accepted included in the single between "over a" and channel case as well as "4.32 GHz, 6.48 EDMG BRP packet GHz, 8.64 GHz, 2.16 + 2.16 GHz or 4.32 + 4.32 GHz channel" 1565 10.7.7.5 Lack of definition of "a Define " BRP Rejected BRP transaction". Transaction" or According to 11ad, " A Change" a BRP BRP is a short for Beam Refinment beam refinement transaction" to "a hence no need to include it in text transaction is a set of BRP beam refinement frames composed of transaction" request and responses." Revised text 10.7.7.5 Rate selection for BRP packets Change the following subclause as follow EDMG BRP packet sent during a BRP transaction to perform beamforming training over a 4.32GHz, 6.48 GHz, 8.64 GHz, 2.16 + 2.16 GHz or 4.32 + 4.32 GHz channel should be transmitted with MCS0. CID Clause Page Comment Proposed change 1852 10.7.7.7 Grammatical error in Change Accepted TXVECTOR parameter "NUM_USERS is restrictions set" to "NUM_USERS set" 1853 10.7.7.7 Grammatical error in Change Accepted TXVECTOR parameter "NUM_MOD is set" restrictions to "NUM_MOD set" 1854 10.7.7.7 Grammatical error in Change "set LONG" Accepted TXVECTOR parameter to "set to LONG" restrictions CID Clause Page Comment Proposed change 1965 10.7.7.9 Lack of relevant Append "IsSC field Accepted modulation class selection of L-Header is set to in the table 10-6 1" to the second column, second row, and "IsSC field of is set to 0" to the second column, third row.
Is this sentence meaningful? Doesn't it end the same with "may be transmitted with any MCS"? outcome between the suggested and the existed text is the same, BRP frame can be sent with any MCS 1566 10.7.7.5 An EDMG BRP packet is a concept of PHY Change "EDMG BRP packet " to " EDMG BRP frame" Accepted 1567 10.7.7.5 EDMG BRP frame is included in the single channel case as well as EDMG BRP packet insert "2.16GHz" between "over a" and "4.32 GHz, 6.48 GHz, 8.64 GHz, 2.16 + 2.16 GHz or 4.32 + 4.32 GHz channel" Accepted 1565 10.7.7.5 Lack of definition of "a BRP transaction". According to 11ad, " A beam refinement transaction is a set of BRP frames composed of request and responses." Define " BRP Transaction" or Change" a BRP transaction" to "a beam refinement transaction" Rejected BRP is a short for Beam Refinment hence no need to include it in text Revised text 10.7.7.5 Rate selection for BRP packets Change the following subclause as follow EDMG BRP packet sent during a BRP transaction to perform beamforming training over a 4.32GHz, 6.48 GHz, 8.64 GHz, 2.16 + 2.16 GHz or 4.32 + 4.32 GHz channel should be transmitted with MCS0. CID Clause Page Comment Proposed change 1852 10.7.7.7 Grammatical error in TXVECTOR parameter restrictions Change "NUM_USERS is set" to "NUM_USERS set" Accepted 1853 10.7.7.7 Grammatical error in TXVECTOR parameter restrictions Change "NUM_MOD is set" to "NUM_MOD set" Accepted 1854 10.7.7.7 Grammatical error in TXVECTOR parameter restrictions Change "set LONG" to "set to LONG" Accepted CID Clause Page Comment Proposed change 1965 10.7.7.9 Lack of relevant modulation class selection in the table 10-6 Append "IsSC field of L-Header is set to 1" to the second column, second row, and "IsSC field of is set to 0" to the second column, third row. Accepted
11-18-0375-02-00ay-multirate-support-cids.docx