[MIB-DOCTORS] Additional comments on draft-ietf-magma-mgmd-mib-12.txt
"Bert Wijnen \(IETF\)" <bertietf@bwijnen.net> Mon, 22 September 2008 16:16 UTC
Return-Path: <mib-doctors-bounces@ietf.org>
X-Original-To: mib-doctors-archive@optimus.ietf.org
Delivered-To: ietfarch-mib-doctors-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9AC273A67EF; Mon, 22 Sep 2008 09:16:27 -0700 (PDT)
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 226523A67EF for <mib-doctors@core3.amsl.com>; Mon, 22 Sep 2008 09:16:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 6txGIkjexw89 for <mib-doctors@core3.amsl.com>; Mon, 22 Sep 2008 09:16:26 -0700 (PDT)
Received: from relay.versatel.net (relay.versatel.net [62.250.3.110]) by core3.amsl.com (Postfix) with SMTP id 4C94E28C1D9 for <mib-doctors@ietf.org>; Mon, 22 Sep 2008 09:15:36 -0700 (PDT)
Received: (qmail 30037 invoked from network); 22 Sep 2008 16:15:02 -0000
Received: from unknown (HELO BertLaptop) (87.215.199.34) by relay.versatel.net with SMTP; 22 Sep 2008 16:15:02 -0000
Message-ID: <455F0140662D4F5B8979B4975865EFCF@BertLaptop>
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
To: Brian Haberman <brian@innovationslab.net>
Date: Mon, 22 Sep 2008 18:14:07 +0200
Organization: Consultant
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
Cc: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, magma@ietf.org, dthaler@windows.microsoft.com
Subject: [MIB-DOCTORS] Additional comments on draft-ietf-magma-mgmd-mib-12.txt
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mib-doctors-bounces@ietf.org
Errors-To: mib-doctors-bounces@ietf.org
I am not subscribed to the magma mailing list. Hopefully Brian can forward. In the past, I had only done some MIB SYNTAX checking (with SMICng) on the earlier versions of this MIB document. The SYNTAX errors I then found have now been fixed. Thanks. I never did a complete MIB review for this MIB module. Neither did I do so this time. I believe that full MIB doctor review was done by Dave Thaler. I assume he will check if his comments have been properly addressed. I now happend to browse through the MIB module some more, and I am somewhat suprised by the many MODULE-COMPLIANCE staments. But not only suprised. I am also confused. For example, I am wondering how the following 2 statements differ. I can see in the DESCRIPTION clauses some differences, but none of that is machine-readable. mgmdIgmpV1HostReadMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "A read-only compliance statement for hosts running IGMPv1 [RFC 1112] and implementing the MGMD MIB. IGMPv1 hosts must support the IPv4 address type." MODULE -- this module MANDATORY-GROUPS { mgmdHostBaseMIBGroup } GROUP mgmdHostOptMIBGroup DESCRIPTION "Write access is not required." ::= { mgmdMIBCompliance 1 } mgmdMldV1HostMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "A read-only compliance statement for hosts running MLDv1 [RFC 2710] and implementing the MGMD MIB. MLDv1 hosts must support the IPv6 address type." MODULE -- this module MANDATORY-GROUPS { mgmdHostBaseMIBGroup } GROUP mgmdHostOptMIBGroup DESCRIPTION "Read-only access required." ::= { mgmdMIBCompliance 8 } But even worse, In the two OBJECT GROUPS that play a role here, I see: mgmdHostBaseMIBGroup OBJECT-GROUP OBJECTS { mgmdHostInterfaceStatus } STATUS current DESCRIPTION "The basic collection of objects providing management of MGMD version 1, 2 or 3 for hosts." ::= { mgmdMIBGroups 1 } mgmdHostOptMIBGroup OBJECT-GROUP OBJECTS { mgmdHostCacheLastReporter, mgmdHostCacheUpTime, mgmdHostInterfaceQuerier, mgmdInverseHostCacheAddress } STATUS current DESCRIPTION "A collection of optional read-only objects for MGMD hosts. Supporting this group can be especially useful in an environment with a router which does not support the MGMD MIB." ::= { mgmdMIBGroups 6 } First, in principle, you do not specify in the DESCRIPTION clasue of an OBJECT-GROUP if they are "optional or not". They are a GROUP, nothing more. If they are mandatory or optional, that is specified in the MODULE-COMPLIANCE. They could be optional in one MODULE-COMPLIANCE and MANDATORY in another. I personally would even prefer the "Opt" is not part of the name of the group. Second, if they are MAX-ACCESS read-only in the OBJECT definition, then that is what it is. If they have MAX-ACCESS read-write or read-create on the OBJECT definition, then they could be read-only for a module-compliance, but again, that is specified in the MODULE-COMPLIANCE statement in the OBJECT clause underneath a MANDATORY-GROUPS or GROUP clause in the MODULE-COMPLIANCE. Again, they could be OK in read-only mode in one MODULE-COMPLIACNE and read-write in another. Now... the object in the first group does have a read-create object. To make a read-only implementation compliant, you would do so by adding a OBJECT clause to the MODULE-COMPLIANCE, see below. My third problem is that it is not clear how you want this implemented. Does it mean that for this MODULE-COMPLIANCE you only have to have the rowstatus object and none of the otehr objects in the table? The objects in the 2nd group all happen to be read-only objects. So although the comment about them being read-only objects does not harm, I think I would not state so in the OBJECT-GROUP DESCRIPTION clause. But that is a NIT And there is certainly not a need to state that "write access is not required" in the MODULE-COMPLIANCE. The objects have MAX-ACCESS of read-only. so !!! You speak about ipv4 or ipv6 support, and such can also be specified in OBJECT clauses (so it become machine readable), see below. I wonder if mgmdIgmpV1HostReadMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "A read-only compliance statement for hosts running IGMPv1 [RFC 1112] and implementing the MGMD MIB. IGMPv1 hosts must support the IPv4 address type." Means that only IPv4 needs to be supported, or that both IPv4 AND IPv6 must be supported? My understanding from that text would be "only IPv4". You may want to clarify that. If you look at my module-compliance suggestion below, then you can see that that makes it much clearer (I have stated it how I understood it). Same for mgmdMldV1HostMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "A read-only compliance statement for hosts running MLDv1 [RFC 2710] and implementing the MGMD MIB. MLDv1 hosts must support the IPv6 address type." Does that mean ONLY IPv6 or both IPv4 and IPv6? So to better document the module compliance, I would do something like: mgmdIgmpV1HostReadMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "A read-only compliance statement for hosts running IGMPv1 [RFC 1112] and implementing the MGMD MIB. IGMPv1 hosts must support only the IPv4 address. In the index, this means for object mgmdHostInterfaceQuerierType OBJECT mgmdHostInterfaceQuerierType SYNTAX InetAddressType {ipv4(1)} " MODULE -- this module MANDATORY-GROUPS { mgmdHostBaseMIBGroup } OBJECT mgmdHostInterfaceStatus SYNTAX RowStatus {active(1)} MIN-ACCESS read-only DESCRIPTION "read-write or read-create access is not required and only the value 'active(1)' needs to be supported" GROUP mgmdHostOptMIBGroup DESCRIPTION "Supporting this optional group can be especially useful in an environment with a router which does not support the MGMD MIB." ::= { mgmdMIBCompliance 1 } Before I go and try to do the other MODULE-COMPLIANCE statements (or help with them), I would first like to hear the author/editor opinion and the opinion of the WG. Bert Wijnen _______________________________________________ MIB-DOCTORS mailing list MIB-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/mib-doctors
- [MIB-DOCTORS] Additional comments on draft-ietf-m… Bert Wijnen (IETF)
- [MIB-DOCTORS] Fw: [Fwd: Additional comments on dr… Bert Wijnen (IETF)
- Re: [MIB-DOCTORS] [Fwd: Additional comments on dr… Bert Wijnen (IETF)
- Re: [MIB-DOCTORS] [Fwd: Additional comments on dr… Bert Wijnen (IETF)
- Re: [MIB-DOCTORS] [Fwd: Additional comments on dr… Bert Wijnen (IETF)
- [MIB-DOCTORS] Weird OBJECT-GROUPS (grouping) in d… Bert Wijnen (IETF)