From: Paul Ruizendaal <pnr@planet.nl>
To: "tuhs@tuhs.org" <tuhs@tuhs.org>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: [TUHS] Re: Mills' initial implementation of FTP - best citation?
Date: Tue, 23 Jan 2024 14:36:56 +0100 [thread overview]
Message-ID: <F4AF68AE-7090-434F-8E2A-46D8616E21CF@planet.nl> (raw)
In-Reply-To: <20240122212953.6CA5718C084@mercury.lcs.mit.edu>
> On 22 Jan 2024, at 22:29, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>
> Maybe the "needing clarification" refers to these two different FTP's? Without
> an explicit classifier, does that text refer to NCP FTP or TCP FTP?
>
> Noel
That is a good point. I looked at a longer section of his talk and indeed the FTP reference is part of his discussion the NCP->TCP transition. Here it becomes easier to find references to support the claim.
The strongest one that I could find is in the TCP-IP Digest mailing list from that era. The first issue has a summary of what is already out there and David Mills work is mentioned:
https://jaist-g.dl.sourceforge.jp/pub/RFC/museum/tcp-ip-digest/tcp-ip-digest.v1n1.1
====
COMSAT
Date: 30 Apr 1980
From: Dave Mills <Mills@ISIE>
1. The TCP/IP implementation here runs in an LSI-11 with a homegrown
operating system compatible in most respects to RT-11. Besides the
TCP/IP levels the system includes many of the common high-level
protocols used in the ARPANET community, such as TELNET, FTP and
XNET.
=====
Although this date precedes the date of the RFC by a few months, I do believe that it is correct and not a typo. For example, IEN-194 (July 1981) discusses the system from a perspective of experience, not of recently completed code.
All that said, I wonder if “doing the first FTP” is a true reflection of his contribution in this era. After all, porting NCP FTP to TCP FTP is not all that big a deal (see for instance https://www.tuhs.org/cgi-bin/utree.pl?file=BBN-Vax-TCP/src/ftp). Maybe the sentence on Wikipedia should say that beyond NTP, he was an important contributor to several other early internet protocols.
next prev parent reply other threads:[~2024-01-23 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 21:29 Noel Chiappa
2024-01-23 13:36 ` Paul Ruizendaal [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-23 4:39 Noel Chiappa
2024-01-23 5:19 ` George Michaelson
2024-01-22 16:15 Paul Ruizendaal
2024-01-23 2:04 ` Bakul Shah
2024-01-22 7:41 [TUHS] " Royce Williams
2024-01-22 12:53 ` [TUHS] " Marc Donner
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=F4AF68AE-7090-434F-8E2A-46D8616E21CF@planet.nl \
--to=pnr@planet.nl \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@tuhs.org \
/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).