[Hubmib] AD review of draft-ietf-hubmib-wis-mib-04.txt

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Sun, 17 November 2002 03:25 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00204 for <hubmib-archive@odin.ietf.org>; Sat, 16 Nov 2002 22:25:01 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gAH3RG112722 for hubmib-archive@odin.ietf.org; Sat, 16 Nov 2002 22:27:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAH3RGv12717; Sat, 16 Nov 2002 22:27:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAH3QJv12685 for <hubmib@optimus.ietf.org>; Sat, 16 Nov 2002 22:26:19 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00192 for <hubmib@ietf.org>; Sat, 16 Nov 2002 22:23:32 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id gAH3Q8827029 for <hubmib@ietf.org>; Sat, 16 Nov 2002 22:26:09 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <V8QYBR6H>; Sun, 17 Nov 2002 04:26:07 +0100
Message-ID: <F74EF3316D9CD4118D8400508BAEDCAA07615EDF@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Mike Heard (E-mail)" <heard@pobox.com>
Cc: "Hubmib Mailing List (E-mail)" <hubmib@ietf.org>
Date: Sun, 17 Nov 2002 04:26:06 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [Hubmib] AD review of draft-ietf-hubmib-wis-mib-04.txt
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Id: <hubmib.ietf.org>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=subscribe>

Sorry that this took so long

- SMICng tells me that Gauge32 is being used without being IMPORTED

- object etherWisDeviceTxTestPatternMode starts ENUM at zero.
  I see the other INTEGER based ENUM does too
  I know it is a CLR, but if it is no problem, then why not start 
  at 1 as recommended by RFC2578?

- thinking aloud: would it be good to do 2 MODULE COMPLIANCES?
  - one etherWisReadOnlyCompliance which is basically the one you now
    have
  - one etherWisFullCompliance that does not specify the min-access to
    read-only
  But I am not sure, cause we do not allow just read-only to the writable
  objects in this MIB module, while we do allow sonet objects to be
  read-only. Maybe I do not understand exactly why?

- Sections 3.1, 3.2 and 3.3 talk about requirements to implement pieces
  of other MIB modules. I see some of it (from sonet mib) back in the
  MODULE-COMPLIANCE. Should we not just include all of the required
  objects from other MIB modules in the MODULE-COMPLIANCE?

-  etherWisDeviceRxTestPatternErrors is a read-write Gauge32
   If I understand it correctly, then you can only SET a value of zero
   If this is a correct understanding, then I would expect to see that
   specified in the MODULE-COMPLIANCE with a WRITE-SYNTAX Gauge32(0)

- In the security section, it would be good to also say someting
  about (non-)vulnerability of read-only objects
   

Editorial/nits
- RFC-Editor no longer accepts more taht 5 authors on front page
  see http://www.rfc-editor.org/policy.html
- Not sure RFC-Editor will accept WAN as acronym in title
  see: http://www.rfc-editor.org/policy.html
- pls expand acronyms when they are first used. For example sect
  3 PCS, PMA, PHY
  see: http://www.rfc-editor.org/policy.html
- It would be good to add the wg mailinglist info to the DESCRIPTION
  clause of the MODULE-IDENTITY
- You talk in various MIB objects about ifAdminState, but I think the
  correct descriptor is ifAdminStatus
- etherWisSectionCurrentJ0Transmitted
  While it is a value "to be transmitted"
  WOuld it be good to reflect that in the descriptor, maybe
     etherWisSectionCurrentJ0ToBeTransmitted
  You have a few more of those

Questions:
- Can you explain why in sections 3.8.1, 3.8.2, 3.8.3 and 3.8.4 
  you use SHALL and not MUST ?? 
- Do we know if/when the IEEE normative document will be final
  so that the normative reference can be resolved?

Thanks,
Bert 
_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib