Re: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB Dr. Review

"Kalyan (Srinivas)Tata" <stata@checkpoint.com> Tue, 22 June 2010 00:01 UTC

Return-Path: <stata@checkpoint.com>
X-Original-To: vrrp@core3.amsl.com
Delivered-To: vrrp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CECD23A68DF; Mon, 21 Jun 2010 17:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.399
X-Spam-Level:
X-Spam-Status: No, score=-0.399 tagged_above=-999 required=5 tests=[BAYES_50=0.001, J_CHICKENPOX_56=0.6, RCVD_IN_DNSWL_LOW=-1]
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 4WGrmVEm1YCL; Mon, 21 Jun 2010 17:01:40 -0700 (PDT)
Received: from us.checkpoint.com (usmail2.us.checkpoint.com [216.200.240.146]) by core3.amsl.com (Postfix) with ESMTP id C8E953A67EA; Mon, 21 Jun 2010 17:01:40 -0700 (PDT)
Received: from us-ex01.ad.checkpoint.com (us-ex01.ad.checkpoint.com [216.200.240.139]) by us.checkpoint.com (8.14.4/8.14.4) with ESMTP id o5M030cd024500; Mon, 21 Jun 2010 17:03:00 -0700
Received: from USEXCHANGE.ad.checkpoint.com ([216.200.240.132]) by US-EX01.ad.checkpoint.com ([216.200.240.139]) with mapi; Mon, 21 Jun 2010 17:02:10 -0700
From: "Kalyan (Srinivas)Tata" <stata@checkpoint.com>
To: Joan Cucchiara <jcucchiara@mindspring.com>, Adrian Farrel <Adrian.Farrel@huawei.com>, "tata_kalyan@yahoo.com" <tata_kalyan@yahoo.com>, "vrrp@ietf.org" <vrrp@ietf.org>
Date: Mon, 21 Jun 2010 17:02:08 -0700
Thread-Topic: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB Dr. Review
Thread-Index: AcsO7/eqRuex+ABKSIaJqje+w6at2ACrVl6g
Message-ID: <9FFC3234F1B7F0439C9B8BF94A83F482152C20DFCA@USEXCHANGE.ad.checkpoint.com>
References: <9CEB032BDB454422BA9F65732441BDF0@your029b8cecfe><EDC652A26FB23C4EB6384A4584434A0401F0DE0F@307622ANEX5.global.avaya.com><001c01caaa58$e7924fd0$6501a8c0@JoanPC><EDC652A26FB23C4EB6384A4584434A0401F0E16E@307622ANEX5.global.avaya.com><497B6D90E0023142AF34948DEFFAB38D3A8772AFBA@EMBX01-HQ.jnpr.net> <002201cabc98$04417510$6501a8c0@JoanPC> <9FFC3234F1B7F0439C9B8BF94A83F482152B162D1E@USEXCHANGE.ad.checkpoint.com> <006301cb0eef$71170de0$6501a8c0@JoanPC>
In-Reply-To: <006301cb0eef$71170de0$6501a8c0@JoanPC>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, "vrrp-chairs@tools.ietf.org" <vrrp-chairs@tools.ietf.org>
Subject: Re: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB Dr. Review
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Router Redundancy Protocol <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jun 2010 00:01:41 -0000

Thanks Joan,
	Most of the comments are clear to me now. I Will try to finalize the draft this week.

>
> [Kalyan>] Shell I go ahead and change the order of indexing to ifindex,
> VrId, AddrType?
>

Yes.  Those indexes uniquely identify the vr, so essentially, the tables are 
listed
by vr.   Please note, this is only a suggestion/proposal and the indexing is 
upto the
WG.  I didn't see any comments about this during Last Call, so as far as I'm 
aware
this is good with the WG, right?

[Kalyan>] I did not see any comments either. So I will change the indexing.

>
> * VrId (Textual Convention)
>
> There is already a VrId in RFC2787. While it looks as if the
> only difference is the DESCRIPTION clause, need to caution against
> doing redefining this.  I would suggest creating a VRID TC and
> making the DESCRIPTION simple, for example:  This value uniquely 
> identifies
> a
> Virtual Router on a VRRP router.
>
> While the remaining text is informative, it is not really necessary.
> Please also give a REFERENCE clause for this.
>
> [Kalyan>]
> [Kalyan>] I see the problem of defining VrId.
> [Kalyan>] I am thinking that you are suggesting that I create a new
> VRRP-TC-MIB which would define VrId separately and import in this MIB. Is
> this correct? Even if I define a new TC-MIB I would have to use a 
> different
> name like VrrpId or should I reuse VrId? If I am changing to VrrpId then 
> do
> I really need to define a new TC-MIB? I don't see any other MIB importing
> this either.
>

No, I wasn't suggesting a new MIB module, but definitely a new TC is needed.
This should have a name that indicates v3 and TC like:   Vrrpv3VrIdTC.

After reading this over again, would like to keep your original description, 
but switch
the wording from:

"A number which, along with the IP version and interface index (IfIndex), 
serves..."

to:

"A number which, along with the interface index (IfIndex) and the IP 
version, serves...."

(If you agree with the proposed indexes (above) for  the 
vrrpv3OperationsTable, etc.,
then the proposed wording above for the TC agrees.  In other words, the 
ordering for the
indexes agrees with how this TC is worded.

[Kalyan>] I misunderstood your originally comment. I will change as you proposed.

[Kalyan>] Thanks
Kalyan