Re: [Entmib] To meet or not to meet?

Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de> Tue, 20 July 2004 08:19 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 EAA29348 for <entmib-archive@lists.ietf.org>; Tue, 20 Jul 2004 04:19:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bmpji-0003tz-F6; Tue, 20 Jul 2004 04:12:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BmpcY-0002Jy-RX for entmib@megatron.ietf.org; Tue, 20 Jul 2004 04:05:07 -0400
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 EAA28434 for <entmib@ietf.org>; Tue, 20 Jul 2004 04:05:01 -0400 (EDT)
Received: from g44d3.g.pppool.de ([80.185.68.211] helo=james.eecs.iu-bremen.de) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bmpca-00048g-CU for entmib@ietf.org; Tue, 20 Jul 2004 04:05:09 -0400
Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000) id 1C87981D4; Tue, 20 Jul 2004 10:04:57 +0200 (CEST)
Date: Tue, 20 Jul 2004 10:04:57 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Kaj Tesink <kaj@research.telcordia.com>
Subject: Re: [Entmib] To meet or not to meet?
Message-ID: <20040720080457.GA1822@iu-bremen.de>
Mail-Followup-To: Kaj Tesink <kaj@research.telcordia.com>, entmib@ietf.org
References: <713043CE8B8E1348AF3C546DBE02C1B4CA1C33@zcarhxm2.corp.nortel.com> <4.3.2.7.2.20040719162902.0179f8c0@128.96.81.11>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.3.2.7.2.20040719162902.0179f8c0@128.96.81.11>
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: entmib@ietf.org
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
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

On Mon, Jul 19, 2004 at 04:36:47PM -0400, Kaj Tesink wrote:
> 
> i cannot be present, but can check whether another telcordia person can 
> attend.
> as far as the draft is concerned, we're talking actually only about two 
> objects,
> of which only one is under debate. dave p. had volunteered a fix, so that 
> could
> be something to discuss (URN approach). i'm personally rather flexible wrt 
> the
> solution so if either the meeting or an adhoc group can coble up something
> we can put it in the draft and be done.

I think the changes on the MIB side are rather straight forward. Below
is a first cut an proposed new text:

3.2.  entSupplPhysicalUris

   This object provides additional identification information about the 
   physical entity. This object may be used to encode for example a 
   URI containing a Common Language Equipment Identifier (CLEI) URI
   [XXX] for the managed physical entity. If no additional identification 
   information is known or supported about the physical entity the object 
   is not instantiated.

And in the MIB definition itself:

   entSupplPhysicalUris OBJECT-TYPE
       SYNTAX      DisplayString
       MAX-ACCESS  read-write
       STATUS	   current
       DESCRIPTION
 	  "This object contains additional identification information 
	   about the physical entity. The object contains URIs and
	   therefore the syntax of this object must conform to RFC
	   2396 section 2. Multiple URIs may be separated by white 
	   space characters."
       ::= { entSupplPhysicalEntry 2 }

The definition of the cleiCode OBJECT-IDENTITY will be removed and
someone from Telcordia needs to write up a document registering a
URN namespace for CLEI codes. 

Note that [XXX] would refer to a most likely informational RFC which
registers a URN namespace for CLEI codes.

/js

P.S. I will not attend the meeting in San Diego. 

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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