INTERNET-DRAFT M. Yevstifeyev Intended Status: Informational November 28, 2010 Expires: June 1, 2011 The tn3270 URI scheme Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright and License Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. 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. Mykyta Yevstifeyev Expires June 1, 2011 [Page 1] INTERNET DRAFT The tn3270 URI scheme November 28, 2010 Abstract This document defines the tn3270 Uniform Resource Identifier (URI) scheme. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Scheme Definition . . . . . . . . . . . . . . . . . . . . . . . 3 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 5. Normative References . . . . . . . . . . . . . . . . . . . . . 4 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 Mykyta Yevstifeyev Expires June 1, 2011 [Page 2] INTERNET DRAFT The tn3270 URI scheme November 28, 2010 1. Introduction The tn3270 URI scheme was first mentioned in RFC 1738. Following the creation of the URI scheme registries per RFC 4395 [RFC4395], it was added to the "Provisional" registry. However there are no clear and acceptable specifications so far for this scheme. The generic syntax of URIs is described in RFC 3986 [RFC3986]. URI registering procedures are defined in RFC 4395 [RFC4395]. This document gives a specification of syntax, semantics and use of tn3270 URI scheme. 2. Scheme Definition The tn3270 URI scheme is used to access services that are provided via TN3270 Telnet Service - Interactive 3270 emulation session (see RFC 2355 [RFC2355] and RFC 1041 [RFC1041] for details). TN3270 service practices are defined in RFC 1576 [RFC1576]. In fact this is Telnet service with special data transfer mode so the form of URI is similar to that of telnet one. The tn3270 URI takes the following form (given in ABNF, as described in RFC 5234 [RFC5234]): tn3270_uri = "tn3270:" "//" [user ":" password] host [":" port] [/] user = password = host = port = 1*5DIGIT The final character "/" can be omitted. The "user:password" pair can be omitted as well as "port" (if it is omitted, defaults to 23 - default Telnet port). Mykyta Yevstifeyev Expires June 1, 2011 [Page 3] INTERNET DRAFT The tn3270 URI scheme November 28, 2010 3. Security Considerations Security considerations for the usage of URIs are discussed in Section 7 of [RFC3986]. Many security consideration for telnet URI scheme defined in RFC 4248 [RFC4248] concern tn3270 one as well. 4. IANA Considerations IANA is asked to update the registration of tn3270 URI scheme using the following registration template: URI scheme name: tn3270 Status: Provisional URI scheme syntax: see Section 2 URI scheme semantics: see Section 2 URI scheme encoding considerations: tn3270 scheme uses UTF-8 (see RFC 3629 [RFC3629] for details) for encoding data. No internalization is intended Protocols that use the scheme: Telnet TN3270 mode (see RFC 2355 [RFC2355] and RFC 1041 [RFC1041] for details) Security considerations: see Section 3 Contact: Mykyta Yevstifeyev Author/Change controller: Mykyta Yevstifeyev References: see Section 5 of this document for references of [RFC1041], [RFC2355] and [RFC3629] 5. Normative References [RFC1041] Rekhter, Y., "Telnet 3270 regime option", RFC 1041, January 1988. [RFC1576] Penner, J., "TN3270 Current Practices", RFC 1576, January 1994. [RFC2355] Kelly, B., "TN3270 Enhancements", RFC 2355, June 1998. Mykyta Yevstifeyev Expires June 1, 2011 [Page 4] INTERNET DRAFT The tn3270 URI scheme November 28, 2010 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. [RFC4248] Hoffman, P., "The telnet URI Scheme", RFC 4248, October 2005. [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and Registration Procedures for New URI Schemes", BCP 35, RFC 4395, February 2006. [RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008. Acknowledgments Many thanks to (in alphabetical order): Alfred HInes and Graham Klyne for their weighty contributions to this document. Author's Addresses Mykyta Yevstifeyev 8 Kuzovkov St., flat 25, Kotovsk, Ukraine EMail: evnikita2@gmail.com Mykyta Yevstifeyev Expires June 1, 2011 [Page 5]