Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!aic.nrl.navy.mil!hoey
From: hoey@aic.nrl.navy.mil (Dan Hoey)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  trace route to OZ (indeed!)
Message-ID: <617394795.hoey@aic.nrl.navy.mil>
Date: 25 Jul 89 18:33:15 GMT
References: <8907200854.AA02438@sapphire.oce.orst.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: hoey@aic.nrl.navy.mil (Dan Hoey)
Organization: Naval Research Lab, Washington, DC
Lines: 17

In article <8907200854.AA02438@sapphire.oce.orst.edu> pvo3366@OCE.ORST.EDU (Paul O'Neill) writes:
...
>20  La_Jolla,CA.NSS.NSF.NET (129.140.6.14)  1240 ms *  1370 ms 
>21  La_Jolla,CA.NSS.NSF.NET (129.140.6.11)  1390 ms  1320 ms  1460 ms 

Say what you like about the bad old host table days, but at least we
didn't get any commas in the host names back then.  I can't even find
out the mail address for whatever zone 14.6.140.129.IN-ADDR.ARPA is in,
but I can hope that the postmasters at the authoritative servers may be
able to figure it out.

Considering what would happen if this name got into a mail header, I
just wonder if it's possible to get CRLFs into the canonical name,
leading to wholesale rewriting of mail headers through host name
canonicalization.  But surely that's impossible....

Dan