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

Ralph Droms <rdroms.ietf@gmail.com> Mon, 04 June 2012 18:29 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 4F82711E80B6 for <roll@ietfa.amsl.com>; Mon, 4 Jun 2012 11:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.539
X-Spam-Level:
X-Spam-Status: No, score=-103.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 oLSfhJWdCYXx for <roll@ietfa.amsl.com>; Mon, 4 Jun 2012 11:29:44 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9833811E809B for <roll@ietf.org>; Mon, 4 Jun 2012 11:29:44 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so3004283vcq.31 for <roll@ietf.org>; Mon, 04 Jun 2012 11:29:44 -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=pWKfp9+u5h0BTJGmILsB8Nngl2aTd1476ZwpTWhA/+8=; b=sOrPiOcb601JnF1jVv5xVGSqVZbaL2hZhobZ1ouKgnfHeCI06Pwu5YxffhQBQ15cJf sq81uEVgMbmjMexI0SFXbSfwtJ/IgOvUILTdrB19p9XlPl98MODTiElb0+EOs7EfNKGM UgH1CeUjEvvXE7zU6va6DQ7c+4KtwBzFLmxMp2bCgc9d2OWLgZL/kzfohnLll/aiQiQc 2+ySwrs+PtQFb1b2Iw9AHMwjInZ0Qmz7ja3XxTBr4gzWM1SWhlS7m6XgB49c9nAGCQPN g5X7TXeOxfr+UvF1afUILHC6etvC1f2Amgh88fWVxbk6qicbep6/FJ/MeC8zhRXNdgK3 kdaQ==
Received: by 10.220.154.2 with SMTP id m2mr13226358vcw.2.1338834583900; Mon, 04 Jun 2012 11:29:43 -0700 (PDT)
Received: from [161.44.65.173] ([161.44.65.173]) by mx.google.com with ESMTPS id j2sm18472314vde.16.2012.06.04.11.29.41 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Jun 2012 11:29:42 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <CAErDfUSBrY4FGoBLCMHNQU0ufzfuPaMnh0ZohB5UL5RaD=FxWQ@mail.gmail.com>
Date: Mon, 4 Jun 2012 14:29:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <29FA5C28-F803-45E6-8C2F-DC0EBCA563D9@gmail.com>
References: <058.aaa3fc2efaae8e26a2ada588bce49a89@trac.tools.ietf.org> <CAErDfUQdq57EtpY_4gmONwaC0t2JM7AgGWUMri_NjR+PgW8wrQ@mail.gmail.com> <19632.1337959850@marajade.sandelman.ca> <CBDF02C3-364B-4C93-A741-E29ADB2B08EF@gmail.com> <CAErDfUSBrY4FGoBLCMHNQU0ufzfuPaMnh0ZohB5UL5RaD=FxWQ@mail.gmail.com>
To: Omprakash Gnawali <gnawali@cs.uh.edu>
X-Mailer: Apple Mail (2.1278)
Cc: draft-ietf-roll-minrank-hysteresis-of@tools.ietf.org, Stiemerling Martin <mstiemerling@googlemail.com>, roll <roll@ietf.org>, Haberman Brian <brian@innovationslab.net>
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: Mon, 04 Jun 2012 18:29:45 -0000

On Jun 2, 2012, at 5:06 AM 6/2/12, Omprakash Gnawali wrote:

> On Fri, Jun 1, 2012 at 2:28 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
>> 
>> 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.
> 
> 
> This is a good feedback based on what is happening in practice. Happy
> to incorporate this by changing the existing text from:
> 
> An implementation SHOULD allow the following parameters to be
>   configured at installation time: MAX_LINK_METRIC, MAX_PATH_COST,
>   PARENT_SWITCH_THRESHOLD, PARENT_SET_SIZE, and ALLOW_FLOATING_ROOT.
>   An implementation MAY allow these parameters to be configured
>   dynamically at run time once a network has been deployed.
> 
> to:
> 
> An implementation needs specific values for the following
> parameters: MAX_LINK_METRIC, MAX_PATH_COST,
>   PARENT_SWITCH_THRESHOLD, PARENT_SET_SIZE, and ALLOW_FLOATING_ROOT.

Should "selected metric" be added to this list?

> These parameters may be set at device
> manufacturing time, configured at installation time, or configured
> at run time once a network has been deployed. MRHOF
> does not directly help determine the values for these
> parameters.

Text looks good to me.

- Ralph

> 
> - om_p