Re: [Roll] WGLC - Working Group Last Call - draft-ietf-roll-trickle-mcast-05

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 16 September 2013 14:59 UTC

Return-Path: <mcr@sandelman.ca>
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 1B58011E8279 for <roll@ietfa.amsl.com>; Mon, 16 Sep 2013 07:59:36 -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 vIkq1PzXClD8 for <roll@ietfa.amsl.com>; Mon, 16 Sep 2013 07:59:35 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 510B811E8110 for <roll@ietf.org>; Mon, 16 Sep 2013 07:59:33 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 90A932016F for <roll@ietf.org>; Mon, 16 Sep 2013 12:08:06 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 5B5B263B18; Mon, 16 Sep 2013 10:59:14 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 49E65636C7 for <roll@ietf.org>; Mon, 16 Sep 2013 10:59:14 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-Reply-To: <CABOxzu1BLtfkWS7Ya1MQ5bLgpqebXhaDtrRY39OYy53EBcw9cQ@mail.gmail.com>
References: <CABOxzu2H3okQF=ivauG7NfkhF2RDPeyskDaa-MnTUuS6zCUCXQ@mail.gmail.com> <CE58AC02.23779%d.sturek@att.net> <CABOxzu1BLtfkWS7Ya1MQ5bLgpqebXhaDtrRY39OYy53EBcw9cQ@mail.gmail.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: Mon, 16 Sep 2013 10:59:14 -0400
Message-ID: <9392.1379343554@sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [Roll] WGLC - Working Group Last Call - draft-ietf-roll-trickle-mcast-05
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: Mon, 16 Sep 2013 14:59:36 -0000

Kerry Lynn <kerlyn@ieee.org> wrote:
    don>>           I believe it is requirement that all devices in a given
    don>> MPL Domain MUST agree on a common value for IMIN, IMAX and k.  In
    don>> terms of a default, we can certainly create such values applicable
    don>> to given deployment topology and an assumed messaging profile but I
    don>> really think some work should go into an applicability statement
    don>> that would provide additional guidance on how to tune these
    don>> values.  I think I mentioned this before but we did (in ZigBee IP)
    don>> create a 30 node, 3 hop network supporting a ROLL RPL instance,
    don>> instrumented all devices, created a single multicast message and
    don>> measured how many devices in the network saw at least a single copy
    don>> of the transmission using various settings for IMIN, IMAX and k.  A
    don>> process similar to this (with knowledge of the topology and
    don>> messaging profile) is needed for tuning these values in a real
    don>> deployment setting.

    Kerry> ACK.  Thanks for your explanations.

With this, are your questions resolved, or are there further text changes
requested?

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