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

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Sat, 31 July 2004 16:41 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 MAA05286 for <entmib-archive@lists.ietf.org>; Sat, 31 Jul 2004 12:41:43 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BqwmW-0002Ha-Ul; Sat, 31 Jul 2004 12:32:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bqwij-0001Zp-LS for entmib@megatron.ietf.org; Sat, 31 Jul 2004 12:28:29 -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 MAA04545 for <entmib@ietf.org>; Sat, 31 Jul 2004 12:28:26 -0400 (EDT)
Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BqwlA-0002GB-Cz for entmib@ietf.org; Sat, 31 Jul 2004 12:31:03 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id i6VGRmIa021489 for <entmib@ietf.org>; Sat, 31 Jul 2004 11:27:49 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <NTS1H1CG>; Sat, 31 Jul 2004 18:27:47 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15504E1D43B@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Kaj Tesink <kaj@research.telcordia.com>, entmib@ietf.org
Subject: RE: [Entmib] To meet or not to meet?
Date: Sat, 31 Jul 2004 18:27:43 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
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

Kaj, can you join in in the chatroom for the entmib?

Thanks,
Bert 

> -----Original Message-----
> From: Kaj Tesink [mailto:kaj@research.telcordia.com]
> Sent: donderdag 29 juli 2004 21:58
> To: entmib@ietf.org
> Subject: Re: [Entmib] To meet or not to meet?
> 
> 
> 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
> 

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