RE: [Entmib] entPhysicalUris object wrap-up

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Wed, 08 December 2004 21:29 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 QAA04779 for <entmib-archive@lists.ietf.org>; Wed, 8 Dec 2004 16:29:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cc9Cy-0007ad-96; Wed, 08 Dec 2004 16:18:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cc94g-0004WR-KI for entmib@megatron.ietf.org; Wed, 08 Dec 2004 16:10:14 -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 QAA03670 for <entmib@ietf.org>; Wed, 8 Dec 2004 16:10:12 -0500 (EST)
Received: from hoemail1.lucent.com ([192.11.226.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cc9BV-0007fV-75 for entmib@ietf.org; Wed, 08 Dec 2004 16:17:19 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iB8LA7R6017993 for <entmib@ietf.org>; Wed, 8 Dec 2004 15:10:07 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <XJHXHHTB>; Wed, 8 Dec 2004 22:10:06 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15505E0CE4F@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Margaret Wasserman <margaret@thingmagic.com>, Andy Bierman <abierman@cisco.com>
Subject: RE: [Entmib] entPhysicalUris object wrap-up
Date: Wed, 8 Dec 2004 22:10:05 +0100
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: b7b9551d71acde901886cc48bfc088a6
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

Inline

> -----Original Message-----
> From: entmib-bounces@ietf.org 
> [mailto:entmib-bounces@ietf.org]On Behalf
> Of Margaret Wasserman
> Sent: Wednesday, December 08, 2004 13:24
> To: Andy Bierman
> Cc: entmib@ietf.org
> Subject: Re: [Entmib] entPhysicalUris object wrap-up
> 
> 
> 
> >I propose that this object be changed back to entPhysicalClei.
> >It should contain the empty string (for none) or a URI
> >string conforming to the CLEI URN specification (from Kaj).
> >If we think of other required semantics in the future,
> >we can add new objects then.
> 
> This makes sense to me if we can quickly, easily resolve the 
> reference issues.
> 
> Otherwise, I think we should just remove the object and let others 
> add it as an "augments" if/when the proposed contents are 
> well-defined.
> 
> >2) references
> >
> >As per Bert's comments, the citation to RFC 2396 will be
> >removed from the DESCRIPTION clause, since it is redundant.
> >Should this be changed to point to the CLEI URN specification,
> >or just add another document to the REFERENCE clause?
> >Where else should this spec be cited in the document?
> >There are normative references, so how long will the
> >Entity MIB be held up waiting for the CLEI URN RFC?
> 
> If we pursue this choice, I think that the CLEI URN document needs to 
> be a normative reference.  Kaj submitted a draft, but I don't know 
> what shape it is in and/or whether Bert is willing to either: (1) 
> allow this group to take on that document, or (2) move it forward as 
> an individual submission.  How close do folks think it is to ready 
> for publication?  Has a MIB doctor reviewed it?  Bert, do you have 
> any thoughts?
> 
I'd suggest that Kaj posts his doc to the IETF I-D repository asap, 
so all IETF people can see it.
Is it a doc that goes stds track, or what?

Besides, I see in the copy that I got from Kaj):
!! Missing citation for Normative reference:
  P007 L011: [RFC3406]   Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom,

idnits 1.47 (02 Nov 2004)

../../draft-tesink-urn-clei-00.txt:

  Looks like you're using RFC 2026 boilerplate. Better change to RFC 3667/3668.
  There are 4 instances of lines with non-ascii characters in the document.

Is the URN intended to be a FORMAL or an INFORMAL one (see rfc3406) ??

Bert
> >3) conformance
> >
> >Currently the new OBJECT-GROUP (entityPhysical3Group)
> >is in the MANDATORY-GROUPS clause.  If both objects
> >allow for null values, then this should not be a problem.
> 
> Okay.
> 
> >4) examples
> >
> >I don't really have time (or enough info) to fill in the
> >examples in section 4, but I know somebody will eventually
> >ask about this before RFC publication.  I would really
> >appreciate some help updating the examples.  (I need to
> >add an example for entPhysicalClass==cpu(12) as well.)
> >Any volunteers? (4.1 and 4.2 can be done independently)
> >I would like to get this over with now ;-)
> 
> Yes.  It would be good to get this finished, so volunteer 
> would be appreciated.
> 
> Margaret

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