17 Jan
2018
17 Jan
'18
1:33 p.m.
From: Warner Losh
I'm curious: does it inter-operate with modern
TCP/IP implementations?
This just a guess, but 'sort of'? It _is_ TCP/IPv4, so it's got compatible
headers, but I don't know if other parts have changed enough to make it not
work.
E.g. it probably only supports class A addresses, for instance, which is going
to influence the code for picking the first-hop router.
Also, the only driver is, IIRC, for an ARPANET interface.
Noel
18 Jan
18 Jan
12:39 p.m.
On 01/17/2018 11:33 AM, Noel Chiappa via cctalk wrote:
This just a guess, but 'sort of'? It is
TCP/IPv4, so it's got compatible
headers, but I don't know if other parts have changed enough to make it
not work.
Are you referring to the 802.3 Ethernet (vs Ethernet II) frame type that
Frank mentioned?
E.g. it probably only supports class A addresses, for
instance, which
is going to influence the code for picking the first-hop router.
I was not aware that there was code that supported /only/ Class A (/8)
addresses and /not/ Class B (/16) or Class C (/24) addresses.
I /thought/ that everything was either classful (as in supports all
three classes: A, B, and C) or classless (as in supports CIDR).
Is my networking history missing something else?
Also, do any of the systems that people want to emulate have conflicting
classful networks? - Read: Were any of the systems that people want
to emulate on the same classful network?
If all the systems that people want to emulate are on different classful
networks, it should be relatively trivial to interconnect them.
Also, the only driver is, IIRC, for an ARPANET
interface.
Please clarify for this n00b what you mean by ARPANET interface? Are
you referring to host specific hardware that was used to communicate
with an IMP?
Do the necessary emulators support the ARPANET interface?
--
Grant. . . .
unix || die
5:24 p.m.
On Jan 18, 2018, at 9:39, Grant Taylor via cctalk
<cctalk at classiccmp.org> wrote:
On 01/17/2018 11:33 AM, Noel Chiappa via cctalk wrote:
In the course of this discussion I have been reminded that BBN did a TCP/IP for the HP3000
that ran under MPE IV. It is described in IEN 167 and if you read that carefully you will
realize that they got started on MPE III; MPE message files (think record-structured
pipes) first appeared in late MPE III but were not documented until MPE IV.
Trawling the Intertubes for, well, anything about this I turned up a sort of progress
report.
<http://www.dtic.mil/dtic/tr/fulltext/u2/a112575.pdf>
It begins on page 66 of 81, on page 68 of 81 it describes changes to the routing table.
"Currently, this table has one entry for each of the possible 256 networks, and
accesses are very fast." and I'll just leave you with that.
-Frank McConnell
E.g. it probably only supports class A addresses,
for instance, which is going to influence the code for picking the first-hop router.
I was not aware that there was code that supported /only/ Class A (/8) addresses and
/not/ Class B (/16) or Class C (/24) addresses.
I /thought/ that everything was either classful (as in supports all three classes: A, B,
and C) or classless (as in supports CIDR).
Is my networking history missing something else?
2378
days inactive
2379
days old
3 comments
4 participants
participants (4)
-
cctalk＠gtaylor.tnetconsulting.net -
fmc＠reanimators.org -
jnc＠mercury.lcs.mit.edu -
lars＠nocrew.org