Re: [Roll] Last Call: <draft-ietf-roll-trickle-mcast-06.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard
Axel Colin de Verdière <axel-ietf@axelcdv.com> Sat, 08 February 2014 00:27 UTC
Return-Path: <axel-ietf@axelcdv.com>
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 260951A0522 for <roll@ietfa.amsl.com>; Fri, 7 Feb 2014 16:27:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level:
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 Nawf7mTCBgIV for <roll@ietfa.amsl.com>; Fri, 7 Feb 2014 16:27:28 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id 8D72D1A051A for <roll@ietf.org>; Fri, 7 Feb 2014 16:27:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 6FB311C02E2; Fri, 7 Feb 2014 16:27:28 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.1.47] (cha75-1-78-192-0-189.fbxo.proxad.net [78.192.0.189]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 41A881C0748; Fri, 7 Feb 2014 16:27:14 -0800 (PST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Axel Colin de Verdière <axel-ietf@axelcdv.com>
In-Reply-To: <0d753074c679b2f79f1ba4acb18cd7f3@xs4all.nl>
Date: Sat, 08 Feb 2014 01:26:50 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <001AF5D9-5760-42D5-8BA9-4F421B39ACDA@axelcdv.com>
References: <20140124201637.988.3372.idtracker@ietfa.amsl.com> <4C62FB50-C8E8-4CEA-BD42-B64076883379@gmail.com> <0d753074c679b2f79f1ba4acb18cd7f3@xs4all.nl>
To: consultancy@vanderstok.org, Routing Over Low power and Lossy networks <roll@ietf.org>
X-Mailer: Apple Mail (2.1827)
Subject: Re: [Roll] Last Call: <draft-ietf-roll-trickle-mcast-06.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard
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, 08 Feb 2014 00:27:30 -0000
Hello, I've reviewed the draft, and I have a couple comments/questions if that's not too late: - I don't see why MPL forwarders on the same link should have the same value for PROACTIVE_FORWARDING. It is now RECOMMENDED to make it so, but I don't see the rationale for this recommendation: on the opposite, I think it would allow some forwarders with less power restrictions to be more proactive than others. - Isn't there a risk that only specifying SEED_SET_ENTRY_LIFETIME without any kind of hysteresis mechanism lead to old Data messages being reinjected in the network? For example, if an MPL forwarder A resets its Control Message trickle timer with a seed (S) close to expiration, there is a risk that a neighbor forwarder that has expired that seed interprets the Control Message as A having new Data messages from seed S, thus resetting its timer for this seed and potentially retransmitting the corresponding Data message(s). - In section 9.2, it is unclear when the M flag should be cleared or set: why would it be arbitrarily cleared and not indicate whether or not this message's sequence number is the largest one received? Thank you, Axel Le 3 févr. 2014 à 11:23, peter van der Stok <stokcons@xs4all.nl> a écrit : > I've reviewed draft-ietf-roll-trickle-mcast-06.txt. The issues > raised during the WG last call concerning our applications, have been addressed adequately. > > peter van der stok > > Ralph Droms schreef op 2014-01-27 16:58: >> I've reviewed draft-ietf-roll-trickle-mcast-06.txt. The issues I >> raised during the WG last call have been addressed and, in my opinion, >> the document is now ready for publication. >> - Ralph >> On Jan 24, 2014, at 3:16 PM 1/24/14, The IESG <iesg-secretary@ietf.org> wrote: >>> The IESG has received a request from the Routing Over Low power and Lossy >>> networks WG (roll) to consider the following document: >>> - 'Multicast Protocol for Low power and Lossy Networks (MPL)' >>> <draft-ietf-roll-trickle-mcast-06.txt> as Proposed Standard >>> This is a second last call, the first one having been abandoned to send >>> the document back to the working group. But the latest revision addresses >>> comments that were received during the first last call. >>> The IESG plans to make a decision in the next few weeks, and solicits >>> final comments on this action. Please send substantive comments to the >>> ietf@ietf.org mailing lists by 2014-02-07. Exceptionally, comments may be >>> sent to iesg@ietf.org instead. In either case, please retain the >>> beginning of the Subject line to allow automated sorting. >>> Abstract >>> This document specifies the Multicast Protocol for Low power and >>> Lossy Networks (MPL) that provides IPv6 multicast forwarding in >>> constrained networks. MPL avoids the need to construct or maintain >>> any multicast forwarding topology, disseminating messages to all MPL >>> Forwarders in an MPL Domain. MPL uses the Trickle algorithm to >>> manage message transmissions for both control and data-plane >>> messages. Different Trickle parameter configurations allow MPL to >>> trade between dissemination latency and transmission efficiency. >>> The file can be obtained via >>> http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/ >>> IESG discussion can be tracked via >>> http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/ballot/ >>> The following IPR Declarations may be related to this I-D: >>> http://datatracker.ietf.org/ipr/1858/ >> _______________________________________________ >> 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
- [Roll] Last Call: <draft-ietf-roll-trickle-mcast-… The IESG
- Re: [Roll] Last Call: <draft-ietf-roll-trickle-mc… Ralph Droms
- Re: [Roll] Last Call: <draft-ietf-roll-trickle-mc… peter van der Stok
- Re: [Roll] Last Call: <draft-ietf-roll-trickle-mc… Axel Colin de Verdière
- Re: [Roll] Last Call: <draft-ietf-roll-trickle-mc… Adrian Farrel
- Re: [Roll] Last Call: <draft-ietf-roll-trickle-mc… Jonathan Hui (johui)
- Re: [Roll] Last Call: <draft-ietf-roll-trickle-mc… Kerry Lynn
- Re: [Roll] Last Call: <draft-ietf-roll-trickle-mc… Ines Robles
- Re: [Roll] Last Call: <draft-ietf-roll-trickle-mc… Axel Colin de Verdière
- Re: [Roll] Last Call: <draft-ietf-roll-trickle-mc… Jonathan Hui (johui)
- Re: [Roll] Last Call: <draft-ietf-roll-trickle-mc… Robert Cragie