Re: [802SEC] P802f and Wake on LAN normative annex
- To: STDS-802-SEC@LISTSERV.IEEE.ORG
- Subject: Re: [802SEC] P802f and Wake on LAN normative annex
- From: Glenn Parsons <00000f6f9e80d40c-dmarc-request@LISTSERV.IEEE.ORG>
- Date: Thu, 13 Jul 2023 09:59:17 +0000
- Accept-language: en-US
- Arc-authentication-results: i=2; mx.google.com; dkim=pass header.i=@ericsson.com header.s=selector1 header.b=aKslQ8eD; arc=pass (i=1 spf=pass spfdomain=ericsson.com dkim=pass dkdomain=ericsson.com dmarc=pass fromdomain=ericsson.com); spf=pass (google.com: domain of glenn.parsons@ericsson.com designates 40.107.237.71 as permitted sender) smtp.mailfrom=glenn.parsons@ericsson.com
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
- Arc-message-signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:content-transfer-encoding:content-language :accept-language:in-reply-to:references:message-id:date:thread-index :thread-topic:subject:to:from:dkim-signature; bh=/M3zmV/BAkpsa77z12Xx/drUvkKko4fpBObi5UvP6NA=; fh=5QbGCnyszCMgeuXH+UloGlSKsiabdaaf8vGhW4A1mXk=; b=vpw7gd8fYzH5IG136BybgWP9LB1HSAnVF8qPzuCyozabsE870H78vcHKsZuJDD2nnw 0Qbhyc4tsLsq9h9vfrTofRZp1cpLpV3y6jiFCg2t+WRjFhmypc3vu+x2TfYEUcHmYcAE k5aWLoVeFZn7hghMNK0rsFvsvdfHOBAkr8jZ0ZP+o5yQOsp2/iZNHQYCXsc5CzP5TJyO uHQ+KmgVThAWBsr9OE0ExZFmrjpq7tlYsu0m515Td1/9eSQnPBV3QFmVU6i0JtjqVMZz ugiSr7EUj4y9X6rxx2K6Ur3G20I6oXW7X4APJ0V27+qwrVsyiNyOlmRc/a7URRb4605o cfQg==
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=/M3zmV/BAkpsa77z12Xx/drUvkKko4fpBObi5UvP6NA=; b=IqNdmsKX+3k5gOMMJrZolnq7c/W/ZSN6A9/dkOHWdeGYqtufyQfEyvJAZveXGsM60cvkvvFx7rTk/OemGWKMZdeD73jJ7u/dlFFJvO9xpBVFwSjFGE2JyM2he3/HDItOLsulPDhso/xxb/eIc8ZxADd6j3ZZ0sH8RRlWAMfF2ZtOomx++kDBiMyfvPZHpoiaLj+wce3iaBUWoJ9WiEKZRLQcjCp+7DhEHXouScS2pmq8cAhGvf/LR/xzyqquuj8PZgSLL0BMipzPprxIUcTNrRAuC11FrMG6XOuECMEBhU/TN8MF4IKO9B0wtsJTrNY5ZOTLDEmLC+KomlgGJ3i3bg==
- Arc-seal: i=2; a=rsa-sha256; t=1689242363; cv=pass; d=google.com; s=arc-20160816; b=Iob+NoHZ/jeVoP296fwiDIzzepgufxm7Lp5uIX3R31lmmm68Of1R3vWDj2V0U941YJ zFQwAm1pVsWlEInyCstlW9fUrNA5bP/1uaPVBjHjel/59d+QbvAVjX9od/E9W7aKI8yw u4Q1qnspsjRz6oK6Nz2a0DoPtVsT294dADBke38KRa9AlQ1VnPu5xe6TmSrOBcot2BMp qu0yuoODUGGY3I9VFBd7YjoilDipwGnixH+PlbaMPcJ6jL20cukgac6cAJaqnAwECAeo Yd5vMxo6w7YC6C7T9qwINlIHgwlZjsVEEQrTNoQMWnHL4X1laf9ANp4uKty0M1bEc3pW PwFQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=QMUSBUmIgCnAaU/xydXE/BNtPEMIuwDJoHaOWkYURm0F2/jvjA3bYPq3sZrFMHWgObg6f62GEwSoeS16aHtTBFhLAd6Wr0LgCJWPYhbYbN0Fa7pFv0qzM7ciCiZm5BPjCGcXjjPH3gLBK+dfWdUr8ogjz+BSzrI7bN76ZFZV9wMAGNbcguINm180M9hCRGyez5gdJEt5sT7Z9B2n4DfKldaeqnDQc+0sjCHvym8bcWimIuZVQLIdMmWWAZWaho3k4ErUSJsSp/y5D1fEDi60VtMZqgLP5jn5Txd4EchUqSV256NrYwQCi3lbGNllNL0rULc5mj49vW9kS0zbpIleSg==
- Delivered-to: mhonarc@GROUPER.IEEE.ORG
- Delivered-to: STDS-802-SEC@listserv.ieee.org
- In-reply-to: <579f0405-833a-950a-f41d-bc7fc2c4eb5f@ieee.org>
- List-help: <https://listserv.ieee.org/cgi-bin/wa?LIST=STDS-802-SEC>, <mailto:LISTSERV@LISTSERV.IEEE.ORG?body=INFO%20STDS-802-SEC>
- List-owner: <mailto:STDS-802-SEC-request@LISTSERV.IEEE.ORG>
- List-subscribe: <mailto:STDS-802-SEC-subscribe-request@LISTSERV.IEEE.ORG>
- List-unsubscribe: <mailto:STDS-802-SEC-unsubscribe-request@LISTSERV.IEEE.ORG>
- References: <579f0405-833a-950a-f41d-bc7fc2c4eb5f@ieee.org>
- Reply-to: Glenn Parsons <glenn.parsons@ERICSSON.COM>
- Sender: ***** IEEE 802 Executive Committee List ***** <STDS-802-SEC@LISTSERV.IEEE.ORG>
- Thread-index: AQHZtVaZeRMTjJeFkUOZ0AuEO56O0q+3Z1Cg
- Thread-topic: [802SEC] P802f and Wake on LAN normative annex
Thanks for your concern James,
For everyone's benefit, the background as indicated in the PAR, is that IETF requested the creation of this YANG module, to replace their RFC 8519. Upon coordination with the RAC it was discovered that the widely used Wake on LAN EtherType was not registered. The IEEE RA assigned it to IEEE 802.1 to allow the definition of the YANG module in P802f.
The RAC wanted to have a reference with the frame format, which resulted in the description in an informative Annex. The WG felt that including an informative frame format for this EtherType was in scope of the P802f PAR, but any protocol definition would not be. As a result, a PAR modification was not made before SA ballot.
An MBS SA ballot comment (I-34) asked to make Annex G normative. The comment resolution group agreed, and D2.1 that was recirculated included this change. There were no comments on this change.
It is my understanding that at the SA ballot stage, the comment resolution group determines if the document is within the scope of the PAR. As a result, I believe the process has been followed.
Cheers,
Glenn.
-----Original Message-----
From: ***** IEEE 802 Executive Committee List ***** <STDS-802-SEC@listserv.ieee.org> On Behalf Of James P. K. Gilb
Sent: July 13, 2023 2:42 AM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: [802SEC] P802f and Wake on LAN normative annex
All (Glenn, please forward this to the appropriate 802.1 list)
You may be surprised to find P802f added a normative annex with a frame format for the (undefined) Wake-on-LAN protocol.
Especially as the scope of the project is to add "YANG modules that contain the EtherType information" and "addresses errors and omissions in IEEE Std 802 description of existing functionality." (full scope below).
Glenn was kind enough to explain the reasons why the group decided to add this normative Annex. However, the reasons why the group made this decision is not relevant to my concern.
My concern is that the project has clearly exceeded its scope. Based on my limited understanding of the rules, when the group realized that they were going to exceed the scope, they should have either:
1) Declined to add the content, or
2) Modified the PAR scope to add "define frame formats for Wake-on-LAN".
I don't think the LMSC should forward this draft to RevCom until one of the two above actions is taken. Modifying the PAR will mean reforming the ballot pool and restarting SA ballot. But that is the point, as interested parties reading the title and scope would not know that the definition of frame formats for Wake-on-LAN is part of the project and so would not have joined the SA ballot pool.
At this point, I intend to vote against conditional forwarding P802f to RevCom.
James Gilb
Full scope of P802f:
This amendment specifies YANG modules that contain the EtherType information, including a compact human-readable name and description.
The name and description for an initial set of EtherTypes are defined for inclusion in the IEEE Registration Authority EtherType public listing. This amendment also addresses errors and omissions in IEEE Std
802 description of existing functionality.
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.