< draft-yevstifeyev-tn3270-uri-17.txt		draft-yevstifeyev-tn3270-uri-18.txt >
	INTERNET-DRAFT M. Yevstifeyev		INTERNET-DRAFT M. Yevstifeyev
	Intended Status: Standards Track March 26, 2011		Intended Status: Standards Track April 6, 2011
	Updates: 2355, 1738, 1041 (if approved)		Updates: 2355, 1738, 1041 (if approved)
	Expires: September 27, 2011		Expires: October 8, 2011
	The 'tn3270' URI Scheme		The 'tn3270' URI Scheme
	<draft-yevstifeyev-tn3270-uri-17>		<draft-yevstifeyev-tn3270-uri-18>
	Abstract		Abstract
	This document is the specification of the 'tn3270' Uniform Resource		This document is the specification of the 'tn3270' Uniform Resource
	Identifier (URI) scheme, that is used to designate the access to the		Identifier (URI) scheme, which is used to designate the access to the
	resources available via Telnet 3270 mode (TN3270) and Telnet 3270		resources available via Telnet 3270 mode (TN3270) and Telnet 3270
	Enchanted mode (TN3270E). It updates RFC 1041 and RFC 2355, that		Enchanted mode (TN3270E). It updates RFC 1041 and RFC 2355, which
	specify these protocols, and RFC 1738, that firstly mentioned this		specify these protocols, and RFC 1738, which firstly mentioned this
	URI scheme, giving no definition of its syntax or semantics.		URI scheme without defining its syntax and semantics.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as		other groups may also distribute working documents as
	Internet-Drafts.		Internet-Drafts.
	skipping to change at page 2, line 28 ¶		skipping to change at page 2, line 28 ¶
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
	5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4		5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
	5.1. Normative References . . . . . . . . . . . . . . . . . . . 4		5.1. Normative References . . . . . . . . . . . . . . . . . . . 4
	5.2. Informative References . . . . . . . . . . . . . . . . . . 5		5.2. Informative References . . . . . . . . . . . . . . . . . . 5
	Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 5		Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 5
	Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6		Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
	1. Introduction		1. Introduction
	This document specifies the 'tn3270' Uniform Resource Identifier		This document specifies the 'tn3270' Uniform Resource Identifier
	(URI) scheme, that is used to designate the access to the resources		(URI) scheme, which is used to designate the access to the resources
	available via Telnet 3270 mode (TN3270), as described in RFC 1041		available via Telnet 3270 mode (TN3270), as described in RFC 1041
	[RFC1041] (especially, see Section 4 of RFC 1041; visit RFC 1576		[RFC1041] (especially, see Section 4 of RFC 1041; visit RFC 1576
	[RFC1576] for TN3270 practices), and Telnet 3270 Enchanted mode		[RFC1576] for TN3270 practices), and Telnet 3270 Enchanted mode
	(TN3270E), as described in RFC 2355 [RFC2355].		(TN3270E), as described in RFC 2355 [RFC2355].
	The 'tn3270' URI scheme was firstly mentioned in RFC 1738 [RFC1738]		The 'tn3270' URI scheme was firstly mentioned in RFC 1738 [RFC1738]
	as used in URIs that designate the access to "Interactive 3270		as used in URIs that designate the access to "Interactive 3270
	emulation sessions". Following the creation of the URI scheme		emulation sessions". Following the creation of the URI scheme
	registries per RFC 4395 [RFC4395], this scheme was added to the		registries per RFC 4395 [RFC4395], this scheme was added to the
	"Provisional URI Schemes" sub-registry in the "Uniform Resource		"Provisional URI Schemes" sub-registry in the "Uniform Resource
	Identifier (URI) Schemes" IANA registry [URIREG]. However RFC 1738		Identifier (URI) Schemes" IANA registry [URIREG]. However RFC 1738
	[RFC1738] does not give any definition of syntax and semantics of the		[RFC1738] does not give any definition of syntax and semantics of the
	'tn3270' URIs and does not have any guidelines for registration of		'tn3270' URIs and does not have any guidelines for registration of
	this scheme.		this scheme.
	Since there is no any acceptable specification of 'tn3270' URI, there		Since there is no acceptable specification of 'tn3270' URI, there is
	is a risk that somebody might try to implement it with some new,		a risk that somebody might try to implement it with some new,
	possibly undocumented, syntax, just by looking at IANA registry. In		possibly undocumented, syntax, just by looking at IANA registry. In
	order to minimize such risk, this document gives precise definition		order to minimize such risk, this document gives precise definition
	of syntax, semantics and use of this URIs and registers the		of syntax, semantics and use of this URIs and registers the
	corresponding scheme. It also updates RFC 2355 [RFC2355], RFC 1738		corresponding scheme. It also updates RFC 2355 [RFC2355], RFC 1738
	[RFC1738] and RFC 1041 [RFC1041].		[RFC1738] and RFC 1041 [RFC1041].
	The generic syntax of URIs is described in RFC 3986 [RFC3986].		The generic syntax of URIs is described in RFC 3986 [RFC3986].
	Registration procedures for new URI schemes are defined in RFC 4395		Registration procedures for new URI schemes are defined in RFC 4395
	[RFC4395].		[RFC4395].
	1.1. Terminology		1.1. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	2. 'tn3270' URI Definition		2. 'tn3270' URI Definition
	The 'tn3270' URI is used to access services that are provided via		The 'tn3270' URI is used to access services which are available via
	available via Telnet 3270 mode (TN3270), as described in RFC 1041		Telnet 3270 mode (TN3270), as described in RFC 1041 [RFC1041], and
	[RFC1041], and Telnet 3270 Enchanted mode (TN3270E), as described in		Telnet 3270 Enchanted mode (TN3270E), as described in RFC 2355
	RFC 2355 [RFC2355]. In fact these protocols are a modified form of		[RFC2355]. In fact these protocols are a modified form of Telnet
	Telnet [RFC0854]; see their specifications for details.		[RFC0854]; see their specifications for details.
	Note: This document does not specify the TN3270 and TN3270E		Note: This document does not specify the TN3270 and TN3270E
	services themselves, but only the URI scheme for them.		services themselves, but only the URI scheme for them.
	There already is the 'telnet' URI scheme [RFC4248], that designates		There already is the 'telnet' URI scheme [RFC4248], which designates
	the access to resources available via usual Telnet [RFC0854]. The		the access to resources available via usual Telnet [RFC0854]. The
	syntax of 'tn3270' URI is similar to that of 'telnet' one (except the		syntax of 'tn3270' URI is similar to that of 'telnet' one (except the
	<scheme> part) and takes the form of <tn3270-uri> rule below (given		<scheme> part) and takes the form of <tn3270-uri> rule below (given
	in ABNF, as described in RFC 5234 [RFC5234]):		in ABNF, as described in RFC 5234 [RFC5234]):
	tn3270-uri = "tn3270:" "//" authority ["/"]		tn3270-uri = "tn3270:" "//" authority ["/"]
	;the 'tn3270' URI takes the form		;the 'tn3270' URI takes the form
	;tn3270://<userinfo>@<host>:<port>/		;tn3270://<userinfo>@<host>:<port>/
	;that is formally defined via the <authority>		;that is formally defined via the <authority>
	skipping to change at page 4, line 6 ¶		skipping to change at page 4, line 6 ¶
	The <userinfo> (in the <authority>) is assumed to provide information		The <userinfo> (in the <authority>) is assumed to provide information
	for authentication using RFC 2941 [RFC2941] Telnet Authentication		for authentication using RFC 2941 [RFC2941] Telnet Authentication
	option.		option.
	3. Security Considerations		3. Security Considerations
	Generic security considerations for the usage of URIs are discussed		Generic security considerations for the usage of URIs are discussed
	in Section 7 of [RFC3986].		in Section 7 of [RFC3986].
	Since 'tn3270' URIs provide access to services that are available via		Since 'tn3270' URIs provide access to services that are available via
	TN3270 and TN3270E, that do not add any new security issues to Telnet		TN3270 and TN3270E, which do not add any new security issues to
	session, as they are a modified form of it, there are no other		Telnet session, as they are a modified form of it, there are no other
	security considerations for 'tn3270' URIs not discussed in RFC 4248		security considerations for 'tn3270' URIs not discussed in RFC 4248
	[RFC4248] - the 'telnet' URI scheme specification.		[RFC4248] - the 'telnet' URI scheme specification.
	4. IANA Considerations		4. IANA Considerations
	IANA is asked to update the registration of the 'tn3270' URI scheme		IANA is asked to update the registration of the 'tn3270' URI scheme
	using the following registration template (see [RFC4395]):		using the following registration template (see [RFC4395]):
	URI scheme name: tn3270		URI scheme name: tn3270
End of changes. 10 change blocks.
	18 lines changed or deleted		18 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/