Re: [Idr] draft-asati-idr-bgp-bestpath-selection-criteria as IDR WG draft

Mike Benjamin <mikeb@gblx.net> Thu, 23 July 2009 16:52 UTC

Return-Path: <mikeb@gblx.net>
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 38ECE3A6B96 for <idr@core3.amsl.com>; Thu, 23 Jul 2009 09:52:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.812
X-Spam-Level:
X-Spam-Status: No, score=-0.812 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iQMopS801Va3 for <idr@core3.amsl.com>; Thu, 23 Jul 2009 09:52:52 -0700 (PDT)
Received: from pinky.disturbed.org (host-216-9-185-208.orbitelcom.com [216.9.185.208]) by core3.amsl.com (Postfix) with ESMTP id 895D63A6B83 for <idr@ietf.org>; Thu, 23 Jul 2009 09:52:52 -0700 (PDT)
Received: from pinky.disturbed.org (localhost [127.0.0.1]) by pinky.disturbed.org (8.14.2/8.14.2) with ESMTP id n6NGpXZT093304; Thu, 23 Jul 2009 09:51:33 -0700 (MST) (envelope-from mikeb@gblx.net)
Received: (from mikeb@localhost) by pinky.disturbed.org (8.14.3/8.14.3/Submit) id n6NGpW19093303; Thu, 23 Jul 2009 09:51:32 -0700 (MST) (envelope-from mikeb@gblx.net)
X-Authentication-Warning: pinky.disturbed.org: mikeb set sender to mikeb@gblx.net using -f
Date: Thu, 23 Jul 2009 09:51:32 -0700
From: Mike Benjamin <mikeb@gblx.net>
To: Curtis Villamizar <curtis@occnc.com>
Message-ID: <20090723165132.GA80638@gblx.net>
References: <56CC1BBE-4437-4FA8-85A6-D4E3E9A9B8C6@juniper.net> <200907230422.n6N4MgYa021490@harbor.orleans.occnc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200907230422.n6N4MgYa021490@harbor.orleans.occnc.com>
User-Agent: Mutt/1.4.2.3i
Cc: idr List <idr@ietf.org>
Subject: Re: [Idr] draft-asati-idr-bgp-bestpath-selection-criteria as IDR WG draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 23 Jul 2009 16:52:53 -0000

On Thu, Jul 23, 2009 at 12:22:42AM -0400, Curtis Villamizar wrote:
: 
: The first rule just seems obvious and out of scope for RFC4271.  Is
: the first rule saying much more than "If there is more than one IGP
: instance, pick the right one"?  If so is that too obvious to need to
: be stated?


The first rule is stating that if the nexthop lookup resolves to a
path that has no knowledge of the route, it should not be considered.

For example, two LERs that do not exchange their BGP table with the
LSR.  In the event of an LSP failure, BGP still resolves the nexthop,
via an IGP path, installs the route, and the device blackholes
anything destined for it.

The mechanism is stating that BGP should be given the knowledge of
where to look for a valid nexthop.  IGP sourced RIB entries can be
considered to establish the BGP session, but should not be used to
resolve the nexthop if that path has no knowledge of how to get there.

--mikeb

: 
: Curtis
: _______________________________________________
: Idr mailing list
: Idr@ietf.org
: https://www.ietf.org/mailman/listinfo/idr

--
Mike Benjamin   -     +1-602-744-3403
mikeb@gblx.net  - Development Engineering
Global Crossing -       Phoenix, USA