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: Sat, 14 Jan 2017 21:30:31 -0500 (EST)	[thread overview]
Message-ID: <20170115023031.B302418C079@mercury.lcs.mit.edu> (raw)

    > From: Johnny Billquist

    > Like I pointed out, RFC760 lacks ICMP.

So? TCP will work without ICMP.

    > Which also makes one question how anyone would have known about IPv4 in
    > 1978.

Well, I can assure you that _I_ knew about it in 1978! (The decision on the v4
packet formats was taken in the 5th floor conference room at 545 Tech Sq,
about 10 doors down from my office!)

But everyone working on TCP/IP heard about Version 4 shortly after the June,
1978 meeting.

    > Also, first definition of TCP shows up in RFC 761

If you're speaking of TCPv4 (one needs to be precise - there were also of
course TCP's 1, 2, 2.5 and 3, going back to 1974), please see IEN-44. (Ignore
IEN's -40 and -41; those were proposals for v4 that got left by the wayside.)

    > So yes, I still have problems with claims that they had it all running
    > in 1978.

I never said we had it "all" running in 1978 - and I explicitly referenced
areas (congestion, addressing/routing) we were still working on over 10 years
later.

But there were working implementations (as in, they could exchange data with
other implementations) of TCP/IPv4 by January 1979 - see IEN 77.

(I'll never forget that weekend - we were in at ISI on Saturday, when it was
normally closed, and IIRC we couldn't figure out how to turn the hallway
lights on, so people were going from office to office in the gloom...)

    Noel


             reply	other threads:[~2017-01-15  2:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-15  2:30 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 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-16  1:01 Noel Chiappa
2017-01-16 10:31 ` Paul Ruizendaal
2017-01-16 12:07 ` Tony Finch
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=20170115023031.B302418C079@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).