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

Yusuke DOI <yusuke.doi@toshiba.co.jp> Sun, 03 November 2013 08:54 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 BDBF811E817F for <roll@ietfa.amsl.com>; Sun, 3 Nov 2013 01:54:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.09
X-Spam-Level:
X-Spam-Status: No, score=-6.09 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 PCYvanAuNPaG for <roll@ietfa.amsl.com>; Sun, 3 Nov 2013 01:54:11 -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 E0D0B11E80D9 for <roll@ietf.org>; Sun, 3 Nov 2013 01:54:10 -0700 (PDT)
Received: from tsbmgw-mgw02.tsbmgw-mgw02.toshiba.co.jp ([133.199.200.50]) by imx2.toshiba.co.jp with ESMTP id rA38s9nt028669 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <roll@ietf.org>; Sun, 3 Nov 2013 17:54:09 +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 rA38s9Vk022179 for <roll@ietf.org>; Sun, 3 Nov 2013 17:54:09 +0900
Received: from localhost ([127.0.0.1]) by tsbmgw-mgw02 (JAMES SMTP Server 2.3.1) with SMTP ID 410 for <roll@ietf.org>; Sun, 3 Nov 2013 17:54:09 +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 rA38s933021920 for <roll@ietf.org>; Sun, 3 Nov 2013 17:54:09 +0900
Received: (from root@localhost) by arc1.toshiba.co.jp id rA38s96S002084 for roll@ietf.org; Sun, 3 Nov 2013 17:54:09 +0900 (JST)
Received: from unknown [133.199.192.144] by arc1.toshiba.co.jp with ESMTP id TAA02081; Sun, 3 Nov 2013 17:54:08 +0900
Received: from mx12.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp with ESMTP id rA38s8uD005678 for <roll@ietf.org>; Sun, 3 Nov 2013 17:54:08 +0900 (JST)
Received: from spiffy21.isl.rdc.toshiba.co.jp by toshiba.co.jp id rA38s8fZ024579; Sun, 3 Nov 2013 17:54:08 +0900 (JST)
Received: from [133.199.17.115] (ivpn-2-115.mobile.toshiba.co.jp [133.199.17.115]) by spiffy21.isl.rdc.toshiba.co.jp (Postfix) with ESMTPS id 13C2597D6E; Sun, 3 Nov 2013 17:54:08 +0900 (JST)
Message-ID: <52760F2D.5000209@toshiba.co.jp>
Date: Sun, 03 Nov 2013 17:54:05 +0900
From: Yusuke DOI <yusuke.doi@toshiba.co.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.2; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <524E7734.1010604@toshiba.co.jp> <161bac5b78b2dd33ad805a81e7df83f4@xs4all.nl> <524EA0B9.4090908@toshiba.co.jp> <641a5c59776214374984816097e08d9a@xs4all.nl> <20131101205139.9C39ECA0DA@sandelman.ca>
In-Reply-To: <20131101205139.9C39ECA0DA@sandelman.ca>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Cc: roll@ietf.org
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: Sun, 03 Nov 2013 08:54:16 -0000

(2013-11-02 5:51), Michael Richardson wrote:
> peter van der Stok <stokcons@xs4all.nl> wrote:
>> Hi Yusuke,
>>
>> For the moment the parameters are general for al interfaces, seeds and
>> messages.
>> In the case of changing per message, the parameter sets need to be
>> attached to each message entry. (for me that is a large change)
> 
> I don't think he wants to do it per message
> He wants to use some out-of-scope management interface to tweak the values
> as the network grows, changes, or as performance data is gathered.
> 
> The question could be restated as:
>      What is the affect on MPL stability is nodes differ on Imin, etc. by up
>   to
>      10% while data transmission is active.

Michael, thank you for question clarification. Yes, we expect changing
large-scale mesh network with low traffic (somewhat around 1,000 node or
even more). I think carefully-selected 'default parameter set' should
work good enough for 95% of deployment. However we need some 'knob' to
control MPL parameters for the last 5% (or even more). The parameter
update shall be moderate and 10% is a good threashold.

(c.f.
http://tools.ietf.org/html/draft-doi-roll-mpl-parameter-configuration-03
is intended to make this happen)

I personally don't expect parameter update should happen frequently
(say, once a day or so). I'd like to analyze deeper on this topic soon,
but no clear result for this IETF meeting yet. (also depends on the
implementations -- if the code does not expect parameters update,

I also have interestingly read draft-roux-roll-mpl-eval-00. I'm trying
to follow their method (by my own code. I need to build it up from
scratch). If there are good codebase to start with, I really appreciate it.

Thanks,

Yusuke