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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 20 July 2004 09:50 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 FAA04219 for <entmib-archive@lists.ietf.org>; Tue, 20 Jul 2004 05:50:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bmr9x-0002q2-T7; Tue, 20 Jul 2004 05:43:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bmr91-0002Rr-HC for entmib@megatron.ietf.org; Tue, 20 Jul 2004 05:42:43 -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 FAA03864 for <entmib@ietf.org>; Tue, 20 Jul 2004 05:42:41 -0400 (EDT)
Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bmr97-0005D1-JO for entmib@ietf.org; Tue, 20 Jul 2004 05:42:50 -0400
Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i6K9fCeq012689 for <entmib@ietf.org>; Tue, 20 Jul 2004 05:41:13 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i6K9fAeq012614 for <entmib@ietf.org>; Tue, 20 Jul 2004 05:41:11 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Entmib] To meet or not to meet?
Date: Tue, 20 Jul 2004 12:42:33 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F056B3232@is0004avexu1.global.avaya.com>
Thread-Topic: [Entmib] To meet or not to meet?
Thread-Index: AcRuMmal+9kEb2+2Sra3JFmbQvO4LgACkehw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <j.schoenwaelder@iu-bremen.de>, "Kaj Tesink" <kaj@research.telcordia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Content-Transfer-Encoding: quoted-printable
Cc: entmib@ietf.org
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
Content-Transfer-Encoding: quoted-printable

Juergen,

A few questions:

1. Should the language about using the CLEI codes be more decisive? SHOULD instead of MAY? For example: 'If CLEI codes are supported in the operational environment where this agent is implemented, this object SHOULD include a URI containing a Common Language Equipment Identifier (CLEI) URI [XXX] for the managed physical entity.'
2.' If no additional identification information is known or supported about the physical entity the object is not instantiated' - This object has a MAX-ACCESS read-write. How would the creation or deletion of the first URI in the list work? Would not it be simpler to use a zero-length string for the case when no identification information is known?
3. 'Note that [XXX] would refer to a most likely informational RFC which registers a URN namespace for CLEI codes.' - Does [XXX] really need to be an Informational RFC? I am afraid that this would hang this MIB until that RFC goes through our wonderful IETF process. Maybe the Telcordia folks already have a document to be referenced as an Informative Reference, or can create one on a shorter path.  

Regards,

Dan



> -----Original Message-----
> From: entmib-bounces@ietf.org 
> [mailto:entmib-bounces@ietf.org]On Behalf Of Juergen Schoenwaelder
> Sent: 20 July, 2004 11:05 AM
> To: Kaj Tesink
> Cc: entmib@ietf.org
> Subject: Re: [Entmib] To meet or not to meet?
> 
> 
> 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
> 

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