Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updated by:

RFC 8996

Author:

P. Ford-Hutchinson

Stream:

IETF

Source:

NON WORKING GROUP

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC4217

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 4217

Abstract

This document describes a mechanism that can be used by FTP clientsand servers to implement security and authentication using the TLSprotocol defined by RFC 2246, "The TLS Protocol Version 1.0.", and theextensions to the FTP protocol defined by RFC 2228, "FTP Security Extensions".It describes the subset of the extensions that are required and theparameters to be used, discusses some of the policy issues thatclients and servers will need to take, considers some of theimplications of those policies, and discusses some expected behavioursof implementations to allow interoperation. This document is intendedto provide TLS support for FTP in a similar way to that provided forSMTP in RFC 2487, "SMTP Service Extension for Secure SMTP overTransport Layer Security", and HTTP in RFC 2817, "Upgrading to TLS WithinHTTP/1.1.".

This specification is in accordance with RFC 959, "File TransferProtocol". It relies on RFC 2246, "The TLS Protocol Version 1.0.", andRFC 2228, "FTP Security Extensions". [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.