Generated by DeepSeek V3.2| RFC 114 | |
|---|---|
| Title | A File Transfer Protocol |
| Number | 114 |
| Author | A. K. Bhushan, M. A. Padlipsky, R. H. Thomas |
| Publication date | April 1971 |
| Status | Obsolete |
| Series | Request for Comments |
| Replaces | None |
| Replaced by | RFC 141, RFC 172, RFC 265, RFC 354, RFC 542, RFC 765 |
RFC 114. Published in April 1971, this document, authored by A. K. Bhushan, M. A. Padlipsky, and R. H. Thomas, represents one of the earliest formal specifications for a File Transfer Protocol (FTP) on the ARPANET. It was a foundational step in standardizing how files could be moved between different host computers, addressing a critical need in the nascent network's development. Although quickly superseded, its proposals for command structure and data transfer modes directly influenced the evolution of the ubiquitous FTP service that became essential to the Internet.
The primary objective was to define a protocol enabling efficient and reliable file transfer between heterogeneous systems on the ARPANET, a network then connecting research institutions like the MIT and Stanford University. It aimed to solve practical problems of interoperability between different operating systems and hardware, such as those from IBM and DEC. The protocol outlined a framework using the existing Network Control Program and built upon concepts from earlier network experiments, seeking to establish a standard set of commands and replies. This effort was part of a broader series of Request for Comments documents coordinated by the Network Working Group, which included figures like Steve Crocker and Vint Cerf.
The protocol operated using a model separating control and data connections, a concept retained in later versions. The user would establish a connection to a server's specified TCP port, though the document predates the formalization of the TCP/IP suite. Commands, sent over the control connection, included basic instructions like `RETRIEVE` for downloading files and `STORE` for uploading, with replies providing numeric status codes. It specified different data transfer modes, including one for handling ASCII text and another for raw binary data, acknowledging the need to handle diverse file types. The specification also grappled with issues of data representation and file structure across different systems, such as those using EBCDIC encoding.
Initial implementations were deployed on key ARPANET nodes, allowing researchers at sites like the UCLA and the Stanford Research Institute to share data and software. Its use demonstrated the utility of a dedicated file transfer service, but also revealed limitations in its design, particularly regarding error handling and security. These practical experiences were immediately fed back into the Network Working Group, leading to rapid revisions. Within months, it was made obsolete by RFC 141, which corrected flaws and expanded functionality, beginning a swift iterative process that continued through documents like RFC 172 and RFC 265.
This RFC was created during a period of intense experimentation following the successful demonstration of the ARPANET in 1969. It followed other foundational application-layer protocols, such as those for Telnet (defined in documents like RFC 97), and preceded the development of electronic mail standards. The work was influenced by earlier time-sharing system file transfer methods and occurred alongside the development of the CYCLADES network in France. The authors were part of the research community centered around projects funded by the DARPA, which sought to create robust, resource-sharing computer networks.
While short-lived, it served as a crucial proof-of-concept, providing the architectural blueprint upon which all subsequent FTP standards were built. Its core model of separate control and data channels became a permanent feature of the protocol, finalized years later in the widely adopted RFC 765. The iterative process it began exemplified the pragmatic, implementation-driven ethos of the early IETF community. Furthermore, the functional need it addressed directly supported the collaborative culture of open-source software development and scientific data exchange, contributing to the Internet's growth as a tool for global research and communication. Category:Request for Comments Category:File Transfer Protocol Category:1971 documents Category:Internet standards Category:History of the Internet