Debian Codegraph @

rfc1576.html

raw
1 <pre>Network Working Group J. Penner
2 Request for Comments: 1576 DCA, Inc.
3 Category: Informational January 1994
4
5
6 <span class="h1">TN3270 Current Practices</span>
7
8 Status of this Memo
9
10 This memo provides information for the Internet community. This memo
11 does not specify an Internet standard of any kind. Distribution of
12 this memo is unlimited.
13
14 Abstract
15
16 This document describes the existing implementation of transferring
17 3270 display terminal data using currently available telnet
18 capabilities. The name traditionally associated with this
19 implementation is TN3270.
20
21 Information is provided to aid in the implementation of TN3270
22 servers as well as client terminal emulators.
23
24 The following areas pertaining to TN3270 implementations are covered
25 in this document:
26
27 1. the telnet options negotiated to transition from a NVT ASCII
28 state to a TN3270 state ready to process incoming 3270 data
29 stream commands
30
31 2. the method for sending and receiving 3270 data
32
33 3. the method of handling some special keys known as SYSREQ and
34 ATTN using current available telnet commands
35
36 4. the events that will transition a TN3270 session back to an NVT
37 session
38
39 Table of Contents
40
41 <a href="#section-1">1</a>. Motivation . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
42 <a href="#section-2">2</a>. Background . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
43 <a href="#section-3">3</a>. Telnet Options and Commands Used . . . . . . . . <a href="#page-4">4</a>
44 <a href="#section-4">4</a>. Connection Negotiation . . . . . . . . . . . . . <a href="#page-4">4</a>
45 <a href="#section-4.1">4.1</a> 3270 Regime Option . . . . . . . . . . . . . . . <a href="#page-6">6</a>
46 <a href="#section-4.2">4.2</a> Suppress Go Ahead Option . . . . . . . . . . . . <a href="#page-6">6</a>
47 <a href="#section-4.3">4.3</a> Echo Option . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
48 <a href="#section-4.4">4.4</a> Timing Mark Option . . . . . . . . . . . . . . . <a href="#page-7">7</a>
49
50
51
52 <span class="grey">TN3270 Enhancements Working Group [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1576">RFC 1576</a> TN3270 Current Practices January 1994</span>
55
56
57 <a href="#section-5">5</a>. Testing for session presence . . . . . . . . . . <a href="#page-7">7</a>
58 <a href="#section-6">6</a>. Handling 3270 data . . . . . . . . . . . . . . . <a href="#page-7">7</a>
59 <a href="#section-7">7</a>. 3270 Structured Fields . . . . . . . . . . . . . <a href="#page-8">8</a>
60 <a href="#section-8">8</a>. The 3270 ATTN (Attention) Key . . . . . . . . . . <a href="#page-8">8</a>
61 <a href="#section-9">9</a>. The 3270 SYSREQ Key . . . . . . . . . . . . . . . <a href="#page-9">9</a>
62 <a href="#section-10">10</a>. Items not addressed by TN3270 . . . . . . . . . . <a href="#page-10">10</a>
63 <a href="#section-11">11</a>. References . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
64 <a href="#section-12">12</a>. Security Considerations . . . . . . . . . . . . . <a href="#page-11">11</a>
65 <a href="#section-13">13</a>. Author's Note . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
66 <a href="#section-14">14</a>. Author's Address . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
67
68 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Motivation</span>
69
70 3270 display terminal data differs from traditional display terminal
71 data in that it is block mode and uses EBCDIC instead of ASCII
72 character representation. These two differences are the primary
73 reason for the differentiation of TN3270 from standard Telnet in this
74 document.
75
76 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Background</span>
77
78 Existing complex IBM 3270 display terminal networks are not easily
79 integrated with the increasing number of multi-platform networking
80 environments, specifically TCP/IP. These complex networks include
81 terminals attached to a 3270 host using SNA (Systems Network
82 Architecture) and non-SNA connections. To address the issue of easily
83 connecting display terminals to 3270 hosts using IP networks, several
84 vendors have introduced telnet servers that provide TCP/IP users a
85 connection to existing IBM mainframes by supporting display terminal
86 emulation using a subset of the existing telnet protocol. Telnet
87 servers may exist on the host itself, or be connected to the host
88 using SNA or non-SNA methods.
89
90 IBM terminals are generically referred to as 3270's which includes a
91 broad range of terminals and devices, not all of which actually begin
92 with the numbers 327x.
93
94 3270 terminals in the IBM SNA network environment have two sessions
95 with the host computer application. One is used for communicating
96 with the host application, the other is used for communicating with
97 the SSCP (System Services Control Point) that links the terminal with
98 the appropriate host computer. For the purposes of TN3270, this
99 distinction is not apparent or relevant since there is actually only
100 a single telnet session with the host computer or server. On an IBM
101 SNA network, the 3270 terminal has a special key that toggles between
102 the two sessions (SYSREQ). A brief discussion on how some telnet
103 servers deal with this is included.
104
105
106
107
108 <span class="grey">TN3270 Enhancements Working Group [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1576">RFC 1576</a> TN3270 Current Practices January 1994</span>
111
112
113 In an SNA environment, a client session is identified by a Logical
114 Unit (LU) name. In a non-SNA environment, there is not a LU name
115 associated with a client session. The closest thing to a LU name in
116 the TN3270 environment is the client's IP address. Although some
117 telnet servers are connected to the host using SNA, TN3270 clients
118 using these servers have no defined way to determine the LU name
119 associated with the session.
120
121 Telnet servers that exist in non-SNA environments do not have to be
122 concerned about providing TN3270 clients with support for the SNA
123 functions described in this document.
124
125 TN3270 does not support typical SNA responses and is classified as a
126 non-SNA protocol. A TN3270 emulator is not aware or concerned about
127 how the telnet server is connected to a 3270 host application.
128
129 NOTE: Except where otherwise stated, this document does not
130 distinguish between telnet servers that represent SNA devices and
131 those that represent non-SNA 3270 devices.
132
133 Some typical "SNA" functions such as the SYSREQ and ATTN keys have
134 been mapped to existing telnet commands and are supported by some
135 telnet server implementations.
136
137 Currently, support for 3270 terminal emulation over Telnet is
138 accomplished by the de facto standard of negotiating three separate
139 Telnet Options - Terminal-Type [<a href="#ref-2" title="&quot;Telnet Terminal-Type Option&quot;">2</a>], Binary Transmission [<a href="#ref-3" title="&quot;Telnet Binary Transmission&quot;">3</a>], and End
140 of Record [<a href="#ref-4" title="&quot;Telnet End of Record Option&quot;">4</a>]. This negotiation and the resulting data flow will be
141 described below.
142
143 <a href="./rfc1041">RFC 1041</a> [<a href="#ref-1" title="&quot;Telnet 3270 Regime Option&quot;">1</a>] attempted to standardize the method of negotiating 3270
144 terminal support by defining the 3270 Regime Telnet Option.
145 Historically, very few developers and vendors ever implemented <a href="./rfc1041">RFC</a>
146 <a href="./rfc1041">1041</a>.
147
148 All references in this document to the 3270 datastream, SNA versus
149 non-SNA operation, 3270 datastream commands, orders, structured
150 fields and the like rely on [<a href="#ref-6" title="&quot;3270 Information Display System - Data Stream Programmer's Reference&quot;">6</a>].
151
152 References to SNA Request and Response Units rely on [<a href="#ref-7" title="&quot;Systems Network Architecture - Formats&quot;">7</a>]. References
153 to SNA and SSCP rely on [<a href="#ref-12" title="&quot;Systems Network Architecture - Concepts and Products&quot;">12</a>].
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">TN3270 Enhancements Working Group [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1576">RFC 1576</a> TN3270 Current Practices January 1994</span>
167
168
169 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Telnet Options and Commands Used</span>
170
171 TN3270 makes use of existing Telnet options and does not define any
172 additional options or commands.
173
174 Telnet option Value (decimal)
175 ------------- ---------------
176 BINARY 0
177 TERMINAL-TYPE 24
178 EOR 25
179
180 Additional options may be used during a TN3270 session and are
181 interpreted as per their respective RFCs. These are [<a href="#ref-1" title="&quot;Telnet 3270 Regime Option&quot;">1</a>] 3270-REGIME,
182 [<a href="#ref-8" title="&quot;Telnet Suppress Go Ahead Option&quot;">8</a>] SUPPRESS-GO-AHEAD, [<a href="#ref-9" title="&quot;Telnet Echo Option&quot;">9</a>] ECHO and [<a href="#ref-10" title="&quot;Telnet Timing Mark Option&quot;">10</a>] TIMING-MARK. Other options
183 should be rejected unless they are specifically handled by the client
184 for NVT mode.
185
186 Commands that may be encountered during a TN3270 session and are
187 described in <a href="./rfc854">RFC 854</a> [<a href="#ref-11" title="&quot;Telnet Protocol Specification&quot;">11</a>] include NOP, BREAK and Interrupt Process.
188
189 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Connection Negotiation</span>
190
191 The following example shows a TN3270-capable server and a TN3270
192 client establishing a connection:
193
194 The TCP/IP port used to connect with is 23 (Telnet).
195
196 At any place before and during the TN3270 connection negotiation
197 process, other telnet commands and data may be transferred and will
198 be interpreted under the existing telnet state. Some existing TN3270
199 servers start a client connection using an NVT telnet dialog to
200 establish parameters needed to complete the TN3270 connection to the
201 desired host.
202
203 The order of negotiating terminal type, EOR and BINARY is not
204 significant, this example shows a typical TN3270 connection.
205
206 Server: IAC DO TERMINAL-TYPE
207
208 Client: IAC WILL TERMINAL-TYPE
209
210 Server: IAC SB TERMINAL-TYPE SEND IAC SE
211
212 Client: IAC SB TERMINAL-TYPE IS &lt;terminal type&gt;IAC SE
213
214 where &lt;terminal type&gt; is a string consisting of terminal model,
215 type and support of enhanced attribute bytes; an example is IBM-
216 3278-2. The acceptable values are listed in <a href="./rfc1340">RFC 1340</a>, Assigned
217
218
219
220 <span class="grey">TN3270 Enhancements Working Group [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1576">RFC 1576</a> TN3270 Current Practices January 1994</span>
223
224
225 Numbers [<a href="#ref-5" title="&quot;Assigned Numbers&quot;">5</a>]. Other values are in use that do not exist in [<a href="#ref-5" title="&quot;Assigned Numbers&quot;">5</a>].
226
227 The -2 following 3278 designates the alternate screen size. 3270
228 terminals have the ability to switch between the standard (24x80)
229 screen size and an alternate screen size. Model -2 is 24x80 which
230 is the same as the standard size. Model -3 is 32x80, model -4 is
231 43x80 and model -5 is 27x132.
232
233 Appending the two character string "-E" to the end of the terminal
234 type signifies that the terminal is capable of handling 3270
235 extended data stream. This is interpreted to mean that the
236 terminal is able to handle structured fields, which are described
237 below. Some telnet server implementations also interpret this to
238 mean that the terminal is capable of handling extended attributes
239 (highlighting, field validation, character set, outlining, etc.)
240 [<a href="#ref-6" title="&quot;3270 Information Display System - Data Stream Programmer's Reference&quot;">6</a>].
241
242 The 3279 series of terminals is capable of extended attributes
243 while the 3278 series is not.
244
245 Server: IAC DO EOR IAC WILL EOR
246 Client: IAC WILL EOR IAC DO EOR
247 Server: IAC DO BINARY IAC WILL BINARY
248 Client: IAC WILL BINARY IAC DO BINARY
249 Server: &lt;3270 data stream&gt; IAC EOR
250 Client: &lt;3270 data stream&gt; IAC EOR
251 . .
252 . .
253
254 To terminate the connection the socket is closed by one of the
255 session partners. Typically, when the user logs off of the host, the
256 telnet server closes the connection.
257
258 If the telnet server wishes to go back to NVT mode, it may issue the
259 following telnet options:
260
261 Server: IAC WONT BINARY
262 Client: IAC DONT BINARY
263
264 or
265
266 Server: IAC WONT EOR
267 Client: IAC DONT EOR
268
269 Either one of the above two cases causes the connection to not
270 satisfy the requirements for a valid TN3270 session. The telnet
271 client would then process data from the server as though it were NVT
272 ASCII data.
273
274
275
276 <span class="grey">TN3270 Enhancements Working Group [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1576">RFC 1576</a> TN3270 Current Practices January 1994</span>
279
280
281 The following examples show how a TN3270 client handles the 3270-
282 REGIME, SUPPRESS-GO-AHEAD, ECHO and TM options.
283
284 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> 3270 Regime Option</span>
285
286 Very few servers support the 3270 Regime Telnet Option. If the
287 client does not support this option and responds negatively as shown
288 in the following example, the server will proceed on to the more
289 typical example shown above.
290
291 Server: IAC DO 3270-REGIME
292 Client: IAC WONT 3270-REGIME
293 Normal negotiation:
294 Server: IAC DO TERMINAL-TYPE
295 ... (see above)
296
297 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> Suppress Go Ahead Option</span>
298
299 The Suppress Go Ahead option [<a href="#ref-8" title="&quot;Telnet Suppress Go Ahead Option&quot;">8</a>] is requested by some servers. The
300 Suppress Go Ahead option RFC lists the default as being go aheads are
301 transmitted to signal the receiver to begin transmitting. Since
302 TN3270 negotiates binary and end-of-record and is a block mode
303 protocol, the telnet go ahead character is not sent. Most servers do
304 not negotiate this option even though they do not use the telnet go
305 ahead character.
306
307 Server: IAC DO SUPPRESS-GO-AHEAD
308 Client: IAC WILL SUPPESS-GO-AHEAD
309
310 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a> Echo Option</span>
311
312 The Echo option [<a href="#ref-9" title="&quot;Telnet Echo Option&quot;">9</a>] is negotiated by those servers that make use of
313 the telnet NVT mode to allow the user to enter information prior to
314 negotiating the options necessary for TN3270. This information
315 includes but is not limited to user identification, password and
316 destination 3270 host. Some servers accept the default for this
317 option which is for the client to not do a local echo of characters
318 the user enters at the keyboard. This allows the server to decide if
319 it should echo characters back to the client (or not in the case of
320 password). Echoing characters back to the client causes slow response
321 time since every character is typically echoed individually. Because
322 of this, some servers negotiate for the client to do it's own local
323 echoing (except for passwords). The following example illustrates
324 this case.
325
326
327
328
329
330
331
332 <span class="grey">TN3270 Enhancements Working Group [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1576">RFC 1576</a> TN3270 Current Practices January 1994</span>
335
336
337 Server: IAC DO ECHO
338 Client: IAC WILL ECHO
339 (Client does local display of all characters)
340 Server: IAC WONT ECHO
341 Client: IAC DONT ECHO
342 (Client enters password - not locally displayed or remotely
343 echoed)
344 Server: IAC DO ECHO
345 Client: IAC WILL ECHO
346 (Client resumes local display of all characters)
347
348 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a> Timing Mark Option</span>
349
350 The Timing Mark option [<a href="#ref-10" title="&quot;Telnet Timing Mark Option&quot;">10</a>] is used by some servers to test for the
351 continued presence of a TN3270 client. The following example will
352 assure the server the client is still alive.
353
354 Server: IAC DO TIMING-MARK
355 Client: IAC WONT TIMING-MARK
356
357 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Testing for session presence</span>
358
359 The NOP command (hexadecimal F1) [<a href="#ref-11" title="&quot;Telnet Protocol Specification&quot;">11</a>] is used by some servers to test
360 for the continued presence of a TN3270 client. If a client has
361 terminated abnormally, TCP/IP send errors will occur. The Timing Mark
362 option, described above, is also used to test for presence.
363
364 Server: IAC NOP
365 Client: &lt;ignore / no response&gt;
366
367 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Handling 3270 data</span>
368
369 The 3270 data stream consists of a command and its associated data.
370 Commands include but are not limited to erase screen, erase and write
371 to screen and read current screen; see [<a href="#ref-6" title="&quot;3270 Information Display System - Data Stream Programmer's Reference&quot;">6</a>] for a complete description
372 of 3270 commands and parameters.
373
374 The reason for negotiating the EOR telnet option [<a href="#ref-4" title="&quot;Telnet End of Record Option&quot;">4</a>] is to provide a
375 method for separating these commands since no length information is
376 specified. 3270 commands are interpreted by the telnet client in
377 their entirety. Each 3270 command and possible data is terminated
378 with the IAC EOR sequence.
379
380 The Binary option [<a href="#ref-3" title="&quot;Telnet Binary Transmission&quot;">3</a>] is also required since 3270 data may contain
381 the FF (hexadecimal) or IAC character. When this character is
382 encountered during a TN3270 connection it is handled as per the
383 Binary RFC [<a href="#ref-3" title="&quot;Telnet Binary Transmission&quot;">3</a>].
384
385
386
387
388 <span class="grey">TN3270 Enhancements Working Group [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1576">RFC 1576</a> TN3270 Current Practices January 1994</span>
391
392
393 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. 3270 Structured Fields</span>
394
395 3270 structured fields provide a much wider range of features than
396 "old-style" 3270 data, such as support for graphics, partitions and
397 IPDS printer datastreams. A structured field is a 3270 data type that
398 allows non 3270 data to be embedded within 3270 data. Briefly, a
399 structured field consists of the structured field command followed by
400 one or more data blocks. Each data block has a length and a
401 structured field identifier, followed optionally by additional data.
402
403 Not every TN3270 client can be expected to support all structured
404 field functions. There must be a mechanism by which those clients
405 that are capable of supporting some or all structured field functions
406 can indicate their wishes. This is typically done by adding "-E" to
407 the end of the terminal type string. That is, when the terminal
408 identifies itself as being able to handle extended attributes, it
409 also is capable of being able to send and receive structured fields.
410
411 The design of 3270 structured fields provides a convenient means to
412 convey the level of support (including no support) for the various
413 structured field functions. This mechanism is the Read Partition
414 Query command, which is sent from the host application to the client.
415 The client responds with a Query Reply, listing which, if any,
416 structured field functions it supports.
417
418 A TN3270 client that supports structured fields will respond to a
419 Read Partition Query command with the appropriate reply. The
420 sequence of events when a client receives a Read Partition Query and
421 does not support structured fields is left up to the client
422 implementation. Typically clients can identify at least this
423 structured field and reply with a null set.
424
425 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. The 3270 ATTN (Attention) Key</span>
426
427 The 3270 ATTN key is interpreted by many host applications in an SNA
428 environment as an indication that the user wishes to interrupt the
429 execution of the current process. A majority of the telnet servers
430 currently accept the telnet IAC BREAK (code 243) [<a href="#ref-11" title="&quot;Telnet Protocol Specification&quot;">11</a>] sequence to
431 signal this event.
432
433 Use of this key requires two things:
434
435 - The TN3270 clients provide as part of their keyboard
436 mapping a single key or a combination of keys that map to
437 the 3270 ATTN key. When the user presses this key(s), the
438 client transmits a Telnet BREAK command to the server.
439
440
441
442
443
444 <span class="grey">TN3270 Enhancements Working Group [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1576">RFC 1576</a> TN3270 Current Practices January 1994</span>
447
448
449 - The TN3270 servers translate the BREAK command received from
450 a TN3270 client into the appropriate form and pass it along
451 to the host application as an ATTN key. In other words, the
452 server representing an SLU in an SNA session would send
453 a SIGNAL RU to the host application.
454
455 The ATTN key is not supported in a non-SNA environment; therefore, a
456 TN3270 server representing non-SNA 3270 devices ignores any Telnet
457 BREAK commands it receives from a client.
458
459 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. The 3270 SYSREQ Key</span>
460
461 The 3270 SYSREQ key is useful in an environment where the telnet
462 server is attached to the host using SNA. The SYSREQ key is useful in
463 this environment when the host application becomes locked or the user
464 wishes to terminate the session without closing the Telnet
465 connection.
466
467 The Telnet Interrupt Process (IP) command [<a href="#ref-11" title="&quot;Telnet Protocol Specification&quot;">11</a>] is interpreted by some
468 telnet servers as a SYSREQ key. Other servers recognize the 3270 Test
469 Request key as a SYSREQ key. In an SNA environment, pressing this
470 key toggles the terminal between the host application session and the
471 SSCP session. Usually the user will enter LOGOFF once this key has
472 been pressed to terminate the application session and then select a
473 new host to connect to. Sometimes, if SYSREQ is pressed again, the
474 host application will become unlocked and normal activities may then
475 proceed.
476
477 It is entirely up to the telnet server to interpret this command and
478 send the appropriate commands to the host as well as format the
479 resulting host data for display on the telnet client. The data format
480 during the SSCP session is in a slightly different format than normal
481 3270 data. Since the telnet server has no way to pass this data
482 directly to the telnet client, it must either handle it entirely and
483 ignore SYSREQ events or convert it to 3270 data to present to the
484 client.
485
486 To implement SYSREQ key support, TN3270 clients provide a key (or
487 combination of keys) that is identified as mapping to the 3270 SYSREQ
488 key. When the user presses this key(s), the client would either
489 transmit a Telnet IP command or Test Request key to the server,
490 depending on the server implementation.
491
492 TN3270 servers representing non-SNA 3270 terminals may ignore any
493 Telnet IP commands or Test Request keys they receive from a client.
494
495
496
497
498
499
500 <span class="grey">TN3270 Enhancements Working Group [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1576">RFC 1576</a> TN3270 Current Practices January 1994</span>
503
504
505 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Items not addressed by TN3270</span>
506
507 There are several items that are not supported by current TN3270
508 implementations; among them are the following:
509
510 - TN3270 provides no capability for clients to emulate the 328x
511 class of printers.
512
513 - There is no mechanism by which a Telnet client can request that
514 a connection be associated with a given 3270 device-name. This
515 can be of importance when a terminal session is being
516 established, since many host applications behave differently
517 depending on the network name of the terminal.
518
519 - The 3270 ATTN and SYSREQ keys are not universally supported.
520
521 - There is no support for the SNA positive/negative response
522 process. All data that is sent is assumed to either be handled
523 or ignored. The lack of SNA response processing in TN3270 is
524 part of what makes TN3270 efficient.
525 A negative response indicates some sort of error at the client
526 while processing the previously received data; this could be
527 caused by the host application building a 3270 datastream that
528 contains an invalid command, or by a mechanical error at the
529 client side, among other things.
530 Positive responses indicate processing of the previously received
531 data has completed.
532
533 - There is no mechanism by which the client can access the SNA
534 BIND information. The BIND image in a SNA environment
535 contains a detailed description of the session between the
536 telnet server and the host application.
537
538 - The connection negotiation does not make it clear whether
539 clients should support 3270 structured fields.
540
541 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
542
543 [<a id="ref-1">1</a>] Rekhter, Y., "Telnet 3270 Regime Option", <a href="./rfc1041">RFC 1041</a>, IBM
544 Corporation, January 1988.
545
546 [<a id="ref-2">2</a>] VanBokkelen, J., "Telnet Terminal-Type Option", <a href="./rfc1091">RFC 1091</a>, FTP
547 Software, Inc., February 1989.
548
549 [<a id="ref-3">3</a>] Postel, J., and J. Reynolds, "Telnet Binary Transmission", STD
550 27, <a href="./rfc856">RFC 856</a>, USC/Information Sciences Institute, May 1983.
551
552
553
554
555
556 <span class="grey">TN3270 Enhancements Working Group [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1576">RFC 1576</a> TN3270 Current Practices January 1994</span>
559
560
561 [<a id="ref-4">4</a>] Postel, J., "Telnet End of Record Option", <a href="./rfc885">RFC 885</a>,
562 USC/Information Sciences Institute, December 1983.
563
564 [<a id="ref-5">5</a>] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, <a href="./rfc1340">RFC 1340</a>,
565 USC/Information Sciences Institute, July 1992.
566
567 [<a id="ref-6">6</a>] "3270 Information Display System - Data Stream Programmer's
568 Reference", publication number GA23-0059, IBM Corporation.
569
570 [<a id="ref-7">7</a>] "Systems Network Architecture - Formats", publication number
571 GA27-3136, IBM Corporation.
572
573 [<a id="ref-8">8</a>] Postel, J., and J. Reynolds, "Telnet Suppress Go Ahead Option",
574 STD 29, <a href="./rfc858">RFC 858</a>, USC/Information Sciences Institute, May 1983.
575
576 [<a id="ref-9">9</a>] Postel, J., and J. Reynolds, "Telnet Echo Option", STD 28, <a href="./rfc857">RFC</a>
577 <a href="./rfc857">857</a>, USC/Information Sciences Institute, May 1983.
578
579 [<a id="ref-10">10</a>] Postel, J., and J. Reynolds, "Telnet Timing Mark Option", STD 31,
580 <a href="./rfc860">RFC 860</a>, USC/Information Sciences Institute, May 1983.
581
582 [<a id="ref-11">11</a>] Postel, J., and J. Reynolds, "Telnet Protocol Specification", STD
583 8, <a href="./rfc854">RFC 854</a>, USC/Information Sciences Institute, May 1983.
584
585 [<a id="ref-12">12</a>] "Systems Network Architecture - Concepts and Products",
586 publication number GC30-3072, IBM Corporation.
587
588 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Security Considerations</span>
589
590 Security issues are not discussed in this memo.
591
592 <span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Author's Note</span>
593
594 Portions of this document were drawn from the following sources:
595
596 - A White Paper written by Owen Reddecliffe, WRQ Corporation,
597 October 1991.
598
599 - Experimental work on the part of Cleve Graves and Michelle
600 Angel, OpenConnect Systems, 1992 - 1993.
601
602 - Discussions at the March 1993 IETF meeting and TN3270 BOF at
603 Interop August 1993.
604
605 - Discussions on the "TN3270E" list, 1993.
606
607
608
609
610
611
612 <span class="grey">TN3270 Enhancements Working Group [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc1576">RFC 1576</a> TN3270 Current Practices January 1994</span>
615
616
617 <span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. Author's Address</span>
618
619 Jon Penner
620 DCA, Inc.
621 2800 Oakmont Drive
622 Austin, TX 78664
623
624 Phone: (512) 388-7090 FAX
625 EMail: [email protected]
626 or dca/g=Jon/s=Penner/[email protected]
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668 TN3270 Enhancements Working Group [Page 12]
669 </pre>