Return to BSD News archive
Xref: sserve comp.unix.bsd:13308 comp.unix.misc:11026 comp.unix.programmer:14515 comp.unix.questions:44652 Newsgroups: comp.unix.bsd,comp.unix.misc,comp.unix.programmer,comp.unix.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!zip.eecs.umich.edu!umn.edu!news-feed-2.peachnet.edu!darwin.sura.net!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!bcstec!bcsaic!hovnania From: hovnania@bcsaic.boeing.com (Paul Hovnanian) Subject: Re: Looking for info on ftpd/ftp Message-ID: <CJzr77.MvI@bcsaic.boeing.com> Keywords: ftp,ftpd Organization: Boeing Computer Services References: <1994Jan20.055604.1364@sctc.com> <CJxnpM.Cw@cd.com> Date: Fri, 21 Jan 1994 17:57:06 GMT Lines: 35 In article <CJxnpM.Cw@cd.com>, Richard Masoner <richardm@cd.com> wrote: >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: Your list semms to be missing RFC 765. I build an ftpd on an oddball host (HP-BASIC) based mainly on the protocol description in this RFC. Others may add information, but this one is a good start. It is available on the automated mail service at nic.ddn.mil Send mail to: service@nic.ddn.mil subject: RFC 765 No message text is required. You will recieve an e-mail reply in about 1 day. Some large RFCs are send in pieces. -- Paul Hovnanian hovnania@atc.boeing.com [Std disclaimers apply]