[Roll] Fwd: New Version Notification for draft-vanderstok-roll-mcreq-02.txt
peter van der Stok <stokcons@xs4all.nl> Sat, 14 July 2012 13:26 UTC
Return-Path: <stokcons@xs4all.nl>
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 D843621F870B for <roll@ietfa.amsl.com>; Sat, 14 Jul 2012 06:26:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.154
X-Spam-Level:
X-Spam-Status: No, score=-0.154 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 elW1nKarSbYr for <roll@ietfa.amsl.com>; Sat, 14 Jul 2012 06:26:23 -0700 (PDT)
Received: from smtp-vbr9.xs4all.nl (smtp-vbr9.xs4all.nl [194.109.24.29]) by ietfa.amsl.com (Postfix) with ESMTP id E683721F86FA for <roll@ietf.org>; Sat, 14 Jul 2012 06:26:22 -0700 (PDT)
Received: from roundcube.xs4all.nl (roundcube1.xs4all.net [194.109.20.195]) by smtp-vbr9.xs4all.nl (8.13.8/8.13.8) with ESMTP id q6EDQUea088940 for <roll@ietf.org>; Sat, 14 Jul 2012 15:26:30 +0200 (CEST) (envelope-from stokcons@xs4all.nl)
Received: from AMontpellier-556-1-306-50.w81-251.abo.wanadoo.fr ([81.251.50.50]) by roundcube.xs4all.nl with HTTP (HTTP/1.1 POST); Sat, 14 Jul 2012 15:26:30 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Sat, 14 Jul 2012 15:26:30 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: roll@ietf.org
Organization: vanderstok consultancy
Mail-Reply-To: <consultancy@vanderstok.org>
Message-ID: <2dec670ff1a72412ba6a7800ee8d95b7@xs4all.nl>
X-Sender: stokcons@xs4all.nl (Ki6Vt3DWZ8ea6UGjpmzizFqMlwHTR6In)
User-Agent: XS4ALL Webmail
X-Virus-Scanned: by XS4ALL Virus Scanner
Subject: [Roll] Fwd: New Version Notification for draft-vanderstok-roll-mcreq-02.txt
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: consultancy@vanderstok.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, 14 Jul 2012 13:26:24 -0000
-------- Originele bericht -------- Onderwerp: New Version Notification for draft-vanderstok-roll-mcreq-02.txt Datum: 2012-07-14 15:20 Afzender: internet-drafts@ietf.org Ontvanger: consultancy@vanderstok.org Kopie: armand.lelkens@philips.com, esko.dijk@philips.com A new version of I-D, draft-vanderstok-roll-mcreq-02.txt has been successfully submitted by Peter van der Stok and posted to the IETF repository. Dear roll wg, We have submitted a draft summarizing our experiences with and recommendations for the trickle Multicast algorithm. One of our main concerns is the timeliness aspects of TRickle multicast , and we are confident that given the network configurations that we expect we can deploy trickle multicast for building control More information in the draft. Greetings, peter van der stok Filename: draft-vanderstok-roll-mcreq Revision: 02 Title: Multicast requirements for control over LLN Creation date: 2012-07-11 WG ID: Individual Submission Number of pages: 15 URL: http://www.ietf.org/internet-drafts/draft-vanderstok-roll-mcreq-02.txt Status: http://datatracker.ietf.org/doc/draft-vanderstok-roll-mcreq Htmlized: http://tools.ietf.org/html/draft-vanderstok-roll-mcreq-02 Diff: http://tools.ietf.org/rfcdiff?url2=draft-vanderstok-roll-mcreq-02 Abstract: This is a working document intended to focus discussion on requirements for multicast in Low-power and Lossy Networks in the area of M2M communication for control applications. The Trickle algorithm, which uses random re-broadcasting to assure that messages arrive at all destinations, has been proposed in the Trickle Multicast Forwarding ROLL WG draft as the basis for a multicast routing protocol. In this draft additional requirements on multicast routing are presented, such as timeliness, motivated by building control. Random re-broadcasting and timeliness can be difficult to reconcile. This draft presents some simulation results in typical control settings which show that achieving latencies below 400 ms is feasible with Trickle. Recommendations are proposed for the current Trickle Multicast Forwarding draft to achieve optimal performance and meet the stated requirements. The IETF Secretariat
- [Roll] Fwd: New Version Notification for draft-va… peter van der Stok