Re: [Rfced-future] [rfc-i] IAB and IESG Search for RFC Series Working Group (RSWG) Chairs

Mirja Kuehlewind <ietf@kuehlewind.net> Thu, 17 March 2022 13:36 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F08D3A00C4; Thu, 17 Mar 2022 06:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 AzkmLNmgbOIY; Thu, 17 Mar 2022 06:36:06 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C2AC3A00B2; Thu, 17 Mar 2022 06:36:06 -0700 (PDT)
Received: from p200300dee70b8e007469170034727a8a.dip0.t-ipconnect.de ([2003:de:e70b:8e00:7469:1700:3472:7a8a] helo=[192.168.178.42]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1nUqIJ-0007ak-P9; Thu, 17 Mar 2022 14:35:59 +0100
User-Agent: Microsoft-MacOutlook/16.48.21041102
Date: Thu, 17 Mar 2022 14:35:58 +0100
From: Mirja Kuehlewind <ietf@kuehlewind.net>
To: Michael Richardson <mcr+ietf@sandelman.ca>, execd@iab.org
CC: rfc-interest@rfc-editor.org, architecture-discuss@ietf.org, rfced-future@iab.org
Message-ID: <89FC552A-7215-440A-8E66-2F056411B64F@kuehlewind.net>
Thread-Topic: [rfc-i] IAB and IESG Search for RFC Series Working Group (RSWG) Chairs
References: <164729256755.8331.9324867816980455015@ietfa.amsl.com> <24082.1647348635@localhost>
In-Reply-To: <24082.1647348635@localhost>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1647524166;a3cedc55;
X-HE-SMSGID: 1nUqIJ-0007ak-P9
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/qGgx4KOXjFi-IIfubt4sbtcsKMM>
Subject: Re: [Rfced-future] [rfc-i] IAB and IESG Search for RFC Series Working Group (RSWG) Chairs
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2022 13:36:11 -0000

Hi Richard,

not sure who this question was addressed to but it actually might be more a question for the program than for me. 

However, I'll tell my view anyway: I believe the answer is we really don't know. I would guess 5 given me modeled this after IETF groups but maybe there is bit of start-up overhead as well or maybe it will be more quite at the start... 

Mirja



On 16.03.22, 19:07, "rfc-interest on behalf of Michael Richardson" <rfc-interest-bounces@rfc-editor.org on behalf of mcr+ietf@sandelman.ca> wrote:


    IAB Executive Administrative Manager <execd@iab.org> wrote:
        > 2. Please provide a statement confirming your willingness to serve as
        > RSWG chair and ability to devote an appropriate level of time to
        > activities associated with the position.

    Please level set "appropriate" here for me on my scale of 1..10:

    A "1" would mean something like 1 virtual meeting per year.
    A "10" would mean something like a monthly meeting, more than three of which would be
    in-person, some outside IETF meetings.

    On such a scale, I think that a regular IETF WG would probably be a 5:
       A few in-person meetings per year,
       and a few virtual interims per year.

    CBOR is a 7.

    --
    Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
               Sandelman Software Works Inc, Ottawa and Worldwide




    _______________________________________________
    rfc-interest mailing list
    rfc-interest@rfc-editor.org
    https://www.rfc-editor.org/mailman/listinfo/rfc-interest