datatracker.ietf.org
Sign in
Version 5.13.0, 2015-03-25
Report a bug

DECoupled Application Data Enroute (DECADE)
RFC 7069

Document type: RFC - Informational (November 2013; No errata)
Was draft-alimi-decade (individual)
Document stream: ISE
Last updated: 2013-11-27
Other versions: plain text, pdf, html
IETF Conflict Review: conflict-review-alimi-decade

ISE State: Published RFC
Document shepherd: No shepherd assigned

IESG State: RFC 7069 (Informational)
Responsible AD: (None)
Send notices to: No addresses provided

Independent Submission                                          R. Alimi
Request for Comments: 7069                                        Google
Category: Informational                                        A. Rahman
ISSN: 2070-1721                         InterDigital Communications, LLC
                                                             D. Kutscher
                                                                     NEC
                                                                 Y. Yang
                                                         Yale University
                                                                 H. Song
                                                     Huawei Technologies
                                                          K. Pentikousis
                                                                    EICT
                                                           November 2013

              DECoupled Application Data Enroute (DECADE)

Abstract

   Content distribution applications, such as those employing peer-to-
   peer (P2P) technologies, are widely used on the Internet and make up
   a large portion of the traffic in many networks.  Often, however,
   content distribution applications use network resources
   inefficiently.  One way to improve efficiency is to introduce storage
   capabilities within the network and enable cooperation between end-
   host and in-network content distribution mechanisms.  This is the
   capability provided by a DECoupled Application Data Enroute (DECADE)
   system, which is introduced in this document.  DECADE enables
   applications to take advantage of in-network storage when
   distributing data objects as opposed to using solely end-to-end
   resources.  This document presents the underlying principles and key
   functionalities of such a system and illustrates operation through a
   set of examples.

Alimi, et al.                 Informational                     [Page 1]
RFC 7069                         DECADE                    November 2013

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This is a contribution to the RFC Series, independently of any other
   RFC stream.  The RFC Editor has chosen to publish this document at
   its discretion and makes no statement about its value for
   implementation or deployment.  Documents approved for publication by
   the RFC Editor are not a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   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/rfc7069.

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.

Alimi, et al.                 Informational                     [Page 2]
RFC 7069                         DECADE                    November 2013

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Architectural Principles  . . . . . . . . . . . . . . . . . .   8
     4.1.  Data- and Control-Plane Decoupling  . . . . . . . . . . .   8
     4.2.  Immutable Data Objects  . . . . . . . . . . . . . . . . .   9
     4.3.  Data Object Identifiers . . . . . . . . . . . . . . . . .  10
     4.4.  Explicit Control  . . . . . . . . . . . . . . . . . . . .  11
     4.5.  Resource and Data Access Control through Delegation . . .  11
   5.  System Components . . . . . . . . . . . . . . . . . . . . . .  12
     5.1.  Application Endpoint  . . . . . . . . . . . . . . . . . .  13
     5.2.  DECADE Client . . . . . . . . . . . . . . . . . . . . . .  14
     5.3.  DECADE Server . . . . . . . . . . . . . . . . . . . . . .  14
     5.4.  Data Sequencing and Naming  . . . . . . . . . . . . . . .  15
     5.5.  Token-Based Authorization and Resource Control  . . . . .  17
     5.6.  Discovery . . . . . . . . . . . . . . . . . . . . . . . .  18
   6.  DECADE Protocol Considerations  . . . . . . . . . . . . . . .  19
     6.1.  Naming  . . . . . . . . . . . . . . . . . . . . . . . . .  19
     6.2.  Resource Protocol . . . . . . . . . . . . . . . . . . . .  19

[include full document text]