A data-oriented (and beyond) network architecture

Abstract

The Internet has evolved greatly from its original incarnation. For instance, the vast majority of current Internet usage is data retrieval and service access, whereas the architecture was designed around host-to-host applications such as telnet and ftp. Moreover, the original Internet was a purely transparent carrier of packets, but now the various network stakeholders use middleboxes to improve security and accelerate applications. To adapt to these changes, we propose the Data-Oriented Network Architecture (DONA), which involves a clean-slate redesign of Internet naming and name resolution.

Providing Information Resilience Through Modularity-Based Caching in Perturbed Information-Centric Networks

“…A user's content request can then be served by any of the network element having a copy of the requested content. Such information retrieval mechanism follows a publish-subscribe approach though different implementations are found in different ICN architectures (e.g., Register and Find primitives are used in [15], Register and Interest in [13] and Publish and Consume in [16], [17]). Here, we take such on-path caching mechanism as the starting point of our proposal.…”

Network Layer Solutions for a Content-Centric Internet

“…Nick-names used by proprietary applications (e.g., Skype) are memorable and decentralized. So-called self-certifying names [4,14] are secure and decentralized.…”

“…For instance, in [4] the authors propose that a publisher P of a content may autonomously label the content as L and the resulting self-certified name is the Digest(Pubkey P ):L, where Digest(Pubkey P ) is a digest of the public key used by the publisher to sign the data. If that the publisher ensures the uniqueness of label L among her published contents, a self-certifying naming schemes is secure and decentralized.…”

“…Therefore, there is a mismatch between the content-centric usage model of the Internet and the address-centric service model offered by the IP layer. Such a mismatch gives rise to several problems that would not exist if the network layer were a content-centric one [2,4,5]. Some of these issues are:…”

“…In terms of deployment, the proposed solutions can be classified as evolutionary [2,4,7] or clean-slate [5,8,11,9]. The evolutionary architectures implement content-centric functionalities by enhancing the actual Internet.…”