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

Re: [STDS-802-11-TGBN] [EXT] Re: [STDS-802-11-TGBN] TGbn Agenda for March F2F

Hello,

 

Bearing in mind the discussions of quantum computers this week, should we

consider a quantum-resistant alternative to DH?

 

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: Chittabrata Ghosh <chitta.ghosh@xxxxxxxxx>
Sent: Wednesday, 12 March 2025 13:53
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] [EXT] Re: [STDS-802-11-TGBN] TGbn Agenda for March F2F

 

Hi Alfred,

 

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, 

Chitto

 

 

 

 

 

On Wed, Mar 12, 2025 at 8:43 AM Liwen Chu <liwen.chu@xxxxxxx> wrote:

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]

 

 

 

 

 

From: Liwen Chu
Sent: Tuesday, March 11, 2025 9:01 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: RE: [EXT] Re: [STDS-802-11-TGBN] TGbn Agenda for March F2F

 

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

  • Do you support that:
    • 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.

 

 

 

 

From: Liwen Chu
Sent: Saturday, March 8, 2025 7:12 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: RE: [EXT] Re: [STDS-802-11-TGBN] TGbn Agenda for March F2F

 

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

 

On Fri, Mar 7, 2025 at 6:33 PM Alfred Asterjadhi <asterjadhi@xxxxxxxxx> wrote:

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.

 

Regards,


Alfred

 

--

Alfred Asterjadhi, PhD

IEEE802.11 TGbe/TGbn Chair,

Qualcomm Technologies Inc.

Cell #:    +1 858 263 9445

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