| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Jay, Thanks for your comments. Good catch about the “renegotiated” part. I’m fine with your suggested text change (with the correct spelling of renegotiated/renegotiation). BR, Duncan From: Jay Yang <yang.zhijie@xxxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Duncan and TTT members, Thanks Duncan for drafting this PDT. Upon reception of the TBD Request frame, the current AP MLD shall: - Transfer the context that is required for resuming operations with the target AP MLD (implementation-specific).
The context that can be transferred is described in 37.x.4 (Contexts). - The current AP MLD may forward any downlink data that is buffered to the target AP MLD [Actual mechanism TBD]. At the time the TBD Response frame is sent, the transfer of the context that is required for resuming operation to the target AP MLD shall be completed. The text of resuming opetions is not clear, and if I remeber correctly, the relevant SP is failure during the not clear text in the SP as well. I suggest we could remove the highlight
sentence for further discussion. Or we could modify the context as bellow: " - Transfer the context that is required for
enabling the operations with the target AP MLD (implementation-specific). The context that can be transferred
or renegocated are described in 37.x.4 (Contexts). - The current AP MLD may forward any downlink data that is buffered to the target AP MLD [Actual mechanism TBD]. At the time the TBD Response frame is sent, the transfer or
regngociation of the context that is required for
enabling the operation to the target AP MLD shall be completed. " Welcome the further comment from you or other TTT memebers. Thanks Best Regards Jay Yang (杨志杰)
Original From: HaoruiYang(Rae) <yanghaorui0217@xxxxxxx> Date: 2024年11月25日
14:30 Subject: Re: [STDS-802-11-TGBN] PDT-MAC-Seamless-Roaming Hi Duncan and TTT members, Thanks Duncan for drafting the PDT. Please find my comment as below: 1. "within the same ESS" --> there is no such agreement based on the passed motions. This also is related to a straw poll still under discussion. So this
should be reworded or removed; 2. "At the time the TBD Response frame is sent, the transfer of the context that is required for resuming operation to the target AP MLD shall be completed."
--> I suggest to change "shall be" to "shall have been" since using "At" requires the the context transfer must be completed at the same time with the response frame is sent. But context transfer can be completed before the response frame is sent. BRs,
Haorui Yang(Rae) ---- Replied Message ----
This is the initial email for: Proposed Draft Text for Seamless Roaming As the PoC for Seamless Roaming, I have created the initial PDT document
11-24-1881r0 for Seamless Roaming. This document includes proposed text based on the motions up to and including the 2024 November IEEE 802 Plenary. We will update the PDT as additional motions are passed. The current version r0 is at a high level. The author list in r0 is based on the 1:1 TTT requests received to me after the TGbn Chair’s guideline to send TTT request
to PoCs. The author list will be updated based on the list of members in the TTT for Seamless Roaming (about 70 members) mentioned in the document by Ross
11-24/1698r12. If you wish to be removed from the TTT or the current (and future) author list, please e-mail me at
dho@xxxxxxxxxxxxxxxx. I will update the author list accordingly in the next revised version (r1). Please send any comments on the draft text (excluding the author list) in 11-24-1881r0
to this e-mail thread. This allows all TTT members to see and discuss your comments, facilitating debate on any changes to the document. This will be our general process for including text in the document. At some point, as the group passes more motions to Seamless Roaming, we will try to find volunteers to create draft text sections
corresponding to those motions. Depending on the size/complexity of that text, it should appear for discussion
within this e-mail thread either as:
We will aim to discuss any new proposed draft text within this thread and reach a super-majority agreement (e.g., 75% of the
TTT membership). However, even 75% is challenging due to the fluid nature of TTT membership. Deciding when to close the debate on new text will be a judgment call, typically when objections reduce to a small number (e.g., less than 25%, or about 15-20 people).
If objections persist, we may need to conduct a straw poll in TGbn and update our document 11-24-1881rx based on the outcome. Future text additions will follow a similar process, aiming for super-majority agreement. Thank you for your cooperation. P.S. credits go to Matthew Fisher/Sanket for the above great model instructions for PDT development. Not much black hair to
save but it’s saved me a ton of time BR, 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 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 |