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

Ralph Droms <rdroms.ietf@gmail.com> Fri, 01 June 2012 19:28 UTC

Return-Path: <rdroms.ietf@gmail.com>
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 7AE8021F86B7 for <roll@ietfa.amsl.com>; Fri, 1 Jun 2012 12:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.359
X-Spam-Level:
X-Spam-Status: No, score=-103.359 tagged_above=-999 required=5 tests=[AWL=0.240, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 jqs9dWPH240e for <roll@ietfa.amsl.com>; Fri, 1 Jun 2012 12:28:37 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id DB19221F86B5 for <roll@ietf.org>; Fri, 1 Jun 2012 12:28:36 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1678559vbb.31 for <roll@ietf.org>; Fri, 01 Jun 2012 12:28:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=uCWT+6C/68eDK+Bg35RAAxYN984eXAaueRt3wArWE3E=; b=DQjFpCp/rAmeIgTI9v8h5ejNthufacEUxOay7n5zPDEpaCIdUM3Q6aRr2DTtikQUrA 789VLKTsFUqPx6gl2fwf62+mkeK5oFGSbdzLh3GneNHV53BeJcFMWVELbPSSb9lpm+P+ Gd4KKxS/YbshmKvKWQKga8dv7UcrcJ51K2DUKbrMsVMi/BqAfRDursIKWxC2W6bIfyhy UvfuJDCk5/MKGDfEPxboDsSWVGGXvS9VY9SMr7FEHaGW2ukMTdkHScOTc+IERaz+zMzS HkSPk97kKzSDvmhrfAazi/6YbCsQGFU3Tj24kN2Qv28UNyo6Xbb/y22uRtjS+G8N7Bjc pkfQ==
Received: by 10.52.67.226 with SMTP id q2mr3595720vdt.53.1338578916313; Fri, 01 Jun 2012 12:28:36 -0700 (PDT)
Received: from che-vpn-cluster-1-318.cisco.com (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPS id i19sm4426822vdt.18.2012.06.01.12.28.33 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 01 Jun 2012 12:28:34 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <19632.1337959850@marajade.sandelman.ca>
Date: Fri, 1 Jun 2012 15:28:32 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CBDF02C3-364B-4C93-A741-E29ADB2B08EF@gmail.com>
References: <058.aaa3fc2efaae8e26a2ada588bce49a89@trac.tools.ietf.org> <CAErDfUQdq57EtpY_4gmONwaC0t2JM7AgGWUMri_NjR+PgW8wrQ@mail.gmail.com> <19632.1337959850@marajade.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1278)
Cc: roll@ietf.org, draft-ietf-roll-minrank-hysteresis-of@tools.ietf.org
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, 01 Jun 2012 19:28:37 -0000

On May 25, 2012, at 11:30 AM 5/25/12, Michael Richardson wrote:

> 
>>>>>> "Omprakash" == Omprakash Gnawali <gnawali@cs.uh.edu> writes:
>    Omprakash> I was wondering if the first paragraph of 6.1 is enough for things
>    Omprakash> that need to be configured/provisioned for MRHOF.
> 
> I think that it works for *MRHOF*, but I think that we have a bigger
> picture problem here.

Given that the ZigBee IP spec prescribes the details of how to use MRHOF, a node that implements ZigBee IP and will not be used in any other deployment scenario can be configured at manufacturing time and there is no need for the node to "allow the [...] parameters to be configured at installation time".  However, I think draft-ietf-roll-minrank-hysteresis-of would be improved by expanding the sense of the text to something like:

   An implementation needs specific values for the following
   paramters: [...]  These parameters may be set at device
   manufacturing time or configured at installation time.  RPL/MRHOF
   do not provide a way for the appropriate values for these
   parameters to be discovered through the network. 

- Ralph

> -- 
> Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works 
> IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/
> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll