Re: [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC from 4/13 to 4/27
Nick Hilliard <nick@foobar.org> Tue, 05 June 2018 21:06 UTC
Return-Path: <nick@foobar.org>
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 F0B1A131181; Tue, 5 Jun 2018 14:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 w0wQRYzozYkq; Tue, 5 Jun 2018 14:06:37 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14D5C131176; Tue, 5 Jun 2018 14:06:36 -0700 (PDT)
X-Envelope-To: idr@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id w55L6WJk087310 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Jun 2018 22:06:32 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
To: Robert Raszuk <robert@raszuk.net>
Cc: Randy Bush <randy@psg.com>, "idr@ietf. org" <idr@ietf.org>, Hares Susan <shares@ndzh.com>, draft-ietf-idr-rs-bfd@ietf.org
References: <013401d3d338$f7c74f60$e755ee20$@ndzh.com> <CACWOCC_fb1NcUC6qGrNFAA0CTBJkDOhecV4J-NgvTP7_wzWV5g@mail.gmail.com> <89466EFB-7F8F-4C5A-AB36-7E510FA3F3C6@juniper.net> <4f6267d4-6759-4ed6-2869-ccbe16d9a817@foobar.org> <m2r2loipj0.wl-randy@psg.com> <CA+b+ERkVoM4Z64BYp3MDd6GihBJBUbLmVMMHTHrd3UKrz+KTYA@mail.gmail.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <1b996f48-9d17-436c-3709-28fc8a93ef42@foobar.org>
Date: Tue, 05 Jun 2018 22:06:30 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 PostboxApp/6.0.10
MIME-Version: 1.0
In-Reply-To: <CA+b+ERkVoM4Z64BYp3MDd6GihBJBUbLmVMMHTHrd3UKrz+KTYA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Nix7Z4vku0bjFE1TRJNqhRHLkr8>
Subject: Re: [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC from 4/13 to 4/27
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.26
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, 05 Jun 2018 21:06:40 -0000
Robert, Robert Raszuk wrote on 04/06/2018 09:38: > * It has been demonstrated with real RS data that vast majority of RS > carry single path for given prefix. This draft will not help in such cases. the bfd brokerage aspect of draft-ietf-idr-rs-bfd will help enormously in this case. > * If there is second path available for a given prefix the simple > solution is to observe that most IXes offer two Route Servers. Therefor > it is trivial to make such secondary RS to distribute second best path > ahead of any failure (knob for this does exist already in number of > shipping implementations) - so this would be one line config change on > RS and no upgrade(s) to the IX clients needed. offering inconsistent views from a route server cluster is difficult. The best thing for an ixp to do is to provide a consistent and predictable service. > * It has also been pointed out that distributing 2 or even 3 or more > paths with add-paths will not cause any customer CE meltdown. So simply > configure "add-paths 2" on those clients who need two paths from single > RS and be done. In theory, yes. In practice, there are very few ebgp add-path implementations. Also in practice, if you want fail failover, you need bfd. > * Let's not forget the bigger picture here. IX peering is an > optimization. To provide redundancy across IX with failing fabric > connectivity, different IX peering can be used or destinations can be > reached over native Internet path. yes, but in order to use that alternative path, the client network needs to detect the failure at the IXP, which is what this draft is trying to achieve. > * Last getting different path does not guarantee any level success if > IX fabric failure location is close to the client. this point is out of scope for this discussion, which deals with arbitrary failures of the ixp fabric. Nick
- Re: [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC… Nick Hilliard
- [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC fro… Susan Hares
- Re: [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC… Randy Bush
- Re: [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC… John G. Scudder
- Re: [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC… Job Snijders
- Re: [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC… Robert Raszuk
- Re: [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC… John G. Scudder
- Re: [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC… Nick Hilliard
- Re: [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC… Randy Bush
- Re: [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC… Robert Raszuk
- Re: [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC… Nick Hilliard
- Re: [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC… Robert Raszuk
- Re: [Idr] draft-ietf-idr-rs-bfd-05 - 2 Week WG LC… Rajiv Asati (rajiva)