| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Dear Abhi, Thank you for your hard work.
I have one comment. I think that the MLD MAC address should not be optional and should always be present in beacons and ML probe responses.
This is because that a MLD receiving the beacon or ML probe responses should have a record name or identifier for any AP MLD information received through beacons and ML probe responses.
In legacy beacons and probe responses, the MAC address of the transmitting AP is used to identify any BSSdescriptionset obtained by a receiving STA. I think the MLD MAC address should be used to identify the MLD, rather than the AP MAC address transmitting
the beacon or ML probe responses. Please let me know of your thoughts. Best regards, Xiaofei Clement Wang Principal Engineer | InterDigital T: (631)
622.4028 From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx> Hi Payam,
I have embedded my responses in the attached file. Could you please take a look? Regarding Link ID field: This is field is needed (and hence placed as the first field) in each per-STA profile so that a receiving STA can associate a per-STA profile to a particular
link. Without this indication, the receiver has no way to map a profile to a link. Additional thoughts embedded in the attached doc. The “Number of Supported Links” subfield was removed based on the discuss during the last call. I will be posting an r6 shortly. It incorporates many of your suggested edits. Regards, From: Payam Torab <torab@xxxxxxxx>
CAUTION: This email originated from outside of
the organization. Hi Abhi/all -- I don’t know where 1274 is as far as SP/motion (may be behind). Few comments/suggestions attached. Most important comments are “Link ID” field in ML IE, which doesn’t have a supporting motion as far as I could find, and “Number of Supported Links”, which it seems to me could be simply the number of Per-STA Profile
subelements present (discussed why in the document). Thanks, Payam From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx> Hi All, A revised version (r5) has been posted: https://mentor.ieee.org/802.11/dcn/20/11-20-1274-05-00be-mac-pdt-mlo-ml-ie-structure.docx In this revision, text in
‘33.x.y.z.1 (General)’ and ‘33.x.y.z.2 (Complete or partial per-STA profile)’ has been simplified based on offline feedback. Regards, From: Abhishek Patil Hi All,
https://mentor.ieee.org/802.11/dcn/20/11-20-1274-04-00be-mac-pdt-mlo-ml-ie-structure.docx I have not covered inclusion of ML IE in Authentication frame since I couldn’t find a motion to support it.
Although I feel ML IE would be the right container to carry MLD MAC addr. Regards, From: Yang, Zhijie (NSB - CN/Shanghai) <zhijie.yang@xxxxxxxxxxxxxxx>
CAUTION: This email originated from outside of
the organization. Hi Arbi, Yonghoon, Larent, Jarkko, I see we have same concern on the ML IE carried in Beacon, Probe RESP, Auth REQ& RESP frame. Could we talk it through this mail loop other than make a lot comment in the document? It will be higher efficient.
As you know, non-AP MLD may perform active scan and passive scan to find AP SSID (or perform special scan to find the hidden SSID), and STA only can find AP by receiving Beacon frame in passive scan mode. I think it’s necessary
to carry ML IE in Beacon frame so that non-AP MLD can distinguish the pre-11be AP from 11be AP. If the non-AP MLD detect the AP MLD with the Beacon frame, non-AP MLD will sent out Auth REQ frame carrying MLD MAC address to AP MLD to set up the connection.
Whether ML IE is mandatory carried in probe response frame is decided how we design the probe request behavior on non-AP MLD side. If we thought non-AP MLD should send out a general scan/normal probe request to
gather pre-11be AP SSID, and then sent out a MLD scan/MLD probe request to gather 11be AP SSID, It’s fine that ML IE is only carried in probe response with which AP MLD reply to the MLD scan. I think Laurent will agree with it since he did a lot of hard work on the will-design of MLD probe request format. But I think it will be more efficient that non-AP MLD can find AP MLD through normal scan/ general probe request other than separate it into two different kinds of scan type. ML IE shall be carried in probe response
from this perspective. Anyway, it’s decided by the group, I think we could set it TBD at present.
According to the following motion, MLD MAC address should be carried in Auth frame, and I think ML IE is the best place to carry MLD MAC address, so I think ML IE should be carried in Auth frame. Do we have other better option to
make it? I guess Yonghong’s concern is where is the better place to show this, in Arbi’s doc or Insun’s doc, correct? If so, I don’t have a clear idea on this. I see the same _expression_ in Insun’s doc(1300/r5.) [Motion 115, #SP89] An Authentication frame transmitted by an STA affiliated with an MLD shall include its
MLD MAC address in a Multi-Link element
carried in the Authentication frame. 20/0387r3 (Multi-link setup follow up II, Po-Kai Huang, Intel) SP#2 Do you support the following?
Approved with unanimous consent Straw poll #89
[#SP89] Thanks Best Regards Jay Yang From: Young Hoon Kwon <younghoon.kwon@xxxxxxx>
Hi Abhi, I have some comments on the text as attached. Thanks, Young Hoon From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
Caution: EXT Email
Hi All,
https://mentor.ieee.org/802.11/dcn/20/11-20-1274-03-00be-mac-pdt-mlo-ml-ie-structure.docx Regards, Abhi From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
Hi All, I’ve posted r2 which incorporates feedback from Laurent and Jay. https://mentor.ieee.org/802.11/dcn/20/11-20-1274-02-00be-mac-pdt-mlo-ml-ie-structure.docx Regards, From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
CAUTION: This email originated from outside of
the organization. Hi All, I have revised my PDT doc (on ML IE) based on feedback received so far.
https://mentor.ieee.org/802.11/dcn/20/11-20-1274-01-00be-mac-pdt-mlo-ml-ie-structure.docx Could you please review and let me know if you have any further inputs? Regards, Abhi From: Abhishek Patil Hello to all TTT members for MLO Discovery: ML IE Structure, I have posted document 11-20/1274 which provides draft text for MLO power save procedures. https://mentor.ieee.org/802.11/dcn/20/11-20-1274-00-00be-mac-pdt-mlo-ml-ie-structure.docx Could you please review and let me know if you have any inputs? Regards, 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 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 |