Re: ARP and NHRP question

Tim Salo <salo@msc.edu> Mon, 27 November 1995 23:56 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04264; 27 Nov 95 18:56 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa04260; 27 Nov 95 18:56 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 SAA12715; Mon, 27 Nov 1995 18:27:49 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id SAA05038 for rolc-out; Mon, 27 Nov 1995 18:41:55 -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 SAA05028 for <rolc@nexen.com>; Mon, 27 Nov 1995 18:41:52 -0500
Received: from noc.msc.edu (noc.msc.edu [137.66.12.254]) by guelah.nexen.com (8.6.12/8.6.12) with SMTP id SAA12707 for <rolc@nexen.com>; Mon, 27 Nov 1995 18:27:36 -0500
Received: from uh.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324)) id AA06180; Mon, 27 Nov 95 17:39:09 -0600
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tim Salo <salo@msc.edu>
Received: (salo@localhost) by uh.msc.edu (8.7.1/8.6.6) id RAA15099; Mon, 27 Nov 1995 17:39:08 -0600 (CST)
Date: Mon, 27 Nov 1995 17:39:08 -0600 (CST)
Message-Id: <199511272339.RAA15099@uh.msc.edu>
To: james@ca.newbridge.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: James Watt <james@ca.newbridge.com>
> Subject: Re: ARP and NHRP question
> To: gray@ctron.com (Eric W. Gray)
> Date: Mon, 27 Nov 1995 17:04:02 -0500 (EST)
> Cc: salo@msc.edu, ip-atm@matmos.hpl.hp.com, rolc@nexen.com
> 
> Eric W. Gray writes:
> +------------
> |Here's where I get confused; if you really want the server to be the complex
> |one and the client to always use one protocol, then don't you want the NHRP
> |server to do the ATMARP (on behalf of the client) so that it can return an
> |answer using NHRP?
> +----------
> Yes, although it would probably be more simple for the NHRP server to _be_
> the ATMARP server...

I still don't understand.

Are you saying that an NHRP server and an ATMARP server should co-reside,
perhaps even share a common database, but support two protocols for
resolving IP addresses into ATM addresses?

Or, should the "NHRP server be the ATMARP server" in the sense that
the server and clients support only one protocol for resolving IP
addresses into ATM addresses, namely the NHPR protocol?

By the way, I prefer the latter solution: migrate to using the NHRP
protocol (or any other other _single_ protocol that works, for that
matter) for resolving both intra-LIS and inter-LIS IP addresses.

-tjs