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

Colin Perkins <csp@csperkins.org> Thu, 28 December 2023 10:25 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 E26D3C15170B; Thu, 28 Dec 2023 02:25:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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_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 i254NvJrKbkw; Thu, 28 Dec 2023 02:25:07 -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 921A8C1654E5; Thu, 28 Dec 2023 02:25:07 -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=TPFXc4i8UOHk78Fhiv55HCfocv+I1HB0R6p4SO9uXD8=; b=yHKxhQTqbO7M4+NviZiymufB88 YGF4GXqO3tw02jrTXR9w+c+ZVzQgHkaIqpVtcpjVdOaiW1o+kreK1rlCokHkyufhK8+e4wO9eQRmU 3xncxeq8/mkbvPqscV5JWnHV2yyqqAbLurOYQ9DJ0h13YXJboLlkzJfHJeh+w8yzkvb7pKsoJOsqH JlBaoK3CAsmR60yZacgo+eYb31vr+8bt3yTA6+PlOLWYiLykZOcUG3BekVYM8OEDu0dCCjvAEa+LQ KcAmVmiJEKKvyrseyiniGfUrr9z9I1WdecACurMluSgL9ou1FA2Nm7BQIT6gom/FaB3zQLXTpoHQE I39kmLiw==;
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 1rInZN-006wWT-Q7; Thu, 28 Dec 2023 10:24:54 +0000
From: Colin Perkins <csp@csperkins.org>
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: Toerless Eckert <tte@cs.fau.de>, irtf-discuss@irtf.org, irsg@irtf.org
Date: Thu, 28 Dec 2023 10:21:49 +0000
X-Mailer: MailMate (1.14r6015)
Message-ID: <3EF05C50-2742-4140-A95D-42B2108C7B1B@csperkins.org>
In-Reply-To: <6.2.5.6.2.20231227094712.08da2570@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>
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/Hby5mgbzj46GVAICkata_68Qo8I>
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 10:25:12 -0000

On 27 Dec 2023, at 18:33, S Moonesamy wrote:
> Hi Toerless, Colin,
> At 12:25 PM 23-10-2023, Toerless Eckert wrote:
>> Thanks, Colin
>>
>> a) I think it would be great if IRTF would practice an open and transparent
>> process and also discuss this document on irtf-discuss, even though i am not sure
>> if this is required for IRTF documents such as this one.
>>
>> b) Given how IETF participants are likely the biggest possible IRTF participants,
>> even if not necessarily as contributors but hopefully as more than welcome
>> commenters, it would be probably helpfull to not only write:
>>
>> " Compared to the IETF equivalent [RFC7154], this IRTF code of conduct
>>   reflects those differences in emphasis between the two organisations. "
>>
>> But maybe elaborate on those core differences as a quick "executive summary"
>> for IETF contributors. Even though it might constitute some degree of duplication
>> over the prior text.
>>
>> c) I am not sure about the exact administrative and organizational relationship
>> between IETF and IRTF, but i hope that wrt. code of conduct it should make sense
>> to think of a common code of conduct across both of them and then specific
>> code of conduct aspects that apply only to standards (group) work and/or only to
>> research (group) work. But it seems we do not have such a common code of conduct.
>>
>> In it's absence i wonder if the IRTF code of conduct should not consider
>> to explicitly inherit the IETF code of conduct and explicitly describe differences.
>> I understand that that would be more work, but it would have the benefit of
>> then also automatically inheriting any changes in IETF code of conduct that
>> is also applicable to IRTF to the IRTF.
>>
>> Right now it seems like its more the opposite: The text about honesty specifically
>> towards AI-tools is of course equally applicable to IETF, and hence investing
>> the work of thinking what a modernized common ietf+irtf code-of-conduct should
>> include might be better spent than trying to first write (only) an IRTF-only
>> code of conduct.
>
> I quoted all the comments from Toreless as it may be useful for people reading the thread.  He raised a good question; would be possible to find some commonality across streams?

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.

> The heading of Section 2 of the draft is "conduct".  The text in that section is about harassment.

Harassment is a form of conduct we wish to prevent.

> Some of the text in Section 3 is along the lines of what is in RFC 7154.  There isn't any mention of imagery in RFC 7154.

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.

> Sections 4 and 5 are more specific to the IRTF.

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 sometimes see a disclosure/declaration of interests in an academic paper.  I could not find that in the draft.

The IRTF does not require such a disclosure and it would be a significant change in practice.

Colin