I-D ACTION:draft-dube-route-reflection-harmful-00.txt
Interesting reading. Has anyone observed this operationally? -scott ----- Begin Included Message -----
From adm@ietf.org Thu Nov 5 11:15 EST 1998 Date: Thu, 05 Nov 1998 10:18:44 -0500 From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-dube-route-reflection-harmful-00.txt Sender: cclark@ns.cnri.reston.va.us To: IETF-Announce: ; Reply-to: Internet-Drafts@ietf.org MIME-version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="Boundary (ID_7WgSXfH+VQuKE2jHxl+2i) Content-Length: 2986
--Boundary_(ID_7WgSXfH+VQuKE2jHxl+2iQ) Content-type: TEXT/PLAIN Content-transfer-encoding: 7BIT A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Route Reflection Considered Harmful Author(s) : R. Dube, J. Scudder Filename : draft-dube-route-reflection-harmful-00.txt Pages : 5 Date : 04-Nov-98 Route reflection as defined by [2] is a popular way of reducing the full-mesh IBGP peering required by routers running the Border Gateway Protocol [1]. There are cases where a topology built using route reflectors produces persistent loops or does not produce the same results as what one would expect with a full IBGP mesh. This document describes these problems. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-dube-route-reflection-harmful-00.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-dube-route-reflection-harmful-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-dube-route-reflection-harmful-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --Boundary_(ID_7WgSXfH+VQuKE2jHxl+2iQ) Content-type: MULTIPART/ALTERNATIVE; BOUNDARY="Boundary_(ID_i1xvPY+rYZXJ++688kA3BQ)" --Boundary_(ID_i1xvPY+rYZXJ++688kA3BQ) Content-type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19981104173505.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-dube-route-reflection-harmful-00.txt --Boundary_(ID_i1xvPY+rYZXJ++688kA3BQ) Content-type: Message/External-body; directory=internet-drafts; access-type=anon-ftp; site=ftp.ietf.org; name=draft-dube-route-reflection-harmful-00.txt Content-disposition: ATTACHMENT; FILENAME=draft-dube-route-reflection-harmful-00.txt Content-Type: text/plain Content-ID: <19981104173505.I-D@ietf.org> --Boundary_(ID_i1xvPY+rYZXJ++688kA3BQ)-- --Boundary_(ID_7WgSXfH+VQuKE2jHxl+2iQ)-- ----- End Included Message -----
Scott Huddle wrote:
Interesting reading. Has anyone observed this operationally?
I don't think so because you have to construct a strange topology to achieve the first described effect (persistent loops); and the second effect ("incorrect" route computations) is pretty much what can be a desired behaviour. The definition of iBGP mesh's behaviour as ideal is questionable in many cases. So, yes, route reflector can behave differently but that can actually be a plus. As long as you know what you're doing. --vadim PS. Actually, even #1 is not a drawback. There's a lot of ways to create persistent loops with creative usage of iBGP mesh alone. That only shows that the tool is powerful enough :) All in all, the draft is a good piece on less than obvious dangers of fancy routing techniques.
participants (2)
-
Scott Huddle
-
Vadim Antonov