Re: [Idr] IDR WG LC on draft-ietf-idr-ix-bgp-route-server (2/2/2015 - 2/16/2015)

Randy Bush <randy@psg.com> Thu, 12 February 2015 06:49 UTC

Return-Path: <randy@psg.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9D4A1A6EFC for <idr@ietfa.amsl.com>; Wed, 11 Feb 2015 22:49:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.31
X-Spam-Level:
X-Spam-Status: No, score=-6.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 68Q-jnMa6SFn for <idr@ietfa.amsl.com>; Wed, 11 Feb 2015 22:49:25 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [198.180.150.18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73DAF1A9074 for <idr@ietf.org>; Wed, 11 Feb 2015 22:49:25 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1YLnaV-0005M1-Pi; Thu, 12 Feb 2015 06:49:24 +0000
Date: Thu, 12 Feb 2015 13:49:20 +0700
Message-ID: <m2egpvr5e7.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: David Freedman <david.freedman@uk.clara.net>
In-Reply-To: <D102087F.AA1B2%david.freedman@uk.clara.net>
References: <D101AA78.AA0D8%david.freedman@uk.clara.net> <m2a90jst34.wl%randy@psg.com> <D102047C.AA1A1%david.freedman@uk.clara.net> <m2k2znr620.wl%randy@psg.com> <D102087F.AA1B2%david.freedman@uk.clara.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/geqTO1_AACpHPUbrPJJ9hiAC69M>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] IDR WG LC on draft-ietf-idr-ix-bgp-route-server (2/2/2015 - 2/16/2015)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 12 Feb 2015 06:49:27 -0000

>> while A may not announce anything to B, B may have gifts for A
> That's fine, there is still a valid forwarding path here, why would we
> not set up a (BFD) session?

you would.  the point is that B can not count on receiving a route to A
to tell B to set up bfd to A

>>>>> which provides some assurance that you know your potential bfd peer
>>>>> set.
>>> Is't this the point of the RS, to facilitate in the face of the
>>> unknown?  with the above approach, assuming I filter against the RS,
>>> if I wanted to, would I not still reach the same outcome?
> 
> I was just commenting on how I feel that this doesn't violate the RS
> model.

cool.  the exercise started with arnold asking what would make me more
comfortable with RSs given that i like my data plane to be congruent
with my control plane.

> Assuming you filter properly (including asking the RS not to spread
> your prefixes to those you don't want it to), you shouldn't get any
> unsolicited BFD setup requests.

makes sense to me.  at bknix with the gang who are figuring out how to
tell members to use ixp-mangler to only configure a bird peering if both
parties agree.

randy