Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!cbosgd!ulysses!ucbvax!tcp-ip
From: tcp-ip@ucbvax.ARPA
Newsgroups: fa.tcp-ip
Subject: subnet addresses
Message-ID: <9444@ucbvax.ARPA>
Date: Mon, 29-Jul-85 16:10:19 EDT
Article-I.D.: ucbvax.9444
Posted: Mon Jul 29 16:10:19 1985
Date-Received: Wed, 31-Jul-85 03:47:03 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 17

From: Mark Crispin <MRC@SIMTEL20.ARPA>

Duh, what does this mean for class B 1822 networks?  The byte that
is normally used for a subnet is the host number on the IMP, e.g.
128.43.0.2 is DREA-XX, host 0 on IMP 2 of DRENET.

We could perhaps change the addressing of DRENET to swap those bytes,
so that DREA-XX would become 128.43.2.0.  It would be more logical
that way.  On the other hand, that sort of thinking would argue that
ARPANET and Milnet should also have a flag day and migrate from the
current net.host.local_port.IMP to net.IMP.host.local_port.

Basically, what I am saying is that I expect that no ban be placed
on class B addresses with 0 in the third octet.  What is done in the
subnet system is one thing, but it must NOT be made a rule outside
of it.
-------