Re: [Gendispatch] Meetings summary

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 16 October 2020 20:13 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F5253A0AD6 for <gendispatch@ietfa.amsl.com>; Fri, 16 Oct 2020 13:13:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level:
X-Spam-Status: No, score=-2.311 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.213, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5DE7mwha2Onz for <gendispatch@ietfa.amsl.com>; Fri, 16 Oct 2020 13:13:05 -0700 (PDT)
Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A6A53A0ACD for <gendispatch@ietf.org>; Fri, 16 Oct 2020 13:13:05 -0700 (PDT)
Received: by mail-pj1-x102d.google.com with SMTP id p21so1970233pju.0 for <gendispatch@ietf.org>; Fri, 16 Oct 2020 13:13:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=zY3+mCtpqdpvLv/QsG6QLt0ejfIcLT5qsyp6+zZPb7A=; b=kW2yPd+ufJxj9q2Hh/1TXRoGfAUshejmteRsH5ItL2BiHqxh22WgiHkxI82FTmRZdw BfV82Is2pIeP77HqF3Syv20XL29dY89jYfpbfd6tX1PCLCRJGPJ/VrKSmJgOGTYPZ0ft 4n81qoCml92a32c3M6XCNjKjlRnHjjik4N6oQfxALL+sNRlnG9yL5LS27BHFaV4PJcDd VskNPfuaDLEgRcIlPVCkkvVuyBAJmqD9+61nQ3evrFbbIe5fpXrPsPMKkOSD9+tAGgiH /B5bDeg47FBG6UfWoDeTGdDyCLLFePeQabhvrzYKl4GoA2+qzWALyvzkJ/EkKHh9iGXh sCAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=zY3+mCtpqdpvLv/QsG6QLt0ejfIcLT5qsyp6+zZPb7A=; b=gWE+7jT5Kle1HGvenCBGhXPMM6mPzoOnJS94t7ktuKrSNkKHpQv98hgHtCIPA7FUZQ VVpwS1/LwT+mjOo6yVSKScr6RyxMKRRbMiohXOitmhN+booz7s78BvjmLEMUSeHdR+rY e0HqbF1O1aRNF4L90Dd1Jy/13E2tkeTk/qoAuYqmtJhmhgL5r9l7RxPqkTsxNkMRoMY6 YSHGIIUk5ttK/Jg9JwEQ4Bt7CeRCFt6OxLrkxf9bcK7cYrY5Hupe1381hDHvuPh80E+t jbCeryLElf5Lu7NvkhxOwmZe6YQukLliCRUuPTt+oopGGGwV930E+ubLlvYSJuFds6mP osaQ==
X-Gm-Message-State: AOAM5334sFt9nyGimiu1XxKaByS6iOweXWov8klIhQAs65g+GjxjDfpp MBAIuzekgXi06HsQtDd4jXyuyRteTYqMUQ==
X-Google-Smtp-Source: ABdhPJzgyEcko0BKIWrT5NG8RFrc6oorRSJvukFx2fKDkagTriIAW4RseXg3Tek3+HTJCOzjJ0322A==
X-Received: by 2002:a17:902:465:b029:d0:89f1:9e2a with SMTP id 92-20020a1709020465b02900d089f19e2amr5782686ple.6.1602879183712; Fri, 16 Oct 2020 13:13:03 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.132.159]) by smtp.gmail.com with ESMTPSA id f204sm3976065pfa.189.2020.10.16.13.13.01 for <gendispatch@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Oct 2020 13:13:02 -0700 (PDT)
To: gendispatch@ietf.org
References: <B1075198-D4F5-498B-B16B-3081A9B07DDD@episteme.net> <76d19c8b-68d3-465f-b869-c18a9db7504f@dogfood.fastmail.com> <37C4EBD5-F9FC-4814-98F5-6926E2D4A66A@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <01b9d36a-1857-d824-5c6f-c1ddf403ff26@gmail.com>
Date: Sat, 17 Oct 2020 09:12:58 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <37C4EBD5-F9FC-4814-98F5-6926E2D4A66A@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/POl088Xbq_8e7kyjts4Dr0qHg4Y>
Subject: Re: [Gendispatch] Meetings summary
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2020 20:13:07 -0000

On 17-Oct-20 02:38, Eliot Lear wrote:
> Bron,
> 
> 
>> On 16 Oct 2020, at 15:02, Bron Gondwana <brong@fastmailteam.com <mailto:brong@fastmailteam.com>> wrote:
>>
>> Oh I'm glad I missed this the other day in my "jetlag" induced stupor (I've been attending CalConnect virtual conference from 2-6am Melbourne time this week), so I didn't get dragged in at the time.
>>
>> I was very disappointed that the key question that I think needs to be answered by the community, and particular by those who favour draft-knodel, didn't have time for proper discussion at the last gendispatch meeting.
>>
>> *Does the IETF have confess to some "sins"?*
> 
> With regard to language, it seems good to recognize that there are phrases that we should avoid.  But I don’t know if that is the same as a confession, or that we have to beat our backs on one to address language.
> 
>>
>> I believe this is the core issue underlying much of the disagreement.  I feel that there's not consensus on whether we have something to apologise for.
>>
>> There's also a sub issue hidden under that, which is this question:
>>
>> *Is the IETF systemically racist?*
> 
> 
> Is that the effort or is the effort to correct language?  The above question seems to me a great opportunity to rathole forever.

That's the point. We can knock off the issue of words that are better avoided quite quickly. Tackling all the isms (not just racism) is a much harder issue, and IMNSHO is one that the IETF *cannot* tackle on its own, because we don't control the demographics of the people who participate in the IETF. I take it as a given that once people participate in the IETF, our rules and guielines disallow any form of discrimination, so it's hard to see how writing an RFC can help much anyway.

In fact there is already an RFC that makes things pretty clear:

>    Open process - any interested person can participate in the work,
>    know what is being decided, and make his or her voice heard on the
>    issue.
...
>    The Internet is a global phenomenon.  The people interested in its
>    evolution are from every culture under the sun and from all walks of
>    life.  The IETF puts its emphasis on technical competence, rough
>    consensus and individual participation, and needs to be open to
>    competent input from any source.

[RFC3935, BCP95]

Yes, of course, there may be prejudiced people among our participants, and there is certainly unconscious bias among our participants. We should probably have a plan for dealing with this, beyond the anti-harassment policy and ombudsteam, but I don't think that plan necessarily includes an RFC.

Regards
   Brian