datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

FTP Command and Extension Registry
RFC 5797

Document type: RFC - Proposed Standard (March 2010; Errata)
Updates RFC 959
Was draft-klensin-ftp-registry (individual in app area)
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 5797 (Proposed Standard)
Responsible AD: Alexey Melnikov
Send notices to: john+ietf@jck.com, ah@tr-sys.de, barryleiba@computer.org

Internet Engineering Task Force (IETF)                        J. Klensin
Request for Comments: 5797
Updates: 959                                                   A. Hoenes
Category: Standards Track                                         TR-Sys
ISSN: 2070-1721                                               March 2010

                   FTP Command and Extension Registry

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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc5797.

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Klensin & Hoenes             Standards Track                    [Page 1]
RFC 5797           FTP Command and Extension Registry         March 2010

Table of Contents

   1. Introduction ....................................................2
   2. Registry Definition .............................................2
      2.1. Registry Name ..............................................2
      2.2. Registry Format ............................................2
      2.3. Criteria for Registration ..................................4
      2.4. Base FTP Commands ..........................................5
      2.5. Obsolete Commands ..........................................5
   3. Initial Contents of Registry ....................................6
   4. Acknowledgments .................................................8
   5. IANA Considerations .............................................9
   6. Security Considerations .........................................9
   7. References ......................................................9
      7.1. Normative References .......................................9
      7.2. Informative References .....................................9

1.  Introduction

   Every version of the FTP specification has added a few new commands,
   with the early ones summarized in RFC 959 [RFC0959].  RFC 2389
   [RFC2389] established a mechanism for specifying and negotiating
   extensions to the FTP protocol specified in RFC 959, by means of
   "FEAT Strings" identifying extensions supported by the FTP server,
   and sent in response to a "FEAT" command.  The number of extensions
   continues to grow, not all of them supported by FEAT.  An IANA
   registry is established to reduce the likelihood of a conflict of
   names and the consequent ambiguity and to encourage the sharing of
   information.  This specification establishes that registry.

2.  Registry Definition

2.1.  Registry Name

   The name of this registry is "FTP Commands and Extensions".

2.2.  Registry Format

   As specified in this RFC, IANA has established a registry for FTP
   commands and extensions.  Registration requests and registry entries
   should include the following:

   Command Name -  The FTP command, either new or modified, used in the
      extension or with which the extension is used.

      Following the long-standing practice to capitalize command names
      in specification documents for FTP, the command names are entered
      in all uppercase.  For extensions amending the operation of a

[include full document text]