Movatterモバイル変換

• Domains
• Protocols
• Numbers
• About

Created

2010-01-07

Last Updated

2024-04-22

Available Formats

XML
HTML
Plain text

Registry Included Below

• FTP Commands and Extensions

FTP Commands and Extensions

Expert(s)

John Klensin

Reference

[RFC5797]

Note

Note: An IESG Standards Action is allowed to direct IANA to change theConformance Requirements listed for any entry. The following commands are part of the base FTP specification[RFC959] and are listed in the registry with the immutable pseudoFEAT code "base".Mandatory commands:ABOR, ACCT, ALLO, APPE, CWD, DELE, HELP, LIST, MODE, NLST, NOOP,PASS, PASV, PORT, QUIT, REIN, REST, RETR, RNFR, RNTO, SITE, STAT,STOR, STRU, TYPE, USEROptional commands:CDUP, MKD, PWD, RMD, SMNT, STOU, SYSTNote: STD 3 [RFC1123] clarified and updated the status andimplementation requirements of these standard FTP commands, and itcontains important complementary information for the followingcommands:LIST, NLST, PASV, REST, SITE, STOUThe following commands were specified as experimental in an extensionto an early version of the FTP specification [RFC775] but laterdeprecated by [RFC1123], because Standard FTP [RFC959]specifies their standard successors.  They are listed in the registrywith the immutable pseudo FEAT code "hist".XCUP, XCWD, XMKD, XPWD, XRMDImplementation note:  Deployed FTP clients still make use of thedeprecated commands and most FTP servers support them as aliasesfor the standard commands.The following commands were specified as part of the "FOOBAR" IPngeffort in [RFC1545] and, later, [RFC1639] and arenow obsolete.  They are listed in the registry with the immutablepseudo FEAT code "hist".LPRT, LPSVLegend for the registry:    o  cmd (Command Name)        Amended versions of commands are tagged with a trailing "+"    o  FEAT Code        Keyword returned in FEAT response line for this command/extension:          - actual FEAT codes are given in upper case          - placeholders (pseudo FEAT codes) are shown in lower case          - "-N/A-" indicates a feature not related to one particular command        See the "Extension name" clause in Section 2.2 of        [RFC5797] for details.    o  description        Brief description of command / extension    o  type (Command Type)        Type or "kind" of command, based on Section 4.1 of [RFC959]:          'a'  ... access control          'p'  ... parameter setting          's'  ... service execution        Combinations like 'p/s' are possible.    o  conf (Conformance Requirements)        Expectation for support in modern FTP implementations:          'm'  ... mandatory to implement          'o'  ... optional          'h'  ... historic

Available Formats

CSV

Footnotes

While an IETF Standards Action would be required to make the FEATmechanism [RFC2389] mandatory, implementation of that extensionmechanism is clearly required in conjunction with any extension orfeature that depends on it.

FEAT String for [RFC4217]: AUTH TLSFEAT String for [RFC2773]: AUTH KEA-SKIPJACK

FEAT String: REST STREAM

FEAT String: TYPE {semicolon-separated list of supported types}