Re: [STDS-802-11-TGBE] CID 18240: elements not carried in a per-STA profile

[Thomas Derham <00000ad2eabc2931-dmarc-request@xxxxxxxxxxxxxxxxx>]

I see, thanks Abhi.

In that case, a few that come to mind are:

• QoS Map element (sent in (Re)Association Response; used to specify table for mapping DSCP to UP by non-AP STA so this is applied at or above MLD layer)
• Supported Operating Classes element (sent in (Re)Association Request etc; used to specify supported opclasses across all radio resources of the device, aka MLD in this context)
• It looks like FT elements (e.g. Mobility Domain) are already specified in the list in that subclause, however I suspect the FILS elements (in bcn/prb, assoc req/resp) should also be included for similar reasons

I think it would also be good to explicitly mention the criteria/reasoning for elements being on this list, so that when we need to update the list in later amendments, we don’t make mistakes.

On the face of it, it seems elements related to MLD-level features seems to be the basic criteria, however (as mentioned in the note in that subclause) security is an MLD level feature yet there can be differences in RSNE on different links, so it seems that simple logic doesn’t always hold up…

Thanks

Thomas

On May 13, 2023 at 8:31:11 PM, Abhishek Patil <appatil@xxxxxxxxxxxxxxxx> wrote:

Hi Thomas,

This would apply only to the frames that carry Basic ML IE carrying a profile of a reported STA. In other words, it applies to the content of the Per-STA Profile subelement carried within the Basic ML IE contained in a Beacon, Probe Req/Resp, (Re)Assoc Req/Resp or Authentication frames.

 

Regards,
Abhi

 

From: Thomas Derham <thomas.derham@xxxxxxxxxxxx>
Sent: Friday, May 12, 2023 1:31 PM
To: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
Cc: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] CID 18240: elements not carried in a per-STA profile

 

Thanks Abhi.

 

What is the scope of this list? I think there’s a large number of elements in 9.4.2 that related to MLD-level features - do we need to include all of them in this list or only elements that are carried in certain frames?

 

For the example in the CID below, MSCS Descriptor is either carried in (MSCS) action frames or in (Re)Association requests. On the other hand, SCS Descriptor is only carried in (SCS) action frames.

 

Thanks

Thomas

 

 

On May 12, 2023 at 12:12:06 PM, Abhishek Patil <appatil@xxxxxxxxxxxxxxxx> wrote:

Hi All,

During today’s TGbe MAC ad-hoc (AM2 session), I deferred CID 18240 so that the group could discuss and add any other missing elements that cannot be carried within a Per STA Profile of a reported STA. This email is to solicit the group’s inputs on the topic. Could you please let me know if there are additional elements that you believe need to be listed in clause 35.3.3.4?

18240

Li-Hsiang Sun

35.3.3.4

484.60

MSCS descriptor element should not be included in Per-STA profile subelement b/c (1) it is a MLD level feature. (2) the value should be the same for all links so by inheritance it would not appear in per-STA profile

add MSCS descriptor element to the list of elements not included in the per-STA profile All STAs affliated with a MLD shall set Mirrored SCS in Extended Capabilities element to the same value

FYI, we can include any missing elements as a resolution to CID 18240.

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

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature