[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 RFC 6270

INTERNET-DRAFT                                            M. Yevstifeyev
Intended Status: Informational                          January 26, 2011
Expires: July 30, 2011


         The 'tn3270' Uniform Resource Identifier (URI) Scheme
                   <draft-yevstifeyev-tn3270-uri-13>

Abstract

   This document defines the 'tn3270' Uniform Resource Identifier (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) 2011 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



M. Yevstifeyev           Expires July 30, 2011                  [Page 1]

INTERNET DRAFT          The 'tn3270' URI scheme         January 26, 2011


   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
      1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Scheme Definition . . . . . . . . . . . . . . . . . . . . . . . 4
   3.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
      5.1.  Normative References . . . . . . . . . . . . . . . . . . . 6
      5.2.  Informative References . . . . . . . . . . . . . . . . . . 6
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . 7
   Author's Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 7



































M. Yevstifeyev           Expires July 30, 2011                  [Page 2]

INTERNET DRAFT          The 'tn3270' URI scheme         January 26, 2011


1.  Introduction

   The 'tn3270' URI scheme was first mentioned in RFC 1738 [RFC1738] as
   used for 'Interactive 3270 emulation sessions'.  Following the
   creation of the URI scheme registries per RFC 4395 [RFC4395], it was
   added to the "Provisional URI Schemes" registry [PROVURI].  RFC 1738
   [RFC1738] does not give any definition of syntax and semantics of
   this URI scheme.

   Since there are no any acceptable specification of 'tn3270' URI
   scheme, there is a risk that somebody might try to implement it with
   some new, possibly undocumented syntax, just by looking at IANA
   registry.  In order to minimize such risk, this documents gives
   precise definition of syntax, semantics and use of this URI scheme.

   The generic syntax of URIs is described in RFC 3986 [RFC3986].
   Registering procedures for new URI schemes are defined in RFC 4395
   [RFC4395].

1.1.  Terminology

   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].



























M. Yevstifeyev           Expires July 30, 2011                  [Page 3]

INTERNET DRAFT          The 'tn3270' URI scheme         January 26, 2011


2.  Scheme Definition

   The 'tn3270' URI scheme is used to access services that are provided
   via Telnet 3270 mode (TN3270) (see RFC 1041 [RFC1041], RFC 1576
   [RFC1576], RFC 1646 [RFC1646] and IBM Publication GA23-0059 [GA23-
   0059] for details) and Telnet 3270 Enchanted Mode (TN3270E) (see RFC
   2355 [RFC2355], RFC 2561 [RFC2561], RFC 2562 [RFC2562] and RFC 3049
   [RFC3049] for details).  In fact these are Telnet services with
   special data transfer mode, so the syntax of 'tn3270' URI is similar
   to that of 'telnet' one [RFC4248].

   Note: This document does not specify the TN3270 and TN3270E
         services themselves, but only the URI scheme for them.

   The 'tn3270' URI takes the following form (given in ABNF, as
   described in RFC 5234 [RFC5234]):

   tn3270uri = "tn3270:" hier-part
   hier-part = "//" authority ["/"]
               ;the URI takes the form
               ;tn3270://<user>:<password>@<host>:<port>/
               ;that is formally defined via the 'authority'

   The 'authority' rule is specified in RFC 3986 [RFC3986].  If 'port'
   (in the 'authority' part) is omitted, it SHALL default to 21.  The
   final character "/" MAY be omitted.

























M. Yevstifeyev           Expires July 30, 2011                  [Page 4]

INTERNET DRAFT          The 'tn3270' URI scheme         January 26, 2011


3.  Security Considerations

   Generic security considerations for the usage of URIs are discussed
   in Section 7 of [RFC3986].

   Since the 'tn3270' URI scheme is used to provide the modified from of
   Telnet service (see Section 2), there are no other security
   considerations for 'tn3270' URI scheme not mentioned in Section 3 of
   RFC 4248 [RFC4248], that defines 'telnet' URI scheme.


4.  IANA Considerations

   IANA is asked to update the registration of tn3270 URI scheme using
   the following registration template (see [RFC4395]):

   URI scheme name: tn3270

   Status: Provisional

   URI scheme syntax: see Section 2 of RFC xxxx

   URI scheme semantics: see Section 2 of RFC xxxx

   URI scheme encoding considerations: generic encoding considerations
   for URI schemes, defined in Section 2 of [RFC3986], concern 'tn3270'
   one as well.  Non-ASCII characters are to be treated as defined in
   RFC 3987 [RFC3987]

   Protocols that use the scheme: Telnet 3270 mode (TN3270) (see RFC
   1041 [RFC1041], RFC 1576 [RFC1576], RFC 1646 [RFC1646] and IBM
   Publication GA23-0059 [GA23-0059] for details) and Telnet 3270
   Enchanted Mode (TN3270E) (see RFC 2355 [RFC2355], RFC 2561 [RFC2561],
   RFC 2562 [RFC2562] and RFC 3049 [RFC3049] for details)

   Security considerations: see Section 3 of RFC xxxx

   Contact: IESG <iesg@ietf.org>

   Author/Change controller: IETF <ietf@ietf.org>

   References: see Section 5 of RFC xxxx

   [RFC Editor: Replace xxxx with assigned RFC number]







M. Yevstifeyev           Expires July 30, 2011                  [Page 5]

INTERNET DRAFT          The 'tn3270' URI scheme         January 26, 2011


5.  References

5.1.  Normative References

   [RFC2119]   S. Bradner, "Key words for use in RFCs to Indicate
               Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC3986]   Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
               Resource Identifier (URI): Generic Syntax", STD 66, RFC
               3986, January 2005.

   [RFC3987]   Duerst, M. and M. Suignard, "Internationalized Resource
               Identifiers (IRIs)", RFC 3987, January 2005.

   [RFC4248]   Hoffman, P., "The telnet URI Scheme", RFC 4248, October
               2005.

   [RFC5234]   Crocker, D., Ed., and P. Overell, "Augmented BNF for
               Syntax Specifications: ABNF", STD 68, RFC 5234, January
               2008.

5.2.  Informative References

   [GA23-0059] IBM Publication, "IBM 3270 Information Display System.
               Data Stream Programmer's Reference", GA23-0059

   [PROVURI]   Internet Assigned Numbers Authority (IANA) Regsitry,
               "Uniform Resource Identifer (URI) Schemes",
               <http://www.iana.org/assignments/uri-schemes.html>

   [RFC1041]   Rekhter, Y., "Telnet 3270 regime option", RFC 1041,
               January 1988.

   [RFC1576]   Penner, J., "TN3270 Current Practices", RFC 1576, January
               1994.

   [RFC1646]   Graves, C., Butts, T., and M. Angel, "TN3270 Extensions
               for LUname and Printer Selection", RFC 1646, July 1994.

   [RFC1738]   Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform
               Resource Locators (URL)", RFC 1738, December 1994.

   [RFC2355]   Kelly, B., "TN3270 Enhancements", RFC 2355, June 1998.

   [RFC2561]   White, K. and R. Moore, "Base Definitions of Managed
               Objects for TN3270E Using SMIv2", RFC 2561, April 1999.

   [RFC2562]   White, K. and R. Moore, "Definitions of Protocol and



M. Yevstifeyev           Expires July 30, 2011                  [Page 6]

INTERNET DRAFT          The 'tn3270' URI scheme         January 26, 2011


               Managed Objects for TN3270E Response Time Collection
               Using SMIv2 (TN3270E-RT-MIB)", RFC 2562, April 1999.

   [RFC3049]   Naugle, J., Kasthurirangan, K., and G. Ledford, "TN3270E
               Service Location and Session Balancing", RFC 3049,
               January 2001.

   [RFC4395]   Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
               Registration Procedures for New URI Schemes", BCP 35, RFC
               4395, February 2006.


Acknowledgments

   Many thanks to Alfred Hoenes, Graham Klyne, Julian Reschke and Peter
   Saint-Andre for their weighty contributions to this document.

Author's Addresses

   Mykyta Yevstifeyev
   8 Kuzovkov St., flat 25,
   Kotovsk, Ukraine

   EMail: evnikita2@gmail.com



























M. Yevstifeyev           Expires July 30, 2011                  [Page 7]


Html markup produced by rfcmarkup 1.109, available from https://tools.ietf.org/tools/rfcmarkup/