| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
FTP Internal Protocol Commands and Command Groups (Page 1 of 2) An FTP session begins with the establishment of a TCP connection from an FTP client (user device) to an FTP server. Once established, the control channel is logically in place between the Server-PI and the User-PI. All communication to manage the operation of the protocol takes place over this channel. The User-PI sends protocol commands to the Server-PI, which processes them and takes appropriate action. The Server-PI responds back with reply codes to tell the User-PI the result of the commands it issued and convey other important information. Each command is identified by a short three-letter or four-letter command code for convenience, and performs a specific task in the overall functionality of FTP. There are several dozen of these protocol commands, and to help organize them, the FTP standard categorizes them into three groups, based on overall function type:
Interestingly, the actual transmission of FTP commands over the control channel is done using specifications based on the Telnet protocol. You may recall from the FTP overview that Telnet and FTP are two of the very oldest TCP/IP applications, the former being for direct network use and the latter for indirect resource access. They were developed at around the same time, and setting up the FTP control channel to act as a type of Telnet connection is a good example of how Internet standards try not to reinvent the wheel.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||