All, During the comment resolution (for IEEE Std 802 REVc) in May, 802.11’s ARC committee took an action to work on the definition of IEEE 802 Network, in particular to address concerns raised about what “could not/should not” be in the definition, because some 802 Std (often 802.11) did not strictly adhere to the proposed language. As a result of our deliberations, we have ended up focusing on the purpose of 802 standard networks (to deliver data to end stations (as defined in IEEE Std 802)) and that the one thing we can see that is common to all 802 networks is that they use IEEE 802 MAC Addresses. (Everything else that has been tried to be a ‘distinguishing factor’ seems to fall on some shaky ground that it might not necessarily be true.) So, here’s what we (802.11 ARC) have as a suggestion, for discussion in the comment resolution meeting tomorrow: IEEE 802 ® network: an interconnected group of two or more devices that forward data between end stations that are identified by IEEE 802 MAC addresses. Please consider, comment, etc., and let’s hope we can find a consensus way forward tomorrow morning. Thanks! Mark From: ***** IEEE 802 Executive Committee List ***** <STDS-802-SEC@listserv.ieee.org> On Behalf Of ROBERT GROW
Sent: Monday, July 10, 2023 12:18 PM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] Definitions for IEEE 802 Network and IEEE 802 Family of standards Geoff, I favor some kind of change like James noted. Historically, there have been a number of standards developed to be compatible with Std 802 and use 802.1 bridging. Power Line networks were one. FDDI used 802 addresses and other than the challenge of frame length, were very compatible with bridging to LMSC specified networks. I also think it is important to distinguish between standards developed within LMSC and elsewhere. I think it is prudent to keep the door open for compatible innovation to happen outside of LMSC, and to preserve the ability for Std 802 to recognize that possibility. —Bob
I don't see any reason to change: IEEE 802® network: A network consisting of one or more interconnected networks each using a medium access control (MAC) protocol specified in
(Even though I can see some flaws in it, e.g. a Dot3 network with a proprietary PHY and media.) On Saturday, July 8, 2023, 12:35:32 AM PDT, Clint Powell <cpowell@ieee.org> wrote: James, While the quality of this mercy may not be strained, I know you're just waiting with bated breath on this one. I , for some very obvious reasons, would strongly object to going with any definition that would preclude anything (standard, recommended practice, etc.) developed within IEEE 802. I'm also not too keen on blanketly including anything not developed within IEEE 802 as well.
The current or less controversial suggestion would be the more appropriate choices. Best Regards,
Clint
Clint Powell
Director - Global Head of Standards Alliances, PACS Mobile @ HID
IEEE 802.15 WG Chair & 802 LMSC Executive Committee
+1 (480) 586-8457 On Sat, Jul 8, 2023 at 12:13 AM, James P. K. Gilb One of the last comments remaining has to do with the definitions of IEEE 802 Network and IEEE 802 Family of standards. It has been suggested that an IEEE 802 Network should be all networks that can be bridged together, including those that do not use and IEEE If we adopt this definition, some outside networks would be included and some IEEE 802 standards would be excluded (e.g., IEEE 802.15.4 due to 64 bit addressing, at the present). The current definition in the published standard is: IEEE 802® network: A network consisting of one or more interconnected networks each using a medium access control (MAC) protocol specified in I don't have proposed text for the alternative definition, but it might One or more interconnected networks that use IEEE 802.1Q bridging. The suggested definition for the IEEE 802 Family of Standards is, perhaps, less controversial, that it is the collection of standards created by the IEEE 802 LAN/MAN standards committee. This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
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 |