IETF Logo Mail Archive

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

Lars Eggert <lars@eggert.org> Wed, 02 March 2022 10:14 UTC

Return-Path: <lars@eggert.org>
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 6578E3A0ED4; Wed, 2 Mar 2022 02:14:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.226
X-Spam-Level: *
X-Spam-Status: No, score=1.226 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_SBL_CSS=3.335, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 Dq6MWRK4wNbw; Wed, 2 Mar 2022 02:14:19 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 B017B3A0EDF; Wed, 2 Mar 2022 02:14:19 -0800 (PST)
Received: from smtpclient.apple (unknown [195.65.18.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 8129C1D373E; Wed, 2 Mar 2022 12:14:10 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1646216050; bh=Rta6nZDW/j7UT70WoE0hiiEctYzXh9gwEYmPt3g8bTo=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=lJsptV/nYvZluUCsi+2BMZdWDcgne4aS8TrIhuNG4TSS6aE0wflwLyikx1qBK+Ss+ VwLBlWt4DAHap6Ia/jgoezMv1xlX/tDchUFH+04U/AkmwNMfYGM6QlK45KLA+aRjB4 CxSJceO5gfCxP03IGq8BIDbbitQcqvZ8oFDYptjc=
Content-Type: multipart/signed; boundary="Apple-Mail=_47D7D351-4933-49BD-80E3-916662C59D79"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <CABcZeBMvs100huWXY0faBLB5+DmqkjzTFXY9ePJvvXxfNt+jOA@mail.gmail.com>
Date: Wed, 02 Mar 2022 11:14:09 +0100
Cc: Paul Hoffman <paul.hoffman@icann.org>, "rfced-future@iab.org" <rfced-future@iab.org>, "iab@iab.org" <iab@iab.org>, Peter Saint-Andre <stpeter@stpeter.im>, Eliot Lear <lear@lear.ch>
Message-Id: <6356FB12-4628-4530-8044-4F3819074F40@eggert.org>
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> <CABcZeBMvs100huWXY0faBLB5+DmqkjzTFXY9ePJvvXxfNt+jOA@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
X-MailScanner-ID: 8129C1D373E.A15BA
X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/HhFy_8GABc8zWOhLSBap7gQRRRU>
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: Wed, 02 Mar 2022 10:14:25 -0000

Hi,

On 2022-3-1, at 20:57, Eric Rescorla <ekr@rtfm.com> wrote:
> 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.

I think the term "moderated" is appropriate, in the sense that IETF WG lists can *become* moderated when the chairs see a need (also see https://www.ietf.org/about/groups/iesg/statements/mailing-lists-moderation/ and https://www.ietf.org/about/groups/iesg/statements/disruptive-posting/ and possibly others.)

Thanks,
Lars

v2.23.0 | Report a Bug | By Email