Hi Dr. Zhou and Brian
Thanks for your further response. As we discussed in the TTT Group, the control frame already contains RA field and AP ID, and the implementation can well handle such case. We have carefully evaluated the proposal to add a following note (e.g., "If the same AP ID is assigned...") to the AP ID section.
A value that is currently allocated as AID, AP ID or RSID to a STA shall not be assigned by the AP or by its affiliated MLD to any other STA.
NOTE 1—The STA is an associated non-AP STA, an unassociated non-AP STA that has been allocated a (Ranging session Identifier) RSID, any other coordinated AP, or a non-AP MLD that is associated with the AP MLD. (#10828)(#7890)
NOTE 2—The peer AP might obtain the same or different AP IDs from other APs after MAPC negotiations.
NOTE 3— If the same AP ID is assigned to a peer AP by different APs, these different APs can be distinguished by the RA field in NDP frames, trigger frames, and ICF frames.
After careful consideration, we have decided not to include such a note for following reason:
1. In practice, using the RA field to distinguish between different APs is an unambiguous approach. In our proposed resolution, we have further clarified that sharing the same AP ID value will not lead to misinterpretation.
2. Explicitly stating that an AP can distinguish frames by their RA field seems to be unnecessary. Distinguishing between frames by RA field is an inherent capability of an AP.
____________
Some reference for quick understanding:
1. Co-BF
In order to perform a UHR Co-BF sounding, an initiating AP shall transmit a UHR NDP Announcement frame with three or more STA Info fields and the RA field set to the broadcast address. STA Info fields shall only be identified with the AP ID and the AID values corresponding to the responding AP and the non-AP UHR STAs associated with the initiating AP.
Even if an AP has the same AP ID assigned by two different APs , it can distinguish which peer AP is sending the NDP frame by the RA field in the NDP frame.
2. Co-SR
The Co-SR Trigger frame shall include one User Info field that corresponds to the Co-SR coordinated AP. The User Info field shall be set as follows:
— The AID12 field shall be set to the AP ID of the Co-SR coordinated AP, which is assigned by the Co-SR coordinating AP during the MAPC agreement establishment procedure as defined in 37.15.2.2.2 (Co-SR negotiation).
Original
From: PeiZhou <zhoupei36@xxxxxxxxx>
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>;
Date:
2025年10月31日 10:37
Subject: [STDS-802-11-TGBN] 回复: [STDS-802-11-TGBN] AP ID assignment related CIDs
Hi Chun,
Thanks for preparing this CR document.
As we already discussed in the TTT group via email, the “NOTE” can be a guidance to implementers (Brian also has this opinion).
I don’t know why the issue raised by CID 4718, 5091, and 6007 is still rejected. It indeed cause some confusion to readers.
Best regards,
Pei Zhou
TCL
发件人: Chun Huang <huang.chun2@xxxxxxxxxx>
发送时间: 2025年10月31日 10:15
收件人: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: [STDS-802-11-TGBN] AP ID assignment related CIDs
发送时间: 2025年10月31日 10:15
收件人: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: [STDS-802-11-TGBN] AP ID assignment related CIDs
Hi All,
I’ve uploaded document 11-25/1875/r0 for CIDs
4139, 4151, 4152, 4272, 4276, 4277, 4600, 4718, 4772, 5090, 5091, 5281, 5714, 5715, 5743, 5744, 5824, 6007, 7613, 7629, 7784, 7890, 7891, 7893, 8563, 8564, 9290, 9822, 9868, 10828, 10829, 10833, 10834, 10835, 10836, 10837, 10838, 11985, 12075, 12076, 12078
Please review and let me know if you have any questions or comments
黄纯00351826
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1