Re: [irtf-discuss] I-D Action: draft-perkins-irtf-code-of-conduct-00.txt

Colin Perkins <csp@csperkins.org> Thu, 28 December 2023 16:35 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3815C151545 for <irtf-discuss@ietfa.amsl.com>; Thu, 28 Dec 2023 08:35:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=csperkins.org
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sLszduijwpOh for <irtf-discuss@ietfa.amsl.com>; Thu, 28 Dec 2023 08:35:33 -0800 (PST)
Received: from mx1.mythic-beasts.com (mx1.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 346DBC14F70B for <irtf-discuss@irtf.org>; Thu, 28 Dec 2023 08:35:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=Date:Subject:To:From; bh=R/aHJOXrtaFVl5ivd5q6TpiyigtT5u7u+0XNnd8hypo=; b=AGEwBYRQxh5+A/FB6qx6KcCZu6 dKj+vtFj0qNvwzAtTuS97huBgUixgs9BPcnjd8CJ6oejW6aSv7+fqpd7Xk8dBrITC4OQSZ3RvT5TF /KRz769DFoZzpYkWUlWHWbHAEHf6UfoeSRzCRWp2M1QOlVFPI33ifzghthO/zMsuEE/GBJBhxdr0p tU5/2atGLdBB5rYbJf41IrvsZtURmyRtaYwSMneY4juD5LJk4vSSLhDvhUS+4KpHP3N51e3wKzkzj Il8OviRb7rrbdQa6rXEyXom195lxbd/H/xmmdgJ3XYaOYr7kChyOAqKbBeCULwj+TKydn+cTxO9zh ZGjpJOmQ==;
Received: by mailhub-cam-d.mythic-beasts.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <csp@csperkins.org>) id 1rItM3-009pYV-0B; Thu, 28 Dec 2023 16:35:31 +0000
From: Colin Perkins <csp@csperkins.org>
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: irtf-discuss@irtf.org, Toerless Eckert <tte@cs.fau.de>
Date: Thu, 28 Dec 2023 16:34:33 +0000
X-Mailer: MailMate (1.14r6015)
Message-ID: <D7ECFD3D-71A8-4C37-B746-6DE7CBE016BC@csperkins.org>
In-Reply-To: <6.2.5.6.2.20231228073302.0c92fd40@elandnews.com>
References: <169807696671.8814.7919240260704168172@ietfa.amsl.com> <66F77DEF-78F1-4395-8D8B-034D861B3A38@csperkins.org> <ZTbWsXhRxOPXq9fc@faui48e.informatik.uni-erlangen.de> <6.2.5.6.2.20231227094712.08da2570@elandnews.com> <3EF05C50-2742-4140-A95D-42B2108C7B1B@csperkins.org> <6.2.5.6.2.20231228073302.0c92fd40@elandnews.com>
MIME-Version: 1.0
Content-Type: text/plain; markup="markdown"
Content-Transfer-Encoding: quoted-printable
X-BlackCat-Spam-Score: 24
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/4q76_adGtM0LK_rOhx6zgXY08_0>
Subject: Re: [irtf-discuss] I-D Action: draft-perkins-irtf-code-of-conduct-00.txt
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://mailman.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://mailman.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Dec 2023 16:35:37 -0000


On 28 Dec 2023, at 15:51, S Moonesamy wrote:

> Hi Colin,
> At 02:21 AM 28-12-2023, Colin Perkins wrote:
>> You did not quote my response to Toerless, where I said that IETF code of conduct is mainly focussed on effective conduct of the standards process. The overwhelming majority of its text is therefore not applicable to the IRTF. Accordingly, I don't believe it makes sense to base the IRTF code of conduct on it.
>
> Sorry about not quoting your response.
>
>> Points 1 and 2 from Section 2 of RFC 7154 have been expanded and updated for inclusion in the IRTF code of conduct. Points 3 and 4 are IETF-specific.
>
> As my opinion may be biased, I will leave it to you and everyone else to assess whether the text makes sense or not.
>
>> As is about half of Section 2 (both the reporting chain if cases of harassment occur and the way mailing lists are moderated differ between IETF and IRTF).
>
> I took a quick look at the existing policies [1].  The current guidance is to report concerns to the ombudsteam (please see first policy listed under "other policies").  May I ask why the reporting chain is being changed?

The reporting chain is not being changed.

Colin