| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hello Gaurang Thanks for your comments, please see that attached response. Best wishes Ming 发件人: Gaurang Naik [mailto:gnaik@xxxxxxxxxxxxxxxx]
Hi Ming, I noticed that a newer version of the document was posted on mentor. I have one additional comment that I have inserted in the attached file. Could you kindly take a look? Thanks, Gaurang From: Gaurang Naik <gnaik@xxxxxxxxxxxxxxxx>
Hi Ming, I have a few comments that I have inserted in the attached document. One of them aligns with what Rojan described below. Could you kindly review my comments? Thanks, Gaurang From: Rojan Chitrakar <rojan.chitrakar@xxxxxxxxxxxxxxxx>
Hi Ming, I meant that transmitting AP information is not relevant for Probe Request variant ML element, so I did not understand why the common info has to be the same. I am working on the CRs for CIDs related to 9.4.2.247b.3 (Probe
Request variant Multi-Link element) and think this discussion may be more relevant in that document and would appreciate if you can take this clause out from your CR document. I will share my CR document soon. Regards, Rojan From: Ganming(Ming Gan) <ming.gan@xxxxxxxxxx>
Thanks Rojan, so you are saying common part of ML element is not needed? actually there is still difference between basic variant and Probe request variant. That is Per STA profile, the Probe Request variant only has Per-STA Control field. Best wishes Ming Gan 发件人: Rojan Chitrakar [mailto:rojan.chitrakar@xxxxxxxxxxxxxxxx]
Hi Ming, Thanks for the PDT. Regarding the below changes:
9.4.2.247b.3 Probe Request variant Multi-Link element
…
The format of the Common Info field in the Probe Request variant Multi-Link element is as same as Basic variant Multi-Link element as defined
in Figure 9-xxxx - Link Info field of the Basic variant Multi-Link element. The Motion is not relevant to the probe request variant ML element since the transmitting AP’s information will never be carried in it. There is no meaning of having a separate variant of ML element Type for Probe Request
if the format is the same as the Basic variant. Also, I am making changes to this sub-clause as part of the D0.3 CRs. Would you be ok to take this out from your PDT and we can discuss this during my CRs if needed? Thanks. Regards, Rojan From: Ganming(Ming Gan) <ming.gan@xxxxxxxxxx>
Hello Alfred Could you add the following PDT document into the queue? Thanks. 11-21-0397-00-00be-PDT ML element for transmitting AP https://mentor.ieee.org/802.11/dcn/21/11-21-0397-00-00be-pdt-ml-element-for-transmitting-ap.docx best wishes Ming Gan 发件人: Huang, Po-kai [mailto:po-kai.huang@xxxxxxxxx]
Hi Alfred, I have a CR document for clause 35.3.11. Can you add it to the MAC queue?
https://mentor.ieee.org/802.11/dcn/21/11-21-0320-00-00be-cr-for-35-3-11.docx Best, Po-Kai From: Huang, Po-kai
Hi Alfred, I have a CR document for clause 12.4. Can you add it to the MAC queue?
https://mentor.ieee.org/802.11/dcn/21/11-21-0260-01-00be-cr-for-12-4.docx Best, Po-Kai From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Hello all, I uploaded an updated version of the agendas, which contains the agenda for the next conference calls, scheduled on
Monday, March 01 (MAC/PHY), 19:00-22:00 ET and
Wednesday, March 03 (JOINT), 10:00-12:00 ET. The agendas can be found here: https://mentor.ieee.org/802.11/dcn/20/11-20-1917-30-00be-jan-mar-tgbe-teleconference-agendas.docx DIAL IN DETAILS FOR MONDAY: Join the MAC meeting here:
https://ieeesa.webex.com/ieeesa/j.php?MTID=m7ff091053a52e440f4d2a5484310a902 Join the PHY meeting here:
https://ieeesa.webex.com/ieeesa/j.php?MTID=mcc198727c4432acc63dd6b70b1b2ae2e Meeting number: 179 600 1391 DIAL IN DETAILS FOR WEDNESDAY: Join the JOINT meeting here:
https://ieeesa.webex.com/ieeesa/j.php?MTID=m1d1c71d54a60bd6b9c5fafd719c959d9 Meeting number: 179 925 7715 Notice: Please note that by now all authors of the submissions for PDTs and CRs (especially MAC) should have sent requests for feedback to the IEEE TGbe reflector. Members are invited to provide feedback
for these contributions prior to the conference call via e-mail so that the time in the conf calls is used efficiently. 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
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-0397-02-00be-pdt-ml-element-for-transmitting-ap+GN_Ming.docx
Description: 11-21-0397-02-00be-pdt-ml-element-for-transmitting-ap+GN_Ming.docx