RFC 1647: TN3270 Enhancements
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2355.
Current version: RFC 2355 — TN3270 Enhancements
In plain English — editorial summary, not part of the RFC
This document describes a protocol that more fully supports 3270 devices than do the existing tn3270 practices. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1647
- Published
- July 1994
- Authors
- B. Kelly
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 34
- Also known as
- —
- Obsoleted by:
- RFC 2355
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1646TN3270 Extensions for LUname and Printer SelectionCurrent
July 1994
- RFC 1412Telnet Authentication: SPXCurrent
January 1993
- RFC 1411Telnet Authentication: Kerberos Version 4Current
January 1993
- RFC 2561Base Definitions of Managed Objects for TN3270E Using SMIv2Current
April 1999
- RFC 2562Definitions of Protocol and Managed Objects for TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB)Current
April 1999
- RFC 2949Telnet Encryption: CAST-128 64 bit Output FeedbackCurrent
September 2000
- RFC 2950Telnet Encryption: CAST-128 64 bit Cipher FeedbackCurrent
September 2000
- RFC 6270The 'tn3270' URI SchemeCurrent
June 2011
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?