RE: To meet or not to meet?

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

Thanks,
Bert 

> -----Original Message-----
> From: Kaj Tesink [mailto:[email protected]]
> Sent: donderdag 29 juli 2004 21:58
> To: [email protected]
> 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: [email protected]
> Tel: (732) 699-6068
> Fax: (732) 336-2336
> 
> _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> 
> 
> _______________________________________________
> Entmib mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/entmib
>