[Idr] advertising more than one route to a destination
Yakov Rekhter <yakov@juniper.net> Mon, 15 August 2005 16:09 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E4hXA-00034k-JP; Mon, 15 Aug 2005 12:09:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E4hX9-00034f-PM for idr@megatron.ietf.org; Mon, 15 Aug 2005 12:09:55 -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 MAA10566 for <idr@ietf.org>; Mon, 15 Aug 2005 12:09:53 -0400 (EDT)
Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E4i6I-0002Hn-Tp for idr@ietf.org; Mon, 15 Aug 2005 12:46:16 -0400
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id j7FG9iBm034145; Mon, 15 Aug 2005 09:09:44 -0700 (PDT) (envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j7FG9iG16181; Mon, 15 Aug 2005 09:09:44 -0700 (PDT) (envelope-from yakov@juniper.net)
Message-Id: <200508151609.j7FG9iG16181@merlot.juniper.net>
To: idr@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <45571.1124122184.1@juniper.net>
Date: Mon, 15 Aug 2005 09:09:44 -0700
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: skh@nexthop.com
Subject: [Idr] advertising more than one route to a destination
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
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. With this in mind, please answer the following two questions: 1. What applications could benefit from allowing a BGP speaker to advertise multiple routes to a destination ? 2. Should the IDR WG start work on extending BGP to support such applications ? The deadline for response is August 29. Yakov. _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr
- [Idr] advertising more than one route to a destin… Yakov Rekhter
- Re: [Idr] advertising more than one route to a de… Paul Jakma
- Re: [Idr] advertising more than one route to a de… Enke Chen
- Re: [Idr] advertising more than one route to a de… Olivier Bonaventure
- Re: [Idr] advertising more than one route to a de… Manav Bhatia