|Thread Links||Date Links|
|Thread Prev||Thread Next||Thread Index||Date Prev||Date Next||Date Index|
Andrew & all – thank you for the good discussion yesterday.
It is unlikely I will make the next meeting, due to a conflict with an NEC codemaking panel that I am on. While we didn’t get through my contribution in entirety, we had some good discussion. I would suggest that you schedule other contributions first, and if I am able to make the meeting, we could just go to discussion of slide 5. You all can review the rest of the written contribution (offline), and I suspect those items are more self-explanatory, tactical, and noncontroversial; however, the last slide gets to what I think is the heart of what I believe is essential to our future meeting vision – flexibility, trust in our chairs, and support (training where needed) for them to make the adjustments necessary for their group.
We touched on this yesterday, but even before having to have virtual meetings, flexibility to the individual group’s needs, trust in, and support of our chairs is key.
My experience has been 802 has been tripping over itself because of overly codified rules. Governing rules are not a standard, nor are they a specification. To do that leads to situations where the desired behavior is always an exception to the rule. We must resist our engineering urge to codify everything, as the operational environment is far more diverse and time-variable than we can handle.
Rules are important tool, but the goal is to remember that we are dealing with humans who want to get a job done, and the best way to do that is balance the structure of rules with guidance, trust, and mentorship of our leaders – and to evolve them with time and circumstance. I have more thoughts on this, but, because they evolve, I will save them until we’ve gotten more of the examples out.
Thank you for those (all bcc’ed) who attended today’s IEEE 802 Future meeting vision ad hoc. The agenda a notes from today’s meeting are in ec-21-0227-04.
Given we have at least one more submission in the hopper (from Ben Rolfe), I propose we have another one hour session in two weeks’ time, but one hour later to avoid clashing again with 802.18 WG. I will send the invitation shortly.
The short term goal of these discussions is to focus on:
Submissions are requested. It is easy to criticise, and so if you highlight remote-only has not worked for some activity, please put some real effort into proposing a way to fix the identified issue(s). Also please focus on actual examples rather than strawmen. So far we have had submissions from:
Would anyone else like to volunteer to present their experiences?
I would like to undertake more discussion off line, and to this end I will consult with the IEEE 802 EC leadership on how they would like to do this, in a manner that is open and yet does not fill the IEEE 802 EC reflector.
To unsubscribe from the STDS-802-SEC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-SEC&A=1