Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[STDS-802-11-TGAX] CID 24027

For the comment:

    24027

Seok, Yongho

319.54

26.2.5

 

When the NAV is set by the preamble puncture HE MU PPDUs (e.g., TXOP Duration field in the HE-SIG-A), there is no NAV reset mechanism in current TGax Draft.

Please define the NAV reset mechanism for this scenario.

Possible solutions are:

1) The CF-END frame is sent in the non-HT duplicate PPDU whose the TXVECTOR parameter CH_BANDWIDTH is set to the maximum bandwidth that does not cover the punctured channel.

This solution can't reset the NAV of all channels on which the preamble puncture HE MU PPDUs were sent.

2) The CF-END frame is sent in the non-HT duplicate PPDU having a preamble puncturing.

 

I would propose the following resolution (based on Po-Kai’s reject reason):

 

REJECTED:

The commenter is incorrect in asserting that there is no NAV reset mechanism for this scenario; the existing NAV reset mechanism (in 10.6.6.6 (Channel Width selection for Control frames)) applies. However, the commenter may be pointing out that this existing mechanism is inadequate. The CRC took a strawpoll to determine support for a new mechanism along the lines proposed: “Do you support send CF-END frame in non-HT duplicate PPDU with inactive channels?” The result Y/N/A=8/12/9 indicates that there is insufficient support for pursuing changes in the direction proposed.

 

-Robert

To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1