rfc-6270

The 'tn3270' URI Scheme

M. Yevstifeyev

date2011-06 streamIETF wgnon working group statusPROPOSED STANDARD pages6 canonicalhttps://www.rfc-editor.org/rfc/rfc6270 doi10.17487/RFC6270 errataview

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. [STANDARDS-TRACK]

updates

rfc-1041 — Telnet 3270 regime option
rfc-1738 — Uniform Resource Locators (URL)
rfc-2355 — TN3270 Enhancements

Extracted elements (10)

design-rationale §1

RFC 1738 mentioned the 'tn3270' URI scheme without defining its syntax or semantics. Without a formal specification, there was risk of incompatible or undocumented implementations arising from the IANA provisional registration alone; RFC 6270 was written to eliminate that ambiguity.

http, process

interoperability-note §1

This document updates RFC 1041 (Telnet 3270 Regime option), RFC 1738 (which first mentioned the scheme), and RFC 2355 (TN3270E specification) to reflect the now-normative 'tn3270' URI scheme definition.

http

normative-requirement §2.2 SHALL

If the <port> part is absent, the default port SHALL be 23, as registered in the IANA port registry.

http

normative-requirement §2.2 REQUIRED

The <host> part of the 'tn3270' URI is REQUIRED and denotes the host to which the TN3270 or TN3270E connection is to be established.

http

protocol-element §2.1

The 'tn3270' URI scheme designates access to resources available via Telnet 3270 mode (TN3270) and Telnet 3270 Enhanced mode (TN3270E). The URI takes the form tn3270://<userinfo>@<host>:<port>/ where userinfo and port are optional.

http

protocol-element §2.2

The <userinfo> part of the 'tn3270' URI is considered to define information for use in the Telnet Authentication option (RFC 2941), which might be used during the TN3270 or TN3270E session.

http, security

registry §4

IANA updated the 'tn3270' URI scheme registration from Provisional to Permanent status, with syntax and semantics referencing RFC 6270, associated protocols TN3270 and TN3270E, and IESG as contact.

registry, http

security-consideration §3

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 (RFC 4251).

security

security-consideration §3

'tn3270' URIs do not add any new security issues beyond those of the Telnet session itself; security considerations are the same as those for the 'telnet' URI scheme specified in RFC 4248. Generic URI security considerations from RFC 3986 Section 7 also apply.

security

wire-format §2.1

The normative ABNF syntax for 'tn3270' URIs is: tn3270-uri = "tn3270:" "//" authority ["/"], where <authority> is defined in RFC 3986. The userinfo and port components are optional.

http