Re: [Entmib] Mini WG LAST CALL: draft-ietf-entmib-v3-06.txt

Margaret Wasserman <margaret@thingmagic.com> Tue, 18 January 2005 17:46 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 MAA14990 for <entmib-archive@lists.ietf.org>; Tue, 18 Jan 2005 12:46: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 1CqxP0-00033u-I7; Tue, 18 Jan 2005 12:44:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CqxHV-0001nW-Dz for entmib@megatron.ietf.org; Tue, 18 Jan 2005 12:36:41 -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 MAA14209 for <entmib@ietf.org>; Tue, 18 Jan 2005 12:36:38 -0500 (EST)
Received: from [204.9.221.21] (helo=thingmagic.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CqxWm-0006Un-Bj for entmib@ietf.org; Tue, 18 Jan 2005 12:52:30 -0500
Received: from [10.0.0.171] (account margaret HELO [192.168.2.2]) by thingmagic.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 263329; Tue, 18 Jan 2005 12:35:10 -0500
Mime-Version: 1.0
Message-Id: <p0620073ebe12f9519217@[192.168.2.2]>
Date: Tue, 18 Jan 2005 12:35:52 -0500
To: j.schoenwaelder@iu-bremen.de
From: Margaret Wasserman <margaret@thingmagic.com>
Subject: Re: [Entmib] Mini WG LAST CALL: draft-ietf-entmib-v3-06.txt
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
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

[Failed to cc: entmib on this response the first time...]

Hi Juergen,

These changes all seem quite concrete and manageable.  Perhaps Andy
could make these changes in parallel with sending this MIB to the IESG
later this week.  Andy?

Margaret

>On Sun, Jan 16, 2005 at 07:50:17AM -0500, Margaret Wasserman wrote:
>
>>  Since this document has already been through WG Last Call several
>>  times, I just like to do a quick check that no new problems have been
>>  introduced as a result of the latest edits, then I will send this
>>  document on to the IESG for publication.
>>
>>  So, if you have any objection to this document being submitted to the
>>  IESG in its current form for publication as a Proposed Standard RFC,
>>  please send them to the entmib@ietf.org mailing list by Wednesday,
>>  January 19th.
>
>I support this document being submitted to the IESG. However, I found
>a few nits that probably should be addressed (personally I do not care
>when in the process):
>
>a) The description of entPhysicalMfgDate says '0000000000000000'H is
>    returned if the date is unknown. The text in section 2.12.1 says
>    that the object is not instantiated if the date is unknown.
>
>    It appears to me that entPhysicalFirmwareRev, entPhysicalSoftwareRev,
>    entPhysicalSerialNum, entPhysicalMfgName, and entPhysicalModelName
>    all return a zero-length string if the value is unknown so I think
>    the description is actually consistent with them.
>
>    Hence I propose the following change to section 2.12.1:
>
>    OLD
>
>      This object contains the date of manufacturing of the managed
>      entity.  If the manufacturing date is unknown or not supported
>      the object is not instantiated.
>
>    NEW
>
>      This object contains the date of manufacturing of the managed
>      entity. If the manufacturing date is unknown or not supported
>      the object is not instantiated. The special value
>      '0000000000000000'H may also be returned in this case.
>
>b) My smilint says the following:
>
>    ./ENTITY-MIB:90: warning: type `PhysicalIndex' has no format
>                              specification
>    ./ENTITY-MIB:104: warning: type `PhysicalIndexOrZero' has no format
>			      specification
>
>    I suggest to add DISPLAY-HINT "d" clauses to the TC definitions.
>
>c) If I understand the MIB review guidelines correctly, then we should
>    put the following into the IANA Considerations section:
>
>       The MIB module in this document uses the following IANA-assigned
>       OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
>
>       Descriptor        OBJECT IDENTIFIER value
>       ----------        -----------------------
>       entityMIB         { mib-2 47 }
>
>       Editor's Note (to be removed prior to publication):  this draft
>       makes no additional requests of the IANA.
>
>    (I know that one can debate the utility of this but I do not want
>    to do this here.)
>
>/js
>
>--
>Juergen Schoenwaelder		    International University Bremen
><http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 
>Bremen, Germany


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