Re: BFD stability follow-up from IETF-91

Jeffrey Haas <jhaas@pfrc.org> Thu, 04 December 2014 15:17 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFB521AD3AF for <rtg-bfd@ietfa.amsl.com>; Thu, 4 Dec 2014 07:17:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.578
X-Spam-Level:
X-Spam-Status: No, score=-1.578 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 mFMQsjFSh8f6 for <rtg-bfd@ietfa.amsl.com>; Thu, 4 Dec 2014 07:17:09 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 13F6A1A0183 for <rtg-bfd@ietf.org>; Thu, 4 Dec 2014 07:17:09 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id C6136C1E5; Thu, 4 Dec 2014 10:17:08 -0500 (EST)
Date: Thu, 04 Dec 2014 10:17:08 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Nobo Akiya (nobo)" <nobo@cisco.com>
Subject: Re: BFD stability follow-up from IETF-91
Message-ID: <20141204151708.GA9458@pfrc>
References: <CO2PR0501MB823C222B7D62779F4DF58CDB3780@CO2PR0501MB823.namprd05.prod.outlook.com> <D0A647C1.28843%mmudigon@cisco.com> <CO2PR0501MB8234A1BDDFD008EE12C847AB3780@CO2PR0501MB823.namprd05.prod.outlook.com> <CECE764681BE964CBE1DFF78F3CDD3943F5AE38D@xmb-aln-x01.cisco.com> <CAG1kdogkUr2YyodeUPWOqea+2jqOkmdYnPywVHCw8j1+=9eM6A@mail.gmail.com> <CECE764681BE964CBE1DFF78F3CDD3943F5AE4AE@xmb-aln-x01.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3943F5AE4AE@xmb-aln-x01.cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-bfd/lbXCxEwPOKNXCwVmnr8Grz4TozI
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 04 Dec 2014 15:17:10 -0000

On Thu, Dec 04, 2014 at 03:14:50PM +0000, Nobo Akiya (nobo) wrote:
> If what you say is the only requirement not met, one approach may be to pursue a non-standard-track document describing some suggested implementation techniques to locally store TX/RX timestamp.
> 
> Given that echo approach will be less accurate and given that we seem to be having difficulty converging, I thought I???ll throw out another idea.

I think my biggest concern is that the echo approach has bidirectional
packet loss possibilities.  Async at least lets the receiver know about
unidirectional packet loss.

Of course, if your goal is to notify the sender that their packets are being
lost, you need a backchannel anyway.  I just don't know if we want that back
channel to be bfd.

- Jeff