From: pnr@planet.nl (Paul Ruizendaal)
Subject: [TUHS] Early Internet work (Was: History of select(2))
Date: Mon, 16 Jan 2017 11:31:32 +0100 [thread overview]
Message-ID: <D166C892-C216-407F-A8FE-9756EB7D2E70@planet.nl> (raw)
In-Reply-To: <20170116010101.8DF6F18C083@mercury.lcs.mit.edu>
On 16 Jan 2017, at 2:01 , Noel Chiappa wrote:
>
>> From: Paul Ruizendaal
>
>> I guess by April 1981 (RFC777) we reach a point where things are
>> specified to a level where implementations would interoperate with
>> today's implementations.
>
> Yes and no. Earlier boxes would interoperate, _if addresses on each end were
> chosen properly_. Modern handling of addresses on hosts (for the 'is this
> destination on my physical network' step of the packet-sending algorithm) did
> not come in until RFC-1122 (October 1989); prior to that, lots of host code
> probably tried to figure out if the destination was class A, B or C, etc, etc.
This is true of the Gurwitz implementation. The Wingfield implementation still uses the older form, where the first 8 bits signify the network and the remaining 24 bits the host address on that network. In terms of routing my view would be to keep it simple: traffic is either local or destined for the single interface / gateway (see below). Interop hence is just looking at TCP.
>
> Also, until RFC-826 (ARP, November 1982) pretty much all the network
> interfaces (and thus the code to turn the 'destination IP address' into an
> attached physical network address, for the first hop) were things like ARPANet
> that no longer exist, so you could't _actually_ fire up one of them unless you
> do something like the 'ARPANet emulation' that the various PDP-10 simulators
> use to allow old OS's running on them to talk to the current Internet.
Yes: all these old implementations have an IMP interface driver at their lowest level. What I'm doing for testing is replacing that by a SLIP driver so that I can hook up to today's network and see if it works.
Paul
next prev parent reply other threads:[~2017-01-16 10:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 1:01 Noel Chiappa
2017-01-16 10:31 ` Paul Ruizendaal [this message]
2017-01-16 12:07 ` Tony Finch
-- 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 15:17 Noel Chiappa
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-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=D166C892-C216-407F-A8FE-9756EB7D2E70@planet.nl \
--to=pnr@planet.nl \
/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).