Recommendations for FTP Clients and Servers in the IPv6/IPv4 Transition Scenario
draft-liu-ftpext2-ftp64-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dapeng Liu , Iljitsch van Beijnum , DENG Hui , Zhen Cao | ||
| Last updated | 2014-01-16 (Latest revision 2013-07-15) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
The File transfer protocol, which was originally defined in RFC 114 and published in 1971, well before TCP and IP were created. However, it is still in wide use. Many FTP servers implement RFC 959, which requires IPv4. RFC 2428 defines extensions that allow FTP to work over IPv6 by introducing the EPRT and EPSV commands. When IPv6 FTP clients attempt to communicate with IPv4 FTP servers through an IPv6-IPv4 translator, only certain combinations of FTP client and server behavior lead to successful file transfers. This document proposes the best current practice for IPv6 FTP client implementations in the IPv6-IPv4 translation scenario, allowing file transfers to succeed without the presence of an ALG (Application Layer Gateway).
Authors
Dapeng Liu
Iljitsch van Beijnum
DENG Hui
Zhen Cao
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)