Re: BFD chair response to presentation on draft-mirmin-bfd-extended

Jeffrey Haas <jhaas@pfrc.org> Wed, 27 November 2019 20:18 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 6891B120A7C; Wed, 27 Nov 2019 12:18:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 n5i49evbfEcF; Wed, 27 Nov 2019 12:17:59 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id DF6DE120A79; Wed, 27 Nov 2019 12:17:59 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id AE4871E2F8; Wed, 27 Nov 2019 15:22:06 -0500 (EST)
Date: Wed, 27 Nov 2019 15:22:06 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: Dave Katz <dkatz@juniper.net>
Cc: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: Re: BFD chair response to presentation on draft-mirmin-bfd-extended
Message-ID: <20191127202206.GA18175@pfrc.org>
References: <20191122025255.GW21134@pfrc.org> <MWHPR11MB1341FAFAD5169AC6E8843D20C1490@MWHPR11MB1341.namprd11.prod.outlook.com> <5013C7DE-81C0-44B6-B15B-8701527358E9@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <5013C7DE-81C0-44B6-B15B-8701527358E9@juniper.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/YP0xEeVsjxIYJUDOBNseSro3OPw>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 27 Nov 2019 20:18:01 -0000

Dave,

On Fri, Nov 22, 2019 at 09:35:12PM +0000, Dave Katz wrote:
> If BFD’s transport semantics are that interesting, someone could take a
> week and whip up a transport that looks rather like BFD but is properly
> suited for the purpose.  That would make all of these issues go away, and
> would provide a common mechanism that could be used more broadly, and
> someone would have an RFC to be proud of.

That's effectively what the discussion needs to be.  And I agree, there's
plumbing like demand and echo that can be gotten rid of.

The adaptive timers are part of the charm that people seem to like, so I
suspect that'd still be a thing people want.  Just not necessarily 3ms
granularity. :-)

> I guess the irony of all of this is that when the BFD WG was formed it was
> expected to be the shortest-lived WG in history.  Now I suspect it’s going
> for a record in the other direction.  ;-)

I still resent Alex Z. and co. for leading me into that trap.

-- Jeff