
From adrian@olddog.co.uk  Wed May 22 09:10:53 2013
Return-Path: <adrian@olddog.co.uk>
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 05B4121F9671 for <vrrp@ietfa.amsl.com>; Wed, 22 May 2013 09:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.204
X-Spam-Level: 
X-Spam-Status: No, score=-1.204 tagged_above=-999 required=5 tests=[AWL=-1.394, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45]
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 mlJ5f0c2wDV8 for <vrrp@ietfa.amsl.com>; Wed, 22 May 2013 09:10:48 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 09FFF21F966B for <vrrp@ietf.org>; Wed, 22 May 2013 09:10:47 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4MGAkOa021338 for <vrrp@ietf.org>; Wed, 22 May 2013 17:10:46 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4MGAjFs021321 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <vrrp@ietf.org>; Wed, 22 May 2013 17:10:46 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <vrrp@ietf.org>
Date: Wed, 22 May 2013 17:10:45 +0100
Message-ID: <026101ce5706$eaec2d50$c0c487f0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5XBnL4IsM5Ro9jTMKWs9HswEhVcg==
Content-Language: en-gb
Subject: [VRRP] draft-zhou-pim-vrrp-01
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Wed, 22 May 2013 16:10:53 -0000

Hello VRRP list,

Please be aware of this work in the PIM working group and comment there =
if you
have an opinion.

Thanks,
Adrian

> -----Original Message-----
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of =
Mike
> McBride
> Sent: 22 May 2013 07:17
> To: Xuxiaohu; sganesan@extremenetworks.com; rajiva@cisco.com;
> pjhingra@cisco.com; weizho2@cisco.com
> Cc: Mike McBride; pim@ietf.org
> Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
>=20
> Folks,
>=20
> We have this new draft-zhou-pim-vrrp-01 which we are about to adopt
> into the pim wg. It has been brought to the WGs attention that there
> is a older draft (draft-xu-pim-drpriority-auto-adjustment-03) which
> may have some overlap with the new one. That older draft does contain
> information about VRRP aware PIM which is attributed to Stig in the
> acknowledgements. If the five of you authors feel that there is some
> validity that the older draft contains some information being used in
> the new draft, you may want to acknowledge that in the references or
> acknowledgements. It appears the drafts are dissimilar enough to not
> be merged but I may be wrong. Please share your opinions on this so we
> can establish consensus within the group and move the document along.
>=20
> If the broader WG participants have an opinion on this please speak =
up.
>=20
> thanks,
> mike
>=20
> On Thu, May 9, 2013 at 7:32 PM, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> > Hi all,
> >
> > This draft reminds me that there has been a draft
> =
(http://tools.ietf.org/html/draft-xu-pim-drpriority-auto-adjustment-03) =
three
> years before which uses almost the same technology to save almost the =
same
> problem.
> >
> > The following is quoted from the above draft:
> >
> >    "In fact, if VRRP is run on the PIM routers and the VRRP has =
enabled
> >    the upstream link tracking mechanism, the PIM DR failover =
mechanism
> >    could be coupled with the VRRP so as to reuse the upstream link
> >    tracking mechanism of VRRP. One option is to synchronize the PIM =
DR
> >    priority value to the VRRP priority value always. In this way, =
the
> >    PIM DR and the VRRP master will always run on an identical router =
if
> >    the VRRP Preempt_Mode is set to True. Another option is to make =
the
> >    PIM DR and the VRRP master run on an identical router anyway =
(i.e.,
> >    regardless whether or not the VRRP Preempt_Mode is True). To =
achieve
> >    this goal, the PIM DR priority of the VRRP master router SHOULD
> >    always be set to a higher fixed value than that of the VRRP slave
> >    router automatically."
> >
> > Best regards,
> > Xiaohu
> >
> >> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> >> =B7=A2=BC=FE=C8=CB: pim-bounces@ietf.org =
[mailto:pim-bounces@ietf.org] =B4=FA=B1=ED Mike
> >> McBride
> >> =B7=A2=CB=CD=CA=B1=BC=E4: 2013=C4=EA5=D4=C210=C8=D5 3:48
> >> =CA=D5=BC=FE=C8=CB: pim@ietf.org
> >> =D6=F7=CC=E2: [pim] call for adoption: draft-zhou-pim-vrrp-01
> >>
> >> draft-zhou-pim-vrrp-01 was presented in our most recent pim meeting =
in
> >> Orlando. 4 people were in favor of adopting the draft. Zero =
against.
> >> Please read the draft (its short) and provide an opinion either way =
by
> >> the end of next Friday the 17th.
> >>
> >> http://www.ietf.org/id/draft-zhou-pim-vrrp-01.txt
> >>
> >> thanks,
> >> mike
> >> _______________________________________________
> >> pim mailing list
> >> pim@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pim
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


From adrian@olddog.co.uk  Wed May 22 09:12:15 2013
Return-Path: <adrian@olddog.co.uk>
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 BFDF121F96C9 for <vrrp@ietfa.amsl.com>; Wed, 22 May 2013 09:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.472
X-Spam-Level: 
X-Spam-Status: No, score=-2.472 tagged_above=-999 required=5 tests=[AWL=0.127,  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 FqCBU8yDD1PG for <vrrp@ietfa.amsl.com>; Wed, 22 May 2013 09:12:10 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 760A821F96E7 for <vrrp@ietf.org>; Wed, 22 May 2013 09:12:09 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4MGC6qs014397;  Wed, 22 May 2013 17:12:06 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4MGC5Rr014376 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 22 May 2013 17:12:06 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <vrrp@ietf.org>
References: <512F8815.5010204@ibtechnology.com>	<A2BB90B33FFDF740876C5AAE307D83DB1C295D1C@xmb-rcd-x05.cisco.com>	<5130366D.6070302@ibtechnology.com>	<A2BB90B33FFDF740876C5AAE307D83DB1C2963EE@xmb-rcd-x05.cisco.com>	<5131B583.3000500@ibtechnology.com> <A2BB90B33FFDF740876C5AAE307D83DB1C297B31@xmb-rcd-x05.cisco.com>
In-Reply-To: <A2BB90B33FFDF740876C5AAE307D83DB1C297B31@xmb-rcd-x05.cisco.com>
Date: Wed, 22 May 2013 17:12:05 +0100
Message-ID: <026201ce5707$1a816bc0$4f844340$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHn+BVuC0d9lEynakgH2ZCVLHLX3AMQu56kAZ1jxcQBlJ/KbAMWSf5xAikaf26YggxCYA==
Content-Language: en-gb
Cc: "'fhrp-team\(mailer list\)'" <fhrp-team@cisco.com>
Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Wed, 22 May 2013 16:12:15 -0000

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 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 correct.
> 
> 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 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 VRRP 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 in other
> state as the VRRP Packets are only supposed to be sent by the Master.
> 
> 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 = 0
will now
> have to be allowed along with the previously discussed modifications to avoid
a
> storm of Priority = 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 zero(i.e.,
> Maintenance_Event), priority value will be changed. And handling of the
> Maintenance_Event is done only in Master state and 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 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 possible
> (especially when preemption is not configured).
> >
> > But if you are asking if priority = 0 should be allowed (either by 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 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 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.
> 
> _______________________________________________
> vrrp mailing list
> vrrp@ietf.org
> https://www.ietf.org/mailman/listinfo/vrrp

