Re: [Roll] last call for roll charter text.
AbdurRashidSangi <rashid.sangi@huawei.com> Thu, 22 September 2016 09:47 UTC
Return-Path: <rashid.sangi@huawei.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 4FF4D12B875 for <roll@ietfa.amsl.com>; Thu, 22 Sep 2016 02:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.537
X-Spam-Level:
X-Spam-Status: No, score=-6.537 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] 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 gzZIGan4iJr4 for <roll@ietfa.amsl.com>; Thu, 22 Sep 2016 02:47:55 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57E2012D838 for <roll@ietf.org>; Thu, 22 Sep 2016 02:47:55 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CRS34596; Thu, 22 Sep 2016 09:47:52 +0000 (GMT)
Received: from SZXEMI411-HUB.china.huawei.com (10.86.210.34) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 22 Sep 2016 10:47:51 +0100
Received: from SZXEMI505-MBS.china.huawei.com ([169.254.4.169]) by szxemi411-hub.china.huawei.com ([10.86.210.34]) with mapi id 14.03.0235.001; Thu, 22 Sep 2016 17:47:45 +0800
From: AbdurRashidSangi <rashid.sangi@huawei.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] last call for roll charter text.
Thread-Index: AQHSEB4mCIXcdp0dOU2kAX1SGwE5UKCFTABA
Date: Thu, 22 Sep 2016 09:47:45 +0000
Message-ID: <C3DD54213F5261438F5CE46038658EE3208006C2@SZXEMI505-MBS.china.huawei.com>
References: <86972780d65c4f893678ee6963d89b7a@xs4all.nl>
In-Reply-To: <86972780d65c4f893678ee6963d89b7a@xs4all.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.151.40]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.57E3A8C9.00CC, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.4.169, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: ee8a0830b18e211d647b8dc15433ae17
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/6EfuHVtaxL30WRsxFFOxDask12o>
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: Thu, 22 Sep 2016 09:47:58 -0000
Hi Peter & Ines, I support the charter. Also agree the charter is clear and concise. Regards, Rashid Sangi. Huawei, Beijing. > -----Original Message----- > From: Roll [mailto:roll-bounces@ietf.org] On Behalf Of peter van der > Stok > Sent: 2016年9月16日 21:24 > To: Roll; emarobl; Alvaro Retana > Subject: [Roll] last call for roll charter text. > > 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. > > -- > Peter van der Stok > vanderstok consultancy > mailto: consultancy@vanderstok.org > www: www.vanderstok.org > tel NL: +31(0)492474673 F: +33(0)966015248 > > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll
- [Roll] last call for roll charter text. peter van der Stok
- Re: [Roll] last call for roll charter text. Pascal Thubert (pthubert)
- Re: [Roll] last call for roll charter text. Mingui Zhang
- Re: [Roll] last call for roll charter text. Rahul Jadhav
- Re: [Roll] last call for roll charter text. Prof. Diego Dujovne
- Re: [Roll] last call for roll charter text. satish anamalamudi
- Re: [Roll] last call for roll charter text. Emmanuel Baccelli
- Re: [Roll] last call for roll charter text. Xavier Vilajosana
- Re: [Roll] last call for roll charter text. Pascal Thubert (pthubert)
- Re: [Roll] last call for roll charter text. SYED MUHAMMAD SAJJAD
- Re: [Roll] last call for roll charter text. AbdurRashidSangi
- Re: [Roll] last call for roll charter text. Charlie Perkins