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

Re: [STDS-802-11-TGBF] Announcement: Additional TGbf Teleconference for March - May 2023



Hi Mike,

 

Thanks for comment.

For your first point, I believe that’s 11az’s text and behavior.  If it’s incorrect, it should be modified either in 11az or 11me. I don’t want to change that in 11bf. In 11bf, I didn’t add any PV1 stuff for sensing frames.

For your second point, you’re true. It’s a good catch. I’ll add the missing part. I guess that’s because 11az D7.0 write two paragraph there so I missed it by mistake.

For your last point, I think that’s the way how 11az did that exception: add exceptions in item c) and d), then add item e) to handle the exceptions. If you have a better idea to restructure it, please suggest.

I do see 11me has merged the original item c) and d) into one. But since that does not merge 11az’s text yet, so I’d rather like use 11az’s text as the base. Anyway when 11me merge 11az, the modification will be done, 11bf could be merged the same way thereafter.

 

BR,

Chaoming

 

发件人: stds-802-11-tgbf@xxxxxxxxxxxxxxxxx <stds-802-11-tgbf@xxxxxxxxxxxxxxxxx> 代表 M Montemurro
发送时间: 2023322 22:06
收件人: 罗朝明(Chaoming Luo) <luochaoming@xxxxxxxx>; STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGBF] Announcement: Additional TGbf Teleconference for March - May 2023

 

Hi Chaoming,

 

I reviewed your security comment resolutions for LB 272 and the resolutions for CIDs 2263 and 2265 are not correct. First of all, PV1 frames do not have a ToDS field and QMF cannot be supported (there are text changes in REVme D3.0 to improve this wording). Secondly in the baseline, there is a sentence "The QMF receiver shall use...." in the baseline that is somehow missing from the 11bf draft. And finally, moving the "excepted" text after the requirement for maintaining replay counters makes the entire description open to interpretation. 

 

I have no issues with calling out behavior for sensing, but the description needs to be restructured to be clearer. 

 

Also note that this subclause has been significantly changed by REVme in LB270 CIDs 3573 and 3574. 

 

Cheers,

 

Mike

 

On Tue, Mar 21, 2023 at 10:32 PM 罗朝明(Chaoming Luo) <000015d97e832564-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:

Hi Tony,

 

Please also help add the following to the queue, thanks!

23/508r0,  lb272-misc-security, around 20min

 

BR,

Chaoming

 

发件人: stds-802-11-tgbf@xxxxxxxxxxxxxxxxx <stds-802-11-tgbf@xxxxxxxxxxxxxxxxx> 代表 Hanxiao (Tony, WT Lab)
发送时间: 2023322 10:18
收件人: Chen, Cheng <cheng.chen@xxxxxxxxx>; STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
主题: 答复: Announcement: Additional TGbf Teleconference for March - May 2023

 

Hi Cheng and all,

         I already asked the officer to fix the error in the website, please check again.

         Thank you for carefully checkingJ

 

Best Regards : )

Tony Xiao Han

 

发件人: Chen, Cheng [mailto:cheng.chen@xxxxxxxxx]
发送时间: 2023321 22:53
收件人: Hanxiao (Tony, WT Lab) <tony.hanxiao@xxxxxxxxxx>; STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
主题: RE: Announcement: Additional TGbf Teleconference for March - May 2023

 

Hi Tony,

 

May I confirm what is the correct time for our Thursday meeting? Below it shows it should be 11pm ET, but what I found at IEEE 802.11 website is 12pm ET. See below.

 

 

 

Best,

Cheng

 

From: Hanxiao (Tony, WT Lab) <0000177ab8f731c4-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, March 9, 2023 10:20 PM
To: STDS-802-11@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11] Announcement: Additional TGbf Teleconference for March - May 2023

 

--- This message came from the IEEE 802.11 Working Group Reflector ---

Dear all,

I am announcing additional teleconferences for TGbf (Please carefully check the slots with different color, easy to be confused J ):

 

·        March      23   (Thursday),   2300 - 01:00 ET

 

·        March      27   (Monday),     1000 - 12:00 ET

·        March      28   (Tuesday),    1000 - 12:00 ET

 

·        April        6     (Thursday),   2300 - 01:00 ET

 

·        April        11   (Tuesday),    1000 - 12:00 ET

·        April        13   (Thursday),   2300 - 01:00 ET

 

·        April        18   (Tuesday),    1000 - 12:00 ET

·        April        20   (Thursday),   2300 - 01:00 ET

 

·        April        24   (Monday),     1000 - 12:00 ET

·        April        25   (Tuesday),    1000 - 12:00 ET

 

·        May         4     (Thursday),   2300 - 01:00 ET

 

 

·        May        8     (Monday),     1000 - 12:00 ET

·        May        9     (Tuesday),    1000 - 12:00 ET

 

Best Regards : )

Tony Xiao Han


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


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


OPPO


本电子邮件及其附件含有OPPO公司的保密信息,仅限于邮件指明的收件人(包含个人及群组)使用。禁止任何人在未经授权的情况下以任何形式使用。如果您错收了本邮件,切勿传播、分发、复制、印刷或使用本邮件之任何部分或其所载之任何内容,并请立即以电子邮件通知发件人并删除本邮件及其附件。
网络通讯固有缺陷可能导致邮件被截留、修改、丢失、破坏或包含计算机病毒等不安全情况,OPPO对此类错误或遗漏而引致之任何损失概不承担责任并保留与本邮件相关之一切权利。
除非明确说明,本邮件及其附件无意作为在任何国家或地区之要约、招揽或承诺,亦无意作为任何交易或合同之正式确认。
发件人、其所属机构或所属机构之关联机构或任何上述机构之股东、董事、高级管理人员、员工或其他任何人(以下称“发件人”或“OPPO”)不因本邮件之误送而放弃其所享之任何权利,亦不对因故意或过失使用该等信息而引发或可能引发的损失承担任何责任。
文化差异披露:因全球文化差异影响,单纯以YES\OK或其他简单词汇的回复并不构成发件人对任何交易或合同之正式确认或接受,请与发件人再次确认以获得明确书面意见。发件人不对任何受文化差异影响而导致故意或错误使用该等信息所造成的任何直接或间接损害承担责任。

This e-mail and its attachments contain confidential information from OPPO, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you are not the intended recipient, please do not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message.
Electronic communications may contain computer viruses or other defects inherently, may not be accurately and/or timely transmitted to other systems, or may be intercepted, modified ,delayed, deleted or interfered. OPPO shall not be liable for any damages that arise or may arise from such matter and reserves all rights in connection with the email.
Unless expressly stated, this e-mail and its attachments are provided without any warranty, acceptance or promise of any kind in any country or region, nor constitute a formal confirmation or acceptance of any transaction or contract.
The sender, together with its affiliates or any shareholder, director, officer, employee or any other person of any such institution (hereinafter referred to as "sender" or "OPPO") does not waive any rights and shall not be liable for any damages that arise or may arise from the intentional or negligent use of such information.
Cultural Differences Disclosure: Due to global cultural differences, any reply with only YES\OK or other simple words does not constitute any confirmation or acceptance of any transaction or contract, please confirm with the sender again to ensure clear opinion in written form. The sender shall not be responsible for any direct or indirect damages resulting from the intentional or misuse of such information.


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


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


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