Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
> I have uploaded a tentative agenda for the teleconference tomorrow. It is available at:
I will try to get some beauty sleep tonight, so I will probably not attend.
Here are my comments for the agenda items:
- I have prepared https://mentor.ieee.org/802.11/dcn/20/11-20-1158-00-00ax-resolutions-for-some-comments-on-11ax-d6-0-sb1.docx
to resolve the three comments assigned to me. I can present when we next have
a teleconf in European working hours (I think Thu 6 Aug?)
- Re today's motions, I have the attached comments on 20/1129. I do not think it is ready for motion.
- Re today's discussions, I have the following comments on 20/0665 for CID 24209:
CF2G4n6G
An AP that operates in the 2.4 GHz band and that is in the same co-located AP set as one or more 6 GHz APs
26.17.2.4 (Out of band discovery of a 6 GHz BSS)
(CFHT2G4 or CFHE2G4):O
CFHE6G:M
Yes o No o
N/A o
CF5Gn6G
An AP that operates in the 5 GHz band and that is in the same co-located AP set as one or more 6 GHz APs
26.17.2.4 (Out of band discovery of a 6 GHz BSS)
(CFHT5G or CFHE5G):O
CFHE6G:M
Yes o No o
N/A o
The requirement, as stated, is on "An AP that operates in the 2.4 GHz band". So the
selector should be just "CFAP AND (CFHT2G4 OR CFHE2G4):O"; nothing about 6G.
If you want you could create another selector, e.g.:
CFcolocated6GAP
An AP that operates in the 2.4, 5 or 6 GHz band and which is one
of the co-located APs in a set that includes a 2.4 GHz or 5 GHz AP
and a 6 GHz AP
CFAP AND (CFHT2G4 OR CFHE2G4):O
CFAP AND (CFHT5G OR CFHE5G):O
CFAP AND CFHE6G:O
and either delete the above, or make them e.g.
CFcolocated6GAP AND (CFHT2G4 OR CFHE2G4):O
CFcolocated6GAP AND (CFHT5G OR CFHE5G):O
with a new row for
An AP that operates in the 6 GHz band and that is in the same co-located AP set as one or more 2.4 GHz or 5 GHz APs
being
CFcolocated6GAP AND CFHE6G:O
but this all starts looking a bit circular.
[BTW, do the 2.4 GHz/5 GHz APs have to be HT APs? Or will ERP/OFDM or
even DSSS/CCK APs do, here? Should "HT " be added before the "AP that
operates" in the descriptions above?]
- Re 20/1142 for CID 24019, I suggest the following text (which I think Abhi is happy with):
A non-AP HE STA shall determine the total number of eligible RA-RUs in a contiguous set of RA-RUs from the Number Of RA-RU subfield (see Figure 9-64f (RA-RU Information subfield format)) in the User Info field corresponding to an eligible RA-RU, excluding RA-RUs that are not within its operating bandwidth.
(Maybe it should be "that are not entirely within", to account for
RUs that span a 20M boundary?)
- Re 20/1123 for CID 24207, might "shall meet at least one of" be
better than "shall meet either one of", which might suggest you must
not meet both?
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 Aboul-Magd
Sent: Wednesday, 29 July 2020 22:43
To: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGAX] TGax CRC Teleconference 2020-07-30
I have uploaded a tentative agenda for the teleconference tomorrow. It is available at:
Please let me know if you plan a submission.
Regards;
Osama.
From: "*** 802.11 TGax - HEW - High Efficiency WLAN ***" <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx> on behalf of Osama AboulMagd <Osama.AboulMagd@xxxxxxxxxx>
Reply-To: Osama AboulMagd <Osama.AboulMagd@xxxxxxxxxx>
Date: Tuesday, July 28, 2020 at 2:22 PM
To: <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx>
Subject: [STDS-802-11-TGAX] TGax CRC Teleconference 2020-07-30
Hello All,
TGax CRC has a conference call scheduled for Thursday July 30 @ 20:00 ET; for 3 hours.
Please let me know if you plan a submission to be added to the list. I’ll upload an agenda later.
Webex info: https://ieeesa.webex.com/ieeesa/j.php?MTID=m03379e62dbec9f142aa671336be2b0b9
Meeting number: 129 816 3004
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 Global call-in numbers
Access code: 129 816 3004
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
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