Re: [Roll] New proposed charter

Abdussalam Baryun <abdussalambaryun@gmail.com> Sat, 12 December 2015 22:22 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 ED6321A90EA for <roll@ietfa.amsl.com>; Sat, 12 Dec 2015 14:22:04 -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 BnbdcpU76ucX for <roll@ietfa.amsl.com>; Sat, 12 Dec 2015 14:22:03 -0800 (PST)
Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (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 4D64B1A90E7 for <roll@ietf.org>; Sat, 12 Dec 2015 14:22:03 -0800 (PST)
Received: by qgz52 with SMTP id 52so37378898qgz.1 for <roll@ietf.org>; Sat, 12 Dec 2015 14:22:02 -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=XBMKV8QBmkZw1M5f2vIPk/5Rppf9svisIyiWTdAidrE=; b=qpoj2BKN7Gk3H6uGFmnZDqMP+9Nw0MHqlpiBNmghnOfViLvHc1yOcgIrHv7M3wpeBX Bnc+Am1tN2+MiPYFef7TSrrsjfzOIN2XSMU2ef2ZASjcgwMCAyVc4yb4EaWpapBQtQX2 0jKrYNvtSrVm8VaMNZd7CYHJHrPeHKac2DcXysMnKKjm0+pDeGBkSE55/SGxJFvTx8kT xvyhpOVWf0tCVWGYdMytaP8p61RtIVnrKvy9EvdDoTD99Di0CL4GKJDmUEkPhKsUuVem HwwFlQWc3KjQkm+lZpokTtqby37iStd0k4LUa3111zQ//UczfciVzGwaKE4klgu6hRCX Q8OQ==
MIME-Version: 1.0
X-Received: by 10.140.96.230 with SMTP id k93mr32410136qge.13.1449958922440; Sat, 12 Dec 2015 14:22:02 -0800 (PST)
Received: by 10.140.95.22 with HTTP; Sat, 12 Dec 2015 14:22:02 -0800 (PST)
In-Reply-To: <12487.1449869206@obiwan.sandelman.ca>
References: <CAP+sJUfYLXN7z5b3UtXbs9a_JQjCfBpJGrihQru+k8wTFsOTbQ@mail.gmail.com> <d176b79c1f4b46f3ae144bd03c5ec94e@XCH-RCD-001.cisco.com> <CADnDZ88OvB1u5cPyUZz=TLQ4iYXMaq1wqq3Z1-i7Q9rUEo12GQ@mail.gmail.com> <12487.1449869206@obiwan.sandelman.ca>
Date: Sun, 13 Dec 2015 00:22:02 +0200
Message-ID: <CADnDZ88=bcP7VHghkdhaJJNkJrZ982HRLc3GK2ee=AgU7BZt0Q@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="001a113a4aa082e0100526badefe"
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/l6zB7-B-D95_iRVbIStJYS0761Q>
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: Sat, 12 Dec 2015 22:22:05 -0000

My previous message was my reply to the request of the chair that welcome
opinions and new recharter, so I did not understand that there are things
out of scope.

On Fri, Dec 11, 2015 at 11:26 PM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> If you have new use cases that you believe can not be satisfied by RPL,
> then
> you should detail them in an ID.
>

There were discussions about use cases before, but I just need to discuss
first, then see if we can do ID. No protocol can satisfy all use cases.

So we can discuss first, and then decide if their is availability,

>
> This is exactly how RPL-P2P came about.
>

Yes there was discussions, some may prefer to do it off-line, and then
write IDs,

>
> If extensions (whether experimental or not), can address the need then they
> would be in scope for this WG.


Ok, but that is why I am replying to the proposing call, so I am discussing
that issue and others,


>   If an entirely new routing protocol is
> needed, then that would be out of scope and would be up to the routing Area
> Directors to decide where that work would be done.
>

I don't think it is out of scope.

Participants are the ones to decide/discuss where new protocols go (don't
forget directors can participate without hats), and directors only have the
final decision after our discussions. Therefore, I hope we discuss
recharter without initial directions/force.

 So I think that new proposal for the recharter should make the option open
for new one experimental ROLL-protocol, to encourage new ideas.

AB