Internet Engineering Task Force (IETF) S. Weiler
Request for Comments: 5781 SPARTA, Inc.
Category: Informational D. Ward
ISSN: 2070-1721 Juniper
R. Housley
Vigil Security
February 2010
Internet Engineering Task Force (IETF) S. Weiler
Request for Comments: 5781 SPARTA, Inc.
Category: Informational D. Ward
ISSN: 2070-1721 Juniper
R. Housley
Vigil Security
February 2010
The rsync URI Scheme
rsync-URI方案
Abstract
摘要
This document specifies the rsync Uniform Resource Identifier (URI) scheme.
本文档指定rsync统一资源标识符（URI）方案。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5781.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc5781.
Copyright Notice
版权公告
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2010 IETF信托基金和确定为文件作者的人员。版权所有。
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 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
URIs were previously defined in RFC 2396, which was obsoleted by RFC 3986 [RFC3986]. The procedures for registering new URI schemes are defined in RFC 4395 [RFC4395]. The rsync utility provides fast incremental file transfer [rsync]. This document defines a URI scheme for rsync.
URI以前是在RFC 2396中定义的，RFC 3986[RFC3986]已将其淘汰。注册新URI方案的过程在RFC 4395[RFC4395]中定义。rsync实用程序提供快速增量文件传输[rsync]。本文档为rsync定义了一个URI方案。
This section contains the registration template for the rsync URI scheme in accordance with RFC 4395 [RFC4395]. This URI scheme is for the rsync protocol using TCP as the transport protocol. Other transports, such as rsync over SSH, are not supported by this URI scheme.
本节包含符合RFC 4395[RFC4395]的rsync URI方案的注册模板。此URI方案用于使用TCP作为传输协议的rsync协议。此URI方案不支持其他传输，例如SSH上的rsync。
URI scheme name: rsync
URI方案名称：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:
URI方案语法：rsync URI描述rsync应用程序的源或目标，包括主机名、路径以及可选的用户和端口。rsync URI的一般形式为：
rsync://[user@]host[:PORT]/Source
rsync://[user@]host[:PORT]/Source
The rsync URI follows the general syntax from RFC 3986 and is defined by the following ABNF [RFC5234]:
rsync URI遵循RFC 3986中的通用语法，并由以下ABNF[RFC5234]定义：
rsyncuri = "rsync:" hier-part ; See RFC 3986 for the definition ; of hier-part
rsyncuri=“rsync:”更高的部分；定义见RFC 3986；上半部分
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.
URI方案语义：rsync URI可以用作rsync应用程序的源或目标。如果未指定端口，则默认为873。
Encoding considerations: Since the rsync URI is defined using standard elements from RFC 3986, no special encoding considerations are present.
编码注意事项：由于rsync URI是使用RFC 3986中的标准元素定义的，因此不存在特殊的编码注意事项。
Applications/protocols that use this URI scheme name: The only application that uses rsync URIs is rsync.
使用此URI方案名称的应用程序/协议：唯一使用rsync URI的应用程序是rsync。
Interoperability considerations: Since only one application is expected to make use of rsync URIs, this URI scheme is expected to have few interoperability concerns.
互操作性注意事项：由于预期只有一个应用程序会使用rsync URI，因此此URI方案预计不会有什么互操作性问题。
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.
安全注意事项：RFC3986的第7节描述了URI方案的一般安全注意事项。关于可靠性和一致性、恶意构造、罕见的IP地址格式、敏感信息和语义攻击的考虑都适用于rsync URI。关于代码转换的考虑不适用。考虑到rsync是如何被经常使用的，预计大多数应用程序不会因为通过给定rsync URI访问的数据随时间的变化而受到影响。
Contact: Russ Housley <housley@vigilsec.com>
Contact: Russ Housley <housley@vigilsec.com>
Author/Change controller: Russ Housley <housley@vigilsec.com>
Author/Change controller: Russ Housley <housley@vigilsec.com>
References: see Section 5.
参考文献：见第5节。
IANA has registered the rsync provisional URI scheme using the template in Section 2.
IANA已经使用第2节中的模板注册了rsync临时URI方案。
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.
[RFC3986]第7节讨论了使用URI的许多安全注意事项。关于可靠性和一致性、恶意构造、罕见的IP地址格式、敏感信息和语义攻击的考虑都适用于rsync URI。关于代码转换的考虑不适用。rsync URI方案没有特别独特的安全考虑。
The security considerations of the rsync protocol are not covered in this document.
本文档不包括rsync协议的安全注意事项。
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，2005年1月。
[RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and Registration Procedures for New URI Schemes", BCP 35, RFC 4395, February 2006.
[RFC4395]Hansen，T.，Hardie，T.，和L.Masinter，“新URI方案的指南和注册程序”，BCP 35，RFC 4395，2006年2月。
[RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5234]Crocker，D.，Ed.，和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，2008年1月。
[rsync] http://rsync.samba.org/.
[rsync]http://rsync.samba.org/.
Authors' Addresses
作者地址
Samuel Weiler SPARTA, Inc. 7110 Samuel Morse Drive Columbia, Maryland 21046 US
美国马里兰州哥伦比亚市塞缪尔·莫尔斯大道7110号塞缪尔·韦勒斯巴达公司，邮编：21046
EMail: weiler@tislabs.com
EMail: weiler@tislabs.com
Dave Ward Juniper Networks 1194 North Mathilda Avenue Sunnyvale, California 94089-1206 US
Dave Ward Juniper Networks美国加利福尼亚州桑尼维尔北玛蒂尔达大道1194号，邮编94089-1206
EMail: dward@juniper.net
EMail: dward@juniper.net
Russ Housley Vigil Security, LLC 918 Spring Knoll Drive Herndon, Virginia 20170 US
Russ Housley Vigil Security，LLC 918 Spring Knoll Drive Herndon，弗吉尼亚州，美国20170
EMail: housley@vigilsec.com
EMail: housley@vigilsec.com