Network Working Group J. Klensin Internet-Draft July 28, 2008 Updates: 959 (if approved) Intended status: Standards Track Expires: January 29, 2009 FTP Extension Registry draft-klensin-ftp-registry-00.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of 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 January 29, 2009. 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. 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. Klensin Expires January 29, 2009 [Page 1] Internet-Draft FTP Extension Registry July 2008 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. Initial Contents of Registry . . . . . . . . . . . . . . . 4 3. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 6.2. Informative References . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 Intellectual Property and Copyright Statements . . . . . . . . . . 6 Klensin Expires January 29, 2009 [Page 2] Internet-Draft FTP Extension Registry July 2008 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. Klensin Expires January 29, 2009 [Page 3] Internet-Draft FTP Extension Registry July 2008 2.3. Initial Contents of Registry ... ??? To be supplied ... 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]. [[anchor7: 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 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. Klensin Expires January 29, 2009 [Page 4] Internet-Draft FTP Extension Registry July 2008 6.2. Informative References [RFC2389] Hethmon, P. and R. Elz, "Feature negotiation mechanism for the File Transfer Protocol", RFC 2389, August 1998. 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 January 29, 2009 [Page 5] Internet-Draft FTP Extension Registry July 2008 Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Klensin Expires January 29, 2009 [Page 6]