Return to BSD News archive
Xref: sserve comp.unix.bsd:13295 comp.unix.misc:11003 comp.unix.programmer:14460 comp.unix.questions:44542
Newsgroups: comp.unix.bsd,comp.unix.misc,comp.unix.programmer,comp.unix.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!think.com!sdd.hp.com!cs.utexas.edu!uunet!bif!richardm
From: richardm@cd.com (Richard Masoner)
Subject: Re: Looking for info on ftpd/ftp
Message-ID: <CJxnpM.Cw@cd.com>
Keywords: ftp,ftpd
Organization: Central Data Corp., Champaign, IL
References: <1994Jan20.055604.1364@sctc.com>
Date: Thu, 20 Jan 1994 14:46:33 GMT
Lines: 71
In article <1994Jan20.055604.1364@sctc.com> macomber@sctc.com (Chuck Macomber) writes:
>I'm looking for a technical paper explaining/discussing how the ftp and ftpd
>operate, preferably at an ftp site, but also journal discussions....
I grepped for "FTP" in the rfc index, and this is what I got:
------------------------------------------------------------------------
1415 Mindel, J.; Slaski, R. FTP-FTAM Gateway Specification. 1993 January;
1350 Sollins, K. THE TFTP PROTOCOL (REVISION 2). 1992 July; 11 p. (Format:
1068 DeSchon, A.; Braden, R. Background File Transfer Program (BFTP). 1988
949 Padlipsky, M. FTP unique-named store command. 1985 July; 2 p.
906 Finlayson, R. Bootstrap loading using TFTP. 1984 June; 4 p. (Format:
783 Sollins, K. TFTP Protocol (revision 2). 1981 June; 18 p. (Format:
775 Mankins, D.; Franklin, D.; Owen, A. Directory oriented FTP commands.
751 Lebling, P. Survey of FTP mail and MLFL. 1978 December 10; 5 p.
743 Harrenstien, K. FTP extension: XRSQ/XRCP. 1977 December 30; 8 p.
737 Harrenstien, K. FTP extension: XSEN. 1977 October 31; 1 p. (Format:
697 Lieb, J. CWD command of FTP (Not online) 1975 July 14; 2 p.
691 Harvey, B. One more try on the FTP. 1975 May 28; 13 p. (Format:
683 Clements, R. FTPSRV - Tenex extension for paged files. 1975 April 3;
640 Postel, J. Revised FTP reply codes. 1974 June 5; 16 p. (Format:
630 Sussmann, J. FTP error code usage for more reliable mail service (Not
593 McKenzie, A.; Postel, J. Telnet and FTP implementation schedule change
571 Braden, R. Tenex FTP problem (Not online) 1973 November 15; 1 p.
entering the net, and FTP protocol] (Not online) 1973 August 27; 1 p.
532 Merryman, R. UCSD-CC Server-FTP facility (Not online) 1973 July 12;
520 Day, J. Memo to FTP group: Proposal for File Access Protocol (Not
506 Padlipsky, M. FTP command naming problem (Not online) 1973 June 26;
480 White, J. Host-dependent FTP parameters (Not online) 1973 March 8;
479 White, J. Use of FTP by the NIC Journal (Not online) 1973 March 8;
478 Bressler, R.; Thomas, R. FTP server-server interaction - II (Not
475 Bhushan, A. FTP and network mail system (Not online) 1973 March 6;
468 Braden, R. FTP data compression (Not online) 1973 March 8; 5 p.
463 Bhushan, A. FTP comments and response to RFC 430 (Not online) 1973
458 Bressler, R.; Thomas, R. Mail retrieval via FTP (Not online) 1973
448 Braden, R. Print files in FTP (Not online) 1973 February 27; 4 p.
438 Thomas, R.; Clements, R. FTP server-server interaction (Not online)
414 Bhushan, A. File Transfer Protocol (FTP) status and further comments
412 Hicks, G. User FTP documentation (Not online) 1972 November 27; 10 p.
238 Braden, R. "Comments on DTP and FTP proposals" (Not online) 1971
------------------------------------------------------------------------
Some of these go *way* back, so I don't know how applicable
it would be. The old ones are also not available online.
And this helpful info from nic.ddn.mil:
------------------------------------------------------------------------
ways_to_get_rfcs December 1993
RFCs can be obtained via FTP from NIS.NSF.NET, NISC.JVNC.NET,
VENERA.ISI.EDU, WUARCHIVE.WUSTL.EDU, SRC.DOC.IC.AC.UK,
FTP.CONCERT.NET, DS.INTERNIC.NET, or NIC.DDN.MIL.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info@ISI.EDU" with the message body
"help: ways_to_get_rfcs". For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Requests to be added to or deleted from this RFC-DIST distribution
list should be sent to RFC-REQUEST@NIC.DDN.MIL.
--
Richard F. Masoner | Seen on a magazine cover:
Central Data Corporation |
1602 Newton Dr., Champaign, IL 61821 | "Guns don't kill people,
(217) 359-8010 x251 | television does."