[MEXT] [Fwd: RE: Last Call: draft-ietf-mext-nemo-mib (NEMO Management Information Base) to Proposed Standard]
marcelo bagnulo braun <marcelo@it.uc3m.es> Wed, 21 January 2009 14:33 UTC
Return-Path: <mext-bounces@ietf.org>
X-Original-To: nemo-archive@megatron.ietf.org
Delivered-To: ietfarch-nemo-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C747528C0F3; Wed, 21 Jan 2009 06:33:31 -0800 (PST)
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CD6ED3A6B49 for <mext@core3.amsl.com>; Wed, 21 Jan 2009 06:33:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.295
X-Spam-Level:
X-Spam-Status: No, score=-5.295 tagged_above=-999 required=5 tests=[AWL=1.304, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id haGtrNQxdQRd for <mext@core3.amsl.com>; Wed, 21 Jan 2009 06:33:29 -0800 (PST)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by core3.amsl.com (Postfix) with ESMTP id 5D5293A694F for <mext@ietf.org>; Wed, 21 Jan 2009 06:33:28 -0800 (PST)
Received: from marcelo-bagnulos-macbook-pro.local (unknown [85.53.138.213]) by smtp01.uc3m.es (Postfix) with ESMTP id 571E7B4CFC4 for <mext@ietf.org>; Wed, 21 Jan 2009 15:33:08 +0100 (CET)
Message-ID: <49773224.3080309@it.uc3m.es>
Date: Wed, 21 Jan 2009 15:33:08 +0100
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: mext <mext@ietf.org>
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.5.0.1026-16414.005
Subject: [MEXT] [Fwd: RE: Last Call: draft-ietf-mext-nemo-mib (NEMO Management Information Base) to Proposed Standard]
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org forwarding on behalf of Dan...
-------- Mensaje original -------- Asunto: RE: Last Call: draft-ietf-mext-nemo-mib (NEMO Management Information Base) to Proposed Standard Fecha: Wed, 21 Jan 2009 14:53:10 +0100 De: Romascanu, Dan (Dan) <dromasca@avaya.com> Para: <ietf@ietf.org> CC: mext@ietf.org Referencias: <20090113161148.4F49A3A6981@core3.amsl.com> This review is a super-set of the MIB Doctor review by Bert Wijnen. This document is not completely ready for being taken into discussion by the IESG. Although there is no major issue with the current version of the document the issues described at #3, #7, #8 and #10 must be fixed. Correcting the other issues raised in the comments is recommended. 1. Section 2.2 (implementation guidance) is incomplete. It should mention the need to support ifTable from IF-MIB as InterfaceIndex is IMPORTed. Also better rename it 'Relationship to other MIB modules'. 2. Compilation is OK - running SMICng (strict checking) results in: W: f(nemo.mi2), (221,5) Row "nemoMrBLEntry" has indexing that may create variables with more than 128 sub-ids W: f(nemo.mi2), (404,5) Row "nemoHaMobileNetworkPrefixEntry" has indexing that may create variables w ith more than 128 sub-ids W: f(nemo.mi2), (540,5) Row "nemoBindingCacheEntry" has indexing that may create variables with more than 128 sub-ids W: f(nemo.mi2), (1092,5) Row "nemoHaCounterEntry" has indexing that may create variables with more th an 128 sub-ids Two are AUGEMENTS, the other two do have a warning in the DESCIRPITON clauses, so OK. 3. The Object nemoMrPrefixRegMode is writable but there is no description of the expected persistency behavior. For read-write object nemoStatus: The value of this object SHOULD remain unchanged across reboots of the managed entity. A SHOULD does not really help a management station as it cannot count for sure on persistency. 4. nemoNotifications OBJECT IDENTIFIER ::= { nemoMIB 0 } nemoObjects OBJECT IDENTIFIER ::= { nemoMIB 1 } nemoConformance OBJECT IDENTIFIER ::= { nemoMIB 3 } Why the Conformance is not under { nemoMIB 2 } as recommended by RFC4181? 5. I see a few times: SYNTAX INTEGER { implicitMode (1), explicitMode (2) } Candidate for a TC. But not a fatal flaw of course 6. I think that according the guidelines in RFC4181, this one nemoHaMobileNetworkPrefixSeqNo OBJECT-TYPE SYNTAX Integer32 (1..1024) would better be an Unsigned32. Again, not a fatal flaw. 7. nemoBindingMrFlag OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "true(1) indicates that the binding cache entry is from an entity acting as a mobile router. false(0) implies that the binding cache entry is from an entity acting as a mobile node. " But the TC in RFC2579 says: TruthValue ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Represents a boolean value." SYNTAX INTEGER { true(1), false(2) } So it should be false(2) and not false(0) in the DESCRIPTION clause. 8. The document must have normative references to RFC 2863 and RFC 4001 as the MIB module defined in this document IMPORTs objects from the MIB modules defined in these RFCs. 9. No need to carry commented objects in the IMPORTS section. 10. The REVISION date is in the future - points to November 12 and not to January 12. 11. It would be useful to add UNITS clauses to the Counter objects. Dan > -----Original Message----- > From: ietf-announce-bounces@ietf.org > [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG > Sent: Tuesday, January 13, 2009 6:12 PM > To: IETF-Announce > Cc: mext@ietf.org > Subject: Last Call: draft-ietf-mext-nemo-mib (NEMO Management > Information Base) to Proposed Standard > > The IESG has received a request from the Mobility EXTensions > for IPv6 WG > (mext) to consider the following document: > > - 'NEMO Management Information Base ' > <draft-ietf-mext-nemo-mib-04.txt> as a Proposed Standard > > The IESG plans to make a decision in the next few weeks, and > solicits final comments on this action. Please send > substantive comments to the ietf@ietf.org mailing lists by > 2009-01-27. Exceptionally, comments may be sent to > iesg@ietf.org instead. In either case, please retain the > beginning of the Subject line to allow automated sorting. > > The file can be obtained via > http://www.ietf.org/internet-drafts/draft-ietf-mext-nemo-mib-04.txt > > > IESG discussion can be tracked via > https://datatracker.ietf.org/public/pidtracker.cgi?command=vie > w_id&dTag=16994&rfc_flag=0 > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-announce > _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf _______________________________________________ MEXT mailing list MEXT@ietf.org https://www.ietf.org/mailman/listinfo/mext
- [MEXT] Last Call: draft-ietf-mext-nemo-mib (NEMO … The IESG
- [MEXT] [Fwd: RE: Last Call: draft-ietf-mext-nemo-… marcelo bagnulo braun
- Re: [MEXT] Last Call: draft-ietf-mext-nemo-mib (N… Romascanu, Dan (Dan)