Re: nhrp-05 ????? - Destination Prefix Extension

debruin@raleigh.ibm.com Thu, 02 November 1995 22:30 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24261; 2 Nov 95 17:30 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa24253; 2 Nov 95 17:30 EST
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id RAA05904; Thu, 2 Nov 1995 17:01:29 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id RAA12907 for rolc-out; Thu, 2 Nov 1995 17:08:56 -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 RAA12895 for <rolc@nexen.com>; Thu, 2 Nov 1995 17:08:53 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: debruin@raleigh.ibm.com
Received: from intgate.raleigh.ibm.com (intgate.raleigh.ibm.com [192.35.236.9]) by guelah.nexen.com (8.6.12/8.6.12) with SMTP id PAA05323 for <rolc@nexen.com>; Thu, 2 Nov 1995 15:38:42 -0500
Received: from netmail.raleigh.ibm.com by intgate.raleigh.ibm.com (AIX 3.2/UCB 5.64/RTP-FW1.0) id AA81413; Thu, 2 Nov 1995 15:48:09 -0500
Received: from debruin.raleigh.ibm.com (debruin.raleigh.ibm.com [9.67.205.231]) by netmail.raleigh.ibm.com (8.6.12/RTP-ral-1.0) with SMTP id PAA13957; Thu, 2 Nov 1995 15:47:44 -0500
Received: by debruin.raleigh.ibm.com (AIX 3.2/UCB 5.64/4.03) id AA14789; Thu, 2 Nov 1995 15:47:15 -0500
Date: Thu, 2 Nov 1995 15:47:15 -0500
Message-Id: <9511022047.AA14789@debruin.raleigh.ibm.com>
To: asmith@baynetworks.com, rolc@nexen.com
Subject: Re: nhrp-05 ????? - Destination Prefix Extension
Cc: gardo@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/

> > From owner-rolc@nexen.com Wed Nov  1 13:55:17 1995
> > From: gardo@vnet.ibm.com
> > Date: Wed, 01 Nov 95 16:33:12 EST  
> > To: bcole@cisco.com, genecox@vnet.ibm.com, rolc@nexen.com
> > Subject: Re: nhrp-05 ????? - Destination Prefix Extension
> > From: Russell.Gardo@nexen.com
> 
> Russell,
>                          
> > >>> "when the Request ID is zero filled the match is made                      
> > >>> based only on the Destination Address"...                                  
> > >>> I believe Andrew has already made this point in an earlier posting.        
> >                                                                                
> > I assume that once the missing paragraph is added, a server should be          
> > able to purge by setting the request-id to zero if it chooses to purge         
> > without using the request-id.                                                  
> 
> Again, to avoid having options and useless checks in the code, just 
> specify that the request-id field in a Purge has no meaning to a receiver.
> No protocol functionality is lost by this simplification and interoperability
> will be enhanced.
> 

If we declare that it has no meaning to a receiver in a Purge message, why 
should we keep it in the Purge message at all?  If nothing is lost, I say 
yank it out and be done with it.


>
> Andrew

- Chris