Re: [Entmib] FW: [psg.com #328] AutoReply: Containment Hierach and entPhysical Containedin

"David T. Perkins" <dperkins@dsperkins.com> Fri, 13 February 2004 07:20 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25266 for <entmib-archive@lists.ietf.org>; Fri, 13 Feb 2004 02:20:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArXcI-0005n6-0M; Fri, 13 Feb 2004 02:20:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArXc5-0005jA-47 for entmib@optimus.ietf.org; Fri, 13 Feb 2004 02:19:49 -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 CAA25203 for <entmib@ietf.org>; Fri, 13 Feb 2004 02:19:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArXbx-0001HO-00 for entmib@ietf.org; Fri, 13 Feb 2004 02:19:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArXb1-0001DN-00 for entmib@ietf.org; Fri, 13 Feb 2004 02:18:44 -0500
Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArXaJ-000197-00 for entmib@ietf.org; Fri, 13 Feb 2004 02:17:59 -0500
Received: from NB5.dsperkins.com (shell4.bayarea.net [209.128.82.1]) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id i1D7Hu310766; Thu, 12 Feb 2004 23:17:56 -0800
Message-Id: <5.2.0.9.2.20040212231230.01fafc50@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Thu, 12 Feb 2004 23:17:49 -0800
To: Sharon Chisholm <schishol@nortelnetworks.com>, entmib@ietf.org
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: Re: [Entmib] FW: [psg.com #328] AutoReply: Containment Hierach and entPhysical Containedin
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A244352@zcard0ka.ca.norte l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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=AWL autolearn=no version=2.60
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>

HI,

This is a real problem. I suggest that a paragraph be added to the
document that describes "containment hierarchy" (and provides
an example). And then all of the uses in the DESCRIPTION clauses
just say "containment hierarchy" and drop all mention of
object entPhysicalContainedIn." If this approach is not
desired, then use a phrase like "....on entities within its       
containment hierarchy. These are entities that specify this
entity as the value for object entPhysicalContainedIn directly
and indirectly."


At 01:44 PM 2/12/2004 -0500, Sharon Chisholm wrote:
>The following is the proposed resolution to entstate-328. The issue 
>will be considered closed pending the proposed edit being done.
>
>In the various object definitions replace phrases like
>
>"as defined by a value of
>               entPhysicalContainedIn that references this entity"
>
>With one like
>
>"as defined by the entPhysicalContainedIn object."
>
>Sharon
>
>-----Original Message-----
>From: rt+entity-state@rt.psg.com [mailto:rt+entity-state@rt.psg.com] 
>Sent: Wednesday, February 11, 2004 12:56 PM
>To: Chisholm, Sharon [CAR:0S00:EXCH]
>Subject: [psg.com #328] AutoReply: Containment Hierach and
>entPhysicalContainedin
><clip>
>
>-------------------------------------------------------------------------
>Juergen Schoenwaelder [j.schoenwaelder@iu-bremen.de]
>
>"5) Several description clauses refer to "entities within its
>   containment hierarchy" followed by a sentence which limits this to
>   the entities "having a value of entPhysicalContainedIn that refers
>   to this entity". This somehow excludes transitive containment. Is
>   this by intention or accident? I mean, if I have C contained in B
>   contained in A, then A still provides indirect service to C."
Regards,
/david t. perkins 


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