Re: [Roll] [roll] #157 (draft-doi-roll-mpl-parameter-configuration): mpl-parameter-configuration-00 - Effect of inconsistent parameter set among nodes

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 30 July 2014 19:48 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6777A1A035A for <roll@ietfa.amsl.com>; Wed, 30 Jul 2014 12:48:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.892
X-Spam-Level:
X-Spam-Status: No, score=-1.892 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KF8TqhHVxqv8 for <roll@ietfa.amsl.com>; Wed, 30 Jul 2014 12:48:07 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E67D1A032E for <roll@ietf.org>; Wed, 30 Jul 2014 12:48:06 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5BBD220028; Wed, 30 Jul 2014 15:50:11 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 2BC5F63B0E; Wed, 30 Jul 2014 15:48:05 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 17F7D637FE; Wed, 30 Jul 2014 15:48:05 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-Reply-To: <6420A78D-4C7D-4DDE-8480-3C913F27F0A9@cs.stanford.edu>
References: <067.f0fd62a4161a1ac153a9b089b2780010@trac.tools.ietf.org> <538302CC.9020904@toshiba.co.jp> <3398D003-F294-455D-A036-AB7C92CDB1E8@cs.stanford.edu> <53D8BAF7.8040105@toshiba.co.jp> <6420A78D-4C7D-4DDE-8480-3C913F27F0A9@cs.stanford.edu>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Wed, 30 Jul 2014 15:48:05 -0400
Message-ID: <21697.1406749685@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/P1pJt7hUyKs27o2AHcSSSJuZG3Y
Cc: draft-doi-roll-mpl-parameter-configuration@tools.ietf.org
Subject: Re: [Roll] [roll] #157 (draft-doi-roll-mpl-parameter-configuration): mpl-parameter-configuration-00 - Effect of inconsistent parameter set among nodes
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 30 Jul 2014 19:48:10 -0000

Philip Levis <pal@cs.stanford.edu> wrote:
    > I think the most significant concern is when configuration changes
    > significantly modify Imin. In this case, the speed of per-hop update
    > can be bounded by the maximum of the old and new Imin values. E.g., if
    > the update has a much smaller Imin, then it will trigger nodes with the
    > old state to use their Imin, but if it's much larger it will take a
    > while before they transmit and implicitly request an update. Similarly,
    > if the update has a much higher Imin, it will take much longer for each
    > hop to transmit the first broadcast that triggers neighbors to shrink
    > their interval.

Can you offer any advice for the document on maximum deltas for Imin?
(a formula, if necessary)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-