Re: Diversity and offensive terminology in RFCs

Ted Lemon <mellon@fugue.com> Fri, 21 September 2018 14:42 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F5B6130E84 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 07:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 yq_UoMXo954T for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 07:42:22 -0700 (PDT)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (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 3D95A130E7F for <ietf@ietf.org>; Fri, 21 Sep 2018 07:42:22 -0700 (PDT)
Received: by mail-qk1-x736.google.com with SMTP id b19-v6so8324191qkc.6 for <ietf@ietf.org>; Fri, 21 Sep 2018 07:42:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=XfnXMFycH24z4J4yDeSL0tHKaCX76tTuxZK8oZwJxNU=; b=HD+vivTfsMP2mGkBjRLafkQcqBPM8W03H909dQPx3Ta0b8A0aVv8yffNyf2HQr7scH 5oFhRuUVnYqZ3TTMD4F7kwov86Hzs0+geQ1AAW2QBJPjEHaU2L1nKqDFAYlBhUwUplSe B8WKWt81CkFuhLPQb6w0b1kJ59+JG12PjN04iEEXNtbuw65nKWLw5EtoAeaXkr7UX2AF xRmSrmh9u39mY2wyaqQG9/NExdHBxe71uDyxNX0zaZE8JWMLUq+dGCrCRIsOKAJSDEK2 nYZ+cbISZDKcaYkSIHN/OraB7pra98XtUa3niLpJyd/c1N0tjRm6RyXBofG62T503f8l +Tkw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=XfnXMFycH24z4J4yDeSL0tHKaCX76tTuxZK8oZwJxNU=; b=TrgiXvhg83kS3MVNFnm9s4Wt4nu6M9SH5f3W2U6zn1t8PIj7jk2hK/eOxsEZjsSVo4 poj7rmm4Pe45hceECi+p1+oF9zCetxbE0X7AF+P26rgcYRIm9jTRKx7AALayXfeZ9EDe 5oSwGt8vfEF5URSL6M4wGRxwLq2+kDeTMXlYfszixCl2yHRTfVPHUOYZmYaluhyELI2s NtCX4bX/PxTptUvbk2Qh9jrzhYTE8t00mByfaAUb8iCvMC77sH83Y8EZhac69Nklogu9 aGl2f3rsJq8lOu7a/3OwHGXCsEwlnQb7FpbKZZYh0aD7hHyd693fTesZdxGZneW6M4MO Id/Q==
X-Gm-Message-State: APzg51B7GE1+sWBNsr+drCSEU8xMpGu+swDk8As4fubsTD7pw6/BA4Lv KkJJqwbegUTwE1HBjh6geOGKgQ==
X-Google-Smtp-Source: ANB0Vda1haLkEFJlorJEzMZQtJXlG4ES00OEsu3wzVDiohN0kIuZuVtAVmEFB2GKO3fNFTvFw8Yf6w==
X-Received: by 2002:a37:787:: with SMTP id 129-v6mr30815643qkh.300.1537540941190; Fri, 21 Sep 2018 07:42:21 -0700 (PDT)
Received: from [10.0.100.12] (c-73-167-89-221.hsd1.nh.comcast.net. [73.167.89.221]) by smtp.gmail.com with ESMTPSA id e65-v6sm15782430qkf.39.2018.09.21.07.42.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Sep 2018 07:42:20 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <276CA865-9AD8-41F9-8F17-395021E81432@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_698C857D-6CE8-4BD7-B394-97F44C74AC54"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Re: Diversity and offensive terminology in RFCs
Date: Fri, 21 Sep 2018 10:42:18 -0400
In-Reply-To: <c04d983a-61ed-3065-c849-af768fa6b62a@cisco.com>
Cc: Toerless Eckert <tte@cs.fau.de>, Paul Hoffman <paul.hoffman@vpnc.org>, ietf <ietf@ietf.org>
To: Eliot Lear <lear@cisco.com>
References: <20180920132601.uwv2lblcvr4ojtk5@faui48e.informatik.uni-erlangen.de> <CAHbuEH7jeGLBMH8Yi+_o+o-NvZKmWt4KbtwbP-8XtL0taUCx_Q@mail.gmail.com> <20180920143103.lvg6rmkzqfyjq3fr@faui48e.informatik.uni-erlangen.de> <52399791-9285-bcab-4fcd-3eb0f0a1f64f@gmail.com> <20180920151907.5wxxlccrvcgzjzcz@faui48e.informatik.uni-erlangen.de> <0FE3D4B6-CDDC-40A5-AC84-9C9E24278919@vpnc.org> <20180920171706.vemkprtgq2potrkr@faui48e.informatik.uni-erlangen.de> <20180920185721.GD68853@isc.org> <20180920201136.dtdw3dcjw663byu4@faui48e.informatik.uni-erlangen.de> <B40D702B-CD2D-42F0-91D5-D7B2776C2A2F@fugue.com> <20180920234451.l3kirvilfpb5pvsh@faui48e.informatik.uni-erlangen.de> <CAPt1N1=j_FC-PdPKt-QUSStxhpaCEaALhdjS-UjDCh8KUn6Zmg@mail.gmail.com> <c04d983a-61ed-3065-c849-af768fa6b62a@cisco.com>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ovzGKGpmVKCUh6Zn7CgDN0XslUw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Sep 2018 14:42:26 -0000

On Sep 21, 2018, at 9:02 AM, Eliot Lear <lear@cisco.com> wrote:
> Although we don't actually have any specifics as to why or how the
> terminology posed a problem.  We have no understanding of the harm in
> this case.  In python one person chose to believe that another person
> really had a problem, and that was that, end of discussion.

Eliot, I've actually explained the context of what transpired to you on the hrpc mailing list, and I don't see what I said reflected in your response here.   It wasn't "one person."   And it wasn't just python—when this was raised in another open source project and taken to a vote, a majority were in favor of using different terms.   None of this rises to the level of statistical clarity, but when dealing with issues like this, that kind of data is difficult to come by.

Do I need to point out to you that quite frequently in situations with bad power dynamics, getting accurate reports from injured parties is very difficult, and there's a strong tendency for their reports to be disbelieved by the majority in power, but when the dam finally breaks, it becomes clear that there was a real problem, and that the majority, in ignoring that problem, created real and substantial harm.

If our standard for approaching this problem involves small p-values, I doubt that we will make any changes at all.   The question is, do we need to require that standard of evidence, or are anonymous reports from people who say they have experienced abuse as a result of the use of this terminology sufficient?