File Transfer Protocol Research Paper
This paper assumes knowledge of the Transmission Control Protocol (TCP)  and the Telnet Protocol .
These documents are contained in the ARPA-Internet protocol handbook .
The use of a "Set Data Type" transaction was proposed in RFC 294 in January 1982. The File Transfer Protocol was now defined as a protocol for file transfer between HOSTs on the ARPANET, with the primary function of FTP defined as transfering files efficiently and reliably among hosts and allowing the convenient use of remote file storage capabilities.
RFC 385 further commented on errors, emphasis points, and additions to the protocol, while RFC 414 provided a status report on the working server and user FTPs.
However, many implementations based on the older specification were not updated.
In 1974, RFCs 607 and 614 continued comments on FTP.
If your email client or browser is correctly configured, clicking on the link will start up the file transfer (if a single file is specified) or open up either a browser or GUI based FTP client window showing the FTP directory contents (if an FTP folder is specified).
Motivated by the transition from the NCP to the TCP as the underlying protocol, a phoenix was born out of all of the above efforts in RFC 765 as the specification of FTP for use on TCP.
In this section, the history, the terminology, and the FTP model are discussed.
The terms defined in this section are only those that have special significance in FTP.
RFC 430, issued in 1973, (among other RFCs too numerous to mention) presented further comments on FTP.
Finally, an "official" FTP document was published as RFC 454.