ICN based Architecture for IoT
draft-zhang-icnrg-icniot-architecture-01

Document Type Expired Internet-Draft (individual)
Last updated 2018-04-19 (latest revision 2017-07-16)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-zhang-icnrg-icniot-architecture-01.txt

Abstract

The Internet of Things (IoT) technology promises to connect billions of objects to Internet. Today, the IoT landscape is very fragmented from both the technology and service perspectives. As a consequence, it is difficult to integrate and cross-correlate data coming from the heterogeneous contexts and build value-added services on top. This reason has motivated the current trend to develop a unified de- fragmented IoT architecture so that objects can be made accessible to applications across organizations and domains. Several proposals have been made to build a unified IoT architecture as an overlay on top of today's Internet. Such overlay solutions, however, inherit the existing limitations of the IP protocol: mobility, security, scalability, and communication reliability. To address this problem, A unified IoT architecture based on the Information Centric Networking (ICN) architecture, which we call ICN-IoT [1] has been proposed. ICN-IoT leverages the salient features of ICN, and thus provides seamless device-to-device (D2D) communication, mobility support, scalability, and efficient content and service delivery. Furthermore, in order to guarantee the real diffusion of ICN-IoT architecture it is fundamental to deal with self-configuring features such as device onboarinding and discovery, service discovery, scalability, security and privacy requirements, content dissemmination since the IoT system will comprise of diverse applications with heterogenous requirements including connectivity, resource constraints and mobility. Towards this, the draft elaborates on a set of middleware functions to enable large operation of an ICN-IoT deployment. This draft begins by motivating the need for an unified ICN-IoT architecture to connect heterogeneous IoT systems. We then propose an ICN-IoT system architecture and middleware components which includes device/network-service discovery, naming service, IoT service discovery, data discovery, user registration, and content delivery. For all of these components, discussions for secure solutions are offered. We also provide discussions on inter- connecting heterogeneous ICN-IoT domains.

Authors

Yanyong Zhang (yyzhang@winlab.rutgers.edu)
Dipankar Raychadhuri (ray@winlab.rutgers.edu)
Luigi Grieco (alfredo.grieco@poliba.it)
Sicari Sabrina (sabrina.sicari@uninsubria.it)
Hang Liu (liuh@cua.edu)
Satyajayant Misra (misra@cs.nmsu.edu)
Ravi Ravindran (ravi.ravindran@huawei.com)
Guoqiang Wang (gq.wang@huawei.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)