Re: nhrp-05 - Purge packets

James Luciani <luciani@nexen.com> Fri, 03 November 1995 23:57 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa29555; 3 Nov 95 18:57 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa29545; 3 Nov 95 18:57 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 SAA14090; Fri, 3 Nov 1995 18:29:19 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id SAA02513 for rolc-out; Fri, 3 Nov 1995 18:39:09 -0500
Received: from shovel.nexen.com (shovel.nexen.com [204.249.98.39]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id SAA02504; Fri, 3 Nov 1995 18:39:06 -0500
Received: from localhost (luciani@localhost) by shovel.nexen.com (8.6.12/8.6.12) with SMTP id SAA20664; Fri, 3 Nov 1995 18:38:32 -0500
Message-Id: <199511032338.SAA20664@shovel.nexen.com>
To: Andrew Smith <asmith@baynetworks.com>
Subject: Re: nhrp-05 - Purge packets
In-reply-to: Your message of "Fri, 03 Nov 1995 12:00:58 PST." <9511032000.AA02720@milliways-le0.engwest>
cc: rolc@nexen.com
Date: Fri, 03 Nov 1995 18:38:32 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: James Luciani <luciani@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/

Andrew,

> > > 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.

Oh come on. Because I don't believe that we should cache every single bit
of information does not mean that the protocol is broken.

Also, I screwed up.  I meant to say that I strongly disagreed with NBMA information
being cached but that the internetworking layer address information would 
be quite agreeable to me. In fact, I like the idea of saving the IP
address not that this is any proof against spoofing but it does prevent 
some accidental purges.

Regards,
-- Jim Luciani
__________________________________________________________________________
James V. Luciani    Ascom Nexion                    voice: +1 508 266-3450
luciani@nexen.com   289 Great Rd., Acton MA 01720   FAX: +1 508 266-2300