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

Re: [STDS-802-11-TGBK] TGbk Apr. 4th Telecon - Call for submissions

Hi Wook Bong,

 

Thank you for reviewing the draft and providing the early inputs. Please see some early feedback inline.

 

 

Thanks

Yanjun

 

From: Wook Bong Lee <wookbong.lee@xxxxxxxxx>
Sent: Tuesday, April 4, 2023 8:27 AM
To: Yanjun Sun <yanjuns@xxxxxxxxxxxxxxxx>
Cc: STDS-802-11-TGBK@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBK] TGbk Apr. 4th Telecon - Call for submissions

 

Hi Yanjun,

 

Thanks for the contribution.

I have a few comments.

 

I am not sure whether restricting to a certain PPDU format is a right/general way to do in MAC.

YS> the baseline text has some rules to limit PPDU selection for theFILS Discovery frame in clause 11 and for multi-TID A-MPDU in clause 26 and we were trying to inherit a similar style. We’re open to other options to clarify this aspect as well.

For example, in 11.21.6.4.3.3 and 11.21.6.4.4.2, you mentioned that for equal or less than 160 MHz, Trigger frame, Ranging NDP-A frame, LMR frame shall not be transmitted in an EHT PPDU.

What about UHR and UHR+ PPDU? Do we need to update this text when there is new amendment?

YS> It depends on whether UHR(+) PPDU can provide compelling benefits for <= 160 MHz. EHT PPDU doesn’t look to providing compelling benefits in these cases, which is why we’re trying to simplify the possible combinations.

 

 

And the following text is not necessary as we discussed during the F2F meeting.

The 320 MHz bandwidth of the Ranging NDP Announcement frame shall be indicated based on rules in 17.3.5.2 (SERVICE field) if the frame is transmitted in a non-HT Duplicate PPDU or based on rules in Table 36-28 (U-SIG field of an EHT MU PPDU) if the frame is transmitted in an EHT MU PPDU. 

YS> we’ve deleted the text the group thought was not necessary. The intention of this new text is to reflect the motion text, and more important, to provide references on how to find 320 MHz indication for NDPA. Otherwise, it’s hard to find the related info. If you’re still concerned about this, an alternative I could think of is to convert this to a note.

 

Best regards,

Wook Bong Lee

 



On Mar 28, 2023, at 1:40 PM, Yanjun Sun <yanjuns@xxxxxxxxxxxxxxxx> wrote:

 

Hi Jonathan, 

 

Could you help add 390r1 (PDT on NDPA) to the queue? We’re updating the PDT based on inputs from the march meeting and will upload it later this week. It’ll need ~45 min.

 

Thanks

Yanjun

 

From: Segev, Jonathan <jonathan.segev@xxxxxxxxx> 
Sent: Tuesday, March 28, 2023 12:47 PM
To: STDS-802-11-TGBK@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBK] TGbk Apr. 4th Telecon - Call for submissions

 

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Hello all,

 

  1. TGbk is scheduled to meet Apr. 4th 10:00 am PT / 13:00 ET.

 

  1. This is a call for submissions, if you have a submission and would like to allocate agenda time please let me know

the DCN and the topic.

 

  1. Note that teleconferences are bounded by the conditions stipulated by the documentation below.

Please review and bring up any questions/concerns you may have before proceeding with the teleconference:

 

 Best Regards,

Jonathan Segev,

Cell (WhatsApp): +1-408-203-3337

 

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

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

 

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