All,
It was suggested that I send this to the entire Dot19 reflector and not just Steve and Ben, as there are others in Dot19 with similar concerns.
Best Regards,
Clint
Clinton Powell – Managing Director/Sr. Consultant
1563 W Kaibab Dr | Chandler, AZ 85248
M: 480 586-8457 S: clintonpowell
SCE - Wireless Consultant
Facebook - Wireless Consultant
IEEE 802.15 Secretary
Zigbee Alliance - Certification Adv. Group Chair
Zigbee Alliance - IEEE 802.15.4 PHY/MAC Adv. Group Chair
Zigbee Alliance - CHIP CSG Dependent Certification Programs Tiger Team Lead
From: Clint <cpowell@xxxxxxxx>
Sent: Friday, October 30, 2020 1:03 PM
To: Steve Shellhammer <sshellha@xxxxxxxxxxxxxxxx>
Cc: Ben Rolfe <ben@xxxxxxxxxxxxxx>; Clint Powell <cpowell@xxxxxxxx>
Subject: RE: [802.19] EC Document on Chairs Guidelines - Scope of CA Document
CAUTION: This email originated from outside of the organization.
Steve,
I would highly encourage 802.19 lobbying changing bullets 1 and 2 from “same frequency bands” to “same and adjacent frequency bands”.
Below is my response as to why I’m not changing my no vote on 802.11ax. This especially applies to adjacent bands.
Osama,
Thank you for reaching out to me regarding my comment and No Vote on 802.11ax.
While I understand that providing Coexistence Assurance may not be a requirement, I cannot in good conscience approve an 802 standard that does not address this issue, given the impact that it has. Working in the utility and other sectors I have experienced far too often proprietary systems being used in the unlicensed and other bands that give no consideration to coexistence with other systems and cause demonstrable interference. In many, if not all cases those systems could have easily used an equally capable 802 standard on which to base their system. Without coexistence assurance between other 802 standards, 802 becomes nothing more than a producer of proprietary systems in this perspective.
In contrast, the 802 process provides an opportunity to present a useful assessment of coexistence characteristics, providing a higher level of confidence to potential adopters. As creators of two of the most widely used wireless standards in the world, we can and should set the standard for the future. We need to be better and hold ourselves to a higher bar.
In the case of 802.11ax, there are many existing uses of 802.15.4 UWB systems and without positive coexistence and interference mitigation mechanisms, 802.11ax will degrade those system's performance and capability. There are no fewer than three major business alliances - the UWB Alliance, The FiRa (Finite Ranging) Consortium, and CCC (Car Connectivity Consortium) all of which are further developing and promoting UWB systems based on 802.15.4. The latter, CCC, has over 200 major company members, including 26 of the world's major car manufacturers. The use of 802.15.4 UWB based technology globally is huge, to say the least, and is being used in industrial, commercial, and consumer spaces, all of which overlap with 802.11. The two technologies offer complementary capabilities, are already being integrated into the same devices, and in combination provide for new opportunities and value to consumers. Positive coexistence is key to realizing this potential value and multiplying the value of RLAN.
While I realize that my comment and vote will not make a difference in the passing of 802.11ax I will continue to raise this issue (providing a positive coexistence assurance analysis and mechanism) on all proposed 802 standards.
Best Regards,
Clint
BR,
Clint
From: Steve Shellhammer <sshellha@xxxxxxxxxxxxxxxx>
Sent: Friday, October 30, 2020 11:51 AM
To: STDS-802-19@xxxxxxxxxxxxxxxxx
Subject: [802.19] EC Document on Chairs Guidelines - Scope of CA Document
All,
Yesterday, the IEEE 802 Rules committee considered the recommended text on the Chairs Guidelines on “The Scope of the Coexistence Assessment Document.” The text was edited based on discussions at the Rules committee.
The 802 Rules chair posted a document, that includes the edited text on Slide 3 of the attached document.
The 802 Executive Committee will consider and vote on these rules changes at the EC closing on November 13.
I wanted to make sure that the 802.19 members and participants could see this document before it is considered at the EC Closing meeting.
Regards,
Steve
To unsubscribe from the STDS-802-19 list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-19&A=1
To unsubscribe from the STDS-802-19 list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-19&A=1