Thanks, Morteza.
I have the following remaining comments:
- 37.x "A DSO non-AP STA may enable or disable the DSO mode" -- I think
it should be made clearer that this is just for its link with the AP,
not generally
- 37.x "The DSO AP shall set the length of the Padding field of the DSO ICF
based on the rules defined in 37.x1 (Padding for a Trigger frame in presence
of intermediate FCS) to ensure that the ICF’s MAC padding duration,
which follows the intermediate FCS if needed by the DSO non-AP STA"
is confusing because it indicates the IFCS might not be present,
but says the padding length is defined in a subclause which ostensibly
only applies in the presence of an IFCS
- 37.x I don't understand why two bullets start "The MAC of the DSO non-AP STA",
while the third just goes "The DSO non-AP STA". This is in a MAC clause,
so it's obvious it's the MAC. I think the first two bullets should be
changed to match the third, i.e. delete "MAC of the"
- 37.x "the DSO non-AP STA does not detect within the PPDU corresponding to the PHY-RXSTART.indication any of the following frames:
[…] a CTS-to-self frame with the RA equal to the MAC address of the DSO AP"
The non-AP STA did not send the CTS frame and indeed not the nominal
receiver for it, so it does not make sense to call it a CTS-to-self
frame. It's just a CTS frame where the RA is the AP's MAC address.
So "-to-self" should be deleted
Editorials:
- 37.x "Dynamic Subband Operatio (DSO)" should be "dynamic subband operation (DSO)" [case and missing n]
- 37.x "DSO operation" should be just "DSO"
- 37.x "NOTE—how" should be "NOTE—How"
Thanks,
Mark
--
Mark RISON, Standards Architect, WLAN English/Esperanto/Français
Samsung Cambridge Solution Centre Tel: +44 1223 434600
1 Cambridge Square, Cambridge CB4 0AE Fax: +44 1223 434601
ROYAUME UNI WWW:
http://www.samsung.com/uk
From: Morteza Mehrnoush <morteza.80211@xxxxxxxxx>
Sent: Wednesday, 12 March 2025 20:58
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] [EXT] Re: [STDS-802-11-TGBN] TGbn Agenda for March F2F
Hi Mark,
Thanks for the comments. Most of your comments are accepted and r4 is uploaded.
Hello,
I have the attached comments on r3.
Thanks,
Mark
--
Mark RISON, Standards Architect, WLAN English/Esperanto/Français
Samsung Cambridge Solution Centre Tel: +44 1223 434600
1 Cambridge Square, Cambridge CB4 0AE Fax: +44 1223 434601
ROYAUME UNI WWW:
http://www.samsung.com/uk
Hi Alfred,
Could you please add DSO PDT (11-25/0454r3) to the MAC queue to run the SP?
Do you support to incorporate the proposed text changes for DSO in 11-25/0454r3 to the latest TGbn draft?
I have deferred my SP based on the request from the floor based on my contribution 11-24/1882r2. Please assist me by including the SP in my document following the SP in contribution 11-24/1883r3.
Do you support that
• TBD request frame initiating roaming preparation
carries the DH parameter element of the non-AP MLD when new PTK is derived
• TBD response frame during roaming preparation carries
DH parameter element generated by the target AP MLD when new PTK is derived
• Non-AP MLD and the target AP MLD derive the PTK based
on the shared PMK and DHss in TBD request and TBD response frames?
Best Regards,
Hi Alfred,
Please add the following SPs to the MAC queue.
Hi all, if you have comments to the SPs, please let me know.
Best Regards,
Liwen
SP 1
-
Do you agree to amend Motion #273 as following?
-
TGbn defines or improves an existing mechanism so that a non-AP STA that is a TXOP responder can indicate its buffered
low latencyLL traffic needs (for traffic from the TxOP TXOP responder to the
TxOP TXOP Holder) in a control response frame. The TXOP holder should consider the indication in determining subsequent actions. Subsequent actions related to this indication are out of the scope of the standard.
-
Note: whether an AP can Indicate indicate its low latency needs is TBD -
The Low Latency Indication is included in the Feedback field of the Feedback Per AID TID Info field (the one that carries control feedback).
-
The Feedback Type field (Located in B12 to B15 of the Block Ack Starting Sequence Control) is set to 1
-
Note: Feedback Type field set to 0 is used for DUO feedback
-
TBD bits in the Feedback field is defined to provide the low latency need.
[support document: 11-25/421]
SP2
-
Do you support that an UHR STA that sets its NAV timer per the BSRP Trigger frame may reset its NAV timer if the following condition is true
-
no PHY-RXEARLYSIG.indication or PHYRXSTART.indication primitive is received from the PHY during a NAVTimeout period.
-
The NAVTimeout period is equal to (2 × aSIFSTime) + T_PREAMBLE + T_SIGNAL + UL_Length + aRxPHYStartDelay + (2 × aSlotTime).
(see Table 17-5—Timing-related parameters)
[support document: 11-25/425]
Hi Alfred,
Please add the following SPs to the MAC queue.
Hi all, if you have comments to the SPs, please let me know.
Best Regards,
Liwen
SP1
-
Do you agree that an AP shall not allow the use of NPCA within its BSS if the BSS operating bandwidth is less than or equal to 40 MHz?
SP2
-
If a TXOP on the NPCA Primary channel overlaps with the TBTT, the AP shall not transmit the Beacon frame or group addressed frames until it switches back to the BSS Primary channel.
-
NOTE – The NPCA AP and non-AP STA participating in frame exchanges must not switch back to the BSS Primary channel at the TBTT and can continue operating on NPCA Primary until the OBSS transmission ends on BSS Primary channel.
Hi Alfred,
Please add the following contributions the queue:
1, 11-25/421, low latency indication
2, 11-25/422, ICF and NAV operation
Best Regards.
Liwen
Hello all,
The initial agenda for the March F2F meeting can be found here.
I plan to upload a revised version that contains the queues up to date (until tomorrow, Saturday,
5:00pm PT) and a preliminary spread of the submissions in each session following the usual per-topic arrangement. To make sure that the queues are stable by then, please send me the submission requests by tomorrow,
Saturday 5:00pm PT).
After that, I will upload the revised version with all received contributions and send the final call for submissions with the usual Sunday deadline.
--
IEEE802.11 TGbe/TGbn Chair,
Qualcomm Technologies Inc.
Office #: +1 858 658 5302
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
![]()
|
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1