by the intended receiver of the whole or in part from the safeguards to those previously frame that is currently under draft. approved. The net effect of these way. *Every* device that is changes has been to enable the permitted to transmit under victim transmitter, subject to current rules will still be permission from the victim AP, to allowed to transmit under the disallow OBSS_PD. The TG rule in the diagram. In considers that the safeguards addition, many more devices available, including the ones will be allowed to transmit. provided in the above referenced Even worse, *every* new document and others (e.g., exclusion device that is allowed to of TXOPs protected by CTS-to-self), transmit will be allowed to do provide fully adequate assurance of so at a transmit power level acceptable operation. that results in the maximum level of interference that would apply under the existing rules: essentially the rule requires the new, interfering transmitter to reduce its transmit power, but only by just enough to get the interference down to that existing maximum. The justifications that have been given for this radical departure from prior practice seem extraordinarily weak, and essentially seem to boil down to (a) a misconception that the current rules constitute a safe harbor, at which the interference caused can be treated as if it didn't exist, and/or (b) the argument that other wireless standards, with entirely different deployment models and a vastly different installed base, do the same thing. This is a reckless attack on the fundamental integrity of 802.11 and on the indispensable attribute of backward compatibility. No evidence has been presented that even begins to justify the changes that are being proposed. Discussion: Document 17/458 describes the need and mechanism to disable OBSS_PD based spatial reuse. This document covers the specification text change required to enable the OBSS_PD spatial reuse feature. TGax Editor: OBSS_PD spatial reuse disable setting to disable OBSS_PD spatial reuse on the transmitted packet, add to 28.16: Set to SRP Disallowed to disallow SRP-based spatial reuse (see 27.9 (Spatial reuse operation) and 27.11.6 B15-B18 Spatial Reuse 4 (SPATIAL_REUSE)). NOTE—This part further development.
by the intended receiver of the frame that is currently under way. *Every* device that is permitted to transmit under current rules will still be allowed to transmit under the rule in the diagram. In addition, many more devices will be allowed to transmit. Even worse, *every* new device that is allowed to transmit will be allowed to do so at a transmit power level that results in the maximum level of interference that would apply under the existing rules: essentially the rule requires the new, interfering transmitter to reduce its transmit power, but only by just enough to get the interference down to that existing maximum. The justifications that have been given for this radical departure from prior practice seem extraordinarily weak, and essentially seem to boil down to (a) a misconception that the current rules constitute a safe harbor, at which the interference caused can be treated as if it didn't exist, and/or (b) the argument that other wireless standards, with entirely different deployment models and a vastly different installed base, do the same thing. This is a reckless attack on the fundamental integrity of 802.11 and on the indispensable attribute of backward compatibility. No evidence has been presented that even begins to justify the changes that are being proposed. whole or in part from the draft. safeguards to those previously approved. The net effect of these changes has been to enable the victim transmitter, subject to permission from the victim AP, to disallow OBSS_PD. The TG considers that the safeguards available, including the ones provided in the above referenced document and others (e.g., exclusion of TXOPs protected by CTS-to-self), provide fully adequate assurance of acceptable operation. Discussion: Document 17/458 describes the need and mechanism to disable OBSS_PD based spatial reuse. This document covers the specification text change required to enable the OBSS_PD spatial reuse feature. TGax Editor: OBSS_PD spatial reuse disable setting to disable OBSS_PD spatial reuse on the transmitted packet, add to 28.16: B15-B18 Spatial Reuse 4 Set to SRP Disallowed to disallow SRP-based spatial reuse (see 27.9 (Spatial reuse operation) and 27.11.6 (SPATIAL_REUSE)). NOTE—This part further development.
11-17-0500-01-00ax-comment-resolution-for-obss-pd-spatial-reuse-disallow.docx