Practical Considerations and Implementation Experiences in Securing Smart Object Networks
draft-ietf-lwig-crypto-sensors-06
|
Document |
Type |
|
Active Internet-Draft (lwig WG)
|
|
Last updated |
|
2018-04-24
(latest revision 2018-02-26)
|
|
Replaces |
|
draft-aks-lwig-crypto-sensors
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Informational
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
Submitted to IESG for Publication
(wg milestone:
Jan 2017 - Submit the lightwei...
)
|
|
Document shepherd |
|
Zhen Cao
|
|
Shepherd write-up |
|
Show
(last changed 2017-09-28)
|
IESG |
IESG state |
|
RFC Ed Queue
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Suresh Krishnan
|
|
Send notices to |
|
Zhen Cao <zhencao.ietf@gmail.com>
|
IANA |
IANA review state |
|
IANA OK - No Actions Needed
|
|
IANA action state |
|
No IC
|
RFC Editor |
RFC Editor state |
|
AUTH48 |
Light-Weight Implementation Guidance M. Sethi
Internet-Draft J. Arkko
Intended status: Informational A. Keranen
Expires: August 30, 2018 Ericsson
H. Back
Nokia
February 26, 2018
Practical Considerations and Implementation Experiences in Securing
Smart Object Networks
draft-ietf-lwig-crypto-sensors-06
Abstract
This memo describes challenges associated with securing resource-
constrained smart object devices. The memo describes a possible
deployment model where resource-constrained devices sign message
objects, discusses the availability of cryptographic libraries for
resource-constrained devices and presents some preliminary
experiences with those libraries for message signing on resource-
constrained devices. Lastly, the memo discusses trade-offs involving
different types of security approaches.
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 August 30, 2018.
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
Sethi, et al. Expires August 30, 2018 [Page 1]
Internet-Draft Smart Object Security Experiences February 2018
(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. Related Work . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Challenges . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Proposed Deployment Model . . . . . . . . . . . . . . . . . . 6
4.1. Provisioning . . . . . . . . . . . . . . . . . . . . . . 6
4.2. Protocol Architecture . . . . . . . . . . . . . . . . . . 9
5. Code Availability . . . . . . . . . . . . . . . . . . . . . . 10
6. Implementation Experiences . . . . . . . . . . . . . . . . . 11
7. Example Application . . . . . . . . . . . . . . . . . . . . . 18
8. Design Trade-Offs . . . . . . . . . . . . . . . . . . . . . . 21
8.1. Feasibility . . . . . . . . . . . . . . . . . . . . . . . 21
8.2. Freshness . . . . . . . . . . . . . . . . . . . . . . . . 22
8.3. Layering . . . . . . . . . . . . . . . . . . . . . . . . 24
8.4. Symmetric vs. Asymmetric Crypto . . . . . . . . . . . . . 26
9. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
10. Security Considerations . . . . . . . . . . . . . . . . . . . 27
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
12. Informative references . . . . . . . . . . . . . . . . . . . 27
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34
1. Introduction
This memo describes challenges associated with securing smart object
devices in constrained implementations and environments. In
Section 3 we specifically discuss three challenges: the
implementation difficulties encountered on resource-constrained
platforms, the problem of provisioning keys and making the choice of
implementing security at the appropriate layer.
Section 4 discusses a potential deployment model for constrained
environments. The model requires minimal amount of configuration,
and we believe it is a natural fit with the typical communication
practices in smart object networking environments.
Section 5 discusses the availability of cryptographic libraries.
Show full document text