Return-Path: X-Original-To: cfrg@ietfa.amsl.com Delivered-To: cfrg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EB22C151996 for ; Sun, 22 Sep 2024 15:39:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.805 X-Spam-Level: X-Spam-Status: No, score=-2.805 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 OX3zNAwGDz5w for ; Sun, 22 Sep 2024 15:39:18 -0700 (PDT) Received: from mx1.mythic-beasts.com (mx1.mythic-beasts.com [46.235.224.141]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54FF8C1840EE for ; Sun, 22 Sep 2024 15:39:18 -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=hKecW3nK7V5J5lNOOc5Dx34jLrx6n6h6TOXPDlMYGKM=; b=hy13RxA4ZDiYCtaGCPzILqsMh6 kEPqLt588lWYmGM9zH9YgSwnV/TsaxAjXzm7fvPg8ugHz3OuIjhISVRZtDqJwH8TLBByfE0MvJVKJ +92Q2WP6SUBXHiWMQp+xPCM7OXNlK3Th/J20CuuS1RMVmYXvGlJqH5G3j+ihhCi08vTvyJzqb9v/0 oW0PWEjX2eSxeJFdocwOAH26EfqYy0FWfJQWE81jJrFVSQOfhMaQ5zF8oxMdkvTrvNqt2fdIT0S0m KU//nRxO427Si+qenqdgIbWP4TcNIOKWk/z81ehIJJh8S5iHQ4IZneNzN8UxRsxL/cUJwjndQ/2GY ARndOtAA==; 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 ) id 1ssVEa-00Dt8m-5O for cfrg@irtf.org; Sun, 22 Sep 2024 23:39:16 +0100 From: Colin Perkins To: cfrg Date: Sun, 22 Sep 2024 23:39:13 +0100 X-Mailer: MailMate (1.14r6065) Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_MailMate_5E7B1206-B51B-4867-8D74-911C13BE8E7F_=" X-BlackCat-Spam-Score: 0 Message-ID-Hash: VM3GEEIKDEF77HIN5ONQC34BXVZGE3EP X-Message-ID-Hash: VM3GEEIKDEF77HIN5ONQC34BXVZGE3EP X-MailFrom: csp@csperkins.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cfrg.irtf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5BCFRG=5D_Re=3A_Last_call=3A_IRTF_Code_of_Conduct?= List-Id: Crypto Forum Research Group Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --=_MailMate_5E7B1206-B51B-4867-8D74-911C13BE8E7F_= Content-Type: text/plain; charset=UTF-8; format=flowed; markup=markdown Content-Transfer-Encoding: quoted-printable The Last Call on the IRTF Code of Conduct has concluded. Thanks to all those who sent comments and provided feedback: = [draft-perkins-irtf-code-of-conduct-05](https://datatracker.ietf.org/doc/= draft-perkins-irtf-code-of-conduct/) = has now been submitted with the following minor changes: * Move the Rationale earlier in the document * Clarify definition of harassment to read =E2=80=9CHarassment is behavio= ur = that is unwelcome, hostile, or intimidating. Harassment includes, in = particular, =E2=80=A6=E2=80=9D rather than =E2=80=9CHarassment is unwelco= me, hostile, or = intimidating behaviour, in particular=E2=80=A6.=E2=80=9D * Be specific that harassment is not tolerated in virtual meetings = rather than implying this under =E2=80=9Cother online forums=E2=80=9D. * Add a paragraph to say: =E2=80=9CThe IRTF sometimes organises meetings = or = activities that co-locate with events organised by others. These = meetings or activities may need to follow the anti-harassment policy of = the hosting event, which may differ from that of the IRTF. In such = cases, the organisers of the IRTF meeting or activity should check with = the IRTF Chair to confirm that the policy is acceptable and it should be = made clear to participants what policy applies.=E2=80=9D * Clarify that permanent suspension of posting rights requires approval = from the IRTF Chair, not merely consultation. * Minor clarifications to the wording about Language and Imagery. * Clarify that documents Internet drafts that build on prior work should = only be written with the permission of any co-authors. * In research ethics, rephrase =E2=80=9Censuring that those who bear the = risk = also gain some benefit=E2=80=9D to =E2=80=9Ctaking care to ensure that=E2= =80=A6=E2=80=9D * Clarify that =E2=80=9Crestrict individual from using IRTF systems=E2=80= =9D should = be =E2=80=9C=E2=80=A6using IRTF IT systems=E2=80=9D to match [RESTRICTING= ]. The draft will now proceed to the IRSG review stage. Colin On 28 Aug 2024, at 11:47, Colin Perkins wrote: > The IRSG is proposing that the IRTF adopt the code of conduct = > described in = > [draft-perkins-irtf-code-of-conduct](https://datatracker.ietf.org/doc/d= raft-perkins-irtf-code-of-conduct/). > > If adopted, this code of conduct will apply to participation in all = > IRTF research groups, the IRTF open meeting, IRTF workshops such as = > the ANRW, mailing list discussions, and other IRTF activities. > > The code of conduct provides guidelines for conduct in meetings and on = > mailing lists, use of language and imagery, academic integrity, = > research ethics, and accessibility. > > The IRSG is proposing the IRTF adopt this code of conduct, distinct = > from that of the IETF ([RFC = > 7154](https://datatracker.ietf.org/doc/rfc7154/)), because the IETF = > code of conduct is focussed on appropriate conduct for the development = > of standards, while the IRTF needs guidelines for the conduct of = > research. The differences between the two documents reflect the = > different roles of IRTF and IETF. Policies that are shared between the = > two organisations, such as those relating to anti-harassment and = > inclusive language, and the role of the Ombudsteam, are included by = > reference. > > This proposal has been under discussion by the IRSG since October = > 2023. Community feedback has been sought via the IRTF announcement = > mailing list, in the IRTF open meetings at IETF 118, 119, and 120, and = > in the plenary of the recent IETF 120 meeting in Vancouver. A number = > of research groups have also previously circulated calls for feedback. > > If you have any final comments or feedback on this [proposed IRTF code = > of = > conduct](https://datatracker.ietf.org/doc/draft-perkins-irtf-code-of-co= nduct/), = > please send them to the IRSG (irsg@irtf.org) with a copy to the = > irtf-discuss@irtf.org mailing list. The deadline for comments is = > Friday, September 13, 2024. > > Colin Perkins > IRTF Chair > _______________________________________________ > CFRG mailing list -- cfrg@irtf.org > To unsubscribe send an email to cfrg-leave@irtf.org --=_MailMate_5E7B1206-B51B-4867-8D74-911C13BE8E7F_= Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The Last Call on the IRTF Code of Conduct has concluded.<= /p>

Thanks to all those who sent comments and provided feedba= ck: draft-perkins-irtf-code-of-conduct-05 has now been submit= ted with the following minor changes:

  • Move the Rationale earlier in the document

  • Clarify definition of harassment to read =E2=80=9CHarassm= ent is behaviour that is unwelcome, hostile, or intimidating. Harassment = includes, in particular, =E2=80=A6=E2=80=9D rather than =E2=80=9CHarassme= nt is unwelcome, hostile, or intimidating behaviour, in particular=E2=80=A6= =2E=E2=80=9D

  • Be specific that harassment is not tolerated in virtual m= eetings rather than implying this under =E2=80=9Cother online forums=E2=80= =9D.

  • Add a paragraph to say: =E2=80=9CThe IRTF sometimes organ= ises meetings or activities that co-locate with events organised by other= s. These meetings or activities may need to follow the anti-harassment po= licy of the hosting event, which may differ from that of the IRTF. In suc= h cases, the organisers of the IRTF meeting or activity should check with= the IRTF Chair to confirm that the policy is acceptable and it should be= made clear to participants what policy applies.=E2=80=9D

  • Clarify that permanent suspension of posting rights requi= res approval from the IRTF Chair, not merely consultation.

  • Minor clarifications to the wording about Language and Im= agery.

  • Clarify that documents Internet drafts that build on prio= r work should only be written with the permission of any co-authors.

  • In research ethics, rephrase =E2=80=9Censuring that those= who bear the risk also gain some benefit=E2=80=9D to =E2=80=9Ctaking car= e to ensure that=E2=80=A6=E2=80=9D

  • Clarify that =E2=80=9Crestrict individual from using IRTF= systems=E2=80=9D should be =E2=80=9C=E2=80=A6using IRTF IT systems=E2=80= =9D to match [RESTRICTING].

The draft will now proceed to the IRSG review stage.

Colin

On 28 Aug 2024, at 11:47, Colin Perkins wrote:

The IRSG is proposing that the IRTF adopt the code of con= duct described in draft-perkins-irtf-code-of-conduct.

If adopted, this code of conduct will apply to participat= ion in all IRTF research groups, the IRTF open meeting, IRTF workshops su= ch as the ANRW, mailing list discussions, and other IRTF activities.

The code of conduct provides guidelines for conduct in me= etings and on mailing lists, use of language and imagery, academic integr= ity, research ethics, and accessibility.

The IRSG is proposing the IRTF adopt this code of conduct= , distinct from that of the IETF (RFC 7154), because the IETF code of conduct is focusse= d on appropriate conduct for the development of standards, while the IRTF= needs guidelines for the conduct of research. The differences between th= e two documents reflect the different roles of IRTF and IETF. Policies th= at are shared between the two organisations, such as those relating to an= ti-harassment and inclusive language, and the role of the Ombudsteam, are= included by reference.

This proposal has been under discussion by the IRSG since= October 2023. Community feedback has been sought via the IRTF announceme= nt mailing list, in the IRTF open meetings at IETF 118, 119, and 120, and= in the plenary of the recent IETF 120 meeting in Vancouver. A number of = research groups have also previously circulated calls for feedback.

If you have any final comments or feedback on this proposed IRTF code of conduct, please send them to the IRSG (irsg@irtf.org) with a copy to the irtf-discuss@irtf.org mailing list. Th= e deadline for comments is Friday, September 13, 2024.

Colin Perkins
IRTF Chair

CFRG mailing list -- cfr= g@irtf.org
To unsubscribe send an email to cf= rg-leave@irtf.org

--=_MailMate_5E7B1206-B51B-4867-8D74-911C13BE8E7F_=--