Re: [Roll] last call for roll charter text.

Charlie Perkins <charles.perkins@earthlink.net> Fri, 30 September 2016 19:32 UTC

Return-Path: <charles.perkins@earthlink.net>
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 5787912B1E0 for <roll@ietfa.amsl.com>; Fri, 30 Sep 2016 12:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.036
X-Spam-Level:
X-Spam-Status: No, score=-5.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.316] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (384-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
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 2owifzfjSzyd for <roll@ietfa.amsl.com>; Fri, 30 Sep 2016 12:32:38 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EDA112B1B9 for <roll@ietf.org>; Fri, 30 Sep 2016 12:32:38 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Td6KYder7vDAmMKmFHNvbWGXEx8tEfXgLT+C1bc9gHPP6LB8RwZo/FV88W+JbtCc; h=Received:Subject:To:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1bq3Xh-0008OK-Dn; Fri, 30 Sep 2016 15:32:21 -0400
To: consultancy@vanderstok.org, Routing Over Low power and Lossy networks <roll@ietf.org>, emarobl <maria.ines.robles@ericsson.com>, Alvaro Retana <aretana@cisco.com>
References: <86972780d65c4f893678ee6963d89b7a@xs4all.nl>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <4dd822d3-af91-b72f-558d-00e574dbbab4@earthlink.net>
Date: Fri, 30 Sep 2016 12:32:19 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <86972780d65c4f893678ee6963d89b7a@xs4all.nl>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac719dd1cbdb52d858611516252aae9859e350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/UBsSwXtM7NuD09p2XkTUBsTx7YQ>
Subject: Re: [Roll] last call for roll charter text.
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: Fri, 30 Sep 2016 19:32:40 -0000

Hello folks,

I support this charter.  I think it is clear and worthwhile and achievable.

Regards,
Charlie P.


On 9/16/2016 6:23 AM, peter van der Stok wrote:
> Dear all,
>
> Below the text for the ROLL charter as discussed in Berlin and on the 
> mailing list.
> The last additions are the milestones based on the feedback of the 
> past months.
>
> Many thanks for all your contributions. The text is shorter and 
> clearer in my opinion.
>
> Please react to (approve) the text, and review the milestone dates 
> when they concern your work.
>
> End of call: Saturday October 1.
>
> Many thanks,
>
> Peter + Ines
>
> ____________________________________________________________________________________________________________________________________________________________________________ 
>
>
>
> Charter for ROLL Working Group
>
> Low power and Lossy Networks (LLNs ) 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.
>
> RFC7102 discusses ROLL specific aspects of LLNs, and RFC7228 provides 
> additional terminology for constrained devices.
>
> 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 Framework 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 networks and/or constrained nodes, such as 
> 6lo (Int) and lwig (Int) and CoRE (App). The working groups PiM (rtg), 
> BIER (rtg) and MANET (rtg) will be consulted when ROLL work can profit 
> from their results. The Working group will align with the 6man (Int) 
> WG 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).
>
> - Additional protocol elements to reduce packet size and the amount of 
> required routing states
>
> - Automatic selection of MPL forwarders to reduce message replication. 
> (coordinated with PiM wg)
>
> - Data models for RPL and MPL management (coordinated with netmod and 
> PiM wg)
>
> - Alternative Multicast algorithm see for example Bier forwarding. 
> (coordinated with PiM wg and relateds wg, e.g. BIER)
>
> - Methods to improve or correct the current RPL behavior and the other 
> protocols defined by the working group.
>
> - Alternative Routing mechanism for constrained environments see for 
> example AODV-RPL
>
>
> Milestones
>
> DATE                            Milestone
> September 2018            Recharter WG or close
> July 2018     Initial submission of a solution for 
> draft-jadhav-roll-no-path-dao-ps to IESG
> November 2017     Initial submission of draft-satish-roll-aodv-rpl to 
> IESG
> November 2017     Initial submission of 
> draft-gundogan-roll-dis-modifications to IESG
> July 2017     Initial submission of draft-bergmann-bier-ccast to IESG
> July 2017         Initial submission of 
> draft-vanderstok-roll-mpl-forw-select to IESG
> March 2017     Initial submission of draft-vanderstok-roll-mpl-yang to 
> IESG
> March 2017     Initial submission of draft-thubert-roll-dao-projection 
> to IESG
> November 2016              Initial Submission of the draft about when 
> to use RFC6553, RFC6554, and IPv6-in-IPv6 encapsulation 
> Draft-ietf-roll-useofrplinfo to the IESG.
> November 2016            IESG Evaluation of draft-roll-routing-dispatch.
>