Re: NHRP + LIS awareness
Andrew Smith <asmith@baynetworks.com> Thu, 16 November 1995 02:57 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27815;
15 Nov 95 21:57 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa27811;
15 Nov 95 21:57 EST
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.99.5]) by
guelah.nexen.com (8.6.12/8.6.12) with ESMTP id VAA16480;
Wed, 15 Nov 1995 21:27:11 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
VAA18532 for rolc-out; Wed, 15 Nov 1995 21:40:47 -0500
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by
maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id VAA18523 for
<rolc@nexen.com>; Wed, 15 Nov 1995 21:40:44 -0500
Received: from lightning.synoptics.com (lightning.synoptics.com
[134.177.3.18]) by nexen.nexen.com (8.6.12/8.6.12) with SMTP id VAA18922 for
<rolc@nexen.com>; Wed, 15 Nov 1995 21:38:10 -0500
Received: from pobox.synoptics.com ([134.177.1.95]) by lightning.synoptics.com
(4.1/SMI-4.1) id AA22707; Wed, 15 Nov 95 18:34:43 PST
Received: from milliways-le0.engwest (milliways-le0.synoptics.com) by
pobox.synoptics.com (4.1/SMI-4.1)
id AA04154; Wed, 15 Nov 95 18:36:07 PST
Received: by milliways-le0.engwest (4.1/SMI-4.1)
id AA00704; Wed, 15 Nov 95 18:36:06 PST
Date: Wed, 15 Nov 95 18:36:06 PST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <asmith@baynetworks.com>
Message-Id: <9511160236.AA00704@milliways-le0.engwest>
To: rolc@nexen.com, bryang@eng.adaptec.com
Subject: Re: NHRP + LIS awareness
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 owner-rolc@nexen.com Wed Nov 15 18:19:07 1995 > Date: Wed, 15 Nov 95 18:00:43 PST > From: bryang@eng.adaptec.com (Bryan Gleeson) > To: rolc@nexen.com > Subject: NHRP + LIS awareness Bryan, > Also let's assume that host station S is aware of its own > LIS / subnet. It would thus seem possible to use NHRP for both > intra-LIS and inter-LIS transfer without the host necessarily > having a netmask of all 1s, and the consequent undesirable > proliferation of host routes in the network. Routers would > be able to do address aggregation, and NHRP could be used > as a perfectly good intra-LIS address resolution protocol. > Are there problems with any of this ? Yes, NHRP always was a fine address resolution protocol. Of course you would have problems resolving IP/LANE hosts that way but I guess the NHS could do a translation somehow, assuming it had a co-located LES and BUS (although I've just remembered this is the wrong list for that discussion, sorry). The only proliferation of host routes that you get is the registrations from clients to NHS but those were there anyway. Presumably the NHS was doing aggregation and advertising prefix rather than per-host reachability into a routing protocol anyway. Presumably this makes the NHS a superset of 1577 ATM-ARP Server functionality, no? > > Regards, > Bryan Gleeson > Adaptec. > 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 ********************************************************************************
- NHRP + LIS awareness Bryan Gleeson
- Re: NHRP + LIS awareness Andrew Smith
- Re: NHRP + LIS awareness Bruce Cole