Re: [STDS-802-11-TGBE] Comments on 11-20-1395-00-00be-pdt-mac-mlo-multi-

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

I think you mean “if … then”, not “if … than”.

From: Akhmetov, Dmitry [mailto:Dmitry.Akhmetov@xxxxxxxxx]
Sent: Tuesday, September 8, 2020 12:54 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] Comments on 11-20-1395-00-00be-pdt-mac-mlo-multi-link-channel-access-general-non-str

Hi Matt,

The confusion basically came from order of words/emphasis of certain words in a sentence.

I guess this minor editorial change of “except that the STA is NSTR limited” to “except for the condition " the STA is not NSTR limited” would clear possible confusion

From the point of format logic everything is fine:

Old text:

If (NAV==IDLE && CCA==IDLE) than

shall send CTS

Done

New text:

If (NAV==IDLE && CCA==IDLE && STA!=NSTR) THAN

shall send CTS

if (NAV==IDLE && CCA==IDLE && !(STA!=NSTR)) THAN

may send CTS

Done

Now, assume STA is STR device, i.e. STA variable has STR value

So first condition (paragraph with non NSTR part) is:

(NAV==IDLE && CCA=IDLE && STR!=NSTR ) -> TRUE && TRUE && TRUE -> TRUE -> in case of STR device we send CTS

Second one (extra text you are proposing with “if all conditions except…”)

(NAV==IDLE && CCA==IDLE && !(STR!=NSTR) -> TRUE && TRUE && !(TRUE) -> TRUE && TRUE && FALSE -> FALSE -> second “paragraph” part not executed

Now, assume STA is NSTR device

NSTR!=NSTR -> FALSE -> first paragraph not executed

!(NSTR!=NSTR)->!(FALSE) -> TRUE -> may send CTS

From: Matthew Fischer <matthew.fischer@xxxxxxxxxxxx>
Sent: Friday, September 04, 2020 6:45 PM
To: Akhmetov, Dmitry <Dmitry.Akhmetov@xxxxxxxxx>
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] Comments on 11-20-1395-00-00be-pdt-mac-mlo-multi-link-channel-access-general-non-str

Dmitry,

On 1) - I understand the reason for your different interpretation.

Maybe it would be better as:

If all of the conditions of the previous paragraph are met, except for "the STA is not NSTR limited"

Would that make it more clear?

Or even more explicitly:

If all of the conditions of the previous paragraph are met, except for the condition "the STA is not NSTR limited"

On Fri, Sep 4, 2020 at 6:35 PM Matthew Fischer <matthew.fischer@xxxxxxxxxxxx> wrote:

Dmitry,

1)

link set should be describable as a set of links rather than a pair - there is no reason to limit it to only 2 links

and yes, the assumption is that all links in the set are NSTR to each other - I thought about whether any asymmetry could exist and it seemed pretty implausible to me

2)

on the CTS response extra condition - you're not reading it correctly

if says, if all of the conditions of the preceding paragraph are met EXCEPT - so you have to reread it as - the only condition that failed in the paragraph was that the STA was NSTR limited

if that is true, then it cannot be the case that an STR STA reaches this point

Matthew Fischer

Nice Guy

Broadcom Inc.

+1 408 543 3370 office
On Fri, Sep 4, 2020 at 6:15 PM Akhmetov, Dmitry <Dmitry.Akhmetov@xxxxxxxxx> wrote:
Hi Matt,

Please find my comments attached

From: Matthew Fischer <00000959766b2ff5-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Friday, September 04, 2020 4:54 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] Comments on 11-20-1395-00-00be-pdt-mac-mlo-multi-link-channel-access-general-non-str

Hello,

I've made a small addition.

I've added another AP should not transmit to an NSTR MLD in the case of when the AP might be able to determine that some STA of the NSTR MLD is actively transmitting to anybody else (i.e. currently, it only mentions transmitting to the AP, because that's easy for the AP to figure out) but it is possible that maybe the AP can see the non-AP transmitting for example, a P2P on a link and the AP might be able to decode the EHT PPDU header AID and Color or something in the MAC header that tells it that this is a TX by the non-AP MLD and if it can do that, then again, the AP should not TX to that NSTR non-AP MLD - so this new should not applies only when the AP is able to make that determination.

https://mentor.ieee.org/802.11/documents?is_dcn=1395&is_group=00be

Matthew Fischer

Nice Guy

Broadcom Inc.

+1 408 543 3370 office
On Thu, Sep 3, 2020 at 6:35 PM 김상현 <shk0787@xxxxxxxxx> wrote:
Dear Matthew and Kaiying,

I saw R2, and it seems to reflect SFD well.

Thank you for your hard work.

Best Regard,

Sanghyun Kim

Sanghyun Kim, Ph.D
WILUS Inc.
5th Fl., 216 Hwangsaeul-ro Bundang-gu,
Seongnam-si Gyeonggi-do 13595, Korea
T +82 31 712 0523
www.wilusgroup.com

-----Original Message-----
From: "Kaiying Lu"<Kaiying.Lu@xxxxxxxxxxxx>
To: <STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx>;
Cc:
Sent: 2020-09-04 (금) 03:41:52 (GMT+09:00)
Subject: Re: [STDS-802-11-TGBE] Comments on 11-20-1395-00-00be-pdt-mac-mlo-multi-link-channel-access-general-non-str

Hi Matt and Sanghyun,

I agree with Sanghyun’s comment. The SFD gave the condition on which the responder is allowed to make a choice. But the condition is that the another STA affiliated with the NSTR MLD is participating an TXOP on that link. Without this condition, the NSTR responder shall respond CTS if NAV is idle on this link.

I think the draft text should reflect this condition.

Thanks,

Kaiying

From: Matthew Fischer [mailto:00000959766b2ff5-dmarc-request@xxxxxxxxxxxxxxxxx]
Sent: Thursday, September 3, 2020 11:00 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] Comments on 11-20-1395-00-00be-pdt-mac-mlo-multi-link-channel-access-general-non-str

Sanghyun,

1)

missing "." added

2)

your comment:

text does not cover “the STA may not respond with a CTS frame." of the SFD. (We need some “may” for a STA with NSTR contrained)

the SFD text bothers me

a. I agree that the SFD says "may" not respond, which appears to allow for the responder to make a choice

b. I agree that doc 1395r0 does not provide a choice to the responder, but instead, always dictates, depending on conditions, that there either shall or shall not be a CTS

When reading the SFD, I assumed that the language was imprecise.

I will create a version which provides the choice as an alternative, assuming that the SFD expresses exactly what the body desired, i.e. that the responder has a choice.

That will be version r2

Matthew Fischer

Nice Guy

Broadcom Inc.

+1 408 543 3370 office

On Wed, Sep 2, 2020 at 10:59 PM 김상현 <shk0787@xxxxxxxxx> wrote:

Dear Matthew,

Thanks for preparing the text.

Please find attached comments.



Best Regards,

Sanghyun Kim

Sanghyun Kim, Ph.D
WILUS Inc.
5th Fl., 216 Hwangsaeul-ro Bundang-gu,
Seongnam-si Gyeonggi-do 13595, Korea
T +82 31 712 0523
www.wilusgroup.com

-----Original Message-----
From: "Liuming Lu"<lu.liuming@xxxxxxxxxx>
To: <STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx>;
Cc:
Sent: 2020-09-03 (목) 11:26:26 (GMT+09:00)
Subject: [STDS-802-11-TGBE] Comments on 11-20-1395-00-00be-pdt-mac-mlo-multi-link-channel-access-general-non-str

Hi Matthew,

Thanks for the preparation for the pdt-mac-mlo-multi-link-channel-access-general-non-str.

I have some comments. Please see the attached file.

Best Regards,

Liuming Lu

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
*********** MEDIATEK Confidentiality Notice ***********
The information contained in this e-mail message (including any 
attachments) may be confidential, proprietary, privileged, or 
otherwise exempt from disclosure under applicable laws. It is 
intended to be conveyed only to the designated recipient(s). Any 
use, dissemination, distribution, printing, retaining or copying 
of this e-mail (including its attachments) by unintended recipient(s) 
is strictly prohibited and may be unlawful. If you are not an 
intended recipient of this e-mail, or believe that you have received 
this e-mail in error, please notify the sender immediately 
(by replying to this e-mail), delete any and all copies of this 
e-mail (including any attachments) from your system, and do not 
disclose the content of this e-mail to any other person. Thank you!
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

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