< draft-weiler-rsync-uri-00.txt   draft-weiler-rsync-uri-01.txt >
Network Working Group S. Weiler Network Working Group S. Weiler
Internet-Draft SPARTA, Inc. Internet-Draft SPARTA, Inc.
Intended status: Standards Track D. Ward Intended status: Informational D. Ward
Expires: January 7, 2010 Cisco Systems Expires: January 26, 2010 Cisco Systems
R. Housley R. Housley
Vigil Security, LLC Vigil Security, LLC
July 6, 2009 July 25, 2009
The rsync URI Scheme The rsync URI Scheme
draft-weiler-rsync-uri-00 draft-weiler-rsync-uri-01
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 7, 2010. This Internet-Draft will expire on January 26, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 27 skipping to change at page 2, line 27
2. rsync URI registration 2. rsync URI registration
This section contains the registration template for the rsync URI This section contains the registration template for the rsync URI
scheme in accordance with RFC 4395 [RFC4395]. scheme in accordance with RFC 4395 [RFC4395].
URI scheme name: rsync URI scheme name: rsync
Status: provisional Status: provisional
URI scheme syntax: An rsync URI describes a source or destination for URI scheme syntax: An rsync URI describes a source or destination for
the rsync protocol including a hostname, path, and optional user and the rsync application including a hostname, path, and optional user
port. The generic form of the rsync URI is: and port. The generic form of the rsync URI is:
rsync://[user@]host[:PORT]/Source rsync://[user@]host[:PORT]/Source
The rsync URI follows the general syntax from RFC 3986 and is defined The rsync URI follows the general syntax from RFC 3986 and is defined
by the following ABNF: by the following ABNF:
rsyncurl = "rsync:" hier-part rsyncurl = "rsync:" hier-part
; See RFC 3986 for the definition ; See RFC 3986 for the definition
; of hier-part ; of hier-part
URI scheme semantics: An rsync URI may be used as either a source or URI scheme semantics: An rsync URI may be used as either a source or
destination for the rsync protocol. If the port is not specified, it destination for the rsync application. If the port is not specified,
defaults to 873. it defaults to 873.
Encoding considerations: since the rsync URI is defined using Encoding considerations: since the rsync URI is defined using
standard elements from RFC 3986, no special encoding considerations standard elements from RFC 3986, no special encoding considerations
are present. are present.
Applications/protocols that use this URI scheme name: the only Applications/protocols that use this URI scheme name: the only
application that uses rsync URIs is rsync. application that uses rsync URIs is rsync.
Interoperability considerations: since only one application is Interoperability considerations: since only one application is
expected to make use of rsync URIs, this URI scheme is expected to expected to make use of rsync URIs, this URI scheme is expected to
 End of changes. 6 change blocks. 
9 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/