FTP consideration for IPv4/IPv6 transition
draft-ietf-ftpext2-ftp64-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Dapeng Liu , Iljitsch van Beijnum , Zhen Cao | ||
Last updated | 2015-10-14 (Latest revision 2012-01-11) | ||
Replaces | draft-liu-ftp64-extension | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Proposed Standard | ||
Formats | |||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired (IESG: Dead) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Pete Resnick | ||
Send notices to | ftpext2-chairs@ietf.org |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Iljitsch van Beijnum
Zhen Cao
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)