Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
Hi, Brian. Thank you for all the work. Regarding CID 1059 and 2019, I like the direction of streamlining the “delay” to an earlier point in the PPDUs. However, I am not convinced with all the details of the changes. For example, I think it would be simpler to just set the aRxPHYStartDelay to a common 24 usec for Clause 17 (OFDM), 19 (HT), 21 (VHT) and 27 (HE). That gives enough time for all these PHYs to detect at least L-SIG and/or RL-SIG, and in
case of HT-GF, the HT-SIG. Then, I don’t think we need the new “KeyValueList” variable, and the operation of taking the max. value. Regards, Youhan From: Brian Hart (brianh) <00000c7561051aea-dmarc-request@xxxxxxxxxxxxxxxxx>
--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
Fixed this. Also aligned the POWER_BOOST_CHANGES with the latest changes in 11be on this topic (from Hanqing’s 22/1270r3). The new doc is now uploaded as r10. -B From: Mark Hamilton <mark.hamilton2152@xxxxxxxxx>
--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
Thanks, Brian. So, CID 1056 still has a proposed resolution in 11-22/576, it just has a different proposal, which is to reject. (Just to make sure the agenda notes – if/as appropriate – that the CID is covered by this submission.) I do have a nit-pick: Since the resolution is Rejected, good practice dictates the actual resolution (not just notes to commenters) provide the rationale for the rejection. In this case, I would recommend just deleting the “Note to Commenter:“
so, this is a full resolution of Rejected and rationale. Thanks. Mark From: Brian Hart (brianh) <brianh@xxxxxxxxx>
Hi Mark – inline -B From: mark.hamilton2152@xxxxxxxxx <mark.hamilton2152@xxxxxxxxx>
Thanks, Brian, I believe 22/576 also resolves:
[So confirmed.]
[Actually I’ve changed CID 1056 to a reject, so now there is no proposal in 22/576r9 to add a new VS trigger frame.] Can you confirm this understanding? And, then, does anyone have a concern with agreeing to these resolutions, also? Thanks. Mark From: Brian Hart (brianh) <00000c7561051aea-dmarc-request@xxxxxxxxxxxxxxxxx>
--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
Hi all Re the resolutions in 22/576, review and email discussion in order to improve the efficiency of the 11me meeting is welcomed. 22/576 resolutions, if accepted, has the following consequences:
Cheers Brian To unsubscribe from the STDS-802-11-TGM list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1 To unsubscribe from the STDS-802-11-TGM list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1 To unsubscribe from the STDS-802-11-TGM list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1 To unsubscribe from the STDS-802-11-TGM list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1 |