My apologies I provided some incorrect information at today's ARC SC teleconference.
P802-REVc did have a comment resolution meeting since our 802.11 May Interim Meeting on Wednesday 31 May 2023 @ 11:00 h ET. Unfortunately, I didn’t attend the meeting, as I was not aware that it was happening (I had a Microsoft Outlook
issue with the online calendar not updating properly). A summary of the CID resolutions updated follows below. Please note that CID 98 is related to the definition of IEEE 802 Network.
The next P802-REVc meeting is scheduled for 20 June 2023 @ 11:00 h ET, please see the IEEE 802 and Subgroup Calendars for meeting details (https://www.ieee802.org/802tele_calendar.html).
Summary of discussions/decisions from the 31 May 2023 P802-REVc comment resolution meeting (1-23-0015-01:
- CID 81 – a comment fixing the “little b”/”Big B” use of bridge in the standard.
At the end of the May Interim the Editor was to prepare of list of changes to either “bridge” or “IEEE Std 802.1Q Bridge” – but additional comments were received from Parsons that this was not a clear task, as it is not clear what should change.
New direction – the commenter will be requested to provide specific changes.
This CID is still open. - CID 98 - Comment: The draft says that "An IEEE 802 network is required, at a minimum, to support the MAC Internal Sublayer Service specified in IEEE Std 802.1AC and support
the use of EtherTypes for protocol identification at the LLC sublayer." Is this a requirement to belong to the "family" of IEEE 802 standards? It appears that not all IEEE 802 standards have convergence functions detailed in IEEE Std 802.1AC.
Suggest Revised – Change “IEEE 802 network” to be “IEEE 802 Network” when referring to compliant networks throughout the draft. Change the definition of IEEE 802® network: to be “IEEE Std 802® Network: A network that provides services via the MAC SAP
in accordance with the ISS of 802.1AC.”
Editor to confirm this is acceptable to all 802 WGs. - CID 122: Add normative 802.1Q reference.
Comment: IEEE Std 802.1Q is not a normative reference as it is not cited in any normative requirement. The closest thing is a "should" in 8.4.2 which refers to annex F (informative) of 802.1Q. Throughout it is used in informative, not normative, statements.
It is properly listed in the bibliography.
Rejected: Subclause 8.4.2 is normative per 12.1 of the style manual (and 6.4 of SASB OpsMan), regardless of F.1.2 being informative in 802.1Q. The statement in 802 is normative, regardless of whether its target is normative or informative in the referenced
document. In addition, 5.3.2.1 is also normative. The text "A bridged IEEE 802 network consists of..." is effectively equivalent to "A bridged IEEE 802 network shall consist of..." And the previous sentence indicates that 802.1Q defines bridge. - CID 146 LSB/MSB
Revised with text in
1-23-0015-01 (extra “most” removed).
Regards,
Joseph
To unsubscribe from the STDS-802-11-ARC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-ARC&A=1