Re: Latest NHRP draft
dhc2@gte.com Thu, 25 May 1995 20:47 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08175;
25 May 95 16:47 EDT
Received: from maelstrom.acton.timeplex.com by IETF.CNRI.Reston.VA.US
id aa08171; 25 May 95 16:47 EDT
Received: (from root@localhost) by maelstrom.acton.timeplex.com
(8.6.12/ACTON-MAIN-1.2) id QAA01198 for rolc-out;
Thu, 25 May 1995 16:25:54 -0400
Received: from ns.gte.com (ns.gte.com [132.197.8.9]) by
maelstrom.acton.timeplex.com (8.6.12/ACTON-MAIN-1.2) with ESMTP id QAA01190
for <rolc@maelstrom.Timeplex.COM>; Thu, 25 May 1995 16:25:50 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: dhc2@gte.com
Received: from minuteman.gte.com by ns.gte.com (8.6.10/8.6.10)
id QAA14728; Thu, 25 May 1995 16:25:43 -0400
Received: by minuteman.gte.com (5.0/SMI-SVR4)
id AA04417; Thu, 25 May 1995 16:29:05 -0400
Date: Thu, 25 May 1995 16:29:05 -0400
Message-Id: <9505252029.AA04417@minuteman.gte.com>
To: bcole@cisco.com
Cc: Robert.G.Cole@att.com, dkatz@cisco.com, rolc@maelstrom.timeplex.com
Subject: Re: Latest NHRP draft
Content-Length: 1168
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/
Bruce, Can you elaborate on how rate limiting would prevent multiple VCs from occuring when the NHRP request goes through multiple NHSs towards its destination. Does this method guarantee that multiple VCs will not occur? Can you provide more explicit justification for this? If the source has multiple NHRP requests within a short period of time, would rate limiting affect the subsequent requests? Thanks, Derya ------------------------------------------------------------------------ > >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.
- Latest NHRP draft Dave Katz
- Re: Latest NHRP draft Andrew Smith
- Re: Latest NHRP draft Robert G. Cole
- Re: Latest NHRP draft Bruce Cole
- Re: Latest NHRP draft Curtis Villamizar
- Re: Latest NHRP draft Robert G. Cole
- Re: Latest NHRP draft Bruce Cole
- Re: Latest NHRP draft Robert G. Cole
- Re: Latest NHRP draft Curtis Villamizar
- Re: Latest NHRP draft dhc2
- Re: Latest NHRP draft Bruce Cole