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

Versions: 00 01 RFC 5781

Network Working Group                                          S. Weiler
Internet-Draft                                              SPARTA, Inc.
Intended status: Informational                                   D. Ward
Expires: January 26, 2010                                  Cisco Systems
                                                              R. Housley
                                                     Vigil Security, LLC
                                                           July 25, 2009


                          The rsync URI Scheme
                       draft-weiler-rsync-uri-01

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/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on January 26, 2010.

Copyright Notice

   Copyright (c) 2009 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 in effect on the date of
   publication of this document (http://trustee.ietf.org/license-info).
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.






Weiler, et al.          Expires January 26, 2010                [Page 1]

Internet-Draft                  rsync URI                      July 2009


Abstract

   This document specifies the rsync Uniform Resource Identifier (URI)
   scheme.


1.  Introduction

   URIs were previously defined in RFC 2396, which was updated by RFC
   3986 [RFC3986].  The procedures for registering new URI schemes are
   defined in RFC 4395 [RFC4395].  This document defines a URI scheme
   for rsync.


2.  rsync URI registration

   This section contains the registration template for the rsync URI
   scheme in accordance with RFC 4395 [RFC4395].

   URI scheme name: rsync

   Status: provisional

   URI scheme syntax: An rsync URI describes a source or destination for
   the rsync application including a hostname, path, and optional user
   and port.  The generic form of the rsync URI is:

   rsync://[user@]host[:PORT]/Source

   The rsync URI follows the general syntax from RFC 3986 and is defined
   by the following ABNF:

      rsyncurl        = "rsync:" hier-part
                         ; See RFC 3986 for the definition
                         ; of hier-part

   URI scheme semantics: An rsync URI may be used as either a source or
   destination for the rsync application.  If the port is not specified,
   it defaults to 873.

   Encoding considerations: since the rsync URI is defined using
   standard elements from RFC 3986, no special encoding considerations
   are present.

   Applications/protocols that use this URI scheme name: the only
   application that uses rsync URIs is rsync.

   Interoperability considerations: since only one application is



Weiler, et al.          Expires January 26, 2010                [Page 2]

Internet-Draft                  rsync URI                      July 2009


   expected to make use of rsync URIs, this URI scheme is expected to
   have few interoperability concerns.

   Security considerations: Section 7 of RFC 3986 describes general
   security considerations for URI schemes.  The considerations about
   reliability and consistency, malicious construction, rare IP address
   formats, sensitive information, and semantic attacks all apply to
   rsync URIs.  The considerations about transcoding do not apply.
   Given how rsync is regularly used, it is expected that most
   applications will not be bothered by data accessed via a given rsync
   URI changing over time.

   Contact: Russ Housley <housley@vigilsec.com>

   Author/Change controller: Russ Housley <housley@vigilsec.com>

   References: see Section 5.


3.  IANA Considerations

   IANA has registered the rsync provisional URI scheme using the
   template in Section 2.


4.  Security Considerations

   Many security considerations for the usage of URIs are discussed in
   Section 7 of [RFC3986].  The considerations about reliability and
   consistency, malicious construction, rare IP address formats,
   sensitive information, and semantic attacks all apply to rsync URIs.
   The considerations about transcoding do not apply.  The rsync URI
   scheme has no particularly unique security considerations.


5.  Normative References

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

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







Weiler, et al.          Expires January 26, 2010                [Page 3]

Internet-Draft                  rsync URI                      July 2009


Authors' Addresses

   Samuel Weiler
   SPARTA, Inc.
   7110 Samuel Morse Drive
   Columbia, Maryland  21046
   US

   Email: weiler@tislabs.com


   Dave Ward
   Cisco Systems
   170 W. Tasman Dr.
   San Jose, California  93134
   US

   Email: dward@cisco.com


   Russ Housley
   Vigil Security, LLC
   918 Spring Knoll Drive
   Herndon, Virginia  20170
   US

   Email: housley@vigilsec.com
























Weiler, et al.          Expires January 26, 2010                [Page 4]


Html markup produced by rfcmarkup 1.108, available from http://tools.ietf.org/tools/rfcmarkup/