Re: [Roll] [roll] #99: clarify for readers how/where provisioning of devices occurs

Omprakash Gnawali <gnawali@cs.uh.edu> Fri, 25 May 2012 14:32 UTC

Return-Path: <gnawali@cs.uh.edu>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88BBF21F8674 for <roll@ietfa.amsl.com>; Fri, 25 May 2012 07:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.977
X-Spam-Level:
X-Spam-Status: No, score=-5.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UsP-jaFvKHrX for <roll@ietfa.amsl.com>; Fri, 25 May 2012 07:32:32 -0700 (PDT)
Received: from dijkstra.cs.uh.edu (dijkstra.cs.uh.edu [129.7.240.12]) by ietfa.amsl.com (Postfix) with ESMTP id F2E4821F8673 for <roll@ietf.org>; Fri, 25 May 2012 07:32:31 -0700 (PDT)
Received: from localhost (dijkstra.cs.uh.edu [127.0.0.1]) by dijkstra.cs.uh.edu (Postfix) with ESMTP id 89D8523CAA5 for <roll@ietf.org>; Fri, 25 May 2012 09:32:31 -0500 (CDT)
X-Virus-Scanned: amavisd-new at cs.uh.edu
Received: from dijkstra.cs.uh.edu ([127.0.0.1]) by localhost (dijkstra.cs.uh.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KzLOK4Toz8iX for <roll@ietf.org>; Fri, 25 May 2012 09:32:28 -0500 (CDT)
Received: from it.cs.uh.edu (it.cs.uh.edu [129.7.240.6]) by dijkstra.cs.uh.edu (Postfix) with ESMTP id 3BA8123CAA2 for <roll@ietf.org>; Fri, 25 May 2012 09:32:28 -0500 (CDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by it.cs.uh.edu (Postfix) with ESMTP id 533B52A280C0 for <roll@ietf.org>; Fri, 25 May 2012 09:28:58 -0500 (CDT)
Received: by wgbdr13 with SMTP id dr13so653207wgb.13 for <roll@ietf.org>; Fri, 25 May 2012 07:32:26 -0700 (PDT)
Received: by 10.180.100.2 with SMTP id eu2mr31858108wib.10.1337956345601; Fri, 25 May 2012 07:32:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.180.101.168 with HTTP; Fri, 25 May 2012 07:32:05 -0700 (PDT)
In-Reply-To: <058.aaa3fc2efaae8e26a2ada588bce49a89@trac.tools.ietf.org>
References: <058.aaa3fc2efaae8e26a2ada588bce49a89@trac.tools.ietf.org>
From: Omprakash Gnawali <gnawali@cs.uh.edu>
Date: Fri, 25 May 2012 09:32:05 -0500
Message-ID: <CAErDfUQdq57EtpY_4gmONwaC0t2JM7AgGWUMri_NjR+PgW8wrQ@mail.gmail.com>
To: roll@ietf.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: draft-ietf-roll-minrank-hysteresis-of@tools.ietf.org, mcr@sandelman.ca
Subject: Re: [Roll] [roll] #99: clarify for readers how/where provisioning of devices occurs
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2012 14:32:32 -0000

I was wondering if the first paragraph of 6.1 is enough for things
that need to be configured/provisioned for MRHOF.

- om_p

On Fri, May 25, 2012 at 9:28 AM, roll issue tracker
<trac+roll@trac.tools.ietf.org>; wrote:
> #99: clarify for readers how/where provisioning of devices occurs
>
>  {{{
>  >      Ralph>  OK, do I understand the fundamental issue correctly: the
>  >      Ralph>  assumption that there must be some form of installation
>  >      Ralph>  process to adapt the device to the specific deployment?
>  >
>  > Yes, that's my understanding of what current manufacturers/system
>  > integrators expect.  Remember: there is layer-2 security stuff that also
>  > would need to be initialized before the smart object could even get on
>  > the network to see any kind of announcement.
>  >
>  > I believe that the layer-2 key initialization stuff will progress in the
>  > future.  802.15.9 is chaired by Bob Moskovitz, and they are discussing
>  > DTLS, IKEv2, HIP and a fourth one.
>  >
>  >
>
>  As long as that is clarified in the document, I am fine with it.
>  }}}
>
> --
> -------------------------+-------------------------------------------------
>  Reporter:  mcr@…        |      Owner:  draft-ietf-roll-minrank-hysteresis-
>     Type:  task         |  of@…
>  Priority:  major        |     Status:  new
> Component:  minrank-     |  Milestone:
>  hysteresis-of          |    Version:
>  Severity:  In WG Last   |   Keywords:
>  Call                   |
> -------------------------+-------------------------------------------------
>
> Ticket URL: <http://trac.tools.ietf.org/wg/roll/trac/ticket/99>
> roll <http://tools.ietf.org/wg/roll/>
>