ACK of purge packets

gardo@vnet.ibm.com Thu, 16 November 1995 14:09 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10792; 16 Nov 95 9:09 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa10788; 16 Nov 95 9:09 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 IAA17733; Thu, 16 Nov 1995 08:39:17 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id IAA22420 for rolc-out; Thu, 16 Nov 1995 08:51:04 -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 IAA22411; Thu, 16 Nov 1995 08:51:01 -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 IAA17689; Thu, 16 Nov 1995 08:35:36 -0500
Message-Id: <199511161335.IAA17689@guelah.nexen.com>
Received: from RALVM29 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 9436; Thu, 16 Nov 95 08:44:07 EST
Date: Thu, 16 Nov 95 08:35:12 EST
To: gray@ctron.com, luciani@nexen.com
cc: rolc@nexen.com, genecox@vnet.ibm.com
Subject: ACK of purge packets
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, 14 Nov 1995 18:21:33 -0500

Eric/Jim,

>>>  I think that you missed the point (maybe?); because of the scenario
>>>  in which a purge is not sent as a result of a component failure
>>>  (crash), a "reliable purge" is an unattainable goal.  This reduces
>>>  the purge protocol to the status of "optimization" and it no longer
>>>  makes sense to require purge originators to repeat purge messages
>>>  until they are acknowledged.

Is there a need or requirement that some clients not participate in
the purge portion of NHRP?

-- Russell