Re: [VRRP] Going on Vacation 7/5 to 7/23
"Joan Cucchiara" <jcucchiara@mindspring.com> Sat, 03 July 2010 17:30 UTC
Return-Path: <jcucchiara@mindspring.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 9B4063A682A for <vrrp@core3.amsl.com>; Sat, 3 Jul 2010 10:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.369
X-Spam-Level: *
X-Spam-Status: No, score=1.369 tagged_above=-999 required=5 tests=[AWL=0.767, BAYES_50=0.001, J_CHICKENPOX_56=0.6, 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 5eVYy-p31POM for <vrrp@core3.amsl.com>; Sat, 3 Jul 2010 10:30:54 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by core3.amsl.com (Postfix) with ESMTP id B33003A67F4 for <vrrp@ietf.org>; Sat, 3 Jul 2010 10:30:53 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=CdJ6Idx3DAKsj5572+c481YOsZj8DoqVAd7Rbl+dCHZAwK73uC/6pnon++z/Bq/u; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [141.154.115.92] (helo=JoanPC) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <jcucchiara@mindspring.com>) id 1OV6YK-0007xK-Qp; Sat, 03 Jul 2010 13:30:57 -0400
Message-ID: <001401cb1ad5$7e5e8130$04000100@JoanPC>
From: Joan Cucchiara <jcucchiara@mindspring.com>
To: "Kalyan (Srinivas)Tata" <stata@checkpoint.com>, Mukesh Gupta <mukesh@juniper.net>, Adrian Farrel <Adrian.Farrel@huawei.com>, tata_kalyan@yahoo.com, "Dan Romascanu (E-mail)" <dromasca@avaya.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> <9FFC3234F1B7F0439C9B8BF94A83F482152C20DFCA@USEXCHANGE.ad.checkpoint.com> <007201cb16e3$36912420$6501a8c0@JoanPC> <497B6D90E0023142AF34948DEFFAB38D3AC45441E5@EMBX01-HQ.jnpr.net> <000901cb17a3$49c5d0c0$6501a8c0@JoanPC> <9FFC3234F1B7F0439C9B8BF94A83F482152C38DF37@USEXCHANGE.ad.checkpoint.com> <000d01cb17e5$6a4fb7b0$6501a8c0@JoanPC> <9FFC3234F1B7F0439C9B8BF94A83F482152C38E066@USEXCHANGE.ad.checkpoint.com> <005e01cb191b$56ca21d0$6501a8c0@JoanPC> <9FFC3234F1B7F0439C9B8BF94A83F482152C38E4C2@USEXCHANGE.ad.checkpoint.com>
Date: Sat, 03 Jul 2010 13:30:55 -0400
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-ELNK-Trace: 4d68bbe9cb71969ea344cf2d1a8e60840a9da525759e2654373be00996ac1185a8169acd567ded0f7ef9f80aaf77e5a4350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 141.154.115.92
Cc: vrrp-chairs@tools.ietf.org, vrrp@ietf.org
Subject: Re: [VRRP] Going on Vacation 7/5 to 7/23
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: Sat, 03 Jul 2010 17:30:55 -0000
Hi Kalyan, Following are NITs: notmaster (0), * please capitalize as: notMaster(0) vridError(4) * please capitalize: vrIdError(4) Thanks, -Joan ----- Original Message ----- From: "Kalyan (Srinivas)Tata" <stata@checkpoint.com> To: "Joan Cucchiara" <jcucchiara@mindspring.com>; "Mukesh Gupta" <mukesh@juniper.net>; "Adrian Farrel" <Adrian.Farrel@huawei.com>; <tata_kalyan@yahoo.com>; "Dan Romascanu (E-mail)" <dromasca@avaya.com> Cc: <vrrp-chairs@tools.ietf.org>; <vrrp@ietf.org> Sent: Thursday, July 01, 2010 2:25 PM Subject: RE: Going on Vacation 7/5 to 7/23 [Kalyan>] Hi Joan, I am CCing the WG to get any input on the following. 5) I think I asked about these before, the accessible-for-notify scalar objects could become part of the Statistics table (as part of the row's objects) and I think this proabably gives more information (for example, if the notifications are disabled, then an operator will still be able to see these "Reason" values). There may need to be an additional enum added, e.g. to vrrpv3ProtoErrReason, noError(0), etc.. I would encourage that this be considered. [Kalyan>] Following are two descriptions. Please comment. vrrpv3StatisticsNewMasterReason OBJECT-TYPE SYNTAX INTEGER { notmaster (0), priority (1), preempted (2), masterNoResponse (3) } MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the reason for the virtual router to transition to MASTER state. If the virtual router never transitioned to master state, this should be set to notmaster(0). Otherwise this indicates the reason this virtual router transitioned to master state the last time. Used by vrrpv3NewMaster notification." ::= { vrrpv3RouterStatisticsEntry 2 } ------------- DESCRIPTION "This indicates the reason for the virtual router to transition to MASTER state. This should be set to notmaster(0) when vrrpv3OperationsState is in initialize(1) or backup(2) states. Used by vrrpv3NewMaster notification." ===================== vrrpv3StatisticsProtoErrReason OBJECT-TYPE SYNTAX INTEGER { noError (0), ipTtlError (1), versionError (2), checksumError (3), vridError(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the reason for the last protocol error. This should be set to noError (0) when no protocol errors are encountered. Used by vrrpv3ProtoError notification." ::= { vrrpv3RouterStatisticsEntry 6 } Thanks Kalyan ----- Original Message ----- From: "Kalyan (Srinivas)Tata" <stata@checkpoint.com> To: "Joan Cucchiara" <jcucchiara@mindspring.com>; "Mukesh Gupta" <mukesh@juniper.net>; "Adrian Farrel" <Adrian.Farrel@huawei.com>; <tata_kalyan@yahoo.com>; "Dan Romascanu (E-mail)" <dromasca@avaya.com> Cc: <vrrp-chairs@tools.ietf.org> Sent: Tuesday, June 29, 2010 9:06 PM Subject: RE: Going on Vacation 7/5 to 7/23 Thanks Joan, Attached is the draft. Thanks Kalyan -----Original Message----- From: Joan Cucchiara [mailto:jcucchiara@mindspring.com] Sent: Tuesday, June 29, 2010 4:47 PM To: Kalyan (Srinivas)Tata; Mukesh Gupta; Adrian Farrel; tata_kalyan@yahoo.com; Dan Romascanu (E-mail) Cc: vrrp-chairs@tools.ietf.org Subject: Re: Going on Vacation 7/5 to 7/23 Kalyan, You can send me the draft and I'll run the MIB through smicngPRO and take a quick look at it. Thanks, -Joan ----- Original Message ----- From: "Kalyan (Srinivas)Tata" <stata@checkpoint.com> To: "Joan Cucchiara" <jcucchiara@mindspring.com>; "Mukesh Gupta" <mukesh@juniper.net>; "Adrian Farrel" <Adrian.Farrel@huawei.com>; <tata_kalyan@yahoo.com>; "Dan Romascanu (E-mail)" <dromasca@avaya.com> Cc: <vrrp-chairs@tools.ietf.org> Sent: Tuesday, June 29, 2010 3:55 PM Subject: RE: Going on Vacation 7/5 to 7/23 Hi Joan, I think most of the edits are done and implemented most of the comments from your earlier email. I left the vrrpv3NewMasterCntl and vrrpv3ProtoErrorCntl in the mib just in case there are implementations that do not implement RFC3413. I am using simple web mib compiler : http://www.simpleweb.org/ietf/mibs/validate/ Validation report File: vrrpv3_mib.txt Severity level requested: 6 Line Severity Problem 43 2 Object identifier element `zzz' name only allowed as first element I think the above is Ok as it will be replaced by IANA number. I used idnits tool : http://tools.ietf.org/tools/idnits/ ============== idnits 2.12.04 tmp/draft-ietf-vrrp-unified-mib-08.txt: Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year Summary: 0 errors (**), 1 warning (==), 0 comments (--). Should i send you the draft directly to you so you can take a quick look or should i submit the draft? Thanks Kalyan -----Original Message----- From: Joan Cucchiara [mailto:jcucchiara@mindspring.com] Sent: Tuesday, June 29, 2010 8:54 AM To: Mukesh Gupta; Kalyan (Srinivas)Tata; Adrian Farrel; tata_kalyan@yahoo.com; Dan Romascanu (E-mail) Cc: vrrp-chairs@tools.ietf.org Subject: Re: Going on Vacation 7/5 to 7/23 Thanks Mukesh! ----- Original Message ----- From: "Mukesh Gupta" <mukesh@juniper.net> To: "Joan Cucchiara" <jcucchiara@mindspring.com>; "Kalyan (Srinivas)Tata" <stata@checkpoint.com>; "Adrian Farrel" <Adrian.Farrel@huawei.com>; <tata_kalyan@yahoo.com>; "Dan Romascanu (E-mail)" <dromasca@avaya.com> Cc: <vrrp-chairs@tools.ietf.org> Sent: Monday, June 28, 2010 1:57 PM Subject: RE: Going on Vacation 7/5 to 7/23 Joan, Thanks for letting us know. Really appreciate your feedback and contribution to the VRRPv3 MIB draft. Regards, Mukesh -----Original Message----- From: Joan Cucchiara [mailto:jcucchiara@mindspring.com] Sent: Monday, June 28, 2010 9:59 AM To: Kalyan (Srinivas)Tata; Adrian Farrel; tata_kalyan@yahoo.com; Dan Romascanu (E-mail) Cc: vrrp-chairs@tools.ietf.org Subject: Going on Vacation 7/5 to 7/23 Dan, Adrian and Kalyan, Just to let you know, I'm going to be on vacation and will not be checking email very often from July 5 to July 23. Currently, Kalyan is reworking the VRRPv3-MIB document (draft-ietf-vrrp-unified-mib-08.txt) based on Last Call/MIB Dr. review of the prior version. fyi, -Joan ----- Original Message ----- From: "Kalyan (Srinivas)Tata" <stata@checkpoint.com> To: "Joan Cucchiara" <jcucchiara@mindspring.com>; "Adrian Farrel" <Adrian.Farrel@huawei.com>; <tata_kalyan@yahoo.com>; <vrrp@ietf.org> Cc: <vrrp-chairs@tools.ietf.org>; "MIB Doctors (E-mail)" <mib-doctors@ietf.org> Sent: Monday, June 21, 2010 8:02 PM Subject: RE: [VRRP] draft-ietf-vrrp-unified-mib-07.txt MIB Dr. Review 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 Scanned by Check Point Total Security Gateway. Scanned by Check Point Total Security Gateway. 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