FTP consideration for IPv4/IPv6 transition
draft-ietf-ftpext2-ftp64-02

 
Document Type Expired Internet-Draft (individual)
Last updated 2012-07-14 (latest revision 2012-01-11)
Replaces draft-liu-ftp64-extension
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
plain text pdf html
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired (IESG: Dead)
Telechat date
Responsible AD Pete Resnick
Send notices to ftpext2-chairs@ietf.org, draft-ietf-ftpext2-ftp64@ietf.org

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-ietf-ftpext2-ftp64-02.txt

Abstract

The File transfer protocol(FTP) has a long histroy,, but still being widely used. The first concept of FTP was described RFC 114, and then was specified in RFC 354. FTP can work in IPv4 environment and then was extended to IPv6. RFC 2428 defines IPv6 extensions of FTP. In the IPv6-IPv4 translation scenario, considerations should be applied to FTP client, server and translation box to ensure FTP protocol work properly. This document discusses the details for FTP to work in IPv4-IPv6 transitiion scenario. This document gives recommendation regarding how IPv6 FTP client should behave in 6to4 scenario.

Authors

Dapeng Liu (liudapeng@chinamobile.com)
Iljitsch van Beijnum (iljitsch@muada.com)
Zhen Cao (caozhen@chinamobile.com)

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