[VRRP] draft-zhou-pim-vrrp-01

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 22 May 2013 16:10 UTC

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
> 
> Folks,
> 
> 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.
> 
> If the broader WG participants have an opinion on this please speak up.
> 
> thanks,
> mike
> 
> 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
> >
> >> -----邮件原件-----
> >> 发件人: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] 代表 Mike
> >> McBride
> >> 发送时间: 2013年5月10日 3:48
> >> 收件人: pim@ietf.org
> >> 主题: [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