Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ucbvax!dyer@harvard.HARVARD.EDU@spdcc.UUCP
From: dyer@harvard.HARVARD.EDU@spdcc.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: internet numbering scheme
Message-ID: <8702010431.AA06392@ucbvax.Berkeley.EDU>
Date: Sat, 31-Jan-87 22:58:24 EST
Article-I.D.: ucbvax.8702010431.AA06392
Posted: Sat Jan 31 22:58:24 1987
Date-Received: Sun, 1-Feb-87 11:47:16 EST
References: <8701291600.AA08933@necntc.NEC.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: dyer@spdcc.COM (Steve Dyer)
Organization: S.P. Dyer Computer Consulting, Cambridge MA
Lines: 16
Approved: tcp-ip@sri-nic.arpa

If your network might eventually be connected to the Internet, you can petition
the NIC for a "network number assignment for a network unconnected to the ARPA
Internet".  This will simplify matters if you ever manage to get hooked up later
(say, via CSNET.)  Send a message to Joyce Reynolds, jkrey@venera.isi.edu, and
she'll send you an electronic form to fill out.  You may request a Class B or
Class C network number, depending on your needs.

I don't see how having VMS machines has much to do with consistent network
numbering.  If they're running TCP/IP and support subnets, they're just like
any other host.  If VMS machines are talking DECnet on an interconnected DECnet,
then you have to worry about being consistent with the other DECnet hosts
and conventions, but it don't have nothing to do with TCP/IP.
---
Steve Dyer
dyer@harvard.HARVARD.EDU
dyer@spdcc.COM aka {linus,wanginst,bbnccv,harvard,ima,ihnp4}!spdcc!dyer