Browse Prior Art Database

FTP Command and Extension Registry (RFC5797)

IP.com Disclosure Number: IPCOM000193828D
Original Publication Date: 2010-Mar-01
Included in the Prior Art Database: 2010-Mar-10
Document File: 20 page(s) / 25K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Klensin: AUTHOR [+2]

Abstract

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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 10% of the total text.

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 Registr...