Re: [Idr] issue 11.2: active route, again [Re: comments on idr-bgp4-20] (fwd)
Gargi Nalawade <gargi@cisco.com> Tue, 02 March 2004 05:18 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 AAA02414 for <idr-archive@ietf.org>; Tue, 2 Mar 2004 00:18:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ay2II-0004zO-00 for idr-archive@ietf.org; Tue, 02 Mar 2004 00:18:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ay2HK-0004sL-00 for idr-archive@ietf.org; Tue, 02 Mar 2004 00:17:15 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Ay2GQ-0004lJ-00; Tue, 02 Mar 2004 00:16:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ay2G9-0005Ed-Pu; Tue, 02 Mar 2004 00:16:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ay2FU-0005CP-6d for idr@optimus.ietf.org; Tue, 02 Mar 2004 00:15:20 -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 AAA02311 for <idr@ietf.org>; Tue, 2 Mar 2004 00:15:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ay2FR-0004dk-00 for idr@ietf.org; Tue, 02 Mar 2004 00:15:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ay2EZ-0004XT-00 for idr@ietf.org; Tue, 02 Mar 2004 00:14:23 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx with esmtp (Exim 4.12) id 1Ay2Dx-0004Od-00 for idr@ietf.org; Tue, 02 Mar 2004 00:13:45 -0500
Received: from cisco.com (hkidc-vpn-client-234-19.cisco.com [10.75.234.19]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i225ClLM006725; Mon, 1 Mar 2004 21:12:48 -0800 (PST)
Message-ID: <404417CE.2020901@cisco.com>
From: Gargi Nalawade <gargi@cisco.com>
Reply-To: gargi@cisco.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
CC: Pedro Roque Marques <roque@juniper.net>, idr@ietf.org
Subject: Re: [Idr] issue 11.2: active route, again [Re: comments on idr-bgp4-20] (fwd)
References: <Pine.LNX.4.44.0403020556590.18137-100000@netcore.fi>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
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 21:12:46 -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
Pekka Savola wrote: > On Mon, 1 Mar 2004, Gargi Nalawade wrote: > >>Are you asking that BGP advertise a route even if the nexthop of the >>route in the forwarding table is different? If so, this definitely >>breaks routing. As long as the nexthop of the 2 routes are the same, >>there is no problem. > > > Thanks for asking for clarification; I think this is very useful, and > a point which has not been spelled out clearly enough. > > I'm only interested of the case where the next-hop interface is the > same for both protocols. (Obviously, there is no 1-to-1 mapping, > because IGP gives an interface, but BGP an address.) For this case - there is no problem. Some implementations can already do this. But again there are operators who want the opposite behavior as well. i.e. BGP should not advertise a route if it is not the owner even if the BGP nexthop is the same as that of the route in the forwarding table. Both behaviors are achieved today by various imple- mentations even though the default may vary from vendor to vendor. Again - time for a clarification. :) Are you asking for that the behavior be present or that the spec be changed to describe both behaviors? -Gargi _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr
- Re: [Idr] issue 11.2: active route, again [Re: co… Pekka Savola
- Re: [Idr] issue 11.2: active route, again [Re: co… Pedro Roque Marques
- Re: [Idr] issue 11.2: active route, again [Re: co… Pekka Savola
- Re: [Idr] issue 11.2: active route, again [Re: co… Pedro Roque Marques
- Re: [Idr] issue 11.2: active route, again [Re: co… vijay gill
- Re: [Idr] issue 11.2: active route, again [Re: co… Pedro Roque Marques
- Re: [Idr] issue 11.2: active route, again [Re: co… Pedro Roque Marques
- Re: [Idr] issue 11.2: active route, again [Re: co… Gargi Nalawade
- Re: [Idr] issue 11.2: active route, again [Re: co… Pekka Savola
- Re: [Idr] issue 11.2: active route, again [Re: co… vijay gill
- Re: [Idr] issue 11.2: active route, again [Re: co… Gargi Nalawade
- Re: [Idr] issue 11.2: active route, again [Re: co… Pekka Savola
- Re: [Idr] issue 11.2: active route, again [Re: co… Gargi Nalawade
- Re: [Idr] issue 11.2: active route, again [Re: co… Pedro Roque Marques
- Re: [Idr] issue 11.2: active route, again [Re: co… Gargi Nalawade
- Re: [Idr] issue 11.2: active route, again [Re: co… vijay gill
- Re: [Idr] issue 11.2: active route, again [Re: co… Pedro Roque Marques
- Re: [Idr] issue 11.2: active route, again [Re: co… Pedro Roque Marques
- Re: [Idr] issue 11.2: active route, again [Re: co… vijay gill
- Re: [Idr] issue 11.2: active route, again [Re: co… vijay gill
- Re: [Idr] issue 11.2: active route, again [Re: co… vijay gill
- Re: [Idr] issue 11.2: active route, again [Re: co… Yakov Rekhter