Re: draft-nitish-vrrp-bfd

"Nitish Gupta (nitisgup)" <nitisgup@cisco.com> Thu, 31 August 2017 05:51 UTC

Return-Path: <nitisgup@cisco.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E6BB1321EC; Wed, 30 Aug 2017 22:51:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.518
X-Spam-Level:
X-Spam-Status: No, score=-14.518 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14K2CqaEbIQY; Wed, 30 Aug 2017 22:51:24 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79163132191; Wed, 30 Aug 2017 22:51:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=52679; q=dns/txt; s=iport; t=1504158683; x=1505368283; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=OPnOaPSLG1q+nchlf8NRd+mumOAmNjNygfnGq/0rRwA=; b=czF7J0VF/cKGYFE0hWD8k3pdEn5vuIJ+2ToLbiKka8GlTkTaCpf5m3O6 ypapgTCCYUcLLr16DEqB+PpiqmrqGxZ9ElQHTHZfjjENhUcL9f89MeXrb fjxNO2QQ5ZtJzKAwK/2vUPpmIoXPOv5LT7YNp8ntVabYp9ZYb22pYeNxz A=;
X-Files: image001.png, image002.png, image003.png, image004.png, image005.jpg : 6451, 970, 950, 1272, 10079
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B6AgBko6dZ/4wNJK1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm8+LWSBFQeDcJo+gXF3hE+Cc48hA1wHASSFGwIahA9DFAECAQE?= =?us-ascii?q?BAQEBAWsohRgBAQEBAwUeAggBGzAQAgEIEQMBAgYBAQEKFQMCAgIFEAoFDBQJC?= =?us-ascii?q?AIEAQ0EAQ4NiX4DFRCuEoInJ4cQDYN/AQEBAQEBAQEBAQEBAQEBAQEBAQEBDg+?= =?us-ascii?q?DKoICgU6BYyuCSDWCRhEzAYEmWwkWCIJVMIIxBYgdgW2TLgOCdTwChlgBBnqHf?= =?us-ascii?q?oR2DIIGWoEUg3kSiReBSYxOAgspiTkHATYhTj93FVsBhQUcgWd2iSWBDwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.41,451,1498521600"; d="png'150?jpg'150,145?scan'150,145,208,217,150,145";a="287403790"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 31 Aug 2017 05:51:19 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v7V5pII0027034 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 31 Aug 2017 05:51:19 GMT
Received: from xch-rtp-003.cisco.com (64.101.220.143) by XCH-RTP-020.cisco.com (64.101.220.160) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 31 Aug 2017 01:51:18 -0400
Received: from xch-rtp-003.cisco.com ([64.101.220.143]) by XCH-RTP-003.cisco.com ([64.101.220.143]) with mapi id 15.00.1263.000; Thu, 31 Aug 2017 01:51:17 -0400
From: "Nitish Gupta (nitisgup)" <nitisgup@cisco.com>
To: "thibault.tabani@altran.com" <thibault.tabani@altran.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
CC: "draft-nitish-vrrp-bfd@ietf.org" <draft-nitish-vrrp-bfd@ietf.org>, "gregimirsky@gmail.com" <gregimirsky@gmail.com>, "Aditya Dogra (addogra)" <addogra@cisco.com>, "colin@doch.org.uk" <colin@doch.org.uk>, "jefftant.ietf@gmail.com" <jefftant.ietf@gmail.com>
Subject: Re: draft-nitish-vrrp-bfd
Thread-Topic: draft-nitish-vrrp-bfd
Thread-Index: AQHTIPDPqLd77Ub+ukaX9C4xggrCwqKdxioA
Date: Thu, 31 Aug 2017 05:51:17 +0000
Message-ID: <EE790B27-2DC3-4BEE-9D5A-6B75178C1604@cisco.com>
References: <CA+RyBmWyxFp447nGSsZvgnKp61LrSxwSoYeJft=Z_dZcSHeUVA@mail.gmail.com>
In-Reply-To: <CA+RyBmWyxFp447nGSsZvgnKp61LrSxwSoYeJft=Z_dZcSHeUVA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1a.0.160910
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.109.105]
Content-Type: multipart/related; boundary="_008_EE790B272DC34BEE9D5A6B75178C1604ciscocom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/HIGt8u0e_UW3LWX8mc5szNX9XQA>
X-Mailman-Approved-At: Thu, 31 Aug 2017 07:48:08 -0700
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Aug 2017 05:51:26 -0000

Hi Thibault,

Thanks for the interest in the Draft, appreciate it. Please review the draft and let us know if you have any comments, suggestions.

Hi RTGWG/RTGBFD,

There were two solutions proposed in the draft.
One pertains to making a peer table in VRRP and uses p2p BFD.
The second solution pertains to p2mp BFD.

While we were working on the draft there was an IPR associated to the DRAFT and the WG felt that we need to wait until we can see the IPR and what its associated to.
We can see that the IPR is available for us to view and we can see that the IPR is associated to p2mp BFD.

https://www.google.com/patents/US20170005915

We are going to submit a draft with the p2p BFD so that we can continue working on the Draft.
There was lot of interest last time as well, just because of the IPR claim we had stopped the work.

Thanks,
Nitish

From: Greg Mirsky <gregimirsky@gmail.com>;
Date: Tuesday, August 29, 2017 at 11:01 AM
To: TABANI Thibault <thibault.tabani@altran.com>;
Cc: "draft-nitish-vrrp-bfd@ietf.org"; <draft-nitish-vrrp-bfd@ietf.org>;, "Nitish Gupta (nitisgup)" <nitisgup@cisco.com>;, "rtg-bfd@ietf.org"; <rtg-bfd@ietf.org>;, "rtgwg@ietf.org"; <rtgwg@ietf.org>;
Subject: Re: draft-nitish-vrrp-bfd
Resent-From: <alias-bounces@ietf.org>;
Resent-To: <nitisgup@cisco.com>;, <addogra@cisco.com>;, <colin@doch.org.uk>;, <gregimirsky@gmail.com>;, <jefftant.ietf@gmail.com>;
Resent-Date: Tuesday, August 29, 2017 at 11:01 AM

Hi Thibault,
thank you for your interest in the draft, much appreciated. Please don't be discouraged that it lapsed, we can fix it easily. I think that authors had similar to your idea when we've started thinking about BFD supporting VRRP. And like you we haven't found any reference in existing documents, hence this draft draft-nitish-vrrp-bfd. Would be much obliged if you review and share your comments, suggestion regarding solutions proposed in the draft.

Regards,
Greg

On Tue, Aug 29, 2017 at 9:20 AM, TABANI Thibault <thibault.tabani@altran.com<mailto:thibault.tabani@altran.com>> wrote:
Hello,

I am working at improving VRRP convergence time. (target a few 100’s of milliseconds)

It appears that VRRP supports BFD health monitoring which might be a better option than tuning VRRP aggressive timers.

Unfortunately I cannot find any active RFC where VRRP supports BFD. The only document I found is your draft document:

Fast failure detection in VRRP with BFD
draft-nitish-vrrp-bfd-04

Unfortunately date expires of this document.  As BFD support for VRRP is implemented on most routers, I suppose that an active RFC might exist on that specific BFD implementation within VRRP. (new backup advertisement messages….peer table….)
br


Thibault TABANI
architect Altran Connected Solutions
Altran France

[id:image001.png@01CF8AFD.950B79F0]

1, Impasse Charles Trenet
44800 Saint-Herblain
France
Tel. : +33 2 40 67 62 62<tel:+33%202%2040%2067%2062%2062>
Mob. : +33 6 79 06 33 63<tel:+33%206%2079%2006%2033%2063>
thibault.tabani@altran.com<mailto:thibault.tabani@altran.com>
www.altran.fr<http://www.altran.fr/>

[escription : Description : cid:image002.png@01CD89E1.42D19210]<http://facebook.com/AltranFrance>[escription : Description : cid:image003.png@01CD89E1.42D19210]<http://twitter.com/AltranFrance>[escription : Description : LinkedIn_signatureMail]<http://linkedin.com/company/altran-france>[escription : Description : pictog_viadeo]<http://www.viadeo.com/fr/company/altran>