IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 17 March 2022 16:49 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 B05B23A1418; Thu, 17 Mar 2022 09:49:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.662
X-Spam-Level:
X-Spam-Status: No, score=-7.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 K4qGOKikWZ4u; Thu, 17 Mar 2022 09:49:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 030553A1287; Thu, 17 Mar 2022 09:49:18 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B0EDF1E64A; Thu, 17 Mar 2022 09:49:18 -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 62AC41E64A for <rfc-interest@rfc-editor.org>; Thu, 17 Mar 2022 09:49:17 -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 oxSF7SGYBGSn for <rfc-interest@rfc-editor.org>; Thu, 17 Mar 2022 09:49:15 -0700 (PDT)
Received: from relay.sandelman.ca (unknown [IPv6:2a01:7e00:e000:2bb::1]) by rfc-editor.org (Postfix) with ESMTPS id 432311E649 for <rfc-interest@rfc-editor.org>; Thu, 17 Mar 2022 09:49:13 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [62.218.44.74]) by relay.sandelman.ca (Postfix) with ESMTPS id CC1CE1F4B8; Thu, 17 Mar 2022 16:49:07 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 3AEC81A0480; Thu, 17 Mar 2022 11:34:02 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
cc: execd@iab.org, rfc-interest@rfc-editor.org, architecture-discuss@ietf.org, rfced-future@iab.org
In-reply-to: <89FC552A-7215-440A-8E66-2F056411B64F@kuehlewind.net>
References: <164729256755.8331.9324867816980455015@ietfa.amsl.com> <24082.1647348635@localhost> <89FC552A-7215-440A-8E66-2F056411B64F@kuehlewind.net>
Comments: In-reply-to Mirja Kuehlewind <ietf@kuehlewind.net> message dated "Thu, 17 Mar 2022 14:35:58 +0100."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 26.3
MIME-Version: 1.0
Date: Thu, 17 Mar 2022 11:34:02 -0400
Message-ID: <260128.1647531242@dooku>
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: multipart/mixed; boundary="===============7722408838193943399=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

Mirja Kuehlewind <ietf@kuehlewind.net> wrote:
    > not sure who this question was addressed to but it actually might be
    > more a question for the program than for me.

Sure.  I certainly hoped to get everyone's attention.

    > 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...

Thank you, that at least is enough information for me.

--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




_______________________________________________
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