DECADE Architecture and Protocol
draft-alimi-protocol-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-02-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
APPSAWG                                                         R. Alimi
Internet-Draft                                                    Google
Intended status: Informational                                 A. Rahman
Expires: August 18, 2013                InterDigital Communications, LLC
                                                             D. Kutscher
                                                                     NEC
                                                                 Y. Yang
                                                         Yale University
                                                                 H. Song
                                                          K. Pentikousis
                                                                  Huawei
                                                       February 14, 2013

                    DECADE Architecture and Protocol
                        draft-alimi-protocol-00

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 in the architecture for introducing a DECADE 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

Alimi, et al.            Expires August 18, 2013                [Page 1]
Internet-Draft             DECADE Architecture             February 2013

   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 18, 2013.

Copyright Notice

   Copyright (c) 2013 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 August 18, 2013                [Page 2]
Internet-Draft             DECADE Architecture             February 2013

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Protocol Flow  . . . . . . . . . . . . . . . . . . . . . . . .  4
     3.1.  Overview . . . . . . . . . . . . . . . . . . . . . . . . .  4
     3.2.  An Example . . . . . . . . . . . . . . . . . . . . . . . .  5
   4.  Architectural Principles . . . . . . . . . . . . . . . . . . .  6
     4.1.  Decoupled Control/Metadata and Data Planes . . . . . . . .  6
     4.2.  Immutable Data Objects . . . . . . . . . . . . . . . . . .  7
     4.3.  Data Objects With Identifiers  . . . . . . . . . . . . . .  8
     4.4.  Explicit Control . . . . . . . . . . . . . . . . . . . . .  9
     4.5.  Resource and Data Access Control through Delegation  . . . 10
   5.  System Components  . . . . . . . . . . . . . . . . . . . . . . 11
     5.1.  Content Distribution Application . . . . . . . . . . . . . 11
     5.2.  DECADE Server  . . . . . . . . . . . . . . . . . . . . . . 13
     5.3.  Data Sequencing and Naming . . . . . . . . . . . . . . . . 15
     5.4.  Token-based Authorization and Resource Control . . . . . . 16
     5.5.  Discovery  . . . . . . . . . . . . . . . . . . . . . . . . 17
   6.  DECADE Protocols . . . . . . . . . . . . . . . . . . . . . . . 18
     6.1.  DECADE Naming  . . . . . . . . . . . . . . . . . . . . . . 18
Show full document text