Re: Comments on NHRP spec.,, modes of deployment etc.

Bruce Cole <bcole@cisco.com> Fri, 18 August 1995 23:26 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa22256; 18 Aug 95 19:26 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa22252; 18 Aug 95 19:26 EDT
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.97.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id TAA00643; Fri, 18 Aug 1995 19:12:33 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id TAA01733 for rolc-out; Fri, 18 Aug 1995 19:12:51 -0400
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 TAA01724 for <rolc@nexen.com>; Fri, 18 Aug 1995 19:12:48 -0400
Received: from greatdane.cisco.com (greatdane.cisco.com [171.69.1.141]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id TAA00639 for <rolc@nexen.com>; Fri, 18 Aug 1995 19:10:36 -0400
Received: from cisco.com (localhost.cisco.com [127.0.0.1]) by greatdane.cisco.com (8.6.8+c/8.6.5) with ESMTP id QAA25237; Fri, 18 Aug 1995 16:10:53 -0700
Message-Id: <199508182310.QAA25237@greatdane.cisco.com>
To: Andrew Smith <asmith@baynetworks.com>
Cc: rolc@nexen.com, bcole@cisco.com
Subject: Re: Comments on NHRP spec.,, modes of deployment etc.
In-Reply-To: Your message of "Thu, 17 Aug 1995 13:51:35 PDT." <9508172051.AA20182@milliways-le0>
Date: Fri, 18 Aug 1995 16:10:52 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Bruce Cole <bcole@cisco.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 Tue Aug 15 13:49:12 1995
> > To: Grenville Armitage <gja@thumper.bellcore.com>
> > Cc: Bruce Cole <bcole@cisco.com>om>, shur@arch4.ho.att.com, rolc@nexen.com
> > Subject: Re: Comments on NHRP spec.,, modes of deployment etc. 
> > In-Reply-To: Your message of "Tue, 15 Aug 1995 10:51:27 EDT."
> >              <199508151451.KAA21047@thumper.bellcore.com> 
> > Date: Tue, 15 Aug 1995 13:28:50 -0700
> > From: Bruce Cole <bcole@cisco.com>
> 
> > (The ability
> > of 'hosts' to answer NHRP requests is still required since it was not
> > made a requirement that NHSes assume the full burden of providing
> > NHRP responses for stations that attempt to register with them).
> 
> Can anyone explain the reasoning behind this as a design choice and also
> point us to the relevent text in the document?

I do not know whether or not this was a design choice.  My reasoning was that
since the current spec does not require NHRP responses to be generated
before the packets reach end stations, one should not assume otherwise.
Remember, it was proposed that we get rid of server mode, so if stations
within the NBMA network do not exactly agree on who their neighboring NHSs
are, requests may be forwarded on to end stations which consider themselves to
only be clients.

Requiring an NHRP client to be able to answer NHRP requests of itself does
not seem unreasonable to me; ARP implementations have no problem with this.
But if the group wants to limit the complexity required in client 
implementations, then that's fine too.  Somebody please draft some text
to make this explicit.

Note that I believe Rob Coltun is drafting text to support the opposite -
where the NHRP requests can be required to go to the end stations.  This is
to better support multi-homed end stations.

> Is this yet another case where the NHRP authors are making some implicit
> assumptions without sharing them with the rest of the world so we can all
> implement the protocol too?

I'm sure that's not the intent, and I honestly don't know what other
cases you're eluding too.  Much of the text of the current draft has
simply evolved, perhaps at the expense of clarity.  Maybe you could submit
some clarifying text?