Re: [802SEC] +++ EC Consent Agenda 7 February 2023 - IEEE 802.3 items - request +++
Hi Glenn,
If you define new functionality only based on the addition of a new SMIv2 or new YANG module, they will. I would, however, note that each IEEE 802.3 amendment includes updates to the IEEE 802.3 protocol agnostic MIBs as required. These two IEEE 802.3 maintenance projects will be to update the SMIv2 (IEEE P802.3.1) and YANG (IEEE 802.3.2) modules based on the already published protocol agnostic MIBs. I, therefore, consider these projects as maintenance as they are 'roll-ups' of previously approved amendments to the protocol agnostic MIBs cast into the specific languages of SMIv2 and YANG.
Best regards,
David
-----Original Message-----
From: Glenn Parsons <glenn.parsons@ericsson.com>
Sent: 02 February 2023 17:12
To: Law, David <dlaw@hpe.com>; STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: RE: [802SEC] +++ EC Consent Agenda 7 February 2023 - IEEE 802.3 items - request +++
David,
Do these revision PARs include the addition of new functionality (e.g., new YANG or MIB modules) to support recent 802.3 amendments?
My reading of the PARs is that they do.
Cheers,
Glenn.
-----Original Message-----
From: ***** IEEE 802 Executive Committee List ***** <STDS-802-SEC@listserv.ieee.org> On Behalf Of Law, David
Sent: January 30, 2023 3:48 PM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: [802SEC] +++ EC Consent Agenda 7 February 2023 - IEEE 802.3 items - request +++
Hi John,
I'd like to request the following two IEEE 802.3 items be placed on the Tuesday 7th February 2023 consent agenda.
Subclause 9.2 of the IEEE 802 Operations manual says that 'At the discretion of the IEEE 802 LMSC Chair, PARs for ordinary items (e.g., Maintenance PARs) and PAR changes essential to the orderly conduct of business (e.g., division of existing work items or name changes to harmonize with equivalent ISO JTC-1 work items) may be placed on the IEEE 802 LMSC agenda if delivered to IEEE 802 LMSC members 48 hours in advance.
I believe that we have allowed maintenance PARs to be approved at EC telecons in the past based on the above. As a result, Paul has agreed to place these items on the agenda, but Paul has also asked James to confirm there isn't a rules issue with doing this. I'm therefore placing these two items on the agenda but will pull them off the agenda if James identifies an issue.
Thanks, and best regards,
David
-----
ME: IEEE P802.3.1 (IEEE 802.3.1b) Standard for Ethernet - Structure of Management Information version 2 (SMIv2) Data Model Definitions revision PAR to NesCom
Motion:
Approve forwarding IEEE P802.3.1 (IEEE 802.3.1b) PAR documentation in <https://mentor.ieee.org/802-ec/dcn/23/ec-23-0016-00-00EC-ieee-p802-3-2-ieee-802-3-2a-draft-par-response.pdf > to NesCom
Move: Law
Second: D'Ambrosia
Working Group vote:
Y:101 N:0 A:3
-----
ME: IEEE P802.3.2 (IEEE 802.3.2a) Standard for Ethernet - YANG Data Model Definitions revision PAR to NesCom
Motion:
Approve forwarding IEEE P802.3.2 (IEEE 802.3.2a) PAR documentation in <https://mentor.ieee.org/802-ec/dcn/23/ec-23-0016-00-00EC-ieee-p802-3-2-ieee-802-3-2a-draft-par-response.pdf > to NesCom
Move: Law
Second: D'Ambrosia
Working Group vote
Y:93 N:0 A:3
----------
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.