Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Here are my thoughts: For 25115 I think
Menzo was going to solicit feedback from Jouni.
The questions are (1) whether "increments […] in a way that ensures that a PN is not reused" is clear enough (not always increment by 1) and (2) whether it's OK to reuse a PN as long as the UP has changed (for PV0, which is all we need to care about here). For 25108 the issue I think is that An originator STA may transmit to a recipient STA the following: […] Up to four dynamic fragments of an MSDU or A-MSDU (if supported
by the recipient) for each MSDU or A-MSDU, and up to one dynamic fragment of an MMPDU in an A-MPDU, where the A- MPDU contains
at least one dynamic fragment using level 3 dynamic fragmentation under block
ack agreement. is not clear as it suggests only one of the (Data)
dynfrags has to be sent under a BA agreement.
Right? Is there any other possible mismatch between the informal description in 26.3.1 and the normative text in 26.3.2.3/4 (or elsewhere)? Thanks, Mark --
Mark RISON, Standards Architect, WLAN English/Esperanto/Français Samsung Cambridge Solution Centre Tel: +44 1223 434600 Innovation Park, Cambridge CB4 0DS Fax: +44 1223 434601 ROYAUME UNI WWW:
http://www.samsung.com/uk From: Ganming (Ming) <ming.gan@xxxxxxxxxx>
Hello Mark and Menzo Since there are two CIDs that need further input from other individuals or more consideration, do you get any feedback now. If
they are ready, we could finish all of them in this week. By the way, I sent the email to you before, maybe you missed it. Best wishes Ming Gan 发件人:
*** 802.11 TGax - HEW - High Efficiency WLAN *** [mailto:STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx]
代表
Mark Rison
Regarding 25089/25090, I'm not persuaded by: NOTE—27.3.4 and 27.3.6.10 specify the requirements on each of the other remaining subfields, such that the solicited non-AP STAs each construct a valid HE TB PPDU in response to the
Trigger frame. Neither 27.3.4 nor 27.3.6.10 have any requirements that I can see about Trigger frame subfields, let alone combinations that yield "valid" HE TB PPDUs. Am I missing something?
I think 25108 and 25115 are not ready (hoping for some Menzo/Jouni updates). Also for 25109, based on the discussion on the wording for 25110/25111, maybe "Data frames containing dynamic
fragments" should be "Data frames that are dynamic
fragments"? Also I think we'd agreed to fix the grammar in "shall
support to transmit and receive". And 25113 had some Nmax editorial tweaks. In fact, maybe none of the updates we made during the last teleconf are in r1; maybe 1647r2 was meant to be uploaded but hasn't?
For 25071, "NSTS-1, where the NSTS
indicates" should be "NSTS – 1, where
NSTS is" i.e. italic and subscript in NSTS, minus not hyphen, no article, is not indicates. Also, the change at 440.48 has been missed. For 25095, there's a "to
indicate indicate". For 25096, " Responding to all
Trigger frame variants, including MU-RTS Trigger frames and NFRP Trigger frames, are suspended" should be "is suspended" (the subject is "Responding"). Thanks, Mark --
Mark RISON, Standards Architect, WLAN English/Esperanto/Français Samsung Cambridge Solution Centre Tel: +44 1223 434600 Innovation Park, Cambridge CB4 0DS Fax: +44 1223 434601 ROYAUME UNI WWW:
http://www.samsung.com/uk From: *** 802.11 TGax - HEW - High Efficiency
WLAN *** <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx>
On Behalf Of Osama AboulMagd Hello All, TGax CRC has a conference call scheduled for Thursday October 22 @
10:00 ET; for 3 hours. TGax CRC has a conference call scheduled for Friday October 23 @
10:00 ET; for 2 hours. I’ve uploaded a draft agenda. It is available at:
https://mentor.ieee.org/802.11/dcn/20/11-20-1552-11-00ax-tgax-crc-teleconference-agendas-october-november-december-2020.pptx
. A list of CIDs ready for motion includes:
Webex Info (Thursday):
https://ieeesa.webex.com/ieeesa/j.php?MTID=maa65737f7b0639948ae3d8f6d15b749d
Meeting number: 173 018 4011
Meeting password: wireless (94735377 from phones and video systems)
Join by phone: Tap to call in from a mobile device (attendees only)
+1-408-418-9388 USA Toll Webex Info (Friday):
https://ieeesa.webex.com/ieeesa/j.php?MTID=mfe1a0e32c20c76e60312d209dfc8f708
Meeting number: 173 200 9381
Meeting password: wireless (94735377 from phones and video systems)
Join by phone: Tap to call in from a mobile device (attendees only)
+1-408-418-9388 USA Toll Teleconferences are bound by the conditions stipulated by the documentation below. Please review them and bring up any questions/concerns
you may have before proceeding with the teleconference • IEEE Code of Ethics https://www.ieee.org/about/corporate/governance/p7-8.html • IEEE Standards Association (IEEE-SA) Affiliation FAQ https://standards.ieee.org/faqs/affiliation.html • Antitrust and Competition Policy https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/other/antitrust.pdf • IEEE-SA Patent Policy http://standards.ieee.org/develop/policies/bylaws/sect6-7.html https://standards.ieee.org/about/sasb/patcom/ • IEEE 802 Working Group Policies &Procedures (29 Jul 2016) http://www.ieee802.org/PNP/approved/IEEE_802_WG_PandP_v19.pdf • IEEE 802 LMSC Chair's Guidelines (Approved 13 Jul 2018 https://mentor.ieee.org/802-ec/dcn/17/ec-17-0120-27-0PNP-ieee-802-lmsc-chairs-guidelines.pdf • Participation in IEEE 802 Meetings https://mentor.ieee.org/802-ec/dcn/16/ec-16-0180-05-00EC-ieee-802-participation-slide.pptx • IEEE 802.11 WG OM: (Approved 10 Nov 2017) https://mentor.ieee.org/802.11/dcn/14/11-14-0629-22-0000-802-11-operations-manual.docx Regards; Osama. To unsubscribe from the STDS-802-11-TGAX list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1
To unsubscribe from the STDS-802-11-TGAX list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1
To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1 |