Re: Latest NHRP draft
Bruce Cole <bcole@cisco.com> Wed, 10 May 1995 18:20 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08784;
10 May 95 14:20 EDT
Received: from maelstrom.acton.timeplex.com by IETF.CNRI.Reston.VA.US
id aa08780; 10 May 95 14:20 EDT
Received: (from root@localhost) by maelstrom.acton.timeplex.com
(8.6.9/ACTON-MAIN-1.2) id OAA24702 for rolc-out;
Wed, 10 May 1995 14:15:41 -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 OAA24684
for <rolc@maelstrom.Timeplex.COM>; Wed, 10 May 1995 14:15:34 -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 LAA02457;
Wed, 10 May 1995 11:15:28 -0700
Message-Id: <199505101815.LAA02457@greatdane.cisco.com>
To: Robert.G.Cole@att.com
Cc: Dave Katz <dkatz@cisco.com>, rolc@maelstrom.timeplex.com
Subject: Re: Latest NHRP draft
In-Reply-To: Your message of "Wed, 10 May 1995 09:31:17 EDT."
<rgc.1150500317A@hogpa.ho.att.com>
Date: Wed, 10 May 1995 11:15:28 -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/
> If the normal routed path over the NBMA travels thru routers A, B, C and D, > where routers B and C are transit routers, wouldn't this lead to > the generation of three seperate "short cut" link layer connections (in the > case of a connection-oriented NBMA like ATM) for the same packet? > For example, > - router A receives a packet and determines that it is to be forwarded > to its NBMA interface. it sends a NHRP request and forwards > the packet to router B, > - router B receives a packet and determines that it is to be forwarded > to its NBMA interface. it sends a NHRP request and forwards > the packet to router C, etc > - once the NHRP replies return to routers A, B and C, they each establish > their own "short cut" connections to D. > > If this is indeed the case, then option (c) above should be removed in favor > of one of the remaining two. Am I missing out on something? 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.
- 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