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

Mike McBride <mmcbride7@gmail.com> Fri, 31 May 2013 07:06 UTC

Return-Path: <mmcbride7@gmail.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 6249321F8624 for <pim@ietfa.amsl.com>; Fri, 31 May 2013 00:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.189
X-Spam-Level:
X-Spam-Status: No, score=0.189 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, NO_RELAYS=-0.001]
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 miTiU7sL5Wte for <pim@ietfa.amsl.com>; Fri, 31 May 2013 00:06:48 -0700 (PDT)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 3CEB421F9344 for <pim@ietf.org>; Fri, 31 May 2013 00:06:45 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id jt11so1716133pbb.38 for <pim@ietf.org>; Fri, 31 May 2013 00:06:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=e43j27rtpFjHlTFpZ4tVtcsbqpBI83dRcdjCn/5NED4=; b=Di8ahn7PxgK0mG9y+EpuOnCV9cOm8F1GcNH1IeW5W1ldCVvI8hWpIyoejBXphwCARE dxn+NAKKnsS7uG6cOUtKez02hJz5MuqtTxh9dXUka4DS1eSUfwscHdqyr7b013TJlJl9 nbi1tUgWLp2lHKer99epE/a2Hi1pVxccWokKKrmY3XSpfwEKq4AvZHcz1HUzu8dwmss+ UpugQ4LE/NAyJjNSCNczuUikoO5JjHgyIyysQ/5z1fVRPfBm5ywZSSFkEk5UlkrEgoLp DwUWES1AUL5ZQhJ7HgpUhLpv1gZmI1G/626vsxOsXXSDrvOjGCYoji/jbU5gyx/nGRYl an0A==
MIME-Version: 1.0
X-Received: by 10.66.122.97 with SMTP id lr1mr12023675pab.147.1369984004897; Fri, 31 May 2013 00:06:44 -0700 (PDT)
Received: by 10.68.59.232 with HTTP; Fri, 31 May 2013 00:06:44 -0700 (PDT)
In-Reply-To: <F567B77E0728694BB6716DB3C9000B6B12ABC487@xmb-rcd-x14.cisco.com>
References: <CAL3FGfwaXhsfRoJXo17LipzGNvUH0jL2sQdcrmMqzBa0ZB16og@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE07F669D4@NKGEML512-MBS.china.huawei.com> <CAL3FGfy2WdAmtnUO97nx0TYMeMqStkUmJfa42VDu=6MOykbzwQ@mail.gmail.com> <B14A62A57AB87D45BB6DD7D9D2B78F0B116B0DB0@xmb-rcd-x06.cisco.com> <F567B77E0728694BB6716DB3C9000B6B12ABC487@xmb-rcd-x14.cisco.com>
Date: Fri, 31 May 2013 00:06:44 -0700
Message-ID: <CAL3FGfyVgze+tVyErjcKaME6esNKRmEYqcobZGpHxBnsTewibg@mail.gmail.com>
From: Mike McBride <mmcbride7@gmail.com>
To: "Prashant Jhingran (pjhingra)" <pjhingra@cisco.com>
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: quoted-printable
Cc: "sganesan@extremenetworks.com" <sganesan@extremenetworks.com>, "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: Fri, 31 May 2013 07:06:53 -0000

Thank you for the responses.

Some feel the two drafts are completely unrelated while others feel
they are completely related. In either case, are you, who feel they
are related, saying you oppose the adoption of draft-zhou-pim-vrrp-01?
We can infer that is the case but I haven't heard explicitly stated
opposition to adoption. We now have several choices for
draft-zhou-pim-vrrp, let me try boiling it down to 3:

1. adopt draft-zhou-pim-vrrp-01 as is
2. adopt draft-zhou-pim-vrrp-01 only after
draft-xu-pim-drpriority-auto-adjustment is referenced.
3. merge the drafts

In either case the authors should revive the expired
draft-xu-pim-drpriority-auto-adjustment-03 for consideration within
the wg irregardless of vrrp-01 adoption outcome.

What say ye?

mike

On Thu, May 23, 2013 at 2:08 AM, Prashant Jhingran (pjhingra)
<pjhingra@cisco.com> wrote:
> Hi Mike,
>
> I agree with Rajiv, both drafts are trying to solve the same issue....that too in almost similar way.
>
> -
> Regards,
> Prashant Jhingran
> NOSTG TME - SP Wi-Fi
>
> http://wwwin.cisco.com/ios/tech/mobile/proxyipv6/
> http://wwwin.cisco.com/ios/tech/broadband
>
>
> -----Original Message-----
> From: Rajiv Asati (rajiva)
> Sent: Thursday, May 23, 2013 3:06 AM
> To: Mike McBride; Xuxiaohu; sganesan@extremenetworks.com; Prashant Jhingran (pjhingra); Wei Zhou (weizho2)
> Cc: Stig Venaas; pim@ietf.org
> Subject: RE: [pim] call for adoption: draft-zhou-pim-vrrp-01
>
> 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