Re: draft-nitish-vrrp-bfd

Colin Docherty <colin@doch.org.uk> Thu, 31 August 2017 13:10 UTC

Return-Path: <colin.doch.org.uk@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 866CF132D91; Thu, 31 Aug 2017 06:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.997
X-Spam-Level:
X-Spam-Status: No, score=-3.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Y74f3otk3uiU; Thu, 31 Aug 2017 06:10:24 -0700 (PDT)
Received: from mail-oi0-f48.google.com (mail-oi0-f48.google.com [209.85.218.48]) (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 547E5132DFC; Thu, 31 Aug 2017 06:10:14 -0700 (PDT)
Received: by mail-oi0-f48.google.com with SMTP id w10so5001477oie.1; Thu, 31 Aug 2017 06:10:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7OZy0JZNkicx+ZsjpVQYEa9hDqHkpa7C0BQGoUG5XYI=; b=C+mI2wOo7D8lLG7kLn13k4uDdOwcyFp216i+hs5eA055dp+6siVNXHdqHpKg18HAGh SBcbfnGKZkErzBKGXr6JA/F97MmvXm0+YOCsbVkvb2OPZTiznF7fcJmEkzmhg5xACeIe bcBBflcAHpDboeslazJ/5habziDJywItLDAJ/LpUpgP285y7wYwO8ujrU5jEgwfVZG8Q qMLWNnvFgNXz2WNxcWgFcKODIANTGtXaRNSzPQNbkpKpmMpCfGd8Q8x4J1kD+oOCpkfz ZjSvkf8v8c9AJqrhOHQwUfMkVg6CUVchOGz8x8ii4j8l8dBJk1ju8hHq6ufmn2l3Rkdb Fa9Q==
X-Gm-Message-State: AHYfb5jV5SLoThDvG7dPPLo1PpPmBJUXnEJ8+/HmlhyJD1WrrvOF3Cae f2dADH58raykx7oinPgjZW//vD9skQ==
X-Google-Smtp-Source: ADKCNb5V05fEDkcBzHPemV6VjqAba8MNKCra/yUWhairGQHafn+iM7IlHfKBiHpBwLXoOeQTtAoY9V1J51IyiFFe2Vg=
X-Received: by 10.202.196.135 with SMTP id u129mr5688355oif.241.1504185013315; Thu, 31 Aug 2017 06:10:13 -0700 (PDT)
MIME-Version: 1.0
References: <CA+RyBmWyxFp447nGSsZvgnKp61LrSxwSoYeJft=Z_dZcSHeUVA@mail.gmail.com> <EE790B27-2DC3-4BEE-9D5A-6B75178C1604@cisco.com> <D5CD54E2.C53E2%acee@cisco.com>
In-Reply-To: <D5CD54E2.C53E2%acee@cisco.com>
From: Colin Docherty <colin@doch.org.uk>
Date: Thu, 31 Aug 2017 13:10:02 +0000
Message-ID: <CACei1EGs-w1LnpR3tpfhcp9ut2Wt7jo-gDFA8VOnzczyLYe27w@mail.gmail.com>
Subject: Re: draft-nitish-vrrp-bfd
To: "Acee Lindem (acee)" <acee@cisco.com>, "Nitish Gupta (nitisgup)" <nitisgup@cisco.com>, "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>, "Aditya Dogra (addogra)" <addogra@cisco.com>
Content-Type: multipart/related; boundary="001a113e2bb865658405580c5d13"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/ZPsBiI5ObAp1yH3LBbaxtny-R0Q>
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 13:10:28 -0000

Totally agree.

Colin.

On Thu, 31 Aug 2017 at 10:56 Acee Lindem (acee) <acee@cisco.com>; wrote:

> Hi Nitish,
>
> Irrespective of any IPR discussions, BFD is inherently a P2P protocol and,
> consequently, I would vote for P2P peer table.
>
> Thanks,
> Acee
>
> From: rtgwg <rtgwg-bounces@ietf.org>; on behalf of "Nitish Gupta
> (nitisgup)" <nitisgup@cisco.com>;
> Date: Thursday, August 31, 2017 at 1:51 AM
> To: "thibault.tabani@altran.com"; <thibault.tabani@altran.com>;, "
> rtg-bfd@ietf.org"; <rtg-bfd@ietf.org>;, Routing WG <rtgwg@ietf.org>;
> Cc: "colin@doch.org.uk"; <colin@doch.org.uk>;, "
> draft-nitish-vrrp-bfd@ietf.org"; <draft-nitish-vrrp-bfd@ietf.org>;, "Aditya
> Dogra (addogra)" <addogra@cisco.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>; 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: id: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: escription : Description : cid:image002.png@01CD89E1.42D19210]
> <http://facebook.com/AltranFrance>[image: escription : Description :
> cid:image003.png@01CD89E1.42D19210] <http://twitter.com/AltranFrance>[image:
> escription : Description : LinkedIn_signatureMail]
> <http://linkedin.com/company/altran-france>[image: escription :
> Description : pictog_viadeo] <http://www.viadeo.com/fr/company/altran>
>
>
>
>
>
>