| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Classified Hi Chong, I noticed the following in 11-22/0074r15:
Could you update 11-22/397 to add CID 331? The proposed resolution in 397r1 still has “immediately”, so CID 331 isn’t addressed yet. Best regards, -Nancy From: Chong Han <chong.han@xxxxxxxxxxxx>
Hi Nancy,
Thank you for your comments. I have updated and uploaded the doc. 11-22/0397r1. The link to the document on mentor is here:
https://mentor.ieee.org/802.11/dcn/22/11-22-0397-01-00bb-resolution-for-cids-in-11-22-0074r11-comments-on-p802-11bb-d1-0.docx Regards,
Chong From: Nancy Lee <nancy.lee@xxxxxxxxxxx>
CAUTION:
This email originated from outside of pureLiFi. Do not click links or open attachments unless you recognize the sender and know for certain that the content is safe. Classified Hi Chong, Thanks for proposing text to resolve these comments.
Per e.g. comment 30, we can’t use the word “may” in the specification. Your proposal still missing the point
that the second case is taking advantage of the fact that LC systems are directional, thus in transmitting the repeated signal it has in some sense already gained access to the downlink channel, and can continue occupying the channel by immediately transmitting
its queued packet. However after considering ACKs, it’s not clear to me this works if Packet 3 requires an ACK. I suggest deleting P21L24-26 and modifying
the resolution of comment 32
to align with your modified figure and to
explicitly state that Packet 1 and Packet 2 show an example of normal DCF/EDCA behavior, whereas Packet 3 and Packet 4 show an example of optional behavior when Packet 4 is queued at the
LC AP before it finishes transmission of repeated Packet 3 as follows: Change resolution of CIDs 32 and 219 to:
Replace P21L30-32 with "After retransmitting Packet 1 and sending an ACK to Packet 1, the LC AP follows normal DCF/EDCA behavior and waits
until its backoff counter reaches zero before transmitting Packet 2 to non-AP LC STA1. Non-AP LC STA1 ACKs Packet 2. Sometime later non-AP LC STA2 obtains access to the channel and transmits Packet 3. Packet 4 is queued at the LC AP before it finishes transmission
of repeated Packet 3 that does not require an ACK. The figure shows optional behavior whereby the LC AP continues occupying the downlink channel by immediately transmitting its queued packet after completing retransmission of Packet 3." Regards, -Nancy From: ** STDS-802-11-TGbb -- Light Communication
Task Group** <STDS-802-11-TGBB@xxxxxxxxxxxxxxxxx>
On Behalf Of Chong Han
Dear all,
I have uploaded a document with Resolutions for CID 88 and 219 in the comment sheet 11-22/0074r11. Nancy, please help check the proposed replacement of existing text
on page 21 for the CID 219. Regards,
Chong To unsubscribe from the STDS-802-11-TGBB list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBB&A=1 The information contained in this email may be confidential and/or legally protected
under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this email is strictly prohibited and may be unlawful. If
you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original email. To unsubscribe from the STDS-802-11-TGBB list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBB&A=1 |