IEEE P802.11 Wireless LANs 11ax D2.3 MAC Comment Resolution for Random Access Date: 2018-04-30 Author(s): Name Affiliation Address Phone email Intel 2200 Mission College Blvd, Po-Kai Huang po-kai.huang@intel.com Corporation Santa Clara, CA 950542200 Chittabrata Ghosh Interpretation of a Motion to Adopt A motion to approve this submission that the editing instructions and any changed or added material are actioned in the TGax D2.3 Draft. This introduction is not part of the adopted material. Editing instructions formatted like this are intended to be copied into the TGax D2.3 (i.e. they are instructions to the 802.11 editor on how to merge the text with the baseline documents). TGax Editor: Editing instructions preceded by Editor” are instructions to the TGax editor to “TGax modify existing material in the TGax draft. As a result of adopting the changes, the TGax editor will execute the instructions rather than copy them to the TGax Draft. CID P.L Clause Comment Proposed Change Resolution 13082 Patrice 91.27 9.3.1.23 When the value of the AID12 field is Remove the Revised – Nezou 0 or 2045, then the RU Allocation following words subfield indicates the first RU of one "more contiguous" Different properties of random access or more contiguous random access RU complicates STA’s requirement to RUs. If there are more than one availability of different RU in SIFS random access RUs, the sizes of all response to Trigger frame. random access RUs are the same and equal to the size of the first RU. Further, the possibility of more than one Further all the subfields of the User User Info field for indicating random Info field apply to all the random access RU for associated or unassociated access RUs. STA complicates STA’s requirement to processs User Info field in SIFS response A user Info field allocates only ONE to Trigger frame. RU ? Allocate multiple RU with only one user info field implies that all Note that currently, AP can only put one random access RU have the same User Info field for associated STA non properties. Give different properties random access response. We propose to allows increasing the efficiency of have similar simplification for random random access by decreasing the access. number of eligible RUs for STAs.
IEEE P802.11 Wireless LANs 11ax D2.3 MAC Comment Resolution for Random Access Date: 2018-04-30 Author(s): Name Affiliation Address Phone email Po-Kai Huang Intel Corporation 2200 Mission College Blvd, Santa Clara, CA 950542200 po-kai.huang@intel.com Chittabrata Ghosh Interpretation of a Motion to Adopt A motion to approve this submission that the editing instructions and any changed or added material are actioned in the TGax D2.3 Draft. This introduction is not part of the adopted material. Editing instructions formatted like this are intended to be copied into the TGax D2.3 (i.e. they are instructions to the 802.11 editor on how to merge the text with the baseline documents). TGax Editor: Editing instructions preceded by “TGax Editor” are instructions to the TGax editor to modify existing material in the TGax draft. As a result of adopting the changes, the TGax editor will execute the instructions rather than copy them to the TGax Draft. CID P.L Clause Comment Proposed Change Resolution 13082 Patrice Nezou 91.27 9.3.1.23 When the value of the AID12 field is 0 or 2045, then the RU Allocation subfield indicates the first RU of one or more contiguous random access RUs. If there are more than one random access RUs, the sizes of all random access RUs are the same and equal to the size of the first RU. Further all the subfields of the User Info field apply to all the random access RUs. A user Info field allocates only ONE RU ? Allocate multiple RU with only one user info field implies that all random access RU have the same properties. Give different properties allows increasing the efficiency of random access by decreasing the number of eligible RUs for STAs. Remove the following words "more contiguous" Revised – Different properties of random access RU complicates STA’s requirement to availability of different RU in SIFS response to Trigger frame. Further, the possibility of more than one User Info field for indicating random access RU for associated or unassociated STA complicates STA’s requirement to processs User Info field in SIFS response to Trigger frame. Note that currently, AP can only put one User Info field for associated STA non random access response. We propose to have similar simplification for random access.