Browse Prior Art Database

TN3270 Enhancements (RFC2355)

IP.com Disclosure Number: IPCOM000002925D
Original Publication Date: 1998-Jun-01
Included in the Prior Art Database: 2019-Feb-15
Document File: 38 page(s) / 51K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Kelly: AUTHOR

Related Documents

10.17487/RFC2355: DOI

Abstract

This document describes a protocol that more fully supports 3270 devices than do traditional tn3270 practices. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 5% of the total text.

Network Working Group B. Kelly Request for Comments: 2355 Auburn University Obsoletes: 1647 June 1998 Category: Standards Track

TN3270 Enhancements

Status of this Memo

This document 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 Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

Abstract

This document describes a protocol that more fully supports 3270 devices than do traditional tn3270 practices. Specifically, it defines a method of emulating both the terminal and printer members of the 3270 family of devices via Telnet; it provides for the ability of a Telnet client to request that it be assigned a specific device- name (also referred to as "LU name" or "network name"); finally, it adds support for a variety of functions such as the ATTN key, the SYSREQ key, and SNA response handling.

This protocol is negotiated under the TN3270E Telnet Option, and is unrelated to the Telnet 3270 Regime Option as defined in RFC 1041 [1].

TABLE OF CONTENTS

1. Introduction ............................................... 2 1.1 Changes to RFC 1647 .................................... 4 2. TN3270E OVERVIEW ........................................... 5 3. COMMAND NAMES AND CODES .................................... 6 4. COMMAND MEANINGS ........................................... 7 5. DEFAULT SPECIFICATION ...................................... 9 6. MOTIVATION ................................................. 9 7. TN3270E SUB-NEGOTIATION RULES .............................. 9 7.1 DEVICE-TYPE Negotiation ................................ 9 7.1.1 Device Pools ...................................... 10 7.1.2 CONNECT Command ................................... 12

Kelly Standards Track [Page 1]

RFC 2355 TN3270 Enhancements June 1998

7.1.3 ASSOCIATE Command ................................. 12 7.1.4 Accepting a Request ............................... 13 7.1.5 REJECT Command .................................... 13 7.2 FUNCTIONS Negotiation .................................. 14 7.2.1 Commands .......................................... 14 7.2.2 List of TN3270E Functions ......................... 16 8. TN3270E DATA MESSAGES ...................................... 16 8.1 The TN3270E Message Header ............................. 18 8.1.1 DATA-TYPE Field ................................... 18 8.1.2 REQUEST-FLAG Field ................................ 19 8.1.3 RESPONSE-FLAG Field ............................... 19 8.1.4 SEQ-NUMBER Field .................................. 20 9. BASIC TN3270E .............................................. 20 9.1 3270 Mode and NVT Mode ................................. 21 10. DETAILS OF PROCESSING TN3270E FUNCTIONS .................... 22 10.1 The SCS-C...

Processing...
Loading...