Network Working Group J. Klensin Internet-Draft August 21, 2009 Updates: 959 (if approved) Intended status: Standards Track Expires: February 22, 2010 FTP Extension Registry draft-klensin-ftp-registry-01.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on February 22, 2010. Copyright Notice Copyright (c) 2009 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 in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. 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 Klensin Expires February 22, 2010 [Page 1]
Internet-Draft FTP Extension Registry August 2009 mechanism for specifying and negotiating FTP extensions. As the number of those extensions increases, it appears useful to establish an IANA registry to reduce the likelihood of conflict of names and the consequent ambiguity. This specification establishes that registry. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Discussion List . . . . . . . . . . . . . . . . . . . . . . 3 2. Registry Definition . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Registry Name . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Registry Format . . . . . . . . . . . . . . . . . . . . . . 3 2.3. Criteria for Registration . . . . . . . . . . . . . . . . . 4 2.4. Initial Contents of Registry . . . . . . . . . . . . . . . 4 3. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6.1. Normative References . . . . . . . . . . . . . . . . . . . 5 6.2. Informative References . . . . . . . . . . . . . . . . . . 5 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . . 5 A.1. Changes in Version-01 . . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 Klensin Expires February 22, 2010 [Page 2]
Internet-Draft FTP Extension Registry August 2009 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 [RFC0959]. As the number of those extensions increases, it appears useful to establish an IANA registry to reduce the likelihood of conflict of names and the consequent ambiguity. This specification establishes that registry. 1.1. Discussion List [[anchor3: RFC Editor: please remove this section before publication.]] Until and unless a WG is created, this proposal will be discussed on the list apps-discuss@ietf.org 2. Registry Definition 2.1. Registry Name The recommended name of this registry is "FTP Extensions". 2.2. Registry Format IANA is requested to establish an FTP extensions registry whose entries should include the following: Command Name The FTP command, either new or modified, used in the extension. Description A brief description of the extension. Parameters A listing and brief description of any parameters associated with the extension. FEAT String The string expected to be included in the response to the FEAT command (see RFC 2389) if the extension is supported. Reference A reference to an RFC or other definition of the extension and/or to implementations supporting it (see the next section). Klensin Expires February 22, 2010 [Page 3]
Internet-Draft FTP Extension Registry August 2009 2.3. Criteria for Registration This registry is primarily intended to avoid conflicting uses of the same extension names and keywords for different purposes, not to demonstrate that an extension is somehow "approved". The "expert review" method will be used, but the designated expert is expected to check only that one of the two criterial that follow are met. 1. The extension is described in an RFC or other generally-available publication for which the fact of publication indicates some level of peer review of document quality. 2. The extension is actually implemented in FTP client and server systems that are generally available (not necessarily either free or unencumbered, but available) and those systems are identified as part of the documentation requirement above. 2.4. Initial Contents of Registry ... ??? List to be supplied. Volunteers to help with the work are urgently sought. ... 3. Acknowledgments Any work to update or extend FTP depends on the base specification in RFC 959. The contributions of its editors, Jon Postel and Joyce Reynolds, are gratefully acknowledged. The option negotiation mechanism specified in RFC 2389 and the accumulation of features that has followed it made this registry relevant; the authors of those documents are acknowledged as well. 4. IANA Considerations IANA is requested to establish the registry described in Section 2. New entries should be added to this registry when extensions to FTP are approved or defined in published RFCs. In other words, the requirement for registration is "RFC Required" [RFC5226]. [[anchor8: Note in Draft: Is there any reason to cut this back to "Specification Required" and specify a Designated Expert process?]] 5. Security Considerations The creation of this registry provides improved documentation and protection against interoperability problems. It introduces no new Klensin Expires February 22, 2010 [Page 4]
Internet-Draft FTP Extension Registry August 2009 security issues. 6. References 6.1. Normative References [RFC0959] Postel, J. and J. Reynolds, "File Transfer Protocol", STD 9, RFC 959, October 1985. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. 6.2. Informative References [RFC2389] Hethmon, P. and R. Elz, "Feature negotiation mechanism for the File Transfer Protocol", RFC 2389, August 1998. Appendix A. Change Log A.1. Changes in Version-01 Updated document to reflect new date and IPR statement. Author's Address John C Klensin 1770 Massachusetts Ave, Ste 322 Cambridge, MA 02140 USA Phone: +1 617 245 1457 Email: john+ietf@jck.com Klensin Expires February 22, 2010 [Page 5]
