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

Re: [STDS-802-11-TGBE] [Suspected Marketing Mail] [STDS-802-11-TGBE] [CR-MAC] Feedback Requested for CRs on Basic variant ML element (Clause 9)



Hi Gaurang,

 

Got it, thanks for the clarification.

 

Thanks

 

Best Regards

 

Jay Yang

 

From: Gaurang Naik <gnaik@xxxxxxxxxxxxxxxx>
Sent: 2021
48 11:55
To: Yang, Zhijie (NSB - CN/Shanghai) <zhijie.yang@xxxxxxxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: RE: [Suspected Marketing Mail] [STDS-802-11-TGBE] [CR-MAC] Feedback Requested for CRs on Basic variant ML element (Clause 9)

 

Hello Jay,

 

Thank you very much for reviewing the CR document.

 

Regarding your question, if there a channel switch on a link, the Link ID *will not* change. Pls refer to the text below from 35.3.4.4 of D0.4 (page 197, line 8):

An AP of an AP MLD shall have a unique link ID that shall not change during the lifetime of the AP MLD.

 

Let us assume that an AP MLD has three links. The mapping will be something link this:

Link ID                  Tuple

0                              <Cl_1, Ch_1, BSSID_1>

1                              <Cl_2, Ch_2, BSSID_2>

2                              <Cl_3, Ch_3, BSSID_3>  

 

Now, let us say the channel on link 0 changes from <Cl_1, Ch_1> to <Cl_4, Ch_4>, the new mapping will be:

Link ID                  Tuple

0                              <Cl_4, Ch_4, BSSID_1>

1                              <Cl_2, Ch_2, BSSID_2>

2                              <Cl_3, Ch_3, BSSID_3>

 

So, the Link ID will not change. Only the tuple value will change. Link ID 0 will now map to the tuple <Cl_4, Ch_4, BSSID_1>.

 

The relationship between the Link ID and the <class, channel, BSSID> tuple was specified in Motion 124, SP 186. Pls see the text below. The note simply captures the motion.

Please let me know if that answers your question.

 

Thanks,

Gaurang

 

From: Yang, Zhijie (NSB - CN/Shanghai) <zhijie.yang@xxxxxxxxxxxxxxx>
Sent: Wednesday, April 7, 2021 8:09 PM
To: Gaurang Naik <gnaik@xxxxxxxxxxxxxxxx>; STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [EXT] RE: [Suspected Marketing Mail] [STDS-802-11-TGBE] [CR-MAC] Feedback Requested for CRs on Basic variant ML element (Clause 9)

 

Hi Gaurang,

 

Thanks for the PDT.

 

For following sentence, as you mentioned, The Link ID is unique value to identify every AP within the AP MLD. But if the AP switches the working channel, it means the Operating class and channel are also changed accordingly. Seems it’s not correct to tie the Link ID to the tuple<class, channel, BSSID>. Or do you mean the Link ID also can be changed?

 

 

[CID 3127]NOTE ? The Link ID of an AP affiliated with an AP MLD is a representation of the tuple consisting of Operating Class, Operating Channel, and BSSID of the AP affiliated with the AP MLD. The Link ID is unique to every AP affiliated with an AP MLD.

 

Thanks

 

Best Regards

 

Jay Yang

 

From: Gaurang Naik <gnaik@xxxxxxxxxxxxxxxx>
Sent: 2021327 0:53
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [Suspected Marketing Mail] [STDS-802-11-TGBE] [CR-MAC] Feedback Requested for CRs on Basic variant ML element (Clause 9)

 

Hello all,

 

I have prepared the CR document 11-21/0506r0 that addresses the following CIDs:

2159, 2161, 3018, 1908, 3019, 2587, 1906, 1907, 1776, 3127, 2436

 

The comments are related to the Basic variant Multi-Link element text in Clause 9.

 

Could you kindly take a look and provide your feedback? Any feedback is appreciated.

 

Thanks,

Gaurang


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