Re: [Entmib] Entity MIB v3

Juergen Schoenwaelder <> Tue, 30 November 2004 11:33 UTC

Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id GAA08085 for <>; Tue, 30 Nov 2004 06:33:24 -0500 (EST)
Received: from localhost.localdomain ([] by with esmtp (Exim 4.32) id 1CZ6Ay-0005lQ-Fr; Tue, 30 Nov 2004 06:28:08 -0500
Received: from ([] by with esmtp (Exim 4.32) id 1CZ67g-0004wK-EH for; Tue, 30 Nov 2004 06:24:45 -0500
Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id GAA07379 for <>; Tue, 30 Nov 2004 06:24:41 -0500 (EST)
Received: from ([]) by with esmtp (Exim 4.33) id 1CZ6Cm-0000gy-8a for; Tue, 30 Nov 2004 06:30:01 -0500
Received: from localhost ( []) by (Postfix) with ESMTP id 6FEE935F4; Tue, 30 Nov 2004 12:24:09 +0100 (CET)
Received: from ([]) by localhost (demetrius []) (amavisd-new, port 10024) with ESMTP id 11054-05; Tue, 30 Nov 2004 12:24:08 +0100 (CET)
Received: from james ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTP id 65C283607; Tue, 30 Nov 2004 12:24:08 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34) id 1CZ677-0000pP-8D; Tue, 30 Nov 2004 12:24:09 +0100
Date: Tue, 30 Nov 2004 12:24:09 +0100
From: Juergen Schoenwaelder <>
To: Margaret Wasserman <>
Subject: Re: [Entmib] Entity MIB v3
Message-ID: <20041130112409.GE2823@james>
Mail-Followup-To: Margaret Wasserman <>, Andy Bierman <>,,
References: <> <p06200720bdd18dd1c671@[]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <p06200720bdd18dd1c671@[]>
User-Agent: Mutt/1.5.6+20040722i
X-Virus-Scanned: by amavisd-new 20030616p5 at
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc:,, 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 Mon, Nov 29, 2004 at 09:41:15PM -0500, Margaret Wasserman wrote:
> >Also, I need examples for the entPhysicalUris object.
> >This object is too vague for me to provide any examples.
> >I also see no guidance for which types of physical
> >entities should provide a mfg date.  FRUs only?
> >More text is needed for both of these new objects.
> Could one of the people who felt strongly that these objects should 
> be included in the Entity MIB update please respond to Andy's request 
> for more information?

I suggest to add language to entPhysicalMfgDate which says that there
is a default value in case the manufacturing date is unknown: 

	The value '0000000000000000'H is returned if the manufacturing
	date of the entity in unknown.

I don't think we need to constrain this object to FRUs. 

Regarding entPhysicalUris: This object was proposed to handle CLIE
codes and other things people may come up with to identify entities.
It would be nice if Kaj Tesink <> could
start an ID which defines a URI namespace for CLIE codes. While
this might take some time and we do not want to depend on it, 
another source of examples might be OID URNs as defined in RFC 
3001, that is something like urn:oid: (I leave it to
your imagination to pick a suitable value for an example).
> If there is no one who care enough about these objects to do actual 
> work to finalize them, perhaps Andy should just leave them out and we 
> can get the Entity MIB update published?

I would love to see Kaj starting to write up the CLIE code URN spec
since this was the major driving force for this addition. I this
does not happen, then dropping these objects (even though I believe
we now have a viable solution) might be a logical conclusion.


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

Entmib mailing list