Network Working Group P. Hoffman Internet-Draft VPN Consortium Expires: May 31, 2005 November 30, 2004 The telnet URI Scheme draft-hoffman-telnet-uri-03.txt Status of this Memo This document is an Internet-Draft and is subject to all provisions of section 3 of RFC 3667. 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 become aware will be disclosed, in accordance with RFC 3668. 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 May 31, 2005. Copyright Notice Copyright (C) The Internet Society (2004). Abstract This document specifies the telnet Uniform Resource Identifier (URI) scheme that was originally specified in RFC 1738. The purpose of this document is to allow RFC 1738 to be moved to historic while keeping the information about the scheme on standards track. 1. Introduction URIs were previously defined in RFC 2396 [RFC2396], which was updated Hoffman Expires May 31, 2005 [Page 1] Internet-Draft The telnet URI Scheme November 2004 by draft-fielding-uri-rfc2396bis [2396bis]. Those documents also specify how to define schemes for URIs. The first definition for many URI schemes appeared in RFC 1738 [RFC1738]. Because that document has been moved to Historic status, this document copies the telnet URI scheme from it to allow that material to remain on standards track. 2. Scheme Definition The Telnet URL scheme is used to designate interactive services that may be accessed by the Telnet protocol. A telnet URL takes the form: telnet://:@:/ The final "/" character may be omitted. If : is omitted, the port defaults to 23. The : can be omitted, as well as the whole : part. Few implementations handle the user name and password very well, if at all. This URL does not designate a data object, but rather an interactive service. Remote interactive services vary widely in the means by which they allow remote logins; in practice, the and supplied are advisory only: clients accessing a telnet URL merely advise the user of the suggested username and password. 3. Security Considerations There are many security considerations for URI schemes discussed in [2396bis]. The telnet protocol uses passwords in the clear for authentication, and offers no privacy, both of which are considered extremely unsafe in current practice. 4 Informative References [RFC1738] Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform Resource Locators (URL)", RFC 1738, December 1994. [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998. [2396bis] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", work in progress, draft-fielding-uri-rfc2396bis-nn.txt. Hoffman Expires May 31, 2005 [Page 2] Internet-Draft The telnet URI Scheme November 2004 Author's Address Paul Hoffman VPN Consortium 127 Segre Place Santa Cruz, CA 95060 US EMail: paul.hoffman@vpnc.org Hoffman Expires May 31, 2005 [Page 3] Internet-Draft The telnet URI Scheme November 2004 Intellectual Property Statement 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. Disclaimer of Validity 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 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. Copyright Statement Copyright (C) The Internet Society (2004). 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. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Hoffman Expires May 31, 2005 [Page 4]