Hi Gaurang
You miss my response in previous attached file- update it in the later version. Please see the attached new
version. Meanwhile please see my response inline
The ML ID is just for discussion in the attached file
Hi Ming,
Thank you very much for responding to my comments.
I looked at the responses in both versions of the document and found that a few of my
questions/comments were not addressed. I have reinserted a few comments in the latest version (r2).
Also, the approved SP text (copied below) relates to Link ID and CSN, both of which apply
to an AP MLD. The motion doesn't talk about MLD ID. Could you kindly explain why the probe request variant of ML IE needs to carry MLD ID and Link ID?
The CSN and Link ID fields are reserved when transmitted by a STA of a non-AP MLD transmits
ML IE and therefore, this change must be captured in clause 9 not clause 35. This is the normal practice in baseline spec.
[Ming] Since it clause 9, it already mentions
The condition for the presence of the MLD MAC Address subfield, the Transmitting AP Link ID subfield and the Transmitting AP Change Sequence subfield
in the Common Info field is defined in 35.3.5.4 (Usage and rules of Multi-link element in the context of multi-link setup) and 35.3.4.3 (Multi-link element usage rules in the context of discovery).
So it is not needed in clause 9
In addition, I also noticed that the changes in clause 35 are not with respect to approved
text (for example, clause 35.3.4.4 was updated by a few docs). The numbering of the subclauses is also incorrect. I’m afraid this can create a conflict when the editor tries to incorporate your changes. Resulting in some of the changes from your doc being
missing in the next draft. I suggest that you base your changes with respect to the latest approved text.
[Ming] It is updated, please refer to the attached file. Thanks
Thanks,
Gaurang
Hi Ming,
I have similar questions as Gaurang. It is not clear to me why the MLD ID and Transmitting AP link id is included in the Probe Request variant
MLE. Moreover, the PDT does not contain any normative text that explains what these fields are for. My impression of the Motion covered in the PDT was that it only targets the Basic variant MLE; I believe SP2 about ML probe request has not been run yet. Shouldn’t
we run the SP first?
Hello Gaurang
Thanks for your comments, please see that attached response.
Best wishes
Ming
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
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
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
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
Hi Ming,
Thanks for the PDT. Regarding the below changes:
9.4.2.247b.3 Probe Request variant Multi-Link element
…
The presence and format of the Common Info field in the Probe Request variant Multi-Link element are
TBD.
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.
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
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
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
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:
DIAL IN DETAILS FOR WEDNESDAY:
Join the JOINT meeting here:
https://ieeesa.webex.com/ieeesa/j.php?MTID=m1d1c71d54a60bd6b9c5fafd719c959d9
Meeting number: 179 925 7715
Meeting password: wireless (94735377 from phones and video systems)
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.
--
Qualcomm Technologies Inc.
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
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