Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!uxc.cso.uiuc.edu!uxc.cso.uiuc.edu!m.cs.uiuc.edu!p.cs.uiuc.edu!zweig
From: zweig@p.cs.uiuc.edu
Newsgroups: comp.protocols.tcp-ip
Subject: Re: trace route to OZ
Message-ID: <93400029@p.cs.uiuc.edu>
Date: 26 Jul 89 17:10:00 GMT
Lines: 30
Nf-ID: #R:<8907211224.AA19984@ucbvax.Berke:-40:p.cs.uiuc.edu:93400029:000:1492
Nf-From: p.cs.uiuc.edu!zweig    Jul 26 12:10:00 1989


> Written Jul 24, 1989 by roy@phri.UUCP in comp.protocols.tcp-ip
> In article <8907191847.AA06030@cincsac.arc.nasa.gov> medin@NSIPO.NASA.GOV
>    ("Milo S. Medin", NASA ARC NSI Project Office) writes:
> > The tcp-ip list is too big and too diverse to be used for network debugging.
> > The MERIT folks and NASA both have mailing lists for operational issues
> > which are appropriate for this type of discussion.
> 
> 	While this may "officially" be true, I'd like to point out that I
> for one have no objection to this on tcp-ip.  While I don't have any direct
> involvement with routing issues, I am interested in knowing as much as I
> can about it.  Listening in on the discussions about problems seems like a
> good way of picking stuff up.
> -- 

  I agree very strongly with this and the other similar opinions that have
been expressed recently. Finding problems people are having can be very
instructive about complex software systems like communication protocol
subsystems. I think the "we don't have the time for your silly little
problems" sentiment would be more appropriate in comp.protocols.ivory-tower.


-Johnny Zweig
 University of Illinois at Urbana-Champaign
 Department of Computer Science
--------------------------------Disclaimer:------------------------------------
   Rule 1: Don't believe everything you read.
   Rule 2: Don't believe anything you read.
   Rule 3: There is no Rule 3.
-------------------------------------------------------------------------------