idnits 2.17.1 draft-yevstifeyev-tn3270-uri-18.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC1738, but the abstract doesn't seem to directly say this. It does mention RFC1738 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC1041, updated by this document, for RFC5378 checks: 1988-01-01) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 6, 2011) is 4768 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Historic RFC: RFC 1041 -- Obsolete informational reference (is this intentional?): RFC 4395 (Obsoleted by RFC 7595) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT M. Yevstifeyev 3 Intended Status: Standards Track April 6, 2011 4 Updates: 2355, 1738, 1041 (if approved) 5 Expires: October 8, 2011 7 The 'tn3270' URI Scheme 8 10 Abstract 12 This document is the specification of the 'tn3270' Uniform Resource 13 Identifier (URI) scheme, which is used to designate the access to the 14 resources available via Telnet 3270 mode (TN3270) and Telnet 3270 15 Enchanted mode (TN3270E). It updates RFC 1041 and RFC 2355, which 16 specify these protocols, and RFC 1738, which firstly mentioned this 17 URI scheme without defining its syntax and semantics. 19 Status of this Memo 21 This Internet-Draft is submitted to IETF in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as 27 Internet-Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/1id-abstracts.html 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html 40 Copyright and License Notice 42 Copyright (c) 2011 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 58 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. 'tn3270' URI Definition . . . . . . . . . . . . . . . . . . . . 3 60 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 61 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 62 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 5.1. Normative References . . . . . . . . . . . . . . . . . . . 4 64 5.2. Informative References . . . . . . . . . . . . . . . . . . 5 65 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 5 66 Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 68 1. Introduction 70 This document specifies the 'tn3270' Uniform Resource Identifier 71 (URI) scheme, which is used to designate the access to the resources 72 available via Telnet 3270 mode (TN3270), as described in RFC 1041 73 [RFC1041] (especially, see Section 4 of RFC 1041; visit RFC 1576 74 [RFC1576] for TN3270 practices), and Telnet 3270 Enchanted mode 75 (TN3270E), as described in RFC 2355 [RFC2355]. 77 The 'tn3270' URI scheme was firstly mentioned in RFC 1738 [RFC1738] 78 as used in URIs that designate the access to "Interactive 3270 79 emulation sessions". Following the creation of the URI scheme 80 registries per RFC 4395 [RFC4395], this scheme was added to the 81 "Provisional URI Schemes" sub-registry in the "Uniform Resource 82 Identifier (URI) Schemes" IANA registry [URIREG]. However RFC 1738 83 [RFC1738] does not give any definition of syntax and semantics of the 84 'tn3270' URIs and does not have any guidelines for registration of 85 this scheme. 87 Since there is no acceptable specification of 'tn3270' URI, there is 88 a risk that somebody might try to implement it with some new, 89 possibly undocumented, syntax, just by looking at IANA registry. In 90 order to minimize such risk, this document gives precise definition 91 of syntax, semantics and use of this URIs and registers the 92 corresponding scheme. It also updates RFC 2355 [RFC2355], RFC 1738 94 [RFC1738] and RFC 1041 [RFC1041]. 96 The generic syntax of URIs is described in RFC 3986 [RFC3986]. 97 Registration procedures for new URI schemes are defined in RFC 4395 98 [RFC4395]. 100 1.1. Terminology 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 104 document are to be interpreted as described in RFC 2119 [RFC2119]. 106 2. 'tn3270' URI Definition 108 The 'tn3270' URI is used to access services which are available via 109 Telnet 3270 mode (TN3270), as described in RFC 1041 [RFC1041], and 110 Telnet 3270 Enchanted mode (TN3270E), as described in RFC 2355 111 [RFC2355]. In fact these protocols are a modified form of Telnet 112 [RFC0854]; see their specifications for details. 114 Note: This document does not specify the TN3270 and TN3270E 115 services themselves, but only the URI scheme for them. 117 There already is the 'telnet' URI scheme [RFC4248], which designates 118 the access to resources available via usual Telnet [RFC0854]. The 119 syntax of 'tn3270' URI is similar to that of 'telnet' one (except the 120 part) and takes the form of rule below (given 121 in ABNF, as described in RFC 5234 [RFC5234]): 123 tn3270-uri = "tn3270:" "//" authority ["/"] 124 ;the 'tn3270' URI takes the form 125 ;tn3270://@:/ 126 ;that is formally defined via the 128 The rule is specified in RFC 3986 [RFC3986]. If 129 (in the ) is omitted, it SHALL default to 21, as 130 registered in [PORTREG]. The final character "/" MAY be omitted. 131 The (in the ) is assumed to provide information 132 for authentication using RFC 2941 [RFC2941] Telnet Authentication 133 option. 135 3. Security Considerations 137 Generic security considerations for the usage of URIs are discussed 138 in Section 7 of [RFC3986]. 140 Since 'tn3270' URIs provide access to services that are available via 141 TN3270 and TN3270E, which do not add any new security issues to 142 Telnet session, as they are a modified form of it, there are no other 143 security considerations for 'tn3270' URIs not discussed in RFC 4248 144 [RFC4248] - the 'telnet' URI scheme specification. 146 4. IANA Considerations 148 IANA is asked to update the registration of the 'tn3270' URI scheme 149 using the following registration template (see [RFC4395]): 151 URI scheme name: tn3270 153 Status: Permanent 155 URI scheme syntax: see Section 2 of RFC xxxx 157 URI scheme semantics: see Section 2 of RFC xxxx 159 URI scheme encoding considerations: there are no other encoding 160 considerations for 'tn3270' URIs not described in RFC 3986 161 [RFC3986] 163 Protocols that use the scheme: Telnet 3270 mode (TN3270) [RFC1041] 164 and Telnet 3270 Enchanted Mode (TN3270E) [RFC2355] 166 Security considerations: see Section 3 of RFC xxxx 168 Contact: IESG 170 Author/Change controller: IETF 172 References: see Section 5 of RFC xxxx 174 [RFC Editor: Replace xxxx with assigned RFC number] 176 5. References 178 5.1. Normative References 180 [RFC1041] Rekhter, Y., "Telnet 3270 regime option", RFC 1041, 181 January 1988. 183 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 184 Requirement Levels", BCP 14, RFC 2119, March 1997. 186 [RFC2355] Kelly, B., "TN3270 Enhancements", RFC 2355, June 1998. 188 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 189 Resource Identifier (URI): Generic Syntax", STD 66, RFC 190 3986, January 2005. 192 [RFC4248] Hoffman, P., "The telnet URI Scheme", RFC 4248, October 193 2005. 195 [RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for 196 Syntax Specifications: ABNF", STD 68, RFC 5234, January 197 2008. 199 5.2. Informative References 201 [PORTREG] Internet Assigned Numbers Authority (IANA) Registry "Port 202 Numbers" 204 [RFC0854] Postel, J. and J. Reynolds, "Telnet Protocol 205 Specification", STD 8, RFC 854, May 1983. 207 [RFC1576] Penner, J., "TN3270 Current Practices", RFC 1576, January 208 1994. 210 [RFC1738] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform 211 Resource Locators (URL)", RFC 1738, December 1994. 212 Obsoleted by RFC4248, RFC4266. 214 [RFC2941] Ts'o, T., Ed., and J. Altman, "Telnet Authentication 215 Option", RFC 2941, September 2000. 217 [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and 218 Registration Procedures for New URI Schemes", BCP 35, RFC 219 4395, February 2006. 221 [URIREG] Internet Assigned Numbers Authority (IANA) Regsitry, 222 "Uniform Resource Identifer (URI) Schemes", 223 225 Appendix A. Acknowledgments 227 Many thanks to Alfred Hoenes, Graham Klyne, Alexey Melnikov, Julian 228 Reschke and Peter Saint-Andre for their input to this document. 230 Author's Addresses 232 Mykyta Yevstifeyev 233 8 Kuzovkov St., flat 25, 234 Kotovsk 235 Ukraine 237 EMail: evnikita2@gmail.com