IETF Logo Mail Archive

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

Jeffrey Haas <jhaas@pfrc.org> Mon, 29 October 2018 16:42 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 DA6F91271FF for <rtg-bfd@ietfa.amsl.com>; Mon, 29 Oct 2018 09:42:24 -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 NaOzkuXEgRPQ for <rtg-bfd@ietfa.amsl.com>; Mon, 29 Oct 2018 09:42:23 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id A2BD2128D09 for <rtg-bfd@ietf.org>; Mon, 29 Oct 2018 09:42:23 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 625931E44B; Mon, 29 Oct 2018 12:41:45 -0400 (EDT)
Date: Mon, 29 Oct 2018 12:41:45 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
Cc: "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "Naiming Shen (naiming)" <naiming@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: Re: BFD WG adoption for draft-haas-bfd-large-packets
Message-ID: <20181029164144.GQ12336@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> <B5988BA3-E039-47C5-9145-48747700E197@cisco.com> <20181029153534.GL12336@pfrc.org> <97dc2816249742649218b7b49b475410@XCH-ALN-001.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <97dc2816249742649218b7b49b475410@XCH-ALN-001.cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/ZTKg3xMYXjpfskSLowiCwKl5xfQ>
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: Mon, 29 Oct 2018 16:42:25 -0000

On Mon, Oct 29, 2018 at 04:39:04PM +0000, Les Ginsberg (ginsberg) wrote:
> Given the MTU issue is associated with a link coming up - and the use of Echo would allow the problem to be detected and prevent the BFD session from coming up - 
> and you are acknowledging that the protocol allows padded Echo packets today ...
> 
> is there really a need to do anything more?

... the fact that the majority of BFD implementations on the planet do not
support Echo mode?

Not to mention my whole comment that BFD Echo is intentionally
under-specified.  The result being that any attempt to specify anything in
it will likely cause interop headaches.

-- Jeff

v2.23.0 | Report a Bug | By Email