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

[STDS-802-11-TGBE] FW: SP2 in 485r2

Hi Alfred

I initiated this discuss on the remaining SP of 485r2 a week ago and received one comment over email. Can you help to bring it back to the agenda next week and see if we can finalize? It will help to resolve the TBDs on MU-RTS. Thanks.

 

BRs,

Xiaogang.

 

From: Chen, Xiaogang C <xiaogang.c.chen@xxxxxxxxx>
Sent: Thursday, April 8, 2021 10:09 AM
To: Chen, Xiaogang C <xiaogang.c.chen@xxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: SP2 in 485r2

 

Hi all,

I’d like to use this thread to initiate the discussion of SP2 in 485r2 I presented yesterday. The last bullet of the SP has been modified to reflect the comment I received from Gorge, and the new SP text is highlighted below. I also add several response to the Qs I got in the call. Feel free to comment and let me know if I missed any question/comments in the call.

 

Do you agree that

    • The CTS response to MU-RTS supports all the modes defined in 11ax and 320MHz Non-HT duplicate transmission;
    • The CTS response to MU-RTS supports transmitting on non-contiguous 20MHz subchannels; 
    • The CTS response to MU-RTS shall be transmitted on the 20MHz subchannel(s) that are overlapped with the large size RU indicated by its own RU allocation subfield.
      • The large size RU indicated by the RU allocation subfield shall be overlapped with the Primary 20MHz channel, such that the CTS transmission includes the primary 20MHz channel.

 

Discussions:

  1. RU vs. RU/MRU: Although my intention at the very beginning is to use “RU/MRU” ,now I am changing to “RU” for several reasons: 1) Since no puncture information is included for RTS, CTS response to RTS also need to retrieve the puncture information from Beacon/operating elements. Given that, I can see the point people prefer “RU”, such that the CTS response to MU-RTS also retrieve the same information as the CTS response to RTS. 2) not including MRU will significantly simplify the spec draft because if we reuse the same style of MU-RTS in  11ax, all the configurations of MRU need to be listed if “MRU” can be indicated in RU allocation subfield.

 

  1. SST: I didn’t include SST in the SP because EHT R1 didn’t extend the SST support defined in 11ax but push to R2. Instead of add another bullet and more TBDs(which is not preferred in current stage), it’s better to enable the SST related portion in R2 after everything is clear.

 

 

BRs,

Xiaogang.

 

From: Chen, Xiaogang C <xiaogang.c.chen@xxxxxxxxx>
Sent: Wednesday, March 17, 2021 11:19 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] TGbe Teleconferences [03/17/2021]: Agendas Posted

 

Hi Alfred

Please kindly add the contribution below to the joint agenda. Thanks.

 

11-21-0485-00-00be Clarifications on the trigger frame design.

 

BRs,

Xiaogang.

 

From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: Monday, March 15, 2021 1:17 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] TGbe Teleconferences [03/17/2021]: Agendas Posted

 

Hello all,

 

I uploaded an updated version of the agendas, which contains the agenda for the next conference calls, scheduled on  Wednesday, March 17 (MAC/PHY), 10:00-12:00 ET.

 

The agendas can be found here:

https://mentor.ieee.org/802.11/dcn/21/11-21-0385-05-00be-mar-may-tgbe-teleconference-agenda.docx

 

DIAL IN DETAILS FOR WEDNESDAY:

Join the MAC meeting here: https://ieeesa.webex.com/ieeesa/j.php?MTID=mfb2eb674f949c8c6823ca5a367ae501a Meeting number: 129 723 0407 Meeting password: wireless (94735377 from phones and video systems)    

 

Meeting number: 129 582 0621 Meeting password: wireless (94735377 from phones and video systems)

 

Notice: Please note that by now all authors of the submissions for PDTs and CRs (especially MAC) should have sent requests for feedback to the IEEE TGbe reflector. Members are invited to provide feedback for these contributions prior to the conference call via e-mail so that the time in the conf calls is used efficiently. 

 

Best Regards,

 

Alfred

 

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

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

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