[gaia] Re: Last call: IRTF Code of Conduct

Colin Perkins <csp@csperkins.org> Sun, 22 September 2024 22:08 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: gaia@ietfa.amsl.com
Delivered-To: gaia@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1888EC14F6A5; Sun, 22 Sep 2024 15:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.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, HTML_MESSAGE=0.001, 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 8--RcoU-B-Z8; Sun, 22 Sep 2024 15:08:23 -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 5C6B0C14F5E0; Sun, 22 Sep 2024 15:08:23 -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=iHO2DSJ616abvqJM6JJBIoC/SnTFExHbfxbxrMXBXfY=; b=F769RGmUSi9fPX3dKPqzOa6CGe S13vt3CWhRQD31m/00hVF/iUYO0rrvlOwgv38zTQhxz9iJ/CXOMD59umTXYFOIH45FfdNxPs7DFnO rA29Zjy5N7mVltHhlV0jYJxCF1oTR6f3xRzt9mDcaLO7DXRzKEXwWsbe68ZWp7MbbAQ29CEM1omwS ckWcNAVdJyUK2eu0ppyWDBAb966Gq8nLA2CXN25TbBxBgmmCTwUwufdGZMa+z+zfNZ2akUaj9f730 PGbq9x2fL3Nq1wDvk4YqmEtKo29Hbh1xGw7Nk4bon4Qeg9U7bd8L3fL+s24pwYUY3O4u+epPQMuWU LkuHbpUA==;
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 <csp@csperkins.org>) id 1ssUkg-00Cwtw-25; Sun, 22 Sep 2024 23:08:22 +0100
From: Colin Perkins <csp@csperkins.org>
To: janercoffin@gmail.com
Date: Sun, 22 Sep 2024 23:08:21 +0100
X-Mailer: MailMate (1.14r6065)
Message-ID: <A58150CC-77D0-4764-AECE-C3ABCC147CDF@csperkins.org>
In-Reply-To: <23E7FC7E-B835-4C99-9D6F-EE7FFA6B5157@gmail.com>
References: <D123800D-9525-4D8C-84ED-530169D8F763@csperkins.org> <23E7FC7E-B835-4C99-9D6F-EE7FFA6B5157@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_A660D75F-8547-462B-9E98-80306374AC5A_="
Content-Transfer-Encoding: 8bit
X-BlackCat-Spam-Score: 0
Message-ID-Hash: RWINC23IFPIKD3FBQU5IF4FZ5OEFI4PR
X-Message-ID-Hash: RWINC23IFPIKD3FBQU5IF4FZ5OEFI4PR
X-MailFrom: csp@csperkins.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-gaia.irtf.org-0; header-match-gaia.irtf.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: gaia@irtf.org, The IRSG <irsg@irtf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [gaia] Re: Last call: IRTF Code of Conduct
List-Id: Global Access to the Internet for All <gaia.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gaia/_Bgtbn1KTxaYlLVpQsSds6fWNqQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gaia>
List-Help: <mailto:gaia-request@irtf.org?subject=help>
List-Owner: <mailto:gaia-owner@irtf.org>
List-Post: <mailto:gaia@irtf.org>
List-Subscribe: <mailto:gaia-join@irtf.org>
List-Unsubscribe: <mailto:gaia-leave@irtf.org>

Thanks, Jane.
Colin

On 22 Sep 2024, at 23:05, janercoffin@gmail.com wrote:

> Hi Colin -
>
> That sounds reasonable. I think we can only set the parameters and 
> guard-rails and tweak things as we go.
>
> Best,
> Jane
> Jane Coffin
> Signal, Telegram, Text, WhatsApp
> +1.202.247.8429
>
>> On Sep 22, 2024, at 15:18, Colin Perkins <csp@csperkins.org> wrote:
>>
>> Hi Jane,
>>
>> [inline; belatedly]
>>
>>> On 10 Sep 2024, at 17:48, Jane Coffin wrote:
>>>
>>> Hi Colin -
>>>
>>> Comments inline back to you:
>>>
>>> Jane R Coffin
>>> Signal, WhatsApp, Text:  +1.202.247.8429
>>>
>>>
>>>
>>>> On Mon, Sep 9, 2024 at 6:38 PM Colin Perkins <csp@csperkins.org> 
>>>> wrote:
>>>>
>>>> Hi Jane,
>>>>
>>>> Thanks for the feedback. Comments inline.
>>>>
>>>>> On 9 Sep 2024, at 20:37, Jane Coffin wrote:
>>>>
>>>>> Hi Colin -
>>>>>
>>>>> Two additional food for thought observations on the draft:
>>>>>
>>>>> In Section 5:
>>>>>
>>>>> 5.  Research Ethics
>>>>>
>>>>>   Participants must ensure that their research, in particular 
>>>>> research
>>>>>   that involves human subjects or personal data, is conducted 
>>>>> ethically
>>>>>   and with respect for persons, in careful consideration of the 
>>>>> risks
>>>>>   and benefits of the work, ensuring that those who bear the risk 
>>>>> also
>>>>>   gain some benefit, and with respect for the law and public 
>>>>> interest.
>>>>>
>>>>> *This clause in blue could be misinterpreted.  Perhaps we change 
>>>>> the
>>>> word "ensuring" to "noting"?
>>>>
>>>> Perhaps “…taking care that those who bear the risk also gain 
>>>> some benefit”?
>>>>
>>> **That works.
>>
>> I settled on “taking care to ensure that those who bear the risk 
>> also gain some benefit” – hopefully that’s okay!
>>
>>
>>>>
>>>>> Section 6:
>>>>>
>>>>> Participants should work to enable remote participation in IRTF
>>>>>   events to support those who cannot attend in person, and should 
>>>>> aim
>>>>>   to make materials available online in a timely and broadly 
>>>>> accessible
>>>>>   manner.
>>>>> *By suggesting we will make materials "available online in a 
>>>>> ...broadly
>>>>> accessible manner"? Access is constrained to a degree.  Should we 
>>>>> qualify
>>>>> this somehow? [RFC2014]
>>>>
>>>> With “access is constrained to a degree” do you mean that some 
>>>> materials
>>>> are not publicly available or that some materials are not 
>>>> accessible to
>>>> remote attendees (or those with disabilities)?
>>>>
>>> I think the word "broadly" is the word that I am curious about.  I 
>>> think we
>>> are speaking specifically about access limited by current IETF 
>>> tools, yes?
>>> Not a complaint, just trying to understand what we mean.
>>
>> Right – the tooling and data formats might have hard-to-fix 
>> limitations that constrain what’s possible, so while we do that we 
>> can, we may not be able to meet every access need.
>>
>> Again, open to suggesting for better wording.
>>
>> Cheers,
>> Colin