Re: ARP and NHRP question

Andrew Smith <asmith@baynetworks.com> Mon, 04 December 1995 22:19 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19259; 4 Dec 95 17:19 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa19255; 4 Dec 95 17:19 EST
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.98.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id QAA22941; Mon, 4 Dec 1995 16:49:39 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id RAA10554 for rolc-out; Mon, 4 Dec 1995 17:03:17 -0500
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id RAA10545 for <rolc@nexen.com>; Mon, 4 Dec 1995 17:03:14 -0500
Received: from lightning.synoptics.com (lightning.synoptics.com [134.177.3.18]) by guelah.nexen.com (8.6.12/8.6.12) with SMTP id QAA22929 for <rolc@nexen.com>; Mon, 4 Dec 1995 16:48:06 -0500
Received: from pobox.synoptics.com ([134.177.1.95]) by lightning.synoptics.com (4.1/SMI-4.1) id AA17036; Mon, 4 Dec 95 13:44:09 PST
Received: from milliways-le0.engwest (milliways-le0.synoptics.com) by pobox.synoptics.com (4.1/SMI-4.1) id AA10099; Mon, 4 Dec 95 13:36:22 PST
Received: by milliways-le0.engwest (4.1/SMI-4.1) id AA03210; Mon, 4 Dec 95 13:36:22 PST
Date: Mon, 4 Dec 95 13:36:22 PST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <asmith@baynetworks.com>
Message-Id: <9512042136.AA03210@milliways-le0.engwest>
To: laubach@terra.com21.com
Subject: Re: ARP and NHRP question
Cc: ip-atm@matmos.hpl.hp.com, rolc@nexen.com
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/

> From laubach@terra.com21.com Sat Dec  2 12:59:54 1995
> Date: Sat, 2 Dec 1995 13:11:37 -0800 (PST)
> From: Mark Laubach <laubach@terra.com21.com>
> To: Juha Heinanen <jh@lohi.dat.tele.fi>
> Cc: carlm@fore.com, asmith@BayNetworks.COM, bryang@eng.adaptec.com,
>         ip-atm@matmos.hpl.hp.com, rolc@nexen.com, carlm@fore.com
> Subject: Re: ARP and NHRP question

Mark,

> The next step of anything we do in a step-by-step
> process requires the support of existing implementations and will still
> require atmarp code in the client.  

What you propose is just one way of providing a transition plan. An equally 
valid plan would deploy multi-protocol support in the servers and only a
single protocol in the clients.

> Granted, that we decided to aim
> towards NHRP at the Danver's meeting - it is just that it takes two steps
> to get there, not one. 

It only requires one step in the clients - that is the important issue here.

> Mark

Andrew


P.S. I apologise for not attending the IETF meetings - other commitments preclude.


********************************************************************************
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
********************************************************************************