[Hubmib] FW: Draft PAR for revision of P802.3.1

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 02 March 2011 17:34 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: hubmib@core3.amsl.com
Delivered-To: hubmib@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 5A3893A67E1 for <hubmib@core3.amsl.com>; Wed, 2 Mar 2011 09:34:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.528
X-Spam-Status: No, score=-102.528 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id MkaR1roQTdeL for <hubmib@core3.amsl.com>; Wed, 2 Mar 2011 09:34:22 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com []) by core3.amsl.com (Postfix) with ESMTP id BA9AE3A681B for <hubmib@ietf.org>; Wed, 2 Mar 2011 09:34:21 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkUBAFcObk3GmAcF/2dsb2JhbACYAT+OGXSkUQKZRIVhBJAA
X-IronPort-AV: E=Sophos; i="4.62,254,1297054800"; d="pdf'?scan'208"; a="61541566"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 02 Mar 2011 12:35:27 -0500
X-IronPort-AV: E=Sophos; i="4.62,254,1297054800"; d="pdf'?scan'208"; a="588973677"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([]) by co300216-co-erhwest-out.avaya.com with ESMTP; 02 Mar 2011 12:35:26 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01CBD900.2CF63486"
Date: Wed, 2 Mar 2011 18:35:07 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0402D195FA@307622ANEX5.global.avaya.com>
Thread-Topic: Draft PAR for revision of P802.3.1
Thread-Index: AcvVS6U1SHoExnvvTfSfw7OyqCVuHgDrW3vwAADC4qA=
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
X-Mailman-Approved-At: Wed, 02 Mar 2011 09:35:52 -0800
Subject: [Hubmib] FW: Draft PAR for revision of P802.3.1
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hubmib>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 17:34:23 -0000

 If you are interested in participating in the further development of
the Ethernet MIBs my recommendation is to start participating in this
project (P802.3.1)



-----Original Message-----
From: Howard Frazier [mailto:hfrazier@broadcom.com] 
Sent: Wednesday, March 02, 2011 6:45 PM
To: Romascanu, Dan (Dan)
Subject: FW: Draft PAR for revision of P802.3.1


Here it is.


-----Original Message-----
From: Howard Frazier
Sent: Friday, February 25, 2011 4:25 PM
Subject: Draft PAR for revision of P802.3.1

Dear Members of the IEEE 802.3.1 Ethernet MIB modules Task Force,

Attached please find a draft of a proposed PAR for a revision of IEEE
Std 802.3.1 Standard for Management Information Base (MIB) definitions
for Ethernet.

As we are nearing completion of the initial project, it is time to start
the process to initiate a revision to catch the document up so that it
is synchronized and consistent with IEEE Std 802.3 Standard for Ethernet
(love the new title). Please review the draft PAR, and let me know if
you have any comments. I plan to seek approval of this PAR at the
upcoming plenary session, and to have it placed on the June IEEE-SA
Standards Board meeting agenda. 
Since it is a "maintenance" PAR, it need not be circulated to the IEEE
802 EC 30 days in advance of the plenary, and we don't need to work up a
5 Criteria slide deck.

You will note that the scope and purpose statements have been reworded
slightly in order to address comments that came up during the initial
project. We no longer use the words "future"
and "recent", and the purpose has been reworded to make it clear that
only the SNMP modules will be published in machine readable form.

I have been asked why the PAR does not include a list of the specific
amendments to IEEE Std 802.3 that will be reflected in the revision of
IEEE Std 802.3.1. Let me first state that I fully intend to mirror the
set of amendments that are being incorporated into the currently
underway revision of IEEE Std 802.3, which means all approved amendments
through 802.3bg. I believe that this should be captured in the project
objectives, rather than the PAR, because I don't want to have to go
through the process of changing the PAR in the event that we later
decide to deviate from this plan.
This is how we did it for the initial project, and I think it should
work just fine for the revision. I will send out a draft set of project
objectives shortly.

I look forward to meeting with you in Singapore.

Howard Frazier
Broadcom Corporation
Chair, IEEE 802.3.1 Ethernet MIB modules Task Force