| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Mike, thank you for your feedback. In fact, I’ve prepared two options. The other CR document is
11-25/2016r1, which describes a solution where the Target AP MLD queries the old PTK from the SMD-ME based on the PTK Name and then derives the new PTK. I suggest you review 11-25/2016 as well — its concept should be closer to your idea.
I don’t have a strong preference between the two options; what I’d like to do is to improve the process description in the current Draft to make the overall procedure easier to understand. Thanks, Xuwen Zhao TCL 发件人: M Montemurro <montemurro.michael@xxxxxxxxx>
Hello Zhao Xuwen, I reviewed the changes and in my opinion, the information that you are looking to include would be in the scope of the PTK, not the PMK. The reason is because in any of these transitions, the non-AP MLD is associated
to the SMD-ME. The PTK is the key resulting from this association (a PMK, or PMK-R1 in the case of FT, can be cached for subsequent associations). The PMK or PMKID do not need to be able to be transmitted from the SMD-ME to the target AP MLD. It could be that we derive the following: - For shared PTK, a PTKName - For per-MLD PTK, a PTKName associated with the per-AP MLD PTK. Thanks, Mike On Wed, Nov 5, 2025 at 10:17 PM Zhao Xuwen <zhaoxuwen123@xxxxxxxxxxx> wrote:
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 |