Re: nhrp-05 - Purge packets
Andrew Smith <asmith@baynetworks.com> Thu, 02 November 1995 20:26 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20916;
2 Nov 95 15:26 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa20911;
2 Nov 95 15:26 EST
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com
(8.6.12/8.6.12) with ESMTP id OAA04886; Thu, 2 Nov 1995 14:57:28 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
PAA11439 for rolc-out; Thu, 2 Nov 1995 15:07:20 -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 PAA11430 for
<rolc@nexen.com>; Thu, 2 Nov 1995 15:07:17 -0500
Received: from lightning.synoptics.com (lightning.synoptics.com
[134.177.3.18]) by guelah.nexen.com (8.6.12/8.6.12) with SMTP id OAA04795 for
<rolc@nexen.com>; Thu, 2 Nov 1995 14:54:28 -0500
Received: from pobox.synoptics.com ([134.177.1.95]) by lightning.synoptics.com
(4.1/SMI-4.1) id AA18052; Thu, 2 Nov 95 12:01:08 PST
Received: from milliways-le0.engwest (milliways-le0.synoptics.com) by
pobox.synoptics.com (4.1/SMI-4.1)
id AA18590; Thu, 2 Nov 95 12:02:31 PST
Received: by milliways-le0.engwest (4.1/SMI-4.1)
id AA01468; Thu, 2 Nov 95 12:02:30 PST
Date: Thu, 2 Nov 95 12:02:30 PST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <asmith@baynetworks.com>
Message-Id: <9511022002.AA01468@milliways-le0.engwest>
To: bcole@cisco.com
Subject: Re: nhrp-05 - Purge packets
Cc: rolc@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/
> To: gardo@vnet.ibm.com > Cc: bcole@cisco.com, luciani@nexen.com, rolc@nexen.com, asmith@BayNetworks.COM, > genecox@vnet.ibm.com > Subject: Re: nhrp-05 - Purge packets > Date: Wed, 01 Nov 1995 12:48:41 -0800 > From: Bruce Cole <bcole@cisco.com> Bruce, > > > >When a station receives an NHRP Purge request, it MUST discard any > > > >previously cached information that matches the Source Address and > > > >Request ID (when the Request ID is zero filled the match is made > > > >based only on the Destination Address). Doesn't the receiver also have to match on some other things e.g. - that the Purge comes from the same guy that supplied the cached information: match on Source IP Address or Source NBMA Address - that the QoS matches what was cached. - what about authentication? Is that used on Purges? - what about NBMA Subnetwork ID? Nowhere is it mentioned that this is or is not allowed in a Purge: presumably it does need to be there in the Purge if an implementation is using it in Request/Reply packets. If it's there, it needs to be checked. I thought things were actually more correct, if a little less clear, before you added this paragraph! Andrew ******************************************************************************** Andrew Smith TEL: +1 408 764 1574 Technology Synergy FAX: +1 408 988 5525 Bay Networks, Inc. E-m: asmith@baynetworks.com Santa Clara, CA ********************************************************************************
- Re: nhrp-05 - Purge packets Andrew Smith
- Re: nhrp-05 - Purge packets Bruce Cole
- Re: nhrp-05 - Purge packets Andrew Smith
- Re: nhrp-05 - Purge packets James Luciani
- Re: nhrp-05 - Purge packets Eric Gray
- Re: nhrp-05 - Purge packets Andrew Smith
- Re: nhrp-05 - Purge packets James Luciani