Connected: An Internet Encyclopedia
4.1.2.12 Connections: RFC-959 Section 5.2

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1123
Up: 4. FILE TRANSFER
Up: 4.1 FILE TRANSFER PROTOCOL -- FTP
Up: 4.1.2. PROTOCOL WALK-THROUGH
Prev: 4.1.2.11 FTP Replies: RFC-959 Section 4.2, Page 35
Next: 4.1.2.13 Minimum Implementation; RFC-959 Section 5.1

4.1.2.12 Connections: RFC-959 Section 5.2

4.1.2.12 Connections: RFC-959 Section 5.2

The words "and the port used" in the second paragraph of this section of RFC-959 are erroneous (historical), and they should be ignored.

On a multihomed server host, the default data transfer port (L-1) MUST be associated with the same local IP address as the corresponding control connection to port L.

A user-FTP MUST NOT send any Telnet controls other than SYNCH and IP on an FTP control connection. In particular, it MUST NOT attempt to negotiate Telnet options on the control connection. However, a server-FTP MUST be capable of accepting and refusing Telnet negotiations (i.e., sending DONT/WONT).

DISCUSSION:

Although the RFC says: "Server- and User- processes should follow the conventions for the Telnet protocol...[on the control connection]", it is not the intent that Telnet option negotiation is to be employed.


Next: 4.1.2.13 Minimum Implementation; RFC-959 Section 5.1

Connected: An Internet Encyclopedia
4.1.2.12 Connections: RFC-959 Section 5.2