Re: [Roll] New proposed charter

Abdussalam Baryun <abdussalambaryun@gmail.com> Fri, 11 December 2015 18:12 UTC

Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D63091A92F1 for <roll@ietfa.amsl.com>; Fri, 11 Dec 2015 10:12:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001] autolearn=ham
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 sdhek1yBpvhp for <roll@ietfa.amsl.com>; Fri, 11 Dec 2015 10:12:40 -0800 (PST)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (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 A3E8E1A92EB for <roll@ietf.org>; Fri, 11 Dec 2015 10:12:40 -0800 (PST)
Received: by qgcc31 with SMTP id c31so203717587qgc.3 for <roll@ietf.org>; Fri, 11 Dec 2015 10:12:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=aKi0qfGbXhABwW21s76OdmX2uJm9EwuyU2RLXfIhqfg=; b=Gvhe5eHVU/75LheRLfA7mlnVh/uSC2sb8oydZp004aPSO3sQk+OgqqW7xDGYKLhI2s MoQX2dOWc/sGibe71AZPAlOnQQlkEgIyy9FyC3lyBpzrHQXEaZeNqeYtacqS+Xl2DXld UlOfwqioYUk/tzb5wlLvYp0OBFvzePQWZvGSAjy52yy351ZBwGLg5MP4s3rW4IXzTn76 4OLb+0n7zm3jRoJ75Zg5/GOfMKz3l+nrvlV06rx7FXrnEcK9RAGGiYVist13+edFsdjR vfXXa70BeB1frmJpHS3wvuXp/ozF7eWhQiU+7+lWNcx2SDlU0f4l0MNrZVUdu+ByP0kG c4og==
MIME-Version: 1.0
X-Received: by 10.141.2.86 with SMTP id e83mr17034939qhd.64.1449857559808; Fri, 11 Dec 2015 10:12:39 -0800 (PST)
Received: by 10.140.95.22 with HTTP; Fri, 11 Dec 2015 10:12:39 -0800 (PST)
In-Reply-To: <d176b79c1f4b46f3ae144bd03c5ec94e@XCH-RCD-001.cisco.com>
References: <CAP+sJUfYLXN7z5b3UtXbs9a_JQjCfBpJGrihQru+k8wTFsOTbQ@mail.gmail.com> <d176b79c1f4b46f3ae144bd03c5ec94e@XCH-RCD-001.cisco.com>
Date: Fri, 11 Dec 2015 20:12:39 +0200
Message-ID: <CADnDZ88OvB1u5cPyUZz=TLQ4iYXMaq1wqq3Z1-i7Q9rUEo12GQ@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary="001a113a420ed3de8a0526a34451"
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/gsqe6bJqtbA7oGuQ8YXgT88Ihmg>
Subject: Re: [Roll] New proposed charter
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Dec 2015 18:12:43 -0000

Dear All,

I think  we should not look only into enhancement of RPL but looking into
one new proposed protocol (experimental). My question is why we only have
one standard protocol for ROLL? we may need to look into different/new
scenarios now, so YES we chosen the one routing RPL as a general purpose
protocol for ROLL, now we need to do maintain RPL with its future work, but
we also can now see special cases where we need new protocols for ROLL. We
noticed that ROLL is more a special case of other routing protocols in the
internet but still we didn't go for experimental drafts that cover special
cases and implementations.

AB
University of Tripoli,


On Fri, Dec 11, 2015 at 7:47 PM, Pascal Thubert (pthubert) <
pthubert@cisco.com> wrote:

> Hello Ines
>
>
>
> I like the proposal because it is open enough to include the various items
> we discussed recently. Great work!
>
>
>
> I’m in  full support for this proposal as you may have guessed,
>
>
>
> Pascal
>
>
>
> *From:* Roll [mailto:roll-bounces@ietf.org] *On Behalf Of *Ines Robles
> *Sent:* vendredi 11 décembre 2015 16:01
> *To:* roll <roll@ietf.org>
> *Cc:* Michael Richardson <mcr+ietf@sandelman.ca>
> *Subject:* [Roll] New proposed charter
>
>
>
>
>
> Dear all:
>
>
>
> We propose the following text to replace the current (much longer) charter
> [https://datatracker.ietf.org/wg/roll/charter/], please let us know your
> opinion about this.
>
>
>
> If you think that other specific topic should be included, please let us
> know as well.
>
>
>
> Charter proposed might be:
>
>
>
> RFC 6550 was published in 2012, and has seen several successful
> deployments.
>
> Over time, additional issues have come up, including issues in the data
> plane of when to use IPinIP headers, and how to compress them, as well as
> the standardization of a mixed storing/non-storing mechanism.
>
> The WG is chartered to look at enhancements and maintenance to the RPL
> protocol, with the aim of eventually revising and advancing RFC 6550 to
> Internet Standard.
>
>
>
> Thank you very much,
>
>
> Michael and Ines.
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>
>