IEEE 802 LMSC Standards Development Criteria Updates
Explore proposed updates to the IEEE 802 LMSC criteria for standards development, focusing on aligning standards with practice and providing evidence of distinct identity. Consider potential changes to enhance clarity and consistency in the standards development process.
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 LMSC Proposed Updates to the criteria for standards development (CSD) 12 November 2022 1 DCN ec-22-0234-00-00EC
Purpose Update to align the CSD as defined in the rules with the practice as performed by 802 WGs Say what you do, so what you say 2
IEEE 802 LMSC Operations Manual 14. IEEE 802 criteria for standards development (CSD) 14.2.3 Distinct Identity Each proposed IEEE 802 LMSC standard shall provide evidence of a distinct identity. Identify standards and standards projects with similar scopes and for each one describe why the proposed project is substantially different. It is not at all clear what this really means and the first sentence and second are inconsistent: first says each standards shall have a distinct identity, yet we apply this to amendments to standards. Often the scope of the project is not Cleary substantially different other than the project amends or revises a different standard In practice, this generally includes little useful information for amendments: E.g. uses a different MAC is deemed a distinct identity (stating the obvious) In practice, there has been very useful examples where the project has made sense and had value despite seeming to be very similar to another project: E.g. 802.15.3 and 802.11 mmWave The Broad market potential establishes the need for the project. At best the unique identity this amends standard x instead of y is a statement of the obvious form the PAR. 3
Proposed Change Option 1: Remove 14.2.3 from the OM Revise the document templates accordingly Check for other ripples Option 2: Modify 14.2.3: Identify standards and standards projects with similar scopes and for each one describe why the proposed project is substantially different. This is consistent with the first sentence: Each proposed IEEE 802 LMSC standard shall provide evidence of a distinct identity 4
