Re: Latest NHRP draft
Curtis Villamizar <curtis@ans.net> Wed, 10 May 1995 18:49 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09348;
10 May 95 14:49 EDT
Received: from maelstrom.acton.timeplex.com by IETF.CNRI.Reston.VA.US
id aa09344; 10 May 95 14:49 EDT
Received: (from root@localhost) by maelstrom.acton.timeplex.com
(8.6.9/ACTON-MAIN-1.2) id OAA25394 for rolc-out;
Wed, 10 May 1995 14:44:58 -0400
Received: from curtis.ansremote.com (curtis.ansremote.com [152.161.2.3]) by
maelstrom.acton.timeplex.com (8.6.9/ACTON-MAIN-1.2) with ESMTP id OAA25386
for <rolc@maelstrom.timeplex.com>; Wed, 10 May 1995 14:44:47 -0400
Received: from curtis.ansremote.com (localhost [127.0.0.1]) by
curtis.ansremote.com (8.6.9/8.6.9) with ESMTP id OAA04022;
Wed, 10 May 1995 14:21:58 -0400
Message-Id: <199505101821.OAA04022@curtis.ansremote.com>
To: Robert.G.Cole@att.com
cc: Dave Katz <dkatz@cisco.com>, rolc@maelstrom.timeplex.com
Reply-To: curtis@ans.net
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 14:20:57 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Curtis Villamizar <curtis@ans.net>
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/
In message <rgc.1150500317A@hogpa.ho.att.com>om>, "Robert G. Cole" writes: > Dave, > > Re: the NHRP draft, it reads: > > > If the NHRP request is triggered by a data packet, station S may > > choose to dispose of the data packet while awaiting an NHRP reply in > > one of the following ways: > > > > (a) Drop the packet > > (b) Retain the packet until the reply arrives and a more optimal > > path is available > > (c) Forward the packet along the routed path toward D > > > > The choice of which of the above to perform is a local policy matter, > > though option (c) is the recommended default, since it may allow data > > to flow to the destination while the NBMA address is being resolved. > > Note that an NHRP request for a given destination MUST NOT be > > triggered on every packet, though periodically retrying a request is > > permitted. > > 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? > > Thanks, > > Bob Cole > > > Robert G. Cole > AT&T Business Multimedia Services, Technical Marketing > rgc@qsun.att.com +1 908 949 1950 (voice) > attmail!rgcole +1 908 949 8887 (fax) > > AT&T Bell Laboratories > Room 3L-533 > 101 Crawfords Corner Road > Holmdel, NJ 07733-3030 > USA Bob, Major transit routers today are seeing on the order of 10,000 unique destination addresses over short periods of time (90 second sampling). If a transit router does not wish to support 10,000 VC (keeping in mind that the entire VCI space is 64K), then it would probably be configured to forward packets hop by hop only. I don't think deleting option (c) is needed. This is a usage issue more than anything. Curtis ps- In data I took a year ago we saw 7,800 dests at 6 kpps over 90 seconds, if I remeber correctly. This was single interface on one router. Only a few samples were taken, at different routers, and the range was about 4,000 to 7,800. This is all from memory, but I've been asked about this enough times that I'm fairly sure the 7,800 figure is accurate. Traffic has more than doubled since then.
- 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