Re: [Roll] New proposed charter

Robert Cragie <robert.cragie@gridmerge.com> Fri, 18 December 2015 17:55 UTC

Return-Path: <robert.cragie@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 9D97F1B37AA for <roll@ietfa.amsl.com>; Fri, 18 Dec 2015 09:55:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 BXnaT9_Vq1vS for <roll@ietfa.amsl.com>; Fri, 18 Dec 2015 09:55:29 -0800 (PST)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (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 556F81B37AC for <roll@ietf.org>; Fri, 18 Dec 2015 09:55:29 -0800 (PST)
Received: by mail-lb0-x233.google.com with SMTP id yq9so48436917lbb.3 for <roll@ietf.org>; Fri, 18 Dec 2015 09:55:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=glSex0bpVs5ILf+gxkXIMjozBt4DXWAS7Jcr3HTa6N4=; b=FJckvzAFPpPVBQ71gfXkFn/9P1XyBwBFHz+/UdSMGP9+rgddTHurDeoTDIOjH/hIeO umxIlf72TlmkkkE1E9Cu22RcmP1jgZ0MLD55RGaCabwuIkCDUCrxTyPk7bdb2TwtJWS1 Jt2em4VbJXO+syWhPlhuNiB73iHp4a6gJSc8MU4g/gluljTnIiB8SnCaY4zaTAkOJ1J7 5fgpJTKUh5xn6QdeY4TnWLxPkFcJyGNNsaFN+0sEMFnrav4X5zIGxZrzBm/2TxyTdNlJ WaXWSQy0IjsbmG/hdntgTv46UXNpqFGzQujK2f+IiyQ6Kj4B2kooVAZH89V1CO4I7Qq/ W8fA==
MIME-Version: 1.0
X-Received: by 10.112.137.66 with SMTP id qg2mr1924711lbb.41.1450461327457; Fri, 18 Dec 2015 09:55:27 -0800 (PST)
Sender: robert.cragie@gmail.com
Received: by 10.25.156.75 with HTTP; Fri, 18 Dec 2015 09:55:27 -0800 (PST)
In-Reply-To: <5563.1450458340@obiwan.sandelman.ca>
References: <CAP+sJUfYLXN7z5b3UtXbs9a_JQjCfBpJGrihQru+k8wTFsOTbQ@mail.gmail.com> <1676228924.7990.1449851481478.JavaMail.vpopmail@atl4oxapp102.mgt.hosting.qts.netsol.com> <11866.1449869031@obiwan.sandelman.ca> <1BB1E83B-243B-41EF-8898-EB372D289C27@amalfisystems.com> <23010.1450031144@obiwan.sandelman.ca> <687E3051-78DB-4425-9261-53D43B6D25CE@amalfisystems.com> <CADnDZ8_g+GGM9mgEjs59RCdV3YjXW-R0at15Df32r5Yp3sgneQ@mail.gmail.com> <5563.1450458340@obiwan.sandelman.ca>
Date: Fri, 18 Dec 2015 17:55:27 +0000
X-Google-Sender-Auth: 3MdAJ5w1nSi2ugkI84yiJ5tC5vk
Message-ID: <CADrU+dL7SUozBtjek2Znb4CxUr7iLJFjpnQ4iE5xDW+KDbM0Jw@mail.gmail.com>
From: Robert Cragie <robert.cragie@gridmerge.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary="089e0115fb102f09aa05272fd88f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/HXhQp-YJbP79ITZELlLv6stCeO0>
Cc: Ines Robles <mariainesrobles@googlemail.com>
Subject: Re: [Roll] New proposed charter
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: robert.cragie@gridmerge.com, 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, 18 Dec 2015 17:55:31 -0000

+1. I cannot under any circumstance envisage the need for ROLL to work on a
new routing protocol. Extensions to RPL, for sure. But not a new routing
protocol.

Robert

On 18 December 2015 at 17:05, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
>     > I agree with you. I think The problem is that the chair has to ask
> the
>     > working group to say what they want to be in scope. What is done so
> far is
>     > that our group chair is asking for new charter but still has the old
> scope of
>     > one protocol for the group. I only know that the WG has the power to
> change
>     > the scope if necessary when they prove that by discussion.
>
> I am quite certain:
>   a) that the IESG will not approve a WG charter that includes more than
> one
>      routing protocol.
>   b) that I don't want to be chair of a group that works on multiple
>      protocols in the same WG.
>   c) that should the IESG do such a thing, that I will have significant
>      feedback for nomcom.
>
> Meanwhile, I will repeat:
>   https://mailarchive.ietf.org/arch/msg/roll/odYLTGE2dkRP-SNrRSvx2-h-pU8
>
> ++ the first step would not be to assume a solution ("a new
> ++ routing protocol"), but rather to establish clearly what the problem is.
>
> So, if you have a draft that explains why another protocol is necessary,
> please point us to it.  It would certainly help figure out where the
> problem
> should be discussed; it could turn out that it's a trivial extension to the
> existing specification.
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/
>
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>
>