Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!orstcs!sapphire!pvo3366
From: pvo3366@sapphire.OCE.ORST.EDU (Paul O'Neill)
Newsgroups: comp.protocols.tcp-ip,orst.internetworking
Subject: Re:  source-route, record route ping (Re:  traceroute)
Message-ID: <14450@orstcs.CS.ORST.EDU>
Date: 17 Dec 89 23:19:50 GMT
References: <8912172016.AA01804@sccgate.scc.com>
Sender: usenet@orstcs.CS.ORST.EDU
Reply-To: pvo3366@sapphire.OCE.ORST.EDU (Paul O'Neill)
Organization: Coastal Imaging Lab, Oregon State University, Corvallis, OR
Lines: 25

In article <8912172016.AA01804@sccgate.scc.com> enger@SCCGATE.SCC.COM (Robert M. Enger) writes:

>Isn't it about time for 4.2 to die?

Sure. And I'm glad my systems are running the latest and the greatest.
However...

>Source route traceroute is out already, better get the weak and disabled
>off the street.

I know folks who are stuck at 4.2 (SunOS 3.5) because their vendors haven't
updated critical applications to run under SunOS 4.0 yet.  Were I to go
out and start crashing their gateways w/ pong or S-R traceroute I doubt
they or the Internet community at large would appreciate it.  

Your street analogy is quite appropriate.  Should Corvettes run Model-T's
off the road because they're weak & disabled?  Especially if there's a
passing lane?  (Regular traceroute usually tells me all I need without 
crashing them.)


Paul O'Neill                 pvo@oce.orst.edu
Coastal Imaging Lab
OSU--Oceanography
Corvallis, OR  97331         503-754-3251