Re: Proxy: comments on section 9.1.3

"'Mathew Richardson'" <mrr@nexthop.com> Fri, 06 September 2002 16:18 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 MAA10983 for <idr-archive@ietf.org>; Fri, 6 Sep 2002 12:18:13 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix) id AFA4591306; Fri, 6 Sep 2002 12:19:30 -0400 (EDT)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id 82F7D91307; Fri, 6 Sep 2002 12:19:30 -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 461BD91306 for <idr@trapdoor.merit.edu>; Fri, 6 Sep 2002 12:18:20 -0400 (EDT)
Received: by segue.merit.edu (Postfix) id 29E895DE4E; Fri, 6 Sep 2002 12:18:20 -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 749485DE4C for <idr@merit.edu>; Fri, 6 Sep 2002 12:18:19 -0400 (EDT)
Received: (from root@localhost) by presque.djinesys.com (8.11.3/8.11.1) id g86GIGS32730; Fri, 6 Sep 2002 12:18:16 -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 g86GIDG32722; Fri, 6 Sep 2002 12:18:13 -0400 (EDT) (envelope-from mrr@mrichardson.nexthop.com)
Received: (from mrr@localhost) by paradigm.nexthop.com (8.11.6/8.11.6) id g86GIDF25436; Fri, 6 Sep 2002 12:18:13 -0400 (EDT)
Date: Fri, 06 Sep 2002 12:18:13 -0400
From: 'Mathew Richardson' <mrr@nexthop.com>
To: "Cambria, Mike" <mcambria@avaya.com>
Cc: "'Abarbanel, Benjamin'" <Benjamin.Abarbanel@marconi.com>, idr@merit.edu
Subject: Re: Proxy: comments on section 9.1.3
Message-ID: <20020906161813.GM23831@nexthop.com>
References: <3A6D367EA1EFD4118C9B00A0C9DD99D7E4ED5C@rerun.avayactc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <3A6D367EA1EFD4118C9B00A0C9DD99D7E4ED5C@rerun.avayactc.com>
User-Agent: Mutt/1.4i
X-Virus-Scanned: by AMaViS perl-11
Sender: owner-idr@merit.edu
Precedence: bulk

> Cambria, Mike <mcambria@avaya.com> [Fri, Sep 06, 2002 at 11:53:53AM -0400]:
>
>(Pretending that I'm) reading the draft for the first time...
>
>Your comment:
>
>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?
>
>and the text in 9.1.3 can be read as a contraction of section 2 (when only
>considering the base document, no route reflectors, route servers etc.):
>
>"... one must focus on the rule that a BGP speaker advertises to its peers
>(other BGP speakers which it communicates with) in neighboring ASs only
>those routes that it itself uses."

I thought that that was in there somewhere :)  I guess I've just gotten
in to the bad habit of skipping the intro and going straight to the
"good stuff" :)

>If, in the scope of an implementation of only what is specified in this
>draft, one can advertise to a peer what is in Loc-RIB but not the Route
>Table, the text in section 2 should be clarified.  Otherwise, the text in
>9.1.3 (and your comment) should be clarified, as it doesn't mention anything
>about the route table.

How about changing the paragraph after c) in 9.1.2 to:

  The local speaker SHALL then install that route in the Loc-RIB,
  replacing any route to the same destination that is currently being
  held in the Loc-RIB.  This route SHALL then also be installed in
  the BGP speakers forwarding table.

<snip>

I personally much prefer this.  It helps keep the base spec focused
on describing the base protocol.

mrr