Re: [pim] call for adoption: draft-zhou-pim-vrrp-01

"Rajiv Asati (rajiva)" <rajiva@cisco.com> Wed, 22 May 2013 21:36 UTC

Return-Path: <rajiva@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2594711E8123 for <pim@ietfa.amsl.com>; Wed, 22 May 2013 14:36:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.328
X-Spam-Level:
X-Spam-Status: No, score=-8.328 tagged_above=-999 required=5 tests=[AWL=-2.271, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, 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 CGe3KhFoBhV3 for <pim@ietfa.amsl.com>; Wed, 22 May 2013 14:36:33 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id DE60411E811B for <pim@ietf.org>; Wed, 22 May 2013 14:36:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4804; q=dns/txt; s=iport; t=1369258593; x=1370468193; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=hVgIDs4Am+vtbCT5r0aL7pVqxXzG2Ovexe1xO9xPBRg=; b=V1gA80kvJaKVr0AxCYnt3C4IS1eUo1Ot6aBHjUZU27IWsPbzDi1uPnvP nYdw84FP7TxLjENu5tNilpVyMaabgKuB39PP6eWFRdOYe36NqiD2Rb9Lx yHqPvrHHr3FJGyn76cjZZHnnl8rur0tDacfLC/8cPIeYRSBMjrtp8WxtS Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8FADI5nVGtJV2d/2dsb2JhbABagwgwgzu+Ow16FnSCIwEBAQQBAQEaFzoLDAQCAQYCEQQBAQEEBh0FAgIfBgsUCQgCBAENBQgBh3IDDwyOBpseCIhfDYh0gSKLJIImFhsHBoI3NmEDlVKDD4p0hSODD4Im
X-IronPort-AV: E=Sophos;i="4.87,724,1363132800"; d="scan'208";a="213805441"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-2.cisco.com with ESMTP; 22 May 2013 21:36:28 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r4MLaSPC017606 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 22 May 2013 21:36:28 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.154]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Wed, 22 May 2013 16:36:27 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Mike McBride <mmcbride7@gmail.com>, Xuxiaohu <xuxiaohu@huawei.com>, "sganesan@extremenetworks.com" <sganesan@extremenetworks.com>, "Prashant Jhingran (pjhingra)" <pjhingra@cisco.com>, "Wei Zhou (weizho2)" <weizho2@cisco.com>
Thread-Topic: [pim] call for adoption: draft-zhou-pim-vrrp-01
Thread-Index: AQHOVrP+ivzvTZvrmky2qTiDZ//NRpkRujug
Date: Wed, 22 May 2013 21:36:27 +0000
Message-ID: <B14A62A57AB87D45BB6DD7D9D2B78F0B116B0DB0@xmb-rcd-x06.cisco.com>
References: <CAL3FGfwaXhsfRoJXo17LipzGNvUH0jL2sQdcrmMqzBa0ZB16og@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE07F669D4@NKGEML512-MBS.china.huawei.com> <CAL3FGfy2WdAmtnUO97nx0TYMeMqStkUmJfa42VDu=6MOykbzwQ@mail.gmail.com>
In-Reply-To: <CAL3FGfy2WdAmtnUO97nx0TYMeMqStkUmJfa42VDu=6MOykbzwQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.213.252]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2013 21:36:38 -0000

Hi Mike,

It seems that both drafts seem to solve nearly the same problem (multiple routers on the multi-access interface and existence of first-hop redundancy protocols e.g. VRRP). 

Cheers,
Rajiv


> -----Original Message-----
> From: Mike McBride [mailto:mmcbride7@gmail.com]
> Sent: Wednesday, May 22, 2013 2:17 AM
> To: Xuxiaohu; sganesan@extremenetworks.com; Rajiv Asati (rajiva);
> Prashant Jhingran (pjhingra); Wei Zhou (weizho2)
> Cc: Stig Venaas; 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