Re: router-router NHRP

"Andrew G. Malis" <malis@nexen.com> Mon, 07 August 1995 12:46 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id ab08471; 7 Aug 95 8:46 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa08467; 7 Aug 95 8:46 EDT
Received: from maelstrom.acton.timeplex.com (maelstrom.nexen.com [204.249.97.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id IAA18142; Mon, 7 Aug 1995 08:32:09 -0400
Received: (from root@localhost) by maelstrom.acton.timeplex.com (8.6.12/8.6.12) id IAA15470 for rolc-out; Mon, 7 Aug 1995 08:23:59 -0400
Received: from phish.acton.timeplex.com (phish.acton.timeplex.com [134.196.22.130]) by maelstrom.acton.timeplex.com (8.6.12/8.6.12) with ESMTP id IAA15461; Mon, 7 Aug 1995 08:23:56 -0400
Received: from localhost (malis@localhost) by phish.acton.timeplex.com (8.6.12/8.6.12) with SMTP id IAA14167; Mon, 7 Aug 1995 08:23:54 -0400
Message-Id: <199508071223.IAA14167@phish.acton.timeplex.com>
To: curtis@ans.net
cc: Andrew Smith <asmith@baynetworks.com>, yakov@cisco.com, rolc@nexen.com, nfinn@cisco.com, malis@nexen.com
Subject: Re: router-router NHRP
In-reply-to: Your message of "Thu, 03 Aug 1995 17:59:30 EDT." <199508032159.RAA07332@brookfield.ans.net>
Date: Mon, 07 Aug 1995 08:23:53 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Andrew G. Malis" <malis@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/

Curtis,

> The whole point is that NHRP is completely inadequate for a) unless
> the tolopogy is constrained such that their is little or no redundant
> connectivity to destinations off the NBMA, which some of us consider a
> very uninteresting case and very unlikely for a large deployment (what
> ROLC originally set out to target).  Somewhere we've lost the
> connection between the requirements that this WG set out to meet and
> the work output.

I couldn't let this go unanswered.  The current rev of NHRP is useful
when either the the source or destination host is an NBMA-attached
host, or is one hop away from the NBMA.  This covers a LOT of cases,
in fact most ATM deployments until we start to see the "ubiquitous ATM
infrastructure".

I agree it doesn't cover the full range of what you term "interesting"
cases, and I also agree that it's important to complete the work.  At
the Stockholm meeting, and again via the minutes following the
meeting, I solicited I-Ds for the Dallas meeting on how to handle the
full range of cases.  I know of at least one such draft in progress,
from Yakov and Bruce, and I had a hallway conversation concerning
another possible draft on the subject.  If you aren't happy with the
current work output, PLEASE submit a draft yourself, or contribute to
the draft(s) in progress, so we can get this done.

Thanks,
Andy
__________________________________________________________________________
Andrew G. Malis   Ascom Nexion                      voice: +1 508 266-4522
malis@nexen.com   289 Great Rd., Acton MA 01720 USA   FAX: +1 508 266-2300