IETF Logo Mail Archive

Re: Latest NHRP draft

Bruce Cole <bcole@cisco.com> Thu, 11 May 1995 04:52 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24447; 11 May 95 0:52 EDT
Received: from maelstrom.acton.timeplex.com by IETF.CNRI.Reston.VA.US id aa24443; 11 May 95 0:52 EDT
Received: (from root@localhost) by maelstrom.acton.timeplex.com (8.6.9/ACTON-MAIN-1.2) id AAA04392 for rolc-out; Thu, 11 May 1995 00:48:15 -0400
Received: from greatdane.cisco.com (greatdane.cisco.com [171.69.1.141]) by maelstrom.acton.timeplex.com (8.6.9/ACTON-MAIN-1.2) with ESMTP id AAA04381 for <rolc@maelstrom.Timeplex.COM>; Thu, 11 May 1995 00:48:09 -0400
Received: from cisco.com (localhost.cisco.com [127.0.0.1]) by greatdane.cisco.com (8.6.8+c/8.6.5) with ESMTP id VAA02593; Wed, 10 May 1995 21:47:59 -0700
Message-Id: <199505110447.VAA02593@greatdane.cisco.com>
To: "Robert G. Cole" <rgc@qsun.att.com>
Cc: Bruce Cole <bcole@cisco.com>, Robert.G.Cole@att.com, Dave Katz <dkatz@cisco.com>, rolc@maelstrom.timeplex.com
Subject: Re: Latest NHRP draft
In-Reply-To: Your message of "Wed, 10 May 1995 22:18:15 EDT." <rgc.1150546335C@hogpa.ho.att.com>
Date: Wed, 10 May 1995 21:47:59 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Bruce Cole <bcole@cisco.com>
X-Orig-Sender: owner-rolc@maelstrom.timeplex.com
Precedence: bulk
X-Info: Submissions to rolc@maelstrom.timeplex.com
X-Info: [Un]Subscribe requests to rolc-request@maelstrom.timeplex.com
X-Info: Archives for rolc via ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/

> >You are missing: rate limiting.  Routers B & C need not transmit multiple
> >NHRP request packets.  They can drop NHRP packets which exceed whatever your
> >desired rate is.
> >
> >The benefit of option (c) is that your IP traffic is not delayed until
> >address resolution (or worse - VC establishment) has completed.
> >
> 
> What I was asking was if, by router A forwarding the initial IP packet 
> (that initiated the first NHRP request) to the transit router B, 
> could this also trigger router B to initiate another NHRP request?

I was answering that yes this could happen, but rate limiting of NHRP
traffic could still cause router D to only receive 1 request.

v2.8.7 | Report a Bug | By Email