Re: router-router NHRP

Yakov Rekhter <yakov@cisco.com> Fri, 10 November 1995 22:08 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15298; 10 Nov 95 17:08 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa15294; 10 Nov 95 17:08 EST
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id QAA20102; Fri, 10 Nov 1995 16:37:59 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id QAA19643 for rolc-out; Fri, 10 Nov 1995 16:43:23 -0500
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id QAA19634 for <rolc@nexen.com>; Fri, 10 Nov 1995 16:43:20 -0500
Received: from hubbub.cisco.com (hubbub.cisco.com [198.92.30.32]) by nexen.nexen.com (8.6.12/8.6.12) with ESMTP id QAA17729 for <rolc@nexen.com>; Fri, 10 Nov 1995 16:41:06 -0500
Received: from puli.cisco.com (puli.cisco.com [171.69.1.174]) by hubbub.cisco.com (8.6.12/CISCO.GATE.1.1) with SMTP id NAA13387; Fri, 10 Nov 1995 13:37:34 -0800
Message-Id: <199511102137.NAA13387@hubbub.cisco.com>
To: Dimitry Haskin <dhaskin@baynetworks.com>
cc: rolc@nexen.com
Subject: Re: router-router NHRP
In-reply-to: Your message of "Thu, 09 Nov 95 09:45:48 EST." <9511091445.AA08958@pobox.BayNetworks.com>
Date: Fri, 10 Nov 95 13:37:33 PST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Yakov Rekhter <yakov@cisco.com>
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/

Dimitry,

> It seems that we fail to communicate.  I never said that your "first
> constraint" requires the originator to "maintain in its FIB a route
> that covers *precisely* the same set of destinations as the target".
> I said (and I believe that you've just confirmed it) that it requires
> the originator to carry *a* route to the target which, of cause, can
> be a supperset of the target.  If we take as an example a transient
> domain with a need to carry the complete Internet set of target, it can
> account for circa 30,000 routes to cover the reachable destinations.

You are certainly correct. So, for example a domain that uses default
for exterior routing could just carry the default route and use
this default route for NHRP. NHRP doesn't alter the amount of routes 
that need to be carried.

Yakov.