Re: router-router NHRP

Yakov Rekhter <yakov@cisco.com> Thu, 09 November 1995 03:06 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24350; 8 Nov 95 22:06 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa24346; 8 Nov 95 22:06 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 VAA07620; Wed, 8 Nov 1995 21:33:24 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id VAA26351 for rolc-out; Wed, 8 Nov 1995 21:44:12 -0500
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id VAA26342 for <rolc@nexen.com>; Wed, 8 Nov 1995 21:44:09 -0500
Received: from hubbub.cisco.com (hubbub.cisco.com [198.92.30.32]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id VAA07603 for <rolc@nexen.com>; Wed, 8 Nov 1995 21:30:09 -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 SAA14057; Wed, 8 Nov 1995 18:39:00 -0800
Message-Id: <199511090239.SAA14057@hubbub.cisco.com>
To: Dimitry Haskin <dhaskin@baynetworks.com>
cc: rolc@nexen.com
Subject: Re: router-router NHRP
In-reply-to: Your message of "Wed, 08 Nov 95 19:06:02 EST." <9511090006.AA13852@pobox.BayNetworks.com>
Date: Wed, 08 Nov 95 18:39:00 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,

> I don't believe you've answered my question on the *implication* (not
> intention) of the "first NHRP target constraint".  To reiterate,  does
> this constraint require that a Request can be only originated if
> a route to the requested target is already present in the originating
> forwarder FIB?  And if so, wouldn't it mandate a large FIB in some cases?

This constraint does not imply that the originator of a Request has to
maintain in its FIB a route that covers precisely the same set of
destinations as the target, priot to issuing the Request.
For example, the originator of a Request may have in its FIB a route
to 192.9.200/24, but may generate NHRP Request for 192.9.9.200.9
as the target.  

Yakov.