An FTP Application Layer Gateway for IPv6-to-IPv4 Translation
RFC 6384, “An FTP Application Layer Gateway for IPv6-to-IPv4 Translation”, is a Proposed Standard document published in October 2011 by I. van Beijnum. The canonical text is published by the RFC Editor.
Abstract
The File Transfer Protocol (FTP) has a very long history, and despite the fact that today other options exist to perform file transfers, FTP is still in common use. As such, in situations where some client computers only have IPv6 connectivity while many servers are still IPv4-only and IPv6-to-IPv4 translators are used to bridge that gap, it is important that FTP is made to work through these translators to the best possible extent.
FTP has an active and a passive mode, both as original commands that are IPv4-specific and as extended, IP version agnostic commands. The only FTP mode that works without changes through an IPv6-to-IPv4 translator is extended passive. However, many existing FTP servers do not support this mode, and some clients do not ask for it. This document specifies a middlebox that may solve this mismatch. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6384 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6383 Advice on When It Is Safe to Start Sending Data on Label Switched Paths Established Using RSVP-TE
- RFC 6385 General Area Review Team Experiences
- RFC 6382 Unique Origin Autonomous System Numbers per Node for Globally Anycasted Services
- RFC 6386 VP8 Data Format and Decoding Guide
- RFC 6381 The 'Codecs' and 'Profiles' Parameters for "Bucket" Media Types
- RFC 6387 GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths
- RFC 6380 Suite B Profile for Internet Protocol Security
- RFC 6388 Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths