File Transfer Protocol LOCK Command for Using a Single Port
draft-bryan-ftp-lock-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Tatsuhiro Tsujikawa , Daniel Stenberg , Anthony Bryan | ||
| Last updated | 2011-06-07 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
One of the biggest hurdles for FTP in real life usage is its use of two connections. First, it uses a primary connection to send control commands on, and when it sends or receives data, it opens a second TCP stream for that purpose. This document specifies a new FTP LOCK command to be used by clients to request the server to use the control connection for data transfers, using a single port instead of two.
Authors
Tatsuhiro Tsujikawa
Daniel Stenberg
Anthony Bryan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)