Re: [Roll] [dhcwg] MPL config draft (Re: I-D Action: draft-ietf-roll-mpl-parameter-configuration-01.txt)

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 19 July 2014 20:27 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 744F61B2988; Sat, 19 Jul 2014 13:27:51 -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 j8HVnHcOats3; Sat, 19 Jul 2014 13:27:46 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B980B1B27B5; Sat, 19 Jul 2014 13:27:46 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id CF2EB2002B; Sat, 19 Jul 2014 16:29:13 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 015AF63B0E; Sat, 19 Jul 2014 16:27:44 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id DF2C563AED; Sat, 19 Jul 2014 16:27:44 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-Reply-To: <E39AD318-FF6E-44A3-A3C8-4321B86B65FA@nominum.com>
References: <20140701155803.14047.81610.idtracker@ietfa.amsl.com> <53BA92D9.3000606@toshiba.co.jp> <CAL10_BqyWcb9_NBq2RzX7oX9g356ypYYDntVASX53q_D7Lrhdg@mail.gmail.com> <53BBA3EF.9040609@toshiba.co.jp> <43CF020C-1007-40A9-8F58-0B4F64672736@nominum.com> <3C9237BF-BF7F-43BF-8A12-35CB9BE6E7F1@gmail.com> <E39AD318-FF6E-44A3-A3C8-4321B86B65FA@nominum.com>
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: Sat, 19 Jul 2014 16:27:44 -0400
Message-ID: <7303.1405801664@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/RGDB29z0Rp8apF9thdANqHoJmyc
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: [Roll] [dhcwg] MPL config draft (Re: I-D Action: draft-ietf-roll-mpl-parameter-configuration-01.txt)
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: Sat, 19 Jul 2014 20:27:51 -0000

Ted Lemon <ted.lemon@nominum.com> wrote:
    >> Ted - what does "this" refer to?  MPL in general?

    > Using DHCP to push a big chunk of information about the state of a mesh
    > network seems like a suboptimal approach.  The fact that compression is
    > desired suggests that you are using the wrong tool for the job.

It's not state about the network, it's configuration parameters about the
(multicast) routing protocol.   Ideally, the parameters need to be the same
across the mesh (but we have validated that mismatches in certain directions
and within certain tolerances are acceptable; usually causing excess energy
use, rather than network in-operation),  but over time the operator will want
to tune the parameters to optimize energy.

As such we need a protocol that assigns lifetimes to parameters and
facilitates expiring old values.  DHCP seems ideal for this; it's also not
RPL specific, as MPL is not tied to RPL.


--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/