IETF Logo Mail Archive

Re: ARP and NHRP question

Mark Laubach <laubach@terra.com21.com> Tue, 28 November 1995 02:14 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06615; 27 Nov 95 21:14 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa06609; 27 Nov 95 21:14 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 UAA13451; Mon, 27 Nov 1995 20:42:43 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id UAA06209 for rolc-out; Mon, 27 Nov 1995 20:55:38 -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 UAA06200 for <rolc@nexen.com>; Mon, 27 Nov 1995 20:55:35 -0500
Received: from terra.com21.com (terra.com21.com [140.174.223.21]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id UAA13447 for <rolc@nexen.com>; Mon, 27 Nov 1995 20:41:19 -0500
Received: (laubach@localhost) by terra.com21.com (8.6.10/8.6.5) id SAA25875; Mon, 27 Nov 1995 18:14:23 -0800
Date: Mon, 27 Nov 1995 18:14:22 -0800 (PST)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mark Laubach <laubach@terra.com21.com>
To: Grenville Armitage <gja@thumper.bellcore.com>
cc: ip-atm@matmos.hpl.hp.com, rolc@nexen.com, gja@thumper.bellcore.com
Subject: Re: ARP and NHRP question
In-Reply-To: <199511280030.TAA16559@thumper.bellcore.com>
Message-ID: <Pine.BSI.3.91.951127180852.11110c-100000@terra.com21.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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/

> Is there a 'gotcha' in the client registration aspect that I've
> forgotten?

I dunno, let's mull it over and make sure the bases are covered.

I seem to remember from conversations with Andy, that we concluded that
the best way to migrate to an NHS and to co-mingle information is for an
NHS to export both an NHRP service interface and an ATMARP service
interface.  This of this approach as a stepwise implementation plan. NHRP
has no credibility ("been out there" experience data) at this point in
time and it needs to be built.  Only after NHRP gets established in the
community, can the ATMARP service interface dwindle as appropriate for
each LIS. 

Mark

v2.8.7 | Report a Bug | By Email