IETF Logo Mail Archive

Re: [Roll] New proposed charter

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 14 December 2015 03:35 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 7ABFA1A1B6D for <roll@ietfa.amsl.com>; Sun, 13 Dec 2015 19:35:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level:
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 FqILmgdUUXDc for <roll@ietfa.amsl.com>; Sun, 13 Dec 2015 19:35:10 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0F3F1A1B6C for <roll@ietf.org>; Sun, 13 Dec 2015 19:35:09 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 70283200A3; Sun, 13 Dec 2015 22:41:01 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 209AB63797; Sun, 13 Dec 2015 22:35:09 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Randy Turner <rturner@amalfisystems.com>
In-Reply-To: <687E3051-78DB-4425-9261-53D43B6D25CE@amalfisystems.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>
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: Sun, 13 Dec 2015 22:35:09 -0500
Message-ID: <12070.1450064109@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/Hx2tiTSK1qDneeco9tPrpvdkiuc>
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>
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: Mon, 14 Dec 2015 03:35:11 -0000

Randy Turner <rturner@amalfisystems.com> wrote:
    > I thought the discussion was around developing a new charter. If that's
    > the case then nothing is "in scope" yet. If we're not discussing
    > potential work items for a new charter then what is this thread about
    > again?  I would be happy to work up a draft if that's what is required
    > to get things "in scope"

Step 1a) adjust charter.  The PROPOSED charter text ALREADY says:

    ***the standardization of a mixed storing/non-storing mechanism***

so anything that you want to write about a "non-storing with multicast-storing"
would fit into that wording.

1b) the text also says, "look at enhancements and maintenance to the RPL
   protocol"

So, anything which ads to RPL is in scope.

2) Step 2, when the new charter is in place, PLEASE:
   "Write an ID, slides, etc.."

about "non-storing with multicast-storing", and see if there is a reason/support for
the IETF to standardize it.  It could be that only you care, in which case
you can write it up as a non-WG submission, not subject to standardization.
Or it could be that it's the coolest thing since HTTP, and everyone wants to
run it...

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/

v2.23.0 | Report a Bug | By Email