Recommendations for FTP Clients and Servers in the IPv6/IPv4 Transition Scenario
draft-liu-ftpext2-ftp64-00

Document Type Expired Internet-Draft (individual)
Last updated 2014-01-16 (latest revision 2013-07-15)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-liu-ftpext2-ftp64-00.txt

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 (liudapeng@chinamobile.com)
Iljitsch van Beijnum (iljitsch@muada.com)
Hui Deng (denghui@chinamobile.com)
Zhen Cao (caozhen@chinamobile.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)