There will be a system update on Friday, May 5th, 6 PM ET. You may experience a brief service interruption.
Browse Prior Art Database

File Transfer Protocol (RFC0542)

IP.com Disclosure Number: IPCOM000003651D
Original Publication Date: 1973-Aug-12
Included in the Prior Art Database: 2000-Sep-13

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

N. Neigus: AUTHOR


File Transfer Protocol (Aug. 12, 1973) RFC 542 NIC 17759 the ACM, Vol. 7, No. 10, 606 (Oct. 1964)). In a line or a record, formatted according to the ASA Standard, the first character is not to be printed. Instead it should be used to determine the vertical movement of the paper which should take place before the rest of the record is printed. The ASA Standard specifies the following control characters:

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 3% of the total text.

File Transfer Protocol

(Aug. 12, 1973)

RFC 542 NIC 17759

Nancy J. Neigus See Also: RFCs 354, 454, 495

Bolt Beranek and Newman, Inc.

Cambridge, Mass.

File Transfer Protocol for the ARPA Network

File Transfer Protocol

(Aug. 12, 1973)

RFC 542 NIC 17759


This document is the result of several months discussion via RFC

(relevant numbers are 430, 448, 454, 463, 468, 478, 480), followed by a

meeting of the FTP committee at BBN on March 16, followed by further

communication among committee members. There are a considerable number

of changes for the last "official" version, see RFCs 354, 385, but the

gross structure remains the same. The places to look for differences

are (1) in the definitions pf types and modes, (2) in the specification

of the data connection and data sockets, (3) in the command-reply

sequences, (4) in the functions dependent on the TELNET protocol (FTP

has been altered to correspond to the new TELNET spec). The model has

been clarified and enlarged to allow inter-server file transfer, and

several new commands have been added to accommodate more specialized (or

site-specific) functions. It is my belief that this new specificiation

reflects the views expressed by the committee at the above-mentioned

meeting and in subsequent conversations.

The large number of incompatibilities would complicate a phased

implementation schedule, such as is in effect for the TELNET protocol.

Therefore we have assigned a new socket, decimal 21, as a temporary

logger socket for the new version and a change-over date of 1 February

1974. Until that date the old (354, 385) version of FTP will be

available on Socket 3 and the new version (attached) should be

implemented on Socket 21. On 1 February the new version will shift to

Socket 3 and the old disappear from view.

The File Transfer protocol should be considered stable at least until

February, though one should feel free to propose further changes via

RFC. (Implementation of new commands on an experimental basis is

encouraged and should also be reported by RFC.) In addition, members of

the FTP committee may be contacted directly about changes. Based on

attendance at the March 16 meeting, they are:

Abhay Bhushan MIT-DMCG

Bob Braden UCLA-CCN

Bob Bressler BBN-NET

Bob Clements BBN-TENEX


Peter Deutsch PARC-MAXC

Wayne Hathaway AMES-67

Mike Kudlick SRI-ARC

Alex McKenzie BBN-NET

Bob Merryman UCSD-CC

Nancy Neigus BBN-NET

Mike Padlipsky MIT-Multics

Jim Pepin USC-44

Ken Pogran MIT-Multics

Jon Postel UCLA-NMC


File Transfer ...