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

"roll issue tracker" <trac+roll@trac.tools.ietf.org> Fri, 25 May 2012 14:28 UTC

Return-Path: <trac+roll@trac.tools.ietf.org>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 9363C21F8603 for <roll@ietfa.amsl.com>; Fri, 25 May 2012 07:28:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 3UR5aksweC3J for <roll@ietfa.amsl.com>; Fri, 25 May 2012 07:28:56 -0700 (PDT)
Received: from gamay.tools.ietf.org (gamay.tools.ietf.org []) by ietfa.amsl.com (Postfix) with ESMTP id 16AB421F85E6 for <roll@ietf.org>; Fri, 25 May 2012 07:28:55 -0700 (PDT)
Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+roll@trac.tools.ietf.org>) id 1SXvVK-00087K-VD; Fri, 25 May 2012 10:28:35 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: roll issue tracker <trac+roll@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: draft-ietf-roll-minrank-hysteresis-of@tools.ietf.org, mcr@sandelman.ca
X-Trac-Project: roll
Date: Fri, 25 May 2012 14:28:34 -0000
X-URL: http://tools.ietf.org/wg/roll/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/roll/trac/ticket/99
Message-ID: <058.aaa3fc2efaae8e26a2ada588bce49a89@trac.tools.ietf.org>
X-Trac-Ticket-ID: 99
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-roll-minrank-hysteresis-of@tools.ietf.org, mcr@sandelman.ca, roll@ietf.org
X-SA-Exim-Mail-From: trac+roll@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false
Resent-Message-Id: <20120525142856.16AB421F85E6@ietfa.amsl.com>
Resent-Date: Fri, 25 May 2012 07:28:55 -0700
Resent-From: trac+roll@trac.tools.ietf.org
Cc: roll@ietf.org
Subject: [Roll] [roll] #99: clarify for readers how/where provisioning of devices occurs
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: roll@ietf.org
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:28:56 -0000

#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/>