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

Kaj Tesink <kaj@research.telcordia.com> Thu, 29 July 2004 20:45 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 QAA08176 for <entmib-archive@lists.ietf.org>; Thu, 29 Jul 2004 16:45:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BqHTX-0007qo-6r; Thu, 29 Jul 2004 16:26:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BqH2q-0004CG-So for entmib@megatron.ietf.org; Thu, 29 Jul 2004 15:58:28 -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 PAA05470 for <entmib@ietf.org>; Thu, 29 Jul 2004 15:58:21 -0400 (EDT)
Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BqH4n-0002IA-Eh for entmib@ietf.org; Thu, 29 Jul 2004 16:00:33 -0400
Received: from shannon.research.telcordia.com (shannon [128.96.81.11]) by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id i6TJvUMS022844 for <entmib@ietf.org>; Thu, 29 Jul 2004 15:57:30 -0400 (EDT)
Received: from kaj-100.research.telcordia.com (kaj-100.cc.telcordia.com [128.96.171.145]) by shannon.research.telcordia.com (8.9.3/8.9.3) with ESMTP id PAA29523 for <entmib@ietf.org>; Thu, 29 Jul 2004 15:57:38 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040729154242.048fde80@128.96.81.11>
X-Sender: kaj@128.96.81.11
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 29 Jul 2004 15:57:50 -0400
To: entmib@ietf.org
From: Kaj Tesink <kaj@research.telcordia.com>
Subject: Re: [Entmib] To meet or not to meet?
In-Reply-To: <20040720080457.GA1822@iu-bremen.de>
References: <4.3.2.7.2.20040719162902.0179f8c0@128.96.81.11> <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"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
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

to summarize where the suppl entity mib discussion stands:
- the vague title seems resolvable; Dan had several specific suggestions;
    any others, pl post and/or resolve at the meeting
- entSupplPhysicalUris
    Juergen's posting & subsequent discussion seem quite reasonable.
     assuming rough consensus i'll update the draft with this & any
     other changes agreed on the list and at the meeting, and
     telcordia will write the request for URN name space.
- anything else?

kaj

PS due to parallel meetings it turns out that the telcordia person
for this, John Haluska cannot attend the meeting but he and Dan
will meet ad-hoc just prior to the entmib wg at 12:30PT in the entmib
mtg room; any interested folks pl join




At 10:04 AM 7/20/2004 +0200, Juergen Schoenwaelder wrote:
>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

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
REACH INFO HAS CHANGED; NEW INFO PER 7/19/04:
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

Kaj Tesink
Telcordia Technologies. Inc.
1 Telcordia Drive
Piscataway, NJ 08854-3923
Email: kaj@research.telcordia.com
Tel: (732) 699-6068
Fax: (732) 336-2336

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/


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