Re: [Roll] Question on MPL: parameter update on runnning MPL forwarders

Yusuke DOI <yusuke.doi@toshiba.co.jp> Fri, 04 October 2013 11:06 UTC

Return-Path: <yusuke.doi@toshiba.co.jp>
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 A8EFB21F942D for <roll@ietfa.amsl.com>; Fri, 4 Oct 2013 04:06:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.089
X-Spam-Level:
X-Spam-Status: No, score=-6.089 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
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 YvqbTZKVLfja for <roll@ietfa.amsl.com>; Fri, 4 Oct 2013 04:06:09 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by ietfa.amsl.com (Postfix) with ESMTP id 7247021F9991 for <roll@ietf.org>; Fri, 4 Oct 2013 04:04:51 -0700 (PDT)
Received: from tsbmgw-mgw02.tsbmgw-mgw02.toshiba.co.jp ([133.199.200.50]) by imx2.toshiba.co.jp with ESMTP id r94B4mSV021828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <roll@ietf.org>; Fri, 4 Oct 2013 20:04:48 +0900 (JST)
Received: from tsbmgw-mgw02 (localhost [127.0.0.1]) by tsbmgw-mgw02.tsbmgw-mgw02.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id r94B4m2I015552 for <roll@ietf.org>; Fri, 4 Oct 2013 20:04:48 +0900
Received: from localhost ([127.0.0.1]) by tsbmgw-mgw02 (JAMES SMTP Server 2.3.1) with SMTP ID 667 for <roll@ietf.org>; Fri, 4 Oct 2013 20:04:48 +0900 (JST)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by tsbmgw-mgw02.tsbmgw-mgw02.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id r94B4mPu015546 for <roll@ietf.org>; Fri, 4 Oct 2013 20:04:48 +0900
Received: (from root@localhost) by arc1.toshiba.co.jp id r94B4mAY022867 for roll@ietf.org; Fri, 4 Oct 2013 20:04:48 +0900 (JST)
Received: from unknown [133.199.192.144] by arc1.toshiba.co.jp with ESMTP id WAA22861; Fri, 4 Oct 2013 20:04:48 +0900
Received: from mx12.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp with ESMTP id r94B4lr5029574 for <roll@ietf.org>; Fri, 4 Oct 2013 20:04:47 +0900 (JST)
Received: from spiffy21.isl.rdc.toshiba.co.jp by toshiba.co.jp id r94B4lfN012419; Fri, 4 Oct 2013 20:04:47 +0900 (JST)
Received: from [133.196.16.145] (ncg-dhcp145.isl.rdc.toshiba.co.jp [133.196.16.145]) by spiffy21.isl.rdc.toshiba.co.jp (Postfix) with ESMTPS id 7EA2897D7E; Fri, 4 Oct 2013 20:04:47 +0900 (JST)
Message-ID: <524EA0B9.4090908@toshiba.co.jp>
Date: Fri, 04 Oct 2013 20:04:25 +0900
From: Yusuke DOI <yusuke.doi@toshiba.co.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: consultancy@vanderstok.org
References: <524E7734.1010604@toshiba.co.jp> <161bac5b78b2dd33ad805a81e7df83f4@xs4all.nl>
In-Reply-To: <161bac5b78b2dd33ad805a81e7df83f4@xs4all.nl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: roll@ietf.org, peter van der Stok <stokcons@xs4all.nl>
Subject: Re: [Roll] Question on MPL: parameter update on runnning MPL forwarders
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <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, 04 Oct 2013 11:06:21 -0000

Hi Peter,

I have not recognized it needs LARGE change. My first idea was to replace the parameters at the very beginning of an interval (step 2 of RFC6206 section 4.2) for each trickle timer. Because it's difficult to synchronize the update, I think unbalanced retransmission may occur in transient period. I assume it's acceptable (safe enough).

Could you tell me about your concerns that requires LARGE spec update?

Regards,

Yusuke


(2013-10-04 17:29), peter van der Stok wrote:
> Hi Yusuke.
>
> I think you may "safely" change Imin, ,k, Imax and repeat per new message for all involved forwarders, while leaving all earlier messages unaffected. BUT this needs LARGE changes to the current spec.
>
> My 2 cents,
>
> peter
>
>
>
> Yusuke DOI schreef op 2013-10-04 10:07:
>> Hi,
>>
>> I have a simple question: is it possible to update MPL parameters of
>> running forwarder instances?
>>
>> To maintain the system in 'good state', I expect some sort of
>> parameter tuning on MPL. Especially for the systems dynamically grows,
>> static configuration of MPL parameters will be difficult. For example,
>> DHCPv6 reconfigure request can be used to update MPL forwarder
>> parameter. However, I'm not sure it's 'safe' to update parameters (K,
>> Imin, Imax) of running MPL forwarder instances.
>>
>> I think it's safe if there are no transmission / no valid seed set. Is
>> it possible to update a running MPL forwarder parameter without
>> breaking current state?
>>
>> Regards,
>>
>> Yusuke
>>
>>
>> _______________________________________________
>> Roll mailing list
>> Roll@ietf.org
>> https://www.ietf.org/mailman/listinfo/roll
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll