The Routing Over Large Clouds Mailing List Archive by date

Cell Relay Retreat>List Archive>month:1995-Nov> msg00157



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

ARP and NHRP question

  • From: Andrew Smith <asmith@baynetworks.com>
  • Date: Mon, 27 Nov 95 18:07:26 PST
  • Cc: ip-atm@matmos.hpl.hp.com, rolc@nexen.com
  • X-Orig-Sender: owner-rolc@nexen.com

> From atmpost@matmos.hpl.hp.com Mon Nov 27 17:23:12 1995
> To: Yakov Rekhter <yakov@cisco.com>
> Cc: curtis@ans.net, ip-atm@matmos.hpl.hp.com
> Reply-To: curtis@ans.net
> Subject: Re: ARP and NHRP question 
> In-Reply-To: Your message of "Wed, 22 Nov 1995 14:55:59 PST."
>              <199511222255.OAA05406@hubbub.cisco.com> 
> Date: Mon, 27 Nov 1995 19:44:30 -0500
> From: Curtis Villamizar <curtis@ans.net>

Curtis,

> If you restrict NHRP to act only within a LIS and only responding for
> things on the LIS, you have about the same as RFC1577 ATM ARP.  You
> lose the robust server redundancy built into RFC1577++.

I would suggest that NHRP will need to merge in some server redundancy 
capabilities pretty fast if it is to be useful. I'm not sure that 
1577++ is the right model to pick long-term though: that merely pushes 
the problem down to the clients without a mechanism to manage the information 
that each client stores (this gets back to the configuration server issues of
a seperate thread).

> Curtis
> 

Andrew


********************************************************************************
Andrew Smith					TEL:	+1 408 764 1574
Technology Synergy Unit				FAX:	+1 408 988 5525
Bay Networks, Inc.				E-m:	asmith@baynetworks.com
Santa Clara, CA
********************************************************************************