Re: BFD WG adoption for draft-haas-bfd-large-packets

Jeffrey Haas <jhaas@pfrc.org> Fri, 26 October 2018 00:58 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 50078130E08 for <rtg-bfd@ietfa.amsl.com>; Thu, 25 Oct 2018 17:58:35 -0700 (PDT)
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 ADG7OjLFdufk for <rtg-bfd@ietfa.amsl.com>; Thu, 25 Oct 2018 17:58:33 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id CEAC11286E7 for <rtg-bfd@ietf.org>; Thu, 25 Oct 2018 17:58:33 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id CAB3B1E44B; Thu, 25 Oct 2018 20:57:55 -0400 (EDT)
Date: Thu, 25 Oct 2018 20:57:55 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
Cc: "Naiming Shen (naiming)" <naiming@cisco.com>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: Re: BFD WG adoption for draft-haas-bfd-large-packets
Message-ID: <20181026005755.GF12336@pfrc.org>
References: <E052CA19-228D-4271-BF9E-7499255E7C53@cisco.com> <7332e35048d34d44a65ea70df409699c@XCH-ALN-001.cisco.com> <90B9205E-CBD8-4779-96D1-2D15BD1F7E24@cisco.com> <e08744fc4b264fd1bf9844dd0f29557e@XCH-ALN-001.cisco.com> <59DD4DA1-6C83-4D3D-92E7-B4271EB259E8@cisco.com> <2dc00a0d58db41958ad61d73d08ead17@XCH-ALN-001.cisco.com> <20181025153804.GD12336@pfrc.org> <a367a9ceec9e4f96ac41223a4fde494f@XCH-ALN-001.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <a367a9ceec9e4f96ac41223a4fde494f@XCH-ALN-001.cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/Sa1l_ku_iHtmRAoHA7PtmoJMlbY>
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: Fri, 26 Oct 2018 00:58:35 -0000

On Thu, Oct 25, 2018 at 10:28:52PM +0000, Les Ginsberg (ginsberg) wrote:
> > https://tools.ietf.org/html/draft-ietf-bfd-stability-02
> 
> [Les:] I have read this draft - not sure how relevant it is.

Mostly, the idea being that it's possible to do probing in BFD without
necessarily having to commit your entire detection resources to it.

> Naiming had suggested that MTU sized packets need not be sent all the time but only occasionally - 
> and that a failure might not be used to take the BFD session down - 
> rather it would be seen as a "soft-failure" and reported separately from the BFD session state.
> My response was in that context - which it seems was also in your mind in your BFD Echo proposal.
> 
> This, however, seems not to be what Albert has in mind - as he has since commented that he really wants to have sub-second detection of MTU issues and 
> he wants traffic rerouted "immediately".

Right.  This is part of the point I'd made earlier in the thread.  Some
consumers need immediate failover and consistent MTU probe while others
might be satisfied with periodic probing.  

An interesting question for the large-packets draft is whether we want to
support a periodic probing mode, perhaps leveraging the stability draft's
ideas.  Or, should it instead only be consistent?

-- Jeff