RFC 2389: Feature negotiation mechanism for the File Transfer Protocol
In plain English — editorial summary, not part of the RFC
This document provides a mechanism by which clients of the FTP protocol can discover which new features are supported by a particular FTP server. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2389
- Published
- August 1998
- Authors
- P. Hethmon; R. Elz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2428FTP Extensions for IPv6 and NATsCurrent
September 1998
- RFC 2640Internationalization of the File Transfer ProtocolCurrent
July 1999
- RFC 3659Extensions to FTPCurrent
March 2007
- RFC 2585Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTPCurrent
May 1999
- RFC 5854The Metalink Download Description FormatCurrent
June 2010
- RFC 6249Metalink/HTTP: Mirrors and HashesCurrent
June 2011
- RFC 2398Some Testing Tools for TCP ImplementorsCurrent
August 1998
- RFC 2228FTP Security ExtensionsCurrent
October 1997
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?