Re: ftp://ftp.cisco.com/fred/rreq-03.txt

Bill Manning <bmanning@isi.edu> Wed, 04 January 1995 04:51 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18820; 3 Jan 95 23:51 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18816; 3 Jan 95 23:51 EST
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa29410; 3 Jan 95 23:51 EST
Received: from zephyr.isi.edu by venera.isi.edu (5.65c/5.61+local-20) id <AA15145>; Tue, 3 Jan 1995 20:35:51 -0800
Received: by zephyr.isi.edu (5.65c/5.61+local-17) id <AA09549>; Tue, 3 Jan 1995 20:35:43 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Bill Manning <bmanning@isi.edu>
Message-Id: <199501040435.AA09549@zephyr.isi.edu>
Subject: Re: ftp://ftp.cisco.com/fred/rreq-03.txt
To: Scott Bradner <sob@newdev.harvard.edu>
Date: Tue, 3 Jan 1995 20:35:43 -0800 (PST)
Cc: bmanning@isi.edu, kre@munnari.oz.au, fred@cisco.com, rreq@isi.edu
In-Reply-To: <199501040421.XAA20122@newdev.harvard.edu> from "Scott Bradner" at Jan 3, 95 11:21:57 pm
X-Mailer: ELM [version 2.4 PL24]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 215

Hit/Hint... its close to the same thing.   

Unless you have no other things on your plate, you might want to 
drop this one.  It is much more trivial (implementation specific)
than route caching... :)

-- 
--bill