Re: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB Dr. Review
"Kalyan (Srinivas)Tata" <stata@checkpoint.com> Thu, 10 June 2010 19:37 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 05AEF28C0FA; Thu, 10 Jun 2010 12:37:03 -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_53=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 WwJqrucnlnwf; Thu, 10 Jun 2010 12:37:01 -0700 (PDT)
Received: from us.checkpoint.com (usmail2.us.checkpoint.com [216.200.240.146]) by core3.amsl.com (Postfix) with ESMTP id 74E1F28C0E3; Thu, 10 Jun 2010 12:37:01 -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 o5AJY7Za029698; Thu, 10 Jun 2010 12:34:07 -0700
Received: from USEXCHANGE.ad.checkpoint.com ([216.200.240.132]) by US-EX01.ad.checkpoint.com ([216.200.240.139]) with mapi; Thu, 10 Jun 2010 12:34:04 -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: Thu, 10 Jun 2010 12:34:03 -0700
Thread-Topic: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB Dr. Review
Thread-Index: Acq8m1X7o+23A1VGQBqqieCc8WuA7xLm45Xg
Message-ID: <9FFC3234F1B7F0439C9B8BF94A83F482152B162D1E@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>
In-Reply-To: <002201cabc98$04417510$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>, "draft-ietf-vrrp-unified-mib@tools.ietf.org" <draft-ietf-vrrp-unified-mib@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: Thu, 10 Jun 2010 19:37:03 -0000
Hi Joan, Sorry for the delay (The usual got busy excuse :) ). I started on the edits for new draft and would like your comments/input on the following. Also as I started to edit, I needed some clarifications on your earlier input. This would be the new draft name: draft-ietf-vrrp-v3-mib-00.txt I also have to get an IANA assigned OID under mib-2. VRRPv3-MIB DEFINITIONS ::= BEGIN Vrrpv3MIB MODULE-IDENTITY . . ::= { mib-2 ZZZ } -- EdNote: Please replace ZZZ with a real OID once it is -- allocated and remove this note. I will have an IANA considerations section. [Kalyan>] Is this OK? [Kalyan>] Also, I am using the same group/table names as the previous draft - I think that should be OK. Just want to confirm with you. I also have some questions on your earlier comments: >> >> I would like to see a discussion of the indexing wrt the device. >> The warnings from the MIB compiler indicate that there may be a >> better indexing (table structure) available. That doesn't mean >> that you need to resolve the warnings, but I would like to see >> some text included which shows why the chosen indexes are >> advantageous for the VRRP router, and the Virtual Routers. >> >> IMHO, if an interface goes down, >> then would be probably more advantageous >> to know the Virtual router(s) associated with that interface. >> (and subsequently the IP addresses on those Virtual Routers). >>>> > [Kalyan>] I do not have any strong reasons for the indexing, As I > mentioned, It was suggested in the earlier meeting and it remained that > way during all these revisions. I will change this to ifIndex, VrId, > AddrType > So will revisit this in the next email or two. [Kalyan>] Shell I go ahead and change the order of indexing to ifindex, VrId, AddrType? 11) Section 10. Please specify that this is the VRRP MIB Module Definition [Kalyan>] I am not sure if you wanted me to specify this some place other than in Description section. Following is what I had. DESCRIPTION "This MIB describes objects used for managing Virtual Router Redundancy Protocol version 3 (VRRPv3) for IPv4 and IPv6. Copyright (C) The Internet Society (2010)." * 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. [Kalyan>] _______________________________________________ vrrp mailing list vrrp@ietf.org https://www.ietf.org/mailman/listinfo/vrrp Scanned by Check Point Total Security Gateway.
- [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB Dr.… Joan Cucchiara
- Re: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB… Kalyan (Srinivas)Tata
- Re: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB… Kalyan (Srinivas)Tata
- Re: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB… Joan Cucchiara
- Re: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB… Kalyan (Srinivas)Tata
- Re: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB… Joan Cucchiara
- Re: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB… Mukesh Gupta
- Re: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB… Kalyan (Srinivas)Tata
- Re: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB… Kalyan (Srinivas)Tata
- Re: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB… Joan Cucchiara
- Re: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB… Kalyan (Srinivas)Tata
- Re: [VRRP] Going on Vacation 7/5 to 7/23 Kalyan (Srinivas)Tata
- Re: [VRRP] Going on Vacation 7/5 to 7/23 Joan Cucchiara