
From ankothar@cisco.com  Fri Aug  2 17:06:21 2013
Return-Path: <ankothar@cisco.com>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A19511E8150 for <vrrp@ietfa.amsl.com>; Fri,  2 Aug 2013 17:06:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 LVLv3cwDPVIx for <vrrp@ietfa.amsl.com>; Fri,  2 Aug 2013 17:06:16 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 13BD211E8146 for <vrrp@ietf.org>; Fri,  2 Aug 2013 17:06:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4861; q=dns/txt; s=iport; t=1375488376; x=1376697976; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=R9CgEajyynBeS0FxDIBhK3KVU0esc36mn/wMYbxANQ4=; b=lVvUXj62M1FcBfDR5frup8XqLwfNQsY7syvZ5cVzmTb41FHC82GMK6aN iA9RUpCDQn6o0gVexlvEoQNCgVhFIXgrUr8gL9QTR8/CzI009Txzs3amK aQ2QwGeb2GCR65E/bkiVwJOl+VRhF55qve2Q1NuYXXGhjZ48BuPDraHMQ E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwFAERI/FGtJXHA/2dsb2JhbABagwY1UL8NgR0WdIIkAQEBAQMBAQE3NAsMBgEZBAEBAQoUCS4LFAkJAQQBDQUIAYgHDLkTjkcJEIEHMQ2DE3QDmQmQJIMXgXE5
X-IronPort-AV: E=Sophos;i="4.89,805,1367971200"; d="scan'208";a="242771177"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-1.cisco.com with ESMTP; 03 Aug 2013 00:06:14 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r7306Een030113 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 3 Aug 2013 00:06:14 GMT
Received: from xmb-rcd-x05.cisco.com ([169.254.15.236]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Fri, 2 Aug 2013 19:06:14 -0500
From: "Anurag Kothari (ankothar)" <ankothar@cisco.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "vrrp@ietf.org" <vrrp@ietf.org>
Thread-Topic: Graceful Failover for VRRP
Thread-Index: Ac6P3T4o48vQ/TAOSwOeNRO+A7+U1w==
Date: Sat, 3 Aug 2013 00:06:13 +0000
Message-ID: <A2BB90B33FFDF740876C5AAE307D83DB255B389F@xmb-rcd-x05.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-Auto-Response-Suppress: DR, OOF, AutoReply
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.218.55]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "fhrp-team\(mailer list\)" <fhrp-team@cisco.com>
Subject: [VRRP] Graceful Failover for VRRP
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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 Aug 2013 00:06:21 -0000

Hi

I have submitted the following I-D on this idea:

TXT: http://www.ietf.org/internet-drafts/draft-kothari-vrrp-graceful-failov=
er-00.txt
HTML: http://tools.ietf.org/html/draft-kothari-vrrp-graceful-failover-00

Please review and provide feedback.

Thanks
-Anurag

-----Original Message-----
From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf Of Adr=
ian Farrel
Sent: Wednesday, May 22, 2013 12:12 PM
To: vrrp@ietf.org
Cc: fhrp-team(mailer list)
Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]

Hi,

If you are wondering how to progress this in the IETF, the answer is...

- write an I-D
- discuss it (here)
- polish it
- ask me to sponsor it for publication as an RFC.

Cheers,
Adrian

> -----Original Message-----
> From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf=20
> Of Anurag Kothari (ankothar)
> Sent: 04 March 2013 23:43
> To: sreenatha; vrrp@ietf.org
> Cc: fhrp-team(mailer list)
> Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]
>=20
> Hi Sreenatha
>=20
> If you mean "if I am not wrong" then yes what you have said below is corr=
ect.
>=20
> Also I believe the objective (particularly in case of time sensitive
application) is to
> avoid any unnecessary switch overs; as already suggested earlier let's=20
> call
this a
> "Change Event" instead of "Maintenance Event". The "Change Event"=20
> would be triggered by change in one of the following parameters of the VR=
RP Packet :
>=20
> 1) Priority (Section 5.2.4. of RFC-5798)
> 2) Max Adver Int (Section 5.2.7. of RFC-5798)
>=20
> And possibly:
>=20
> 3) IPvX Address(es) (Section 5.2.9.  of RFC-5798)
>=20
> The "Change Event" would only be handled in Master State and ignored=20
> in other state as the VRRP Packets are only supposed to be sent by the Ma=
ster.
>=20
> So to rephrase the proposal:
>=20
>     - If a Change event is received, then:
>=20
>     + Send an ADVERTISEMENT
>=20
>     + Reset the Adver_Timer to Advertisement_Interval
>=20
>     -endif // Change recv
>=20
> To cover the failover scenario (in the absence of preemption) Priority=20
> =3D 0
will now
> have to be allowed along with the previously discussed modifications=20
> to avoid
a
> storm of Priority =3D 0 Advertisements from two masters.
>=20
> Please Share your thoughts.
>=20
> Thanks
> -Anurag
>=20
> -----Original Message-----
> From: sreenatha [mailto:sreenatha.setty@ibtechnology.com]
> Sent: Saturday, March 02, 2013 3:17 AM
> To: Anurag Kothari (ankothar)
> Cc: vrrp@ietf.org
> Subject: Re: Proposal for Maintenance Event for VRRP [RFC-5798]
>=20
> Hi Anurag,
>      Thanks for clarification.
>=20
>       If i am wrong, user is allowed to configure Priority value as=20
> zero(i.e., Maintenance_Event), priority value will be changed. And=20
> handling of the Maintenance_Event is done only in Master state and=20
> ignored in Backup and Init state.
>=20
> Thanks,
> Sreenatha
>=20
> On 03/01/2013 08:31 PM, Anurag Kothari (ankothar) wrote:
> > Hi Sreenatha
> >
> > I don't think we need to define a "Maintenance_Event" when the=20
> > router is in
> either Init or Backup State. The intention of the "Maintenance_Event"=20
> is to trigger a failover from "Master" to a "Backup" router as soon as=20
> possible (especially when preemption is not configured).
> >
> > But if you are asking if priority =3D 0 should be allowed (either by=20
> > user
> configuration or dynamically) when the router is in "Init" or "Backup"=20
> state
then I
> think the answer should be yes, It should be treated just like any=20
> other
change in
> priority is treated when the router is in these states.
> >
> > Please let me know if I am missing something.
> >
> > Thanks
> > -Anurag
> >
> >
>=20
> Disclaimer :
> This email communication may contain privileged and confidential=20
> information and is intended for the use of the addressee only.If you=20
> are not an intended recipient you are requested not to reproduce, copy=20
> disseminate or in any
manner
> distribute this email communication as the same is strictly=20
> prohibited. If you
have
> received this email in error, please notify the sender immediately by=20
> return
e-
> mail and delete the communication sent in error. Email communications=20
> cannot be guaranteed to be secure & error free and IB Technology is=20
> not liable for
any
> errors in the email communication or for the proper, timely and=20
> complete transmission thereof.
>=20
> _______________________________________________
> vrrp mailing list
> vrrp@ietf.org
> https://www.ietf.org/mailman/listinfo/vrrp

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www.ietf.org/mailman/listinfo/vrrp

From aceler@avaya.com  Sat Aug  3 11:21:19 2013
Return-Path: <aceler@avaya.com>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DC3D21F9EEE for <vrrp@ietfa.amsl.com>; Sat,  3 Aug 2013 11:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 UkFejhti8xJt for <vrrp@ietfa.amsl.com>; Sat,  3 Aug 2013 11:21:13 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 8F48F21F893E for <vrrp@ietf.org>; Sat,  3 Aug 2013 11:21:13 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAPhI/VGHCzI1/2dsb2JhbABagmUhNVC/FIEdFnSCJAEBAQEDAQEBDyg0CwwEAgEIDQQEAQEBChQJBycLFAkIAQEEAQ0FCAESB4duAQubM5sNF45ICRCBBzEHBoMTdAOZCoUeiweDF4FxOQ
X-IronPort-AV: E=Sophos;i="4.89,808,1367985600"; d="scan'208";a="22209580"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 03 Aug 2013 14:21:12 -0400
Received: from unknown (HELO AZ-US1EXHC03.global.avaya.com) ([135.11.85.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 03 Aug 2013 14:14:34 -0400
Received: from AZ-US1EXMB05.global.avaya.com ([fe80::d51e:20b6:bd25:82b7]) by AZ-US1EXHC03.global.avaya.com ([::1]) with mapi id 14.03.0146.000; Sat, 3 Aug 2013 14:21:11 -0400
From: "Celer, Alicja (Alicja)" <aceler@avaya.com>
To: "Anurag Kothari (ankothar)" <ankothar@cisco.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "vrrp@ietf.org" <vrrp@ietf.org>
Thread-Topic: Graceful Failover for VRRP
Thread-Index: Ac6P3T4o48vQ/TAOSwOeNRO+A7+U1wAmJQlG
Date: Sat, 3 Aug 2013 18:21:11 +0000
Message-ID: <BADCB091A7B456478087D87523A86EBA42C5431A@AZ-US1EXMB05.global.avaya.com>
References: <A2BB90B33FFDF740876C5AAE307D83DB255B389F@xmb-rcd-x05.cisco.com>
In-Reply-To: <A2BB90B33FFDF740876C5AAE307D83DB255B389F@xmb-rcd-x05.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.11.30.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "fhrp-team\(mailer list\)" <fhrp-team@cisco.com>
Subject: Re: [VRRP] Graceful Failover for VRRP
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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 Aug 2013 18:21:19 -0000

Hi Anurag,=0A=
=0A=
I've posted a draft addressing a similar issue and proposing a similar solu=
tion in 1999. Did you get a chance to review it?  If not, would you like a =
copy maybe we converge on a solution? =0A=
=0A=
kind regar ds,=0A=
Alicja=0A=
________________________________________=0A=
From: vrrp-bounces@ietf.org [vrrp-bounces@ietf.org] on behalf of Anurag Kot=
hari (ankothar) [ankothar@cisco.com]=0A=
Sent: Friday, August 02, 2013 8:06 PM=0A=
To: adrian@olddog.co.uk; vrrp@ietf.org=0A=
Cc: fhrp-team(mailer list)=0A=
Subject: [VRRP] Graceful Failover for VRRP=0A=
=0A=
Hi=0A=
=0A=
I have submitted the following I-D on this idea:=0A=
=0A=
TXT: http://www.ietf.org/internet-drafts/draft-kothari-vrrp-graceful-failov=
er-00.txt=0A=
HTML: http://tools.ietf.org/html/draft-kothari-vrrp-graceful-failover-00=0A=
=0A=
Please review and provide feedback.=0A=
=0A=
Thanks=0A=
-Anurag=0A=
=0A=
-----Original Message-----=0A=
From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf Of Adr=
ian Farrel=0A=
Sent: Wednesday, May 22, 2013 12:12 PM=0A=
To: vrrp@ietf.org=0A=
Cc: fhrp-team(mailer list)=0A=
Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]=0A=
=0A=
Hi,=0A=
=0A=
If you are wondering how to progress this in the IETF, the answer is...=0A=
=0A=
- write an I-D=0A=
- discuss it (here)=0A=
- polish it=0A=
- ask me to sponsor it for publication as an RFC.=0A=
=0A=
Cheers,=0A=
Adrian=0A=
=0A=
> -----Original Message-----=0A=
> From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf=0A=
> Of Anurag Kothari (ankothar)=0A=
> Sent: 04 March 2013 23:43=0A=
> To: sreenatha; vrrp@ietf.org=0A=
> Cc: fhrp-team(mailer list)=0A=
> Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]=0A=
>=0A=
> Hi Sreenatha=0A=
>=0A=
> If you mean "if I am not wrong" then yes what you have said below is corr=
ect.=0A=
>=0A=
> Also I believe the objective (particularly in case of time sensitive=0A=
application) is to=0A=
> avoid any unnecessary switch overs; as already suggested earlier let's=0A=
> call=0A=
this a=0A=
> "Change Event" instead of "Maintenance Event". The "Change Event"=0A=
> would be triggered by change in one of the following parameters of the VR=
RP Packet :=0A=
>=0A=
> 1) Priority (Section 5.2.4. of RFC-5798)=0A=
> 2) Max Adver Int (Section 5.2.7. of RFC-5798)=0A=
>=0A=
> And possibly:=0A=
>=0A=
> 3) IPvX Address(es) (Section 5.2.9.  of RFC-5798)=0A=
>=0A=
> The "Change Event" would only be handled in Master State and ignored=0A=
> in other state as the VRRP Packets are only supposed to be sent by the Ma=
ster.=0A=
>=0A=
> So to rephrase the proposal:=0A=
>=0A=
>     - If a Change event is received, then:=0A=
>=0A=
>     + Send an ADVERTISEMENT=0A=
>=0A=
>     + Reset the Adver_Timer to Advertisement_Interval=0A=
>=0A=
>     -endif // Change recv=0A=
>=0A=
> To cover the failover scenario (in the absence of preemption) Priority=0A=
> =3D 0=0A=
will now=0A=
> have to be allowed along with the previously discussed modifications=0A=
> to avoid=0A=
a=0A=
> storm of Priority =3D 0 Advertisements from two masters.=0A=
>=0A=
> Please Share your thoughts.=0A=
>=0A=
> Thanks=0A=
> -Anurag=0A=
>=0A=
> -----Original Message-----=0A=
> From: sreenatha [mailto:sreenatha.setty@ibtechnology.com]=0A=
> Sent: Saturday, March 02, 2013 3:17 AM=0A=
> To: Anurag Kothari (ankothar)=0A=
> Cc: vrrp@ietf.org=0A=
> Subject: Re: Proposal for Maintenance Event for VRRP [RFC-5798]=0A=
>=0A=
> Hi Anurag,=0A=
>      Thanks for clarification.=0A=
>=0A=
>       If i am wrong, user is allowed to configure Priority value as=0A=
> zero(i.e., Maintenance_Event), priority value will be changed. And=0A=
> handling of the Maintenance_Event is done only in Master state and=0A=
> ignored in Backup and Init state.=0A=
>=0A=
> Thanks,=0A=
> Sreenatha=0A=
>=0A=
> On 03/01/2013 08:31 PM, Anurag Kothari (ankothar) wrote:=0A=
> > Hi Sreenatha=0A=
> >=0A=
> > I don't think we need to define a "Maintenance_Event" when the=0A=
> > router is in=0A=
> either Init or Backup State. The intention of the "Maintenance_Event"=0A=
> is to trigger a failover from "Master" to a "Backup" router as soon as=0A=
> possible (especially when preemption is not configured).=0A=
> >=0A=
> > But if you are asking if priority =3D 0 should be allowed (either by=0A=
> > user=0A=
> configuration or dynamically) when the router is in "Init" or "Backup"=0A=
> state=0A=
then I=0A=
> think the answer should be yes, It should be treated just like any=0A=
> other=0A=
change in=0A=
> priority is treated when the router is in these states.=0A=
> >=0A=
> > Please let me know if I am missing something.=0A=
> >=0A=
> > Thanks=0A=
> > -Anurag=0A=
> >=0A=
> >=0A=
>=0A=
> Disclaimer :=0A=
> This email communication may contain privileged and confidential=0A=
> information and is intended for the use of the addressee only.If you=0A=
> are not an intended recipient you are requested not to reproduce, copy=0A=
> disseminate or in any=0A=
manner=0A=
> distribute this email communication as the same is strictly=0A=
> prohibited. If you=0A=
have=0A=
> received this email in error, please notify the sender immediately by=0A=
> return=0A=
e-=0A=
> mail and delete the communication sent in error. Email communications=0A=
> cannot be guaranteed to be secure & error free and IB Technology is=0A=
> not liable for=0A=
any=0A=
> errors in the email communication or for the proper, timely and=0A=
> complete transmission thereof.=0A=
>=0A=
> _______________________________________________=0A=
> vrrp mailing list=0A=
> vrrp@ietf.org=0A=
> https://www.ietf.org/mailman/listinfo/vrrp=0A=
=0A=
_______________________________________________=0A=
vrrp mailing list=0A=
vrrp@ietf.org=0A=
https://www.ietf.org/mailman/listinfo/vrrp=0A=
_______________________________________________=0A=
vrrp mailing list=0A=
vrrp@ietf.org=0A=
https://www.ietf.org/mailman/listinfo/vrrp=0A=

From ankothar@cisco.com  Sat Aug  3 11:36:52 2013
Return-Path: <ankothar@cisco.com>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B795C21F9F52 for <vrrp@ietfa.amsl.com>; Sat,  3 Aug 2013 11:36:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 hpOFAgqsFK+p for <vrrp@ietfa.amsl.com>; Sat,  3 Aug 2013 11:36:47 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id AA01F11E80AD for <vrrp@ietf.org>; Sat,  3 Aug 2013 11:36:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6088; q=dns/txt; s=iport; t=1375555007; x=1376764607; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=r72iLLWOm1sENNaktMyonXbTyft8DAdRtgv20yQd04Q=; b=aLmqZfIO6uDX1HUs5fZueJEVChk5d3uLhAY9MMo3RwTG7zI4oQlWD69R ZP03fm8GW6pvqLaZyqo5ySUgB32AojmO5xtZOtdj4pfMeZkaXbOq6uSIC YWxbDgxSXZ34C7k1m7yMX5I3O+8Drdti+bYeIbq1/fiGA5Fd1N06aO0GX A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAOtM/VGtJV2a/2dsb2JhbABagwY1UL8UgR0WdIIkAQEBAQMBAQE3NAsMBAIBCBEEAQEBChQJBycLFAkIAQEEAQ0FCAESh3UMtkWOSAkQgQcPIgcGgxN0A5kKkCWDF4FxOQ
X-IronPort-AV: E=Sophos;i="4.89,808,1367971200"; d="scan'208";a="242951217"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-1.cisco.com with ESMTP; 03 Aug 2013 18:36:47 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r73Ialvx000594 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 3 Aug 2013 18:36:47 GMT
Received: from xmb-rcd-x05.cisco.com ([169.254.15.236]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Sat, 3 Aug 2013 13:36:46 -0500
From: "Anurag Kothari (ankothar)" <ankothar@cisco.com>
To: "Celer, Alicja (Alicja)" <aceler@avaya.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "vrrp@ietf.org" <vrrp@ietf.org>
Thread-Topic: Graceful Failover for VRRP
Thread-Index: Ac6P3T4o48vQ/TAOSwOeNRO+A7+U1wAmJQlGAABFo1A=
Date: Sat, 3 Aug 2013 18:36:45 +0000
Message-ID: <A2BB90B33FFDF740876C5AAE307D83DB255B46EF@xmb-rcd-x05.cisco.com>
References: <A2BB90B33FFDF740876C5AAE307D83DB255B389F@xmb-rcd-x05.cisco.com> <BADCB091A7B456478087D87523A86EBA42C5431A@AZ-US1EXMB05.global.avaya.com>
In-Reply-To: <BADCB091A7B456478087D87523A86EBA42C5431A@AZ-US1EXMB05.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-Auto-Response-Suppress: DR, OOF, AutoReply
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.218.55]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "fhrp-team\(mailer list\)" <fhrp-team@cisco.com>
Subject: Re: [VRRP] Graceful Failover for VRRP
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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 Aug 2013 18:36:53 -0000

Hello Alicja

Sorry, I was not aware of your draft. I did a quick search and I suppose yo=
u are referring to:

http://tools.ietf.org/html/draft-celer-vrrp-ext-00

Please let me know if it is otherwise.

I would definitely go through it and get back to you; If it is the same ide=
a we can surely try to converge on a solution.

Thanks
-Anurag

-----Original Message-----
From: Celer, Alicja (Alicja) [mailto:aceler@avaya.com]=20
Sent: Saturday, August 03, 2013 2:21 PM
To: Anurag Kothari (ankothar); adrian@olddog.co.uk; vrrp@ietf.org
Cc: fhrp-team(mailer list)
Subject: RE: Graceful Failover for VRRP

Hi Anurag,

I've posted a draft addressing a similar issue and proposing a similar solu=
tion in 1999. Did you get a chance to review it?  If not, would you like a =
copy maybe we converge on a solution?=20

kind regar ds,
Alicja
________________________________________
From: vrrp-bounces@ietf.org [vrrp-bounces@ietf.org] on behalf of Anurag Kot=
hari (ankothar) [ankothar@cisco.com]
Sent: Friday, August 02, 2013 8:06 PM
To: adrian@olddog.co.uk; vrrp@ietf.org
Cc: fhrp-team(mailer list)
Subject: [VRRP] Graceful Failover for VRRP

Hi

I have submitted the following I-D on this idea:

TXT: http://www.ietf.org/internet-drafts/draft-kothari-vrrp-graceful-failov=
er-00.txt
HTML: http://tools.ietf.org/html/draft-kothari-vrrp-graceful-failover-00

Please review and provide feedback.

Thanks
-Anurag

-----Original Message-----
From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf Of Adr=
ian Farrel
Sent: Wednesday, May 22, 2013 12:12 PM
To: vrrp@ietf.org
Cc: fhrp-team(mailer list)
Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]

Hi,

If you are wondering how to progress this in the IETF, the answer is...

- write an I-D
- discuss it (here)
- polish it
- ask me to sponsor it for publication as an RFC.

Cheers,
Adrian

> -----Original Message-----
> From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf=20
> Of Anurag Kothari (ankothar)
> Sent: 04 March 2013 23:43
> To: sreenatha; vrrp@ietf.org
> Cc: fhrp-team(mailer list)
> Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]
>
> Hi Sreenatha
>
> If you mean "if I am not wrong" then yes what you have said below is corr=
ect.
>
> Also I believe the objective (particularly in case of time sensitive
application) is to
> avoid any unnecessary switch overs; as already suggested earlier let's=20
> call
this a
> "Change Event" instead of "Maintenance Event". The "Change Event"
> would be triggered by change in one of the following parameters of the VR=
RP Packet :
>
> 1) Priority (Section 5.2.4. of RFC-5798)
> 2) Max Adver Int (Section 5.2.7. of RFC-5798)
>
> And possibly:
>
> 3) IPvX Address(es) (Section 5.2.9.  of RFC-5798)
>
> The "Change Event" would only be handled in Master State and ignored=20
> in other state as the VRRP Packets are only supposed to be sent by the Ma=
ster.
>
> So to rephrase the proposal:
>
>     - If a Change event is received, then:
>
>     + Send an ADVERTISEMENT
>
>     + Reset the Adver_Timer to Advertisement_Interval
>
>     -endif // Change recv
>
> To cover the failover scenario (in the absence of preemption) Priority=20
> =3D 0
will now
> have to be allowed along with the previously discussed modifications=20
> to avoid
a
> storm of Priority =3D 0 Advertisements from two masters.
>
> Please Share your thoughts.
>
> Thanks
> -Anurag
>
> -----Original Message-----
> From: sreenatha [mailto:sreenatha.setty@ibtechnology.com]
> Sent: Saturday, March 02, 2013 3:17 AM
> To: Anurag Kothari (ankothar)
> Cc: vrrp@ietf.org
> Subject: Re: Proposal for Maintenance Event for VRRP [RFC-5798]
>
> Hi Anurag,
>      Thanks for clarification.
>
>       If i am wrong, user is allowed to configure Priority value as=20
> zero(i.e., Maintenance_Event), priority value will be changed. And=20
> handling of the Maintenance_Event is done only in Master state and=20
> ignored in Backup and Init state.
>
> Thanks,
> Sreenatha
>
> On 03/01/2013 08:31 PM, Anurag Kothari (ankothar) wrote:
> > Hi Sreenatha
> >
> > I don't think we need to define a "Maintenance_Event" when the=20
> > router is in
> either Init or Backup State. The intention of the "Maintenance_Event"
> is to trigger a failover from "Master" to a "Backup" router as soon as=20
> possible (especially when preemption is not configured).
> >
> > But if you are asking if priority =3D 0 should be allowed (either by=20
> > user
> configuration or dynamically) when the router is in "Init" or "Backup"
> state
then I
> think the answer should be yes, It should be treated just like any=20
> other
change in
> priority is treated when the router is in these states.
> >
> > Please let me know if I am missing something.
> >
> > Thanks
> > -Anurag
> >
> >
>
> Disclaimer :
> This email communication may contain privileged and confidential=20
> information and is intended for the use of the addressee only.If you=20
> are not an intended recipient you are requested not to reproduce, copy=20
> disseminate or in any
manner
> distribute this email communication as the same is strictly=20
> prohibited. If you
have
> received this email in error, please notify the sender immediately by=20
> return
e-
> mail and delete the communication sent in error. Email communications=20
> cannot be guaranteed to be secure & error free and IB Technology is=20
> not liable for
any
> errors in the email communication or for the proper, timely and=20
> complete transmission thereof.
>
> _______________________________________________
> vrrp mailing list
> vrrp@ietf.org
> https://www.ietf.org/mailman/listinfo/vrrp

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www.ietf.org/mailman/listinfo/vrrp
_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www.ietf.org/mailman/listinfo/vrrp

From ankothar@cisco.com  Sat Aug  3 12:16:39 2013
Return-Path: <ankothar@cisco.com>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD89011E80D5 for <vrrp@ietfa.amsl.com>; Sat,  3 Aug 2013 12:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 heski11Un1Iv for <vrrp@ietfa.amsl.com>; Sat,  3 Aug 2013 12:16:35 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id A22A221F9F9E for <vrrp@ietf.org>; Sat,  3 Aug 2013 12:16:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6636; q=dns/txt; s=iport; t=1375557394; x=1376766994; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=1sHSmO654xXt9ri+paSV6iKuXgMPK9PI6ZeuI0RsTK0=; b=ZtD9SL4MTKh2o9PpFqfD5rGyX8KR1/4F/8nnPTCzI7WuyQBYISkFJ/uH ECyvUA7MIM3TTzry9t06HY285LryUaZtWST9IItEqlDwQLhDGbMRp2i5f oucLyFoA0QOjRikLEbfBlvJDjMj4vo+LBJk2cedkTRu0UBEXwyc3CXlda U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAIZW/VGtJV2Y/2dsb2JhbABagwY1UL8UgR0WdIIkAQEBAQMBAQE3NAsMBgEIEQQBAQEKFAkuCxQJCQEEAQ0FCAESh3UMtkGOSAkQgQcPIg2DE3QDmQqQJYMXgXE5
X-IronPort-AV: E=Sophos;i="4.89,808,1367971200"; d="scan'208";a="243235322"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-4.cisco.com with ESMTP; 03 Aug 2013 19:16:34 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r73JGXN2017111 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 3 Aug 2013 19:16:33 GMT
Received: from xmb-rcd-x05.cisco.com ([169.254.15.236]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Sat, 3 Aug 2013 14:16:33 -0500
From: "Anurag Kothari (ankothar)" <ankothar@cisco.com>
To: "Celer, Alicja (Alicja)" <aceler@avaya.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "vrrp@ietf.org" <vrrp@ietf.org>
Thread-Topic: Graceful Failover for VRRP
Thread-Index: Ac6Qfd+Pkvaf0yCJT+yizdY87T+nqw==
Date: Sat, 3 Aug 2013 19:16:33 +0000
Message-ID: <A2BB90B33FFDF740876C5AAE307D83DB255B484E@xmb-rcd-x05.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-Auto-Response-Suppress: DR, OOF, AutoReply
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.218.55]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "fhrp-team\(mailer list\)" <fhrp-team@cisco.com>
Subject: Re: [VRRP] Graceful Failover for VRRP
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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 Aug 2013 19:16:39 -0000

Hello Alicja

I went through your draft:

http://tools.ietf.org/html/draft-celer-vrrp-ext-00

and my draft is totally and fundamentally different from yours.

Please let me know if it is some other draft of your that you are referring=
 to or if I am missing something here.

Thanks
-Anurag=20

-----Original Message-----
From: Anurag Kothari (ankothar)=20
Sent: Saturday, August 03, 2013 2:37 PM
To: 'Celer, Alicja (Alicja)'; adrian@olddog.co.uk; vrrp@ietf.org
Cc: fhrp-team(mailer list)
Subject: RE: Graceful Failover for VRRP

Hello Alicja

Sorry, I was not aware of your draft. I did a quick search and I suppose yo=
u are referring to:

http://tools.ietf.org/html/draft-celer-vrrp-ext-00

Please let me know if it is otherwise.

I would definitely go through it and get back to you; If it is the same ide=
a we can surely try to converge on a solution.

Thanks
-Anurag

-----Original Message-----
From: Celer, Alicja (Alicja) [mailto:aceler@avaya.com]
Sent: Saturday, August 03, 2013 2:21 PM
To: Anurag Kothari (ankothar); adrian@olddog.co.uk; vrrp@ietf.org
Cc: fhrp-team(mailer list)
Subject: RE: Graceful Failover for VRRP

Hi Anurag,

I've posted a draft addressing a similar issue and proposing a similar solu=
tion in 1999. Did you get a chance to review it?  If not, would you like a =
copy maybe we converge on a solution?=20

kind regar ds,
Alicja
________________________________________
From: vrrp-bounces@ietf.org [vrrp-bounces@ietf.org] on behalf of Anurag Kot=
hari (ankothar) [ankothar@cisco.com]
Sent: Friday, August 02, 2013 8:06 PM
To: adrian@olddog.co.uk; vrrp@ietf.org
Cc: fhrp-team(mailer list)
Subject: [VRRP] Graceful Failover for VRRP

Hi

I have submitted the following I-D on this idea:

TXT: http://www.ietf.org/internet-drafts/draft-kothari-vrrp-graceful-failov=
er-00.txt
HTML: http://tools.ietf.org/html/draft-kothari-vrrp-graceful-failover-00

Please review and provide feedback.

Thanks
-Anurag

-----Original Message-----
From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf Of Adr=
ian Farrel
Sent: Wednesday, May 22, 2013 12:12 PM
To: vrrp@ietf.org
Cc: fhrp-team(mailer list)
Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]

Hi,

If you are wondering how to progress this in the IETF, the answer is...

- write an I-D
- discuss it (here)
- polish it
- ask me to sponsor it for publication as an RFC.

Cheers,
Adrian

> -----Original Message-----
> From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf=20
> Of Anurag Kothari (ankothar)
> Sent: 04 March 2013 23:43
> To: sreenatha; vrrp@ietf.org
> Cc: fhrp-team(mailer list)
> Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]
>
> Hi Sreenatha
>
> If you mean "if I am not wrong" then yes what you have said below is corr=
ect.
>
> Also I believe the objective (particularly in case of time sensitive
application) is to
> avoid any unnecessary switch overs; as already suggested earlier let's=20
> call
this a
> "Change Event" instead of "Maintenance Event". The "Change Event"
> would be triggered by change in one of the following parameters of the VR=
RP Packet :
>
> 1) Priority (Section 5.2.4. of RFC-5798)
> 2) Max Adver Int (Section 5.2.7. of RFC-5798)
>
> And possibly:
>
> 3) IPvX Address(es) (Section 5.2.9.  of RFC-5798)
>
> The "Change Event" would only be handled in Master State and ignored=20
> in other state as the VRRP Packets are only supposed to be sent by the Ma=
ster.
>
> So to rephrase the proposal:
>
>     - If a Change event is received, then:
>
>     + Send an ADVERTISEMENT
>
>     + Reset the Adver_Timer to Advertisement_Interval
>
>     -endif // Change recv
>
> To cover the failover scenario (in the absence of preemption) Priority=20
> =3D 0
will now
> have to be allowed along with the previously discussed modifications=20
> to avoid
a
> storm of Priority =3D 0 Advertisements from two masters.
>
> Please Share your thoughts.
>
> Thanks
> -Anurag
>
> -----Original Message-----
> From: sreenatha [mailto:sreenatha.setty@ibtechnology.com]
> Sent: Saturday, March 02, 2013 3:17 AM
> To: Anurag Kothari (ankothar)
> Cc: vrrp@ietf.org
> Subject: Re: Proposal for Maintenance Event for VRRP [RFC-5798]
>
> Hi Anurag,
>      Thanks for clarification.
>
>       If i am wrong, user is allowed to configure Priority value as=20
> zero(i.e., Maintenance_Event), priority value will be changed. And=20
> handling of the Maintenance_Event is done only in Master state and=20
> ignored in Backup and Init state.
>
> Thanks,
> Sreenatha
>
> On 03/01/2013 08:31 PM, Anurag Kothari (ankothar) wrote:
> > Hi Sreenatha
> >
> > I don't think we need to define a "Maintenance_Event" when the=20
> > router is in
> either Init or Backup State. The intention of the "Maintenance_Event"
> is to trigger a failover from "Master" to a "Backup" router as soon as=20
> possible (especially when preemption is not configured).
> >
> > But if you are asking if priority =3D 0 should be allowed (either by=20
> > user
> configuration or dynamically) when the router is in "Init" or "Backup"
> state
then I
> think the answer should be yes, It should be treated just like any=20
> other
change in
> priority is treated when the router is in these states.
> >
> > Please let me know if I am missing something.
> >
> > Thanks
> > -Anurag
> >
> >
>
> Disclaimer :
> This email communication may contain privileged and confidential=20
> information and is intended for the use of the addressee only.If you=20
> are not an intended recipient you are requested not to reproduce, copy=20
> disseminate or in any
manner
> distribute this email communication as the same is strictly=20
> prohibited. If you
have
> received this email in error, please notify the sender immediately by=20
> return
e-
> mail and delete the communication sent in error. Email communications=20
> cannot be guaranteed to be secure & error free and IB Technology is=20
> not liable for
any
> errors in the email communication or for the proper, timely and=20
> complete transmission thereof.
>
> _______________________________________________
> vrrp mailing list
> vrrp@ietf.org
> https://www.ietf.org/mailman/listinfo/vrrp

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www.ietf.org/mailman/listinfo/vrrp
_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www.ietf.org/mailman/listinfo/vrrp

From sreenatha.setty@ibtechnology.com  Mon Aug  5 22:41:14 2013
Return-Path: <sreenatha.setty@ibtechnology.com>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AFC821F9D65 for <vrrp@ietfa.amsl.com>; Mon,  5 Aug 2013 22:41:14 -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 E+HWyOzYO4ow for <vrrp@ietfa.amsl.com>; Mon,  5 Aug 2013 22:41:10 -0700 (PDT)
Received: from ipinternal.indiabulls.com (ipinternal.indiabulls.com [202.54.119.192]) by ietfa.amsl.com (Postfix) with ESMTP id 43D6421F8EB2 for <vrrp@ietf.org>; Mon,  5 Aug 2013 22:41:08 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqIEAL2LAFKsEQH4/2dsb2JhbABbgzu4LYcSgTZ0giQBBggCHhIcGBgFBhAEAwECHykgFgkBBAEKCAkCBYd/DbVzkCSEBwOJKI9ikCWBNoFpNA
X-IronPort-AV: E=Sophos;i="4.89,824,1367951400"; d="scan'208";a="24397727"
Received: from IGSmtp.indiabulls.com (172.17.1.157) by MUM-IDC-SCAS.indiabulls.com (172.17.1.248) with Microsoft SMTP Server id 14.3.123.3; Tue, 6 Aug 2013 11:11:01 +0530
X-IronPort-AV: E=Sophos;i="4.89,824,1367951400"; d="scan'208";a="121646262"
Received: from 115.112.33.139.static-delhi.vsnl.net.in (HELO IBGGN86455L) ([115.112.33.139])  by ipgate.indiabulls.com with ESMTP; 06 Aug 2013 11:06:05 +0530
From: sreenatha setty <sreenatha.setty@ibtechnology.com>
To: <vrrp@ietf.org>, "Anurag Kothari (ankothar)" <ankothar@cisco.com>
Date: Tue, 6 Aug 2013 11:11:00 +0530
Message-ID: <001001ce9267$88419810$98c4c830$@ibtechnology.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6SZRersJTclBN/T4CjKlje6p1yDw==
Content-Language: en-in
Content-Transfer-Encoding: 7bit
Subject: [VRRP] . Re: Graceful Failover for VRRP
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 06 Aug 2013 05:41:14 -0000

Hi Anurag,
     I went through the draft. I have few queries. 
    The new "Change Event" you are trying to define is not actually new. In
earlier implementation also, if there is a change in Priority or
Advertisement Interval or VRIP address configurations, first VRRP will go to
Init state, then wait for some time (probably for Master down timer interval
if it's not the address owner) then becomes master if no eligible master is
available in the network.  I think only for Priority 0 configuration we need
to define new event. (I guess this you discussed over this mailing list
earlier.)
     And one more thing, I guess draft need to contain one more section
regarding the importance of the priority 0 configuration, before it talks
about the updates to RFC. Draft mentioned about this only in abstract. But
not really explaining in detail why we need to allow this configuration
(Priority 0).  Can you please elaborate it further?

Thanks,
Sreenatha



Message: 1
Date: Sat, 3 Aug 2013 00:06:13 +0000
From: "Anurag Kothari (ankothar)" <ankothar@cisco.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "vrrp@ietf.org"
	<vrrp@ietf.org>
Cc: "fhrp-team\(mailer list\)" <fhrp-team@cisco.com>
Subject: [VRRP] Graceful Failover for VRRP
Message-ID:
	<A2BB90B33FFDF740876C5AAE307D83DB255B389F@xmb-rcd-x05.cisco.com>
Content-Type: text/plain; charset="us-ascii"

Hi

I have submitted the following I-D on this idea:

TXT:
http://www.ietf.org/internet-drafts/draft-kothari-vrrp-graceful-failover-00.
txt
HTML: http://tools.ietf.org/html/draft-kothari-vrrp-graceful-failover-00

Please review and provide feedback.

Thanks
-Anurag


Disclaimer : 
This email communication may contain privileged and confidential information and is intended for the use of the addressee only.If you are not an intended recipient you are requested not to reproduce, copy disseminate or in any manner distribute this email communication as the same is strictly prohibited. If you have received this email in error, please notify the sender immediately by return e-mail and delete the communication sent in error. Email communications cannot be guaranteed to be secure & error free and IB Technology is not liable for any errors in the email communication or for the proper, timely and complete transmission thereof.


From ankothar@cisco.com  Tue Aug  6 07:17:54 2013
Return-Path: <ankothar@cisco.com>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBF9C21F9FE5 for <vrrp@ietfa.amsl.com>; Tue,  6 Aug 2013 07:17:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 JvfP-r5pWSSb for <vrrp@ietfa.amsl.com>; Tue,  6 Aug 2013 07:17:48 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 7B19A21F9FC9 for <vrrp@ietf.org>; Tue,  6 Aug 2013 07:17:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3754; q=dns/txt; s=iport; t=1375798668; x=1377008268; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=cReTtIob1Z1lf+BWdutd0zgyYafZj4u5NIoO4meSMpI=; b=FtZFqVk8UHO7zd91OfQ6G6EIlqzZJhby3vnvjdPwxBrgqLdBofcGKbJF c4Lalllh4zgv8dKxRLIKe+NC2iBBXO/D5OHd1Ivz+5mtWDSMywaz+INL8 T8VxqdbYUWPBHQYQIyWwmnhuApON8sAg90BB0XQ5P4dXeLt/xst/6dxLx 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag8FAK4EAVKtJV2c/2dsb2JhbABbgwY1UL59gR0WdIIkAQEBBDo0FwQCAQgRAwEBAQsUCQcyFAkIAQEEARIIAYgHDLZVjlQQgQUGCSkCBIMUdAOUCoUBkCSDF4FxOQ
X-IronPort-AV: E=Sophos;i="4.89,827,1367971200"; d="scan'208";a="244080553"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-5.cisco.com with ESMTP; 06 Aug 2013 14:17:43 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r76EHhe7022579 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 6 Aug 2013 14:17:43 GMT
Received: from xmb-rcd-x05.cisco.com ([169.254.15.236]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Tue, 6 Aug 2013 09:17:43 -0500
From: "Anurag Kothari (ankothar)" <ankothar@cisco.com>
To: sreenatha setty <sreenatha.setty@ibtechnology.com>, "vrrp@ietf.org" <vrrp@ietf.org>
Thread-Topic: . Re: Graceful Failover for VRRP 
Thread-Index: Ac6SZRersJTclBN/T4CjKlje6p1yDwAQz/fw
Date: Tue, 6 Aug 2013 14:17:42 +0000
Message-ID: <A2BB90B33FFDF740876C5AAE307D83DB255C2E9A@xmb-rcd-x05.cisco.com>
References: <001001ce9267$88419810$98c4c830$@ibtechnology.com>
In-Reply-To: <001001ce9267$88419810$98c4c830$@ibtechnology.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.248.109]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [VRRP] . Re: Graceful Failover for VRRP
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Virtual Router Redundancy Protocol  <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 06 Aug 2013 14:17:54 -0000

Hello Sreenatha

The earlier specification of VRRP do not talk about a change event but I do=
 agree that most implementations would have to have it in some form or the =
other in order to send the VRRP Packets with correct values after any chang=
es.

I do not think the Master router has to go into Init state even in older (i=
.e. current) implementations whenever any of the parameters mentioned in th=
e draft change, just that instead of sending the updated VRRP Packet immedi=
ately on change it would send it whenever the Adver_Timer fires.

I think it is better to track all changes to priority by the change event i=
nstead of just priority being changed to 0 for this will trigger failover i=
mmediately for the following Case:

* Preemption is enabled.
* Priority is not reduced all the way to zero on uplink failure.
 * Uplink goes down

Regarding your second point: Next version of the draft can surely have more=
 information regarding why we need priority zero and cover some use cases.

Thanks a lot for taking time to review this and providing your feedback.

Regards
-Anurag=20

-----Original Message-----
From: sreenatha setty [mailto:sreenatha.setty@ibtechnology.com]=20
Sent: Tuesday, August 06, 2013 1:41 AM
To: vrrp@ietf.org; Anurag Kothari (ankothar)
Subject: . Re: Graceful Failover for VRRP=20

Hi Anurag,
     I went through the draft. I have few queries.=20
    The new "Change Event" you are trying to define is not actually new. In=
 earlier implementation also, if there is a change in Priority or Advertise=
ment Interval or VRIP address configurations, first VRRP will go to Init st=
ate, then wait for some time (probably for Master down timer interval if it=
's not the address owner) then becomes master if no eligible master is avai=
lable in the network.  I think only for Priority 0 configuration we need to=
 define new event. (I guess this you discussed over this mailing list
earlier.)
     And one more thing, I guess draft need to contain one more section reg=
arding the importance of the priority 0 configuration, before it talks abou=
t the updates to RFC. Draft mentioned about this only in abstract. But not =
really explaining in detail why we need to allow this configuration (Priori=
ty 0).  Can you please elaborate it further?

Thanks,
Sreenatha



Message: 1
Date: Sat, 3 Aug 2013 00:06:13 +0000
From: "Anurag Kothari (ankothar)" <ankothar@cisco.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "vrrp@ietf.org"
	<vrrp@ietf.org>
Cc: "fhrp-team\(mailer list\)" <fhrp-team@cisco.com>
Subject: [VRRP] Graceful Failover for VRRP
Message-ID:
	<A2BB90B33FFDF740876C5AAE307D83DB255B389F@xmb-rcd-x05.cisco.com>
Content-Type: text/plain; charset=3D"us-ascii"

Hi

I have submitted the following I-D on this idea:

TXT:
http://www.ietf.org/internet-drafts/draft-kothari-vrrp-graceful-failover-00=
.
txt
HTML: http://tools.ietf.org/html/draft-kothari-vrrp-graceful-failover-00

Please review and provide feedback.

Thanks
-Anurag


Disclaimer :=20
This email communication may contain privileged and confidential informatio=
n and is intended for the use of the addressee only.If you are not an inten=
ded recipient you are requested not to reproduce, copy disseminate or in an=
y manner distribute this email communication as the same is strictly prohib=
ited. If you have received this email in error, please notify the sender im=
mediately by return e-mail and delete the communication sent in error. Emai=
l communications cannot be guaranteed to be secure & error free and IB Tech=
nology is not liable for any errors in the email communication or for the p=
roper, timely and complete transmission thereof.

