🚀 go-pugleaf

In article <1992Aug01.175418.7792@anomaly.sbs.risc.net> kd1hz@anomaly.sbs.risc.net (Michael P. Deignan (KD1HZ)) writes:
>In fact, this very week I set up a tcp/ip network using a network 
>address of 143.62.5.x. Does someone "own" this IP address? Probably.
>Does it matter to me? No, since the network I set up is completely
>internal and has no intention of ever connecting to the Internet.

As long as this network is not intended to connect to the Internet, then
such an addressing scheme is quite workable.

However, how many parties out in the world have numbered their hosts with
"reserved" IP addresses, only to find out (the hard way) that they have to
renumber their network if they want to connect into the Internet?

As a matter of fact, 143.62 is indeed a reserved network.  According to the
whois server at NIC.DDN.MIL, Cincinnati Milacron has reserved that particular
network.

>--  Dr. Michael P. Deignan (deg.pend.)      /   "Its okay dear,
>--  Domain: kd1hz@anomaly.sbs.risc.net     /     you can show me...
>--    UUCP: ..!uunet!anomaly!kd1hz        /      I'm a Doctor..."


-- 
D. Robert Spexet II, N0OKR   Internet:  spexet@math.lsa.umich.edu
Department of Mathematics    BITnet:    user68xr@umichum.bitnet
The University of Michigan   UUCP:      uunet!mailrus!math.lsa.umich.edu!spexet
Ann Arbor, Michigan 48109