RFC 6270: The 'tn3270' URI Scheme
In plain English — editorial summary, not part of the RFC
This document is the specification of the 'tn3270' Uniform Resource Identifier (URI) scheme, which is used to designate the access to the resources available via Telnet 3270 mode (TN3270) and Telnet 3270 Enhanced mode (TN3270E). It updates RFC 1041 and RFC 2355, which specify these protocols, and RFC 1738, which firstly mentioned this URI scheme without defining its syntax and semantics. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6270
- Published
- June 2011
- Authors
- M. Yevstifeyev
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6196Moving mailserver: URI Scheme to HistoricCurrent
March 2011
- RFC 6570URI TemplateCurrent
March 2012
- RFC 5870A Uniform Resource Identifier for Geographic Locations ('geo' URI)Current
June 2010
- RFC 6920Naming Things with HashesCurrent
April 2013
- RFC 5122Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)Current
February 2008
- RFC 5028A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) ServicesUpdated
October 2007
- RFC 7565The 'acct' URI SchemeCurrent
May 2015
- RFC 4769IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling InformationUpdated
November 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?