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

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

Hi Xiangxin,

Happy New Year!

Thanks for your comments. Please see my response inline below.

BR,

Duncan

From: 顾祥新 (Xiangxin Gu) <Xiangxin.Gu@xxxxxxxxxx>
Sent: Friday, January 3, 2025 12:46 AM
To: Duncan Ho <dho@xxxxxxxxxxxxxxxx>; 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,

Happy New Year!

Thanks for the effort on the PDT. I have a question on the text. What is “another target AP MLD”?

[DH] I changed it to “to a target AP MLD” and hope that clarifies it.

I have also a suggestion to add “When a non-AP MLD uses … to a target AP MLD” at the beginning of clause 37.12.2, as the following:

[DH] Looks good. I’ve added this phrase now.

BR,

Xiangxin Gu

Communication Standards Devision

From: Duncan Ho <00002b3e54cff3e2-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Friday, January 3, 2025 7:01 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] PDT-MAC-Seamless-Roaming

Dear SR TTT members,

Happy New Year!

Thanks Mark, Mike and Guogang for your review of the draft and all your thoughtful comments. Much appreciated! I just uploaded the R1 of the PDT here based on all the comments I’ve received so far.

Mark, I’ve addressed your comments in the attached “11-24-1881-01-011bn-PDT-mac-seamless-roaming-v5-mgr+DH” and “11-24-1881-00-00bn-pdt-mac-seamless-roaming-mgr+DH-mgr+DH”.

Guogang, I’ve addressed your comments in the attached “11-24-1881-00-00bn-pdt-mac-seamless-roaming-HGG+DH”,

Mike, I’ve added the “To be done” you suggested.

For the sentence about notifying the DS about the DS mapping change, I’m keeping it for now since “DS mapping change” is in the Motion and it is one of the important aspects of seamless roaming. However, I do understand that we may need to modify it or add clarifications later as we have further discussion on the SR framework and DS mapping updates.

Thanks,

Duncan

From: Mark Rison <m.rison@xxxxxxxxxxx>
Sent: Monday, December 23, 2024 6:01 AM
To: Duncan Ho <dho@xxxxxxxxxxxxxxxx>; 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.

- "The non-AP MLD may transmit Class 3 frames to the target AP MLD after receiving the TBD Response frame sent by the current AP MLD." seems meaningless since "after" can mean a very long period and the non-AP surely will send class 3 frame after it moves under target AP. Maybe the intention is to use "when"?

[DH] The sentence specifies the EARLIEST time the non-AP MLD can transmit Class 3 frames so it seems correct to me. Are you saying some may interpret the “after” can mean a very long time (which is not specified)? That does not seem like a natural interpretation of spec language. Note we cannot use “when” because at the time the Response frame is received, the non-AP MLD may or may not have frames to transmit immediately.

It would be clearer to express this as "The non-AP MLD shall not transmit Class 3 frames to the target MLD until it has received the TBD Response frame."

- "In addition, by this time, the DS has been notified about the update of the destination mapping for the non-AP MLD if necessary, from the currently AP MLD to the target AP MLD."

"by the time" is confusing since the sentence above uses "may" so there can be 2 possible cases.

[DH] This sentence is a bit problematic. I’ll try to reword it in the next revision of the draft.

This appears to be some kind of hidden "shall". The "shall" should be made explicit.

Thanks,

Mark

Mark RISON, Standards Architect, WLAN English/Esperanto/Français

Samsung Cambridge Solution Centre Tel: +44 1223 434600

1 Cambridge Square, Cambridge CB4 0AE Fax: +44 1223 434601

ROYAUME UNI WWW: http://www.samsung.com/uk

From: Duncan Ho <00002b3e54cff3e2-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Saturday, 21 December 2024 01:14
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] PDT-MAC-Seamless-Roaming

Hi Haorui,

Thanks for your comments and please see my responses inline below.

From: Haorui Yang(Rae) <yanghaorui0217@xxxxxxx>
Sent: Monday, December 16, 2024 10:05 PM
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 the updated draft.

I have the below comment:

- "In addition, by this time, the DS has been notified about the update of the destination mapping for the non-AP MLD if necessary, from the currently AP MLD to the target AP MLD."

"by the time" is confusing since the sentence above uses "may" so there can be 2 possible cases.

[DH] This sentence is a bit problematic. I’ll try to reword it in the next revision of the draft.

Thanks,

Duncan

BRs,

Haorui Yang(Rae)

China Mobile

---- Replied Message ----

From	M Montemurro<montemurro.michael@xxxxxxxxx>
Date	12/17/2024 00:30
To	<STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject	Re: [STDS-802-11-TGBN] PDT-MAC-Seamless-Roaming

Hi Duncan,

Thanks for the update. I have two comments:

1) The text I added (To be done: Define the framework for seamless transition needs to be a placeholder in this contribution.)

2) I believe the following text is contentious and should not be included in this draft text at this time (pending the discussion on framework above).

"In addition, by this time, the DS has been notified about the update of the destination mapping for the non-AP MLD if necessary, from the currently AP MLD to the target AP MLD"

I would suggest that you delete it at this time.

Cheers,

Mike

On Fri, Dec 13, 2024 at 11:59 PM Duncan Ho <dho@xxxxxxxxxxxxxxxx> wrote:

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:33 PM 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:

Text included directly in an email (for small additions/changes)
Text in a new WORD document sent as an attachment (not an official 802.11 submission)
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

This email (including its attachments) is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. Unauthorized use, dissemination, distribution or copying of this email or the information herein or taking any action in reliance on the contents of this email or the information herein, by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is strictly prohibited. If you are not the intended recipient, please do not read, copy, use or disclose any part of this e-mail to others. Please notify the sender immediately and permanently delete this e-mail and any attachments if you received it in error. Internet communications cannot be guaranteed to be timely, secure, error-free or virus-free. The sender does not accept liability for any errors or omissions.
本邮件及其附件具有保密性质，受法律保护不得泄露，仅发送给本邮件所指特定收件人。严禁非经授权使用、宣传、发布或复制本邮件或其内容。若非该特定收件人，请勿阅读、复制、 使用或披露本邮件的任何内容。若误收本邮件，请从系统中永久性删除本邮件及所有附件，并以回复邮件的方式即刻告知发件人。无法保证互联网通信及时、安全、无误或防毒。发件人对任何错漏均不承担责任。

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