Re: [Idr] issue 11.2: active route, again [Re: comments on idr-bgp4-20] (fwd)

Pedro Roque Marques <roque@juniper.net> Tue, 02 March 2004 22:51 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05732 for <idr-archive@ietf.org>; Tue, 2 Mar 2004 17:51:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AyIju-0005Gq-00 for idr-archive@ietf.org; Tue, 02 Mar 2004 17:51:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AyIj2-00058v-00 for idr-archive@ietf.org; Tue, 02 Mar 2004 17:50:57 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AyIiN-00051j-00; Tue, 02 Mar 2004 17:50:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AyIiA-000447-TR; Tue, 02 Mar 2004 17:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AyIhw-00043g-D1 for idr@optimus.ietf.org; Tue, 02 Mar 2004 17:49:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05703 for <idr@ietf.org>; Tue, 2 Mar 2004 17:49:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AyIht-0004zq-00 for idr@ietf.org; Tue, 02 Mar 2004 17:49:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AyIgv-0004tH-00 for idr@ietf.org; Tue, 02 Mar 2004 17:48:46 -0500
Received: from natint2.juniper.net ([207.17.136.150] helo=roque-bsd.juniper.net) by ietf-mx with esmtp (Exim 4.12) id 1AyIg1-0004gy-00 for idr@ietf.org; Tue, 02 Mar 2004 17:47:49 -0500
Received: from roque-bsd.juniper.net (localhost [127.0.0.1]) by roque-bsd.juniper.net (8.12.8p1/8.12.3) with ESMTP id i22MlJ1K052564; Tue, 2 Mar 2004 14:47:19 -0800 (PST) (envelope-from roque@roque-bsd.juniper.net)
Received: (from roque@localhost) by roque-bsd.juniper.net (8.12.8p1/8.12.3/Submit) id i22MlJXN052561; Tue, 2 Mar 2004 14:47:19 -0800 (PST)
Message-Id: <200403022247.i22MlJXN052561@roque-bsd.juniper.net>
From: Pedro Roque Marques <roque@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: vijay gill <vgill@vijaygill.com>
Cc: idr@ietf.org
Subject: Re: [Idr] issue 11.2: active route, again [Re: comments on idr-bgp4-20] (fwd)
In-Reply-To: <20040302153406.GA5590@vijaygill.com>
References: <Pine.LNX.4.44.0403020736200.19488-100000@netcore.fi> <40442200.3030904@cisco.com> <200403020645.i226jiF4050962@roque-bsd.juniper.net> <20040302153406.GA5590@vijaygill.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Content-Transfer-Encoding: 7bit
Sender: idr-admin@ietf.org
Errors-To: idr-admin@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Id: Inter-Domain Routing <idr.ietf.org>
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>
List-Archive: <https://www1.ietf.org/mail-archive/working-groups/idr/>
Date: Tue, 02 Mar 2004 14:47:19 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

vijay gill writes:

> What BGP does should be separate from anything else. You have the
> bgp database, operate on the BGP database. Pick routes, only look to
> see if you have a valid next-hop, and then continue on.

Vijay,
I'm sure that your view as its merits... but we also need to consider
the question the other way around.

When you receive a BGP advertisement from a neighbor, do you expect 
traffic sent to that neighbor to follow the ASes that are present in
the corresponding routing advertisement ?

Do you make any assumptions based on the contents of such as-path
attribute ?

Is it a 'feature' or a 'bug' if traffic doesn't follow the path
advertised by routing...

This is an issue that exists today... and not strictly related to the
advertisement of inactive paths. I believe CAIDA has made measurements
of such inconsistencies.

But while it is easy for all of us to say "i'd like to be able to do
whatever i want" a more interesting question is "what i would like
others to contrain themselfs to"...

Disabling the advertisement of inactive routes is not a panacea that
will address all inconsistencies, assuming one does care about
those...

  Pedro.

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