| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
On Mon, Jul 5, 2021 at 12:07 PM, George Zimmerman<george@CMEPHYCONSULTING.COM> wrote:Paul & Roger –
I appreciate the work that went into the new proposal; however, I do not find myself supportive of it, and, in fact, somewhat opposed. This comes primarily from the first point below, which is fundamental to the new proposal; however, I also have concerns about the proposal overstepping its bounds.
The new proposal relies heavily on a definition which is 802 jargon. It is extremely important that the scope and purpose be understandable to those outside the group itself. More specifically, it must be well-defined outside jargon which might be used in a group – otherwise the scope and purpose become at best difficult to understand, and at worst self-referential. “access domains” as you state, is a term used in 802. It was such an obscure usage that you had to cite how many times it was used. Therefore, it doesn’t provide clarity at all.
The second issue is that I believe the proposal goes well beyond scope and purpose of 802 and attempts to impose a structure on the 802 working groups. The scope and purpose of the overall standards committee is not the place to define its structure or governing principles. That is for other parts of the governing documents. Perhaps this is a mistake, perhaps it is on purpose; however, if the phrase (“developed by Working Groups responsible for medium access control, are specified for transmission of frames within an access domain”) was intended in any sense to state that the organization of a working group was along “medium access control”, and “an access control”, both in the singular, was meant to define what the coverage of a working group would be, I would say that is inappropriate. There seems no need to mention “Working Groups” within the scope and purpose at all. They are an organizational aspect of how the standards committee (under the IEEE-SA) organizes its work, and, the scope of WGs is subject to review and may be changed by the standards committee & working group (with approval by the standards committee) under our P&Ps. The scope of the overall standards committee is just the wrong place to mention this.
It is important that a scope and purpose statement be just specific enough to limit let people outside know WHAT the group does, and not so-specific that it steps into the HOW the group does it – that is the realm of policy and procedure. I feel that the ‘new proposal’ provides far more detail than is warranted, and does so in an internally-encoded way that reduces clarity when viewed outside of specific 802 documents.
-george
From: ***** IEEE 802 Executive Committee List ***** <STDS-802-SEC@LISTSERV.IEEE.ORG> On Behalf Of Paul Nikolich
Sent: Thursday, July 1, 2021 8:41 AM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] Action Item: 802 Mission and Purpose
Roger,
Thank you for the background and status update on the 802 LMSC Mission/Purpose action item.
The alternative mission/purpose text you and Geoff have crafted looks good (copied below). I am interested to hear what our 802 EC colleagues think.
Regards,
--Paul
Consequently, Marks and Thompson propose the following alternative mission/purpose text:
IEEE 802 develops and maintain standards specifying data link layer and physical layer protocols to support packet transmission and delivery among network-layer clients. (1) Protocols, developed by Working Groups responsible for medium access control, are specified for transmission of frames within an access domain with sufficient detail to allow multivendor interoperability across the interfaces to the communication medium.
(2) Interoperability is also specified for transmission of frames via a network of such access domains, including bridging.
Supplementary specifications detail related functionality, including control, management, discovery, synchronization, security, channel coexistence, and power distribution. Supporting outputs include future-looking documentation, standards body interactions, and regulatory contributions.
------ Original Message ------
From: "Roger Marks" <r.b.marks@ieee.org>
Sent: 6/25/2021 4:16:34 PM
Subject: [802SEC] Action Item: 802 Mission and Purpose
Per the minutes of the 1 June 2021 802 LMSC EC meeting, I was assigned an Action Item
-lead the building of consensus for the 802 LMSC Mission/Purpose text in the 802 Chair’s Guideline
To advance this action, I have posted a document entitled "Action Item: 802 Mission and Purpose":
https://mentor.ieee.org/802-ec/dcn/21/ec-21-0143-00-00EC.pdf
This document:-summarizes the background of the Action Item
-reproduces versions of the statement that have been previously circulated
-proposes a new version of the statement
-requests comment via the reflector
-indicates that I will provide an update at the 23 July EC meeting
-indicates that a meeting will be scheduled at that time, if warranted
Cheers,
Roger
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
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
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
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