If a TXOP is protected by an RTS or CTS frame carried in a non-HT or a non-HT duplicate PPDU, the TXOP holder shall set the TXVECTOR parameter CH_BANDWIDTH as follows: So we will go with the proposed. Discussion , in the Std. in this concept, the term PPDU” is interpreted as PPDU”. “a “every Proposed resolution: REJECT In the Std., in this context, the term PPDU” is interpreted as PPDU” and therefore the instruction is “a “every unambiguous. CID Commenter Clause Line Comment Proposed 365 Woojin Ahn 10.22.2.4 1487.50 an EDCAF may reach a slot Add the following. boundary where the backoff timer has a value of 0 At each of the above-described without having any pending specific slot boundaries, each frame (e.g., expiration of EDCAF shall initialize EDCAF MSDU lifetime/ after -- is NO frame available for transmission as a transmission at that EDCAF, and holder). There's no -- The backoff timer for that normative behavior for such EDCAF has a value of 0 condition. We think thath it is better to initialize an EDCAF when its bacff counter reaches zero and there's no available frame. Discussion: To start the EDCA procedure there must be a frame queued for transmission (see P1485.16). I cannot find anything in the EDCA section on what happens if an MSDU lifetime expires. If this means that there is no frame in the transmit queue, then one would suppose that the EDCA is cancelled. In DCF and EDCA immediately after having successfully transmitted a packet the STA backs off using CWmin, and then counts down. So, if an MSDU lifetime is reached (due to excessive back off?), should the STA: still count down from where it is, wait for timer = 0 and then do not immediately back assume the condition that a frame has been transmitted, and immediately backs off using CWmin assume the condition that there is no frame to be transmitted and the backoff has reached 0. The commenter is proposing a)
If a TXOP is protected by an RTS or CTS frame carried in a non-HT or a non-HT duplicate PPDU, the TXOP holder shall set the TXVECTOR parameter CH_BANDWIDTH as follows: So we will go with the proposed. Discussion , in the Std. in this concept, the term “a PPDU” is interpreted as “every PPDU”. Proposed resolution: REJECT In the Std., in this context, the term “a PPDU” is interpreted as “every PPDU” and therefore the instruction is unambiguous. CID Commenter Clause Line Comment Proposed 365 Woojin Ahn 10.22.2.4 1487.50 an EDCAF may reach a slot boundary where the backoff timer has a value of 0 without having any pending frame (e.g., expiration of MSDU lifetime/ after transmission as a holder). There's no normative behavior for such condition. We think thath it is better to initialize an EDCAF when its bacff counter reaches zero and there's no available frame. Add the following. At each of the above-described specific slot boundaries, each EDCAF shall initialize EDCAF -- is NO frame available for transmission at that EDCAF, and -- The backoff timer for that EDCAF has a value of 0 Discussion: To start the EDCA procedure there must be a frame queued for transmission (see P1485.16). I cannot find anything in the EDCA section on what happens if an MSDU lifetime expires. If this means that there is no frame in the transmit queue, then one would suppose that the EDCA is cancelled. In DCF and EDCA immediately after having successfully transmitted a packet the STA backs off using CWmin, and then counts down. So, if an MSDU lifetime is reached (due to excessive back off?), should the STA: still count down from where it is, wait for timer = 0 and then do not immediately back assume the condition that a frame has been transmitted, and immediately backs off using CWmin assume the condition that there is no frame to be transmitted and the backoff has reached 0. The commenter is proposing a)