Information-Centric Networking (ICN) and Software-Defined Networking (SDN) are both new evolving network architectures that are receiving a lot of attention from researchers. ICN is a Future Internet architecture which tries to transform the current Internet architecture from location- and host-centric to content-centric, where obtaining requested data is achieved by the contents’ names regardless of the location of the data. From another angle, SDN is considered a new Internet architecture that moves the control plane management from network devices to a centralized controller. The SDN controller enhances network robustness and improves its scalability, reliability, and flexibility. The integration of ICN and SDN results in massive benefits, where SDN enhances ICN networks’ manageability, controllability, and functionality, and ICN reshapes the SDN design to make it compatible with ICN features and to enhance ICN in terms of network caching, routing, mobility, and security.. In this review paper, a comprehensive survey of the issues and challenges of integrating ICN and SDN is presented. Firstly, ICN’s main characteristics are summarized, and a short comparison between different ICN architectures is completed. Then, the key details of SDN are highlighted. Moreover, the motivation and benefits of merging ICN with SDN are summarized and the state-of-the-art work on merging ICN and SDN is reviewed and classified from several aspects. Finally, several open research issues are highlighted.

Named data networking (NDN) is gaining momentum as a future Internet architecture. NDN is a type of information-centric networking (ICN) that attempts to change the current Internet architecture from host/location-centric to content-centric, where data retrieving is done by the names of the contents irrespective of the location of the data. A mechanism to advertise the namebased prefixes between different domains is necessary to accelerate the NDN deployment. In IP-based routing, border gateway protocol (BGP) is the de facto inter-domain routing protocol that plays a vital role in Internet communication by enabling different Internet domains to exchange routing information.In its current form, BGP can advertise and process IP-based prefixes, but it cannot advertise or process NDN name-based prefixes. Accordingly, BGP needs to be extended to support NDN technology. This paper proposes an NDN extension for BGP, referred to as N-BGP, that offers a solution to exchange name-based routes in the current BGP networks. This proposed extension modifies the traditional BGP speaker into a hybrid one. This hybrid speaker is qualified to understand, advertise, receive, process, and store both IP-based and name-based routes simultaneously and efficiently, without disturbing or breaking the current Internet operation; that is, it can coexist along with traditional speakers. We also validate and evaluate our proposed solution in a hybrid environment, and the results show that N-BGP has the capability to exchange and process both Name and IP-based routes efficiently.border gateway protocol (BGP), information-centric networking (ICN), inter-domain routing, named-data networking (NDN) | INTRODUCTIONBGP is, the inter-domain routing protocol, responsible for exchanging Internet routing information between autonomous systems (ASes), where each AS contains a set of routers under a single administration. 1 However, in its current form, it processes, advertises, and stores IP-based prefixes, but it is not capable of processing, advertising, and storing name-based routes for NDN networks. NDN is one of the prominent information-centric networking (ICN) architectures. Accordingly, to enable the routing of name-based traffic, there are two obvious approaches: develop and implement a new name-based inter-domain routing protocol or evolve the existing BGP protocol to support name-based

No abstract

No abstract

No abstract