| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Vishnu, Sorry for late response. Thanks for your comments. I think the following sentence has already addressed your concern. “An AP MLD may (#12808) use Multi-Link Traffic Indication element and TIM element carried in a Beacon frame or Wake-up Request MLI Control subfield carried
with an individually addressed frame to recommend a non-AP MLD to use one or more enabled links to retrieve individually addressed buffered BU(s).” Regrads Gougang Huang 发件人: Vishnu Ratnam [mailto:vishnu.r@xxxxxxxxxxx]
Hi Guogang, Thank you for your document 1517r1. As you are aware, I have a very similar CR document 11-22/1201r3 that has been presented before in the group and has had significant
offline discussions as well. The only difference I can see between the two contributions (apart from other changes to ML traffic indication element etc.) is as follows:
11-22/1201r3: The link recommendation in the new A-control does not violate downlink T2LM 11-22/1517r1: The link recommendation in the new A-control can violate the downlink T2LM Although I am fine with either direction (both have their own benefits), many people in offline discussion (can be seen from reflector) prefer not violating the
T2LM. So I would suggest to run a straw poll to check which direction the group prefers.
Side comment:
I think the text needs to be changed slightly to highlight that the Link Recommendation in the A-control is to indicate a link to fetch the "currently" buffered
BUs at the AP MLD and is not a long-term recommendation like the Link Recommendation frame, whose purpose is different. For example: "An AP affiliated with an AP MLD may transmit an individually addressed frame containing a Wake-up
Request MLI Control subfield to provide link recommendation for a non-AP MLD to retrieve the
BU(s) that are currently buffered at the AP MLD." Regards, Vishnu From: huangguogang <000017b1384624cd-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Alfred, Please add the following contribution to the agenda: 11-22-1517-00-00be-lb266-cr-on-unicast-link-recommedation (6 CIDs) Regards Guogang Huang 发件人: Alfred Asterjadhi [mailto:asterjadhi@xxxxxxxxx]
Hello all, I uploaded a preliminary version of the agenda for the TGbe MAC ad-hoc scheduled Nov 11 and 12, 2022, located at the same hotel as the IEEE802.11 plenary. The MAC ad-hoc will be in mixed mode and hence Webex links are
also provided. Currently the queues are empty and will be populated after the Wednesday MAC conf call. Please let me know if you have any questions. Regards,
-- 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 |