IEEE P802.11 Wireless LANs 11ax D1.0 MAC Comment Resolution for 10.3.2.4 and 27.2.2 Part I Date: 2017-03-06 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 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 TGax D1.0 Draft. This introduction is not part of the adopted material. Editing instructions formatted like this are intended to be copied into the TGax D1.0 Draft (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 Commenter P.L Clause Comment Proposed Change Resolution Yusuke 152.56 27.2.2 Two NAVs is defined in this spec but the Define a new CF-END Rejected – 0 Tanaka current RA field of CF-END is broadcast frame whose RA is and an HE STA can not decide which the address of the Currently, the TA field of the CF-End is always NAV should be reset when it receives intended STA. set to the BSSID. As a result, the STA can CF-END. always classify the frame as Intra-BSS or BSS based on the BSSID. Hence, there is no need to define a new CF-End Frame. Zhou Lan 150.25 27.2.2 "An HE non-AP STA shall maintain two per comment Rejected – NAV timers. An HE AP STA may maintain two NAV timers." clarify the different One of the main motivation for maintiatning requirement between AP and Non-AP two NAV timers is for the non-AP STA to be STA able to ignore the NAV and considers the basic NAV in response to Trigger frame. Since AP STA will never receive a Trigger frame. Maintaining two NAV timers is then optional for AP STA.
IEEE P802.11 Wireless LANs 11ax D1.0 MAC Comment Resolution for 10.3.2.4 and 27.2.2 Part I Date: 2017-03-06 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 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 TGax D1.0 Draft. This introduction is not part of the adopted material. Editing instructions formatted like this are intended to be copied into the TGax D1.0 Draft (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 Commenter P.L Clause Comment Proposed Change Resolution Yusuke Tanaka 152.56 27.2.2 Two NAVs is defined in this spec but the current RA field of CF-END is broadcast and an HE STA can not decide which NAV should be reset when it receives CF-END. Define a new CF-END frame whose RA is the address of the intended STA. Rejected – Currently, the TA field of the CF-End is always set to the BSSID. As a result, the STA can always classify the frame as Intra-BSS or based on the BSSID. Hence, there is no need to define a new CF-End Frame. Zhou Lan 150.25 27.2.2 "An HE non-AP STA shall maintain two NAV timers. An HE AP STA may maintain two NAV timers." clarify the different requirement between AP and Non-AP STA per comment Rejected – One of the main motivation for maintiatning two NAV timers is for the non-AP STA to be able to ignore the NAV and considers the basic NAV in response to Trigger frame. Since AP STA will never receive a Trigger frame. Maintaining two NAV timers is then optional for AP STA. BSS 0
11-17-0324-00-00ax-cr-for-10-3-2-4-and-27-2-2-part-i.docx