Re: [Entmib] WG Last Call: Entity State MIB
Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de> Wed, 09 July 2003 15:14 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04694 for <entmib-archive@lists.ietf.org>; Wed, 9 Jul 2003 11:14:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aGdE-0001DJ-N3; Wed, 09 Jul 2003 11:13:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aFaM-0004La-PJ for entmib@optimus.ietf.org; Wed, 09 Jul 2003 10:06:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01331 for <entmib@ietf.org>; Wed, 9 Jul 2003 10:06:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aFaK-0006pc-00 for entmib@ietf.org; Wed, 09 Jul 2003 10:06:16 -0400
Received: from agitator.ibr.cs.tu-bs.de ([134.169.34.18]) by ietf-mx with esmtp (Exim 4.12) id 19aFaJ-0006pZ-00 for entmib@ietf.org; Wed, 09 Jul 2003 10:06:15 -0400
Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian-6.4) with ESMTP id h69E68Kb018783 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 9 Jul 2003 16:06:08 +0200
Received: from hansa.ibr.cs.tu-bs.de (schoenw@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian-6.4) with ESMTP id h69E68Sk021481; Wed, 9 Jul 2003 16:06:08 +0200
Received: (from schoenw@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian-6.4) id h69E67kt021478; Wed, 9 Jul 2003 16:06:07 +0200
Date: Wed, 09 Jul 2003 16:06:07 +0200
Message-Id: <200307091406.h69E67kt021478@hansa.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: mrw@windriver.com
CC: entmib@ietf.org
In-reply-to: <5.1.0.14.2.20030708083046.0385f7f8@mail.windriver.com> (message from Margaret Wasserman on Tue, 08 Jul 2003 08:35:34 -0400)
Subject: Re: [Entmib] WG Last Call: Entity State MIB
References: <5.1.0.14.2.20030708083046.0385f7f8@mail.windriver.com>
X-IBRFilter-SpamReport: -9.9 () IN_REP_TO,REFERENCES
X-Scanned-By: MIMEDefang 2.24 (www . roaringpenguin . com / mimedefang)
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=unsubscribe>
List-Id: IETF Entity MIB WG <entmib.ietf.org>
List-Post: <mailto:entmib@ietf.org>
List-Help: <mailto:entmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=subscribe>
>>>>> Margaret Wasserman writes: Margaret> This is an Entity MIB working group last call for comments Margaret> on advancing the following document as a Proposed Standard: I have read draft-ietf-entmib-state-01.txt and I generally like this document. Below are some comments, many of them are editorial, others ask for more discussion of relationships to other MIBs. But I also understand that this can be done later when the document is revised. a) Typo in section 2: "so this term us substituted". b) Typo in section 2.1: "interesting issues not addresses in existing work" c) Typo in section 2.2: "It also compare this combination of states" d) state 'lock' for entStateAdmin of a container? e) entStatAdmin is actually entStateAdmin f) state 'active' for entStateUsage of a power supply? g) state 'active' for entStateUsage of a fan? h) Relationship of the entState* objects to the dot1dStpPortEnable of the BRIDGE-MIB? i) Relationship of the entState* objects to the hrDeviceStatus of the HOST-RESOURCES-MIB? j) Relationship of the entState* objects to the objects using the SubUnitStatus TC of the Printer-MIB? k) Is my understanding correct that alarmOutstanding(5) of the AlarmStatus TC is set when at least one of critical(2), major(3), minor(4), warning(6), indeterminate(7) is set? If not, the explanation can probably improved. ;-) l) Implementation of the notifications is unconditionally optional? m) In the security section, you may want to explain that access to the objects defined in this MIB allows to figure out what the active and standby resources in a network are and that this information can be used to optimize attacks on networks. So even read-only access to this MIB should be properly protected. y) In general, the description of the states for each combination of entity class and state value is incomplete (see d,e,f above). What is the interpretation of combinations not mentioned in the text? Are such combinations simply undefined but not illegal or are they illegal? Overall, I like this very much. A simple but highly useful addition to the ENTITY-MIB. /js -- Juergen Schoenwaelder International University Bremen <http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib
- [Entmib] WG Last Call: Entity State MIB Margaret Wasserman
- Re: [Entmib] WG Last Call: Entity State MIB Margaret Wasserman
- Re: [Entmib] WG Last Call: Entity State MIB Juergen Schoenwaelder
- RE: [Entmib] WG Last Call: Entity State MIB Romascanu, Dan (Dan)
- [Entmib] WG Last Call: Entity State MIB Margaret Wasserman
- Re: [Entmib] WG Last Call: Entity State MIB Margaret Wasserman