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

Don Sturek <d.sturek@att.net> Fri, 04 October 2013 13:51 UTC

Return-Path: <d.sturek@att.net>
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 928EA21F9A90 for <roll@ietfa.amsl.com>; Fri, 4 Oct 2013 06:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 7uQQNeKhYEQY for <roll@ietfa.amsl.com>; Fri, 4 Oct 2013 06:51:22 -0700 (PDT)
Received: from nm7-vm8.access.bullet.mail.bf1.yahoo.com (nm7-vm8.access.bullet.mail.bf1.yahoo.com [216.109.114.167]) by ietfa.amsl.com (Postfix) with ESMTP id B7BF721F9A2E for <roll@ietf.org>; Fri, 4 Oct 2013 06:45:18 -0700 (PDT)
Received: from [66.196.81.158] by nm7.access.bullet.mail.bf1.yahoo.com with NNFMP; 04 Oct 2013 13:45:17 -0000
Received: from [98.138.104.99] by tm4.access.bullet.mail.bf1.yahoo.com with NNFMP; 04 Oct 2013 13:45:17 -0000
Received: from [127.0.0.1] by smtp119.sbc.mail.ne1.yahoo.com with NNFMP; 04 Oct 2013 13:45:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1380894317; bh=2nSR+pED1QPQXCtuCKXkcqvlZ124wQsI5sP0fF76jLM=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic:In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; b=0Ek+/Gh68IEmqg93ZO8YBROo8smRGVTV9AcxqE5UpfIJdrVHROwHlejj8cxydNVU/m8D0v9vMkT4TiVDdp7KmLQi9cY1WSBbZ0iKOo3yEUPmSZBQohz0YSQ9X9zAvP5Juh/jLX3uTuXuwCM2AxwfNUvkOkQ2clELsb/K5FBpkf8=
X-Yahoo-Newman-Id: 63068.44506.bm@smtp119.sbc.mail.ne1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: _u6NolYVM1mIjE6_IyNHiekE85yUePuqZl1Gj0VOCXvV8ZI YOxwOIw2oJ.ovIAuWzM.kZRVOG_iKr5QCSlHSm71XhmTPA7eVz4OPnC.HuDN IewIHsDaJQ4MQh6XDEqoVjQnSaFUUC53m5zlSc.DfkeBWaGh6A3yRJanw9WV xaKSLS2m5SsNgpLvpUio37130vVd_LXOSe4LgK5IxrOnlod7kl5msblRORp6 1oZ.c4Y9VvTHrb2C3a2bJXgIth6pH0ICElNSwLghIf3MthMN5NlDCUkuzpdW eXUTTHpuF8513QTWcsL5emGkWygUf83hSA3So6z1E7T0RQwOFt4OqXE5.Tnj 8yk_Ji4Y2MOcXk4vPiCMOJTt5cRqKVoTjxm2N0y6tIAQQFOXS5XIhZJDkagh iSXzHspuunbDFC616v.Ja3lYzKhzcLdnY0RqCDwW2d4rY2DnnaMaq8up_URt xyXkdpYbS916wEvXCvgWh7aZUUB6Cxx8b_Bo9JDyckeYS.KiXGZbynDePh9Q hb4.ca.pa2UKMiv15qNMDkXhScx9nSCK6.eteZfqMzV8vv4Hcobz3RuVKS6S _TNY6
X-Yahoo-SMTP: fvjol_aswBAraSJvMLe2r1XTzhBhbFxY8q8c3jo-
X-Rocket-Received: from [10.0.0.4] (d.sturek@69.105.138.165 with ) by smtp119.sbc.mail.ne1.yahoo.com with SMTP; 04 Oct 2013 13:45:17 +0000 UTC
User-Agent: Microsoft-MacOutlook/14.3.7.130812
Date: Fri, 04 Oct 2013 06:45:13 -0700
From: Don Sturek <d.sturek@att.net>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Message-ID: <CE741320.23F5F%d.sturek@att.net>
Thread-Topic: [Roll] Question on MPL: parameter update on runnning MPL forwarders
In-Reply-To: <524E7734.1010604@toshiba.co.jp>
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 13:51:43 -0000

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