IETF Logo Mail Archive

Re: NHRP question

Eric Gray <gray@ctron.com> Mon, 16 October 1995 14:10 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09358; 16 Oct 95 10:10 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa09352; 16 Oct 95 10:10 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id JAA26026; Mon, 16 Oct 1995 09:42:00 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id JAA03672 for rolc-out; Mon, 16 Oct 1995 09:51:22 -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 JAA03663 for <rolc@nexen.com>; Mon, 16 Oct 1995 09:51:19 -0400
Received: from gatekeeper.ctron.com (ctron.com [134.141.197.25]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id JAA26022 for <rolc@nexen.com>; Mon, 16 Oct 1995 09:41:47 -0400
Received: (from news@localhost) by gatekeeper.ctron.com (8.6.12/8.6.9) id JAA22166 for <rolc@nexen.com>; Mon, 16 Oct 1995 09:48:25 -0400
Received: from stealth.ctron.com(134.141.5.107) by gatekeeper via smap (V1.3mjr) id sma022147; Mon Oct 16 09:48:02 1995
Received: from olympus.ctron.com by stealth.ctron.com (4.1/SMI-4.1) id AA26003; Mon, 16 Oct 95 09:50:54 EDT
Received: from blarney (blarney.ctron.com [134.141.66.40]) by olympus.ctron.com (8.6.12/8.6.9) with SMTP id JAA15084; Mon, 16 Oct 1995 09:38:41 -0400
Received: by blarney (931110.SGI/930416.SGI) for gardo@vnet.ibm.com id AA16656; Mon, 16 Oct 95 09:43:22 -0400
Date: Mon, 16 Oct 95 09:43:22 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Eric Gray <gray@ctron.com>
Message-Id: <9510161343.AA16656@blarney>
To: rolc@nexen.com, gardo@vnet.ibm.com
Subject: Re: NHRP question
Cc: debruin@vnet.ibm.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/

>> Folks,
>> Current NHRP spec allows for multiple next-hop IP address entries
>> in NHRP Reply. Could anyone provide some practical examples where
>> this feature would be useful ?
>> Yakov.

> Another use is multiple equal cost routes when using the "destination
> prefix extension".
> 
> I would prefer this feature (multiple next-hop entries) be moved from
> the mandatory part to the extension part (an optional extension).
> 
> -- Russell

I agree with Russell.  It would be good if each next-hop entry could be
associated with a (set of) NBMA address(es) in the reply as well.



					Eric Gray

v2.8.7 | Report a Bug | By Email