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 traditional tn3270 practices. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2355
- Published
- June 1998
- Authors
- B. Kelly
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 38
- Also known as
- —
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 2259Simple Nomenclator Query Protocol (SNQP)Current
January 1998
- 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 2639Internet Printing Protocol/1.0: Implementer's GuideObsoleted
July 1999
- RFC 2649An LDAP Control and Schema for Holding Operation SignaturesCurrent
August 1999
- RFC 2696LDAP Control Extension for Simple Paged Results ManipulationCurrent
September 1999
- RFC 28775250 Telnet EnhancementsObsoleted
July 2000
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?