Re: Diversity and offensive terminology in RFCs
Phillip Hallam-Baker <phill@hallambaker.com> Fri, 21 September 2018 15:44 UTC
Return-Path: <hallam@gmail.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 E53C2130EDA for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 08:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.503
X-Spam-Level:
X-Spam-Status: No, score=-1.503 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.146, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 RfJtezsPJWs7 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 08:44:51 -0700 (PDT)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (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 D77AE130E9A for <ietf@ietf.org>; Fri, 21 Sep 2018 08:44:50 -0700 (PDT)
Received: by mail-oi0-x22b.google.com with SMTP id l82-v6so11757272oih.11 for <ietf@ietf.org>; Fri, 21 Sep 2018 08:44:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=yYzb2U98fCvwpVLCRBmCJAK44qGmgRpLxcVGaTnAMSI=; b=QOat77BszKVlPVSgUMyg5c4U0Ys50I3u+nrOlrKMrJNkoDWgYWfyUqXRQhs2RTy843 wz56ZfCQ6UXmljNMdL/sdj/cB+T5J5b8wx4hRwPSbfkQXCukTuYjgIRG4Bt0feo5uiHD WxR2dbRMOGwTs5p/EesQYz/X5jtLSl3kBFHuefCwYimW/j4e++Tubi7WIkUNS8lw6qQi FqrSiljYQwBwZ7geWX3fUW0SkQBaQGymUuGf2MPVWW/bN8QmIG3lESGtSJnXfEoe7c/l gkuLnWH4E+L+6qBBfHAsfaPXpgxnsiLafB5vtgflZySPLycF3Vr8ApMm6JQDk8sZbLAz NtMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=yYzb2U98fCvwpVLCRBmCJAK44qGmgRpLxcVGaTnAMSI=; b=d8F6+vt9cOJ5RA0MVE2oABrBis4Iw5f+l/xX3wqO9n0azQv/pYgQLTgzUE0Kk+UQhr gpQR9knIbxsYM3GRIcMv/FhqgrsiKVb6Q9AyA+8CzNoM6uhS3oy5y+70gEeNoeBLaz8s 2Y5oAHfKyKJSOWkG6dZltVD09WCfOT+mLN/FrqoOIaY9lCVsb0GuAFpKUSmb3sv85ntt M13Nd13rDYYRLt6e0/VwHoeLVaBB/ko3DeJxQQZrbjllnRHnHLyfK++q4mKfZe4uEWsq 0N+wfn/7WQB8D39Vlp6nlLN6pOWJBFnHfHp0ZKZYAC9cwKvyI3NMh7d8jNeQhbQ/Tflz 6MOg==
X-Gm-Message-State: APzg51DLPKanBEhJTreKRmJlbdKvSW13oA2sxFa4f7eKA0qBoZ3sMO4Q k1CMvyjLo4VT0GFZuGgi18dWKPTYnv3goJpvL78=
X-Google-Smtp-Source: ANB0VdYtv9xMXi2PEJKfLEnUsQboTQteNtiIu31pFOoiLukD1z1gUGQbZps+8I4I92ykrgegMbjokyri/GFbFAgL9Ng=
X-Received: by 2002:aca:34d6:: with SMTP id b205-v6mr1849661oia.77.1537544690152; Fri, 21 Sep 2018 08:44:50 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 2002:a9d:27c8:0:0:0:0:0 with HTTP; Fri, 21 Sep 2018 08:44:49 -0700 (PDT)
In-Reply-To: <737419165.14108666.1537504425226@mail.yahoo.com>
References: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> <20180920174256.GC68853@isc.org> <5BA454E1.4020105@signal100.com> <CAG4d1rd6e0yG_OffDcCVgLa0ayEDPcfF4yb1a=1d0d3rMZD=0w@mail.gmail.com> <5BA45FFF.80004@signal100.com> <5BA466B2.8060705@signal100.com> <CAMm+LwguCCqCSH1g1fi20gHeB2QMSK73i8ssNWcihQuaAg5psA@mail.gmail.com> <737419165.14108666.1537504425226@mail.yahoo.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 21 Sep 2018 11:44:49 -0400
X-Google-Sender-Auth: 4f-5MJu_sYg1BAO80nsjsqq-pDo
Message-ID: <CAMm+Lwhb3SCUx9kFBT7Fyyks8_RnzqapHrzW3u1CLNu3V-a93A@mail.gmail.com>
Subject: Re: Diversity and offensive terminology in RFCs
To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
Cc: Mark Rousell <mark.rousell@signal100.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000153ba5057663852c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bc_RrLK6RM4nWtsTYiRcLPVlQvs>
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 15:45:00 -0000
On Fri, Sep 21, 2018 at 12:33 AM, Lloyd Wood <lloyd.wood@yahoo.co.uk> wrote: > "Since the man in the middle is always up to no good," > > TCP accelerators for satellite; email relaying, DNS resolvers > > that aren't root name servers... > > intermediaries are often there for good helpful reasons. No, an intermediary is not the same as a Man-in-the-Middle. If you use the term MITM to me, I will immediately interpret that as a description of an attack because that is what the established use as a term of art defines it to be. You should not be using MITM for any situation where a positive or even a neutral disposition is intended. It is unclear at best, I regard it as wrong. A DNS resolver is a point at which a MITM attack might be staged but it is not a MITM attack of itself. And the notion that resolvers are mere relays is actually one that I think is wrong and has held back development of DNS. The client-resolver protocol need not be the same as the resolver-authoritative. These are entirely different applications that should not have been confused in the first place and we are only recently managing to unconfuse. The no-DNS and DoH work are examples showing why the resolver-authoritative protocol is not the most effective. If I talk about an Email relay being a MITM then I am saying that changing my character set, wrapping lines and all the really obnoxious behavior they routinely engage in are attacks. Of course on the gender neutral side, MITM attacks are traditionally performed by Eve. And historically, many of the intercept operators on the allied side were women. It was one of the few field combat roles they were permitted.
- Diversity and offensive terminology in RFCs Niels ten Oever
- Re: Diversity and offensive terminology in RFCs Riccardo Bernardini
- Re: Diversity and offensive terminology in RFCs Stewart Bryant
- Re: Diversity and offensive terminology in RFCs Petr Špaček
- Re: Diversity and offensive terminology in RFCs Niels ten Oever
- Re: Diversity and offensive terminology in RFCs Dave Cridland
- Re: Diversity and offensive terminology in RFCs Loa Andersson
- Re: Diversity and offensive terminology in RFCs Mukund Sivaraman
- SV: Diversity and offensive terminology in RFCs Anne-Marie Eklund-Löwinder
- RE: Diversity and offensive terminology in RFCs Roberta Maglione (robmgl)
- Re: Diversity and offensive terminology in RFCs Ole Troan
- Re: Diversity and offensive terminology in RFCs Michal Krsek
- Re: Diversity and offensive terminology in RFCs Tony Finch
- Re: Diversity and offensive terminology in RFCs Job Snijders
- Re: Diversity and offensive terminology in RFCs Anton Ivanov
- Re: Diversity and offensive terminology in RFCs Anton Ivanov
- RE: Diversity and offensive terminology in RFCs Adrian Farrel
- Re: SV: Diversity and offensive terminology in RF… Jaap Akkerhuis
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Andrew Sullivan
- Re: Diversity and offensive terminology in RFCs Kathleen Moriarty
- Re: Diversity and offensive terminology in RFCs lloyd.wood
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: SV: Diversity and offensive terminology in RF… lloyd.wood
- Re: Diversity and offensive terminology in RFCs Paul Wouters
- Re: Diversity and offensive terminology in RFCs Paul Wouters
- Re: Diversity and offensive terminology in RFCs lloyd.wood
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Stephan Wenger
- Re: Diversity and offensive terminology in RFCs Mark Nottingham
- Re: Diversity and offensive terminology in RFCs Stephen Farrell
- RE: Diversity and offensive terminology in RFCs John E Drake
- Re: Diversity and offensive terminology in RFCs Melinda Shore
- Re: Diversity and offensive terminology in RFCs Dick Franks
- Re: Diversity and offensive terminology in RFCs ned+ietf
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Melinda Shore
- Re: Diversity and offensive terminology in RFCs Melinda Shore
- Re: Diversity and offensive terminology in RFCs Paul Hoffman
- Re: SV: Diversity and offensive terminology in RF… Evan Hunt
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- ""Man-in-the-middle""? <was, Re: SV: Diversity an… Charlie Perkins
- Re: Diversity and offensive terminology in RFCs Evan Hunt
- Re: Diversity and offensive terminology in RFCs Melinda Shore
- Re: Diversity and offensive terminology in RFCs Evan Hunt
- Re: SV: Diversity and offensive terminology in RF… Michael StJohns
- Re: ""Man-in-the-middle""? <was, Re: SV: Diversit… Dave Aronson
- Re: SV: Diversity and offensive terminology in RF… Heather Flanagan
- Re: Diversity and offensive terminology in RFCs Mark Nottingham
- Re: Diversity and offensive terminology in RFCs Heather Flanagan
- Re: Diversity and offensive terminology in RFCs Evan Hunt
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: Diversity and offensive terminology in RFCs Ted Lemon
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Evan Hunt
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: Diversity and offensive terminology in RFCs John C Klensin
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: SV: Diversity and offensive terminology in RF… Anton Ivanov
- Re: Diversity and offensive terminology in RFCs Yoav Nir
- Re: Diversity and offensive terminology in RFCs Kyle Rose
- Re: Diversity and offensive terminology in RFCs Brian E Carpenter
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: Diversity and offensive terminology in RFCs Dave Cridland
- Re: Diversity and offensive terminology in RFCs Ted Lemon
- Re: why exactly is HRPC for, was Diversity and of… John Levine
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Ted Lemon
- Re: Diversity and offensive terminology in RFCs Brian E Carpenter
- Re: Diversity and offensive terminology in RFCs Mark Rousell
- Re: why exactly is HRPC for, was Diversity and of… Mark Rousell
- Re: why exactly is HRPC for, was Diversity and of… Melinda Shore
- Re: Diversity and offensive terminology in RFCs Alia Atlas
- Re: why exactly is HRPC for, was Diversity and of… Allison Mankin
- Re: Diversity and offensive terminology in RFCs Mark Rousell
- Re: Diversity and offensive terminology in RFCs Mark Rousell
- Re: Diversity and offensive terminology in RFCs Mark Rousell
- Re: Diversity and offensive terminology in RFCs Phillip Hallam-Baker
- Re: Diversity and offensive terminology in RFCs Lloyd Wood
- Re: Diversity and offensive terminology in RFCs Lloyd Wood
- On-path attackers (Was: Re: Diversity and offensi… Jari Arkko
- Re: why exactly is HRPC for, was Diversity and of… Eliot Lear
- Re: why exactly is HRPC for, was Diversity and of… Niels ten Oever
- Re: why exactly is HRPC for, was Diversity and of… Lloyd Wood
- Re: Diversity and offensive terminology in RFCs Eliot Lear
- Re: On-path attackers (Was: Re: Diversity and off… Kathleen Moriarty
- Re: Diversity and offensive terminology in RFCs Alissa Cooper
- Re: why exactly is HRPC for, was Diversity and of… Paul Wouters
- Re: why exactly is HRPC for, was Diversity and of… Ted Lemon
- Re: On-path attackers (Was: Re: Diversity and off… Donald Eastlake
- Re: why exactly is HRPC for, was Diversity and of… Lloyd Wood
- Re: Diversity and offensive terminology in RFCs Niels ten Oever
- Re: On-path attackers (Was: Re: Diversity and off… Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Ted Lemon
- Re: Diversity and offensive terminology in RFCs Anton Ivanov
- Re: On-path attackers (Was: Re: Diversity and off… Ted Lemon
- Re: why exactly is HRPC for, was Diversity and of… John R Levine
- Re: Diversity and offensive terminology in RFCs Paul Wouters
- Re: Diversity and offensive terminology in RFCs Eliot Lear
- Re: Diversity and offensive terminology in RFCs Phillip Hallam-Baker
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Nico Williams
- Re: why exactly is HRPC for, was Diversity and of… Avri
- Re: Diversity and offensive terminology in RFCs Spencer Dawkins at IETF
- Re: Diversity and offensive terminology in RFCs Dave Cridland
- Re: why exactly is HRPC for, was Diversity and of… John Levine
- Re: why exactly is HRPC for, was Diversity and of… Spencer Dawkins at IETF
- Re: why exactly is HRPC for, was Diversity and of… Allison Mankin
- Tell me if I should send this Re: why exactly is … Mallory Knodel
- Mallory-in-the-middle attacks (Re: SV: Diversity … Nico Williams
- Re: Diversity and offensive terminology in RFCs Nico Williams
- Re: On-path attackers (Was: Re: Diversity and off… Brian E Carpenter
- Re: Diversity and offensive terminology in RFCs Glenn Deen
- Re: Mallory-in-the-middle attacks (Re: SV: Divers… Nico Williams
- Re: Tell me if I should send this Re: why exactly… lloyd.wood
- Re: Mallory-in-the-middle attacks (Re: SV: Divers… Mallory Knodel
- Re: why exactly is HRPC for, was Diversity and of… Mallory Knodel
- Re: Diversity and offensive terminology in RFCs Abdussalam Baryun
- Re: why exactly is HRPC for, was Diversity and of… S Moonesamy
- Re: why exactly is HRPC for, was Diversity and of… Mallory Knodel