[Hubmib] FW: Reviewed 802.3af MIBs

"Romascanu, Dan \(Dan\)" <dromasca@avaya.com> Mon, 31 October 2005 12:48 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EWZ5q-0007g8-IG; Mon, 31 Oct 2005 07:48:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EWZ4I-00073r-43 for hubmib@megatron.ietf.org; Mon, 31 Oct 2005 07:47:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04724 for <hubmib@ietf.org>; Mon, 31 Oct 2005 07:46:56 -0500 (EST)
Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EWZIL-0000Zo-Ls for hubmib@ietf.org; Mon, 31 Oct 2005 08:01:55 -0500
Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j9VCX4C3005700 for <hubmib@ietf.org>; Mon, 31 Oct 2005 07:33:04 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j9VCWnC3005434 for <hubmib@ietf.org>; Mon, 31 Oct 2005 07:32:50 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C5DE19.27BE61DC"
Date: Mon, 31 Oct 2005 14:46:47 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F09658973@is0004avexu1.global.avaya.com>
Thread-Topic: Reviewed 802.3af MIBs
Thread-Index: AcXd4x4FH6QoPVSHR6C1wQoFDRayDwAFbH1Q
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Hub MIB <hubmib@ietf.org>
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 2d92b22c5caa2a53a313a843b91375a0
X-Mailman-Approved-At: Mon, 31 Oct 2005 07:48:51 -0500
Subject: [Hubmib] FW: Reviewed 802.3af MIBs
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

 


 

-----Original Message-----
From: David T. Perkins [mailto:dperkins@dsperkins.com] 
Sent: Monday, October 31, 2005 8:18 AM
To: Wijnen, Bert (Bert)
Cc: Romascanu, Dan (Dan)
Subject: Reviewed 802.3af MIBs

HI,

Attached are the reviews for the MIB module documents.

In general, I don't believe that the modules were ready for review.
Also, the IEEE 802.3af has resulted in 3 documents (and maybe 4, if you
count the mau MIB 3636bis I-D). However, these documents do not seem
coordinated with each other or coordinated with other interface types
that have come from the 802.3 document family.

I'm sorry I took so long. The job was difficult, and I'm sure that I
spent over 40 hours on this job and several hours on the phone to Loir
in Israel. There were many times that I was confused and came to
incorrect conclusions, and had to restart. Note that taking the IEEE
CMIP GDMO and converting to IETF MIB modules is never easy due to the
differences between SNMP and CMIP modeling and due to the complex IETF
interface modeling (which has been somewhat of a moving target).

If I wasn't clear in any of my comments, please send questions.

Regards,
/david t. perkins

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib