RFC 4248: The telnet URI Scheme
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4248
- Published
- October 2005
- Authors
- P. Hoffman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 4
- Also known as
- —
- Obsoletes:
- RFC 1738
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1738 (1994)
- RFC 4248 (2005)
- RFC 4266 (2005) ✓
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4266The gopher URI SchemeCurrent
November 2005
- RFC 2295Transparent Content Negotiation in HTTPCurrent
March 1998
- RFC 8089The "file" URI SchemeUpdated
February 2017
- RFC 4246International Standard Audiovisual Number (ISAN) URN DefinitionCurrent
February 2006
- RFC 4157The prospero URI SchemeCurrent
August 2005
- RFC 4156The wais URI SchemeCurrent
August 2005
- RFC 4151The 'tag' URI SchemeCurrent
October 2005
- RFC 4395Guidelines and Registration Procedures for New URI SchemesObsoleted
February 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?