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

Re: [STDS-802-11-TGBE] CID 11138 in doc 11-22/1978



Thanks Subir!

 

From: Subir Das <subirdas21@xxxxxxxxx>
Sent: Wednesday, January 11, 2023 2:02 PM
To: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] CID 11138 in doc 11-22/1978

 

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

Hi Abhi,

Thanks for addressing the comments. I do agree with them.

 

-Subir 

 

 

 

On Mon, Jan 9, 2023 at 11:22 PM Abhishek Patil <appatil@xxxxxxxxxxxxxxxx> wrote:

Hi Subir,


Thank you for your email and suggestions.

 

Does EPCS make use of Basic ML IE along with Priority Access ML IE? If not, we don’t need to add reference to 35.16 for Basic ML IE.

I have added reference to 35.16 under 9.4.2.312.6 (see below):

 

 

I have updated the text based on your suggestion for MLD MAC Address field for other variants of ML IE:

 

 

Please let me know if you have additional feedback.

 

Regards,
Abhi

 

 

From: Subir Das <subirdas21@xxxxxxxxx>
Sent: Monday, January 9, 2023 9:26 AM
To: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] CID 11138 in doc 11-22/1978

 

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

Hi Abhi,

Thanks for your analysis. I agree with you on adding a reference to clause 35.16 (under Priority Access variant) for conditions when the (MU) EDCA Parameter Set elements are included in the STA Profile field.

 Don't you also need  to add clause 35.16 reference to the following section? 

 

9.4.2.312.2.4  Link Info field of the Basic Multi-Link element

TGbe editor: Please update the contents of the following paragraph in this subclause as shown below:

The contents of the STA Profile field are determined based on whether the Per-STA Profile subelement carries complete or partial profile. When carrying partial profile, the contents of the STA Profile field depend on the elements requested by a non-AP MLD (see 35.3.4.2) or if the reported AP is advertising certain elements (see 35.3.11). When carrying complete profile, the contents of the STA Profile field are subject to rules are defined in 35.3.3.3 (Advertisement of complete or partial per-link information).

 

 

Another point regarding your update on the following:

 

9.4.2.312.2.3 Common Info field of the Basic Multi-Link element

TGbe editor: Please update the following paragraph in this subclause as shown below:

The MLD MAC Address subfield specifies the MAC Address of the MLD with which the STA transmitting the Basic Multi-Link element is affiliated.If the transmitting STA is a non-AP STA or is an AP that does not belong to a multiple BSSID set or is an AP corresponding to a transmitted BSSID in a multiple BSSID set, then the MLD MAC Address subfield specifies the MAC Address of the MLD with which the STA transmitting the Basic Multi-Link element is affiliated with. If the AP MLD described by the Basic Multi-Link element is affiliated with an AP corresponding to a nontransmitted BSSID in the same multiple BSSID set as the AP transmitting the frame carrying the Basic Multi-Link element, then the MLD MAC Address subfield specifies the MAC Address of the AP MLD.

 

If you look at Clause 9.4.2.312.6 Priority Access Multi-Link element, I  am wondering if we need to update the following language based on your above update.

 

"The AP MLD MAC Address subfield specifies the MAC Address of the AP MLD which the AP transmitting the Priority Access Multi-Link element is affiliated with."  

 

regards, 

_Subir 

 

 

On Fri, Jan 6, 2023 at 12:28 PM Abhishek Patil <appatil@xxxxxxxxxxxxxxxx> wrote:

Hi Subir, All,

 

During yesterday's TGbe MAC call, we discussed resolution for CID 11138 in doc 11-22/1978. The comment was related to the description of the STA Profile field of Basic Multi-Link element.

 

Subir suggested to check if other variants of Multi-Link element need similar change to the description of STA Profile field.

 

My conclusion is that we don’t need any further changes. Here’s a brief summary of my analysis:

In the current draft, only Probe Request and Priority Access variant of Multi-Link element can have STA Profile field. The description text for STA Profile field for Probe Request and Priority Access variant is sufficiently detailed in describing the format (and contents) of the field under different conditions. Therefore, we don’t need further changes. The only addition we could consider is to make reference to clause 35.16 (under Priority Access variant) for conditions when the (MU) EDCA Parameter Set elements are included in the STA Profile field.

 

I’ve included snippets of the description for the two variants for your reference.

 

Description of STA Profile field in Probe Request Multi-Link element:

 

Description of STA Profile field in Priority Access Multi-Link element:

 

Could you please let me know if you agree with my analysis and/or if you have other suggestions?

 

Regards,
Abhi

 

 


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