Named data networking over a Software-Defined Network using fixed-size content names

Jung Hwan Cha, Youn Hee Han, Sung-Gi Min

Research output: Contribution to journalArticle

3 Citations (Scopus)

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.

Original languageEnglish
Pages (from-to)1455-1463
Number of pages9
JournalIEICE Transactions on Communications
VolumeE99B
Issue number7
DOIs
Publication statusPublished - 2016 Jul 1

Fingerprint

Switches
Software defined networking

Keywords

  • ICN deployment problem
  • Information-Centric Networking (ICN)
  • Name tag
  • Software-Defined Networking (SDN)

ASJC Scopus subject areas

  • Electrical and Electronic Engineering
  • Computer Networks and Communications
  • Software

Cite this

Named data networking over a Software-Defined Network using fixed-size content names. / Cha, Jung Hwan; Han, Youn Hee; Min, Sung-Gi.

In: IEICE Transactions on Communications, Vol. E99B, No. 7, 01.07.2016, p. 1455-1463.

Research output: Contribution to journalArticle

@article{bb128742de37435191a657b9607f3b6a,
title = "Named data networking over a Software-Defined Network using fixed-size content names",
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 = "ICN deployment problem, Information-Centric Networking (ICN), Name tag, Software-Defined Networking (SDN)",
author = "Cha, {Jung Hwan} and Han, {Youn Hee} and Sung-Gi Min",
year = "2016",
month = "7",
day = "1",
doi = "10.1587/transcom.2015EBP3464",
language = "English",
volume = "E99B",
pages = "1455--1463",
journal = "IEICE Transactions on Communications",
issn = "0916-8516",
publisher = "Maruzen Co., Ltd/Maruzen Kabushikikaisha",
number = "7",

}

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

PY - 2016/7/1

Y1 - 2016/7/1

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

VL - E99B

SP - 1455

EP - 1463

JO - IEICE Transactions on Communications

JF - IEICE Transactions on Communications

SN - 0916-8516

IS - 7

ER -