Re: [Entmib] entPhysicalUris object wrap-up

"David T. Perkins" <dperkins@dsperkins.com> Wed, 08 December 2004 22:27 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16414 for <entmib-archive@lists.ietf.org>; Wed, 8 Dec 2004 17:27:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cc9kF-00082A-D2; Wed, 08 Dec 2004 16:53:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cc9NE-0002fY-3j for entmib@megatron.ietf.org; Wed, 08 Dec 2004 16:29:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04772 for <entmib@ietf.org>; Wed, 8 Dec 2004 16:29:21 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cc9U3-0007z5-KM for entmib@ietf.org; Wed, 08 Dec 2004 16:36:29 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id iB8LRdkc009986; Wed, 8 Dec 2004 13:27:39 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1]) by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id iB8LRcAr008048; Wed, 8 Dec 2004 13:27:38 -0800
Received: from localhost (dperkins@localhost) by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id iB8LRceB008027; Wed, 8 Dec 2004 13:27:38 -0800
X-Authentication-Warning: shell4.bayarea.net: dperkins owned process doing -bs
Date: Wed, 8 Dec 2004 13:27:37 -0800 (PST)
From: "David T. Perkins" <dperkins@dsperkins.com>
X-Sender: dperkins@shell4.bayarea.net
To: Margaret Wasserman <margaret@thingmagic.com>
Subject: Re: [Entmib] entPhysicalUris object wrap-up
In-Reply-To: <p06200729bddcf64d2d89@[192.168.2.2]>
Message-ID: <Pine.LNX.4.10.10412081325350.25144-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: entmib@ietf.org, Andy Bierman <abierman@cisco.com>
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF Entity MIB WG <entmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=unsubscribe>
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>
Sender: entmib-bounces@ietf.org
Errors-To: entmib-bounces@ietf.org

HI,

I somehow missed the motivating reasons to go from a 
an object that can provide a alternative identification
to an object that supports only CLEI codes.

On Wed, 8 Dec 2004, Margaret Wasserman wrote:
> >I propose that this object be changed back to entPhysicalClei.
> >It should contain the empty string (for none) or a URI
> >string conforming to the CLEI URN specification (from Kaj).
> >If we think of other required semantics in the future,
> >we can add new objects then.
> 
> This makes sense to me if we can quickly, easily resolve the reference issues.
> 
> Otherwise, I think we should just remove the object and let others 
> add it as an "augments" if/when the proposed contents are 
> well-defined.
> 
Regards,
/david t. perkins


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