DECADE Architecture
draft-ietf-decade-arch-06
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (decade WG)
|
|
Last updated |
|
2012-05-31
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Informational
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
| Stream |
WG state
|
|
WG Document
Doc Shepherd Follow-up Underway
|
|
Document shepherd |
|
Haibin Song
|
|
Shepherd write-up |
|
Show
(last changed 2011-12-29)
|
| IESG |
IESG state |
|
AD is watching
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Martin Stiemerling
|
|
IESG note |
|
Haibin Song (haibin.song@huawei.com) is the document shepherd.
|
|
Send notices to |
|
decade-chairs@tools.ietf.org, draft-ietf-decade-arch@tools.ietf.org
|
DECADE R. Alimi
Internet-Draft Google
Intended status: Informational A. Rahman
Expires: December 2, 2012 InterDigital Communications, LLC
D. Kutscher
NEC
Y. Yang
Yale University
May 31, 2012
DECADE Architecture
draft-ietf-decade-arch-06
Abstract
Content Distribution Applications (e.g., P2P applications) are widely
used on the Internet and make up a large portion of the traffic in
many networks. One technique to improve the network efficiency of
these applications is to introduce storage capabilities within the
networks; this is the capability provided by a DECADE (DECoupled
Application Data Enroute) compatible system. This document presents
an architecture, discusses the underlying principles, and identifies
key functionalities required for introducing a DECADE-compatible in-
network storage system. In addition, some examples are given to
illustrate these concepts.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
Alimi, et al. Expires December 2, 2012 [Page 1]
Internet-Draft DECADE Architecture May 2012
This Internet-Draft will expire on December 2, 2012.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(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.
Alimi, et al. Expires December 2, 2012 [Page 2]
Internet-Draft DECADE Architecture May 2012
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. DECADE-compatible Client . . . . . . . . . . . . . . . . . 5
2.2. DECADE-compatible Server . . . . . . . . . . . . . . . . . 5
2.3. Content Provider . . . . . . . . . . . . . . . . . . . . . 6
2.4. Content Consumer . . . . . . . . . . . . . . . . . . . . . 6
2.5. Storage Provider . . . . . . . . . . . . . . . . . . . . . 6
2.6. Content Distribution Application . . . . . . . . . . . . . 6
2.7. Application End-Point . . . . . . . . . . . . . . . . . . 6
2.8. Data Object . . . . . . . . . . . . . . . . . . . . . . . 6
3. Protocol Flow . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2. An Example . . . . . . . . . . . . . . . . . . . . . . . . 8
4. Architectural Principles . . . . . . . . . . . . . . . . . . . 9
4.1. Decoupled Control/Metadata and Data Planes . . . . . . . . 9
4.2. Immutable Data Objects . . . . . . . . . . . . . . . . . . 10
4.3. Data Objects With Identifiers . . . . . . . . . . . . . . 10
4.4. Data Object Naming Scheme . . . . . . . . . . . . . . . . 11
4.5. Explicit Control . . . . . . . . . . . . . . . . . . . . . 12
4.6. Resource and Data Access Control . . . . . . . . . . . . . 13
5. System Components . . . . . . . . . . . . . . . . . . . . . . 14
5.1. Content Distribution Application . . . . . . . . . . . . . 14
Show full document text