Connected: An Internet Encyclopedia
RFC 959 - 3.3. DATA CONNECTION MANAGEMENT

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 959
Up: 3. DATA TRANSFER FUNCTIONS
Prev: 3.2. ESTABLISHING DATA CONNECTIONS
Next: 3.4. TRANSMISSION MODES

### 3.3. DATA CONNECTION MANAGEMENT

Default Data Connection Ports: All FTP implementations must support use of the default data connection ports, and only the User-PI may initiate the use of non-default ports.

Negotiating Non-Default Data Ports: The User-PI may specify a non-default user side data port with the PORT command. The User-PI may request the server side to identify a non-default server side data port with the PASV command. Since a connection is defined by the pair of addresses, either of these actions is enough to get a different data connection, still it is permitted to do both commands to use new ports on both ends of the data connection.

Reuse of the Data Connection: When using the stream mode of data transfer the end of the file must be indicated by closing the connection. This causes a problem if multiple files are to be transfered in the session, due to need for TCP to hold the connection record for a time out period to guarantee the reliable communication. Thus the connection can not be reopened at once.

There are two solutions to this problem. The first is to negotiate a non-default port. The second is to use another transfer mode.

A comment on transfer modes. The stream transfer mode is inherently unreliable, since one can not determine if the connection closed prematurely or not. The other transfer modes (Block, Compressed) do not close the connection to indicate the end of file. They have enough FTP encoding that the data connection can be parsed to determine the end of the file. Thus using these modes one can leave the data connection open for multiple file transfers.

Next: 3.4. TRANSMISSION MODES

Connected: An Internet Encyclopedia
RFC 959 - 3.3. DATA CONNECTION MANAGEMENT