Re: nhrp-05 - Purge packets
Andrew Smith <asmith@baynetworks.com> Fri, 03 November 1995 20:21 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa23805;
3 Nov 95 15:21 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa23801;
3 Nov 95 15: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 OAA12308;
Fri, 3 Nov 1995 14:54:46 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
PAA29724 for rolc-out; Fri, 3 Nov 1995 15:03:26 -0500
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by
maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id PAA29713;
Fri, 3 Nov 1995 15:03:23 -0500
Received: from lightning.synoptics.com (lightning.synoptics.com
[134.177.3.18]) by nexen.nexen.com (8.6.12/8.6.12) with SMTP id PAA09128;
Fri, 3 Nov 1995 15:01:42 -0500
Received: from pobox.synoptics.com ([134.177.1.95]) by lightning.synoptics.com
(4.1/SMI-4.1) id AA10192; Fri, 3 Nov 95 11:59:36 PST
Received: from milliways-le0.engwest (milliways-le0.synoptics.com) by
pobox.synoptics.com (4.1/SMI-4.1)
id AA12839; Fri, 3 Nov 95 12:00:59 PST
Received: by milliways-le0.engwest (4.1/SMI-4.1)
id AA02720; Fri, 3 Nov 95 12:00:58 PST
Date: Fri, 3 Nov 95 12:00:58 PST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <asmith@baynetworks.com>
Message-Id: <9511032000.AA02720@milliways-le0.engwest>
To: luciani@nexen.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/
> From owner-rolc@nexen.com Fri Nov 3 09:08:43 1995 > To: asmith@BayNetworks.COM (Andrew Smith) > Subject: Re: nhrp-05 - Purge packets > Cc: rolc@nexen.com > Date: Fri, 03 Nov 1995 11:51:38 -0500 > From: James Luciani <luciani@nexen.com> Jim, > > Doesn't the receiver also have to match on some other things e.g. > > I am strongly against keeping this much state around on a per cache entry > basis. I disagee. (28 bytes for source info X number of cache entries). Sorry, but the protocol has to work correctly. Life's tough. If you can show that it works correctly without these checks under conditions where the NHS is failing over then that's fine. I don't want to see another 1/2-engineered protocol out there: we have enough of those around here already. ... > Don't we know the NBMA Subnet ID as a result of knowing which interface > the packet came in on? A wrong NBMA Subnet ID is in fact an error condition. > > - 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. So you're saying that it's already checked on reception? That wasn't clear to me from reading the current spec. > > Regards, > -- Jim Luciani 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