idnits 2.17.00 (12 Aug 2021) /tmp/idnits50809/draft-weiler-rsync-uri-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) 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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 6, 2009) is 4701 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) ** Obsolete normative reference: RFC 4395 (Obsoleted by RFC 7595) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. Weiler 3 Internet-Draft SPARTA, Inc. 4 Intended status: Standards Track D. Ward 5 Expires: January 7, 2010 Cisco Systems 6 R. Housley 7 Vigil Security, LLC 8 July 6, 2009 10 The rsync URI Scheme 11 draft-weiler-rsync-uri-00 13 Status of this Memo 15 This Internet-Draft is submitted to IETF in full conformance with the 16 provisions of BCP 78 and BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on January 7, 2010. 36 Copyright Notice 38 Copyright (c) 2009 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents in effect on the date of 43 publication of this document (http://trustee.ietf.org/license-info). 44 Please review these documents carefully, as they describe your rights 45 and restrictions with respect to this document. 47 Abstract 49 This document specifies the rsync Uniform Resource Identifier (URI) 50 scheme. 52 1. Introduction 54 URIs were previously defined in RFC 2396, which was updated by RFC 55 3986 [RFC3986]. The procedures for registering new URI schemes are 56 defined in RFC 4395 [RFC4395]. This document defines a URI scheme 57 for rsync. 59 2. rsync URI registration 61 This section contains the registration template for the rsync URI 62 scheme in accordance with RFC 4395 [RFC4395]. 64 URI scheme name: rsync 66 Status: provisional 68 URI scheme syntax: An rsync URI describes a source or destination for 69 the rsync protocol including a hostname, path, and optional user and 70 port. The generic form of the rsync URI is: 72 rsync://[user@]host[:PORT]/Source 74 The rsync URI follows the general syntax from RFC 3986 and is defined 75 by the following ABNF: 77 rsyncurl = "rsync:" hier-part 78 ; See RFC 3986 for the definition 79 ; of hier-part 81 URI scheme semantics: An rsync URI may be used as either a source or 82 destination for the rsync protocol. If the port is not specified, it 83 defaults to 873. 85 Encoding considerations: since the rsync URI is defined using 86 standard elements from RFC 3986, no special encoding considerations 87 are present. 89 Applications/protocols that use this URI scheme name: the only 90 application that uses rsync URIs is rsync. 92 Interoperability considerations: since only one application is 93 expected to make use of rsync URIs, this URI scheme is expected to 94 have few interoperability concerns. 96 Security considerations: Section 7 of RFC 3986 describes general 97 security considerations for URI schemes. The considerations about 98 reliability and consistency, malicious construction, rare IP address 99 formats, sensitive information, and semantic attacks all apply to 100 rsync URIs. The considerations about transcoding do not apply. 101 Given how rsync is regularly used, it is expected that most 102 applications will not be bothered by data accessed via a given rsync 103 URI changing over time. 105 Contact: Russ Housley 107 Author/Change controller: Russ Housley 109 References: see Section 5. 111 3. IANA Considerations 113 IANA has registered the rsync provisional URI scheme using the 114 template in Section 2. 116 4. Security Considerations 118 Many security considerations for the usage of URIs are discussed in 119 Section 7 of [RFC3986]. The considerations about reliability and 120 consistency, malicious construction, rare IP address formats, 121 sensitive information, and semantic attacks all apply to rsync URIs. 122 The considerations about transcoding do not apply. The rsync URI 123 scheme has no particularly unique security considerations. 125 5. Normative References 127 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 128 Resource Identifier (URI): Generic Syntax", STD 66, 129 RFC 3986, January 2005. 131 [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and 132 Registration Procedures for New URI Schemes", BCP 35, 133 RFC 4395, February 2006. 135 Authors' Addresses 137 Samuel Weiler 138 SPARTA, Inc. 139 7110 Samuel Morse Drive 140 Columbia, Maryland 21046 141 US 143 Email: weiler@tislabs.com 145 Dave Ward 146 Cisco Systems 147 170 W. Tasman Dr. 148 San Jose, California 93134 149 US 151 Email: dward@cisco.com 153 Russ Housley 154 Vigil Security, LLC 155 918 Spring Knoll Drive 156 Herndon, Virginia 20170 157 US 159 Email: housley@vigilsec.com