Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Ming I have reviewed your proposal (21/1443r0). Please see my comments in the attached document. Thanks. Best, Namyeong. From: Abhishek Patil [mailto:appatil@xxxxxxxxxxxxxxxx] Hi Ming, Laurent, We must not increment the BPCC when the 5 elements listed in 35.3.10.2 (of D1.2) are updated on any link. Per 35.3.10.2, updates to any of these IEs for an affiliated AP will cause other (affiliated) APs to include the corresponding IE(s) in the ML IE carried in its Beacon & Probe Resp frame. As a result, the updated are directly available to the non-AP MLD on each link and don’t need to be part of the critical updates procedure. I had submitted a comment to address this issue:
Regards, From: Cariou, Laurent <laurent.cariou@xxxxxxxxx> WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Ming, Looks in the good direction for non-special scenarios. See attached some editorial to make things clearer. For special scenario: There is the case where the information of the critical updates are included in the frame on which the Critical Update flag is set (Quiet element, CSA, eCSA, …). We need to see what is the procedure here: as the STA already received all the info of the critical update in the frame, it doesn’t make sense to be forced to retrieve one more time the information. We likely need a flag in that case that indicates that all info of the critical update is included in the frame. This will have impact on this procedure here so we need to address that. Maybe one way is to add one condition, something like: Unless the non-AP MLD has received the updated elements and fields corresponding to the critical update. Thanks, Laurent From: Ganming(Ming Gan) <ming.gan@xxxxxxxxxx> Hi Alfred Sorry, I made a mistake. The document # is not correct, it is 21/1443r0 CC36 CR for Retrieving Critical Update. Best wishes Ming 发件人: Ganming(Ming Gan) [mailto:ming.gan@xxxxxxxxxx] Hello Alfred Could your help add the SP for 21/1587r0 into the agenda? Thanks. Best wishes Ming Gan 发件人: Gaurang Naik [mailto:gnaik@xxxxxxxxxxxxxxxx] Hi Alfred, Could you kindly add document 11-21/1659 to the MAC queue? All, Document 11-21/1659 proposes a resolution for CID 4002 and is related to the inclusion of the ML element in Authentication frames. Kindly let me know if you have any feedback. Thanks, Gaurang From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx> WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hello all, I uploaded an updated version of the agendas, which contains the agenda for the next conference calls, scheduled on Monday October 11 (MAC/PHY), 19:00-21:00 ET and Wednesday October 13 (Joint), 10:00-12:00 ET. The agendas can be found here: https://mentor.ieee.org/802.11/dcn/21/11-21-1478-14-00be-sept-nov-tgbe-teleconference-agenda.docx Note for CR documents: Please update the baseline to TGbe D1.2 (available in the member's area) for the CR documents. Alternatively, please ensure that there are no conflicts between the proposed changes in the CR documents and TGbe D1.2. DIAL IN DETAILS FOR MONDAY: Join the MAC meeting here: https://ieeesa.webex.com/ieeesa/j.php?MTID=mdf33f68dda7130d8020992c4432c15dd Meeting number: 234 895 70425 Meeting password: wireless (94735377 from phones and video systems) Join the PHY meeting here: https://ieeesa.webex.com/ieeesa/j.php?MTID=m3b56ece2a546e1ad42c0696e060bb01a Meeting number: 234 742 12243 Meeting password: wireless (94735377 from phones and video systems) DIAL IN DETAILS FOR WEDNESDAY: Join the Joint meeting here: https://ieeesa.webex.com/ieeesa/j.php?MTID=m0bbc2bbf02a4808bf9238e19661d3a1b Meeting number: 233 296 78733 Meeting password: wireless (94735377 from phones and video systems) Let me know if you have any questions and/or suggestions. Best Regards, Alfred -- Alfred Asterjadhi, PhD IEEE802.11 TGbe Chair, Qualcomm Technologies Inc. Cell #: +1 858 263 9445 Office #: +1 858 658 5302 To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 --------------------------------------------------------------------- This e-mail and any attachments may contain confidential material for To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 |
Attachment:
11-21-1443-00-00be-cc36-cr-for-retrieving-critical-update_NK.DOCX
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document