Re: [Entmib] Entity State MIB Next Steps

Subrahmanya Hegde <subrah@cisco.com> Sun, 11 January 2004 15:53 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02908 for <entmib-archive@odin.ietf.org>; Sun, 11 Jan 2004 10:53:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afhtd-0006SK-V0 for entmib-archive@odin.ietf.org; Sun, 11 Jan 2004 10:53:02 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0BFr1go024813 for entmib-archive@odin.ietf.org; Sun, 11 Jan 2004 10:53:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afhtd-0006S6-Dg; Sun, 11 Jan 2004 10:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfhtX-0006Rf-M9 for entmib@optimus.ietf.org; Sun, 11 Jan 2004 10:52:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02900 for <entmib@ietf.org>; Sun, 11 Jan 2004 10:52:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AfhtV-0002K1-00 for entmib@ietf.org; Sun, 11 Jan 2004 10:52:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Afht6-0002GW-00 for entmib@ietf.org; Sun, 11 Jan 2004 10:52:29 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1Afhq8-00026L-00 for entmib@ietf.org; Sun, 11 Jan 2004 10:49:24 -0500
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0BFmQGN028512; Sun, 11 Jan 2004 07:48:26 -0800 (PST)
Received: from cisco.com (sjc-vpn3-848.cisco.com [10.21.67.80]) by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id APU04048; Sun, 11 Jan 2004 07:48:25 -0800 (PST)
Message-ID: <40017049.7010305@cisco.com>
Date: Sun, 11 Jan 2004 07:48:25 -0800
From: Subrahmanya Hegde <subrah@cisco.com>
Organization: Cisco Systems, Inc
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Margaret Wasserman <margaret@thingmagic.com>
CC: entmib@ietf.org
Subject: Re: [Entmib] Entity State MIB Next Steps
References: <5.1.0.14.2.20040109082204.04499668@ms101.mail1.com>
In-Reply-To: <5.1.0.14.2.20040109082204.04499668@ms101.mail1.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit

Hi
 a Minor Suggestion:

Instead of having these OID definitions:

-- Notifications

   entStateTraps      OBJECT IDENTIFIER ::= { entityStateMIB 2 }
   entStateTrapPrefix OBJECT IDENTIFIER ::= { entStateTraps 0 }


We can have
 entStateNotifs OBJECT IDENTIFIER ::= { entityStateMIB 0 }
 
and use 'entStateNotifs' in the corresponding NOTIFICATION-TYPE

Reason we would like to avoid name 'Traps' is: Latest RFCs refer them
as Notifications


Subra



Margaret Wasserman wrote:

>
> Now that the newest version of the Entity State MIB is available,
> the WG has a decision to make.  In my opinion, we have two
> choices:
>
> (1) We decide that the structure and objects defined in the
> current draft are acceptable, and we send the current draft
> to WG Last Call in order to identify and resolve final
> issues.
>
> (2) We decide that we want to change the structure or objects
> defined in this MIB to make it simpler or more functional.
>
> I would appreciate it if people would respond to this message
> with their opinions, so that I can attempt to judge the consensus
> of the WG on this issue.
>
> Thanks,
> Margaret
>
>
> _______________________________________________
> Entmib mailing list
> Entmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/entmib
>


_______________________________________________
Entmib mailing list
Entmib@ietf.org
https://www1.ietf.org/mailman/listinfo/entmib