IEEE 802 Restructuring Ad Hoc Problem Statement and Architecture Group Overview
"Explore the historical context and current issues surrounding the IEEE 802 restructuring ad hoc problem statement and architecture group. Delve into their objectives, meetings, known issues, and ongoing efforts for technical coherence."
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
IEEE 802 Restructuring ad hoc Problem Statement: Technical Coherence Roger Marks and Glenn Parsons* *pending final review 2021-03-16 802-ec-21-0068-00-00EC
Maintaining Coherence: Historical IEEE 802 Plenary Meeting Formerly held on Monday morning at IEEE 802 Plenary IEEE 802.1 WG has, for decades, offered to organize a Technical Plenary meeting on cross-WG architectural issues Has not been held in recent memory (around 20 years) Joint topical coordination meetings, generally during IEEE 802 Plenaries IEEE 802 Architecture Group (see below) IEEE Std 802, Overview and Architecture 1990; revisions 2001 and 2014; third amendment in progress Coordinated meetings to develop 2014 revision Some issues arise in 802/IETF coordination discussions Criteria for Standards Development
IEEE 802 Architecture Group: 2004-2006 https://www.ieee802.org/1/files/public/802_architecture_group/ Intent: Improve alignment between WG projects and existing 802 architecture by: Identifying current problems, omissions, conflicts, ramifications, and their potential resolution Identifying potential refinements or changes to the architecture Providing a regular forum in which such discussion can take place, in a lower pressure environment than is possible during the core Plenary cycle. Meeting: Sunday 2-5 PM before 802 Plenary Identifying current problems, omissions, conflicts, ramifications, and their potential resolution (no formal output documents) Chaired by 802.1 Chair Ended after 7 Plenaries no longer useful in its current form If there is a need for the group to meet in order to address a specific and focussed problem then we will schedule an ad-hoc Architecture group meeting for that purpose. The best placing for this would be to use a Plenary tutorial slot. The 802.1 Technical Plenary will still be available as a vehicle for addressing specific technical problems across 802.
IEEE 802 Architecture Group: known issues 57 slides in final slide set QoS, CoS, security, management, MAC service definition, MIB, frame size, location awareness, link aggregation, dual homing, synchronization, rate control, congestion management, latency, power management, wake-on-LAN, WLAN bridging, 64-bit bridging, LLC, wireless mesh, soft handover, multicast, authentication, service discovery Many of these topics are not yet closed. Some were addressed with large efforts, such as 802.11ak & 802.1Qbz New topics have arisen; e.g. YANG, local MAC addressing, automotive, industrial, factory, aerospace, data center, etc.
Current Situation IEEE 802 LMSC P&P: Approval for moving a draft standard to Sponsor ballot, or approval of any substantive change in the scope of a standard proposed by a subgroup, shall be referred to the Sponsor for approval. The Sponsor may delegate approval authority and form a subgroup for this purpose. Approval to move a standard to Sponsor ballot from such a subgroup requires a majority vote. This vote shall be limited to procedural issues and PAR alignment only. IEEE 802 LMSC Operations Manual: The LMSC provides procedural and, if necessary, technical guidance to the Working Groups and TAGs as it relates to their charters. oversees Working Group and Technical Advisory Group operations to ensure that it is within the scope of IEEE 802 LMSC, and its established charter. 5C: Each proposed IEEE 802 LMSC standard should be in conformance with IEEE Std 802, IEEE 802.1AC, and IEEE 802.1Q. If any variances in conformance emerge, they shall be thoroughly disclosed and reviewed with IEEE 802.1 Working Group prior to submitting a PAR to the IEEE 802 LMSC.
Going forward 802 wide technical coherence is warranted To reduce duplicative efforts To add functionality to networks To increase commonality as seen by higher layers To strengthen the meaning of the brand and of an IEEE 802 Network Are we a family of standards, or just roommates? Technical coordination needs a regular venue LMSC Architecture Standing Committee Potentially scheduled without conflicting WG meetings Potentially tasked to review/recommend draft standards prior to EC motion IEEE Std 802 revision project More explicit architectural details Conformance matter and PICS
