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 06: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 BAA06917 for <idr-archive@ietf.org>; Tue, 2 Mar 2004 01:51:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ay3kO-0000U9-00 for idr-archive@ietf.org; Tue, 02 Mar 2004 01:51:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ay3jW-0000NF-00 for idr-archive@ietf.org; Tue, 02 Mar 2004 01:50:27 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Ay3iu-0000GM-00; Tue, 02 Mar 2004 01:49:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ay3iA-0001Ta-BQ; Tue, 02 Mar 2004 01:49:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ay3hV-0001Jb-Ex for idr@optimus.ietf.org; Tue, 02 Mar 2004 01:48:21 -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 BAA06743 for <idr@ietf.org>; Tue, 2 Mar 2004 01:48:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ay3hS-00006n-00 for idr@ietf.org; Tue, 02 Mar 2004 01:48:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ay3gT-0007mp-00 for idr@ietf.org; Tue, 02 Mar 2004 01:47:18 -0500
Received: from natint2.juniper.net ([207.17.136.150] helo=roque-bsd.juniper.net) by ietf-mx with esmtp (Exim 4.12) id 1Ay3fY-0007aH-00 for idr@ietf.org; Tue, 02 Mar 2004 01:46:20 -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 i226ji1K050965; Mon, 1 Mar 2004 22:45:44 -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 i226jiF4050962; Mon, 1 Mar 2004 22:45:44 -0800 (PST)
Message-Id: <200403020645.i226jiF4050962@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: gargi@cisco.com
Cc: idr@ietf.org
Subject: Re: [Idr] issue 11.2: active route, again [Re: comments on idr-bgp4-20] (fwd)
In-Reply-To: <40442200.3030904@cisco.com>
References: <Pine.LNX.4.44.0403020736200.19488-100000@netcore.fi> <40442200.3030904@cisco.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: Mon, 01 Mar 2004 22:45:44 -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

Gargi Nalawade writes:

> Now that I understand your request for modification & clarification
> better, I think it makes sense. It would be good to clarify in the
> spec.

> If there is no operator here who can think of a reason why  they may
> want to explicitly prohibit BGP from advertising a route it doesnt own,
> even when the nexthop matches that in the forwarding table, we should
> make the other behavior (i.e. advertise even if BGP doesnt own the route 
> when the nexthop matches) the recommended one, stating the currently
> stated but least used behavior as an optional alternative.

My time to ask for a clarification...

It seems that you are saying that:

1) when the nexthop of a BGP route doesn't match the forwarding
nexthop selected in the routing table that BGP should not advertise
the route. In your words "it breaks routing", or it has the potential
to do so.

2) If the next-hop does match, BGP should advertise its route, even if
less preferred.

A second question would be how do you define 'next-hop matching' in
the context of an iBGP route vs an IGP route.

regards,
  Pedro.

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