Re: [Terminology] Update to TERM charter text

Lars Eggert <lars@eggert.org> Tue, 13 April 2021 13:56 UTC

Return-Path: <lars@eggert.org>
X-Original-To: terminology@ietfa.amsl.com
Delivered-To: terminology@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F42F3A1803 for <terminology@ietfa.amsl.com>; Tue, 13 Apr 2021 06:56:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 FUoCscrJFxin for <terminology@ietfa.amsl.com>; Tue, 13 Apr 2021 06:56:38 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (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 4B3D33A17F4 for <terminology@ietf.org>; Tue, 13 Apr 2021 06:56:38 -0700 (PDT)
Received: from [IPv6:2a00:ac00:4000:400:75a4:136a:31e4:4341] (unknown [IPv6:2a00:ac00:4000:400:75a4:136a:31e4:4341]) (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 0DFA0600336; Tue, 13 Apr 2021 16:56:26 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1618322187; bh=dVuXLsry+y/Eq5txPCtfaefSY6XuXsGGf48Ga4lu2z8=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=LRuMLcY4AzOOLRLKVSvTFyvFmM8SEbi7ZknCYMFL92gHJFXKSGHftagFzwWTmT7j8 /zJhdd6BUCLexDDdeWIG9JrtgNr9RAhz/nwGVQyAZIVhZ716YS8J3JAEaW5ARJYsWJ WYWzA4mIhgsUK2XgxiuGiURZWM5cUgnWl6sCjXhc=
From: Lars Eggert <lars@eggert.org>
Message-Id: <9CC26797-B2EF-4E24-8F48-09DEDF8F6697@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_3EEE8F6D-62D7-4B20-A81A-D099F617F790"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Tue, 13 Apr 2021 16:56:26 +0300
In-Reply-To: <31add831-4c5f-315d-3070-1633cdcd032b@digitaldissidents.org>
Cc: terminology@ietf.org
To: Niels ten Oever <lists@digitaldissidents.org>
References: <8143F715-9D83-4C15-B441-D0D8CA302C50@eggert.org> <D5FEBE8C-14D4-48BD-AAE7-9436E296CB7E@eggert.org> <ed88e91a-1224-4918-710e-dfe6e5c89df4@digitaldissidents.org> <9191f3bd-d52a-4fa4-b117-79b3bb517cdf@www.fastmail.com> <6a54335a-b033-60a1-a431-ba92954527cc@digitaldissidents.org> <F89896BC-7654-4EF0-99FF-43C2E1AB74E8@eggert.org> <31add831-4c5f-315d-3070-1633cdcd032b@digitaldissidents.org>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
X-MailScanner-ID: 0DFA0600336.A3504
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/2m9fZEzRIP5YIoQCq4NKGHFmE4Q>
Subject: Re: [Terminology] Update to TERM charter text
X-BeenThere: terminology@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Effective Terminology in IETF Documents <terminology.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/terminology>, <mailto:terminology-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/terminology/>
List-Post: <mailto:terminology@ietf.org>
List-Help: <mailto:terminology-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/terminology>, <mailto:terminology-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Apr 2021 13:56:43 -0000

Hi,

On 2021-4-13, at 16:47, Niels ten Oever <lists@digitaldissidents.org> wrote:
> On 13-04-2021 12:51, Lars Eggert wrote:
>> 
>> when it comes to documents, yes. But not usually when it comes to charter text. Since it's the responsible ADs who are in charge of scoping the work in their area, it is usually them that edit charter text, especially if the chartering is somewhat contentious.
> 
> Which is fine - but I wanted to indicate that changing the charter now and in this manner (in a particular direction that was extensively discussed earlier in the process), will probably make the reaching of consensus on a document to be produced by this WG much harder.

that's a valid concern. But I want to stress that we're not doing anything out of the ordinary here. The charter has been discussed in gendispatch, and consensus for a way forward was established in gendispatch, i.e., that a WG should be formed on the basis of the charter text that was discussed there.

The next step in the formation of a WG is usually a BOF, followed by IESG (internal) and then IETF (external) review of the charter. Since we had a BOF-like discussion in gendispatch, we skipped the BOF and went straight to internal and most recently external review.

Often, no significant comments are received and a WG is chartered with only minor tweaks to the charter proposal that was sent out for review. In this case, the IESG received quite a bit of very polarized comments, and as the responsible AD for the area I am attempting to reflect those pieces of feedback in the charter update for which I see some level of consensus. I'm doing this in the hopes that this will make the overall charter gain rough consensus when it goes out again for external review.

I'm hoping this explains the process a bit more.

Thanks,
Lars