Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-11-TGBN] PDT-MAC-Seamless-Roaming



Hi Jay,

 

Thanks for your comment and I agree that the current Motions indeed do not mandate the Response to be from the current AP MLD. Let me remove the “current AP MLD” and reword the sentence then.

 

BR,

Duncan

 

From: Jay Yang <yang.zhijie@xxxxxxxxxx>
Sent: Saturday, December 14, 2024 4:56 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] PDT-MAC-Seamless-Roaming

 

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 your efforts.

 

Regarding the following highlight sentence, it's reasonable if the DS mapping change is made by the target AP MLD , and thus the target AP MLD shall send the Response frame. Not sure why you think the response frame is sent by the current AP MLD ?

 

After receiving the TBD Request frame:

The current AP MLD shall transfer the context that is required for enabling operations with the target AP MLD .. The context that can be transferred or renegotiated is defined in 37.12.4 (Contexts).

The current AP MLD may forward to the target AP MLD any pending individually addressed downlink data that are intended for the non-AP MLD that initiated Seamless Transition [Actual mechanism TBD ].

The current AP MLD shall send a TBD Response frame to the non-AP MLD after the transfer or renegotiation of the context is completed.

 

 

 

 

 

Thanks

 

Best Regards

 

Jay Yang (杨志杰)

 

 

Original

Date: 20241214 12:59

Subject: Re: [STDS-802-11-TGBN] PDT-MAC-Seamless-Roaming

Dear Seamless Roaming TTT members,

 

Thanks Mark, Binita , John, and Mike for all your good comments! I’ve addressed them in the attached files “…-mgr+DH” and “_bg_JRW-mm+DH”. For the comments that I’ve accepted, I marked them “resolved” so they are hidden. For those comments that need more explanation and/or discussion, I’ve embedded my responses.

 

All the changes are implemented in the attached v5 of the R1 draft.

 

I hope I’ve resolved your comments satisfactorily. Please let me know if you have any further comments.

 

BR,

Duncan

 

 

From: M Montemurro <montemurro.michael@xxxxxxxxx>
Sent: Wednesday, December 11, 2024 8:10 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] PDT-MAC-Seamless-Roaming

 

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 starting this work. Attached are my comments posted on top of the latest document I could find in this thread.

 

Cheers,

 

Mike

 

On Fri, Nov 15, 2024 at 9:33PM Duncan Ho <00002b3e54cff3e2-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:

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:

  1. Text included directly in an email (for small additions/changes)
  2. Text in a new WORD document sent as an attachment (not an official 802.11 submission)
  3. Text in a copy of the 11-24/1881rx WORD document showing additions and changes, attached to the email thread.

 

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


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