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

"Pascal Thubert (pthubert)" <> Mon, 19 September 2016 12:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 88ABA127735 for <>; Mon, 19 Sep 2016 05:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -16.836
X-Spam-Status: No, score=-16.836 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6_g_BNmDFb4C for <>; Mon, 19 Sep 2016 05:34:51 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A12C512B390 for <>; Mon, 19 Sep 2016 05:34:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=27718; q=dns/txt; s=iport; t=1474288469; x=1475498069; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=wW2l5dAibIaaYAXZdPrZPxEQCXBNBuTJE5sVTkj0RlU=; b=ZIWmDMVU7u2b1cqHtY/MEfyIAJy6HDRLeFV83IbsxDtWJS//UaFgHBSx +KcbFCoBdFPeURtdEQsNMo+zvkGqE2eR/ybZgjJj/C0Hw7rnYdnP12+Uw VSx0I43lDsvhqngoMZAAOBBE4c48ahsXjPWE8ScwJk56wkWnRkmauzL5k U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.30,361,1470700800"; d="scan'208,217";a="150547196"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Sep 2016 12:34:03 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id u8JCY3ji011740 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <>; Mon, 19 Sep 2016 12:34:03 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 19 Sep 2016 07:34:02 -0500
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Mon, 19 Sep 2016 07:34:02 -0500
From: "Pascal Thubert (pthubert)" <>
To: Routing Over Low power and Lossy networks <>
Thread-Topic: [Roll] last call for roll charter text.
Thread-Index: AQHSEB4ktJnDPx/U2E66J28DPoFPdaCAuCeAgAA2d4D//9SPkA==
Date: Mon, 19 Sep 2016 12:33:34 +0000
Deferred-Delivery: Mon, 19 Sep 2016 12:32:45 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_5392cc5323e74a42b4784e15b701e942XCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Roll] last call for roll charter text.
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <>
List-Id: Routing Over Low power and Lossy networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 19 Sep 2016 12:34:54 -0000

Hello Emmanuel :

I think that the last item

Alternative Routing mechanism for constrained environments see for example AODV-RPL

Is about that goal,


From: Roll [] On Behalf Of Emmanuel Baccelli
Sent: lundi 19 septembre 2016 12:07
To: Routing Over Low power and Lossy networks <>;
Subject: Re: [Roll] last call for roll charter text.

Hi everyone,
I also support the charter.
A comment: should we consider mentioning explicitly the standards-track version of the P2P-RPL, as suggested by Pascal during the meeting in Berlin?

On Mon, Sep 19, 2016 at 8:51 AM, satish anamalamudi <<>> wrote:
Hello everyone,

I support the current charter and proposed milestones.

With Regards,

On Fri, Sep 16, 2016 at 6:53 PM, 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


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.

Peter van der Stok
vanderstok consultancy
tel NL: +31(0)492474673<tel:%2B31%280%29492474673>     F: +33(0)966015248<tel:%2B33%280%29966015248>

Roll mailing list<>


With Regards,
Dr. Satish Anamalamudi, PhD.,
Research Engineer,
Huawei Networking Research Laboratory,
Beijing, China.

Roll mailing list<>