Re: Purge packet

shur@arch4.ho.att.com Mon, 16 October 1995 13:47 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08901; 16 Oct 95 9:47 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa08897; 16 Oct 95 9:47 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id JAA25718; Mon, 16 Oct 1995 09:21:17 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id JAA03307 for rolc-out; Mon, 16 Oct 1995 09:30:35 -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 JAA03298 for <rolc@nexen.com>; Mon, 16 Oct 1995 09:30:32 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: shur@arch4.ho.att.com
Received: from gw2.att.com (gw2.att.com [192.20.239.134]) by guelah.nexen.com (8.6.12/8.6.12) with SMTP id JAA25712 for <rolc@nexen.com>; Mon, 16 Oct 1995 09:20:52 -0400
Received: from arch4.ho.att.com by ig1.att.att.com id AA20028; Mon, 16 Oct 95 09:22:32 EDT
Received: from dahlia.ho.att.com by arch4.ho.att.com (4.1/EMS-1.2 GIS) id AA14783; Mon, 16 Oct 95 09:23:17 EDT
Received: by dahlia.ho.att.com (4.1/EMS-1.1 SunOS) id AA18375; Mon, 16 Oct 95 09:23:41 EDT
Date: Mon, 16 Oct 95 09:23:41 EDT
Message-Id: <9510161323.AA18375@dahlia.ho.att.com>
To: rolc@nexen.com, gardo@vnet.ibm.com
Subject: Re: Purge packet
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/

Russell,

> When a client supports the "Destination Prefix Extension", what
> benefit is the Request-ID in the Purge packet?  Isn't this duplicate
> information, therefore a higher risk of error.
> 
> To send the "Destination Prefix Extension" in a Purge packet,
> the server must remember whether that client supplied this extension
> in the original Request packet.  Correct?
> 
> Why not remove the Request-ID from Purge packet and add a mask field to
> the Purge packet?  I don't think it really complicates the client to
> remove the Request-ID from the Purge packet.  Will servers really need to
> check the Request-ID in Purge packet acknowledgements?
> 
> I propose that the Purge packet be changed, by removing the Request-ID
> and adding a mask field.
> 
> -- Russell
> 
I support the addition of the mask field.

David.