Re: [Rfced-future] [Ext] Comments on draft-iab-rfcefdp-rfced-model

Eric Rescorla <ekr@rtfm.com> Tue, 01 March 2022 19:58 UTC

Return-Path: <ekr@rtfm.com>
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 DD1BF3A0CB4 for <rfced-future@ietfa.amsl.com>; Tue, 1 Mar 2022 11:58:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20210112.gappssmtp.com
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 e8-p4ZIKad_R for <rfced-future@ietfa.amsl.com>; Tue, 1 Mar 2022 11:58:17 -0800 (PST)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E71F13A0CA8 for <rfced-future@iab.org>; Tue, 1 Mar 2022 11:58:14 -0800 (PST)
Received: by mail-io1-xd31.google.com with SMTP id d19so19754550ioc.8 for <rfced-future@iab.org>; Tue, 01 Mar 2022 11:58:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uDnlDbKbBAvpXP+McFmQauH5MW97PJStyQHR0IcV5Zc=; b=HLU8Z5ao/fDrg1TP/ZKxFHzzqt9Q4mQ1IGgv3p7vtFXz2+lTbauywP1Eu/OxIUOwEE kpu2d4iGrZhpTwJruQcTUEaJtB6NgZIezAIo7jWLS5OSmnxzsXqVYECMgDfXbv1kjunP SBwZ6dz2IbD82BJApYrRot0fyzt54MAq9qnGnKHnudQk3KNvJJgSATVyW1RhTrTr4awx jE3o0/exG9k/0sU7ohuYG2ZkH2y7p8Vyhagkm9ias8c/WsFmyR6KLKbgrm4qO2V8E9H+ Pc8qOesFlCIlqRFFO/UgeWBPiqpRjjv2T4b1hIeKmKj6fj1gZQtoyLv102xZl3Bojqo9 /GoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uDnlDbKbBAvpXP+McFmQauH5MW97PJStyQHR0IcV5Zc=; b=E3ldyC8tD3BsA9GlRUZ8znCPAL326j+ZHqzx+UaZV76xqmmqzvTyzcaCrCca6Ir+yz c+WKAHNiQbGw7MkPWUVwxKT3YZWd/3EJawmKmUCh1CsAwpr4jdaONnNDsk7xp89wVLAg CHogfA2jI03FIEC2r0b0oVnqGPbSLXtVgFqVJnXdjU3amWahBJsy+ph+FCHV6grHdDy3 qWrpM/ZV+RjJXr+RXMzbutSkyAA4faOGWLtcDhCutTQy+XUZqkyF027PO0VhlVLkBc0j ZCik2KtSjWQPllaQEnUXYGV6H4RHFfPkBa8fh9yii8onJZmXtjcKnTigxd8Bx2JvL4kV lrvg==
X-Gm-Message-State: AOAM531Xn3fHHE2tUTXcHtlGriMpE2lvlgw8UrQbUGqX+rzshZ1cjRo+ ERdxkpyd74CjcbGKVJ6wfr82NGMjSJXrVqzUcvvP7w==
X-Google-Smtp-Source: ABdhPJzmXPZwfDeqiU0FDlmPrfhIiBCwsXzrz0mhikyqffV24GsxBnqk/pSJTolyiXb3ERi0wrcL+aYO1qzlBe0OY3I=
X-Received: by 2002:a5d:8946:0:b0:63d:aa75:40ad with SMTP id b6-20020a5d8946000000b0063daa7540admr20326415iot.148.1646164693986; Tue, 01 Mar 2022 11:58:13 -0800 (PST)
MIME-Version: 1.0
References: <74AF211B-741E-46FC-9E35-8015D5254515@icann.org> <f55fba34-c449-8566-0423-147fc1fa3363@lear.ch> <0c1711fe-bc05-e6b0-2f94-eb1c24ae3766@stpeter.im> <CABcZeBPqGHt0KD4tjQZFd7SVRwQHVa7fj7wJ_LYCn-3XQKjfjg@mail.gmail.com> <01D06884-9136-49EB-AE2F-904EBAEB2BE5@icann.org>
In-Reply-To: <01D06884-9136-49EB-AE2F-904EBAEB2BE5@icann.org>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 01 Mar 2022 11:57:37 -0800
Message-ID: <CABcZeBMvs100huWXY0faBLB5+DmqkjzTFXY9ePJvvXxfNt+jOA@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@icann.org>
Cc: Peter Saint-Andre <stpeter@stpeter.im>, Eliot Lear <lear@lear.ch>, "rfced-future@iab.org" <rfced-future@iab.org>, "iab@iab.org" <iab@iab.org>
Content-Type: multipart/alternative; boundary="000000000000d3ca8f05d92d95be"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/GXNjYh2iioSvwxnsM_uQIl7jQvw>
Subject: Re: [Rfced-future] [Ext] Comments on draft-iab-rfcefdp-rfced-model
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: Tue, 01 Mar 2022 19:58:28 -0000

On Tue, Mar 1, 2022 at 10:56 AM Paul Hoffman <paul.hoffman@icann.org> wrote:

>
> On Mar 1, 2022, at 10:45 AM, Eric Rescorla <ekr@rtfm.com> wrote:
> >> Here is a proposed change:
> >>
> >> OLD
> >>
> >>     The RSAB seeks
> >>     such input by, at a minimum, sending a notice to the rfc-interest
> >>     mailing list or to its successor or future equivalent.
> >>
> >> NEW
> >>
> >>     The RSAB seeks
> >>     such input by, at a minimum, sending a notice to the mailing list of
> >>     the RSWG (which should supersede the current rfc-interest list).
> >>
> > I actually don't agree with this. I think the WG should have a separate
> list
> > that is moderated by the chairs. The rfc-interest list can continue, but
> > I think the new model deserves a new list.
> >
>
> Personal view: the RSWG list should not be moderated, just like IETF WG
> lists are not moderated. This will surely be painful, with lots of
> strongly-held views supported only by predictions of the future, but that's
> also true for a fair number of IETF WG lists.
>
> I read the proposed "(which should supersede the current rfc-interest
> list)" to mean that the new list will have a new name. Maybe better wording
> would be:
>
>     The RSAB seeks
>     such input by, at a minimum, sending a notice to the mailing list of
>     the RSWG, and the current rfc-interest list will be closed for
>     submissions and archived.
>

Paul,

Thanks for your email. you're right that "moderated" was the wrong term. I
meant "managed" in the sense that WG chairs manage IETF lists now. This can
be very light touch, but they're ultimately responsible for keeping things
on topic, addressing misbehavior, etc.

-Ekr


> --Paul Hoffman