Re: router-router NHRP
Dimitry Haskin <dhaskin@baynetworks.com> Wed, 15 November 1995 00:10 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa26155;
14 Nov 95 19:10 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa26151;
14 Nov 95 19:10 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 SAA08066;
Tue, 14 Nov 1995 18:41:02 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
SAA28806 for rolc-out; Tue, 14 Nov 1995 18:54:31 -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 SAA28797 for
<rolc@nexen.com>; Tue, 14 Nov 1995 18:54:25 -0500
Received: from lobster.wellfleet.com (lobster.wellfleet.com [192.32.253.3]) by
nexen.nexen.com (8.6.12/8.6.12) with SMTP id SAA22686 for <rolc@nexen.com>;
Tue, 14 Nov 1995 18:51:57 -0500
Received: from pobox.BayNetworks.com (pobox.wellfleet.com) by
lobster.wellfleet.com (4.1/SMI-4.1)
id AA27802; Tue, 14 Nov 95 18:49:23 EST
Received: from andover.engeast by pobox.BayNetworks.com (4.1/SMI-4.1)
id AA13444; Tue, 14 Nov 95 18:50:25 EST
Date: Tue, 14 Nov 95 18:50:25 EST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Dimitry Haskin <dhaskin@baynetworks.com>
Message-Id: <9511142350.AA13444@pobox.BayNetworks.com>
To: yakov@cisco.com
Subject: Re: router-router NHRP
Cc: rolc@nexen.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/
Yakov, > > > > > Another case which I believe is not supported by the proposal is > > > > "third party advertisements", i.e. when an exit forwarder is not > > > > the same device as a router that acquires a route. But may be it is > > > > not an important case to support. > > > > > > Actually the proposal does support this case. So, if a border router > > > receives a BGP route (which carries NEXT_HOP information), the border > > > router may pass the next hop information (rather than its own address) > > > in response to an NHRP Request. > > > > > > > But, in this case, how would forwarders at each end of a shortcut monitor > > the viability of the route that was used for the shortcut? Since they don't > > run BGP and only have the default route in their FIBs they wouldn't see any > routing change unless they are somehow informed of such a change by the border > > BGP router which responded to the Request. The shortcut's egress forwarder > > would't be even able to associate a shortcat with a specific route since it h > as > > never seen the corresponding Request in the first place. Isn't it so? I did > n't > > see any mechanism in your proposal to handle that. > > Consider a router X within an OSPF domain, ASBR Y of that domain, and > router Z (outside of the OSPF domain) that peers with Y using BGP. Z > advertises to Y a route to some destination D, and puts its own address > as the next hop. Y injects this route into OSPF. When X originates an > NHRP Request for D, and the Request reaches Y, Y has a route to D, but > the next hop on this route is not Y, but Z. Y returns Z as the next hop > in the NHRP Reply. Since Y certainly sees any changes in this route, Y > would be able to send to X a Purge message once Y notices the changes. > Good. But there is no text in your proposal that requires a proxy router that replied with a third party address to send a Purge message to the originator of the shortcut. The proposal should be clear on that since there are certain implications of such a requirement, e.g. the amount of state that need to be saved at a proxy router, especially if such a router is a proxy for a good number of edge forwarders. Dimitry
- router-router NHRP Yakov Rekhter
- Re: router-router NHRP Andrew Smith
- Re: router-router NHRP Yakov Rekhter
- Re: router-router NHRP Andrew Smith
- Re: router-router NHRP Robert Coltun
- Re: router-router NHRP Norman W. Finn
- Re: router-router NHRP Andrew Smith
- Re: router-router NHRP Curtis Villamizar
- Re: router-router NHRP Andrew G. Malis
- Re: router-router NHRP shur
- Re: router-router NHRP Dimitry Haskin
- Re: router-router NHRP Yakov Rekhter
- Re: router-router NHRP Dimitry Haskin
- Re: router-router NHRP Yakov Rekhter
- Re: router-router NHRP Dimitry Haskin
- Re: router-router NHRP Yakov Rekhter
- Re: router-router NHRP Dimitry Haskin
- Re: router-router NHRP Yakov Rekhter
- Re: router-router NHRP Dimitry Haskin
- Re: router-router NHRP Yakov Rekhter
- Re: router-router NHRP Dimitry Haskin
- Re: router-router NHRP Yakov Rekhter
- Re: router-router NHRP Dimitry Haskin
- Re: router-router NHRP Yakov Rekhter
- Re: router-router NHRP Dimitry Haskin
- Re: router-router NHRP Yakov Rekhter
- Re: router-router NHRP Dimitry Haskin
- Re: router-router NHRP Yakov Rekhter