IETF Logo Mail Archive

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

DOI Yusuke <yusuke.doi@toshiba.co.jp> Fri, 04 October 2013 15:11 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 0A14921F9BB5 for <roll@ietfa.amsl.com>; Fri, 4 Oct 2013 08:11:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.09
X-Spam-Level:
X-Spam-Status: No, score=-8.09 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]
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 zTmt++vhrwvw for <roll@ietfa.amsl.com>; Fri, 4 Oct 2013 08:11:26 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id 3F5F321F9D9A for <roll@ietf.org>; Fri, 4 Oct 2013 08:07:07 -0700 (PDT)
Received: from tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp ([133.199.232.103]) by imx12.toshiba.co.jp with ESMTP id r94F76po000084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <roll@ietf.org>; Sat, 5 Oct 2013 00:07:06 +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 r94F755A014256 for <roll@ietf.org>; Sat, 5 Oct 2013 00:07:05 +0900
Received: from localhost ([127.0.0.1]) by tsbmgw-mgw01 (JAMES SMTP Server 2.3.1) with SMTP ID 846 for <roll@ietf.org>; Sat, 5 Oct 2013 00:07:05 +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 r94F75Q3014250 for <roll@ietf.org>; Sat, 5 Oct 2013 00:07:05 +0900
Received: (from root@localhost) by arc11.toshiba.co.jp id r94F75HK005027 for roll@ietf.org; Sat, 5 Oct 2013 00:07:05 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] by arc11.toshiba.co.jp with ESMTP id AAA05025; Sat, 5 Oct 2013 00:07:05 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp with ESMTP id r94F75P6017239 for <roll@ietf.org>; Sat, 5 Oct 2013 00:07:05 +0900 (JST)
Received: by toshiba.co.jp id r94F74xX010751; Sat, 5 Oct 2013 00:07:04 +0900 (JST)
Date: Sat, 05 Oct 2013 00:07:03 +0900
Message-Id: <201310041507.r94F74xX010751@toshiba.co.jp>
To: roll@ietf.org, d.sturek@att.net
From: DOI Yusuke <yusuke.doi@toshiba.co.jp>
In-Reply-To: <CE741320.23F5F%d.sturek@att.net>
References: <524E7734.1010604@toshiba.co.jp> <CE741320.23F5F%d.sturek@att.net>
X-Mailer: Mew version 6.3 on Emacs 23.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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 15:11:40 -0000

Hi Don,

I thought some unbalanced transmission could happen and acceptable,
but other issues may occur as you and Peter say.

I think it's better to find some workaround for now.

Thank you very much!

Yusuke

From: Don Sturek <d.sturek@att.net>
Subject: Re: [Roll] Question on MPL: parameter update on runnning MPL forwarders
Date: Fri, 04 Oct 2013 06:45:13 -0700

> Hi Yusuke,
> 
> <I haven't tried this with our running code however...... >
> 
> I don't believe it is possible to change imin, imax, k or any other
> operational MPL forwarder parameter without some sort of
> pre-distribution/synchronization of the new parameters.  It would work as
> you note if there are no transmission or valid seed set but if multicast
> traffic is already present using an existing seed, I would expect you
> would see issues in distribution of messages if you change the parameters
> while in operation.   Additionally, if you use MPL to distribute the
> change with existing multicast traffic you will find some nodes do not get
> the new parameters (which will create other problems when you want the new
> parameters to take effect)
> 
> Don
> 
> 
> 
> On 10/4/13 1:07 AM, "Yusuke DOI" <yusuke.doi@toshiba.co.jp> wrote:
> 
>>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

v2.23.0 | Report a Bug | By Email