2013 21st IEEE International Conference on Network Protocols (ICNP) 2013
DOI: 10.1109/icnp.2013.6733634
|View full text |Cite
|
Sign up to set email alerts
|

Enabling ICN in IP networks using SDN

Abstract: In this work, we outline how to enable InformationCentric Networking (ICN) on existing IP networks, such as ISP or data center networks, using Software-Defined Networking (SDN) functions and control. We describe a mechanism that requires neither new or extended network/L3 and transport/L4 protocols nor changes of ICN host network stacks, and supports aggregation of routes inside the SDN controlled network. The proposed solution is agnostic of the specific ICN protocol in use, and does not require all network e… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
24
0

Year Published

2016
2016
2020
2020

Publication Types

Select...
6
2
1

Relationship

0
9

Authors

Journals

citations
Cited by 26 publications
(24 citation statements)
references
References 1 publication
0
24
0
Order By: Relevance
“…Vahlenkamp et al [20] propose to use Software-Defined Networking (SDN) to enable ICN on an existing IP network. An SDN controller installs the appropriate forwarding state for each ICN demands.…”
Section: Coexistence With Ipmentioning
confidence: 99%
“…Vahlenkamp et al [20] propose to use Software-Defined Networking (SDN) to enable ICN on an existing IP network. An SDN controller installs the appropriate forwarding state for each ICN demands.…”
Section: Coexistence With Ipmentioning
confidence: 99%
“…Focusing on a single concept of network softwarisation, more studies have coupled ICN with Software Defined Networking (SDN) for various purposes. SRSC [1] is a controllerbased forwarding scheme for NDN to perform the route management as an alternative to NLSR, [31], [30], [23] and [18] use SDN, and more precisely OpenFlow to transport ICN over IP while also optimizing the caching on the path, but [30] and [18] must twist the use of IP address and port fields to contain hashes of content names in order to allow OpenFlow switches to process Interests, while [23] rather chose to use IP options and payload, and [31] chose to extend OpenFlow for a cleaner approach. While fundamentally different in the internal operation, our architecture shares with the ones cited above the centralized nature of route management.…”
Section: State Of the Art 21 Nfv And Sdn Initiatives For Icnsmentioning
confidence: 99%
“…In the works of Salsano et al and Vahlenkamp et al, switches are not ICN‐aware, making the SDN controller responsible for managing ICN request and response packets. This solution is similar to the stateless approach we compare with and incurs large delays due to the required interaction between the switch and the controller, different from our stateful approach that completely avoids such interaction.…”
Section: Related Workmentioning
confidence: 99%