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

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

Hi Alfred,


Please add the following SPs to the MAC queue:


Coex:


SP1: Do you agree to the following conditions for transmitting unsolicited unavailability indications that can be sent by a non-AP as a TXOP holder in a BSRP GI3 trigger frame:


Supporting documents: 11-24/1559r1



Control/Security:


  1. Do you agree that the I-FCS in a Trigger frame is included as part of 2 contiguous User Info fields known as I-FCS User Info fields?

  2. Do you agree that the AID in these 2 I-FCS User Info fields have the same special AID12 value of 2011?

  3. Do you agree that the 32 bits of the actual I-FCS are distributed between the 2 I-FCS User Info fields keeping 24 bits in first User Info and 8 bits in second User Info?

  4. Do you agree that the I-FCS bits in each I-FCS User Info field start on the byte boundary after leaving a gap of 4 reserved bits after the AID12 field?

  5. Do you agree that the input to the I-FCS computation covers all bytes from the Frame Control field up to and including the last User Info that precedes the I-FCS, but not including anything in the I-FCS User Info fields or later?

    1.  The input of the I-FCS does not cover any of the fields starting from the first IFCS User Info field

  6. Do you agree that the I-FCS User Info fields appear after all User Info fields that are addressed to STAs that require the inclusion of I-FCS?

  7. Do you agree that, representing IFCS value as IFCS[0:31] where IFCS[0] is the LSB, the IFCS bits are ordered in the 2 consecutive “Dedicated IFCS” User Info fields in the trigger frame as follows:

    1. The 24 bits of IFCS (namely IFCS0 subfield) in the 1st “dedicated IFCS” User Info field contain IFCS[0:23] in the same order (bit 16 of the 1st “dedicated IFCS” User Info field is set to IFCS[0])

    2. The 8 bits of IFCS (namely IFCS1 subfield) in the 2nd “dedicated IFCS” User Info field contain IFCS[24:31] in the same order (bit 16 of the 2nd “dedicated IFCS” User Info field is set to IFCS[24])



Supporting documents: 23/1873r0, 23/2003r1, 25/0144, 24/497r0, 24/1129r1


Regards,

Sindhu



On Sat, Mar 8, 2025, 8:03 AM 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

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature