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

Thomas Watteyne <thomas.watteyne@inria.fr> Mon, 18 July 2016 17:52 UTC

Return-Path: <thomas.watteyne@inria.fr>
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 8202B12D8B5 for <roll@ietfa.amsl.com>; Mon, 18 Jul 2016 10:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.176
X-Spam-Level:
X-Spam-Status: No, score=-8.176 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.287, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=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 L7t6vS-mzuGF for <roll@ietfa.amsl.com>; Mon, 18 Jul 2016 10:52:53 -0700 (PDT)
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E79512DB2D for <roll@ietf.org>; Mon, 18 Jul 2016 10:52:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.28,385,1464645600"; d="scan'208,217";a="185147615"
Received: from mail-lf0-f52.google.com ([209.85.215.52]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 18 Jul 2016 19:52:50 +0200
Received: by mail-lf0-f52.google.com with SMTP id l69so80341083lfg.1 for <roll@ietf.org>; Mon, 18 Jul 2016 10:52:50 -0700 (PDT)
X-Gm-Message-State: ALyK8tIsGkZUmJuZZXeYnV8a5Ci/eGoSA/5AuUEzg4cPrHAhw93Eg3TPdIYDrcK5w73+VCo5XMlzQqGUg7rBXQ==
X-Received: by 10.25.155.149 with SMTP id d143mr9682938lfe.121.1468864370093; Mon, 18 Jul 2016 10:52:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.208.9 with HTTP; Mon, 18 Jul 2016 10:52:30 -0700 (PDT)
In-Reply-To: <CAP+sJUcs-JACpMQ+JZVXSqDK5X8gkLB9AEXho9JnmWpdt14s2w@mail.gmail.com>
References: <CAP+sJUcs-JACpMQ+JZVXSqDK5X8gkLB9AEXho9JnmWpdt14s2w@mail.gmail.com>
From: Thomas Watteyne <thomas.watteyne@inria.fr>
Date: Mon, 18 Jul 2016 19:52:30 +0200
X-Gmail-Original-Message-ID: <CADJ9OA9cbZ2eTu8cYNu7Vrsm0HfB=S+ogc+=WUiP-_LAENe+gA@mail.gmail.com>
Message-ID: <CADJ9OA9cbZ2eTu8cYNu7Vrsm0HfB=S+ogc+=WUiP-_LAENe+gA@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary=001a11401fba00b5fc0537eca330
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/8JCi_KcpOvU6PKMH8h5y3rcCHb0>
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 17:52:56 -0000

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
_______________________________________