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 03:32 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 A7F0B1A1EEC for <idr@ietfa.amsl.com>; Wed, 11 Feb 2015 19:32:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 tXgItzphHVhr for <idr@ietfa.amsl.com>; Wed, 11 Feb 2015 19:32:27 -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 40A7B1A1EFE for <idr@ietf.org>; Wed, 11 Feb 2015 19:32:26 -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 1YLkVq-000487-IE; Thu, 12 Feb 2015 03:32:23 +0000
Date: Thu, 12 Feb 2015 10:32:15 +0700
Message-ID: <m2a90jst34.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: David Freedman <david.freedman@uk.clara.net>
In-Reply-To: <D101AA78.AA0D8%david.freedman@uk.clara.net>
References: <D101AA78.AA0D8%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/OsofDl_neRm31IciT1j807LlFfw>
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 03:32:28 -0000

we considered a more 'liberal' approach similar to one recommended
privately by job, where the peer discovers who to set up bfd with by
what next hops they get.  this has problems in that it assumes NH is
set, prefixes exist (A may announce nothing to B), etc.

we also considered full rigid signaling approaches such as you and
nick suggest.  this path is much firmer theoretical ground.  the problem
is that it will wait years or forever for vendors to implement.

so this draft represents a middle ground (yes, a sofa-bed is neither a
good sofa nor a good bed:-) which we hope can be easily hacked so we can
actually deploy and use it, but which provides some assurance that you
know your potential bfd peer set.

ymmv, of course.

randy