TY - JOUR
T1 - Named data networking over a Software-Defined Network using fixed-size content names
AU - Cha, Jung Hwan
AU - Han, Youn Hee
AU - Min, Sung Gi
N1 - Publisher Copyright:
© Copyright 2016 The Institute of Electronics, Information and Communication Engineers.
Copyright:
Copyright 2017 Elsevier B.V., All rights reserved.
PY - 2016/7
Y1 - 2016/7
N2 - Named Data Networking (NDN) has emerged as an alternative to traditional IP-based networking for the achievement of Information-Centric Networking (ICN). Currently, most NDN is deployed over IP networks, but such an overlay deployment increases the transport network overhead due to the use of dual network control planes (NDN routing and IP routing). Software-Defined Networking (SDN) can be used to mitigate the network overhead by forwarding NDN packets without the use of IP routing. However, to deploy NDN over SDN, a variable NDN content name needs to be mapped to a fixed-size match field in an OpenFlow switch flow table. For efficient support of such a mapping task, we propose a new architecture that uses dual name for content: content name and Name Tag. The Name Tag is derived from the corresponding content name and is a legitimate IPv6 address. By using the proposed Name Tag, the SDN with an NDN control application can transport an IPv6 packet that encapsulates an NDN packet for an NDN name-based routing. We emulate the proposed architecture using Mininet and verify that it is feasible.
AB - Named Data Networking (NDN) has emerged as an alternative to traditional IP-based networking for the achievement of Information-Centric Networking (ICN). Currently, most NDN is deployed over IP networks, but such an overlay deployment increases the transport network overhead due to the use of dual network control planes (NDN routing and IP routing). Software-Defined Networking (SDN) can be used to mitigate the network overhead by forwarding NDN packets without the use of IP routing. However, to deploy NDN over SDN, a variable NDN content name needs to be mapped to a fixed-size match field in an OpenFlow switch flow table. For efficient support of such a mapping task, we propose a new architecture that uses dual name for content: content name and Name Tag. The Name Tag is derived from the corresponding content name and is a legitimate IPv6 address. By using the proposed Name Tag, the SDN with an NDN control application can transport an IPv6 packet that encapsulates an NDN packet for an NDN name-based routing. We emulate the proposed architecture using Mininet and verify that it is feasible.
KW - ICN deployment problem
KW - Information-Centric Networking (ICN)
KW - Name tag
KW - Software-Defined Networking (SDN)
UR - http://www.scopus.com/inward/record.url?scp=84976640183&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84976640183&partnerID=8YFLogxK
U2 - 10.1587/transcom.2015EBP3464
DO - 10.1587/transcom.2015EBP3464
M3 - Article
AN - SCOPUS:84976640183
SN - 0916-8516
VL - E99B
SP - 1455
EP - 1463
JO - IEICE Transactions on Communications
JF - IEICE Transactions on Communications
IS - 7
ER -