The telnet URI Scheme (RFC4248)
Original Publication Date: 2005-Oct-01
Included in the Prior Art Database: 2005-Oct-28
Internet Society Requests For Comment (RFCs)
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 made obsolete while keeping the information about the scheme on standards track.
Network Working Group P.
Request for Comments: 4248 VPN Consortium
Obsoletes: 1738 October 2005
Category: Standards Track
The telnet URI Scheme
Status of this Memo
specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright (C) The Internet Society (2005).
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 made obsolete while keeping
the information about the scheme on standards track.
previously defined in [RFC2396], which was updated by
[RFC3986]. Those documents also specify how to define schemes for
definition for many URI schemes appeared in [RFC1738].
Because that document has been made obsolete, this document copies
the telnet URI scheme from it to allow that material to remain on
2. Scheme Definition
The Telnet URL
scheme is used to designate interactive services that
may be accessed by the Telnet protocol [STD8].
A telnet URL takes the form:
Hoffman Standards Track [Page 1]
RFC 4248 The telnet URI Scheme October 2005
The final "/" character may be omitted. If :<port> is omitted, the
port defaults to 23. The :<password> can be omitted, as well as the
whole <user>:<password> 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 <user> and
<password> supplied are advisory only: clients accessing a telnet URL
merely advise the user of the suggested username and password.
Many RFCs have
added various services to the Telnet protocol for
better authentication, encryption of traffic, or both. Those RFCs
have not specified new URI schemes for Telnet to invoke those
services (along the lines of "https" being a different URI scheme
from "http"). Some modern telnet clients attempt to invoke those