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

Colin Perkins <csp@csperkins.org> Tue, 24 October 2023 16:50 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 3C2A0C14CEF9; Tue, 24 Oct 2023 09:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.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_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 gJVvFEkn2X35; Tue, 24 Oct 2023 09:50:52 -0700 (PDT)
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 CDD18C14CEFD; Tue, 24 Oct 2023 09:50:52 -0700 (PDT)
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=ipiUPPsV8GQuRJaqSAqh2H83yaCP0mfwJ+aaG8l2QzE=; b=lYNjWv6Ppfsk2wAY05QlxaGETO 3vSeKdD0gD397hTvzmK/PEDCdxKs2axfJrJDjSRREj5m5T1RwU+i/kNXjMB+iRURxKMYlbwTCId5t aQrrzG/4hh4boQdmgrovJU0IN4Rra2G88OOVIiqn0B8vcGGRHbmGENI69bR3c5sfAseb3LhV7It5o OTWgJ+0VulxHqNGj4CsdhZOr9MUG21S1hnD7xayQA3Gp8Hg1RTk0QXweO90296l1dFy2bcRt015Lv siu68B8oHpirZkg99ajHZ/o4nv91oBOhlEVIQ/gZyW5fW7enj2THD+Lb+bU3b7Wncn+xxbd8YYQfy 4GrTNk8w==;
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 1qvKcF-007nXn-Gb; Tue, 24 Oct 2023 17:50:51 +0100
From: Colin Perkins <csp@csperkins.org>
To: Toerless Eckert <tte@cs.fau.de>
Cc: irtf-discuss@irtf.org, Internet Research Steering Group <irsg@irtf.org>, sm+ietf@elandsys.com
Date: Tue, 24 Oct 2023 17:49:38 +0100
X-Mailer: MailMate (1.14r5997)
Message-ID: <D48D841C-2E92-4220-B008-1D31E5E9EF92@csperkins.org>
In-Reply-To: <ZTbWsXhRxOPXq9fc@faui48e.informatik.uni-erlangen.de>
References: <169807696671.8814.7919240260704168172@ietfa.amsl.com> <66F77DEF-78F1-4395-8D8B-034D861B3A38@csperkins.org> <ZTbWsXhRxOPXq9fc@faui48e.informatik.uni-erlangen.de>
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/V41mp6G6OZ0CED6ARC9ztDEwy0c>
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://www.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://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Oct 2023 16:50:57 -0000


On 23 Oct 2023, at 21:25, 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.

You're welcome to discuss on the irtf-discuss@ list, but if you want comments to be considered they should be copied to the IRSG.

> 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.

The paragraph prior to the one you quoted highlights some of the core differences between the two organisations. I can add a reference to RFC 7418 that expands on these.

> 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.

The 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.

Colin