| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi
Guogang, Consider the following example.
You start with sending 0 to 512 in link 1 and 512 to 1023 in link 2. Somehow link 2 is faster, so you end up with sending 512 to 1000. (say SSN2 is 1000) Say link1 is slower, so you end up with SSN1 65. Now, say you move 65 to 512 to link 2 and 1001 to link 1. SSN1 will become 1001 now, which means both SSN1 and SSN2 becomes >1000, and you can not deliver
65 to 512 anymore. Best, Po-Kai From: huangguogang <huangguogang1@xxxxxxxxxx> Hi Po-kai,
Thank you for your response. Could you give an example to explain how the scheduling algorithm will affect my proposed approach? BR Guogang Huang 发件人:
Huang, Po-kai [mailto:po-kai.huang@xxxxxxxxx]
Hi Guogang, Thanks for checking with me. Please see my response below. Best, Po-Kai From: huangguogang <huangguogang1@xxxxxxxxxx>
Hi Po-kai,
For the proposed scheme, I agree that the responding side needs to communicate among links to acquire the WinStartR. But I don’t think this is a big issue.
[Po-Kai]: I think this comment is just the same as the comment from Liwen and George that different links needs to communicate this new SSN value in level that is required to respond
Block Ack to support this mechanism. In addition, I ‘m not sure that whether I get all your points in the teleconference meeting. Could you describe your questions or comments through email? I try to
response them. [Po-Kai]: My comment is that for the proposal from Liwen, I can immediately see that the approach works for any scheduling algorithm that may happen between different links. However,
for your proposal, I cannot immediately see if it works for any scheduling algorithm that may happen. This is more of a general comment. BR
Guogang Huang 发件人:
huangguogang Hi all, If you still have questions or comments for the contribution DCN681r1, please send it to me through email. Thanks, Guogang Huang 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 |