Re: [Roll] Request for Comments ROLL Charter - version 06

Ines Robles <mariainesrobles@googlemail.com> Mon, 18 July 2016 18:24 UTC

Return-Path: <mariainesrobles@googlemail.com>
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 85F5212B036 for <roll@ietfa.amsl.com>; Mon, 18 Jul 2016 11:24:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.689
X-Spam-Level:
X-Spam-Status: No, score=-2.689 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=googlemail.com
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 aGlzBQirPCFR for <roll@ietfa.amsl.com>; Mon, 18 Jul 2016 11:23:58 -0700 (PDT)
Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 529EC12B016 for <roll@ietf.org>; Mon, 18 Jul 2016 11:23:58 -0700 (PDT)
Received: by mail-vk0-x236.google.com with SMTP id w127so192057358vkh.2 for <roll@ietf.org>; Mon, 18 Jul 2016 11:23:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=zAdcZFRPxwJMn1qLmfZCkbKYVzaJZZ+VsM60miLtw60=; b=toA9dFH6AJyktADLVP7LZre+gy5w7j9uZ1qigIxlM5pv6V6IiK4Auo3vR0RZAdw1Jh nNjCvcJEO+QKEvzIbJdfOYc2wN1YSGbq1M6pm8WH0aALhV2KsOsYuF5XXXJ1CIE/rFBR Ce92x4+fc4XN431klP/m1uC6NaksrU5zaQgySmeqk6yRtyHFRn0XNEkUowraQ1kGUb4p 4TKndygZU9jAvdU21LDUQpoxaloOKLJkJRKUVoq5tXzJuhOE3Kp4VfOCisERHx1eNByN oXR1/mk8TswgHmT4jsxKlNgVQGh2synkb4+zZwZ17BPlvEh0H69xHjnKdb9JHBvchZSQ DrKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=zAdcZFRPxwJMn1qLmfZCkbKYVzaJZZ+VsM60miLtw60=; b=kR+5Si/yUX8WRdo5aC8yC4T+A/4KKeAYGrzwJ1WGFxkuFrLtOeLVYENVAnsjWuVMdH TIOYvbZHJ/HItmS/OuOIxs0/Po7U+IY6+tvIx2whKapZyeBGF1hi06n900SwVbNhACqg YLUZD0Eoj3hKj1FRxawQ/8mZmYQXaT2wrAojrSgH7pWN+n/NKq5GqiqmIGCkNLK0EXZ9 AQI8/I9Gpq39K6zSitiOJTeSDId1J8BnApK0gHSPDntmrY5yIx7TI5zq/VwerrcPq0Gi elzKcd5Bs0EmUF1zuLokY4klomrm1mn8CZSGh7qa9kojgEcfLK0iv4Vip544REJwrVrO B72g==
X-Gm-Message-State: ALyK8tI0MSa+UKG4S6OLrBxk6V+PmpzUHmS6wV8LsxgrOrJLLtEV8UT4TuBJ77i17ujSr1bYbczUkwyopeMMwQ==
X-Received: by 10.176.2.238 with SMTP id 101mr18699794uah.5.1468866237203; Mon, 18 Jul 2016 11:23:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.36.241 with HTTP; Mon, 18 Jul 2016 11:23:56 -0700 (PDT)
In-Reply-To: <CADJ9OA9cbZ2eTu8cYNu7Vrsm0HfB=S+ogc+=WUiP-_LAENe+gA@mail.gmail.com>
References: <CAP+sJUcs-JACpMQ+JZVXSqDK5X8gkLB9AEXho9JnmWpdt14s2w@mail.gmail.com> <CADJ9OA9cbZ2eTu8cYNu7Vrsm0HfB=S+ogc+=WUiP-_LAENe+gA@mail.gmail.com>
From: Ines Robles <mariainesrobles@googlemail.com>
Date: Mon, 18 Jul 2016 21:23:56 +0300
Message-ID: <CAP+sJUcXEoVz8AoTzUndWqLpfrxEdrOJGDmq7ZZckZAmJ1o4Ew@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary=001a113cf1904a8aa10537ed12ee
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/oFTOc-5PzVzeUBzCGQbTLkJALNQ>
Subject: Re: [Roll] Request for Comments ROLL Charter - version 06
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2016 18:24:01 -0000

Ok, Thank you Thomas! :-)

2016-07-18 20:52 GMT+03:00 Thomas Watteyne <thomas.watteyne@inria.fr>;:

> Ines, Peter,
>
> Looks good to me. Two typos: "groupThe " and an etra "two" in the items.
> T
>
> On Mon, Jul 18, 2016 at 7:47 PM, Ines Robles <
> mariainesrobles@googlemail.com>; wrote:
>
>> Dear all,
>>
>> Please find the new charter. We have reduced the history part, removed
>> redundant text and updated work items.
>>
>> Please comments
>>
>> Thank you very much,
>>
>> Peter and Ines
>>
>>
>> ////////////////////////////////////////////////////////////////////////////////////////////////////////
>>
>> CHARTER PROPOSAL:
>>
>> Charter for ROLL Working Group
>>
>> Low power and Lossy Networks (LLNs ) [RFC7102] [RFC7228] are made up of
>> many embedded devices with limited power, memory, and processing resources.
>> They are interconnected by a variety of links, such as IEEE 802.15.4,
>> Bluetooth, Low Power WiFi, wired or other low power PLC (Powerline
>> Communication) links. LLNs are transitioning to an end-to-end IP-based
>> solution to avoid the problem of non-interoperable networks interconnected
>> by protocol translation gateways and proxies.
>>
>> Generally speaking, LLNs are characterized as follows, but not limited to:
>>
>>
>>    -
>>
>>    LLNs operate with a hard, very small bound on state.
>>    -
>>
>>    In most cases, LLN optimize for saving energy by using small packet
>>    headers and reduce amount of control packets.
>>    -
>>
>>    Typical traffic patterns are not simply unicast flows (e.g. in some
>>    cases most if not all traffic can be point to multipoint).
>>    -
>>
>>    In most cases, LLNs will be employed over link layers with restricted
>>    frame-sizes and low bit rates, thus a routing protocol for LLNs should be
>>    specifically adapted for such link layers.
>>    -
>>
>>    LLN routing protocols have to be very careful when trading off
>>    efficiency for generality; since LLN nodes do not have resources to waste.
>>    -
>>
>>    These specific properties cause LLNs to have specific routing
>>    requirements.
>>
>>
>> RFC 5548, 5673, 5826, and 5876 describe the requirements for LLNs from
>> several application perspectives.
>>
>> The Working Group has focused on routing solutions for the areas:
>> connected home, building and urban sensor networks. It has developed a
>>  protocol set that takes into consideration various aspects including high
>> reliability in the presence of time varying loss characteristics and
>> connectivity while permitting low-power operation with very modest memory
>> and CPU pressure in networks potentially comprising a very large number
>> (several thousands) of nodes.
>>
>> The Working Group continues to focus on routing issues for LLN and to
>> maintain, improve and streamline the protocols developed by the working
>> group, including RPL and MPL.
>>
>> ROLL will coordinate closely with the working groups in other areas that
>> focus on constrained node networks, such as 6lo (Internet) and CoRE (APP).
>> behavior and the other protocols defined by the working groupThe Working
>> group will align with the 6man and BIER WGs when needed.
>>
>> Work Items are:
>>
>> - Guidance in using RFC6553, RFC6554, and IPv6-in-IPv6 encapsulation.
>> The WGLC on this work will be shared with 6lo.
>>
>> - Compression of  RFC6553, RFC6554, and IP headers in the 6LoWPAN
>> adaptation layer context. (coordinated with 6lo WG).
>>
>> - Automatic selection of MPL forwarders to reduce message replication
>>
>> - Data models for RPL and MPL management (coordinated with netmod wg)
>>
>> - Alternative Multicast algorithm such as BIER forwarding.
>> two
>>
>> - Methods to improve or correct the current RPL control messages
>> behaviour, e.g. DIS and No-Path DAO.
>>
>> Milestones
>>
>> DATE                            Milestone
>>
>> September 2017            Recharter WG or close
>>
>> March 2017           Initial submission of draft about YANG RPL model to
>> IESG
>>
>> January 2017         Initial submission of draft about MPL selection to
>> IESG
>>
>> November 2016        Initial submission of draft about Bier Multicast to
>> IESG
>>
>> October 2016         Submit draft about YANG MPL model to IESG
>>
>> August 2016          Initial Submission of the draft about when to use
>> RFC6553, RFC6554, and IPv6-in-IPv6 encapsulation
>> Draft-ietf-roll-useofrplinfo to the IESG.
>>
>> May 2016             Initial submission of the draft about how to
>> compress RFC6553, RFC6554, and IP headers in the 6LoWPAN adaptation layer
>> context.  to the IESG. draft-ietf-roll-routing-dispatch
>> November 2016        Initial Submission of the No-Path DAO Problem
>> Statement to the IESG
>>
>> _______________________________________________
>> Roll mailing list
>> Roll@ietf.org
>> https://www.ietf.org/mailman/listinfo/roll
>>
>>
>
>
> --
> _______________________________________
>
> Thomas Watteyne, PhD
> Research Scientist & Innovator, Inria
> Sr Networking Design Eng, Linear Tech
> Founder & co-lead, UC Berkeley OpenWSN
> Co-chair, IETF 6TiSCH
>
> www.thomaswatteyne.com
> _______________________________________
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>
>