[6lowapp] New I-D: Initial Configuration of Resource-Constrained Devices (aka: Bootstrapping / Commissioning)

"Oflynn, Colin" <Colin.OFlynn@atmel.com> Tue, 02 March 2010 07:22 UTC

Return-Path: <Colin.OFlynn@atmel.com>
X-Original-To: 6lowapp@core3.amsl.com
Delivered-To: 6lowapp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6167828C6E9; Mon, 1 Mar 2010 23:22:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QByM3q2ytG0k; Mon, 1 Mar 2010 23:22:06 -0800 (PST)
Received: from sjogate2.atmel.com (newsmtp5.atmel.com [204.2.163.5]) by core3.amsl.com (Postfix) with ESMTP id 73D0028C6E0; Mon, 1 Mar 2010 23:22:06 -0800 (PST)
Received: from csomb01.corp.atmel.com ([10.95.30.150]) by sjogate2.atmel.com (8.13.6/8.13.6) with ESMTP id o227K5P0013087; Mon, 1 Mar 2010 23:20:06 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAB9D9.06CD064C"
Date: Tue, 02 Mar 2010 00:21:50 -0700
Message-ID: <C6471264338047459F18230B4F871DA0098F048D@csomb01.corp.atmel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: New I-D: Initial Configuration of Resource-Constrained Devices (aka: Bootstrapping / Commissioning)
Thread-Index: Acq52QauWhYparFBSh2geEx+R60x5Q==
From: "Oflynn, Colin" <Colin.OFlynn@atmel.com>
To: core@ietf.org, 6lowapp@ietf.org
Subject: [6lowapp] New I-D: Initial Configuration of Resource-Constrained Devices (aka: Bootstrapping / Commissioning)
X-BeenThere: 6lowapp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowapp>
List-Post: <mailto:6lowapp@ietf.org>
List-Help: <mailto:6lowapp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2010 07:22:07 -0000

http://www.ietf.org/id/draft-oflynn-core-bootstrapping-00.txt

Lots to do in here still. Note this was posted yesterday, but I didn't get around to forwarding the announcement. This updates the previous 6lowapp bootstrapping document a bit too, but is posted as a new I-D to move to the CoRE group.

Regards,

  -Colin


Filename:          draft-oflynn-core-bootstrapping
Version:           00
Title:             Initial Configuration of Resource-Constrained Devices
Creation_date:     2010-02-28
WG ID:             Individual Submission
Number_of_pages: 28
Abstract:
The Internet of Things is marching its way towards completion.  Nodes
can use standards from the 6LoWPAN and ROLL WG to achieve IP
connectivity.  IEEE Standards ensure connectivity at lower layers for
resource-constrained devices.  Yet a central problem remains at a
more basic layer without a suitable answer: how to initially
configure the network.  Without configuration the network never
advances beyond a large box of nodes.  Current solutions tend to be
specific to a certain vendor, node type, or application.

This document outlines exactly what problems are faced in solving
this problem.  General problems faced in any low-power wireless
network are outlined first; followed by how these apply to
bootstrapping.  A selection of currently proposed techniques is
presented.  From these a more generic approach is presented, which
can solve the problem for a wide range of situations.

An emphasis is on performing this bootstrapping in a secure manner.
This document does not cover operation of the network securely.  This
document does provide the basis for allowing the network to operate
securely however, by providing standard methods for key exchanges and
authentication.

Submitter: Colin O'Flynn (colin.oflynn@atmel.com)

Author(s):
Colin O'Flynn, colin.oflynn@atmel.com
Behcet Sarikaya, sarikaya@ieee.org