IETF Logo Mail Archive

Re: [Idr] I-D Action: draft-ietf-idr-rs-bfd-02.txt

Gert Doering <gert@space.net> Tue, 21 March 2017 08:26 UTC

Return-Path: <gert@space.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F43D129680 for <idr@ietfa.amsl.com>; Tue, 21 Mar 2017 01:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-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 bi0AmjUl3ogv for <idr@ietfa.amsl.com>; Tue, 21 Mar 2017 01:26:27 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB2B1127333 for <idr@ietf.org>; Tue, 21 Mar 2017 01:26:25 -0700 (PDT)
X-Original-To: idr@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id AADA960771 for <idr@ietf.org>; Tue, 21 Mar 2017 09:26:22 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 76F0B604A9; Tue, 21 Mar 2017 09:26:22 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id 688816B922; Tue, 21 Mar 2017 09:26:22 +0100 (CET)
Date: Tue, 21 Mar 2017 09:26:22 +0100
From: Gert Doering <gert@space.net>
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: Gert Doering <gert@space.net>, Robert Raszuk <robert@raszuk.net>, idr wg <idr@ietf.org>
Message-ID: <20170321082622.GP2367@Space.Net>
References: <CA+b+ERmWUL-pVwjW8Vq+Vz8UzYDpcVBZxxhtM6WFqhmG+r35WA@mail.gmail.com> <58C95A05.3030107@foobar.org> <20170315195050.GT12864@pfrc.org> <CA+b+ERn-uya3kB-FgXvfFjdK-hPmj-W-mv_T+TnbEAfkzR8Hfg@mail.gmail.com> <20170315212656.GD2367@Space.Net> <CA+b+ER=MnejDq5JNyNUHvf7mV7vkFehbeE65a_5cqFUsTEAzZA@mail.gmail.com> <CACWOCC-gAPbV0fdraHkkjhSo=Tc_YUFWMTOjx311a2XDJZMDmQ@mail.gmail.com> <CA+b+ERmxQkH75tbotT16hsZvqrvMVsX0G_zyY1ofA=kTZZzZ0w@mail.gmail.com> <20170316073753.GE2367@Space.Net> <20170320200415.GB28021@pfrc.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="L/UlCz6KLdX40+mu"
Content-Disposition: inline
In-Reply-To: <20170320200415.GB28021@pfrc.org>
X-NCC-RegID: de.space
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/uKBGmqvFi3TPlgS8JjDm14fY-6Q>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-rs-bfd-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Mar 2017 08:26:29 -0000

Hi,

On Mon, Mar 20, 2017 at 04:04:15PM -0400, Jeffrey Haas wrote:
> On Thu, Mar 16, 2017 at 08:37:53AM +0100, Gert Doering wrote:
[..]
> > (I'm not aware of any gear that will do this right now, as in "if
> > IPv4 ARP or IPv6 ND fails, mark NH as invalid and look for other paths
> > in BGP" - but I'm always willing to learn)
> 
> Having been at the wrong end of quirks of ND/ARP issues, I don't recommend
> this as a sufficiently useful mechanism.  

Well, it won't catch all possible faults - but generally having a feedback
mechanism from the L2 address resolution layer about "no idea where to
send this packet to!" would catch the easy ones, that is: total blackholing
due to fabric issues and "peer botched their IPv6 ACLs and ND breaks".

> I also suspect the IXPs wouldn't want their customers participating in a
> layer 2 OAM mechanism.  This leaves layer 3, which moves us largely to BFD.
> 
> Or alternatively ping. Which is gross, but would totally work.

Indeed :-)

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279

v2.23.0 | Report a Bug | By Email