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

S Moonesamy <sm+ietf@elandsys.com> Wed, 27 December 2023 18:35 UTC

Return-Path: <sm@elandsys.com>
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 40804C1519B1; Wed, 27 Dec 2023 10:35:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.705
X-Spam-Level:
X-Spam-Status: No, score=-1.705 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
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 Gnhh95GC2Lb6; Wed, 27 Dec 2023 10:35:23 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D400BC1519AA; Wed, 27 Dec 2023 10:35:23 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.57.156]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 3BRIY8Up003218 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Dec 2023 10:35:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1703702103; x=1703788503; i=@elandsys.com; bh=lze0nxK2MfW7pmmnJnD9rKzw++fpK5k/gvjFNRBj8n4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=sLHb9buyo9N7GkooUgZ8hC+BggPUEDQ9/1WJiPu2/c8eMLGh0p0AcCJk3/90qXeEY 0K4j+8JdESkGS5a6auExo3VjiQbNMw9Xe26slJsFhTwDK/TZvH215w6vlofYdX/uRv yPJvsDGDgD2oJTYGc0oYHXEVOjYDOvKWvkQe1P3g=
Message-Id: <6.2.5.6.2.20231227094712.08da2570@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 27 Dec 2023 10:33:24 -0800
To: Toerless Eckert <tte@cs.fau.de>, Colin Perkins <csp@csperkins.org>
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: irtf-discuss@irtf.org, irsg@irtf.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; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/RqvI848i-WKiTCuWXaS86afmheY>
Subject: Re: [irtf-discuss] Fwd: 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: Wed, 27 Dec 2023 18:35:28 -0000

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?

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

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.

Sections 4 and 5 are more specific to the IRTF.

I sometimes see a disclosure/declaration of interests in an academic 
paper.  I could not find that in the draft.

Regards,
S. Moonesamy