Re: [MIB-DOCTORS] MIB doctor review of draft-ietf-manet-olsrv2-mib-08.txt (UNCLASSIFIED)

Randy Presuhn <randy_presuhn@mindspring.com> Tue, 28 May 2013 22:16 UTC

Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41E4F21F8454 for <mib-doctors@ietfa.amsl.com>; Tue, 28 May 2013 15:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MsJr4OVOXi+r for <mib-doctors@ietfa.amsl.com>; Tue, 28 May 2013 15:15:58 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id EA54E21F8633 for <mib-doctors@ietf.org>; Tue, 28 May 2013 15:15:57 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=LDKi9fM0QKst9aPbCNtU2jf7V9CVtkKZ8tmaI/VfIqiJKkXVOsxinGalfAlaeN/i; h=Message-ID:Date:From:Reply-To:To:Subject:Cc:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.38] (helo=elwamui-lapwing.atl.sa.earthlink.net) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1UhSBN-00068R-TI; Tue, 28 May 2013 18:15:53 -0400
Received: from 99.23.160.185 by webmail.earthlink.net with HTTP; Tue, 28 May 2013 18:15:53 -0400
Message-ID: <1753780.1369779353736.JavaMail.root@elwamui-lapwing.atl.sa.earthlink.net>
Date: Tue, 28 May 2013 15:15:53 -0700
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: "Cole, Robert G CIV USARMY CERDEC (US)" <robert.g.cole.civ@mail.mil>, 'Benoit Claise' <bclaise@cisco.com>, "Robert G. Cole" <rgcole01@comcast.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Mailer: EarthLink Zoo Mail 1.0
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88880ff2f3e23ebe94655c7268b84638ee62104b39749be8179350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.38
Cc: "draft-ietf-manet-olsrv2-mib.all@tools.ietf.org" <draft-ietf-manet-olsrv2-mib.all@tools.ietf.org>, "mib-doctors@ietf.org" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] MIB doctor review of draft-ietf-manet-olsrv2-mib-08.txt (UNCLASSIFIED)
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Randy Presuhn <randy_presuhn@mindspring.com>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 28 May 2013 22:16:04 -0000

Hi -

>From: "Cole, Robert G CIV USARMY CERDEC (US)" <robert.g.cole.civ@mail.mil>
>Sent: May 28, 2013 12:44 PM
>To: 'Benoit Claise' <bclaise@cisco.com>, Randy Presuhn <randy_presuhn@mindspring.com>, "Robert G. Cole" <rgcole01@comcast.net>
>Cc: "draft-ietf-manet-olsrv2-mib.all@tools.ietf.org" <draft-ietf-manet-olsrv2-mib.all@tools.ietf.org>, "mib-doctors@ietf.org" <mib-doctors@ietf.org>
>Subject: RE: [MIB-DOCTORS] MIB doctor review of	draft-ietf-manet-olsrv2-mib-08.txt (UNCLASSIFIED)
>
>Classification: UNCLASSIFIED
>Caveats: NONE
>
>Benoit,
>
>Not all the tables in the olsrv2-mib are augments to the nhdp-mib.  There
>are some new tables in the olsrv2-mib as well.  Specifically, the
>olsrv2TibAdRemoteRouterSetTable uses an index of syntax '
>NeighborRouterIndex'.  I interpreted Randy's concerns as related to the use
>of the NeighborRouterIndex in this table and in the nhdp-mib to ensure
>consistency of indices.  It sounds as if my text changes need some further
>clarifications.

If the values need to be consistent in order for this to work correctly
(and from the comments it sounds like they do) then a "SHOULD" is not
appropriate.  If something will not work unless done in a particular way
(e.g. the values of type NeighborRouterIndex here need to match the values
used in the nhdp-mib in that system) then it's really a "MUST" situation.

Randy