Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Sherief, Please see my comments inline Thanks, Rony From: Sherief Helwa <shelwa@xxxxxxxxxxxxxxxx>
Hi Rony, Thanks for your feedback! Please see my response
inline. Regards, Sherief From: Rony Ross <0000491f5321510d-dmarc-request@xxxxxxxxxxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Sherief, I’ve attached technical comments on 25/0742r2 Mainly:
[SH] I don’t mind revisiting the naming but I suggest we keep names as is for now to avoid confusion and last minutes changes that might make some members
lose track. [RR] The original name seems to be confusing. As mentioned in some comments, there are cases in which the
receiver failures would not necessarily manifest as errors in the BACK
[SH] I agree on the concept that this should be up to the device, i.e., the non-AP STA, to decide which is more significant. But sorry, didn’t get the first
part of this point. [RR] The STA knows that it experienced significant receiver performance degradation. It has no way of knowing
how many MPDUs failed and how these failures manifest in the BACK. Therefore,
“Receiver Performance Degradation” is the only thing that the STA can indicate in the BACK. The rules in the following section cannot
be followed and should be removed: “following the rules below: If the STA reports in the Multi-STA Block Ack frame that all the frame(s) requiring an immediate response are successfully
received, then the STA shall set the In-Device Error Flag subfield to 0. If the STA reports in the Multi-STA Block Ack frame that at least one of the frames requiring an immediate response
is not successfully received, then the STA shall set the In-Device Error Flag subfield to: 1 if at least one of the unsuccessful receptions is due to an in-device error that occurred during the reception
of the PPDU containing these frame(s) 0 if either none of the unsuccessful receptions is due to an in-device error or the source of
the error is unknown.” As there are concerns regarding the impact of this bit on the AP’s rate selection algorithm, I also suggest
replacing the following note “If the AP receives an indication from the
DUO STA that an in-device error has occurred during the reception of the soliciting PPDU, then the expectation is that the AP does not consider the failed reception of any of the frames that solicited an immediate response and contained in the soliciting PPDU
as an input to the AP’s rate selection algorithm, which is by itself out of scope of the standard.” with “If the AP receives an indication from
the DUO STA that Receiver Performance Degradation occurred during reception of the soliciting PPDU, it is expected that the AP incorporate this indication into its rate selection algorithm. Specifically, the AP may attribute acknowledgment failures to internal
receiver degradation rather than to adverse channel conditions.. The AP’s rate selection algorithm is out of scope of the standard.” Thanks, Rony From: Sherief Helwa <00002dded7ae4daf-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Alfred, Can you please add the following documents to the MAC queue?
Regards, Sherief From: Liwen Chu <liwen.chu@xxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Alfred, Please add the following CR document to the MAC queue: https://mentor.ieee.org/802.11/dcn/25/11-25-0669-00-00bn-cr-cc50-mac-cids-in-clause-37-9-1.docx Best Regards, Liwen From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Hi Alfred, Please add the following (presented) CR doc to agenda for MAC queue for SP: https://mentor.ieee.org/802.11/dcn/25/11-25-0479-01-00bn-cr-for-cid-1378.docx Regards, Dibakar From: Eunsung Park <esung.park@xxxxxxx>
Hi Alfred, Could you please add the following CR documents to the PHY queue?
Best regards, Eunsung From: Eunsung Park [mailto:esung.park@xxxxxxx]
Hi Alfred, Could you please add the following CR document to the PHY queue?
Best regards, Eunsung From: Eunsung Park [mailto:esung.park@xxxxxxx]
Hi Alfred, Could you please add the following CR document to the PHY queue?
Best regards, Eunsung From: Eunsung Park [mailto:esung.park@xxxxxxx]
Hi Alfred, Please add the following CR documents to the PHY agenda?
Best regards, Eunsung From: Eugene Baik [mailto:0000419888923000-dmarc-request@xxxxxxxxxxxxxxxxx]
Hi Alfred, Can you add 11-25-0509-00-00bn – CC50 CID resolutions for 38.1 to the agenda, if it’s not too late? Thanks, Eugene From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hello all, We have a MAC/PHY teleconference scheduled for Monday 24 March 2025, and I am finalizing the agenda (planned to be posted tomorrow). Currently there is only one PHY submission in the queue so I would
like to ask members to send me additional requests for PHY CR submissions asap and no later than
tomorrow, Friday 17:00 ET. This way we can use the teleconferences in an efficient way and start the comment resolution process. Guidelines for scheduled PHY conf calls: · Members
are invited to send submission requests to be added to the PHY submissions queue. · Requests may
explicitly indicate if the requestor prefers to discuss his/her submission at a particular PHY conf call. If there is no such explicit indication then the submission will be added by default to the PHY submissions queue and will be scheduled for presentation
in a subsequent PHY conference call during which there are at least 3 submissions available for discussion. · A scheduled PHY conference
call will be cancelled if the planned PHY agenda for that particular conference call does not have at least 3 queued presentations or at least one queued presentation with an explicit request. Regards, Alfred --
Alfred Asterjadhi, PhD IEEE802.11 TGbe/TGbn Chair, Qualcomm Technologies Inc. Cell #: +1 858 263 9445 Office #: +1 858 658 5302 To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1 To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1 To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1 To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1 To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1 To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1 |