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

Jeffrey Haas <jhaas@pfrc.org> Tue, 04 July 2017 17:44 UTC

Return-Path: <jhaas@slice.pfrc.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 3381C132603 for <idr@ietfa.amsl.com>; Tue, 4 Jul 2017 10:44:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 idLcm9lCdn79 for <idr@ietfa.amsl.com>; Tue, 4 Jul 2017 10:44:21 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 88AEE129AEB for <idr@ietf.org>; Tue, 4 Jul 2017 10:44:21 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 1FB831E34A; Tue, 4 Jul 2017 13:53:35 -0400 (EDT)
Date: Tue, 04 Jul 2017 13:53:34 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Job Snijders <job@ntt.net>
Cc: idr@ietf.org
Message-ID: <20170704175334.GO2289@pfrc.org>
References: <m2van9z3jp.wl-randy@psg.com> <CACWOCC8tPVD20SJ60h-=NGbPMG3Fae2a0TY5rMFb=EnN7H-C6Q@mail.gmail.com> <m2o9t1z1hj.wl-randy@psg.com> <CACWOCC_bQitHeR9tHc5tPsXmoSDDLQH764equTAHrP854fYh-A@mail.gmail.com> <BF65C4DC-D2F5-41AF-8454-D43B403E328B@juniper.net> <CACWOCC9cmz7ARnWNowCCEu3Rt_NiyuWgJMZ3pWfmxZ_BO8Ovjw@mail.gmail.com> <292534ED-98BC-49A0-82A2-45B6688F851D@juniper.net> <CACWOCC_KTzJLQAJf_j4ZqM1oJSFq9JcyT7aAPLGf3+2Ess7BBA@mail.gmail.com> <09BFF794-6899-4DA5-8EF5-DDF86513BFBA@pfrc.org> <20170704104840.mg5bflnmmjlv4jbi@Vurt.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20170704104840.mg5bflnmmjlv4jbi@Vurt.local>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/3UqEFTQW0n5fWq_coQg2dyOU0ec>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-rs-bfd-03.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, 04 Jul 2017 17:44:23 -0000

On Tue, Jul 04, 2017 at 12:48:40PM +0200, Job Snijders wrote:
> On Mon, Jul 03, 2017 at 06:20:28PM -0400, Jeffrey Haas wrote:
> > > On Jul 3, 2017, at 5:55 PM, Job Snijders <job@ntt.net> wrote:
> > > 
> > > I'm not sure whether events will be packed together this neatly. 
> > > 
> > > Questions that remain: 
> > > 
> > > - is it absolutely necessary for the RS to be aware of the entire
> > > bfd session topology state?
> > 
> > The draft is written with the idea that some/many devices *won't* be
> > aware.  If the state is Unknown, things still work.
> 
> Like with today's RS? "This draft doesn't make it worse" is hardly an
> impressive statement ;-)

It's BGP.  You have to deal with what incremental deployment looks like.

[...]
> > Looked at a somewhat different way, choosing the backup paths is no
> > different than add-paths or diverse paths feature choosing the next
> > best path.  But since the RS and the client could have already
> > conveyed the possible set of nexthops for the view, there's no need
> > for stepwise discovery. Perhaps this point needs to be made clearer
> > in the draft.
> 
> But any churn in the possible set of nexthops, directly results in BGP
> churn, where as when the route server is not kept in the loop about who
> can reach who, there will not be any churn at the route server level
> when 2 RS participants cannot reach each other (temporarily).

I believe you are confused about the CPU work associated with providing
add-paths actually is.

Add-paths implementations already run N-best calculations.  They must
already include the work of running policy and BGP loop checks.  Adding an
additional exclusion list based on nexthop viability for the view isn't
significantly more work for a given round of route selection.

If you'd like to argue "send them 2, and if they both don't work, let god
and their backup paths sort it out", fine.  You're welcome to run your RS
that way - if you run a RS.  What I don't understand is why you object to
someone else doing something different.

-- Jeff