FTP Command and Extension Registry
RFC 5797, “FTP Command and Extension Registry”, is a Proposed Standard document published in March 2010 by J. Klensin, A. Hoenes. It updates RFC 959. The canonical text is published by the RFC Editor.
Abstract
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]
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 5797 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5796 Authentication and Confidentiality in Protocol Independent Multicast Sparse Mode Link-Local Messages
- RFC 5798 Virtual Router Redundancy Protocol Version 3 for IPv4 and IPv6
- RFC 5795 The RObust Header Compression Framework
- RFC 5794 A Description of the ARIA Encryption Algorithm
- RFC 5793 PB-TNC: A Posture Broker Protocol Compatible with Trusted Network Connect
- RFC 5801 Using Generic Security Service Application Program Interface Mechanisms in Simple Authentication and Security Layer : The GS2 Mechanism Family
- RFC 5792 PA-TNC: A Posture Attribute Protocol Compatible with Trusted Network Connect
- RFC 5802 Salted Challenge Response Authentication Mechanism SASL and GSS-API Mechanisms