Re: Final ROLC minutes from Stockholm

"Andrew G. Malis" <malis@nexen.com> Fri, 11 August 1995 12:36 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09226; 11 Aug 95 8:36 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa09222; 11 Aug 95 8:36 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 IAA14394; Fri, 11 Aug 1995 08:22:34 -0400
Received: (from root@localhost) by maelstrom.acton.timeplex.com (8.6.12/8.6.12) id IAA26140 for rolc-out; Fri, 11 Aug 1995 08:16:03 -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 IAA26131; Fri, 11 Aug 1995 08:15:59 -0400
Received: from localhost (malis@localhost) by phish.acton.timeplex.com (8.6.12/8.6.12) with SMTP id IAA26947; Fri, 11 Aug 1995 08:15:56 -0400
Message-Id: <199508111215.IAA26947@phish.acton.timeplex.com>
To: shur@arch4.ho.att.com
cc: rolc@nexen.com, malis@nexen.com, malis@nexen.com
Subject: Re: Final ROLC minutes from Stockholm
In-reply-to: Your message of "Thu, 10 Aug 1995 17:48:58 EDT." <9508102148.AA00296@dahlia.ho.att.com>
Date: Fri, 11 Aug 1995 08:15:56 -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/

David,

> > From the ROLC minutes
> > 2. Include destination address in Purge requests - agreed.
>
> Could someone clarify - which destination address is this? Is it the
> target of the original NHRP query?

Yup.  The issue is that for the Purge message, draft -04 requires the
use of the Request ID field as the key to search the cache, and this
is the only use of this field as a search key - all other cache
lookups are keyed off the destination address in the original NHRP
query.  To make the Purge consistent with other NHRP messages, and
only require one cache search key, it will now have the exact same
syntax as the Request and Reply packets - Request ID, Dest. Addr,
Source Addr.

> If so, it might be useful to also allow the network address
> associated with an off-NBMA target to also be included in Purge
> requests.

Could you elucidate?  If by "network address" you mean the destination
IP or other network layer address, it's already there.  If you mean
the NBMA address, why would you want to include it?  The whole point
of the message is to cause cache entries to be removed.

Cheers,
Andy