Re: [Entmib] Entity Management and Dual IP Stack

Juergen Schoenwaelder <> Thu, 27 October 2005 23:13 UTC

Received: from localhost.localdomain ([] by with esmtp (Exim 4.32) id 1EVGvn-0007bi-5U; Thu, 27 Oct 2005 19:13:11 -0400
Received: from ([] by with esmtp (Exim 4.32) id 1EVGvl-0007bd-UL for; Thu, 27 Oct 2005 19:13:09 -0400
Received: from (ietf-mx []) by (8.9.1a/8.9.1a) with ESMTP id TAA26122 for <>; Thu, 27 Oct 2005 19:12:53 -0400 (EDT)
Received: from ([]) by with esmtp (Exim 4.43) id 1EVH9D-0005Ab-2D for; Thu, 27 Oct 2005 19:27:04 -0400
Received: from localhost ( []) by (Postfix) with ESMTP id 67CAB4C102; Fri, 28 Oct 2005 01:12:48 +0200 (CEST)
Received: from ([]) by localhost (demetrius []) (amavisd-new, port 10024) with ESMTP id 32459-02; Fri, 28 Oct 2005 01:12:47 +0200 (CEST)
Received: from (unknown []) by (Postfix) with ESMTP id AA89C4C13A; Fri, 28 Oct 2005 01:12:45 +0200 (CEST)
Received: by boskop.local (Postfix, from userid 501) id C15D151660F; Fri, 28 Oct 2005 00:55:06 +0200 (CEST)
Date: Fri, 28 Oct 2005 00:55:06 +0200
From: Juergen Schoenwaelder <>
To: Eduardo Cardona <>
Subject: Re: [Entmib] Entity Management and Dual IP Stack
Message-ID: <20051027225506.GA21228@boskop.local>
Mail-Followup-To: Eduardo Cardona <>, Sharon Chisholm <>, "Entmib-wg (E-mail)" <>
References: <>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.5.10i
X-Virus-Scanned: by amavisd-new 20030616p5 at
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: "Entmib-wg \(E-mail\)" <>
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF Entity MIB WG <>
List-Unsubscribe: <>, <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

On Thu, Oct 27, 2005 at 12:01:26PM -0600, Eduardo Cardona wrote:
> Thanks for the reply. 
> It is one logical entity with two IP management addresses  ( one IPv4
> and one IPv6), my question is how to configure entLogicalTDomain and
> entLogicalTAddress to support both IPv4 and IPv6 for the same logical
> entitiy 

I agree that this is a valid question to ask and it seems that there
is no good answer to this question.

My understanding of the SNMP architecture is that an SNMP engine is
identified by an SNMP engine ID. Since an SNMP engine can be attached
to multiple transport endpoints, there needs to be a 1:N mapping of
SNMP engine IDs to the transports the engine is listening on. The
SNMPv3 specs may not be particular clear how this 1:N mapping is
represented in the core SNMP MIBs (and I believe the SNMP core MIB
modules are the place where this information should be represented).

The ENTITY-MIB should not try to duplicate this information 1:N
mapping and just refer to the appropriate table via the relevant SNMP
engine ID. However, the ENTITY-MIB was first published in 1996 (RFC
2037) and at that time the concept of an engine ID did not really
exist so it is understandable why the entLogicalEntry looks like it

To summarize: I see a problem here. Is it worth fixing?  Perhaps.  How
much time will it take to do that in the IETF? I better don't
speculate. Perhaps much more important is to record this as a "defect
report" (where?) so that people can worry about this once this MIB is
opened up for revision.


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

Entmib mailing list