Named Data Networking over a Software-Defined Network Using Fixed-Size Content Names

Jung-Hwan CHA; Youn-Hee HAN; Sung-Gi MIN

doi:10.1587/transcom.2015EBP3464

Named Data Networking over a Software-Defined Network Using Fixed-Size Content Names

Jung-Hwan CHA, Youn-Hee HAN, Sung-Gi MIN

Full Text Views

0

Share
Cite this

Summary :

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.

Publication: IEICE TRANSACTIONS on Communications Vol.E99-B No.7 pp.1455-1463

Publication Date: 2016/07/01

Publicized

Online ISSN: 1745-1345

DOI: 10.1587/transcom.2015EBP3464

Type of Manuscript: PAPER

Category: Network

Authors

Jung-Hwan CHA
  Korea University
Youn-Hee HAN
  Korea University of Technology and Education
Sung-Gi MIN
  Korea University

Keyword

Information-Centric Networking (ICN), Software-Defined Networking (SDN), name tag, ICN deployment problem

Cite this

Copy

Jung-Hwan CHA, Youn-Hee HAN, Sung-Gi MIN, "Named Data Networking over a Software-Defined Network Using Fixed-Size Content Names" in IEICE TRANSACTIONS on Communications, vol. E99-B, no. 7, pp. 1455-1463, July 2016, doi: 10.1587/transcom.2015EBP3464.
Abstract: 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.
URL: https://globals.ieice.org/en_transactions/communications/10.1587/transcom.2015EBP3464/_p

Copy

@ARTICLE{e99-b_7_1455,
author={Jung-Hwan CHA, Youn-Hee HAN, Sung-Gi MIN, },
journal={IEICE TRANSACTIONS on Communications},
title={Named Data Networking over a Software-Defined Network Using Fixed-Size Content Names},
year={2016},
volume={E99-B},
number={7},
pages={1455-1463},
abstract={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.},
keywords={},
doi={10.1587/transcom.2015EBP3464},
ISSN={1745-1345},
month={July},}

Copy

TY - JOUR
TI - Named Data Networking over a Software-Defined Network Using Fixed-Size Content Names
T2 - IEICE TRANSACTIONS on Communications
SP - 1455
EP - 1463
AU - Jung-Hwan CHA
AU - Youn-Hee HAN
AU - Sung-Gi MIN
PY - 2016
DO - 10.1587/transcom.2015EBP3464
JO - IEICE TRANSACTIONS on Communications
SN - 1745-1345
VL - E99-B
IS - 7
JA - IEICE TRANSACTIONS on Communications
Y1 - July 2016
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.
ER -