Consumer / Producer Communication with Application Level Framing in Named Data Networking

Abstract

Over time the Internet has evolved from a network that interconnects hosts to a network that interconnects information objects broadly defined; these objects range from movie files, Facebook content, twitter messages, to sensor data and authenticated device actuation commands.As a newly proposed architecture to meet this new usage, Named Data Networking (NDN) replaces the host-based addressing scheme by names of information objects in moving packets through the network. In an NDN network consumers send Interest packets carrying application-level names to request information objects, and the network returns the requested Data packets reversing the path of the Interests. As a new way of doing networking, NDN introduces new design patterns for applications. To make the content available in the network, one needs to consider multiple design choices, which range from name structure and security model to more basic issues such as data segmentation. To fetch content, This dissertation addresses the above challenges with the design of a new Consumer / Producer API and its associated protocol suite that can play socketequivalent roles in an NDN network. We demonstrate how the API can be used to invoke the most fundamental communication patterns in an NDN network and also show how stand-alone and web-based applications can be designed on top of the API. While the architecture of NDN is still a subject to the changes, we believe that the Consumer / Producer API framework can be successfully extended to accommodate new protocols, communication patterns and applications.iii The dissertation of Ilya Moiseenko is approved.

Named Data Networking: A Survey on Routing Strategies

“…NDN is a state-of-the-art new emerging technology that can effectively solve many problems caused by conventional Internet architecture [41]. NDN is an ICN application that keeps its focus on information, rather than location [42] NDN naturally solves many IP architecture problems, such as routing loop and consumer mobility [43]. The major advantage of NDN is in-network caching from the network Content Store (CS).…”

Decoupling information and connectivity via information-centric transport

“…An IP-based application can also implement its own transport mechanisms by following the Application-Level-Framing (ALF) concept [16]. Related work has shown that ICN can provide similar transport mechanisms to applications with CCT requirements [17][18][19]. ICT does not preclude CCT transport mechanisms for ICN applications.…”

“…The work in [17] proposes a consumer-producer API, built to simplify and reduce the implementation efforts of NDN application developers. Although this work addresses some of the challenges discussed here, we propose a general-purpose information-centric abstraction and a mechanism that provide in-network transport.…”

End-to-end encrypted scalable abstract data types over ICN

“…Several attempts have been made for wrapping the Interest/Data messaging into more conveniently usable primitives, the motivation being that for example "reliable and secure application-level message exchange" or "file replication" are the relevant services in which application developers are interested in. Support for Producer/Consumer communication has been the focus of several authors (Moiseenko [13], PARC's CCNx 1.0 lib and now CICN sockets [16]). ChronoSync [39] can be seen as way to automatically replicate hierarchically organized data over ICN.…”