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 35203C180B44 for ; Mon, 9 Sep 2024 02:52:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.108 X-Spam-Level: X-Spam-Status: No, score=-2.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, HTML_MESSAGE=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 oojBEZpHj6O6 for ; Mon, 9 Sep 2024 02:52:14 -0700 (PDT) Received: from mx2.mythic-beasts.com (mx2.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 71350C169411 for ; Mon, 9 Sep 2024 02:52:14 -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=cd0SK5804grZDNwKC1NBWGvhiXt7y8mNAyNlOEPjb7s=; b=KMVTg+J2COsAn4pPO/853Q/StC LJMT/tP/ztbPQAIi41YH3NBdtC6XdpmeTubNa3oBrAGiFC4AlYv7G2bMpJqyTtvj1TXp8L+27LMVN anMHNaiyvQzEBANNGpdYDT8xVroUFGtACOEt16PWxQLUnfsFiUpQZ6tW8G7XQsCr9xy1uN5uMBJsY 3wcYtMY2eNOd48PmxipHMjFHXQFoHrmR5867SXquYymjL65x1xIQE1cTGgdiDHT7Zr9rpMa5png+1 ba/jIl5jFJWqJZuWvCyyfZdQD9+gy185Rd/PeVvsOcDUzm/6UjCWPmWqZdz7ktoub/sUJpG3ZtC+H zxgO0zPw==; Received: by mailhub-hex-d.mythic-beasts.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1snb48-006aOt-7z for cfrg@irtf.org; Mon, 09 Sep 2024 10:52:12 +0100 From: Colin Perkins To: cfrg Date: Mon, 09 Sep 2024 10:52:11 +0100 X-Mailer: MailMate (1.14r6065) Message-ID: <3C8A08B2-CCB0-439F-BFEB-0584331D550C@csperkins.org> In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_MailMate_3175C203-2BCF-45F4-AE7B-6F4C61A1EAB9_=" X-BlackCat-Spam-Score: 24 Message-ID-Hash: PRKYZEGUUOAPG3R3BVJWJZBHR2XSATLD X-Message-ID-Hash: PRKYZEGUUOAPG3R3BVJWJZBHR2XSATLD 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_3175C203-2BCF-45F4-AE7B-6F4C61A1EAB9_= Content-Type: text/plain; format=flowed; markup=markdown Content-Transfer-Encoding: quoted-printable A reminder that the last call for comments on the IRTF code of conduct = ends this Friday, 13th September 2024. If you have any final comments or = feedback on the proposed code of conduct, please send them to the IRSG = (irsg@irtf.org) with a copy to the irtf-discuss@irtf.org mailing list. Colin Perkins IRTF Chair 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_3175C203-2BCF-45F4-AE7B-6F4C61A1EAB9_= Content-Type: text/html Content-Transfer-Encoding: quoted-printable

A reminder that the last call for comments on the IRTF co= de of conduct ends this Friday, 13th September 2024. If you have any fina= l comments or feedback on the proposed code of conduct, please send them = to the IRSG (irsg@irtf.org) with a c= opy to the irtf-discuss@irtf.org= mailing list.

Colin Perkins
IRTF Chair

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_3175C203-2BCF-45F4-AE7B-6F4C61A1EAB9_=--