[Search] [txt|pdfized|bibtex] [Tracker] [Email] [Nits]
Versions: 00                                                            
INTERNET-DRAFT                                            M. Yevstifeyev
Intended Status: Informational                          February 2, 2011
Updates: 1282 (if approved)
Expires: August 6, 2011


         The 'rlogin' Uniform Resource Identifier (URI) Scheme
                   <draft-yevstifeyev-rlogin-uri-00>


Abstract

   This document is a specification of 'rlogin' Uniform Resource
   Identifier (URI) scheme.  It updates RFC 1282.


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



Yesvtifeyev              Expires August 6, 2011                 [Page 1]


INTERNET DRAFT            'rlogin' URI scheme           February 2, 2011


   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.


Table of Contents

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


1.  Introduction

   The Rlogin protocol was firstly defined in RFC 1258 [RFC1258], that
   has been made obsolete by RFC 1282 [RFC1282].  This protocol is used
   for access to remote Unix terminal; in fact it provides the same
   service as Telnet protocol [RFC854].

   This document specifies the Uniform Resource Identifier (URI) scheme
   for access to the resources, available via this protocol - 'rlogin'
   URI scheme.

   Generic URI syntax is defined in RFC 3986 [RFC3986]; registration
   procedures for new URI schemes are described 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].













Yesvtifeyev              Expires August 6, 2011                 [Page 2]


INTERNET DRAFT            'rlogin' URI scheme           February 2, 2011


2.  Scheme Definition

   The 'rlogin' URI scheme is used to access the resources available via
   Rlogin protocol [RFC1282].  This scheme support only Rlogin over TCP,
   as described in its original specification; Rlogin over SSH, TLS,
   etc. are not provided by this URI scheme.

   The 'rlogin' URI takes the following form (described in Augmented
   Backus-Naur Form (ABNF) [RFC5234]):

     rlogin-uri = "rlogin:" hier-part
     hier-part  = "//" host [":" port] ["/"]

   The rules 'host' and 'port' are defined in RFC 3986 [RFC3986].  If
   the 'port' is omitted, it SHALL default to 513.  The final character
   "/" MAY be omitted.



































Yesvtifeyev              Expires August 6, 2011                 [Page 3]


INTERNET DRAFT            'rlogin' URI scheme           February 2, 2011


3.  Security Considerations

   The Rlogin protocol uses ACLs (access control lists) to control the
   access to the terminals.  It does not provide any authentification
   features, that may be provided in the next versions of the protocol.

   The 'rlogin' URI scheme designates the access to resources, available
   by Rlogin over TCP, but does not support more secure Rlogin over SSH,
   TLS, etc.


4.  IANA Considerations

   IANA is asked to register the 'rlogin' URI scheme using the following
   template (see RFC 4395 [RFC4395]):

     URI scheme name: rlogin

     Status: Permanent

     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 RFC 3986 [RFC3986],
     concern 'rlogin' one as well.  Non-ASCII characters are to be
     mapped as defined in Section 3.1 of RFC 3987 [RFC3987]

     Protocols that use the scheme: Rlogin protocol [RFC1282]

     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]











Yesvtifeyev              Expires August 6, 2011                 [Page 4]


INTERNET DRAFT            'rlogin' URI scheme           February 2, 2011


5.  References

5.1.  Normative References

   [RFC1282]   Kantor, B., "BSD Rlogin", RFC 1282, December 1991.

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

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

5.2.  Informative References

   [RFC854]    Postel, J. and J. Reynolds, "Telnet Protocol
               Specification", STD 8, RFC 854, May 1983.

   [RFC1258]   Kantor, B., "BSD Rlogin", RFC 1258, September 1991.

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


Author's Addresses

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

   EMail: evnikita2@gmail.com












Yesvtifeyev              Expires August 6, 2011                 [Page 5]