[Idr] Status of the AddPath Capability
Uli Bornhauser <ub@cs.uni-bonn.de> Mon, 03 December 2007 07:44 UTC
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iz5yb-00020z-Vl; Mon, 03 Dec 2007 02:44:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iz5ya-00020q-KG for idr@ietf.org; Mon, 03 Dec 2007 02:44:24 -0500
Received: from postfix.iai.uni-bonn.de ([131.220.8.4]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iz5yZ-0003Fr-0V for idr@ietf.org; Mon, 03 Dec 2007 02:44:24 -0500
X-IAI-Env-From: <ub@cs.uni-bonn.de> : [81.173.185.4]
Received: from [192.171.2.2] (xdsl-81-173-185-4.netcologne.de [81.173.185.4]) by postfix.iai.uni-bonn.de (Postfix) with ESMTP id 5834F5C85E; Mon, 3 Dec 2007 08:44:19 +0100 (MET) (envelope-from ub@cs.uni-bonn.de) (envelope-to VARIOUS) (2) (internal use: ta=1, tu=1, te=1, am=P, au=ub)
Message-ID: <4753B3CC.40903@cs.uni-bonn.de>
Date: Mon, 03 Dec 2007 08:44:12 +0100
From: Uli Bornhauser <ub@cs.uni-bonn.de>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: idr@ietf.org
X-Enigmail-Version: 0.95.5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc:
Subject: [Idr] Status of the AddPath Capability
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>
Errors-To: idr-bounces@ietf.org
Hello Everybody, my name is Uli Bornhauser, and I am a PhD. Student at the University of Bonn, Germany. I’m working in the area of Inter Domain Routing, trying to develop new BGP routing architectures. This area of research is motivated by routing anomalies as temporal and consistent divergence, for example, that come along with iBGP scaling techniques such as iBGP Route Reflection. Obviously, there are various approaches discussed in literature to avoid these and other routing anomalies using Route Reflection. As some of you certainly know, some interesting approaches try to avoid these anomalies by advertising additional path information via a BGP session between two BGP peers (AddPath capability). Extensions to advertise several paths for a single destination through the same BGP sessions are discussed by Daniel Walton, Alvaro Retana, and Enke Chen [1] as well as Manav Bhatia, Joel M. Halpern, and Paul Jakma [2], for example. In the last months, I have considered some new approaches which can avoid various routing anomalies in general. However, to make these approaches usable in practice its seems to be necessary to exchange more path information in the AS than specified in BGPv4, as described in the Internet Drafts mentioned above. >From my point of view, an interesting question is what status these documents have? Is anyone working in this area and are there efforts at the current point in time to include these extension in BGP? The last information about this topic I found is the IETF‐65 IDR minutes [3]. What happen after that? Are there any new developments in this area in 2007? I am grateful for all comments and suggestions. Regards Uli Bornhauser -- ______________________________________________________________ Uli Bornhauser University of Bonn Institute of Computer Science IV Email: ub@cs.uni-bonn.de Roemerstr. 164 Phone: +49 (228) 73 - 4550 D - 53117 Bonn Fax: +49 (228) 73 - 4571 Germany _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr
- [Idr] Status of the AddPath Capability Uli Bornhauser
- Re: [Idr] Status of the AddPath Capability Uli Bornhauser