Internet Engineering Task Force (IETF) R. Alimi, Ed.
Request for Comments: 6392 Google
Category: Informational A. Rahman, Ed.
ISSN: 2070-1721 InterDigital Communications, LLC
Y. Yang, Ed.
Yale University
October 2011
Internet Engineering Task Force (IETF) R. Alimi, Ed.
Request for Comments: 6392 Google
Category: Informational A. Rahman, Ed.
ISSN: 2070-1721 InterDigital Communications, LLC
Y. Yang, Ed.
Yale University
October 2011
A Survey of In-Network Storage Systems
网络中存储系统的研究综述
Abstract
摘要
This document surveys deployed and experimental in-network storage systems and describes their applicability for the DECADE (DECoupled Application Data Enroute) architecture.
本文档概述了在网络存储系统中部署和试验的存储系统，并描述了它们对DECED（去耦应用程序数据途中传输）体系结构的适用性。
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/rfc6392.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6392.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 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许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................3
2. Survey Overview .................................................3
2.1. Terminology and Concepts ...................................3
2.2. Historical Context .........................................3
3. In-Network Storage System Components ............................5
3.1. Data Access Interface ......................................5
3.2. Data Management Operations .................................5
3.3. Data Search Capability .....................................6
3.4. Access Control Authorization ...............................6
3.5. Resource Control Interface .................................6
3.6. Discovery Mechanism ........................................7
3.7. Storage Mode ...............................................7
4. In-Network Storage Systems ......................................7
4.1. Amazon S3 ..................................................7
4.2. BranchCache ................................................9
4.3. Cache-and-Forward Architecture ............................11
4.4. Cloud Data Management Interface ...........................12
4.5. Content Delivery Network ..................................14
4.6. Delay-Tolerant Network ....................................16
4.7. Named Data Networking .....................................18
4.8. Network of Information ....................................19
4.9. Network Traffic Redundancy Elimination ....................22
4.10. OceanStore ...............................................23
4.11. P2P Cache ................................................24
4.12. Photo Sharing ............................................26
4.13. Usenet ...................................................28
4.14. Web Cache ................................................29
4.15. Observations Regarding In-Network Storage Systems ........31
5. Storage and Other Related Protocols ............................32
5.1. HTTP ......................................................32
5.2. iSCSI .....................................................33
5.3. NFS .......................................................34
5.4. OAuth .....................................................36
5.5. WebDAV ....................................................37
5.6. Observations Regarding Storage and Related Protocols ......39
6. Conclusions ....................................................40
7. Security Considerations ........................................40
8. Contributors ...................................................40
9. Acknowledgments ................................................41
10. Informative References ........................................41
1. Introduction ....................................................3
2. Survey Overview .................................................3
2.1. Terminology and Concepts ...................................3
2.2. Historical Context .........................................3
3. In-Network Storage System Components ............................5
3.1. Data Access Interface ......................................5
3.2. Data Management Operations .................................5
3.3. Data Search Capability .....................................6
3.4. Access Control Authorization ...............................6
3.5. Resource Control Interface .................................6
3.6. Discovery Mechanism ........................................7
3.7. Storage Mode ...............................................7
4. In-Network Storage Systems ......................................7
4.1. Amazon S3 ..................................................7
4.2. BranchCache ................................................9
4.3. Cache-and-Forward Architecture ............................11
4.4. Cloud Data Management Interface ...........................12
4.5. Content Delivery Network ..................................14
4.6. Delay-Tolerant Network ....................................16
4.7. Named Data Networking .....................................18
4.8. Network of Information ....................................19
4.9. Network Traffic Redundancy Elimination ....................22
4.10. OceanStore ...............................................23
4.11. P2P Cache ................................................24
4.12. Photo Sharing ............................................26
4.13. Usenet ...................................................28
4.14. Web Cache ................................................29
4.15. Observations Regarding In-Network Storage Systems ........31
5. Storage and Other Related Protocols ............................32
5.1. HTTP ......................................................32
5.2. iSCSI .....................................................33
5.3. NFS .......................................................34
5.4. OAuth .....................................................36
5.5. WebDAV ....................................................37
5.6. Observations Regarding Storage and Related Protocols ......39
6. Conclusions ....................................................40
7. Security Considerations ........................................40
8. Contributors ...................................................40
9. Acknowledgments ................................................41
10. Informative References ........................................41
DECADE (DECoupled Application Data Enroute) is an architecture that provides applications with access to provider-based in-network storage for content distribution (hereafter referred to as only "in-network storage" in this document). With access to in-network storage, content distribution applications can be designed to place less load on network infrastructure. As a simple example, a peer of a Peer-to-Peer (P2P) application may upload to other peers through its in-network storage, saving its usage of last-mile uplink bandwidth. See [1] for further discussion.
十年（DECoupled Application Data-InRoute）是一种体系结构，它为应用程序提供对基于提供商的网络存储中的内容分发的访问（在本文档中仅称为“网络存储中”）。通过访问网络内存储，可以设计内容分发应用程序，以减少网络基础架构上的负载。作为一个简单的示例，对等（P2P）应用程序的对等方可以通过其网络内存储上传到其他对等方，从而节省其最后一英里上行链路带宽的使用。有关进一步的讨论，请参见[1]。
A major motivation for DECADE is the substantial increase in capacity and reduction in cost offered by storage systems. For example, over the last two decades, there has been at least a 30-fold increase in the amount of storage that a customer can get for a given price (for flash memory and hard disk drives) [2] [3] [4].
这十年的一个主要动机是存储系统提供的容量大幅增加和成本降低。例如，在过去二十年中，客户以给定价格（闪存和硬盘驱动器）可以获得的存储量至少增加了30倍[2][3][4]。
High-capacity and low-cost in-network storage devices introduce substantial opportunities. One example of in-network storage is content caches supporting Web and P2P content. DECADE differs from existing content caches whose control fully resides with the owners of the caching devices in that DECADE also allows applications to control access to their allocated in-network storage, as well as the resources consumed while accessing that storage (bandwidth, connections, storage space). While designed in the context of P2P applications, DECADE may be useful to other applications as well. This document provides details on deployed and experimental in-network storage solutions, and evaluates their suitability for DECADE.
高容量和低成本的网络存储设备带来了大量的机会。网络存储的一个例子是支持Web和P2P内容的内容缓存。十年不同于现有内容缓存，它的控制权完全掌握在该十年中缓存设备的所有者手中，还允许应用程序控制对其分配的网络存储的访问，以及访问该存储时消耗的资源（带宽、连接、存储空间）。虽然是在P2P应用程序的背景下设计的，但TEADE也可能对其他应用程序有用。本文档详细介绍了已部署和正在试验的网络存储解决方案，并评估了它们在未来十年中的适用性。
We note that the survey presented in this document is only representative of the research in this area. Rather than trying to enumerate an exhaustive list, we have chosen some typical techniques that lead to derivative works.
我们注意到，本文件中的调查仅代表该领域的研究。我们并没有试图列举一个详尽的列表，而是选择了一些典型的技术来衍生作品。
This document uses terms defined in [1].
本文件使用[1]中定义的术语。
In-network storage has been used previously in numerous scenarios to reduce network traffic and enable more efficient content distribution. This section presents a brief history of content distribution techniques and illustrates how DECADE relates to past
以前，在许多场景中都使用了网络存储，以减少网络流量并实现更高效的内容分发。本节简要介绍内容分发技术的历史，并说明十年与过去十年的关系
approaches. Systems have been developed with particular use cases in mind. Thus, this survey is not meant to point out shortcomings of existing solutions, but rather to indicate where certain capabilities required in DECADE [5] are not provided by existing systems.
方法。系统的开发考虑了特定的用例。因此，本次调查的目的不是指出现有解决方案的缺点，而是指出现有系统无法提供十年[5]所需的某些功能。
In the early stage of Internet development, most Web content was stored at a central server, and clients requested Web content from the central server. In this architecture, the central server was required to provide a large amount of bandwidth. As more and more users access Web content, a central server can become overloaded. The use of Web caches is one technique to reduce load on a central server. Web caches store frequently requested content and provide bandwidth for serving the content to clients.
在Internet开发的早期阶段，大多数Web内容存储在中央服务器上，客户端从中央服务器请求Web内容。在这种体系结构中，需要中央服务器提供大量带宽。随着越来越多的用户访问Web内容，中央服务器可能会过载。使用Web缓存是减少中央服务器负载的一种技术。Web缓存存储频繁请求的内容，并为向客户端提供内容服务提供带宽。
The ongoing growth of broadband technology in the worldwide market has been driven by the hunger of customers for new multimedia services as well as Web content. In particular, the use of audio and video streaming formats has become common for delivery of rich information to the public, both residential and business.
宽带技术在全球市场的持续增长是由客户对新的多媒体服务和网络内容的渴望所驱动的。特别是，音频和视频流格式的使用已成为向公众（包括住宅和商业）提供丰富信息的常见方式。
To overcome this challenge of massive multimedia consumption, just installing more Web caches will not be enough. Moving content closer to the consumer results in greater network efficiency, improved Quality of Service (QoS), and lower latency, while facilitating personalization of content through broadband content applications. In these edge technologies, Content Delivery Networks (CDNs) are a representative technique. CDNs are based on a large-scale distributed network of servers located closer to customers for efficient delivery of digital content, including various forms of multimedia content.
要克服这种大规模多媒体消费的挑战，仅仅安装更多的Web缓存是不够的。将内容移动到更靠近消费者的位置可以提高网络效率、提高服务质量（QoS）和降低延迟，同时通过宽带内容应用程序促进内容的个性化。在这些边缘技术中，内容交付网络（CDN）是一种典型的技术。CDN基于大型分布式服务器网络，这些服务器位于离客户较近的位置，用于高效地交付数字内容，包括各种形式的多媒体内容。
Although CDNs are an effective means of information access and delivery, there are two barriers to making CDNs a more common service: cost and replication integrity. Deploying a CDN with its associated infrastructure is expensive. A CDN also requires administrative control over nodes with large storage capacity at geographically dispersed locations with adequate connectivity. CDNs can be scalable, but due to this administrative and cost overhead, they are not rapidly deployable for the common user.
虽然CDN是一种有效的信息访问和交付手段，但要使CDN成为一种更常见的服务，有两个障碍：成本和复制完整性。部署CDN及其相关基础架构的成本很高。CDN还需要对地理位置分散且具有足够连接性的具有大存储容量的节点进行管理控制。CDN是可扩展的，但由于这种管理和成本开销，它们不能快速部署给普通用户。
The emergence and maturation of P2P has allowed improvements to many network applications. P2P allows the use of client resources, such as CPU, memory, storage, and bandwidth, for serving content. This can reduce the amount of resources required by a content provider. Multimedia content delivery using various P2P or peer-assisted frameworks has been shown to greatly reduce the dependence on CDNs and central content servers. However, the popularity of P2P applications has resulted in increased traffic on ISP networks. P2P
P2P的出现和成熟使得许多网络应用得以改进。P2P允许使用客户端资源（如CPU、内存、存储和带宽）来服务内容。这可以减少内容提供商所需的资源量。使用各种P2P或对等辅助框架的多媒体内容交付已被证明可以大大减少对CDN和中央内容服务器的依赖。然而，P2P应用的普及导致了ISP网络流量的增加。对等网络
caches (both transparent and non-transparent) have been introduced as a way to reduce the burden. Though they can be effective in reducing traffic in certain areas of ISP networks, P2P caches have their shortcomings. In particular, they are application-dependent and thus difficult to keep up to date with new and evolving P2P application protocols. Second, applications may benefit from explicit control of in-network storage, which P2P caches do not provide. See [1] for further discussion.
缓存（透明和非透明）已经被引入，作为一种减轻负担的方法。虽然P2P缓存可以有效地减少ISP网络某些区域的流量，但它们也有其缺点。特别是，它们依赖于应用程序，因此很难跟上新的和不断发展的P2P应用程序协议。其次，应用程序可能受益于对网络存储的显式控制，而P2P缓存不提供这种控制。有关进一步的讨论，请参见[1]。
DECADE aims to provide a standard protocol allowing P2P applications (including content providers) to make use of in-network storage to reduce the traffic burden on ISP networks, while enabling P2P applications to control access to content they have placed in in-network storage.
TEDEC旨在提供一种标准协议，允许P2P应用程序（包括内容提供商）利用网络存储来减少ISP网络的流量负担，同时使P2P应用程序能够控制对其放入网络存储中的内容的访问。
Before surveying individual technologies, we describe the basic components of in-network storage. For consistency and for ease of comparison, we use the same model to evaluate each storage technology in this document.
在介绍各种技术之前，我们先介绍网络存储的基本组件。为了一致性和便于比较，我们在本文档中使用相同的模型来评估每种存储技术。
Note that the network protocol(s) used by a given storage system are also an important part of the design. We omit details of particular protocol choices in this document.
请注意，给定存储系统使用的网络协议也是设计的一个重要部分。在本文档中，我们省略了特定协议选择的细节。
A set of operations is made available to a user for accessing data in the in-network storage system. Solutions typically allow both read and write operations, though the mechanisms for doing so can differ drastically.
一组操作可供用户访问网络存储系统中的数据。解决方案通常允许读操作和写操作，尽管这样做的机制可能会有很大的不同。
Storage systems may provide users the ability to manage stored content. For example, operations such as delete and move may be provided to users. In this survey, we focus on data management operations that are provided to users and omit those provided to system administrators.
存储系统可以为用户提供管理存储内容的能力。例如，可以向用户提供诸如删除和移动之类的操作。在本次调查中，我们重点关注提供给用户的数据管理操作，而忽略了提供给系统管理员的数据管理操作。
Some storage systems may provide the capability to search or enumerate content that has been stored. In this survey, we focus on search capabilities that are provided to users and omit those provided to system administrators. An example of a search would be to find the list of items stored by a given user over a given period of time.
某些存储系统可能提供搜索或枚举已存储内容的功能。在本次调查中，我们重点关注提供给用户的搜索功能，而忽略了提供给系统管理员的搜索功能。搜索的一个例子是查找给定用户在给定时间段内存储的项目列表。
Storage systems typically allow a user, content owner, or some other entity to define the access policies for the in-network storage system. The in-network storage system then checks the authorization of a user before it stores or retrieves content. We define three types of access control authorization: public-unrestricted, public-restricted, and private.
存储系统通常允许用户、内容所有者或其他实体定义网络存储系统的访问策略。然后，网络内存储系统在存储或检索内容之前检查用户的授权。我们定义了三种类型的访问控制授权：public unrestricted、public restricted和private。
"Public-unrestricted" refers to content on an in-network storage system that is widely available to all clients (i.e., without restrictions). An example is accessing Wikipedia on the Web, or anonymous access to FTP sites.
“公共无限制”是指网络存储系统中的内容，所有客户端均可广泛使用（即，无限制）。例如在网上访问维基百科，或者匿名访问FTP站点。
"Public-restricted" refers to content on an in-network storage system that is available to a restricted (though still potentially large) set of clients, but that does not require any confidential credentials from the client. An example is some content (e.g., a TV show episode) on the Internet that can only be viewable in selected countries or networks (i.e., white/black lists or black-out areas).
“公共受限”是指网络存储系统中的内容，这些内容可供受限（尽管可能仍然很大）客户端使用，但不需要客户端提供任何机密凭据。例如，互联网上的某些内容（如电视节目插曲）只能在选定的国家或网络中查看（即白名单/黑名单或黑名单区域）。
"Private" refers to content on an in-network storage system that is only made available to one or more clients presenting the required confidential credentials (e.g., password or key). This content is not available to anyone without the proper confidential access credentials.
“专用”是指网络存储系统上的内容，仅提供给一个或多个提供所需机密凭据（例如密码或密钥）的客户端。没有适当的机密访问凭据，任何人都无法访问此内容。
Note that a combination of access control types may be applicable for a given scenario. For example, the retrieval (read) of content from an in-network storage system may be public-unrestricted, but the storage (write) to the same system may be private.
请注意，访问控制类型的组合可能适用于给定场景。例如，从网络内存储系统检索（读取）内容可以是公共的，而不受限制，但是对同一系统的存储（写入）可以是私有的。
This is the interface through which users manage the resources on in-network storage systems that can be used by other peers, e.g., the bandwidth or connections. The storage system may also allow users to indicate a time for which resources are granted.
这是用户管理网络存储系统上可供其他对等方使用的资源（例如带宽或连接）的接口。存储系统还允许用户指示授予资源的时间。
Users use the discovery mechanism to find the location of in-network storage, find an access interface or resource control interface, or find other interfaces of in-network storage.
用户使用发现机制查找网络存储的位置、查找访问接口或资源控制接口，或查找网络存储的其他接口。
Storage systems may use the following modes of storage: file system, object-based, or block-based.
存储系统可以使用以下存储模式：文件系统、基于对象或基于块。
A file system typically organizes files into a hierarchical tree structure. Each level of the hierarchy normally contains zero or more directories, each with zero or more files. A file system may also be flat or use some other organizing principle.
文件系统通常将文件组织成分层树结构。层次结构的每个级别通常包含零个或多个目录，每个目录都包含零个或多个文件。文件系统也可以是扁平的，或者使用其他一些组织原则。
We define an object-based storage mode as one that stores discrete chunks of data (e.g., IP datagrams or another type of aggregation useful to an application) without a pre-defined hierarchy or meta-structure.
我们将基于对象的存储模式定义为一种存储离散数据块（例如，IP数据报或对应用程序有用的另一种聚合类型）的存储模式，而无需预定义的层次结构或元结构。
We define a block-based storage mode as one that stores a raw sequence of bytes, with a client being able to read and/or write data at offsets within that sequence. Data is typically accessed in blocks for efficiency. A common example for this storage mode is raw access to a hard disk.
我们将基于块的存储模式定义为存储原始字节序列的存储模式，客户机能够在该序列中的偏移量处读取和/或写入数据。为了提高效率，数据通常分块访问。这种存储模式的一个常见示例是对硬盘的原始访问。
In this survey, we define "storage mode" to refer to how data is structured within the system, which may not be the same as how it is accessed by a client. For example, a caching system may cache objects with hierarchical names, but may internally use an object-based storage mode.
在本次调查中，我们将“存储模式”定义为系统内数据的结构，这可能与客户端访问数据的方式不同。例如，缓存系统可以缓存具有分层名称的对象，但可以在内部使用基于对象的存储模式。
This section surveys in-network storage systems using the methodology defined above. The survey includes some systems that are widely deployed today, some systems that are just being deployed, and some experimental systems. The survey covers both traditional client-server architectures and P2P architectures. The surveyed systems are listed in alphabetical order. Also, for each system, a brief explanation of the relevance to DECADE is given.
本节使用上面定义的方法对网络存储系统进行调查。该调查包括目前广泛部署的一些系统、一些刚刚部署的系统和一些实验系统。该调查涵盖了传统的客户机-服务器体系结构和P2P体系结构。调查的系统按字母顺序列出。此外，对于每一个系统，都给出了与十年相关的简要说明。
Amazon S3 (Simple Storage Service) [6] provides an online storage service using Web (HTTP) interfaces. Users create buckets, and each bucket can contain stored objects. Users are provided an interface
AmazonS3（简单存储服务）[6]使用Web（HTTP）接口提供在线存储服务。用户创建bucket，每个bucket可以包含存储的对象。为用户提供了一个接口
through which they can manage their buckets. Amazon S3 is a popular backend storage service for other services. Other related storage services are the Blob Service provided by Windows Azure [7], Google Storage for Developers [8], and Dropbox [9].
通过它，他们可以管理自己的水桶。AmazonS3是其他服务的流行后端存储服务。其他相关的存储服务包括Windows Azure提供的Blob服务[7]、Google storage for Developers[8]和Dropbox[9]。
Amazon S3 is a very widely used (deployed) example of in-network storage. Amazon S3 leases the storage to third-party companies for disparate services. In particular, Amazon S3 has a rich model for authorization (using signed queries) to integrate with a wide variety of use cases. A focus for Amazon S3 is scalability. Particular simplifications that were made are the absence of a general, hierarchical namespace and the inability to update the contents of existing data.
AmazonS3是一个非常广泛使用（部署）的网络存储示例。Amazon S3将存储租赁给第三方公司，以提供不同的服务。特别是，AmazonS3有一个丰富的授权模型（使用签名查询）来集成各种各样的用例。AmazonS3的一个重点是可伸缩性。所做的特别简化是缺少通用的分层名称空间，并且无法更新现有数据的内容。
Users can read and write objects.
用户可以读取和写入对象。
Users can delete previously stored objects.
用户可以删除以前存储的对象。
Users can list contents of buckets to find objects matching desired criteria.
用户可以列出存储桶的内容，以查找符合所需条件的对象。
All methods of access control are supported for clients: public-unrestricted, public-restricted, and private.
客户端支持所有访问控制方法：public unrestricted、public restricted和private。
For example, access to stored objects can be restricted by an owner, a list of other Amazon S3 Web Service users, or all Amazon S3 Web Service users; or can be open to all users (anonymous access). Another option is for the owner to generate and sign a query (e.g., a query to read an object) that can be used by any user until an owner-defined expiration time.
例如，所有者、其他AmazonS3Web服务用户列表或所有AmazonS3Web服务用户可以限制对存储对象的访问；或者可以对所有用户开放（匿名访问）。另一个选项是所有者生成并签署查询（例如，读取对象的查询），该查询可供任何用户使用，直到所有者定义的过期时间。
Not provided.
没有提供。
Users are provided a well-known DNS name (either a default provided by Amazon S3, or one customized by a particular user). Users accessing S3 storage use DNS to discover an IP address where S3 requests can be sent.
向用户提供一个众所周知的DNS名称（AmazonS3提供的默认名称，或特定用户自定义的名称）。访问S3存储的用户使用DNS发现可以发送S3请求的IP地址。
Object-based, with the extension that objects can be organized into user-defined buckets.
基于对象，扩展为可以将对象组织到用户定义的存储桶中。
BranchCache [10] is a feature integrated into Windows (Windows 7 and Windows Server 2008R2) that aims to optimize enterprise branch office file access over WAN links. The main goals are to reduce WAN link utilization and improve application responsiveness by caching and sharing content within a branch while still maintaining end-to-end security. BranchCache allows files retrieved from the Web servers and file servers located in headquarters or data centers to be cached in remote branch offices, and shared among users in the same branch accessing the same content. BranchCache operates transparently by instrumenting the HTTP and Server Message Block (SMB) components of the networking stack. It provides two modes of operation: Distributed Cache and Hosted Cache.
BranchCache[10]是集成到Windows（Windows 7和Windows Server 2008R2）中的一项功能，旨在通过WAN链接优化企业分支办公室文件访问。主要目标是通过缓存和共享分支内的内容，同时保持端到端的安全性，从而降低WAN链路利用率并提高应用程序响应能力。BranchCache允许从Web服务器和位于总部或数据中心的文件服务器检索的文件缓存在远程分支办公室中，并在访问相同内容的同一分支中的用户之间共享。BranchCache通过检测网络堆栈的HTTP和服务器消息块（SMB）组件透明地运行。它提供两种操作模式：分布式缓存和托管缓存。
In both modes, a client always contacts a BranchCache-enabled content server first to get the content identifiers for local search. If the content is cached locally, the client then retrieves the content within the branch. Otherwise, the client will go back to the original content server to request the content. The two modes differ in how the content is shared.
在这两种模式中，客户端总是首先联系启用BranchCache的内容服务器，以获取用于本地搜索的内容标识符。如果内容在本地缓存，则客户端将检索分支内的内容。否则，客户端将返回原始content server请求内容。这两种模式在内容共享方式上有所不同。
In the Hosted Cache mode, a locally provisioned server acts as a cache for files retrieved from the servers. After getting the content identifiers, the client first consults the cache for the desired file. If it is not present in the cache, the client retrieves it from the content server and sends it to the cache for storage.
在托管缓存模式下，本地配置的服务器充当从服务器检索的文件的缓存。在获取内容标识符之后，客户机首先查阅缓存以查找所需的文件。如果它不在缓存中，客户端将从content server检索它并将其发送到缓存进行存储。
In the Distributed Cache mode, a client first queries other clients in the same network using the Web Services Discovery multicast protocol [11]. As in the Hosted Cache mode, the client retrieves the file from the content server if it is not available locally. After retrieving the file (either from another client or the content server), the client stores the file locally.
在分布式缓存模式下，客户端首先使用Web服务发现多播协议查询同一网络中的其他客户端[11]。与托管缓存模式一样，如果文件在本地不可用，客户端将从content server检索该文件。从另一个客户端或content server检索文件后，客户端将文件存储在本地。
The original content server always authorizes requests from clients. Cached content is encrypted such that clients can decrypt the data only using keys derived from metadata returned by the content server. In addition to instrumenting the networking stack at clients, content servers must also support BranchCache.
原始content server始终授权来自客户端的请求。缓存的内容是加密的，因此客户端只能使用从content server返回的元数据派生的密钥来解密数据。除了在客户端检测网络堆栈，内容服务器还必须支持BranchCache。
BranchCache is an example of an in-network storage system primarily targeted at enterprise networks. It supports a P2P-like mode (Distributed Cache) as well as a client-server mode (Hosted Cache). Integration into the Microsoft OS will ensure wide distribution of this in-network storage technology.
BranchCache是主要针对企业网络的网络内存储系统的一个示例。它支持类P2P模式（分布式缓存）和客户机-服务器模式（托管缓存）。与Microsoft操作系统的集成将确保这种网络存储技术的广泛应用。
Clients transparently retrieve (read) data from a cache (on a client or a Hosted Cache), since BranchCache operates by instrumenting the networking stack. In the Hosted Cache mode, clients write data to the Hosted Cache once it is retrieved from the content server.
客户端从缓存（在客户端或托管缓存上）透明地检索（读取）数据，因为BranchCache通过检测网络堆栈进行操作。在托管缓存模式下，从content server检索数据后，客户端会将数据写入托管缓存。
Not provided.
没有提供。
Not provided.
没有提供。
The access control method for clients is private. For example, transferred content is encrypted, and can only be decrypted by keys derived from data received from the original content server. Though data may be transferred to unauthorized clients, end-to-end security is maintained by only allowing authorized clients to decrypt the data.
客户端的访问控制方法是私有的。例如，传输的内容是加密的，并且只能通过从原始content server接收的数据派生的密钥进行解密。尽管数据可能会传输到未经授权的客户端，但端到端安全性是通过仅允许授权客户端解密数据来维护的。
The storage capacity of caches on the clients and Hosted Caches is configurable by system administrators. The Hosted Cache further allows configuration of the maximum number of simultaneous client accesses. In the Distributed Cache mode, exponential back-off and throttling mechanisms are utilized to prevent reply storms of popular content requests. The client will also spread data-block access among multiple serving clients that have the content (complete or partial) to improve latency and provide some load balancing.
客户端和托管缓存上缓存的存储容量可由系统管理员配置。托管缓存还允许配置最大数量的同时客户端访问。在分布式缓存模式中，利用指数回退和节流机制来防止流行内容请求的回复风暴。客户端还将在具有内容（完整或部分）的多个服务客户端之间传播数据块访问，以改善延迟并提供一些负载平衡。
The Distributed Cache mode uses multicast for discovery of other clients and content within a local network. Currently, the Hosted Cache mode uses policy provisioning or manual configuration of the server used as the Hosted Cache. In this mode, the address of the server may be found via DNS.
分布式缓存模式使用多播来发现本地网络中的其他客户端和内容。当前，托管缓存模式使用策略设置或手动配置用作托管缓存的服务器。在此模式下，可以通过DNS找到服务器的地址。
Object-based.
基于对象的。
Cache-and-Forward (CNF) [12] is an architecture for content delivery services for the future Internet. In this architecture, storage can be exploited on nodes within the network, either directly on routers or deployed near the routers. CNF is based on the concept of store-and-forward routers with large storage, providing for opportunistic delivery to occasionally disconnected mobile users and for in-network caching of content. The proposed CNF protocol uses reliable hop-by-hop transfer of large data files between CNF routers in place of an end-to-end transport protocol such as TCP.
缓存和转发（CNF）[12]是未来互联网内容交付服务的体系结构。在这种体系结构中，可以直接在路由器上或部署在路由器附近的网络节点上利用存储。CNF基于具有大存储的存储转发路由器的概念，为偶尔断开连接的移动用户提供机会交付，并提供内容的网络内缓存。建议的CNF协议使用CNF路由器之间可靠的逐跳传输大数据文件，而不是端到端传输协议（如TCP）。
CNF is an example of an experimental in-network storage system that would require storage space on (or near) a large number of routers in the Internet if it was deployed. As the name of the system implies, it would provide short-term caching and not long-term network storage.
CNF是一个实验性的网络存储系统的例子，如果部署它，它需要在互联网上的大量路由器上（或附近）存储空间。顾名思义，该系统将提供短期缓存，而不是长期网络存储。
Users implicitly store content at CNF routers by requesting files. End hosts read content from in-network storage by submitting queries for content.
用户通过请求文件在CNF路由器上隐式存储内容。终端主机通过提交内容查询从网络存储中读取内容。
Not provided.
没有提供。
Not provided.
没有提供。
The access control method is public-restricted (to any client that is part of the CNF network).
访问控制方法是公开限制的（对属于CNF网络的任何客户端）。
Not provided.
没有提供。
A query including a location-independent content ID is sent to the network and routed to a CNF router, which handles retrieval of the data and forwarding to the end host.
包括独立于位置的内容ID的查询被发送到网络并路由到CNF路由器，该路由器处理数据的检索并转发到终端主机。
Object-based, with objects representing individual files. The architecture proposes to cache large files in storage within the network, though objects could be made to represent smaller chunks of larger files.
基于对象，对象表示单个文件。该体系结构建议将大型文件缓存在网络中的存储器中，尽管对象可以表示较小的大块大型文件。
The Cloud Data Management Interface (CDMI) is a specification to access and manage cloud storage. CDMI is specified by the Storage Networking Industry Association (SNIA).
云数据管理接口（CDMI）是访问和管理云存储的规范。CDMI由存储网络行业协会（SNIA）指定。
CDMI is a functional interface that applications can use to create, retrieve, update, and delete data elements from the cloud. As part of this interface, the client will be able to discover the capabilities of the cloud storage offering and use this interface to manage containers and the data that is placed in them. In addition, metadata can be set on containers and their contained data elements through this interface [13].
CDMI是一个功能接口，应用程序可以使用它从云中创建、检索、更新和删除数据元素。作为此接口的一部分，客户机将能够发现云存储产品的功能，并使用此接口管理容器和放置在其中的数据。此外，可以通过此接口在容器及其包含的数据元素上设置元数据[13]。
CDMI follows a traditional client-server model, and operates over an HTTP interface using the Representational State Transfer (REST) model. Similar to Amazon S3 buckets (see Section 4.1), users may create containers in which data objects may be stored. Even though data objects may be accessed via a user-defined name within a container, it is also possible to access data objects via a storage-defined Object ID, which is provided in the response upon creation of a data object.
CDMI遵循传统的客户机-服务器模型，并使用表示性状态传输（REST）模型在HTTP接口上运行。与AmazonS3存储桶类似（参见第4.1节），用户可以创建存储数据对象的容器。即使可以通过容器内的用户定义名称访问数据对象，也可以通过存储定义的对象ID访问数据对象，该ID在创建数据对象时在响应中提供。
CDMI is an important initiative to standardize storage interfaces for cloud services, which are rapidly becoming an important type of storage service. In particular, it specifies a set of operations for creating, reading, writing, and managing data objects at a remote server (or set of servers) via HTTP.
CDMI是云服务存储接口标准化的一项重要举措，云服务正迅速成为一种重要的存储服务类型。特别是，它指定了一组操作，用于通过HTTP在远程服务器（或一组服务器）上创建、读取、写入和管理数据对象。
Users can read and write data objects, and also update data in existing data objects. CDMI data objects are sent on the wire embedded as a field in a JavaScript Object Notation (JSON) object. The protocol also defines interfaces in which the contents of data objects can be written via simple HTTP GET/PUT operations.
用户可以读取和写入数据对象，还可以更新现有数据对象中的数据。CDMI数据对象通过内嵌在JavaScript对象表示法（JSON）对象中的字段的线路发送。该协议还定义了一些接口，在这些接口中，数据对象的内容可以通过简单的HTTP GET/PUT操作写入。
Users can delete already-existing data objects. The create operation also supports modes in which the created object is copied or moved from an existing data object.
用户可以删除已有的数据对象。创建操作还支持从现有数据对象复制或移动已创建对象的模式。
Data system metadata also allows users to configure policies regarding time-to-live, after which a data object is automatically deleted, as well as the redundancy with which a data object is stored.
数据系统元数据还允许用户配置有关生存时间的策略，在此之后数据对象将自动删除，以及数据对象存储的冗余。
Users may list the contents of containers to locate data objects matching any desired criteria.
用户可以列出容器的内容，以查找与任何所需条件匹配的数据对象。
All methods of access control for clients are supported: public-unrestricted, public-restricted, and private.
支持客户端的所有访问控制方法：public unrestricted、public restricted和private。
In particular, CDMI allows access to data objects to be protected by Access Control Lists (ACLs) that can allow or restrict access based on user name, group, administrative status, or whether a user is authenticated or anonymous.
尤其是，CDMI允许访问受访问控制列表（ACL）保护的数据对象，ACL可以基于用户名、组、管理状态或用户是否经过身份验证或匿名来允许或限制访问。
CDMI supports attributes 'cdmi_max_latency' and 'cdmi_max_throughput' (set at either the level of containers, or a specific data object), which control the level of service offered to any users accessing a particular data object.
CDMI支持属性“CDMI_max_latency”和“CDMI_max_through”（在容器级别或特定数据对象上设置），它们控制为访问特定数据对象的任何用户提供的服务级别。
Users are provided a well-known DNS name. The DNS name is resolved to determine the IP address to which requests may be sent.
向用户提供一个众所周知的DNS名称。解析DNS名称以确定可向其发送请求的IP地址。
Object-based, with the extension that objects can be organized into user-defined containers.
基于对象，扩展为可以将对象组织到用户定义的容器中。
A CDN provides services that improve performance by minimizing the amount of data transmitted through the network, improving accessibility, and maintaining correctness through content replication. CDNs offer fast and reliable applications and services by distributing content to cache or edge servers located close to users. See [14] for an additional taxonomy and survey.
CDN提供的服务通过最小化通过网络传输的数据量、提高可访问性以及通过内容复制保持正确性来提高性能。CDN通过将内容分发到靠近用户的缓存或边缘服务器，提供快速可靠的应用程序和服务。参见[14]了解更多分类和调查。
A CDN has some combination of content delivery, request routing, distribution, and accounting infrastructures. The content-delivery infrastructure consists of a set of edge servers (also called surrogates) that deliver copies of content to end users. The request-routing infrastructure is responsible for directing client requests to appropriate edge servers. It also interacts with the distribution infrastructure to keep an up-to-date view of the content stored in the CDN caches. The distribution infrastructure moves content from the origin server to the CDN edge servers and ensures consistency of content in the caches. The accounting infrastructure maintains logs of client accesses and records the usage of the CDN servers. This information is used for traffic reporting and usage-based billing.
CDN结合了内容交付、请求路由、分发和记帐基础架构。内容交付基础架构由一组边缘服务器（也称为代理服务器）组成，这些服务器将内容副本交付给最终用户。请求路由基础结构负责将客户端请求定向到适当的边缘服务器。它还与分发基础架构交互，以保持CDN缓存中存储的内容的最新视图。分发基础架构将内容从源服务器移动到CDN边缘服务器，并确保缓存中内容的一致性。会计基础架构维护客户端访问日志，并记录CDN服务器的使用情况。此信息用于流量报告和基于使用情况的计费。
In practice, a CDN typically hosts static content including images, video, media clips, advertisements, and other embedded objects for Web viewing. A focus for CDNs is the ability to publish and deliver content to end users in a reliable and timely manner. A CDN focuses on building its network infrastructure to provide the following services and functionalities: storage and management of content; distribution of content among surrogates; cache management; delivery of static, dynamic, and streaming content; backup and disaster recovery solutions; and monitoring, performance measurement, and reporting.
实际上，CDN通常承载静态内容，包括图像、视频、媒体剪辑、广告和其他用于Web查看的嵌入式对象。CDN的一个重点是能够以可靠和及时的方式向最终用户发布和交付内容。CDN专注于构建其网络基础设施，以提供以下服务和功能：内容的存储和管理；代孕者之间的内容分布；缓存管理；提供静态、动态和流媒体内容；备份和灾难恢复解决方案；以及监控、绩效衡量和报告。
Examples of existing CDNs are Akamai, Limelight, and CloudFront.
现有CDN的示例有Akamai、Limelight和CloudFront。
The following description uses the term "content provider" to refer to the entity purchasing a CDN service, and the term "client" to refer to the subscriber requesting content via the CDN from the content provider.
以下描述使用术语“内容提供商”表示购买CDN服务的实体，使用术语“客户端”表示通过CDN向内容提供商请求内容的订阅者。
CDNs are a very widely used (deployed) example of in-network storage for multimedia content. The existence and operation of the storage system are totally transparent to the end user. CDNs typically require a strong business relationship between the content providers and content distributors, and often the business relationship extends to the ISPs.
CDN是一种广泛使用（部署）的多媒体内容网络存储示例。存储系统的存在和操作对最终用户完全透明。CDN通常要求内容提供商和内容分销商之间建立牢固的业务关系，而且业务关系通常延伸到ISP。
A CDN is typically a closed system, and generally provides only a read (retrieve) access interface to clients. A CDN typically does not provide a write (store) access interface to clients. The content provider can access network edge servers and store content on them, or edge servers can retrieve content from content providers. Client nodes can only retrieve content from edge servers.
CDN通常是一个封闭系统，通常只向客户端提供读取（检索）访问接口。CDN通常不向客户端提供写（存储）访问接口。内容提供商可以访问网络边缘服务器并在其上存储内容，或者边缘服务器可以从内容提供商检索内容。客户端节点只能从边缘服务器检索内容。
A content provider can manage the data distributed in different cache nodes, such as moving popular data objects from one cache node to another cache node, or deleting rarely accessed data objects in cache nodes. User nodes, however, have no right to perform these operations.
内容提供商可以管理分布在不同缓存节点中的数据，例如将常用数据对象从一个缓存节点移动到另一个缓存节点，或者删除缓存节点中很少访问的数据对象。但是，用户节点无权执行这些操作。
A content provider can search or enumerate the data each cache node stores. User nodes cannot perform search operations.
内容提供商可以搜索或枚举每个缓存节点存储的数据。用户节点无法执行搜索操作。
All methods of access control (for reading) are supported for clients: public-unrestricted, public-restricted, and private. Some CDN edge servers allow usage of HTTP basic authentication with the origin server or restrictions by IP address, or they can use a token-based technique to allow the origin server to apply its own authorization criteria.
客户端支持所有访问控制方法（用于读取）：public unrestricted、public restricted和private。某些CDN边缘服务器允许使用源服务器的HTTP基本身份验证或IP地址限制，也可以使用基于令牌的技术允许源服务器应用其自己的授权标准。
As mentioned previously, clients typically cannot write to the CDN. Writing is typically a private operation for the content providers.
如前所述，客户端通常无法写入CDN。写入通常是内容提供者的私有操作。
Not provided.
没有提供。
Content providers can directly find internal CDN cache nodes to store content, since they typically have an explicit business relationship. Clients can locate CDN nodes through DNS or other redirection mechanisms.
内容提供商可以直接找到内部CDN缓存节点来存储内容，因为它们通常具有明确的业务关系。客户端可以通过DNS或其他重定向机制定位CDN节点。
Though the addressing of objects uses URLs that typically refer to objects in a hierarchical fashion, the storage mode is typically object-based.
尽管对象寻址使用的URL通常以分层方式引用对象，但存储模式通常是基于对象的。
The Delay-Tolerant Network (DTN) [15] is an evolution of an architecture originally designed for the Interplanetary Internet. The Interplanetary Internet is a communication system envisioned to provide Internet-like services across interplanetary distances in support of deep space exploration. The DTN architecture can be utilized in various operational environments characterized by severe communication disruptions, disconnections, and high delays (e.g., a month-long loss of connectivity between two planetary networks because of high solar radiation due to sun spots). The DTN architecture is thus suitable for environments including deep space networks, sensor-based networks, certain satellite networks, and underwater acoustic networks.
延迟容忍网络（DTN）[15]是最初为星际互联网设计的体系结构的演变。星际互联网是一种通信系统，旨在跨星际距离提供类似互联网的服务，以支持深空探索。DTN体系结构可用于各种操作环境，其特点是严重的通信中断、断开连接和高延迟（例如，由于太阳黑子的高太阳辐射，两个行星网络之间的连接中断长达一个月）。因此，DTN体系结构适用于包括深空网络、基于传感器的网络、某些卫星网络和水声网络在内的环境。
A key aspect of the DTN is a store-and-forward overlay layer called the "Bundle Protocol" or "Bundle Layer", which exists between the transport and application layers [16]. The Bundle Layer forms a logical overlay that employs persistent storage to help combat long-term network interruptions by providing a store-and-forward service. While traditional IP networks are also based on store-and-forward principles, the amount of time of a packet being kept in "storage" at a traditional IP router is typically on the order of milliseconds (or less). In contrast, the DTN architecture assumes that most Bundle Layer nodes will use some form of persistent storage (e.g., hard disk, flash memory, etc.) for DTN packets because of the nature of the DTN environment.
DTN的一个关键方面是存储转发覆盖层，称为“捆绑协议”或“捆绑层”，它存在于传输层和应用层之间[16]。Bundle层形成一个逻辑覆盖层，它使用持久性存储，通过提供存储转发服务来帮助应对长期网络中断。虽然传统IP网络也基于存储转发原则，但在传统IP路由器上，数据包被保存在“存储器”中的时间通常为毫秒（或更短）。相比之下，由于DTN环境的性质，DTN体系结构假定大多数捆绑层节点将对DTN数据包使用某种形式的持久存储（例如硬盘、闪存等）。
The DTN is an example of an experimental in-network storage system that would require fundamental changes to the Internet protocols.
DTN是一种实验性的网络存储系统，它需要对Internet协议进行根本性的更改。
Users implicitly cause content to be stored (until successfully forwarded) at Bundle Layer nodes by initiating/terminating any transaction that traverses the DTN.
用户通过启动/终止任何穿越DTN的事务，隐式地将内容存储（直到成功转发）到捆绑层节点。
Users can implicitly cause deletion of content stored at Bundle Layer nodes via a "time-to-live" type of parameter that the user can control (for transactions originating from the user).
用户可以通过用户可以控制的“生存时间”类型的参数（对于源自用户的事务），隐式删除存储在捆绑层节点上的内容。
Not provided.
没有提供。
The access control method is public-restricted (to any client that is part of the DTN) or private.
访问控制方法是公开的（限于属于DTN的任何客户端）或私有的。
Not provided.
没有提供。
A Uniform Resource Identifier (URI) approach is used as the basis of the addressing scheme for DTN transactions (and subsequent store-and-forward routing through the DTN network).
统一资源标识符（URI）方法用作DTN事务寻址方案（以及通过DTN网络的后续存储和转发路由）的基础。
Object-based. DTN applications send data to the Bundle Layer, which then breaks the data into segments. These segments are then routed through the DTN network, and stored in Bundle Layer nodes as required (before being forwarded).
基于对象的。DTN应用程序将数据发送到Bundle层，然后Bundle层将数据分成多个段。然后，这些段通过DTN网络路由，并根据需要存储在捆绑层节点中（在转发之前）。
Named Data Networking (NDN) [17] is a research initiative that proposes to move to a new model of addressing and routing for the Internet. NDN uses "named data"-based routing and forwarding, to replace the current IP-address-based model. NDN also uses name-based data caching in the routers.
命名数据网络（NDN）[17]是一项研究计划，旨在转向互联网寻址和路由的新模式。NDN使用基于“命名数据”的路由和转发来取代当前基于IP地址的模型。NDN还在路由器中使用基于名称的数据缓存。
Each NDN Data packet will be assigned a content name and will be cryptographically signed. Data delivery is driven by the requesting end. Routers disseminate name-based prefix announcements by using routing protocols such as Intermediate System to Intermediate System (IS-IS) or the Border Gateway Protocol (BGP). The requester will send out an "Interest" packet, which identifies the name of the data that it wants. Routers that receive this Interest packet will remember the interface it came from and will then forward it on a name-based routing protocol. Once an Interest packet reaches a node that has the desired data, a named Data packet is sent back, which carries both the name and content of the data, along with a digital signature of the producer. This named Data packet is then forwarded back to the original requester on the reverse path of the Interest packet [18].
每个NDN数据包将被分配一个内容名，并将进行加密签名。数据传递由请求端驱动。路由器通过使用诸如中间系统到中间系统（IS-IS）或边界网关协议（BGP）等路由协议来传播基于名称的前缀公告。请求者将发送一个“兴趣”数据包，该数据包标识其所需数据的名称。接收这个感兴趣的数据包的路由器将记住它来自的接口，然后根据基于名称的路由协议转发它。一旦感兴趣的数据包到达具有所需数据的节点，命名的数据包被发送回，该数据包携带数据的名称和内容，以及生产者的数字签名。然后，该命名数据包在兴趣包的反向路径上转发回原始请求者[18]。
A key aspect of NDN is that routers have the capability to cache the named data. If a request for the same data (i.e., same name) comes to the router, then the NDN router will forward the named data stored locally to fulfill the request. The proponents of NDN believe that the network can be designed naturally, matching data delivery characteristics instead of communication between endpoints, because data delivery has become the primary use of the network.
NDN的一个关键方面是路由器具有缓存命名数据的能力。如果路由器收到相同数据（即相同名称）的请求，则NDN路由器将转发本地存储的命名数据以满足该请求。NDN的支持者认为网络可以自然设计，匹配数据交付特征，而不是端点之间的通信，因为数据交付已成为网络的主要用途。
NDN is an example of an experimental in-network storage system that would require storage space on a large number of routers in the Internet. Named Data packets would be kept in storage in the NDN routers and provided to new requesters of the same data.
NDN是一个实验性的网络存储系统的例子，它需要在互联网上的大量路由器上存储空间。命名数据包将保存在NDN路由器中的存储器中，并提供给相同数据的新请求者。
Users implicitly store content at NDN routers by requesting content (the named Data packets) from the network. Subsequent requests by different users for the same content will cause the named Data packets to be read from the NDN routers' in-network storage.
用户通过从网络请求内容（命名数据包），在NDN路由器上隐式存储内容。不同用户对相同内容的后续请求将导致从网络存储中的NDN路由器读取命名数据包。
Users do not have the direct ability to delete content stored in the NDN routers. However, there will be some type of time-to-live parameter associated with the named Data packets, though this has not yet been specified.
用户无法直接删除存储在NDN路由器中的内容。然而，将有一些类型的生存时间参数与命名的数据包相关联，尽管尚未指定。
Not provided.
没有提供。
All methods of access control for clients are supported: public-unrestricted, public-restricted, and private.
支持客户端的所有访问控制方法：public unrestricted、public restricted和private。
The basic security mechanism in NDN is for the sender to digitally sign the content (the named Data packets) that it sends. It is envisioned that a complete access control system can be built on top of NDN, though this has not yet been specified.
NDN中的基本安全机制是发送方对其发送的内容（命名数据包）进行数字签名。设想在NDN的基础上建立一个完整的访问控制系统，尽管这一点尚未明确。
Not provided.
没有提供。
Names are used as the basis of the addressing and discovery scheme for NDN (and subsequent store-and-forward routing through the NDN network). NDN names are assumed to be hierarchical and to be able to be deterministically constructed. This is still an active area of research.
名称用作NDN寻址和发现方案（以及通过NDN网络的后续存储和转发路由）的基础。NDN名称被假定为分层的，并且能够确定地构造。这仍然是一个活跃的研究领域。
Object-based. NDN sends named Data packets through the network. These Data packets are routed through the NDN network and stored in NDN routers.
基于对象的。NDN通过网络发送命名数据包。这些数据包通过NDN网络路由并存储在NDN路由器中。
Similar to NDN (see Section 4.7), Network of Information (NetInf) [19] is another information-centric approach in which the named data objects are the basic component of the networking architecture. NetInf is thus moving away from today's host-centric networking
与NDN（见第4.7节）类似，信息网络（NetInf）[19]是另一种以信息为中心的方法，其中命名数据对象是网络体系结构的基本组件。因此，NetInf正在远离今天以主机为中心的网络
architecture where the nodes in the network are the primary objects. In today's network, the information objects are named relative to the hosts they are stored on (e.g., http://www.example.com/information-object.txt).
网络中的节点是主要对象的体系结构。在当今的网络中，信息对象是相对于其存储的主机命名的（例如。，http://www.example.com/information-object.txt).
The NetInf naming and security framework builds the foundation for an information-centric security model that integrates security deeply into the architecture. In this model, trust is based on the information itself. Information objects (IOs) are given a unique name with cryptographic properties. Together with additional metadata, the name can be used to verify the data integrity as well as several other security properties, such as self-certification, name persistency, and owner authentication and identification. The approach also gives some benefits over the security model in today's host-centric networks, as it minimizes the need for trust in the infrastructure, including the hosts providing the data, the channel, or the resolution service.
NETIF命名和安全框架为以信息为中心的安全模型奠定了基础，该模型将安全性深入地集成到体系结构中。在这个模型中，信任是基于信息本身的。信息对象（IOs）被赋予具有加密属性的唯一名称。该名称与其他元数据一起可用于验证数据完整性以及其他几个安全属性，如自认证、名称持久性以及所有者身份验证和标识。与当今以主机为中心的网络中的安全模型相比，该方法还提供了一些好处，因为它最大限度地减少了对基础架构（包括提供数据、通道或解析服务的主机）的信任需求。
In NetInf, the information objects are published into the network. They are registered with a Name Resolution Service (NRS). The NRS is also used to register network locators that can be used to retrieve data objects that represent the published IOs. When a receiver wants to retrieve an IO, the request for the IO is resolved by the NRS into a set of locators. These locators are then used to retrieve a copy of the data object from the "best" available source(s). NetInf is open to use any type of underlying transport network. The locators can thus be a heterogeneous set, e.g., IPv4, IPv6, Medium Access Control (MAC), etc.
在NetInf中，信息对象发布到网络中。它们在名称解析服务（NRS）中注册。NRS还用于注册网络定位器，这些定位器可用于检索表示已发布IOs的数据对象。当接收器想要检索IO时，NRS将IO请求解析为一组定位器。然后使用这些定位器从“最佳”可用源检索数据对象的副本。NetInf开放使用任何类型的底层传输网络。因此，定位器可以是异构集，例如IPv4、IPv6、媒体访问控制（MAC）等。
NetInf will make extensive use of caching of information objects in the network and will provide network functionality that is similar to what overlay solutions such as CDNs and P2P distribution networks (e.g., BitTorrent) provide today.
NetInf将广泛使用网络中的信息对象缓存，并将提供与覆盖解决方案（如CDN和P2P分发网络（如BitTorrent））类似的网络功能。
NetInf is an example of an experimental information-centric network architecture that will require storage space for storage and caching of information objects on a large number of NetInf nodes in the Internet.
NetInf是一种实验性的以信息为中心的网络体系结构的示例，该体系结构需要存储空间，以便在Internet上的大量NetInf节点上存储和缓存信息对象。
Users will publish IOs with specific IDs into the network. This is done by the client sending a register message to the NRS stating that the IO with the specific ID is available. When another user wishes to retrieve the IO, they will use the given ID to make a request for the IO. The ID is then resolved by the NRS, and the IO is delivered from a nearby in-network storage location.
用户将使用特定ID将IOs发布到网络中。这是通过客户端向NRS发送一条寄存器消息来完成的，该消息声明具有特定ID的IO可用。当其他用户希望检索IO时，他们将使用给定的ID请求IO。然后由NRS解析ID，并从附近的网络存储位置传递IO。
Users do not have the direct ability to delete content stored in the NetInf nodes. However, there can be some type of time-to-live parameter associated with the information objects, though this has not yet been specified.
用户无法直接删除存储在NetInf节点中的内容。但是，可能存在与信息对象关联的某种类型的生存时间参数，尽管尚未指定。
Not provided.
没有提供。
All methods of access control for clients are supported: public-unrestricted, public-restricted, and private. The basic security mechanism in NetInf is for the publisher to digitally sign the content of the information object that it publishes. It is envisioned that a complete access control system can be built on top of NetInf, though this has not yet been specified.
支持客户端的所有访问控制方法：public unrestricted、public restricted和private。NetInf中的基本安全机制是发布者对其发布的信息对象的内容进行数字签名。设想在NetInf的基础上建立一个完整的访问控制系统，尽管这一点尚未明确。
Not provided.
没有提供。
NetInf IDs are used for naming and accessing information objects. The IDs are resolved by the NRS into locators that are used for routing and transport of data through the transport networks. This is still an active area of research.
NetInf ID用于命名和访问信息对象。NRS将ID解析为定位器，用于通过传输网络路由和传输数据。这仍然是一个活跃的研究领域。
Object-based. From an application perspective, NetInf can be used for publishing entire files or chunks of files. NetInf is agnostic to the application perspective and treats everything as information objects.
基于对象的。从应用程序的角度来看，NetInf可用于发布整个文件或文件块。NetInf对应用程序透视图是不可知的，它将所有内容都视为信息对象。
Redundancy Elimination (RE) is used for identifying and removing repeated content from network transfers. This technique has been proposed to improve network performance in many types of networks, such as ISP backbones and enterprise access links. One example of an RE proposal is SmartRE [20], proposed by Anand et al., which focuses on network-wide RE. In packet-level RE, forwarding elements are equipped with additional storage that can be used to cache data from forwarded packets. Upstream routers may replace packet data with a fingerprint that tells a downstream router how to decode and reconstruct the packet based on cached data.
冗余消除（RE）用于识别和删除网络传输中的重复内容。这种技术被提出用于改善许多类型网络的网络性能，如ISP主干网和企业接入链路。重新提案的一个例子是SmartRE[20]，由Anand等人提出，其重点是网络范围的重新提案。在包级RE中，转发元件配备有可用于缓存来自转发包的数据的附加存储器。上游路由器可以用指纹替换分组数据，该指纹告诉下游路由器如何基于缓存数据解码和重构分组。
RE is an example of an experimental in-network storage system that would require a large amount of associated packet processing at routers if it was ever deployed.
RE是一个实验性的网络存储系统的例子，如果它被部署，将需要在路由器上进行大量相关的数据包处理。
RE is typically transparent to the user. Writing into storage is done by transferring data that has not already been cached. Storage is read when users transmit data identical to previously transmitted data.
RE通常对用户是透明的。写入存储器是通过传输尚未缓存的数据来完成的。当用户传输与先前传输的数据相同的数据时，读取存储器。
Not provided.
没有提供。
Not provided.
没有提供。
The access control method is public-restricted (to any client that is part of the RE network). Note that the content provider still retains control over which peers receive the requested data. The returned data is "compressed" as it is transferred within the network.
访问控制方法是公开限制的（对作为RE网络一部分的任何客户端）。请注意，内容提供商仍然保留对哪些对等方接收请求数据的控制。返回的数据在网络内传输时被“压缩”。
Not provided. The content provider still retains control over the rate at which packets are sent to a peer. The packet size within the network may be reduced.
没有提供。内容提供商仍然保留对向对等方发送数据包的速率的控制。可以减小网络内的分组大小。
No discovery mechanism is necessary. Routers can use RE without the users' knowledge.
不需要发现机制。路由器可以在用户不知情的情况下使用RE。
Object-based, with "objects" being data from packets transmitted within the network.
基于对象，其中“对象”是来自网络内传输的数据包的数据。
OceanStore [21] is a storage platform developed at the University of California, Berkeley, that provides globally distributed storage. OceanStore implements a model where multiple storage providers can pool resources together. Thus, a major focus is on resiliency, self-organization, and self-maintenance.
OntStale[21 ]是加利福尼亚大学伯克利开发的一个存储平台，它提供了全球分布式存储。OceanStore实现了一个模型，在该模型中，多个存储提供商可以将资源集中在一起。因此，主要关注弹性、自组织和自我维护。
The protocol is resilient to some storage nodes being compromised by utilizing Byzantine agreement and erasure codes to store data at primary replicas.
该协议通过利用拜占庭协议和擦除码在主副本上存储数据，对某些存储节点受到破坏具有弹性。
OceanStore is an example of an experimental in-network storage system that provides a high degree of network resilience to failure scenarios.
OceanStore是一个实验性网络存储系统的示例，它提供了对故障场景的高度网络恢复能力。
Users may read and write objects.
用户可以读取和写入对象。
Objects may be replaced by newer versions, and multiple versions of an object may be maintained.
对象可以被更新的版本替换，并且可以维护一个对象的多个版本。
Not provided.
没有提供。
Provided, but specifics for clients are unclear from the available references.
提供，但从现有参考资料中不清楚客户的具体情况。
Not provided.
没有提供。
Users require an entry point into the system in the form of one storage node that is part of OceanStore. If a hostname is provided, the address of a storage node may be determined via DNS.
用户需要以作为OceanStore一部分的一个存储节点的形式进入系统。如果提供了主机名，则可以通过DNS确定存储节点的地址。
Object-based.
基于对象的。
Caching of P2P traffic is a useful approach to reduce P2P network traffic, because objects in P2P systems are mostly immutable and the traffic is highly repetitive. In addition, making use of P2P caches does not require changes to P2P protocols and can be deployed transparently from clients.
P2P流量缓存是减少P2P网络流量的有效方法，因为P2P系统中的对象大多是不可变的，并且流量具有高度的重复性。此外，使用P2P缓存不需要更改P2P协议，并且可以从客户端透明地部署。
P2P caches operate similarly to Web caches (Section 4.14) in that they temporarily store frequently requested content. Requests for content already stored in the cache can be served from local storage instead of requiring the data to be transmitted over expensive network links.
P2P缓存的操作与Web缓存（第4.14节）类似，它们临时存储频繁请求的内容。对已经存储在缓存中的内容的请求可以从本地存储中提供，而不需要通过昂贵的网络链路传输数据。
Two types of P2P caches exist: transparent P2P caches and non-transparent P2P caches.
存在两种类型的P2P缓存：透明P2P缓存和非透明P2P缓存。
For a transparent cache, once a P2P cache is established, the network will transparently redirect P2P traffic to the cache, which either serves the file directly or passes the request on to a remote P2P user and simultaneously caches that data. Transparency is typically implemented using Deep Packet Inspection (DPI). DPI products identify and pass P2P packets to the P2P caching system so it can cache and accelerate the traffic.
对于透明缓存，一旦建立P2P缓存，网络将透明地将P2P流量重定向到缓存，该缓存直接为文件提供服务，或将请求传递给远程P2P用户，同时缓存该数据。透明性通常使用深度数据包检查（DPI）实现。DPI产品识别P2P数据包并将其传递给P2P缓存系统，以便它能够缓存和加速流量。
A non-transparent cache appears as a super peer; it explicitly peers with other P2P clients.
非透明缓存显示为超级对等；它显式地与其他P2P客户端进行对等。
To enable operation with existing P2P software, P2P caches directly support P2P application protocols. A large number of P2P protocols are used by P2P software and hence are supported by caches, leading to higher complexity. Additionally, these protocols evolve over time, and new protocols are introduced.
为了能够使用现有的P2P软件进行操作，P2P缓存直接支持P2P应用程序协议。P2P软件使用大量P2P协议，因此缓存支持这些协议，从而导致更高的复杂性。此外，这些协议随着时间的推移而发展，并引入了新的协议。
A P2P cache is an example of in-network storage for P2P systems. However, unlike DECADE, the existence and operation of the storage system are totally transparent to the end user.
P2P缓存是P2P系统网络存储的一个例子。但是，与DECED不同，存储系统的存在和操作对最终用户是完全透明的。
The data access interface allows P2P content to be cached (stored) and supplied (retrieved) locally such that network traffic is reduced, but it is transparent to P2P users, and P2P users implicitly use the data access interface (in the form of their native P2P application protocol) to store or retrieve content.
数据访问接口允许在本地缓存（存储）和提供（检索）P2P内容，从而减少网络流量，但它对P2P用户是透明的，并且P2P用户隐式使用数据访问接口（以其本机P2P应用程序协议的形式）来存储或检索内容。
Not provided.
没有提供。
Not provided.
没有提供。
The access control method is typically public-restricted (to any client that is part of the P2P channel or swarm).
访问控制方法通常是公开限制的（对于属于P2P通道或swarm的任何客户端）。
Not provided.
没有提供。
The use of DPI means that no discovery mechanism is provided to P2P users; it is transparent to P2P users. Since DPI is used to recognize P2P applications' private protocols, P2P cache implementations must be updated as new applications are added and existing protocols evolve.
DPI的使用意味着没有向P2P用户提供发现机制；它对P2P用户是透明的。由于DPI用于识别P2P应用程序的私有协议，因此P2P缓存实现必须随着新应用程序的添加和现有协议的发展而更新。
Object-based. Chunks (typically, the unit of transfer among P2P clients) of content are stored in the cache.
基于对象的。内容块（通常是P2P客户端之间的传输单元）存储在缓存中。
The data access interface allows P2P content to be cached (stored) and supplied (retrieved) locally such that network traffic is reduced. P2P users implicitly store and retrieve from the cache using the P2P application's native protocol.
数据访问接口允许在本地缓存（存储）和提供（检索）P2P内容，从而减少网络流量。P2P用户使用P2P应用程序的本机协议隐式地存储和检索缓存。
Not provided.
没有提供。
Not provided.
没有提供。
The access control method is typically public-restricted (to any client that is part of the P2P channel or swarm).
访问控制方法通常是公开限制的（对于属于P2P通道或swarm的任何客户端）。
Not provided.
没有提供。
A P2P cache node behaves as if it were a normal peer in order to join the P2P overlay network. Other P2P users can find such a cache node through an overlay routing mechanism and can interact with it as if it were a normal neighbor node.
为了加入P2P覆盖网络，P2P缓存节点的行为就好像它是一个普通的对等节点一样。其他P2P用户可以通过覆盖路由机制找到这样的缓存节点，并可以像普通邻居节点一样与之交互。
Object-based. Chunks (typically, the unit of transfer among P2P clients) of content are stored in the cache.
基于对象的。内容块（通常是P2P客户端之间的传输单元）存储在缓存中。
There are a growing number of popular online photo-sharing (storing) systems. For example, the Kodak Gallery system [22] serves over 60 million users and stores billions of images [23]. Other well-known examples of photo-sharing systems include Flickr [24] and ImageShack [25]. There are also a number of popular blogging
越来越多的流行在线照片共享（存储）系统。例如，柯达画廊系统[22]为6000多万用户提供服务，存储了数十亿张图像[23]。照片共享系统的其他著名示例包括Flickr[24]和ImageShack[25]。还有一些流行的博客
services, such as Tumblr [26], that specialize in sharing large numbers of photos as well as other multimedia content (e.g., video, text, audio, etc.) as part of their service. All of these in-network storage systems utilize both free and paid subscription models.
Tumblr[26]等服务，专门共享大量照片以及其他多媒体内容（如视频、文本、音频等），作为其服务的一部分。所有这些网络存储系统都使用免费和付费订阅模式。
Most photo-sharing systems are based on a traditional client-server architecture. However, a minority of systems also offer a P2P mode of operation. The client-server architecture is typically based on HTTP, with a browser client and a Web server.
大多数照片共享系统都基于传统的客户机-服务器体系结构。然而，少数系统也提供P2P操作模式。客户机-服务器体系结构通常基于HTTP，带有浏览器客户机和Web服务器。
Photo sharing is a very widely used (deployed) example of in-network storage where the end user has direct visibility and extensive control of the system. The typical end-user interface is through an HTTP-based Web browser.
照片共享是一种非常广泛使用（部署）的网络存储示例，最终用户可以直接查看并广泛控制系统。典型的最终用户界面是通过基于HTTP的Web浏览器。
Users can read (view) and write (store) photos.
用户可以读取（查看）和写入（存储）照片。
Users can delete previously stored photos.
用户可以删除以前存储的照片。
Users can tag photos and/or organize them using sophisticated Web photo album generators. Users can then search for objects (photos) matching desired criteria.
用户可以使用复杂的网络相册生成器对照片进行标记和/或组织。然后，用户可以搜索符合所需条件的对象（照片）。
The access control method for clients is typically either private or public-unrestricted. For example, writing (storing) to a photo blog is typically private to the owner of the account. However, all other clients can view (read) the contents of the blog (i.e., public-unrestricted). Some photo-sharing Websites provide private access to read photos to allow sharing with a limited set of friends.
客户端的访问控制方法通常是私有的或不受限制的公共的。例如，向照片博客的写入（存储）通常是帐户所有者的私有内容。但是，所有其他客户端都可以查看（阅读）博客的内容（即不受限制的公共内容）。一些照片共享网站提供私人阅读照片的权限，允许与有限的朋友共享。
Not provided.
没有提供。
Clients usually log on manually to a central Web page for the service and enter the appropriate information to access the desired information. The address to which the client connects is usually determined by DNS using the hostname from the provided URL.
客户端通常手动登录到服务的中心网页，并输入适当的信息以访问所需的信息。客户端连接到的地址通常由DNS使用提供的URL中的主机名来确定。
File system (file-based). Photos are usually stored as files. They can then be organized into meta-structures (e.g., albums, galleries, etc.) using sophisticated Web photo album generators.
文件系统（基于文件）。照片通常存储为文件。然后，可以使用复杂的Web相册生成器将它们组织成元结构（例如相册、图库等）。
Usenet is a distributed Internet-based discussion (message) system. The Usenet messages are arranged as a set of "newsgroups" that are classified hierarchically by subject. Usenet information is distributed and stored among a large conglomeration of servers that store and forward messages to one another in so-called news feeds. Individual users may read messages from, and post messages to, a local news server typically operated by an ISP. This local server communicates with other servers and exchanges articles with them. In this fashion, the message is copied from server to server and eventually reaches every server in the network [27].
Usenet是一个基于Internet的分布式讨论（消息）系统。Usenet消息被安排为一组“新闻组”，按主题分层分类。Usenet信息分布和存储在一个大型服务器集群中，这些服务器以所谓的新闻提要的形式相互存储和转发消息。个人用户可以从通常由ISP操作的本地新闻服务器读取消息并向其发布消息。此本地服务器与其他服务器通信并与它们交换文章。通过这种方式，消息从一台服务器复制到另一台服务器，并最终到达网络中的每台服务器[27]。
Traditional Usenet as described above operates as a P2P network between the servers, and in a client-server architecture between the user and their local news server. The user requires a Usenet client to be installed on their computer and a Usenet server account (through their ISP). However, with the rise of Web browsers, the Usenet architecture is evolving to be Web-based. The most popular example of this is Google Groups, where Google hosts all the newsgroups and client access is via a standard HTTP-based Web browser [28].
如上所述，传统的Usenet作为服务器之间的P2P网络运行，并在用户与其本地新闻服务器之间的客户机-服务器体系结构中运行。用户需要在其计算机上安装一个Usenet客户端和一个Usenet服务器帐户（通过其ISP）。然而，随着Web浏览器的兴起，Usenet体系结构正在演变为基于Web的。最流行的例子是Google Groups，Google托管所有新闻组，客户端通过标准的基于HTTP的Web浏览器访问[28]。
Usenet is a historically very important and widely used (deployed) example of in-network storage in the Internet. The use of this system is rapidly declining, but efforts have been made to preserve the stored content for historical purposes.
Usenet是一个历史上非常重要且广泛使用（部署）的Internet网络存储示例。该系统的使用率正在迅速下降，但已做出努力，将存储的内容保存起来，以用于历史目的。
Users can read and post (store) messages.
用户可以阅读和发布（存储）消息。
Users sometimes have limited ability to delete messages that they previously posted.
用户有时删除以前发布的邮件的能力有限。
Traditionally, users could manually search through the newsgroups, as they are classified hierarchically by subject. In the newer Web-based systems, there is also an automatic search capability based on key-word matches.
传统上，用户可以手动搜索新闻组，因为它们是按主题分层分类的。在较新的基于Web的系统中，还具有基于关键字匹配的自动搜索功能。
The access control method is either public-unrestricted or private (to client members of that newsgroup).
访问控制方法是public unrestricted或private（对于该新闻组的客户端成员）。
Not provided.
没有提供。
Clients usually log on manually to their Usenet accounts. DNS may be used to resolve hostnames to their corresponding addresses.
客户端通常手动登录到其Usenet帐户。DNS可用于将主机名解析为其相应的地址。
File system. Messages are usually stored as files that are then organized hierarchically by subject into newsgroups.
文件系统。消息通常存储为文件，然后按主题分层组织到新闻组中。
Web cache [29] has been widely deployed by many ISPs to reduce bandwidth consumption and Web access latency since the late 1990s. A Web cache can cache the Web documents (e.g., HTML pages, images) between server and client to reduce bandwidth usage, server load, and perceived lag. A Web cache server is typically shared by many clients, and stores copies of documents passing through it; subsequent requests may be satisfied from the cache if certain conditions are met.
自20世纪90年代末以来，许多ISP已广泛部署Web缓存[29]，以减少带宽消耗和Web访问延迟。Web缓存可以在服务器和客户端之间缓存Web文档（例如HTML页面、图像），以减少带宽使用、服务器负载和感知延迟。Web缓存服务器通常由多个客户端共享，并存储通过它的文档副本；如果满足某些条件，则可以从缓存中满足后续请求。
Another form of cache is a client-side cache, typically implemented in Web browsers. A client-side cache can keep a local copy of all pages recently displayed by a browser, and when the user returns to one of these Web pages, the local cached copy is reused.
另一种缓存形式是客户端缓存，通常在Web浏览器中实现。客户端缓存可以保留浏览器最近显示的所有页面的本地副本，当用户返回其中一个网页时，本地缓存副本将被重用。
A related protocol for P2P applications to use Web cache is HPTP (HTTP-based Peer to Peer) [30]. It proposes sharing chunks of P2P files/streams using HTTP with cache-control headers.
P2P应用程序使用Web缓存的相关协议是HPTP（基于HTTP的对等协议）[30]。它建议使用带有缓存控制头的HTTP共享P2P文件/流块。
Web cache is a very widely used (deployed) example of in-network storage for the key Internet application of Web browsing. The existence and operation of the storage system are transparent to the end user in most cases. The content caching time is controlled by time-to-live parameters associated with the original content. The principle of Web caching is to speed up Web page reading by using (the same) content previously requested by another user to service a new user.
Web缓存是一个非常广泛使用（部署）的网络存储示例，用于Web浏览的关键Internet应用程序。在大多数情况下，存储系统的存在和操作对最终用户是透明的。内容缓存时间由与原始内容关联的生存时间参数控制。Web缓存的原理是通过使用其他用户先前请求的（相同的）内容为新用户提供服务来加速Web页面读取。
Users explicitly read from a Web cache by making requests, but they cannot explicitly write data into it. Data is implicitly stored in the Web cache by requesting content that is not already cached and meets policy restrictions of the cache provider.
用户通过发出请求显式地从Web缓存中读取数据，但不能显式地将数据写入其中。通过请求尚未缓存且满足缓存提供程序策略限制的内容，数据隐式存储在Web缓存中。
Not provided.
没有提供。
Not provided.
没有提供。
The access control method for clients is public-unrestricted. It is important to note that if content is authenticated or encrypted (e.g., HTTPS, Secure Socket Layer (SSL)), it will not be cached. Also, if the content is flagged as private (vs. public) at the HTTP level by the origin server, it will not be cached.
客户端的访问控制方法是公共的，不受限制。需要注意的是，如果内容经过身份验证或加密（例如HTTPS、安全套接字层（SSL）），则不会对其进行缓存。此外，如果源服务器在HTTP级别将内容标记为private（相对于public），则不会缓存该内容。
Not provided.
没有提供。
Web caches can be transparently deployed between a Web server and Web clients, employing DPI for discovery. Alternatively, Web caches could be explicitly discovered by clients using techniques such as DNS or manual configuration.
Web缓存可以透明地部署在Web服务器和Web客户端之间，使用DPI进行发现。或者，客户端可以使用DNS或手动配置等技术显式发现Web缓存。
Object-based. Web content is keyed within the cache by HTTP Request fields, such as Method, URI, and Headers.
基于对象的。Web内容通过HTTP请求字段（如方法、URI和标头）在缓存中设置密钥。
The following observations about the surveyed in-network storage systems are made in the context of DECADE as defined by [1].
以下是在[1]定义的十年背景下对网络存储系统中调查的数据进行的观察。
The majority of the surveyed systems were designed for client-server architectures and do not support P2P. However, there are some important exceptions, especially for some of the newer technologies such as BranchCache and P2P cache, that do support a P2P mode of operation.
大多数被调查的系统都是为客户机-服务器体系结构设计的，不支持P2P。然而，也有一些重要的例外，特别是对于一些较新的技术，如BranchCache和P2P缓存，它们确实支持P2P操作模式。
The P2P cache systems are interesting, since they do not require changes to the P2P applications themselves. However, this is also a limitation in that they are required to support each application protocol.
P2P缓存系统很有趣，因为它们不需要更改P2P应用程序本身。然而，这也是一个限制，因为它们需要支持每个应用程序协议。
Many of the surveyed systems were designed for caching as opposed to long-term network storage. Thus, during DECADE protocol design, it should be carefully considered whether a caching mode should be supported in addition to a long-term network storage mode. There is typically a trade-off between providing a caching mode and long-term (and usually also reliable) storage with regards to some performance metrics. Note that [1] identifies issues with classical caching from a DECADE perspective, such as the fact that P2P caches typically do not allow users to explicitly control content stored in the cache.
许多被调查的系统都是为缓存而设计的，而不是长期的网络存储。因此，在十年协议设计期间，除了长期网络存储模式外，还应仔细考虑是否应支持缓存模式。就某些性能指标而言，通常需要在提供缓存模式和长期（通常也是可靠的）存储之间进行权衡。请注意，[1]从十年的角度确定了经典缓存的问题，例如P2P缓存通常不允许用户显式控制缓存中存储的内容。
Certain components of the surveyed systems are outside of the scope of DECADE. For example, a protocol used for searching across multiple DECADE servers is out of scope. However, applications may still be able to implement such functionality if DECADE exposes the appropriate primitives. This has the benefit of keeping the core in-network storage systems simple, while permitting diverse applications to design mechanisms that meet their own requirements.
所调查系统的某些组件不在十年范围内。例如，用于跨多个十年服务器搜索的协议超出范围。但是，如果TEDEX公开了适当的原语，应用程序可能仍然能够实现这样的功能。这样做的好处是使网络存储系统中的核心保持简单，同时允许各种应用程序设计满足其自身需求的机制。
Today, most in-network storage systems follow some variant of the authorization model of public-unrestricted, public-restricted, and private. For DECADE, we may need to evolve the authorization model to support a resource owner (e.g., end user) authorization, in addition to the network authorization.
如今，大多数网络存储系统都遵循公共非限制、公共限制和私有授权模式的一些变体。十年来，除了网络授权之外，我们可能还需要改进授权模型以支持资源所有者（例如，最终用户）授权。
This section surveys existing storage and other related protocols, as well as comments on the usage of these protocols to satisfy DECADE's use cases. The surveyed protocols are listed alphabetically.
本节将调查现有的存储和其他相关协议，以及对这些协议的使用情况的评论，以满足十年的使用情况。调查的协议按字母顺序列出。
HTTP [31] is a key protocol for the World Wide Web. It is a stateless client-server protocol that allows applications to be designed using the REST model. HTTP is often associated with downloading (reading) content from Web servers to Web browsers, but it also has support for uploading (writing) content to Web servers. It has been used as the underlying protocol for other protocols, such as Web Distributed Authoring and Versioning (WebDAV).
HTTP[31]是万维网的关键协议。它是一种无状态客户机-服务器协议，允许使用REST模型设计应用程序。HTTP通常与从Web服务器下载（读取）内容到Web浏览器相关联，但它也支持将内容上传（写入）到Web服务器。它已被用作其他协议的底层协议，如Web分布式创作和版本控制（WebDAV）。
HTTP is used in some of the most popular in-network storage systems surveyed previously, including CDNs, photo sharing, and Web cache. Usage of HTTP by a storage protocol implies that no extra software is required in the client (i.e., Web-based client), as all standard Web browsers are based on HTTP.
HTTP用于之前调查过的一些最流行的网络存储系统，包括CDN、照片共享和Web缓存。存储协议使用HTTP意味着客户端（即基于Web的客户端）不需要额外的软件，因为所有标准Web浏览器都基于HTTP。
Basic read and write operations are supported (using HTTP GET, PUT, and POST methods).
支持基本的读写操作（使用HTTP GET、PUT和POST方法）。
Not provided.
没有提供。
Not provided.
没有提供。
All methods of access control for clients are supported: public-unrestricted, public-restricted, and private.
支持客户端的所有访问控制方法：public unrestricted、public restricted和private。
The majority of Web pages are public-unrestricted in terms of reading but do not allow any uploading of content. In-network storage systems range from private or public-unrestricted for photo sharing (described in Section 4.12.5) to public-unrestricted for Web caching (described in Section 4.14.5).
大多数网页都是公开的，不受阅读限制，但不允许上传任何内容。网络存储系统的范围从照片共享的私有或公共不受限制（如第4.12.5节所述）到Web缓存的公共不受限制（如第4.14.5节所述）。
Not provided.
没有提供。
Manual configuration is typically used. Clients typically address HTTP servers by providing a hostname, which is resolved to an address using DNS.
通常使用手动配置。客户端通常通过提供主机名来寻址HTTP服务器，主机名使用DNS解析为地址。
HTTP is a protocol; it thus does not define a storage mode. However, a non-collection resource can typically be thought of as a "file". These files may be organized into collections, which typically map onto the HTTP path hierarchy, creating the illusion of a file system.
HTTP是一种协议；因此，它没有定义存储模式。但是，非集合资源通常可以被视为“文件”。这些文件可以组织成集合，这些集合通常映射到HTTP路径层次结构上，从而产生文件系统的错觉。
HTTP is based on a client-server architecture and thus is not directly applicable for the DECADE focus on P2P. Also, HTTP offers only a rudimentary toolset for storage operations compared to some of the other storage protocols.
HTTP基于客户机-服务器体系结构，因此不直接适用于P2P的十年重点。此外，与其他一些存储协议相比，HTTP仅为存储操作提供了一个基本的工具集。
Small Computer System Interface (SCSI) is a set of protocols enabling communication with storage devices such as disk drives and tapes; Internet SCSI (iSCSI) [32] is a protocol enabling SCSI commands to be sent over TCP. As in SCSI, iSCSI allows an Initiator to send commands to a Target. These commands operate on the device level as opposed to individual data objects stored on the device.
小型计算机系统接口（SCSI）是一组协议，支持与存储设备（如磁盘驱动器和磁带）进行通信；Internet SCSI（iSCSI）[32]是一种允许通过TCP发送SCSI命令的协议。与SCSI中一样，iSCSI允许启动器向目标发送命令。这些命令在设备级别上运行，而不是在设备上存储单个数据对象。
Read and write commands indicate which data is to be read or written by specifying the offset (using Logical Block Addressing) into the storage device. The size of data to be read or written is an additional parameter in the command.
读写命令通过指定存储设备中的偏移量（使用逻辑块寻址）来指示要读取或写入的数据。要读取或写入的数据的大小是命令中的一个附加参数。
Since commands operate at the device level, management operations are different than with traditional file systems. Management commands for SCSI/iSCSI include explicit device control commands, such as starting, stopping, and formatting the device.
由于命令在设备级别运行，因此管理操作与传统文件系统不同。SCSI/iSCSI的管理命令包括显式设备控制命令，如启动、停止和格式化设备。
SCSI/iSCSI does not provide the ability to search for particular data within a device. Note that such capabilities can be implemented outside of iSCSI.
SCSI/iSCSI不提供在设备内搜索特定数据的功能。请注意，这些功能可以在iSCSI之外实现。
With respect to access to devices, the access control method is private. iSCSI uses the Challenge Handshake Authentication Protocol (CHAP) [33] to authenticate Initiators and Targets when accessing storage devices. However, since SCSI/iSCSI operates at the device level, neither authentication nor authorization is provided for individual data objects. Note that such capabilities can be implemented outside of iSCSI.
关于对设备的访问，访问控制方法是私有的。iSCSI使用质询握手身份验证协议（CHAP）[33]在访问存储设备时对启动器和目标进行身份验证。但是，由于SCSI/iSCSI在设备级别运行，因此不对单个数据对象提供身份验证或授权。请注意，这些功能可以在iSCSI之外实现。
Not provided.
没有提供。
Manual configuration may be used. An alternative is the Internet Storage Name Service (iSNS) [34], which provides the ability to discover available storage resources.
可以使用手动配置。另一种选择是Internet存储名称服务（iSNS）[34]，它提供了发现可用存储资源的能力。
As a protocol, iSCSI does not explicitly have a storage mode. However, it provides block-based access to clients. SCSI/iSCSI provides an Initiator with block-level access to the storage device.
作为一种协议，iSCSI没有明确的存储模式。但是，它提供了对客户端的基于块的访问。SCSI/iSCSI为启动器提供对存储设备的块级访问。
The Network File System (NFS) is designed to allow users to access files over a network in a manner similar to how local storage is accessed. NFS is typically used in local area networks or in enterprise settings, though changes made in later versions of NFS (e.g., [35]) make it easier to operate over the Internet.
网络文件系统（NFS）旨在允许用户以与访问本地存储类似的方式通过网络访问文件。NFS通常在局域网或企业设置中使用，尽管在更高版本的NFS（例如[35]）中所做的更改使其更易于在Internet上操作。
Traditional file-system operations such as read, write, and update (overwrite) are provided. Locking is provided to support concurrent access by multiple clients.
提供了读取、写入和更新（覆盖）等传统文件系统操作。提供锁定以支持多个客户端的并发访问。
Traditional file-system operations such as move and delete are provided.
提供了移动和删除等传统文件系统操作。
The user has the ability to list contents of directories to find filenames matching desired criteria.
用户能够列出目录的内容，以查找符合所需条件的文件名。
All methods of access control for clients are supported: public-unrestricted, public-restricted, and private. For example, files and directories can be protected using read, write, and execute permissions for the files' owner and group, and for the public (others). Also, NFSv4.1 has a rich ACL model allowing a list of Access Control Entries (ACEs) to be configured for each file or directory. The ACEs can specify per-user read/write access to file data, file/directory attributes, creation/deletion of files in a directory, etc.
支持客户端的所有访问控制方法：public unrestricted、public restricted和private。例如，可以使用文件所有者和组以及公众（其他人）的读、写和执行权限来保护文件和目录。此外，NFSv4.1有一个丰富的ACL模型，允许为每个文件或目录配置访问控制项（ACE）列表。ACEs可以指定每个用户对文件数据的读/写访问、文件/目录属性、目录中文件的创建/删除等。
While disk space quotas can be configured, administrative policy typically limits the total amount of storage allocated to a particular user. User control of bandwidth and connections used by remote peers is not provided.
虽然可以配置磁盘空间配额，但管理策略通常会限制分配给特定用户的存储总量。不提供对远程对等方使用的带宽和连接的用户控制。
Manual configuration is typically used. Clients address NFS servers by providing a hostname and a directory that should be mounted. DNS may be used to look up an address for the provided hostname.
通常使用手动配置。客户端通过提供主机名和应装入的目录来寻址NFS服务器。DNS可用于查找所提供主机名的地址。
As a protocol, there is no defined internal storage mode. However, implementations typically use the underlying file-system storage. Note that extensions have been defined for alternate storage modes (e.g., block-based [36] and object-based [37]).
作为协议，没有定义内部存储模式。但是，实现通常使用底层文件系统存储。请注意，已为备用存储模式（例如，基于块的[36]和基于对象的[37]）定义了扩展。
The efficiency and scalability of the NFS access control method are concerns in the context of DECADE. In particular, Section 6.2.1 of [35] states that:
NFS访问控制方法的效率和可扩展性是十年来人们关注的问题。具体而言，[35]第6.2.1节规定：
Only ACEs that have a "who" that matches the requester are considered.
仅考虑具有与请求者匹配的“谁”的ACE。
Thus, in the context of DECADE, to specify per-peer access control policies for an object, a client would need to explicitly configure the ACL for the object for each individual peer. A concern with this approach is scalability when a client's peers may change frequently, and ACLs for many small objects need to be updated constantly during participation in a swarm.
因此，在TEDEC环境中，要为对象指定每个对等访问控制策略，客户端需要为每个单独的对等显式配置对象的ACL。这种方法的一个问题是可伸缩性，当客户端的对等方可能频繁更改时，许多小对象的ACL需要在参与swarm过程中不断更新。
Note that NFSv4.1's usage of RPCSEC_GSS provides support for multiple security mechanisms. Kerberos V5 is required, but others, such as X.509 certificates, are also supported by way of the Generic Security Service Application Program Interface (GSS-API). Note, however, that NFSv4.1's usage of such security mechanisms is limited to linking a requesting user to a particular account maintained by the NFS server.
注意，NFSv4.1对RPCSEC_GSS的使用提供了对多种安全机制的支持。Kerberos V5是必需的，但通用安全服务应用程序接口（GSS-API）也支持其他证书，如X.509证书。但是，请注意，NFSv4.1对此类安全机制的使用仅限于将请求用户链接到NFS服务器维护的特定帐户。
Open Authorization (OAuth) [38] is a protocol that enriches the traditional client-server authentication model for Web resources. In particular, OAuth distinguishes the "client" from the "resource owner", thus enabling a resource owner to authorize a particular client for access (e.g., for a particular lifetime) to private resources.
开放授权（OAuth）[38]是一种协议，它丰富了Web资源的传统客户机-服务器身份验证模型。尤其是，OAuth将“客户机”与“资源所有者”区分开来，从而使资源所有者能够授权特定客户机访问私有资源（例如，在特定的生命周期内）。
We include OAuth in this survey so that its authentication model can be evaluated in the context of DECADE. OAuth itself, however, is not a network storage protocol.
我们将OAuth包括在这项调查中，以便可以在十年的上下文中评估其身份验证模型。然而，OAuth本身并不是一个网络存储协议。
Not provided.
没有提供。
Not provided.
没有提供。
Not provided.
没有提供。
Not provided. While similar in spirit to the WebDAV ticketing extensions [39], OAuth instead uses the following process: (1) a client constructs a delegation request, (2) the client forwards the request to the resource owner for authorization, (3) the resource owner authorizes the request, and finally (4) a callback is made to the client indicating that its request has been authorized.
没有提供。虽然与WebDAV票务扩展[39]的精神类似，OAuth使用以下过程：（1）客户端构造委托请求，（2）客户端将请求转发给资源所有者进行授权，（3）资源所有者授权请求，最后（4）对客户端进行回调，指示其请求已被授权。
Once the process is complete, the client has a set of token credentials that grant it access to the protected resource. The token credentials may have an expiration time, and they can also be revoked by the resource owner at any time.
流程完成后，客户端将拥有一组令牌凭据，用于授予其对受保护资源的访问权限。令牌凭据可能有过期时间，资源所有者也可以随时吊销令牌凭据。
Not provided.
没有提供。
Not provided.
没有提供。
Not provided.
没有提供。
The ticketing mechanism requires server involvement, and the discussion relating to WebDAV's proposed ticketing mechanism (see Section 5.5.8) applies here as well.
票务机制需要服务器参与，与WebDAV提议的票务机制相关的讨论（见第5.5.8节）也适用于此。
WebDAV [40] is a protocol designed for Web content authoring. It is developed as an extension to HTTP (described in Section 5.1), meaning that it can be simpler to integrate into existing software. WebDAV supports traditional operations for reading/writing from storage, as well as other constructs, such as locking and collections, that are important when multiple users collaborate to author or edit a set of documents.
WebDAV[40]是一种为Web内容创作而设计的协议。它是作为HTTP的扩展开发的（在第5.1节中描述），这意味着它可以更简单地集成到现有软件中。WebDAV支持从存储中读/写的传统操作，以及其他构造（如锁定和集合），当多个用户协作编写或编辑一组文档时，这些构造非常重要。
Traditional read and write operations are supported (using HTTP GET and PUT methods, respectively). Locking is provided to support concurrent access by multiple clients.
支持传统的读写操作（分别使用HTTPGET和PUT方法）。提供锁定以支持多个客户端的并发访问。
WebDAV supports traditional file-system operations, such as move, delete, and copy. Objects are organized into collections, and these operations can also be performed on collections. WebDAV also allows objects to have user-defined properties.
WebDAV支持传统的文件系统操作，如移动、删除和复制。对象被组织到集合中，也可以对集合执行这些操作。WebDAV还允许对象具有用户定义的属性。
The user has the ability to list contents of collections to find objects matching desired criteria. A SEARCH extension [41] has also been specified allowing listing of objects matching client-defined criteria.
用户可以列出集合的内容，以查找符合所需条件的对象。还指定了搜索扩展[41]，允许列出与客户端定义的条件匹配的对象。
All methods of access control for clients are supported: public-unrestricted, public-restricted, and private.
支持客户端的所有访问控制方法：public unrestricted、public restricted和private。
For example, an ACL extension [42] is provided for WebDAV. ACLs allow both user-based and group-based access control policies (relating to reading, writing, properties, locking, etc.) to be defined for objects and collections.
例如，为WebDAV提供了ACL扩展[42]。ACL允许为对象和集合定义基于用户和基于组的访问控制策略（与读取、写入、属性、锁定等相关）。
A ticketing extension [39] has also been proposed, but has not progressed since 2001. This extension allows a client to request the WebDAV server to create a "ticket" (e.g., for reading an object) that can be distributed to other clients. Tickets may be given expiration times, or may only allow for a fixed number of uses. The proposed extension requires the server to generate tickets and maintain state for outstanding tickets.
还提议延长票务[39]，但自2001年以来一直没有进展。此扩展允许客户端请求WebDAV服务器创建可分发给其他客户端的“票据”（例如，用于读取对象）。门票可能会有到期时间，或者只允许固定数量的使用。建议的扩展要求服务器生成票证并维护未完成票证的状态。
An extension [43] allows disk space quotas to be configured for collections. The extension also allows WebDAV clients to query current disk space usage. User control of bandwidth and connections used by remote peers is not provided.
扩展[43]允许为集合配置磁盘空间配额。该扩展还允许WebDAV客户端查询当前磁盘空间使用情况。不提供对远程对等方使用的带宽和连接的用户控制。
Manual configuration is typically used. Clients address WebDAV servers by providing a hostname, which can be resolved to an address using DNS.
通常使用手动配置。客户端通过提供主机名来寻址WebDAV服务器，主机名可以使用DNS解析为地址。
Though no storage mode is explicitly defined, WebDAV can be thought of as providing file system (file-based) storage to a client. A non-collection resource can typically be thought of as a "file". Files may be organized into collections, which typically map onto the HTTP path hierarchy.
虽然没有明确定义存储模式，但WebDAV可以被认为是向客户端提供文件系统（基于文件的）存储。非集合资源通常可以被视为“文件”。文件可以组织成集合，这些集合通常映射到HTTP路径层次结构。
The efficiency and scalability of the WebDAV access control method are concerns in the context of DECADE, for reasons similar to those stated in Section 5.3.8 for NFS. The proposed WebDAV ticketing extension partially alleviates these concerns, but the particular technique may need further evaluation before being applied to DECADE. In particular, since DECADE clients may continuously upload/download a large number of small-size objects, and a single DECADE server may need to scale to many concurrent DECADE clients, requiring the server to maintain ticket state and generate tickets may not be the best design choice. Server-generated tickets can also increase latency for data transport operations, depending on the message flow used by DECADE.
WebDAV访问控制方法的效率和可扩展性是十年来关注的问题，其原因与NFS第5.3.8节中所述的原因类似。提议的WebDAV票务扩展部分缓解了这些担忧，但在应用于DECED之前，可能需要对特定技术进行进一步评估。特别是，由于十年客户端可能会连续上载/下载大量小尺寸对象，并且单个十年服务器可能需要扩展到多个并发十年客户端，因此要求服务器维护票证状态并生成票证可能不是最佳设计选择。服务器生成的票证也会增加数据传输操作的延迟，具体取决于用户使用的消息流。
The following observations about the surveyed storage and related protocols are made in the context of DECADE as defined by [1].
以下关于所调查的存储和相关协议的观察是在[1]定义的十年背景下进行的。
All of the surveyed protocols were primarily designed for client-server architectures and not for P2P. However, it is conceivable that some of the protocols could be adapted to work in a P2P architecture.
所有被调查的协议主要是为客户机-服务器体系结构设计的，而不是为P2P设计的。然而，可以想象，其中一些协议可以适用于P2P体系结构。
Several popular in-network storage systems today use HTTP as their key protocol, even though it is not classically considered as a storage protocol. HTTP is a stateless protocol that is used to design RESTful applications. HTTP is a well-supported and widely implemented protocol that can provide important insights for DECADE.
如今，一些流行的网络存储系统使用HTTP作为其关键协议，尽管它不是经典的存储协议。HTTP是一种无状态协议，用于设计RESTful应用程序。HTTP是一个支持良好且广泛实现的协议，可以为未来十年提供重要的见解。
The majority of the surveyed protocols do not support low-latency access for applications such as live streaming. This was one of the key general requirements for DECADE.
大多数被调查的协议都不支持实时流媒体等应用程序的低延迟访问。这是十年的主要一般要求之一。
The majority of the surveyed protocols do not support any form of resource control interface. Resource control is required for users to manage the resources on in-network storage systems, e.g., the bandwidth or connections, that can be used by other peers. Resource control is a key capability required for DECADE.
大多数被调查的协议不支持任何形式的资源控制接口。用户需要进行资源控制，以管理网络存储系统上可供其他对等方使用的资源，例如带宽或连接。资源控制是十年所需的关键能力。
Nearly all surveyed protocols did, however, support the following capabilities required for DECADE: ability of the user to read/write content, some form of access control, some form of error indication, and the ability to traverse firewalls and NATs.
然而，几乎所有被调查的协议都支持十年来所需的以下功能：用户读/写内容的能力、某种形式的访问控制、某种形式的错误指示以及穿越防火墙和NAT的能力。
Though there have been many successful in-network storage systems, they have been designed for use cases different from those defined in DECADE. For example, many of the surveyed in-network storage systems and protocols were designed for client-server architectures and not P2P. No surveyed system or protocol has the functionality and features to fully meet the set of requirements defined for DECADE. DECADE aims to provide a standard protocol for P2P applications and content providers to access and control in-network storage, resulting in increased network efficiency while retaining control over content shared with peers. Additionally, defining a standard protocol can reduce the complexity of in-network storage, since multiple P2P application protocols no longer need to be implemented by in-network storage systems.
尽管在网络存储系统中已经有许多成功的应用，但它们是为不同于十年前定义的用例而设计的。例如，许多被调查的网络存储系统和协议是为客户机-服务器体系结构而不是P2P设计的。没有一个经过调查的系统或协议具有完全满足十年定义的一系列要求的功能和特性。TEDEC旨在为P2P应用程序和内容提供商提供一个标准协议，以访问和控制网络存储，从而提高网络效率，同时保持对与对等方共享的内容的控制。此外，定义标准协议可以降低网络存储的复杂性，因为网络存储系统不再需要实现多个P2P应用程序协议。
This document is a survey of existing in-network storage systems, and does not introduce any security considerations beyond those of the surveyed systems.
本文档是对现有网络存储系统的概述，除介绍所调查系统的安全注意事项外，不介绍任何其他安全注意事项。
For more information on security considerations of DECADE, see [1].
有关十年安全注意事项的更多信息，请参见[1]。
The editors would like to thank the following people for contributing to the development of this document:
编辑们要感谢以下人员为本文件的编写做出了贡献：
- ZhiHui Lv
- 吕志辉
- Borje Ohlman
- 博尔杰·奥尔曼
- Pang Tao
- 庞涛
- Lucy Yong
- 杨露西
- Juan Carlos Zuniga
- 胡安·卡洛斯·祖尼加
The editors would like to thank the following people for providing valuable comments to various draft versions of this document: David Bryan, Tao Mao, Haibin Song, Ove Strandberg, Yu-Shun Wang, Richard Woundy, Yunfei Zhang, and Ning Zong.
编辑们要感谢以下人士为本文件的各种草案提供了宝贵的意见：大卫·布莱恩、陶茂、宋海滨、奥夫·斯特兰德伯格、王宇顺、理查德·沃迪、张云飞和宁宗。
[1] Song, H., Zong, N., Yang, Y., and R. Alimi, "DECoupled Application Data Enroute (DECADE) Problem Statement", Work in Progress, October 2011.
[1] Song，H.，Zong，N.，Yang，Y.，和R.Alimi，“分离应用程序数据途中（十年）问题陈述”，正在进行的工作，2011年10月。
[2] Storage Search, "Flash Memory vs. Hard Disk Drives -- Which Will Win?", <http://www.storagesearch.com/semico-art1.html>.
[2] 存储搜索，“闪存与硬盘驱动器——哪一个会赢？”<http://www.storagesearch.com/semico-art1.html>.
[3] Brisken, W., "Hard Drive Price Trends", US VLBI Technical Meeting, May 2008.
[3] W.布里斯肯，“硬盘价格趋势”，美国VLBI技术会议，2008年5月。
[4] Woundy, R., "TSV P2P Efforts -- From an ISP's Perspective", IETF 81, Quebec, Canada, July 2011, <http://www.ietf.org/proceedings/81/slides/tsvarea-3.pdf>.
[4] Woundy，R.，“TSV P2P努力——从ISP的角度”，IETF 81，魁北克，加拿大，2011年7月<http://www.ietf.org/proceedings/81/slides/tsvarea-3.pdf>.
[5] Gu, Y., Bryan, D., Yang, Y., and R. Alimi, "DECADE Requirements", Work in Progress, September 2011.
[5] Gu，Y.，Bryan，D.，Yang，Y.，和R.Alimi，“十年要求”，正在进行的工作，2011年9月。
[6] Amazon Web Services, "Amazon Simple Storage Service (Amazon S3)", <http://aws.amazon.com/s3/>.
[6] 亚马逊网络服务，“亚马逊简单存储服务（Amazon S3）”<http://aws.amazon.com/s3/>.
[7] Calder, B., Wang, T., Mainali, S., and J. Wu, "Windows Azure Blob -- Programming Blob Storage", May 2009, <http://www.microsoft.com/windowsazure/whitepapers/>.
[7] Calder，B.，Wang，T.，Mainali，S.，和J.Wu，“Windows Azure Blob——编程Blob存储”，2009年5月<http://www.microsoft.com/windowsazure/whitepapers/>.
[8] Google, "Google Storage for Developers", <http://code.google.com/apis/storage>.
[8] 谷歌，“谷歌开发者存储”<http://code.google.com/apis/storage>.
[9] Dropbox, "Dropbox Features", <http://www.dropbox.com/features>.
[9] Dropbox，“Dropbox功能”<http://www.dropbox.com/features>.
[10] Microsoft Corporation, "BranchCache", <http://technet.microsoft.com/en-us/network/dd425028.aspx>.
[10] 微软公司，“BranchCache”<http://technet.microsoft.com/en-us/network/dd425028.aspx>.
[11] Microsoft Corporation, "Web Services Dynamic Discovery (WS-Discovery)", April 2005, <http://specs.xmlsoap.org/ ws/2005/04/discovery/ws-discovery.pdf>.
[11] 微软公司，“Web服务动态发现（WS-Discovery）”，2005年4月<http://specs.xmlsoap.org/ ws/2005/04/discovery/ws-discovery.pdf>。
[12] Paul, S., Yates, R., Raychaudhuri, D., and J. Kurose, "The Cache-and-Forward Network Architecture for Efficient Mobile Content Delivery Services in the Future Internet", Innovations in NGN: Future Network and Services, 2008.
[12] Paul，S.，Yates，R.，Raychaudhuri，D.，和J.Kurose，“未来互联网中高效移动内容交付服务的缓存和转发网络架构”，NGN创新：未来网络和服务，2008年。
[13] SNIA, "Cloud Data Management Interface (CDMI)", <http://www.snia.org/cdmi>.
[13] SNIA，“云数据管理接口（CDMI）”<http://www.snia.org/cdmi>.
[14] Pathan, A.K. and Buyya, R., "A Taxonomy and Survey of Content Delivery Networks", Grid Computing and Distributed Systems Laboratory, University of Melbourne, Technical Report, February 2007.
[14] Pathan，A.K.和Buyya，R，“分类和调查内容交付网络”，网格计算和分布式系统实验室，墨尔本大学，技术报告，2007年2月。
[15] Cerf, V., Burleigh, S., Hooke, A., Torgerson, L., Durst, R., Scott, K., Fall, K., and H. Weiss, "Delay-Tolerant Networking Architecture", RFC 4838, April 2007.
[15] Cerf，V.，Burleigh，S.，Hooke，A.，Torgerson，L.，Durst，R.，Scott，K.，Fall，K.，和H.Weiss，“延迟容忍网络架构”，RFC 4838，2007年4月。
[16] Scott, K. and S. Burleigh, "Bundle Protocol Specification", RFC 5050, November 2007.
[16] Scott，K.和S.Burleigh，“捆绑协议规范”，RFC 50502007年11月。
[17] Named Data Networking, "Named Data Networking Home Page", <http://www.named-data.net/>.
[17] 命名数据网络，“命名数据网络主页”<http://www.named-data.net/>.
[18] Named Data Networking, "Named Data Networking (NDN) Project", <http://www.named-data.net/ndn-proj.pdf>.
[18] 命名数据网络，“命名数据网络（NDN）项目”<http://www.named-data.net/ndn-proj.pdf>.
[19] Network of Information, "NetInf Overview", <http://www.netinf.org/home/overview/>.
[19] 信息网络，“NetInf概述”<http://www.netinf.org/home/overview/>.
[20] Anand, A., Sekar, V., and A. Akella, "SmartRE: An Architecture for Coordinated Network-wide Redundancy Elimination", SIGCOMM 2009.
[20] Anand，A.，Sekar，V.，和A.Akella，“SmartRE：协调网络范围冗余消除的体系结构”，SIGCOM2009。
[21] Rhea, S., Eaton, P., Geels, D., Weatherspoon, H., Zhao, B., and J. Kubiatowicz, "Pond: the OceanStore Prototype", FAST 2003.
[21] Rhea，S.，Eaton，P.，Geels，D.，Weatherspoon，H.，Zhao，B.，和J.Kubiatowicz，“池塘：海洋商店原型”，FAST 2003。
[22] Kodak, "Kodak Gallery Home Page", <http://www.kodakgallery.com/gallery/welcome.jsp>.
[22] 柯达，“柯达画廊主页”<http://www.kodakgallery.com/gallery/welcome.jsp>.
[23] Wikipedia, "Kodak Gallery", <http://en.wikipedia.org/wiki/Kodak_Gallery>.
[23] 维基百科，“柯达画廊”<http://en.wikipedia.org/wiki/Kodak_Gallery>.
[24] Flickr, "Flickr Home Page", <http://www.flickr.com>.
[24] Flickr，“Flickr主页”<http://www.flickr.com>.
[25] ImageShack, "ImageShack Home Page", <http://imageshack.us>.
[25] ImageShack，“ImageShack主页”<http://imageshack.us>.
[26] Tumblr, "Tumblr Home Page", <http://www.tumblr.com>.
[26] Tumblr，“Tumblr主页”<http://www.tumblr.com>.
[27] Wikipedia, "Usenet", <http://en.wikipedia.org/wiki/Usenet>.
[27] 维基百科，“Usenet”<http://en.wikipedia.org/wiki/Usenet>.
[28] Google, "Google Groups", <http://groups.google.com>.
[28] 谷歌，“谷歌集团”<http://groups.google.com>.
[29] Huston, G., Telstra, "Web Caching", The Internet Protocol Journal Volume 2, No. 3.
[29] Huston，G.，Telstra，“网络缓存”，互联网协议杂志第2卷，第3期。
[30] Shen, G., Wang, Y., Xiong, Y., Zhao, B., and Z-L. Zhang, "HPTP: Relieving the Tension between ISPs and P2P", 6th International Workshop on Peer-To-Peer Systems (IPTPS2007).
[30] 沈，G.，王，Y.，熊，Y.，赵，B.，和Z-L.张，“HPTP：缓解ISP和P2P之间的紧张关系”，第六届对等系统国际研讨会（IPTPS2007）。
[31] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[31] 菲尔丁，R.，盖蒂斯，J.，莫卧儿，J.，弗莱斯蒂克，H.，马斯特，L.，利奇，P.，和T.伯纳斯李，“超文本传输协议——HTTP/1.1”，RFC2616，1999年6月。
[32] Satran, J., Meth, K., Sapuntzakis, C., Chadalapaka, M., and E. Zeidner, "Internet Small Computer Systems Interface (iSCSI)", RFC 3720, April 2004.
[32] Satran，J.，Meth，K.，Sapuntzakis，C.，Chadalapaka，M.，和E.Zeidner，“互联网小型计算机系统接口（iSCSI）”，RFC 3720，2004年4月。
[33] Simpson, W., "PPP Challenge Handshake Authentication Protocol (CHAP)", RFC 1994, August 1996.
[33] 辛普森，W.，“PPP挑战握手认证协议（CHAP）”，RFC 1994，1996年8月。
[34] Tseng, J., Gibbons, K., Travostino, F., Du Laney, C., and J. Souza, "Internet Storage Name Service (iSNS)", RFC 4171, September 2005.
[34] Tseng，J.，Gibbons，K.，Travostino，F.，Du Laney，C.，和J.Souza，“互联网存储名称服务（iSNS）”，RFC 41712005年9月。
[35] Shepler, S., Ed., Eisler, M., Ed., and D. Noveck, Ed., "Network File System (NFS) Version 4 Minor Version 1 Protocol", RFC 5661, January 2010.
[35] Shepler，S.，Ed.，Eisler，M.，Ed.，和D.Noveck，Ed.，“网络文件系统（NFS）版本4次要版本1协议”，RFC 56612010年1月。
[36] Black, D., Fridella, S., and J. Glasgow, "Parallel NFS (pNFS) Block/Volume Layout", RFC 5663, January 2010.
[36] Black，D.，Fridella，S.，和J.Glasgow，“并行NFS（pNFS）块/卷布局”，RFC 5663，2010年1月。
[37] Halevy, B., Welch, B., and J. Zelenka, "Object-Based Parallel NFS (pNFS) Operations", RFC 5664, January 2010.
[37] Halevy，B.，Welch，B.，和J.Zelenka，“基于对象的并行NFS（pNFS）操作”，RFC 5664，2010年1月。
[38] Hammer-Lahav, E., Ed., "The OAuth 1.0 Protocol", RFC 5849, April 2010.
[38] Hammer Lahav，E.，编辑，“OAuth 1.0协议”，RFC 5849，2010年4月。
[39] Ito, K., "Ticket-Based Access Control Extension to WebDAV", Work in Progress, October 2001.
[39] Ito，K.，“WebDAV基于票证的访问控制扩展”，正在进行的工作，2001年10月。
[40] Dusseault, L., Ed., "HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)", RFC 4918, June 2007.
[40] Dusseault，L.，Ed.，“Web分布式创作和版本控制（WebDAV）的HTTP扩展”，RFC4918，2007年6月。
[41] Reschke, J., Ed., Reddy, S., Davis, J., and A. Babich, "Web Distributed Authoring and Versioning (WebDAV) SEARCH", RFC 5323, November 2008.
[41] Reschke，J.，Ed.，Reddy，S.，Davis，J.，和A.Babich，“Web分布式创作和版本控制（WebDAV）搜索”，RFC 53232008年11月。
[42] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol", RFC 3744, May 2004.
[42] Clemm，G.，Reschke，J.，Sedlar，E.，和J.Whitehead，“Web分布式创作和版本控制（WebDAV）访问控制协议”，RFC 3744，2004年5月。
[43] Korver, B. and L. Dusseault, "Quota and Size Properties for Distributed Authoring and Versioning (DAV) Collections", RFC 4331, February 2006.
[43] Korver，B.和L.Dusseault，“分布式创作和版本控制（DAV）集合的配额和大小属性”，RFC 43312006年2月。
Authors' Addresses
作者地址
Richard Alimi (editor) Google
理查德·阿利米（编辑）谷歌
EMail: ralimi@google.com
EMail: ralimi@google.com
Akbar Rahman (editor) InterDigital Communications, LLC
Akbar Rahman（编辑）InterDigital Communications，LLC
EMail: Akbar.Rahman@InterDigital.com
EMail: Akbar.Rahman@InterDigital.com
Yang Richard Yang (editor) Yale University
Yang Richard Yang（编辑）耶鲁大学
EMail: yry@cs.yale.edu
EMail: yry@cs.yale.edu