Re: [Idr] advertising more than one route to a destination

Paul Jakma <paul@clubi.ie> Mon, 15 August 2005 16:17 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E4hep-0005Zu-So; Mon, 15 Aug 2005 12:17:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E4hen-0005Zj-Mx for idr@megatron.ietf.org; Mon, 15 Aug 2005 12:17:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11287 for <idr@ietf.org>; Mon, 15 Aug 2005 12:17:47 -0400 (EDT)
Received: from hibernia.jakma.org ([212.17.55.49] ident=[U2FsdGVkX19lr6dE0jTVKImijMtLMNQOZPC5LTiuE10=]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E4iDw-0002cW-N6 for idr@ietf.org; Mon, 15 Aug 2005 12:54:10 -0400
Received: from sheen.jakma.org (sheen.jakma.org [212.17.55.53]) by hibernia.jakma.org (8.13.1/8.13.1) with ESMTP id j7FGH9IH015908; Mon, 15 Aug 2005 17:17:12 +0100
Date: Mon, 15 Aug 2005 17:17:09 +0100
From: Paul Jakma <paul@clubi.ie>
X-X-Sender: paul@sheen.jakma.org
To: Yakov Rekhter <yakov@juniper.net>
Subject: Re: [Idr] advertising more than one route to a destination
In-Reply-To: <200508151609.j7FG9iG16181@merlot.juniper.net>
Message-ID: <Pine.LNX.4.63.0508151713470.7023@sheen.jakma.org>
References: <200508151609.j7FG9iG16181@merlot.juniper.net>
Mail-Copies-To: paul@hibernia.jakma.org
Mail-Followup-To: paul@hibernia.jakma.org
X-NSA: al aqsar jihad musharef jet-A1 avgas ammonium qran inshallah allah al-akbar martyr iraq saddam hammas hisballah rabin ayatollah korea vietnam revolt mustard gas british airways washington peroxide cool
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: skh@nexthop.com, Inter-Domain Routing List <idr@ietf.org>, "Nipper, Arnold" <arnold.nipper@de-cix.net>
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

On Mon, 15 Aug 2005, Yakov Rekhter wrote:

> Folks,
>
> As you know the basic BGP spec currently restricts a BGP speaker
> to advertise at most a single route to a given destination (given
> address prefix).
>
> The purpose of this e-mail is to solicit opinions on (a) what 
> applications could benefit if the above restriction is relaxed, as 
> to allow a BGP speaker to advertise multiple routes to a given 
> destination, and (b) whether the IDR WG should start work on 
> extending BGP to support these applications.

a) eBGP Route-servers at IXes, to act as 'dumb'
   (non-best-path-selecting) reflectors so as to reduce eBGP 'mesh'
   between IX users.

   iBGP reflectors, to reduce route-oscillations (see Walton, et al).

b) Yes.

    Note: there's at least one private draft examining this.

regards,
-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
Fortune:
Consultant, n.:
 	An ordinary man a long way from home.

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