The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: bakul@iitbombay.org, tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Re: Mills' initial implementation of FTP - best citation?
Date: Mon, 22 Jan 2024 23:39:56 -0500 (EST)	[thread overview]
Message-ID: <20240123043956.1DEEF18C085@mercury.lcs.mit.edu> (raw)

    > From: Bakul Shah

    > He was part of NSFNet, so could have got first FTP on NSFnet or a
    > later version of FTP.

You all are talking about _two separate FTP's_ (as I pointed out
previously). If you all would stop confusing yourselves, you'd be able to sort
out the bogons.

In this particular case, the NSFnet appeared at a _much_ later stage of the
growth of the Internet (yes, it is spelled with a capital 'I'; the morons at
the AP were not aware that 'internet' was a pre-existing word with a
_different meaning_) than when Dave was working with the Fuzzball, and by that
point there were _many_ TCP FTP's (e.g. the ITS one I previously sent the URL
to the source for), so the 'first FTP on NSFnet' is a non-concept.

The best bet for accurate data is to look at the TCP meeting minutes from the
IEN series:

    https://www.rfc-editor.org/ien/ien-index.html

Looking quickly, the first one that Dave appears in might be IEN-160,
"Internet Meeting Notes -- 7-8-9 October 1980". (He wasn't in the "Attendees"
lists of any of the earlier ones I looked at.) Look in the "Status Reports"
sections to see if he says anything about where he's at. The one for this one
says:

  "Dave described the configuration of equipment at COMSAT which consists of a
  number of small hosts, mainly LSI-11s. ... COMSAT has also used NIFTP to
  transmit files between their hosts and ISIE.  The NIFTP software was provided
  by UCL. ... COMSAT plans to .. arrange a permanent connection to the ARPANET."

I have no idea what a "NIFTP" might be. Also, there is a reason that serious
historians prefer contemporary written records, not people's memories.

	   Noel






             reply	other threads:[~2024-01-23  4:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23  4:39 Noel Chiappa [this message]
2024-01-23  5:19 ` George Michaelson
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22 21:29 Noel Chiappa
2024-01-23 13:36 ` Paul Ruizendaal
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=20240123043956.1DEEF18C085@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    --cc=bakul@iitbombay.org \
    --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).