Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!decwrl!pyramid!pesnta!hplabs!ucbvax!SALLY.UTEXAS.EDU!jsq
From: jsq@SALLY.UTEXAS.EDU.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: more interesting features of 4.2
Message-ID: <8606041338.AA18083@sally.UTEXAS.EDU>
Date: Wed, 4-Jun-86 09:38:35 EDT
Article-I.D.: sally.8606041338.AA18083
Posted: Wed Jun  4 09:38:35 1986
Date-Received: Wed, 4-Jun-86 23:54:39 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 11
Approved: tcp-ip@sri-nic.arpa

Right.  I had assumed RFC917 was completely superseded when RFC950
came out, but I see it still has quite a bit of useful information in it.

The ARP hack has many deficiencies, as you point out, but many of us
don't have much choice since we have systems to which we don't have
the source and for which the vendor has not yet implemented subnets
(e.g., TOPS-20, Silicon Graphics, Integrated Solutions, Bridge, Sun,
VMS, Ridge, etc. ad nauseum).

Perhaps the MIT ICMP host redirect method is the better interim solution.
Does anyone have anything more to add on that than what's in RFC917?