Citation
Palmer Dabbelt, John D. Kubiatowicz. " A Case for the Universal DataPlane". Talk or presentation, 29, September, 2013; Presented at the First International Workshop on the Swarm at the Edge of the Cloud (SEC'13 @ ESWeek), Montreal. See also the Universal Dataplane Wiki.

Abstract
In this talk, we will make the argument that interposing a "Universal Data Plane" (UDPlane) abstraction between components in Swarm applications provides a clean mechanism for constructing such applications. The UDPlane is a distributed entity that persists beneath the physical components of swarm applications. It provides location-independent naming for sources and sinks of data (called "Endpoints" for the remainder of this document). Endpoints are not permanently associated with IP addresses or other fixed routing addresses, but rather exist in a large flat namespace with sufficient identifiers (such as SHA-256 hashes). The basic abstraction is that of sending secure, immutable data "transactions" from a source Endpoint to one or more sink Endpoints. Transactions are time-stamped and (to the extent possible) securely associated with the source of the transaction via a signature. Sinks are specified by, among other things, their level of data persistence from transient to deep archival (years or decades).

Electronic downloads

• http://www.src.org/library/publication/p067987/. (SRC Website)
• ACaseForTheUniversalDataplane_Dabbelt_SEC13_Montreal.pdf · application/pdf · 3718 kbytes
• kubitowicz_udplane_edge.pdf · application/pdf · 528 kbytes. (Abstract)

• HTML

  Palmer Dabbelt, John D. Kubiatowicz. <a
  href="http://www.terraswarm.org/pubs/116.html"><i>
  A Case for the Universal DataPlane</i></a>, Talk
  or presentation,  29, September, 2013; Presented at the
  <a
  href="http://www.terraswarm.org/conferences/13/swarm/index.htm">First
  International Workshop on the Swarm at the Edge of the Cloud
  (SEC'13 @ ESWeek)</a>, Montreal.  See also the <a
  href="http://www.terraswarm.org/platforms/wiki/Main/UniversalDataplane"
  >Universal Dataplane Wiki</a>.

• Plain text

  Palmer Dabbelt, John D. Kubiatowicz. " A Case for the
  Universal DataPlane". Talk or presentation,  29,
  September, 2013; Presented at the <a
  href="http://www.terraswarm.org/conferences/13/swarm/index.htm">First
  International Workshop on the Swarm at the Edge of the Cloud
  (SEC'13 @ ESWeek)</a>, Montreal.  See also the <a
  href="http://www.terraswarm.org/platforms/wiki/Main/UniversalDataplane"
  >Universal Dataplane Wiki</a>.

• BibTeX

  @presentation{DabbeltKubiatowicz13_CaseForUniversalDataPlane,
      author = {Palmer Dabbelt and John D. Kubiatowicz},
      title = { A Case for the Universal DataPlane},
      day = {29},
      month = {September},
      year = {2013},
      note = {Presented at the <a
                href="http://www.terraswarm.org/conferences/13/swarm/index.htm">First
                International Workshop on the Swarm at the Edge of
                the Cloud (SEC'13 @ ESWeek)</a>, Montreal.  See
                also the <a
                href="http://www.terraswarm.org/platforms/wiki/Main/UniversalDataplane"
                >Universal Dataplane Wiki</a>.},
      abstract = {In this talk, we will make the argument that
                interposing a "Universal Data Plane" (UDPlane)
                abstraction between components in Swarm
                applications provides a clean mechanism for
                constructing such applications. The UDPlane is a
                distributed entity that persists beneath the
                physical components of swarm applications. It
                provides location-independent naming for sources
                and sinks of data (called "Endpoints" for the
                remainder of this document). Endpoints are not
                permanently associated with IP addresses or other
                fixed routing addresses, but rather exist in a
                large flat namespace with sufficient identifiers
                (such as SHA-256 hashes). The basic abstraction is
                that of sending secure, immutable data
                "transactions" from a source Endpoint to one or
                more sink Endpoints. Transactions are time-stamped
                and (to the extent possible) securely associated
                with the source of the transaction via a
                signature. Sinks are specified by, among other
                things, their level of data persistence from
                transient to deep archival (years or decades).},
      URL = {http://terraswarm.org/pubs/116.html}
  }
  

Posted by Christopher Brooks on 29 Sep 2013.