Re: draft-nitish-vrrp-bfd

Greg Mirsky <gregimirsky@gmail.com> Tue, 29 August 2017 18:01 UTC

Return-Path: <gregimirsky@gmail.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 089291329BD; Tue, 29 Aug 2017 11:01:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 LQhY0rPBgCoJ; Tue, 29 Aug 2017 11:01:08 -0700 (PDT)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B98C1321AF; Tue, 29 Aug 2017 11:01:08 -0700 (PDT)
Received: by mail-lf0-x22b.google.com with SMTP id d17so16273757lfe.1; Tue, 29 Aug 2017 11:01:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=+otYG/I+7snEjZtY0FwNP3HAWWRSygtdbHM97CuYR0o=; b=FgjSogclV/pFNXilh1XpTpVEaOWipB7r+kfI1Xg3puSkqf1+PgcYCw+9SaHeAvpxeY cmP/7ZzfFK649QT0dmwFHYHN1izoAnC2fh2uzIfmJOvW3O9aVz8R9lvePus/s1N2ydS4 ClPA8fmO5tvaQAXPYOYAmJO/6bXQ7fLlWYv+i3XmW/0tCHHME6s3Usw4Wn9ybZC+pgeR a7r9itp3QyvUnWfiAV6KfRVyFrQQyB6kE3w2GJGYVSoBFxWSEJ6ofYX4AhCJuOcxbbNv TzF5oBbXBru9dPO/AfEdeupRhL89xFVivvMSgYjKabYiPsSbXAHoc5+p7gd0IimieJga a3sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=+otYG/I+7snEjZtY0FwNP3HAWWRSygtdbHM97CuYR0o=; b=qz6gvvmOw+WL/QnDmyhNtDX4biN0nJEVBUHHDv0k3NJlt0oPrYiyIK4gWpYzkm6h+0 RuWCy4FWVwinf8xY7tHpsXsGdS5y/7M2RjFyc4Yqn8zXXq1DehyrU7fOPVgztXzHu+OR Ji5F0zcIDRwDy3eb7LFzHv5Ygr64P4L5d/rWk0ezG11DTuhB0Tvgn5nFDqDdiWTEc1oF irMlBMNyKbPOamxekzw34bspA6oxMIiIhhtliSHEtqMi1r7hg1SPsNYf5yEh+EKRdT9i cs0IWhgbYF94BsGoECfaW9u5JwV7OUDK+wCjsq3q/JwNvgxVPO+1k4fW7Lb8cOyMzp5r Lpag==
X-Gm-Message-State: AHYfb5iyVHU6BBVcacWaSh4NZ0drc1nTfwWdXUb5iyEkLSOSq9Hn+PT1 9AUUzjFUaodvAFpHAfhVRuU6Jiwbzg==
X-Received: by 10.25.41.21 with SMTP id p21mr327408lfp.37.1504029666006; Tue, 29 Aug 2017 11:01:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.88.81 with HTTP; Tue, 29 Aug 2017 11:01:04 -0700 (PDT)
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 29 Aug 2017 11:01:04 -0700
Message-ID: <CA+RyBmWyxFp447nGSsZvgnKp61LrSxwSoYeJft=Z_dZcSHeUVA@mail.gmail.com>
Subject: Re: draft-nitish-vrrp-bfd
To: TABANI Thibault <thibault.tabani@altran.com>
Cc: "draft-nitish-vrrp-bfd@ietf.org" <draft-nitish-vrrp-bfd@ietf.org>, "nitisgup@cisco.com" <nitisgup@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Content-Type: multipart/related; boundary="001a114104d0fa0e5e0557e8312d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/kUGZ8rzKPqvkxrx8zWI6-y8E3C4>
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: Tue, 29 Aug 2017 18:01:11 -0000

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
> 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
>
>
> *[image: cid:image001.png@01CF8AFD.950B79F0]*
>
>
>
> 1, Impasse Charles Trenet
>
> 44800 Saint-Herblain
> France
>
> Tel. : +33 2 40 67 62 62 <+33%202%2040%2067%2062%2062>
> Mob. : +33 6 79 06 33 63 <+33%206%2079%2006%2033%2063>
> *thibault.tabani@altran.com <thibault.tabani@altran.com>*
> *www.altran.fr <http://www.altran.fr/>*
>
>
>
> [image: Description : Description : cid:image002.png@01CD89E1.42D19210]
> <http://facebook.com/AltranFrance>[image: Description : Description :
> cid:image003.png@01CD89E1.42D19210] <http://twitter.com/AltranFrance>[image:
> Description : Description : LinkedIn_signatureMail]
> <http://linkedin.com/company/altran-france>[image: Description :
> Description : pictog_viadeo] <http://www.viadeo.com/fr/company/altran>
>
>
>