Re: Diversity and offensive terminology in RFCs

Paul Wouters <paul@nohats.ca> Thu, 20 September 2018 14:04 UTC

Return-Path: <paul@nohats.ca>
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 3F5541277CC for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 07:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 F1Z7OP_RoU4F for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 07:04:11 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 977BF130DE8 for <ietf@ietf.org>; Thu, 20 Sep 2018 07:04:11 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 42GJPP1SSDzDCy for <ietf@ietf.org>; Thu, 20 Sep 2018 16:04:09 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1537452249; bh=Wo56rSSHYSqSNzB7O8K709j/ppTo0/GvX+8uPUJJhF8=; h=Date:From:To:Subject:In-Reply-To:References; b=DIPyyOjGd+EnwCwdnLsFLVqUEYg05ueKChorpN84Oip/QX50HfJjC4YiYT1UXhA86 soUwIXrwJ2FlKNlmOdeaYr1ya41RfScaSnE3amxOW3B23W9Da9pVMhgmmsMSfnOmJR yxyI1bzmjg3i2GRh4HGxuilJvV0N+3u7F8aVUIuE=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 5gWS_OZroAeX for <ietf@ietf.org>; Thu, 20 Sep 2018 16:04:03 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS for <ietf@ietf.org>; Thu, 20 Sep 2018 16:04:02 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 989B35602F8; Thu, 20 Sep 2018 10:04:01 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 989B35602F8
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 8C649424DCE7 for <ietf@ietf.org>; Thu, 20 Sep 2018 10:04:01 -0400 (EDT)
Date: Thu, 20 Sep 2018 10:04:01 -0400
From: Paul Wouters <paul@nohats.ca>
To: ietf@ietf.org
Subject: Re: Diversity and offensive terminology in RFCs
In-Reply-To: <CAHbuEH7jeGLBMH8Yi+_o+o-NvZKmWt4KbtwbP-8XtL0taUCx_Q@mail.gmail.com>
Message-ID: <alpine.LRH.2.21.1809200954290.12509@bofh.nohats.ca>
References: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> <20180920132601.uwv2lblcvr4ojtk5@faui48e.informatik.uni-erlangen.de> <CAHbuEH7jeGLBMH8Yi+_o+o-NvZKmWt4KbtwbP-8XtL0taUCx_Q@mail.gmail.com>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CdmfC82f3lOQzVbwvkol9ZfUaAg>
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: Thu, 20 Sep 2018 14:04:14 -0000

On Thu, 20 Sep 2018, Kathleen Moriarty wrote:

> And what if your last name were Moriarty?  You'd never have the community be okay with you as a Security AD? ;-)

For years I bit my lip instead of asking "family of?" :)

> but don't think there is a racial connotation to black/white list.  White lists being preferred may be where the issue
> arrises I'm guessing.  Switching would be fine with me.

These small implications do add up to a group of people feeling the
negative practical effects, so I think we should work on not being
an even very small part of the problem.

> I already say active interception or session hijacking and think that's a fine replacement for man-in-the-middle.  I didn't see an issue with
> man-in-the-middle.

It's similar to "manned spaceflight". NASA's guidelines have been for
a very long time to use "crewed flight". If that helps a single girl to
not deem becoming an astronaut[1] as impossible, that's a win. Although
it is also a little different here because I hope no girls aspire to
become a man-in-the-middle :)

I think monkey/machine in-the-middle works and it allows us to keep
using the MITM acronym. And "session hijacking" to me could be done
without being in the path, so I wouldn't equate the two terms.

Paul