Practical Considerations and Implementation Experiences in Securing Smart Object Networks
draft-aks-crypto-sensors-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-03-12
Replaced by draft-aks-lwig-crypto-sensors
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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)
Network Working Group                                           J. Arkko
Internet-Draft                                                A. Keranen
Intended status: Informational                                  Ericsson
Expires: August 4, 2012                                         M. Sethi
                                                                Ericsson
                                                        Aalto University
                                                              March 2012

  Practical Considerations and Implementation Experiences in Securing
                         Smart Object Networks
                      draft-aks-crypto-sensors-01

Abstract

   This memo describes challenges associated with securing smart object
   devices in constrained implementations and environments.  The memo
   describes a possible deployment model suitable for these
   environments, discusses the availability of cryptographic libraries
   for small devices, presents some experiences in implementing small
   devices using those libraries, and discusses trade-offs involving
   different types of 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 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 August 4, 2012.

Copyright Notice

   Copyright (c) 2012 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

Arkko, et al.            Expires August 4, 2012                 [Page 1]
Internet-Draft      Smart Object Security Experiences         March 2012

   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
     1.1.  Related Work . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Challenges . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Proposed Deployment Model  . . . . . . . . . . . . . . . . . .  5
     3.1.  Provisioning . . . . . . . . . . . . . . . . . . . . . . .  6
     3.2.  Protocol Architecture  . . . . . . . . . . . . . . . . . .  7
   4.  Code Availability  . . . . . . . . . . . . . . . . . . . . . .  8
   5.  Implementation Experiences . . . . . . . . . . . . . . . . . . 10
   6.  Design Trade-Offs  . . . . . . . . . . . . . . . . . . . . . . 14
     6.1.  Feasibility  . . . . . . . . . . . . . . . . . . . . . . . 14
     6.2.  Layering . . . . . . . . . . . . . . . . . . . . . . . . . 15
     6.3.  Symmetric vs. Asymmetric Crypto  . . . . . . . . . . . . . 17
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 17
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 18
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 18
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 19
   Appendix A.  Acknowledgments . . . . . . . . . . . . . . . . . . . 21
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21

Arkko, et al.            Expires August 4, 2012                 [Page 2]
Internet-Draft      Smart Object Security Experiences         March 2012

1.  Introduction

   This memo describes challenges associated with securing smart object
   devices in constrained implementations and environments (see
   Section 2).

   Secondly, Section 3 discusses a deployment model that the authors are
   considering for constrained environments.  The model requires minimal
   amount of configuration, and we believe it is a natural fit with the
   typical communication practices smart object networking environments.

   Thirdly, Section 4 discusses the availability of cryptographic
   libraries.  Section 5 presents some experiences in implementing small
   devices using those libraries, including information about achievable
   code sizes and speeds on typical hardware.
Show full document text