Network Working Group D. Liu
Internet-Draft Q. An
Intended status: Experimental Alibaba Group
Expires: January 7, 2017 July 6, 2016
Guidance for Thing Secure Bootstrapping Design
draft-liu-t2trg-secure-bootstrapping-00
Abstract
This document gives guidance for designing secure bootstrapping
method for Internet of Things (IoT) systems.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
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 January 7, 2017.
Copyright Notice
Copyright (c) 2016 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
Liu & An Expires January 7, 2017 [Page 1]
Internet-Draft ITS Scenario July 2016
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. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Detailed Flow . . . . . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
7. Normative References . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
This document provides a guidance desgin for thing secure
bootstrapping for Internet of Things (IoT) system. It introduces
third-party entity located in Internet into thing bootstrapping, to
offer enhanced security.
2. Architecture
Architecture for thing secure bootstrapping method is shown in figure
1.
preamble to the figure.
+---------+
| Cloud |
| Server |
+---------+
|
|
+------------------------------+
| Group Owner |
+------------------------------+
| |
+-----------+ +----------+
| |
+----------+ +----------+
| Thing | | User APP |
+----------+ +----------+
Figure 1: Architecture for thing secure bootstrapping method
Liu & An Expires January 7, 2017 [Page 2]
Internet-Draft ITS Scenario July 2016
3. Detailed Flow
This section discusses detailed flow for thing secure bootstrapping
method.
The flow of thing secure bootstrapping method is shown in figure 2.
preamble to the figure.
Liu & An Expires January 7, 2017 [Page 3]
Internet-Draft ITS Scenario July 2016
+----+ +----+ +------+ +-----+ +------+
|User| |User| |Thing | |Group| |Cloud |
| | |APP | | | |Owner| |Server|
+----+ +----+ +------+ +-----+ +------+
|1.Initiate | | | |
|bootstrapping. | | | |
|User APP is in | | | |
|"Listen" mode | | | |
|-------------->| | | |
| | | | 2.Notify |
| | | | Server |
| |--------------+-------------+-------------->|
| | | | 3.Create PSK |
| | | | and send to |
| | | | group owner |
| | | |<--------------|
| | |4.Broadcast | |
| | |RandomKey | |
| | |<------------| |
|5.Trigger thing| | | |
|into secure | | | |
|bootsrapping | | | |
|mode | | | |
|---------------+------------->| | |
| | |---+6.Scan | |
| | | |to get | |
| | |<--+RandomKey| |
| | | | |
| | |7.Func(PSK, | |
| | |RandomKey) | |
| | |------------>| |
| | | | |
| | |8.Result of | |
| | |bootstrapping| |
| | |<------------| |
| |9.Result of | | |
| |bootstrapping | | |
| |<-------------| | |
| | | | |
|10.If succeeds,| | | |
|notify server | | | |
|---------------+--------------+-------------+-------------->|
| | | | |
Figure 1: Architecture for thing secure bootstrapping method
Liu & An Expires January 7, 2017 [Page 4]
Internet-Draft ITS Scenario July 2016
Premise of secure bootstrapping
o Group Owner can connect to Internet with server.
o User application has been binded with group owner.
Func() in step 7 is used to calculate a value based on inputing
RandomKey and PSK. and is known by both thing and group owner. The
definion is out of this document's scope.
4. IANA Considerations
This document makes no request of IANA.
5. Security Considerations
TBD
6. Acknowledgements
TBD
7. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
Authors' Addresses
Dapeng Liu
Alibaba Group
Beijing
Beijing
Phone: +86-1391788933
Email: maxpassion@gmail.com
Qing An
Alibaba Group
Beijing
Beijing
Phone: +86-13810495624
Email: anqing.aq@alibaba-inc.com
Liu & An Expires January 7, 2017 [Page 5]