description of the protocol, as defined in the proposed changes in doc 3197 27.9.1 SR mode is not defined: "A Revise or define SR Revised agree that – STA can select an mode. SR mode is not clear. OBSS_PDlevel during its Clarify the text, by operation under SR mode." defining an OBSS_PD Also in P192L7. SR opportunity and using this along the description of the protocol, as defined in the proposed changes in doc 5689 27.9.2.2 SR mode is not defined. It is Define what exactly Revised Clarify the – better to define the mode in is SR mode. For text, by removing SR the beginning of this section. example, " a mode mode, defining an that a STA operates OBSS_PD SR in a PD level that is opportunity and differnet from legacy using this along the PD threshold on description of the OBSS PPDUs" protocol, as defined in the proposed changes in doc 9541 27.9.2.2 """If a STA chooses a specific Define SR mode. Revised Clarify the – OBSS_PD_{level} during its text, by removing SR operation under SR mode, mode, defining an ..."" OBSS_PD SR opportunity and SR mode undefined." this along the description of the protocol, as defined in the proposed changes in doc 3222 190.30 27.9.2.1 There should be an Suggest to add exception for response exceptions for any frames (e.g. CTS, ACK, and response BA etc) here. Otherwise a such as CTS, ACK, STA ignores an OBSS TXOP BA etc. The whose intended recipient exception could happens to be nearby, e.g. be similar to the within -62dBm or -72dBm currently-listed reach. This causes exceptions for significant interference to Public Action the OBSS recipient which frames. could have been ignored if response frames where excluded from OBSS-PD rule.
description of the protocol, as defined in the proposed changes in doc 3197 27.9.1 SR mode is not defined: "A STA can select an OBSS_PDlevel during its operation under SR mode." Also in P192L7. Revise or define SR mode. Revised – agree that SR mode is not clear. Clarify the text, by defining an OBSS_PD SR opportunity and using this along the description of the protocol, as defined in the proposed changes in doc 5689 27.9.2.2 SR mode is not defined. It is better to define the mode in the beginning of this section. Define what exactly is SR mode. For example, " a mode that a STA operates in a PD level that is differnet from legacy PD threshold on OBSS PPDUs" Revised – Clarify the text, by removing SR mode, defining an OBSS_PD SR opportunity and using this along the description of the protocol, as defined in the proposed changes in doc 9541 27.9.2.2 """If a STA chooses a specific OBSS_PD_{level} during its operation under SR mode, ..."" SR mode undefined." Define SR mode. Revised – Clarify the text, by removing SR mode, defining an OBSS_PD SR opportunity and this along the description of the protocol, as defined in the proposed changes in doc 3222 190.30 27.9.2.1 There should be an exception for response frames (e.g. CTS, ACK, and BA etc) here. Otherwise a STA ignores an OBSS TXOP whose intended recipient happens to be nearby, e.g. within -62dBm or -72dBm reach. This causes significant interference to the OBSS recipient which could have been ignored if response frames where excluded from OBSS-PD rule. Suggest to add exceptions for any response such as CTS, ACK, BA etc. The exception could be similar to the currently-listed exceptions for Public Action frames.
11-17-0267-01-00ax-cr-for-25-9-2-2-obss-pd-spatial-reuse.docx