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

Xuxiaohu <xuxiaohu@huawei.com> Fri, 10 May 2013 02:32 UTC

Return-Path: <xuxiaohu@huawei.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 E5C9E21F8FF0 for <pim@ietfa.amsl.com>; Thu, 9 May 2013 19:32:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.226
X-Spam-Level:
X-Spam-Status: No, score=-2.226 tagged_above=-999 required=5 tests=[AWL=-0.169, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
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 UGFxvZWeRYeP for <pim@ietfa.amsl.com>; Thu, 9 May 2013 19:32:43 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4885821F8C7D for <pim@ietf.org>; Thu, 9 May 2013 19:32:43 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ASQ82497; Fri, 10 May 2013 02:32:39 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 10 May 2013 03:32:28 +0100
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 10 May 2013 03:32:38 +0100
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.243]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.01.0323.007; Fri, 10 May 2013 10:32:32 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] call for adoption: draft-zhou-pim-vrrp-01
Thread-Index: AQHOTO46Kv7cKrIMmE+yfb3Ht5i9dJj9sx9A
Date: Fri, 10 May 2013 02:32:32 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE07F669D4@NKGEML512-MBS.china.huawei.com>
References: <CAL3FGfwaXhsfRoJXo17LipzGNvUH0jL2sQdcrmMqzBa0ZB16og@mail.gmail.com>
In-Reply-To: <CAL3FGfwaXhsfRoJXo17LipzGNvUH0jL2sQdcrmMqzBa0ZB16og@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.130]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
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, 10 May 2013 02:32:44 -0000

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