Re: [Roll] New proposed charter

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 18 December 2015 17:05 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 B9BC51B3725 for <roll@ietfa.amsl.com>; Fri, 18 Dec 2015 09:05:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 sDPSEloTWJIG for <roll@ietfa.amsl.com>; Fri, 18 Dec 2015 09:05:41 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B090F1B3712 for <roll@ietf.org>; Fri, 18 Dec 2015 09:05:41 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id DB03C2009E; Fri, 18 Dec 2015 12:11:48 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id ABEA8636CA; Fri, 18 Dec 2015 12:05:40 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
In-Reply-To: <CADnDZ8_g+GGM9mgEjs59RCdV3YjXW-R0at15Df32r5Yp3sgneQ@mail.gmail.com>
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>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Fri, 18 Dec 2015 12:05:40 -0500
Message-ID: <5563.1450458340@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/nyy3PS1rZiD_1IM0gwiJI-3LOe0>
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, 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: 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:05:43 -0000

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/