Design Considerations for Applying ICN to IoT
draft-irtf-icnrg-icniot-02
|
| Document |
Type |
|
Active Internet-Draft (icnrg RG)
|
|
Last updated |
|
2018-10-22
|
|
Replaces |
|
draft-zhang-icnrg-icniot
|
|
Stream |
|
IRTF
|
|
Intended RFC status |
|
Informational
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
IRTF state
|
|
Active RG Document
|
|
Consensus Boilerplate |
|
Unknown
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
ICN Research Group R. Ravindran, Ed.
Internet-Draft Huawei Technologies
Intended status: Informational Y. Zhang
Expires: April 25, 2019 WINLAB, Rutgers University
L. Grieco
Politecnico di Bari (DEI)
A. Lindgren
RISE SICS
J. Burke
UCLA REMAP
B. Ahlgren
RISE SICS
A. Azgin
Huawei Technologies
October 22, 2018
Design Considerations for Applying ICN to IoT
draft-irtf-icnrg-icniot-02
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 to enable a horizontally unified IoT
architecture. The objective of such an architecture is to make
resource objects securely 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 today's
Internet and the mostly information-centric nature of the IoT domain.
To address this mismatch, the common set of protocols and network
services offered by an information-centric networking (ICN)
architecture can be leveraged to realize an ICN-based IoT (or ICN-
IoT) architecture that can take advantage of the salient features of
ICN such as naming, security, mobility, compute and efficient content
and service delivery support offered by it.
In this draft, we summarize the general IoT demands, and ICN features
that support these requirements, and then discuss the challenges to
realize an ICN-based IoT framework. Beyond this, the goal of this
draft is not to offer any specific ICN-IoT architectural proposal.
Ravindran, Ed., et al. Expires April 25, 2019 [Page 1]
Internet-Draft ICN based Architecture for IoT October 2018
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 https://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 April 25, 2019.
Copyright Notice
Copyright (c) 2018 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
(https://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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Motivating ICN for IoT . . . . . . . . . . . . . . . . . . . 4
2.1. Advantages of using ICN for IoT . . . . . . . . . . . . . 5
2.2. Service Scenarios . . . . . . . . . . . . . . . . . . . . 6
3. IoT Architectural Requirements . . . . . . . . . . . . . . . 11
3.1. Naming . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2. Security and Privacy . . . . . . . . . . . . . . . . . . 12
3.3. Scalability . . . . . . . . . . . . . . . . . . . . . . . 13
3.4. Resource Constraints . . . . . . . . . . . . . . . . . . 13
3.5. Traffic Characteristics . . . . . . . . . . . . . . . . . 14
3.6. Contextual Communication . . . . . . . . . . . . . . . . 14
Show full document text