| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi, Duncan Glad to hear from you. And one more question. According to the description of the latest PDT, BA/SCS renegotiation after ST is the default way to set up the new BA session or the SCS session if the correspond context
transfer failed. But a novel idea come to my mind that the renegotiation procedure can be done in the ST execute stage just like fast BSS transition did. The negotiation parameter can be carried in ST execute request/response. With this way, the ST procedure
will be more smoothly if the context transfer is failed. Cheers Renfang Zhou 发件人: Duncan Ho <dho@xxxxxxxxxxxxxxxx>
Hi Renfang, Thanks for your good comments. I’ll update Part 3 soon to reflect those points you pointed out. BR, Duncan From:
周仁芳 <zhourenfang@xxxxxxxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi, Duncan Thanks for the hard work you have did. I have some questions as below.
1.
Part 3 section 37.9.1, P9, the sentence
“the component of the 802.1X Authenticator in the SMD-ME interacts with an 802.1X Authenticator component in the AP MLD that manages the 802.1X Controlled Port for the non-AP MLD”
seems not clear, I suggest that giving the definition and the responsibility of the component of the 802.1X Authenticator in the SMD-ME and the component of the 802.1X Authenticator in the SMD-ME, and how the interacts? Or give a note/reference to help comprehension
2.
SNouce and ANouce are used to derive a new PTK if the Different PTK mode is used in section 37.9.5.3 of part 3. In my understanding, SNouce shall be included in ST preparation
request, and ANouce shall be included in ST preparation response, maybe both of them can be included in SMD BSS Transition Parameters element, but it was not mentioned in the other place, so, I suggest add ANouce and SNouce in SMD BSS Transition Parameters
element or some other subfield.
3.
Diffie-Hellman Parameter element shall be included optionally in
UHR Link Reconfiguration request/Response, add it in the table 9-658bb and table 9-658bc
4.
Section 37.9.5.3, the new PTK is derived in ST preparation stage if the Different PTK mode is used, but there is no PTK confirm stage(verified the Non-AP MLD and target
AP MLD share the same new PTK), in my understanding, it can be done in ST execution stage, which means the ST execution shall still be protected by the old PTK, and confirm information shall be included in ST execution request/response, if I am correct, new
text shall be add to clarify this. Besides
5.
I suggest adding text to clarify when the new key will be used if the if the Different PTK mode is used Cheers Renfang Zhou 发件人: Duncan Ho <00002b3e54cff3e2-dmarc-request@xxxxxxxxxxxxxxxxx>
Dear Seamless Roaming TTT, I’ve prepared these documents for the ad-hoc meeting next week. Could you please let me know if you have any comments or questions? 25/753r2 PDT MAC on Seamless Roaming
Part 3 (Security) – the r1 was presented before so this is an updated version 25/1020r0 PDT-CR MAC on Seamless
Roaming Part 4 (Emergency roaming) – not presented before 25/1101r0 PDT-CR MAC on Seamless
Roaming Part 5 (Detailed frame formats and signaling) – not presented before Thanks, Duncan 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 |