Design Considerations for Applying ICN to IoT
draft-zhang-icnrg-icniot-01

Document Type Active Internet-Draft (individual)
Last updated 2017-06-26
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ICN Research Group                                              Y. Zhang
Internet-Draft                                            D. Raychadhuri
Intended status: Informational                WINLAB, Rutgers University
Expires: December 28, 2017                                     L. Grieco
                                               Politecnico di Bari (DEI)
                                                             E. Baccelli
                                                                   INRIA
                                                                J. Burke
                                                              UCLA REMAP
                                                            R. Ravindran
                                                                 G. Wang
                                                     Huawei Technologies
                                                             A. Lindgren
                                                              B. Ahlgren
                                                               RISE SICS
                                                              O. Schelen
                                          Lulea University of Technology
                                                           June 26, 2017

             Design Considerations for Applying ICN to IoT
                      draft-zhang-icnrg-icniot-01

Abstract

   The Internet of Things (IoT) promises to connect billions of objects
   to the Internet.  After deploying many stand-alone IoT systems in
   different domains, the current trend is to develop a common, "thin
   waist" of protocols over a horizontal unified, defragmented IoT
   architecture.  Such an architecture will make objects accessible to
   applications across organizations and domains.  Towards this goal,
   quite a few proposals have been made to build an application-layer
   based unified IoT platform on top of today's host-centric Internet.
   However, there is a fundamental mismatch between the host-centric
   nature of todays Internet and mostly information-centric nature of
   the IoT system.  To address this mismatch, an information-centric
   network (ICN) architecture can provide a common set of protocols and
   services, called 'ICN-IoT', which can be used to build IoT platforms.
   ICN-IoT leverages the salient features of ICN, and thus provides
   naming, security, mobility support,scalability, and efficient content
   and service delivery.

   This draft summarizes general IoT demands, and covers the challenges
   and design considerations ICN faces to realize a ICN-IoT framework
   based on ICN architecture.

Zhang, et al.           Expires December 28, 2017               [Page 1]
Internet-Draft       ICN based Architecture for IoT            June 2017

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 28, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  IoT Motivation  . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Motivating ICN for IoT  . . . . . . . . . . . . . . . . . . .   4
   3.  IoT Architectural Requirements  . . . . . . . . . . . . . . .   9
     3.1.  Naming  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     3.2.  Security and Privacy  . . . . . . . . . . . . . . . . . .  10
     3.3.  Scalability . . . . . . . . . . . . . . . . . . . . . . .  10
     3.4.  Resource Constraints  . . . . . . . . . . . . . . . . . .  10
     3.5.  Traffic Characteristics . . . . . . . . . . . . . . . . .  11
Show full document text