Re: ARP and NHRP question

James Watt <james@ca.newbridge.com> Tue, 28 November 1995 17:03 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20319; 28 Nov 95 12:03 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa20315; 28 Nov 95 12:03 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 LAA16504; Tue, 28 Nov 1995 11:29:04 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id LAA12528 for rolc-out; Tue, 28 Nov 1995 11:42: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 LAA12519 for <rolc@nexen.com>; Tue, 28 Nov 1995 11:42:53 -0500
Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id LAA16496 for <rolc@nexen.com>; Tue, 28 Nov 1995 11:28:32 -0500
Received: (from adm@localhost) by ns.newbridge.com (8.6.12/8.6.12) id LAA28433; Tue, 28 Nov 1995 11:39:34 -0500
Received: from portero(192.75.23.66) by ns via smap (V1.3) id sma028374; Tue Nov 28 11:39:04 1995
Received: from thor.ca.newbridge.com (thor121.ca.newbridge.com [138.120.121.43]) by kanmaster.ca.newbridge.com (8.6.12/8.6.12) with ESMTP id LAA06599; Tue, 28 Nov 1995 11:39:03 -0500
Received: from fields.newbridge (fields.ca.newbridge.com [138.120.144.160]) by thor.ca.newbridge.com (8.6.12/8.6.12) with SMTP id LAA24947; Tue, 28 Nov 1995 11:39:02 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: James Watt <james@ca.newbridge.com>
Message-Id: <199511281639.LAA24947@thor.ca.newbridge.com>
Subject: Re: ARP and NHRP question
To: Tim Salo <salo@msc.edu>
Date: Tue, 28 Nov 1995 11:38:59 -0500 (EST)
Cc: james@ca.newbridge.com, ip-atm@matmos.hpl.hp.com, rolc@nexen.com
In-Reply-To: <199511272339.RAA15099@uh.msc.edu> from "Tim Salo" at Nov 27, 95 05:39:08 pm
X-Mailer: ELM [version 2.4 PL22]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 2069
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/

Tim Salo writes:

+----------
|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?
+--------
My thinking was that the former turned into the latter when the last of
the ATMARP clients went away - I didn't really think about the distinction.

From my point of view the end game is definitely the latter case.  When
thinking about how to get from today to there, I had got myself solidly
stuck in backwards compatibility think. Thus I assumed we needed to support
ATMARP at least for a transition period.

But that was just my view of how to deal with the transition.  I think
the key _behavioural_ question is:

    Does an NHRP client have to be an ATMARP client to have shortcuts
    to intra-LIS destinations ?

My vote is NO !! There are two implications:

1)  The NHRP server _must_ have "an interface" to the ATMARP service for
    information interchange and

2) When there is no ATMARP left, the NHRP servers will need a co-ordination
   mechanism (as Andrew pointed out) - however as long as there is ATMARP left
   we can use the ATMARP service to do the co-ordination required for 
   intra-LIS support.

Currently the spec says (Section 2.2 para 3):
     'In addition to NHRP, NHSs ... may support "classical" ARP
      service as well.'

It goes on to say (para 4):
     'This table can be constructed ... through mechanisms outside the
      scope of this document (examples of such mechanisms include ARP...'

It would seem we need to adjust this to reflect point (1) above.

Comments ?
-james
____________________________________________________________________________
James W. Watt,     james@newbridge.com                   Ph: +1 613 591-3600
Newbridge Networks 600 March Rd Kanata ON Canada K2K 2E6 FAX:+1 613 591-3680