nhrp-05
gardo@vnet.ibm.com Tue, 07 November 1995 17:21 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15480;
7 Nov 95 12:21 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa15476;
7 Nov 95 12:21 EST
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.99.5]) by
guelah.nexen.com (8.6.12/8.6.12) with ESMTP id MAA27457 for
<ietf-archive@ietf.cnri.reston.va.us>; Tue, 7 Nov 1995 12:09:20 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
LAA06820 for rolc-out; Tue, 7 Nov 1995 11:57:48 -0500
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 LAA06804 for
<rolc@nexen.com>; Tue, 7 Nov 1995 11:57:45 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: gardo@vnet.ibm.com
Received: from VNET.IBM.COM (vnet.ibm.com [199.171.26.4]) by guelah.nexen.com
(8.6.12/8.6.12) with SMTP id LAA27171 for <rolc@nexen.com>;
Tue, 7 Nov 1995 11:43:49 -0500
Message-Id: <199511071643.LAA27171@guelah.nexen.com>
Received: from RALVM29 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 2173;
Tue, 07 Nov 95 11:51:08 EST
Date: Tue, 7 Nov 95 11:51:00 EST
To: horton@citr.uq.oz.au
cc: rolc@nexen.com, genecox@vnet.ibm.com
Subject: nhrp-05
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/
Ref: Your note of Tue, 07 Nov 95 02:56:50 -0500
David, >>6. Proposal to add prefix mask to purge packet >A prefix mask extension sounds reasonable, though it may >complicate client implementations to always act on it. >If the purge acknowledge set the mask to be what was actually >purged, then the NHS revert to entry by entry if needed. I don't see how a mask in the Purge would really complicate client implementations. Are there implementations that do not have access to all cache entries? However, if NHRP clients are not required to support the mask in a Purge, then I prefer a client's support of the purge-mask be communicated during the Request/Reply exchange, in a separate PURGE-MASK EXTENSION that is non-discretionary (this would be a new extension). I like this better than using the ack because it makes the purge more reliable on the first Purge packet because the server knows which clients support the purge mask before sending a Purge, instead of learning afterwards... Have a nice day! -- Russell
- Re: nhrp-05 David Horton
- nhrp-05 gardo