Abstract

The huge amount of content names available in Named-Data Networking (NDN) challenges both the required routing table size and the techniques for locating and forwarding information. Content copies and content mobility exacerbate the scalability challenge to reach content in the new locations. We present and analyze the performance of a proposed Controller-based Routing Scheme, named CRoS-NDN, which preserves NDN features using the same interest and data packets. CRoS-NDN supports content mobility and provides fast content recovery from copies that do not belong to the consumer-producer path because it splits identity from location without incurring FIB size explosion or supposing prefix aggregation. It provides features similar to Content Distribution Networks (CDN) in NDN, and improves the routing efficiency. We compare our proposal with similar routing protocols and derive analytical expressions for lower-bound efficiency and upper-bound latency. We also conduct extensive simulations to evaluate results in data delivery efficiency and delay. The results show the robust behavior of the proposed scheme achieving the best efficiency and delay performance for a wide range of scenarios. Furthermore, CRoS-NDN results in low use of processing time and memory for a growing number of prefixes.

Highlights

  • Named-Data Networking (NDN) applications refer directly to content names, instead of host network identifiers for communication [1]

  • We analyze the performance and compare it with the main routing/forwarding schemes used for NDN in the literature: INFORM [51], Open Shortest Path First (OSPF) Based Routing Protocol for Named Data Networking (OSPFN) [52], Named-Data Link State Routing (NLSR) [53], and Distance-based Content Routing (DCR) protocol [54]

  • We observe that the higher is the number of announced prefixes (AP), the better is CRoS-NDN and NLSRLike efficiency, while OSPFLike behavior is the contrary

Read more

Summary

Introduction

Named-Data Networking (NDN) applications refer directly to content names, instead of host network identifiers for communication [1]. In this new paradigm, both host mobility/multihoming and content mobility/multihoming do not concern applications because the NDN-network layer focuses on unique network-visible names that identify content. Both host mobility/multihoming and content mobility/multihoming do not concern applications because the NDN-network layer focuses on unique network-visible names that identify content It forwards two types of packets: interest and data packets. On the way from the consumer to the content copy, keeps a registry of the interest packet, such that the data packet containing the desired content finds the return path back to the consumer.

Objectives
Discussion
Conclusion
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call