Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hello Mark
Sorry for missing your email. Based on 21/577r5, each link maintains its own scoreboard and the MLD Upper MAC sublayer optionally delivers the BA record on one link to the MLD Lower
MAC sublayer of other links. Now it seems the size of the scoreboard of each link is quite important since each STA will use this to provide reception status. However, it is still confusing how to implement the HT-immediate block ack architecture, including
WinSizeO, WinSizeR. What do you think about it? Best wishes Ming Gan 发件人: Duncan Ho [mailto:dho@xxxxxxxxxxxxxxxx]
Hi Mark, Yes, adding it to your 21/1111 sounds good to me. I think that would be a good clarification. Thanks, Duncan From:
mark.hamilton2152@xxxxxxxxx <mark.hamilton2152@xxxxxxxxx>
CAUTION: This email
originated from outside of the organization. By the way, we could add this to document 11-21/1111, if you are worried about touching 11-21/0577 since it has already passed straw poll. Mark From:
mark.hamilton2152@xxxxxxxxx <mark.hamilton2152@xxxxxxxxx>
Ming/Duncan, Should we add a statement that the Block Ack agreement is between the peer MLDs, the scoreboarding function that is in the Lower MAC sublayer is just a “link local” optimization that may provide partial information about
block ack status? That is, it is not where the overall block ack agreement is negotiated or maintained. Mark From: Duncan Ho <dho@xxxxxxxxxxxxxxxx>
Hi Ming, The diagram and associated text made no such requirement/assumption since they are meant for describing the functions and not how the detailed parameters are set or negotiated, etc. Thanks, Duncan From: Ganming(Ming Gan) <ming.gan@xxxxxxxxxx>
CAUTION: This email
originated from outside of the organization. Hello Duncan I have a general question about the figure. Does it imply the size of each scoreboard for each link needs negotiation during ADDBA request/response? Best wishes Ming Gan 发件人:
顾祥新 (Xiangxin Gu) [mailto:Xiangxin.Gu@xxxxxxxxxx]
Hi Duncan, Thank you for the contribution! I think we can have a more general example in Figure 35-xxx
– Example MLD and the affiliated STA communication system, such as 2 STAs in non-AP MLD setting up link1 and link3 with AP MLD which has 3 STAs. BR, Xiangxin Unisoc Technologies Co., Ltd. +86 21 20360600 3324 From: Arik Klein <arik.klein@xxxxxxxxxx>
Now with the doc… Sorry. Regards, Arik From: Arik Klein
Hi Duncan, Thanks for sharing this document. I’ve attach my comments with my colleague (Stephen McCann) comments. I’ll appreciate your review for these comments. Regards, Arik From: Duncan Ho <dho@xxxxxxxxxxxxxxxx>
Hi all, Please see
https://mentor.ieee.org/802.11/dcn/21/11-21-0577-00-00be-cr-mld-architecture.docx and let me know if you have any comments or questions. Thanks, Duncan 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 |