Re: draft-nitish-vrrp-bfd

"Nitish Gupta (nitisgup)" <nitisgup@cisco.com> Thu, 31 August 2017 06:39 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 F25791321A2; Wed, 30 Aug 2017 23:39:30 -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 GxgjBfNL0Kid; Wed, 30 Aug 2017 23:39:28 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC908124207; Wed, 30 Aug 2017 23:39:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=56075; q=dns/txt; s=iport; t=1504161567; x=1505371167; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=XmXC+r4WG6/SMe8ONnHzmGlznSUpc9iLs1cyq6ousuc=; b=SpQb1AhIuHPEYziz+O094DxIxDGzNPIfxAhpIkUDZ5vZaI4ER9MRrSE3 g0by7npBN01+49rM47VauY2vXGRaNk/YW9dueAtRJZgaNIcEQpAD72ThB amTB5onArHgOcJIgLTkabkjnMlyRw8hE30LffJGvS7pxtqvpg6Fatcy2m g=;
X-Files: image001.png, image002.png, image003.png, image004.png, image005.jpg : 6452, 971, 951, 1273, 10080
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ANAwDZrqdZ/49dJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm8+LWSBFQeDcJo+gU8id4RPgnOPIQNcBwEkhRsCGoQQQxQBAgE?= =?us-ascii?q?BAQEBAQFrKIUYAQEBAQMFHgIIARswEAIBCBEDAQIGAQEBChUDAgICBRAKBQwUC?= =?us-ascii?q?QgCBAENBAEODYl+AxUQrl2CJyeHEA2DfwEBAQEBAQEBAQEBAQEBAQEBAQEBAQ4?= =?us-ascii?q?PgyqCAoFOgWMrC4I9NYJGETMBgSZbCRYIglUwgjEFiB2BbZMuA4J1PAKGWAEGe?= =?us-ascii?q?od+hHaCElqBFIN5EokXgUmMTgILKYk5BwE2IU4/dxVbAYUFHIFndgGJJIEPAQE?= =?us-ascii?q?B?=
X-IronPort-AV: E=Sophos;i="5.41,451,1498521600"; d="png'150?jpg'150,145?scan'150,145,208,217,150,145";a="474386479"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Aug 2017 06:39:15 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v7V6dE8u028841 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 31 Aug 2017 06:39:14 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 02:39:13 -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 02:39:13 -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+ukaX9C4xggrCwqKdxioAgAANY4A=
Date: Thu, 31 Aug 2017 06:39:13 +0000
Message-ID: <FCB81B10-8845-4ED3-BBDD-19EEADBF39A0@cisco.com>
References: <CA+RyBmWyxFp447nGSsZvgnKp61LrSxwSoYeJft=Z_dZcSHeUVA@mail.gmail.com> <EE790B27-2DC3-4BEE-9D5A-6B75178C1604@cisco.com>
In-Reply-To: <EE790B27-2DC3-4BEE-9D5A-6B75178C1604@cisco.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_FCB81B1088454ED3BBDD19EEADBF39A0ciscocom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/Rn1TBT5aEgN4MCakIpKOfsnUyXo>
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 06:39:31 -0000

Hi All,

We have submitted the draft for VRRP with p2p BFD.
Please review and let us know your comments and suggestions.
https://www.ietf.org/internet-drafts/draft-nitish-vrrp-bfd-p2p-00.txt

Thanks,
Nitish
From: "Nitish Gupta (nitisgup)" <nitisgup@cisco.com>
Date: Wednesday, August 30, 2017 at 10:51 PM
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

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

[cid:image001.png@01D321E9.31185090]

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/>

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