Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!cbosgd!ulysses!ucbvax!A.ISI.EDU!CERF
From: CERF@A.ISI.EDU.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: ICMP message caching
Message-ID: <[A.ISI.EDU].1-Apr-87.21:32:29.CERF>
Date: Wed, 1-Apr-87 21:32:00 EST
Article-I.D.: <[A.ISI.EDU].1-Apr-87.21:32:29.CERF>
Posted: Wed Apr  1 21:32:00 1987
Date-Received: Sat, 4-Apr-87 10:17:27 EST
References: <8703291428.AA29318@brillig.umd.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 16
Approved: tcp-ip@sri-nic.arpa

Steve,

there will be some howls, but I think the idea of ICMP caching to
be worth exploring. We are surely in agreement that the more knowledge 
you can obtain about the Internet condition, the better you can, at
the source, make decisions about traffic routing, retransmission,
attempts to set-up connections, etc.

I am sure this subject has come up before - some folks were uncomfortable
because it seemed to smack of protocol boundary crossing - Dave mIlls
mentioned a similar idea relative to caching such information th the
gateways, too.

Let's see what comments your notion uncovers!

Vint