CurrentPROPOSED STANDARDIETF stream

RFC 5797: FTP Command and Extension Registry

In plain English — editorial summary, not part of the RFC

Every version of the FTP specification has added a few new commands, with the early ones summarized in RFC 959. RFC 2389 established a mechanism for specifying and negotiating FTP extensions. The number of extensions, both those supported by the mechanism and some that are not, continues to increase. An IANA registry of FTP Command and Feature names is established to reduce the likelihood of conflict of names and the consequent ambiguity. This specification establishes that registry. [STANDARDS-TRACK]

Document record

Document ID
RFC5797
Published
March 2010
Authors
J. Klensin; A. Hoenes
Status
PROPOSED STANDARD
Stream
IETF
Area
Pages
10
Also known as
Updates:
RFC 959

Topics

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?

canonical URL: /rfc/5797-ftp-command-and-extension-registry