The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Early Internet work (Was: History of select(2))
Date: Mon, 16 Jan 2017 10:17:45 -0500 (EST)	[thread overview]
Message-ID: <20170116151745.1B12018C085@mercury.lcs.mit.edu> (raw)

    > From: Tony Finch

This is getting a bit far afield from Unix, so my apologies to the list for
that. But to avoid dumping it in the Internet-History list abruptly, let me
answer here _briefly_ (believe it or not, the below _is_ brief).

    > AIUI there were two major revisions to the IPv4 addressing architecture:

Not quite (see below). First, one needs to understand that there are two
different timelines for changes to addressing: in the hosts, and in the
routers (called 'gateways' originally). To start with, they were tied
together, but as of RFC-1122, they were formally separated: hosts no longer
fully understood the syntax/semantics of addresses, just (mostly) treated them
as opaque 32-bit quantities.

    > subnetting (RFC 917, October 1994 ... RFC 950, August 1985), and
    > classless routing (RFC 1519, September 1993)

Originally, network numbers were 8 bits, and the 'rest' (local) part was 24.
Mapping from IP addresses to physical network addresses was some with direct
mapping - ARP did not exist - the actual local address (e.g. IMP/Port) was
contained in the 'rest' field - each network had a document which specified
the mapping. (Which is part of the interoperability issue with old
implementations.)

As some point early on, it was realized that 8 bits of network number were not
enough, and the awful A/B/C kludge was added (it was dropped on the community,
not discussed before-hand). Subnetting was indeed the next change.  Then the
host/router split happened.

Classless routing (which effectively extended addesses, for path-computation
purposes, to 32+N bits - since you couldn't look at a 32-bit IP address and
immediately tell which was the 'network' part any more, you _had_ to have the
mask as well, to tell you how many bits of any given address were the network
number) was more of a process than a single change - the inter-AS routing
(BGP) had to change, but so did IGP's (OSPF, IS-IS), etc, etc.

    > originally called supernetting (RFC 1338, June 1992).

There was this effort called ROAD which produced RFC-1338 and 1519, and IIRC
there was an intermediate, involving blocks of network numbers (1338), and
that slowly evolved into arbitrary blocks (1519).

One should also note that the term "super-netting" comes from a proposal by
Carl-Hubert ("Roki") Rokitansky which did not, alas, make it to RFC. (His
purpose was different, but it used the same mechanism.) Alas, the authors of
1338/1519 failed to properly acknowledge his earlier work.

	  Noel


             reply	other threads:[~2017-01-16 15:17 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 15:17 Noel Chiappa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-01-30 16:15 Noel Chiappa
2017-01-30 16:41 ` Clem Cole
2017-01-30 16:44 ` Clem Cole
2017-01-30 15:34 Noel Chiappa
2017-01-30 21:20 ` Paul Ruizendaal
2017-01-30  2:50 Noel Chiappa
2017-01-30  3:33 ` Nick Downing
2017-01-30  3:38   ` Ron Natalie
2017-02-08  3:58   ` Dave Horsfall
2017-01-30  8:26 ` Paul Ruizendaal
2017-01-30  1:44 Noel Chiappa
2017-01-29 18:35 Noel Chiappa
2017-01-29 17:41 Noel Chiappa
2017-01-29 20:28 ` Paul Ruizendaal
2017-01-30  1:34 ` Nick Downing
2017-01-30  2:19   ` Clem Cole
2017-01-30  2:30     ` Larry McVoy
2017-01-30  2:43       ` Ron Natalie
2017-01-30  2:43       ` Clem Cole
2017-01-30  2:32     ` Larry McVoy
2017-01-30  2:39       ` Clem Cole
2017-01-30 13:13     ` Dave Horsfall
2017-01-30 13:37       ` Larry McVoy
2017-01-16 14:42 Noel Chiappa
     [not found] <mailman.1.1484532001.2693.tuhs@minnie.tuhs.org>
2017-01-16 10:21 ` Johnny Billquist
2017-01-16  1:47 Noel Chiappa
2017-01-16 10:06 ` Paul Ruizendaal
2017-01-16  1:01 Noel Chiappa
2017-01-16 10:31 ` Paul Ruizendaal
2017-01-16 12:07 ` Tony Finch
2017-01-15  2:30 Noel Chiappa
2017-01-13 13:19 Noel Chiappa
2017-01-09  2:35 [TUHS] History of select(2) Warren Toomey
2017-01-09 10:36 ` Paul Ruizendaal
2017-01-12  3:54   ` Clem Cole
2017-01-13  9:13     ` Paul Ruizendaal
     [not found]       ` <20170114164102.GA31665@yeono.kjorling.se>
2017-01-16  0:13         ` [TUHS] Early Internet work (Was: History of select(2)) Paul Ruizendaal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170116151745.1B12018C085@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).