IETF Logo Mail Archive

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

Yusuke DOI <yusuke.doi@toshiba.co.jp> Fri, 04 October 2013 08:15 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 A1F3021F9B85 for <roll@ietfa.amsl.com>; Fri, 4 Oct 2013 01:15:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.089
X-Spam-Level:
X-Spam-Status: No, score=-8.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_HI=-8, 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 Zj6GbRzcRLfk for <roll@ietfa.amsl.com>; Fri, 4 Oct 2013 01:15:28 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id 34B5821F9C69 for <roll@ietf.org>; Fri, 4 Oct 2013 01:08:05 -0700 (PDT)
Received: from tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp ([133.199.232.103]) by imx12.toshiba.co.jp with ESMTP id r9487i4Z024337 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <roll@ietf.org>; Fri, 4 Oct 2013 17:07:45 +0900 (JST)
Received: from tsbmgw-mgw01 (localhost [127.0.0.1]) by tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id r9487hig012311 for <roll@ietf.org>; Fri, 4 Oct 2013 17:07:43 +0900
Received: from localhost ([127.0.0.1]) by tsbmgw-mgw01 (JAMES SMTP Server 2.3.1) with SMTP ID 281 for <roll@ietf.org>; Fri, 4 Oct 2013 17:07:43 +0900 (JST)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id r9487hua012306 for <roll@ietf.org>; Fri, 4 Oct 2013 17:07:43 +0900
Received: (from root@localhost) by arc11.toshiba.co.jp id r9487hI0023511 for roll@ietf.org; Fri, 4 Oct 2013 17:07:43 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] by arc11.toshiba.co.jp with ESMTP id TAA23507; Fri, 4 Oct 2013 17:07:43 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp with ESMTP id r9487gNl028982 for <roll@ietf.org>; Fri, 4 Oct 2013 17:07:42 +0900 (JST)
Received: from spiffy21.isl.rdc.toshiba.co.jp by toshiba.co.jp id r9487gsb024011; Fri, 4 Oct 2013 17:07:42 +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 3141997D7E for <roll@ietf.org>; Fri, 4 Oct 2013 17:07:39 +0900 (JST)
Message-ID: <524E7734.1010604@toshiba.co.jp>
Date: Fri, 04 Oct 2013 17:07:16 +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: roll@ietf.org
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Subject: [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 08:15:41 -0000

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

v2.23.0 | Report a Bug | By Email