Re: NHRP protocol modifications and clarifications

Andrew Smith <asmith@baynetworks.com> Fri, 07 July 1995 20:55 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14947; 7 Jul 95 16:55 EDT
Received: from [204.249.96.18] by IETF.CNRI.Reston.VA.US id aa14943; 7 Jul 95 16:55 EDT
Received: from maelstrom.acton.timeplex.com (maelstrom.nexen.com [204.249.97.5]) by nexen.nexen.com (8.6.12/8.6.12) with ESMTP id QAA07291; Fri, 7 Jul 1995 16:40:10 -0400
Received: (from root@localhost) by maelstrom.acton.timeplex.com (8.6.12/8.6.12) id QAA28790 for rolc-out; Fri, 7 Jul 1995 16:35:40 -0400
Received: from nexen.nexen.com ([204.249.96.18]) by maelstrom.acton.timeplex.com (8.6.12/8.6.12) with ESMTP id QAA28781 for <rolc@nexen.com>; Fri, 7 Jul 1995 16:35:36 -0400
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 QAA07215 for <rolc@nexen.com>; Fri, 7 Jul 1995 16:35:35 -0400
Received: from BayNetworks.COM ([134.177.1.95]) by lightning.synoptics.com (4.1/SMI-4.1) id AA15637; Fri, 7 Jul 95 13:32:02 PDT
Received: from milliways-le0 (milliways-le0.synoptics.com) by BayNetworks.COM (4.1/SMI-4.1) id AA22228; Fri, 7 Jul 95 13:33:03 PDT
Received: by milliways-le0 (4.1/2.0N) id AA09757; Fri, 7 Jul 95 13:35:06 PDT
Message-Id: <9507072035.AA09757@milliways-le0>
Date: Fri, 7 Jul 95 13:35:06 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <asmith@baynetworks.com>
To: bcole@cisco.com
Subject: Re: NHRP protocol modifications and clarifications
Cc: 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 owner-rolc@nexen.com Fri Jul  7 12:56:48 1995
> To: James Luciani <luciani@nexen.com>
> Cc: Bruce Cole <bcole@cisco.com>om>, rolc@nexen.com, bcole@cisco.com
> Subject: Re: NHRP protocol modifications and clarifications 
> Date: Fri, 07 Jul 1995 12:33:45 -0700
> From: Bruce Cole <bcole@cisco.com>

Bruce,

> > What about the case when you have 2 or more NHCs which are co-resident with 
> > their NHS?  You can't figure out for whom the packet was sent in this case 
> > without burdening all NHCs to check to their database.
> 
> I don't think I understand the need for multiple distinct clients in an NBMA
> station (where the clients share the same IP address and interface).

There is an important analogy here with LANE: LANE allows a client to use 
multiple ATM addresses to represent the same MAC destination (for very good 
implementation reasons which I won't go into now - ask Norm). This works because
the server is neither allowed nor required to cache these bindings and answer
queries on behalf of the client. NHRP uses a different model: the server must
caches all bindings and the client never gets to respond to any queries.
However, NHRP also precludes multiple clients from registering as the same
IP address: therefore NHRP cannot support an implementation which would
prefer to use multiple separate incoming VCCs into the same IP destination.

This is a non-feature, not a bug, and it does complicate some implementations.
 
> I would clarify "own identify".  For the purposes of this section, I believe
> it means the set of IP addresses and NBMA addresses assigned to the NHS
> station itself.

I would also add the clarification that these are all 1:1 mappings and that all
IP and ATM addresses are unique across the whole cloud.


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