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

"Cole, Robert G CIV USARMY CERDEC (US)" <robert.g.cole.civ@mail.mil> Wed, 29 May 2013 13:11 UTC

Return-Path: <robert.g.cole.civ@mail.mil>
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 591DE21F8825 for <mib-doctors@ietfa.amsl.com>; Wed, 29 May 2013 06:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 vm2p36INORjf for <mib-doctors@ietfa.amsl.com>; Wed, 29 May 2013 06:11:02 -0700 (PDT)
Received: from edge-cols.mail.mil (edge-cols.mail.mil [131.64.100.6]) by ietfa.amsl.com (Postfix) with ESMTP id C86CC21F87B7 for <mib-doctors@ietf.org>; Wed, 29 May 2013 06:11:01 -0700 (PDT)
Received: from UCOLHP3F.easf.csd.disa.mil (131.64.100.145) by UCOLHP4Z.easf.csd.disa.mil (131.64.100.6) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 29 May 2013 13:10:59 +0000
Received: from UCOLHP9H.easf.csd.disa.mil ([169.254.5.190]) by UCOLHP3F.easf.csd.disa.mil ([131.64.100.145]) with mapi id 14.03.0123.003; Wed, 29 May 2013 13:09:45 +0000
From: "Cole, Robert G CIV USARMY CERDEC (US)" <robert.g.cole.civ@mail.mil>
To: 'Benoit Claise' <bclaise@cisco.com>, Randy Presuhn <randy_presuhn@mindspring.com>
Thread-Topic: [MIB-DOCTORS] MIB doctor review of draft-ietf-manet-olsrv2-mib-08.txt (UNCLASSIFIED)
Thread-Index: AQHOW/WJeh9ou+PzQEOCDR44oV8HL5kcI03w
Date: Wed, 29 May 2013 13:09:44 +0000
Message-ID: <B9468E58D6A0A84AAD66FE4E694BEABB55E33713@ucolhp9h.easf.csd.disa.mil>
References: <1753780.1369779353736.JavaMail.root@elwamui-lapwing.atl.sa.earthlink.net> <51A53407.3040404@cisco.com>
In-Reply-To: <51A53407.3040404@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [131.64.62.4]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_006C_01CE5C4C.41641130"
MIME-Version: 1.0
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>, "Robert G. Cole" <rgcole01@comcast.net>
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
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: Wed, 29 May 2013 13:11:07 -0000

Classification: UNCLASSIFIED
Caveats: NONE

Benoit,

The indexes in the previous sentence.  I'll clarify and incorporate Randy's 
comment from below as well.

Thanks, Bob

Robert G. Cole
Comm:  443.395.8744
Email: robert.g.cole@us.army.mil


-----Original Message-----
From: Benoit Claise [mailto:bclaise@cisco.com]
Sent: Tuesday, May 28, 2013 6:48 PM
To: Randy Presuhn
Cc: Cole, Robert G CIV USARMY CERDEC (US); Robert G. Cole; 
draft-ietf-manet-olsrv2-mib.all@tools.ietf.org; mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] MIB doctor review of 
draft-ietf-manet-olsrv2-mib-08.txt (UNCLASSIFIED)

Bob, Randy,


   OLSRv2 depends on the neighborhood information that is discovered by
   [RFC6130 <https://tools.ietf.org/html/rfc6130> ].  In order to access the 
Objects relating to discovered
   neighbors, the State Group tables of the NHDP-MIB [RFC6779 
<https://tools.ietf.org/html/rfc6779> ] module
   are aligned with this MIB module.  This is accomplished through the
   use of the AUGMENTS capability of SMIv2 and the definition of
   TEXTUAL-CONVENTIONS in the NHDP-MIB module: specifically the
   NeighborRouterIndex.  These object types are used to develop indexes
   into common NHDP-MIB module and routing protocol State Group tables.
   The values of these objects and the semantics of each individual
   value SHOULD be identical for the two MIB modules within a given SNMP
   context.  This will allow for improved cross referencing of
   information across the two MIB modules within a given SNMP context.
My confusion comes from this question: what are "these objects" in the red 
sentence above?
- The indexes in the previous sentence?
- The object types in the previous sentence?
- The augmented objects?
- something else?

Regards, Benoit


	Hi -


		From: "Cole, Robert G CIV USARMY CERDEC (US)" <robert.g.cole.civ@mail.mil> 
<mailto:robert.g.cole.civ@mail.mil>
		Sent: May 28, 2013 12:44 PM
		To: 'Benoit Claise' <bclaise@cisco.com> <mailto:bclaise@cisco.com> , Randy 
Presuhn <randy_presuhn@mindspring.com> <mailto:randy_presuhn@mindspring.com> , 
"Robert G. Cole" <rgcole01@comcast.net> <mailto:rgcole01@comcast.net>
		Cc: "draft-ietf-manet-olsrv2-mib.all@tools.ietf.org" 
<mailto:draft-ietf-manet-olsrv2-mib.all@tools.ietf.org> 
<draft-ietf-manet-olsrv2-mib.all@tools.ietf.org> 
<mailto:draft-ietf-manet-olsrv2-mib.all@tools.ietf.org> , 
"mib-doctors@ietf.org" <mailto:mib-doctors@ietf.org>  <mib-doctors@ietf.org> 
<mailto:mib-doctors@ietf.org>
		Subject: RE: [MIB-DOCTORS] MIB doctor review ofdraft-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





Classification: UNCLASSIFIED
Caveats: NONE