All – we are going to have a discussion on the scope statement at the rules meeting. Not that you can’t discuss on the reflector – just letting you know.
George Zimmerman, Ph.D.
President & Principal
CME Consulting, Inc.
Experts in Advanced PHYsical Communications
george@xxxxxxxxxxxxxxxxxxxx
310-920-3860
From: Gaurav Patwardhan <gauravpatwardhan1@xxxxxxxxx>
Sent: Thursday, July 2, 2026 11:10 AM
To: George Zimmerman <george@xxxxxxxxxxxxxxxxxxxx>
Cc: STDS-802-LMSC@xxxxxxxxxxxxxxxxx
Subject: Re: [802-LMSC] Nikolich comments on the proposed LMSC P&P updates
Hi Paul, George,
I am not the expert here, but I believe we should not remove the 'advocate for them on a global basis' text, because we have a 802 LMSC Public Visibility Standing Committee and 802.18 RR-TAG, both of which have scope built around external facing advocacy.
Regards,
Gaurav
Thanks, Paul – I was going to begin drafting today, so you’re not late.
George Zimmerman, Ph.D.
President & Principal
CME Consulting, Inc.
Experts in Advanced PHYsical Communications
george@xxxxxxxxxxxxxxxxxxxx
310-920-3860
I know I'm late, but here is my input so far:
a) 1.6 Scope -- The draft wording needs polishing.
Currently: "The scope of the Standards Committee is to develop and maintain networking standards, recommended practices and guides
for local, metropolitan, and other area networks, and associated technologies, using an open and accredited process, and to advocate them on a global basis."
I suggest: "The scope of the Standards Committee is to
provide oversight for the development and maintenance of local, metropolitan, and other area network standards, recommended practices and guides,
and associated technologies, using an open and accredited process, and to advocate
for them on a global basis."
Rationale: IEEE 802 LMSC does not develop technologies. Advocation shouldn't be in the Scope -- it's an ancillary support function.
Currently: "The Standards Committee is responsible for the development and coordination of one or more standards projects including
their maintenance after their approval as standards by the IEEE SASB."
I suggest: "The Standards Committee is responsible for
oversight over the development and coordination of one or more standards projects including their maintenance after their approval as standards by the IEEE SASB.
c) 2.2 Dominance/3. Officers
Currently: "3. The votes of individuals in the dominating party are treated as a single vote for
the purpose of that activity. Officers"
This should be split -- "The votes of individuals in the dominating party are treated as a single vote for
the purpose of that activity" belongs to the previous line.
3. Officers should be a header
Change "by IEEE Computer Society Standards Activities Board (SAB)" to "by IEEE Computer Society Standards Activities Board (CSAB)"
and update every occurrence of SAB with CSAB.
That's it for now. Happy Independence Day!
------ Original Message ------
Sent: 6/29/2026 1:13:48 PM
Subject: [802-LMSC] reminder - any comments on the proposed LMSC P&P updates?
I had asked for any comments on the proposed LMSC P&P updates (aligning with the new Audcom template) to be emailed to me (or the reflector)
by July 1 in order to aide in my reformatting the draft. I have seen none to date. (see
https://www.ieee802.org/email/stds-802-lmsc/msg01063.html for the request and the the document links).
Advance notice of comments, so that I may note them when I reformat, would be greatly appreciated.
George A. Zimmerman, Ph.D.
2nd Vice Chair, IEEE 802 LAN/MAN Standards Committee
CME Consulting, Inc.
george@xxxxxxxxxxxxxxxxxxxx
1-310-920-3860
To unsubscribe from the STDS-802-LMSC list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-LMSC&A=1
To unsubscribe from the STDS-802-LMSC list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-LMSC&A=1
To unsubscribe from the STDS-802-LMSC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-LMSC&A=1
|