1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
|
<pre>Internet Engineering Task Force (IETF) M. Yevstifeyev
Request for Comments: 6270 June 2011
Updates: <a href="./rfc1041">1041</a>, <a href="./rfc1738">1738</a>, <a href="./rfc2355">2355</a>
Category: Standards Track
ISSN: 2070-1721
<span class="h1">The 'tn3270' URI Scheme</span>
Abstract
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 <a href="./rfc1041">RFC 1041</a> and <a href="./rfc2355">RFC 2355</a>, which
specify these protocols, and <a href="./rfc1738">RFC 1738</a>, which firstly mentioned this
URI scheme without defining its syntax and semantics.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6270">http://www.rfc-editor.org/info/rfc6270</a>.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Yevstifeyev Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6270">RFC 6270</a> The 'tn3270' URI Scheme June 2011</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Terminology ................................................<a href="#page-3">3</a>
<a href="#section-2">2</a>. URI Scheme Definition ...........................................<a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. URI Scheme Syntax ..........................................<a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. URI Scheme Semantics .......................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. Security Considerations .........................................<a href="#page-3">3</a>
<a href="#section-4">4</a>. IANA Considerations .............................................<a href="#page-4">4</a>
<a href="#section-5">5</a>. References ......................................................<a href="#page-4">4</a>
<a href="#section-5.1">5.1</a>. Normative References .......................................<a href="#page-4">4</a>
<a href="#section-5.2">5.2</a>. Informative References .....................................<a href="#page-5">5</a>
<a href="#appendix-A">Appendix A</a>. Acknowledgments ........................................<a href="#page-6">6</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document specifies 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).
Telnet 3270 mode (TN3270) is a name used to denote the special mode
of Telnet session [<a href="./rfc0854" title=""Telnet Protocol Specification"">RFC0854</a>]. If it is used, the 3270 data stream
[<a href="#ref-GA23-0059" title=""IBM 3270 Information Display System. Data Stream Programmer's Reference"">GA23-0059</a>] is used when transmitting data during the Telnet session,
whereas the Telnet 3270 Regime option [<a href="./rfc1041" title=""Telnet 3270 regime option"">RFC1041</a>] is used to enable and
negotiate its use. (See [<a href="./rfc1576" title=""TN3270 Current Practices"">RFC1576</a>] for some other background
information on TN3270.) Telnet 3270 Enhanced mode (TN3270E) has a
similar principle; see <a href="./rfc2355">RFC 2355</a> [<a href="./rfc2355" title=""TN3270 Enhancements"">RFC2355</a>] for its specification.
The 'tn3270' URI scheme was firstly mentioned in <a href="./rfc1738">RFC 1738</a> [<a href="./rfc1738" title=""Uniform Resource Locators (URL)"">RFC1738</a>]
as used in URIs that designate the access to "Interactive 3270
emulation sessions". Following the creation of the URI schemes
registry per <a href="./rfc4395">RFC 4395</a> [<a href="./rfc4395" title=""Guidelines and Registration Procedures for New URI Schemes"">RFC4395</a>], this scheme was added to the
"Provisional URI Schemes" sub-registry in the "Uniform Resource
Identifier (URI) Schemes" IANA registry [<a href="#ref-URIREG" title=""Uniform Resource Identifier (URI) Schemes"">URIREG</a>]. However, <a href="./rfc1738">RFC 1738</a>
[<a href="./rfc1738" title=""Uniform Resource Locators (URL)"">RFC1738</a>] does not give any definition of syntax or semantics of the
'tn3270' URIs and does not have any guidelines for registration of
this scheme.
Since there is no acceptable specification of the 'tn3270' URI, there
is a risk that somebody might try to implement it with some new,
possibly undocumented, syntax, just by looking at the IANA registry.
In order to minimize such risk, this document gives a precise
definition of syntax, semantics, use of this URI, and it registers
the corresponding scheme. It also updates <a href="./rfc2355">RFC 2355</a> [<a href="./rfc2355" title=""TN3270 Enhancements"">RFC2355</a>], <a href="./rfc1738">RFC</a>
<a href="./rfc1738">1738</a> [<a href="./rfc1738" title=""Uniform Resource Locators (URL)"">RFC1738</a>], and <a href="./rfc1041">RFC 1041</a> [<a href="./rfc1041" title=""Telnet 3270 regime option"">RFC1041</a>].
<span class="grey">Yevstifeyev Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6270">RFC 6270</a> The 'tn3270' URI Scheme June 2011</span>
The generic syntax of URIs is described in <a href="./rfc3986">RFC 3986</a> [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>].
Registration procedures for new URI schemes are defined in <a href="./rfc4395">RFC 4395</a>
[<a href="./rfc4395" title=""Guidelines and Registration Procedures for New URI Schemes"">RFC4395</a>].
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. URI Scheme Definition</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. URI Scheme Syntax</span>
The 'tn3270' URI takes the following form (the syntax below is non-
normative):
tn3270://<userinfo>@<host>:<port>/
where the <userinfo> part with the "@" (at) sign character, as well
as the <port> part with the preceding ":" (colon) character, is
OPTIONAL.
The normative syntax of the 'tn3270' URI is defined in <tn3270-uri>
ABNF [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>] rule:
tn3270-uri = "tn3270:" "//" authority ["/"]
where the <authority> rule is specified in <a href="./rfc3986">RFC 3986</a> [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>].
The semantics of each part of the 'tn3270' URI are defined below, in
<a href="#section-2.2">Section 2.2</a>.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. URI Scheme Semantics</span>
The <host> part of the 'tn3270' URI, which is REQUIRED, denotes the
host to which the TN3270 or TN3270E connection is to be established.
The <userinfo> part is considered to define the information for use
in the Telnet Authentication option [<a href="./rfc2941" title=""Telnet Authentication Option"">RFC2941</a>], which might be used
during the TN3270 or TN3270E session. The <port> part, if present,
denotes the port on which the TCP connection to the <host> is to be
established. If it is absent, the default port SHALL be 23, as
registered in [<a href="#ref-PORTREG" title=""Port Numbers"">PORTREG</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
Generic security considerations for the usage of URIs are discussed
in <a href="./rfc3986#section-7">Section 7 of [RFC3986]</a>.
<span class="grey">Yevstifeyev Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6270">RFC 6270</a> The 'tn3270' URI Scheme June 2011</span>
Since 'tn3270' URIs provide access to services that are available via
TN3270 and TN3270E, which do not add any new security issues to the
Telnet session, as they are a modified form of it, there are no other
security considerations for 'tn3270' URIs that are not discussed in
<a href="./rfc4248">RFC 4248</a> [<a href="./rfc4248" title=""The telnet URI Scheme"">RFC4248</a>], the 'telnet' URI scheme specification.
The Telnet protocol, as well as TN3270 and TN3270E, is inherently
insecure. Those needing remote login access and related services are
encouraged to use a more secure technology, such as Secure Shell
[<a href="./rfc4251" title=""The Secure Shell (SSH) Protocol Architecture"">RFC4251</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
IANA updated the registration of the 'tn3270' URI scheme using the
following registration template (see [<a href="./rfc4395" title=""Guidelines and Registration Procedures for New URI Schemes"">RFC4395</a>]):
URI scheme name: tn3270
Status: Permanent
URI scheme syntax: see <a href="./rfc6270#section-2.1">Section 2.1 of RFC 6270</a>
URI scheme semantics: see <a href="./rfc6270#section-2.2">Section 2.2 of RFC 6270</a>
URI scheme encoding considerations: there are no other encoding
considerations for 'tn3270' URIs that are not described in <a href="./rfc3986">RFC</a>
<a href="./rfc3986">3986</a> [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]
Protocols that use the scheme: Telnet 3270 mode (TN3270) [<a href="./rfc1041" title=""Telnet 3270 regime option"">RFC1041</a>]
and Telnet 3270 Enhanced Mode (TN3270E) [<a href="./rfc2355" title=""TN3270 Enhancements"">RFC2355</a>]
Security considerations: see <a href="./rfc6270#section-3">Section 3 of RFC 6270</a>
Contact: IESG <iesg@ietf.org>
Author/Change controller: IETF <ietf@ietf.org>
References: see <a href="./rfc6270#section-5">Section 5 of RFC 6270</a>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Normative References</span>
[<a id="ref-RFC1041">RFC1041</a>] Rekhter, Y., "Telnet 3270 regime option", <a href="./rfc1041">RFC 1041</a>,
January 1988.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
<span class="grey">Yevstifeyev Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6270">RFC 6270</a> The 'tn3270' URI Scheme June 2011</span>
[<a id="ref-RFC2355">RFC2355</a>] Kelly, B., "TN3270 Enhancements", <a href="./rfc2355">RFC 2355</a>, June 1998.
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, <a href="./rfc3986">RFC</a>
<a href="./rfc3986">3986</a>, January 2005.
[<a id="ref-RFC4248">RFC4248</a>] Hoffman, P., "The telnet URI Scheme", <a href="./rfc4248">RFC 4248</a>, October
2005.
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed., and P. Overell, "Augmented BNF for
Syntax Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, January
2008.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Informative References</span>
[<a id="ref-GA23-0059">GA23-0059</a>] IBM Corporation, "IBM 3270 Information Display System.
Data Stream Programmer's Reference", IBM Publication
GA23-0059, July 1992.
[<a id="ref-PORTREG">PORTREG</a>] Internet Assigned Numbers Authority (IANA) Registry,
"Port Numbers", <<a href="http://www.iana.org">http://www.iana.org</a>>.
[<a id="ref-RFC0854">RFC0854</a>] Postel, J. and J. Reynolds, "Telnet Protocol
Specification", STD 8, <a href="./rfc854">RFC 854</a>, May 1983.
[<a id="ref-RFC1576">RFC1576</a>] Penner, J., "TN3270 Current Practices", <a href="./rfc1576">RFC 1576</a>, January
1994.
[<a id="ref-RFC1738">RFC1738</a>] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform
Resource Locators (URL)", <a href="./rfc1738">RFC 1738</a>, December 1994.
[<a id="ref-RFC2941">RFC2941</a>] Ts'o, T., Ed., and J. Altman, "Telnet Authentication
Option", <a href="./rfc2941">RFC 2941</a>, September 2000.
[<a id="ref-RFC4251">RFC4251</a>] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH)
Protocol Architecture", <a href="./rfc4251">RFC 4251</a>, January 2006.
[<a id="ref-RFC4395">RFC4395</a>] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
Registration Procedures for New URI Schemes", <a href="https://www.rfc-editor.org/bcp/bcp35">BCP 35</a>, <a href="./rfc4395">RFC</a>
<a href="./rfc4395">4395</a>, February 2006.
[<a id="ref-URIREG">URIREG</a>] Internet Assigned Numbers Authority (IANA) Registry,
"Uniform Resource Identifier (URI) Schemes",
<<a href="http://www.iana.org">http://www.iana.org</a>>.
<span class="grey">Yevstifeyev Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6270">RFC 6270</a> The 'tn3270' URI Scheme June 2011</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Acknowledgments</span>
Many thanks to Alfred Hoenes, Graham Klyne, Alexey Melnikov, Julian
Reschke, and Peter Saint-Andre for their input to this document.
Author's Addresses
Mykyta Yevstifeyev
8 Kuzovkov St., flat 25,
Kotovsk
Ukraine
EMail: evnikita2@gmail.com
Yevstifeyev Standards Track [Page 6]
</pre>
|
