Internet Engineering Task Force (IETF) M. Yevstifeyev
Request for Comments: 6270 June 2011
Updates: 1041, 1738, 2355
Category: Standards Track
ISSN: 2070-1721
Internet Engineering Task Force (IETF) M. Yevstifeyev
Request for Comments: 6270 June 2011
Updates: 1041, 1738, 2355
Category: Standards Track
ISSN: 2070-1721
The 'tn3270' URI Scheme
“tn3270”URI方案
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 RFC 1041 and RFC 2355, which specify these protocols, and RFC 1738, which firstly mentioned this URI scheme without defining its syntax and semantics.
本文档是“tn3270”统一资源标识符（URI）方案的规范，用于指定通过Telnet 3270模式（tn3270）和Telnet 3270增强模式（TN3270E）对可用资源的访问。它更新了RFC1041和RFC2355，它们指定了这些协议，以及RFC1738，它们首先提到了这个URI方案，但没有定义它的语法和语义。
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 Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6270.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6270.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) 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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................2
1.1. Terminology ................................................3
2. URI Scheme Definition ...........................................3
2.1. URI Scheme Syntax ..........................................3
2.2. URI Scheme Semantics .......................................3
3. Security Considerations .........................................3
4. IANA Considerations .............................................4
5. References ......................................................4
5.1. Normative References .......................................4
5.2. Informative References .....................................5
Appendix A. Acknowledgments ........................................6
1. Introduction ....................................................2
1.1. Terminology ................................................3
2. URI Scheme Definition ...........................................3
2.1. URI Scheme Syntax ..........................................3
2.2. URI Scheme Semantics .......................................3
3. Security Considerations .........................................3
4. IANA Considerations .............................................4
5. References ......................................................4
5.1. Normative References .......................................4
5.2. Informative References .....................................5
Appendix A. Acknowledgments ........................................6
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).
本文档指定了“tn3270”统一资源标识符（URI）方案，该方案用于指定通过Telnet 3270模式（tn3270）和Telnet 3270增强模式（TN3270E）对可用资源的访问。
Telnet 3270 mode (TN3270) is a name used to denote the special mode of Telnet session [RFC0854]. If it is used, the 3270 data stream [GA23-0059] is used when transmitting data during the Telnet session, whereas the Telnet 3270 Regime option [RFC1041] is used to enable and negotiate its use. (See [RFC1576] for some other background information on TN3270.) Telnet 3270 Enhanced mode (TN3270E) has a similar principle; see RFC 2355 [RFC2355] for its specification.
Telnet 3270模式（TN3270）是用于表示Telnet会话[RFC0854]的特殊模式的名称。如果使用，则在Telnet会话期间传输数据时使用3270数据流[GA23-0059]，而Telnet 3270机制选项[RFC1041]用于启用和协商其使用。（参见[RFC1576]了解TN3270的一些其他背景信息。）Telnet 3270增强模式（TN3270E）具有类似的原理；其规格见RFC 2355[RFC2355]。
The 'tn3270' URI scheme was firstly mentioned in RFC 1738 [RFC1738] as used in URIs that designate the access to "Interactive 3270 emulation sessions". Following the creation of the URI schemes registry per RFC 4395 [RFC4395], this scheme was added to the "Provisional URI Schemes" sub-registry in the "Uniform Resource Identifier (URI) Schemes" IANA registry [URIREG]. However, RFC 1738 [RFC1738] does not give any definition of syntax or semantics of the 'tn3270' URIs and does not have any guidelines for registration of this scheme.
RFC 1738[RFC1738]中首先提到了“tn3270”URI方案，该方案在指定访问“交互式3270仿真会话”的URI中使用。根据RFC 4395[RFC4395]创建URI方案注册表后，该方案被添加到IANA注册表[URIREG]中“统一资源标识符（URI）方案”的“临时URI方案”子注册表中。然而，RFC 1738[RFC1738]没有给出“tn3270”URI的语法或语义的任何定义，也没有注册此方案的任何指南。
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 RFC 2355 [RFC2355], RFC 1738 [RFC1738], and RFC 1041 [RFC1041].
由于没有可接受的“tn3270”URI规范，因此有人可能仅仅通过查看IANA注册表，就尝试使用一些新的、可能未记录的语法来实现它。为了尽量减少这种风险，本文给出了该URI的语法、语义和用法的精确定义，并注册了相应的方案。它还更新了RFC 2355[RFC2355]、RFC 1738[RFC1738]和RFC 1041[RFC1041]。
The generic syntax of URIs is described in RFC 3986 [RFC3986]. Registration procedures for new URI schemes are defined in RFC 4395 [RFC4395].
URI的通用语法在RFC 3986[RFC3986]中进行了描述。RFC 4395[RFC4395]中定义了新URI方案的注册程序。
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 RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
The 'tn3270' URI takes the following form (the syntax below is non-normative):
“tn3270”URI采用以下形式（以下语法不规范）：
tn3270://<userinfo>@<host>:<port>/
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.
其中带有“@”（at）符号字符的<userinfo>部分以及前面带有“：”（冒号）字符的<port>部分是可选的。
The normative syntax of the 'tn3270' URI is defined in <tn3270-uri> ABNF [RFC5234] rule:
“tn3270”URI的规范语法在<tn3270 URI>ABNF[RFC5234]规则中定义：
tn3270-uri = "tn3270:" "//" authority ["/"]
tn3270-uri = "tn3270:" "//" authority ["/"]
where the <authority> rule is specified in RFC 3986 [RFC3986].
RFC 3986[RFC3986]中规定了<authority>规则。
The semantics of each part of the 'tn3270' URI are defined below, in Section 2.2.
“tn3270”URI的每个部分的语义定义如下，见第2.2节。
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 [RFC2941], 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 [PORTREG].
“tn3270”URI的<host>部分是必需的，表示要建立tn3270或TN3270E连接的主机。<userinfo>部分被认为是定义在Telnet身份验证选项[RFC2941]中使用的信息，该选项可能在TN3270或TN3270E会话期间使用。<port>部分（如果存在）表示要在其上建立到<host>的TCP连接的端口。如果没有，默认端口应为23，在[PORTREG]中注册。
Generic security considerations for the usage of URIs are discussed in Section 7 of [RFC3986].
[RFC3986]第7节讨论了使用URI的一般安全注意事项。
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 RFC 4248 [RFC4248], the 'telnet' URI scheme specification.
由于“tn3270”URI提供对通过tn3270和TN3270E提供的服务的访问，这些服务不会向Telnet会话添加任何新的安全问题，因为它们是Telnet会话的一种修改形式，因此“tn3270”URI没有在RFC 4248[RFC4248]“Telnet”URI方案规范中未讨论的其他安全注意事项。
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 [RFC4251].
Telnet协议以及TN3270和TN3270E本身就是不安全的。鼓励那些需要远程登录访问和相关服务的用户使用更安全的技术，如secure Shell[RFC4251]。
IANA updated the registration of the 'tn3270' URI scheme using the following registration template (see [RFC4395]):
IANA使用以下注册模板更新了“tn3270”URI方案的注册（请参见[RFC4395]）：
URI scheme name: tn3270
URI方案名称：tn3270
Status: Permanent
地位：永久
URI scheme syntax: see Section 2.1 of RFC 6270
URI方案语法：参见RFC6270第2.1节
URI scheme semantics: see Section 2.2 of RFC 6270
URI方案语义：参见RFC6270第2.2节
URI scheme encoding considerations: there are no other encoding considerations for 'tn3270' URIs that are not described in RFC 3986 [RFC3986]
URI方案编码注意事项：“tn3270”URI没有RFC 3986[RFC3986]中未描述的其他编码注意事项
Protocols that use the scheme: Telnet 3270 mode (TN3270) [RFC1041] and Telnet 3270 Enhanced Mode (TN3270E) [RFC2355]
使用该方案的协议：Telnet 3270模式（TN3270）[RFC1041]和Telnet 3270增强模式（TN3270E）[RFC2355]
Security considerations: see Section 3 of RFC 6270
安全注意事项：见RFC 6270第3节
Contact: IESG <iesg@ietf.org>
Contact: IESG <iesg@ietf.org>
Author/Change controller: IETF <ietf@ietf.org>
Author/Change controller: IETF <ietf@ietf.org>
References: see Section 5 of RFC 6270
参考：见RFC 6270第5节
[RFC1041] Rekhter, Y., "Telnet 3270 regime option", RFC 1041, January 1988.
[RFC1041]Rekhter，Y.，“Telnet 3270体制选择”，RFC 10411988年1月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2355] Kelly, B., "TN3270 Enhancements", RFC 2355, June 1998.
[RFC2355]Kelly，B.，“TN3270增强”，RFC 23551998年6月。
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，2005年1月。
[RFC4248] Hoffman, P., "The telnet URI Scheme", RFC 4248, October 2005.
[RFC4248]Hoffman，P.，“telnet URI方案”，RFC 4248，2005年10月。
[RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5234]Crocker，D.，Ed.，和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，2008年1月。
[GA23-0059] IBM Corporation, "IBM 3270 Information Display System. Data Stream Programmer's Reference", IBM Publication GA23-0059, July 1992.
[GA23-0059]IBM公司，“IBM 3270信息显示系统.数据流程序员参考”，IBM出版物GA23-0059，1992年7月。
[PORTREG] Internet Assigned Numbers Authority (IANA) Registry, "Port Numbers", <http://www.iana.org>.
[PORTREG]互联网分配号码管理局（IANA）注册表，“端口号”<http://www.iana.org>.
[RFC0854] Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD 8, RFC 854, May 1983.
[RFC0854]Postel，J.和J.Reynolds，“Telnet协议规范”，STD 8，RFC 854，1983年5月。
[RFC1576] Penner, J., "TN3270 Current Practices", RFC 1576, January 1994.
[RFC1576]Penner，J.，“TN3270当前实践”，RFC 1576，1994年1月。
[RFC1738] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform Resource Locators (URL)", RFC 1738, December 1994.
[RFC1738]Berners Lee，T.，Masinter，L.，和M.McCahill，“统一资源定位器（URL）”，RFC 17381994年12月。
[RFC2941] Ts'o, T., Ed., and J. Altman, "Telnet Authentication Option", RFC 2941, September 2000.
[RFC2941]曹，T.，Ed.，和J.Altman，“Telnet认证选项”，RFC 29412000年9月。
[RFC4251] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH) Protocol Architecture", RFC 4251, January 2006.
[RFC4251]Ylonen，T.和C.Lonvick，编辑，“安全外壳（SSH）协议架构”，RFC 4251，2006年1月。
[RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and Registration Procedures for New URI Schemes", BCP 35, RFC 4395, February 2006.
[RFC4395]Hansen，T.，Hardie，T.，和L.Masinter，“新URI方案的指南和注册程序”，BCP 35，RFC 4395，2006年2月。
[URIREG] Internet Assigned Numbers Authority (IANA) Registry, "Uniform Resource Identifier (URI) Schemes", <http://www.iana.org>.
[URIREG]互联网分配号码管理局（IANA）注册表，“统一资源标识符（URI）方案”<http://www.iana.org>.
Many thanks to Alfred Hoenes, Graham Klyne, Alexey Melnikov, Julian Reschke, and Peter Saint-Andre for their input to this document.
非常感谢Alfred Hoenes、Graham Klyne、Alexey Melnikov、Julian Reschke和Peter Saint Andre对本文件的贡献。
Author's Addresses
作者地址
Mykyta Yevstifeyev 8 Kuzovkov St., flat 25, Kotovsk Ukraine
Mykyta Yevstifeyev 8 Kuzovkov St.，乌克兰科托夫斯克25号公寓
EMail: evnikita2@gmail.com
EMail: evnikita2@gmail.com