From: Lars Brinkhoff <lars@nocrew.org>
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: coff@minnie.tuhs.org
Subject: Re: [COFF] [TUHS] conventions around zero padding in ip4
Date: Wed, 11 May 2022 05:30:16 +0000 [thread overview]
Message-ID: <7w5ymcprfb.fsf@junk.nocrew.org> (raw)
In-Reply-To: <20220510221912.06EAE18C085@mercury.lcs.mit.edu> (Noel Chiappa's message of "Tue, 10 May 2022 18:19:12 -0400 (EDT)")
Noel Chiappa wrote:
> > Any idea when the TENEX implementation was made?
>
> Anyway, about the first details about the TENEX TCP implementation
> (done by Bill Pluumer, whom we have now sadly lost) I could find are
> in IEN-67 ("Meeting Notes - 30 & 31 January 1978"):
>
> https://www.rfc-editor.org/ien/ien67.pdf
Thanks! I found this from "19SEP76" which must have been a very
early version.
https://elists.isoc.org/pipermail/internet-history/2020-March/005912.html
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next prev parent reply other threads:[~2022-05-11 5:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 22:19 Noel Chiappa
2022-05-11 5:30 ` Lars Brinkhoff [this message]
[not found] <20220509161416.EDB2F18C073@mercury.lcs.mit.edu>
2022-05-10 5:23 ` Lars Brinkhoff
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=7w5ymcprfb.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=coff@minnie.tuhs.org \
--cc=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).