IETF Logo Mail Archive

Re: [Roll] Request for Comments for ROLL Charter

peter van der Stok <stokcons@xs4all.nl> Thu, 07 July 2016 07:21 UTC

Return-Path: <stokcons@xs4all.nl>
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 EBFF912D131 for <roll@ietfa.amsl.com>; Thu, 7 Jul 2016 00:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, 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 aPf3T6r98hNi for <roll@ietfa.amsl.com>; Thu, 7 Jul 2016 00:21:52 -0700 (PDT)
Received: from lb3-smtp-cloud6.xs4all.net (lb3-smtp-cloud6.xs4all.net [194.109.24.31]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FA8012B04B for <roll@ietf.org>; Thu, 7 Jul 2016 00:21:52 -0700 (PDT)
Received: from webmail.xs4all.nl ([194.109.20.209]) by smtp-cloud6.xs4all.net with ESMTP id FjMp1t0074WfiVN01jMpzX; Thu, 07 Jul 2016 09:21:50 +0200
Received: from AMontpellier-654-1-248-197.w92-133.abo.wanadoo.fr ([92.133.19.197]) by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Thu, 07 Jul 2016 09:21:49 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Thu, 07 Jul 2016 09:21:49 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Organization: vanderstok consultancy
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <3031.1467828123@dooku.sandelman.ca>
References: <CAP+sJUdRQHJhuszRLmMLoObVVELTGKAboPZpjHRV1M1t3T1BpA@mail.gmail.com> <962ecd511f1b4629bcf329790509bb0c@XCH-RCD-001.cisco.com> <17987.1467118035@obiwan.sandelman.ca> <7887a2c930bd4eb3b90da72e2bbe914b@XCH-RCD-001.cisco.com> <ec28f1cd-5f5e-43d9-bfc6-706a8b3116f2@gmail.com> <CAH7SZV-yuc8Zx6NBi_vMHZMFqEwZuKb25hewE2w1CC48yNyZ6Q@mail.gmail.com> <d9eb6a59c4206fe735a69e2d6ba57724@xs4all.nl> <dd7a9d7b-9963-bd5e-3ff5-b271dffe040a@gmail.com> <cbd3ddb63cc7a373b76b90438bcf727a@xs4all.nl> <CAP+sJUeg93Kz31pB2P3KwsyH0mQZy73H4ujksCkoROt8qNXhYA@mail.gmail.com> <f7829a0333174a46ba135ed5f803f6fa@XCH-RCD-001.cisco.com> <18245.1467816848@obiwan.sandelman.ca> <6c6ec0d6be3b1f474e1deaea7aace0d2@xs4all.nl> <3031.1467828123@dooku.sandelman.ca>
Message-ID: <30bd9ca12b47cacd94910a387cda4fb4@xs4all.nl>
X-Sender: stokcons@xs4all.nl (6BZfk8OI5PLMQwKpbmM0ESP+gk/ROGQD)
User-Agent: XS4ALL Webmail
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/s_2nM8qwmffMCxALFQHj1xvyohY>
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Re: [Roll] Request for Comments for ROLL Charter
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: consultancy@vanderstok.org, 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, 07 Jul 2016 07:21:55 -0000

We seem to be in agreement.
I just wanted to emphasize that when detailed concrete subjects with 
associated draft turn up, we make this clear in the milestones.
Which means that the list of subjects can be more general.
And indeed, not everything we have in mind needs a milestone now.

I was not thinking about IESG approval procedures.

Peter

Michael Richardson schreef op 2016-07-06 20:02:
> peter van der Stok <stokcons@xs4all.nl> wrote:
>     >> To me, it just fits into the maintenance of the specification.  
> We
>     >> don't need to list every single thing unless there will be a 
> series of
>     >> milestones associated with the work.
> 
> 
>     > I sympathize with Michael's remark.  Is there an associated 
> milestone
>     > before June 2017?  The idea is to have a limited set of concrete
>     > subjects with corresponding realistic milestones
> 
> I'm not sure if I'm answering your ? or just emphasizing the point...
> 
> I said: "series of milestones" here.
> 
> If we are taking on work that is more than a single document, then I 
> think we
> need IESG and charter support.  If it's just a single document, and it 
> shows
> up, then when we adopt it, we insert a milestone.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email