IETF Logo Mail Archive

Re: [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: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF35E3A07B4; Thu, 17 Mar 2022 06:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.662
X-Spam-Level:
X-Spam-Status: No, score=-2.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, MAILING_LIST_MULTI=-1, SPF_PASS=-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 ts2al1rxCYwo; Thu, 17 Mar 2022 06:36:15 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 559F53A05F0; Thu, 17 Mar 2022 06:36:13 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 703D91309BA; Thu, 17 Mar 2022 06:36:12 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id DF81B1309BA for <rfc-interest@rfc-editor.org>; Thu, 17 Mar 2022 06:36:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aOL1Sgva42qe for <rfc-interest@rfc-editor.org>; Thu, 17 Mar 2022 06:36:07 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) by rfc-editor.org (Postfix) with ESMTPS id 0EC5711FD99 for <rfc-interest@rfc-editor.org>; 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
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1647524167;aa9500f7;
X-HE-SMSGID: 1nUqIJ-0007ak-P9
Subject: Re: [rfc-i] IAB and IESG Search for RFC Series Working Group (RSWG) Chairs
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

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


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

v2.8.7 | Report a Bug | By Email