Study Report on a Framework for Cloud Inter-connection toward the Realization of IoT
draft-baba-iot-interconnection-04
Internet Research Task Force H. Baba
Internet-Draft The University of Tokyo
Intended status: Informational I. Miyake
Expires: March 13, 2021 IoT Square Inc.
J. Matsumura
BizMobile Inc.
Y. Ishida
Japan Network Enabler Corporation
September 9, 2020
Study Report on a Framework for Cloud Inter-connection toward the
Realization of IoT
draft-baba-iot-interconnection-04
Abstract
This paper describes issues for solutions through cloud inter-
connection to structural problems, which are called as "silo effects"
found in cloud-connected electric home appliances, housing equipment
and sensors in the face of increasingly accelerated connection of
them. Specifically, this paper explains an inter-connection
agreement considered to be required for enhancement of cloud inter-
connection, what performance guarantee as well as IoT supervising and
management should be, necessity of inter-connection HUB which is able
to provide inter-connection amongst the preponderance of private
cloud groups, and the necessity of a mechanism to avoid threats that
cause danger to users when we make the inter-connection.
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 March 13, 2021.
Baba, et al. Expires March 13, 2021 [Page 1]
Internet-Draft IoT Interconnections September 2020
Copyright Notice
Copyright (c) 2020 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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Draft Framework for Cloud Inter-connection . . . . . . . . . 3
3. Interconnection Agreement . . . . . . . . . . . . . . . . . . 4
4. IoT Device Operation Confirmation and Monitoring . . . . . . 6
5. Interconnection HUB . . . . . . . . . . . . . . . . . . . . . 7
6. Flexibility of this method . . . . . . . . . . . . . . . . . 9
7. Mechanisms to avoid threats when we make the inter-connection 9
8. Security Considerations . . . . . . . . . . . . . . . . . . . 9
9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 10
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
11. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 10
12. Normative References . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
To date, based on the results of interviews with "Things" companies,
the authors of this paper, the Autors, issued a Problem Statement on
IoT [1], and reported on an experiment of WebAPI [2]. With further
interviewing and experiments, various requirements specification on a
base for securing cloud inter-connection in the anticipated IoT
society become clearer.
Currently, the use of various connected devices, hereinafter "IoT
Devices" is largely expected to become a using scene of IoT, and such
IoT Device manufacturers operates their private cloud groups, the
"Cloud", where IoT Devices are connected one after another. It
depends on the manufactures whether API of one cloud is open to a
third party or whether the cloud remains closed just for itself just
like a "silo". However, it is expected that API be open by
Show full document text