RE: [Entmib] FW: DISCUSS: draft-ietf-entmib-v3-07.txt

Kaj Tesink <kaj@research.telcordia.com> Wed, 02 February 2005 16:47 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 LAA26851 for <entmib-archive@lists.ietf.org>; Wed, 2 Feb 2005 11:47:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwNcw-0001rm-Pj; Wed, 02 Feb 2005 11:45:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwNTt-0006ph-So for entmib@megatron.ietf.org; Wed, 02 Feb 2005 11:35:53 -0500
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 LAA25295 for <entmib@ietf.org>; Wed, 2 Feb 2005 11:35:49 -0500 (EST)
Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwNmH-0004hA-EV for entmib@ietf.org; Wed, 02 Feb 2005 11:54:54 -0500
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 j12GZ65u008843; Wed, 2 Feb 2005 11:35:06 -0500 (EST)
Received: from KAJ-2.research.telcordia.com (chood-2-1560897ud.cc.telcordia.com [128.96.171.154] (may be forged)) by shannon.research.telcordia.com (8.9.3/8.9.3) with ESMTP id LAA05658; Wed, 2 Feb 2005 11:35:02 -0500 (EST)
Message-Id: <6.1.2.0.2.20050202113127.048f8ba8@128.96.81.11>
X-Sender: kaj@128.96.81.11
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Wed, 02 Feb 2005 11:34:46 -0500
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
From: Kaj Tesink <kaj@research.telcordia.com>
Subject: RE: [Entmib] FW: DISCUSS: draft-ietf-entmib-v3-07.txt
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B15503C7A05E@nl0006exch001u.nl .lucent.com>
References: <7D5D48D2CAA3D84C813F5B154F43B15503C7A05E@nl0006exch001u.nl.lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
Cc: "Entmib-wg \(E-mail\)" <entmib@ietf.org>, "'Andy Bierman'" <abierman@cisco.com>
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

At 10:54 AM 2/2/2005, Wijnen, Bert (Bert) wrote:
>Andy writes:
> >
> > At 07:05 AM 2/2/2005, Wijnen, Bert (Bert) wrote:
> > >Can the author/editor and/or the WG react please.
> > >I need (if possible) an answer by tomorrow (Thursday) 11am US
> > >eastern at the latest (that is, if we want to try and get this
> > >approved this week).
> >
> > what are the edits? CLEI URI to CLEI URN. reference
> > RFC 2396 -> RFC 3986.  Any other nits?  Can't you just carry
> > forward an edit list without an update?
> >
>
>I can do that if the WG agrees that that is indeed what we want to do.
>I cannot just make such changes without checking back with at least
>the authors/editors or the WG.
>
> > It's not like these updates require anybody to comment.
> > Who's going to object to fixing a nit?
> >
>I can do those fixes with an RFC-Editor note if we agree that
>is what we want to do.


as i was the troublemaker asking for this object:
agree with Andy; simple nits & no problem

kaj



>Bert
> >
> > >Bert
> >
> > Andy
> >
> >
> >
> > >> -----Original Message-----
> > >> From: entmib-bounces@ietf.org
> > >> [mailto:entmib-bounces@ietf.org]On Behalf
> > >> Of Wijnen, Bert (Bert)
> > >> Sent: Tuesday, February 01, 2005 01:05
> > >> To: Entmib-wg (E-mail)
> > >> Subject: [Entmib] FW: DISCUSS: draft-ietf-entmib-v3-07.txt
> > >>
> > >>
> > >> Feedback from IESG
> > >>
> > >> -----Original Message-----
> > >> From: iesg-bounces@ietf.org
> > [mailto:iesg-bounces@ietf.org]On Behalf Of
> > >> Ted Hardie
> > >> Sent: Monday, January 31, 2005 23:28
> > >> To: iesg@ietf.org
> > >> Subject: DISCUSS: draft-ietf-entmib-v3-07.txt
> > >>
> > >>
> > >> Minor, but should be fixed.  The document currently says:
> > >>
> > >> entPhysicalUris OBJECT-TYPE
> > >>      SYNTAX      OCTET STRING
> > >>      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 present and are
> > separated by white
> > >>              space characters. Leading and trailing white space
> > >>              characters are ignored.
> > >>
> > >>              If no additional identification information
> > is known or
> > >>              supported about the physical entity the object is not
> > >>              instantiated.  A zero length octet string may also be
> > >>              returned in this case."
> > >>      REFERENCE
> > >>              "RFC 2396, Uniform Resource Identifiers (URI): Generic
> > >>              Syntax, section 2, August 1998."
> > >>
> > >> This should be updated to the new URI RFC and a pointer to the
> > >> appropriate syntax restrictions.  This text also does not limit
> > >> the types of URIs which may be present.  If they are limited,
> > >> an enumerated list should be included.
> > >>
> > >> The document also uses "CLEI URI" to refer to a URN in the CLEI
> > >> namespace.  That's technically correct, but it would be easier
> > >> to understand if CLEI URN was used.  Here's an example:
> > >>
> > >>      The entPhysicalUris object may be used to encode for
> > >> example a URI
> > >>      containing a Common Language Equipment Identifier
> > (CLEI) URI for
> > >>      the managed physical entity. The URN name space for CLEIs is
> > >>      defined in [RFC CLEIURN], and the CLEI format is defined in
> > >>      [T1.213][T1.213a].
> > >>
> > >> Simply swapping out (CLEI) URI for (CLEI) URN would be fine.
> > >>
> > >> _______________________________________________
> > >> 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


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

Kaj Tesink
Telcordia Technologies. Inc.
One Telcordia drive
Piscataway, NJ 08854
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