Re: Proxy: comments on section 9.1.3

"'Mathew Richardson'" <mrr@nexthop.com> Fri, 06 September 2002 14:34 UTC

Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05353 for <idr-archive@ietf.org>; Fri, 6 Sep 2002 10:34:40 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix) id BC7A0912E7; Fri, 6 Sep 2002 10:34:34 -0400 (EDT)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id 7577D912F3; Fri, 6 Sep 2002 10:34:34 -0400 (EDT)
Delivered-To: idr@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id 31A9D912E7 for <idr@trapdoor.merit.edu>; Fri, 6 Sep 2002 10:34:28 -0400 (EDT)
Received: by segue.merit.edu (Postfix) id 167815DE4E; Fri, 6 Sep 2002 10:34:28 -0400 (EDT)
Delivered-To: idr@merit.edu
Received: from presque.djinesys.com (dns.nexthop.com [64.211.218.216]) by segue.merit.edu (Postfix) with ESMTP id 891E65DDCA for <idr@merit.edu>; Fri, 6 Sep 2002 10:34:27 -0400 (EDT)
Received: (from root@localhost) by presque.djinesys.com (8.11.3/8.11.1) id g86EYPS28196; Fri, 6 Sep 2002 10:34:25 -0400 (EDT) (envelope-from mrr@mrichardson.nexthop.com)
Received: from paradigm.nexthop.com (mrichardson.nexthop.com [64.211.218.45]) by presque.djinesys.com (8.11.3/8.11.1) with ESMTP id g86EYMG28189; Fri, 6 Sep 2002 10:34:22 -0400 (EDT) (envelope-from mrr@mrichardson.nexthop.com)
Received: (from mrr@localhost) by paradigm.nexthop.com (8.11.6/8.11.6) id g86EYMj24755; Fri, 6 Sep 2002 10:34:22 -0400 (EDT)
Date: Fri, 06 Sep 2002 10:34:22 -0400
From: 'Mathew Richardson' <mrr@nexthop.com>
To: "Abarbanel, Benjamin" <Benjamin.Abarbanel@marconi.com>
Cc: idr@merit.edu
Subject: Re: Proxy: comments on section 9.1.3
Message-ID: <20020906143422.GC23831@nexthop.com>
References: <39469E08BD83D411A3D900204840EC55BC2DD1@vie-msgusr-01.dc.fore.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <39469E08BD83D411A3D900204840EC55BC2DD1@vie-msgusr-01.dc.fore.com>
User-Agent: Mutt/1.4i
X-Virus-Scanned: by AMaViS perl-11
Sender: owner-idr@merit.edu
Precedence: bulk

> Abarbanel, Benjamin <Benjamin.Abarbanel@Marconi.com> [Fri, Sep 06, 2002 at 10:26:59AM -0400]:
>Mathew:
>
> 
>> >
>> >I'm looking for clarification to wording in section 9.1.3 
>> Phase 3: Route
>> >Dessemination of draft-ietf-idr-bgp4-17.txt.
>> >
>> >My understanding is that a BGP route should not be 
>> advertised to a peer if
>> >that route is not also in the Routing Table (e.g. FIB).  I 
>> was looking for
>> >wording to support this, but am now starting to second guess myself.
>> >
>
>What about the case where the best BGP route for a given destination is
>rejected/
>preempted from the routing table by a higher preferenced IGP, Static, etc.,
>route which is really used for forwarding?

This route would have to be in the Loc-RIB, and would replace all other
routes in the Loc-RIB.  Whether this actually happens or not is a matter
of local-policy.

>Somewhere in section 9.1.x, Do we want to mention the fact that the best 
>Loc-RIB BGP route for a given destination is still advertised to outgoing 
>peers via the Adj-RIB-out after it passes the outbound policy filtering,
>even though it is not really used for forwarding?

<snip>

You're talking about the case where a BGP route to some destination D
has been installed in the Loc-RIB, but no route to destination D has been
added to the forwarding table?  I'm not sure we want to elaborate on that
case, except, perhaps, to disallow it.

mrr