Re: [Entmib] Entity MIB v3

Juergen Schoenwaelder <> Tue, 30 November 2004 19:16 UTC

Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id OAA21872 for <>; Tue, 30 Nov 2004 14:16:06 -0500 (EST)
Received: from localhost.localdomain ([] by with esmtp (Exim 4.32) id 1CZDID-0002uC-IJ; Tue, 30 Nov 2004 14:04:05 -0500
Received: from ([] by with esmtp (Exim 4.32) id 1CZDCx-0001A8-JF for; Tue, 30 Nov 2004 13:58:43 -0500
Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id NAA20240 for <>; Tue, 30 Nov 2004 13:58:37 -0500 (EST)
Received: from ([]) by with esmtp (Exim 4.33) id 1CZDI7-0003tY-Aj for; Tue, 30 Nov 2004 14:04:00 -0500
Received: from localhost ( []) by (Postfix) with ESMTP id A30DA3256; Tue, 30 Nov 2004 19:58:06 +0100 (CET)
Received: from ([]) by localhost (demetrius []) (amavisd-new, port 10024) with ESMTP id 08646-03; Tue, 30 Nov 2004 19:58:05 +0100 (CET)
Received: from james ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTP id BCBD635FA; Tue, 30 Nov 2004 19:58:04 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34) id 1CZDCN-0000bf-W9; Tue, 30 Nov 2004 19:58:04 +0100
Date: Tue, 30 Nov 2004 19:58:03 +0100
From: Juergen Schoenwaelder <>
To: David B Harrington <>
Subject: Re: [Entmib] Entity MIB v3
Message-ID: <20041130185803.GB2231@james>
Mail-Followup-To: David B Harrington <>, 'Andy Bierman' <>, 'Margaret Wasserman' <>,,
References: <> <>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.5.6+20040722i
X-Virus-Scanned: by amavisd-new 20030616p5 at
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: "'Margaret Wasserman'" <>,,, "'Andy Bierman'" <>
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF Entity MIB WG <>
List-Unsubscribe: <>, <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

On Tue, Nov 30, 2004 at 11:37:31AM -0500, David B Harrington wrote:
> It could be useful to identify something like a mfg code or OEM part
> number, to make it easier to identify problem components for things
> like product recalls. Enterasys uses a proprietary MIB object for this
> type of information (amongst other info). In some cases, other SDOs
> define standards for the semantics. The information is not necessarily
> something that we are likely to reach standardization on. This
> information is likely to be available via the CLI or an HTML-based
> interface, and it might be useful to define an SNMP-equivalent, but a
> URI is not a normal SNMP construct.

I read this as an argument in favor of the entPhysicalUris addition.
> I agree there is the possibility of namespace conflict, and the
> usefulness of this object to a vendor-neutral application is
> questionable. 

Please someone explain to me the namespace conflict you are seeing.
> I don't object to removing this object from this module. For those who
> wish to use a CLIE URI, I suggest they write an RFC with the CLIE
> codes and include a mib module with the URI object to augment the
> entity mib table. Hopefully, they will also include an object to
> identify the namespace.

Now you seem to argue against the entPhysicalUris addition. (I fail
to see why you need an object to identify a namespace since the
namespace should be clear from the URI. But then I admit that I fail
to understand the point raised above, so I am obviously missing some
pieces here.)

So, Dave, what do you want to tell us?


Juergen Schoenwaelder		    International University Bremen
<>	    P.O. Box 750 561, 28725 Bremen, Germany

Entmib mailing list