Named Function Networking (NFN) extends classic Information Centric Networking (ICN), such that in addition to resolving data access by name, it also supports the concept of function definition and application to data (or other functions) in the same resolution-by-name process. This empowers the network to select internally (optimal) places for fulfilling a potentially complex user expression. Forwarding optimization and routing policies become thereafter a basis of dynamic decisions for (re)-distributing computations, and retrieving results.In this paper we describe the intrinsic operations and mechanisms of an instantiation of NFN based on untyped Lambda expressions and Scala procedures. Then, we demonstrate through a series of proof-of-concept experiments how they extend the capabilities of an information centric network (CCN), for orchestrating and distributing data computations, and re-using cached results from previous computations. In the end we report and discuss the main observations stemming from these experiments and highlight important insights that can impact the architecting of ICN protocols that focus on named-data.

No abstract

No abstract

In content-based security, encrypted content as well as wrapped access keys are made freely available by an Information Centric Network: Only those clients which are able to unwrap the encryption key can access the protected content. In this paper we extend this model to computation chains where derived data (e.g. produced by a Named Function Network) also has to comply to the content-based security approach. A central problem to solve is the synchronized ondemand publishing of encrypted results and wrapped keys as well as defining the set of consumers which are authorized to access the derived data. In this paper we introduce "contentattendant policies" and report on a running prototype that demonstrates how to enforce data owner-defined access control policies despite fully decentralized and arbitrarily long computation chains. CCS Concepts •Networks → Network protocol design; •Security and privacy → Security protocols;

No abstract