Re: IESG Statement On Oppressive or Exclusionary Language

Richard Barnes <rlb@ipv.sx> Fri, 07 August 2020 15:51 UTC

Return-Path: <rlb@ipv.sx>
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 4B8A43A0BE0 for <ietf@ietfa.amsl.com>; Fri, 7 Aug 2020 08:51:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.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 M2JT3JhBrsF2 for <ietf@ietfa.amsl.com>; Fri, 7 Aug 2020 08:51:03 -0700 (PDT)
Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (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 5CABE3A0BD9 for <ietf@ietf.org>; Fri, 7 Aug 2020 08:51:03 -0700 (PDT)
Received: by mail-qt1-x836.google.com with SMTP id b25so1611291qto.2 for <ietf@ietf.org>; Fri, 07 Aug 2020 08:51:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yLFe5kpkF6jXO/xRlmCgs7a3+Yfob2206V0va7b1NLk=; b=A00lJuSxx9+UQZh8tq5Q8TpMoh9BIDBHQQKTRUXwFFD3lcUmqthoPHAODbULqrfDCq NV9EfYRW31+kFzeM9gmGTb9e6RVKCs9ZH56b2MZwTrzyc+71PcadUwBzZAUQLk1Z649e e8+zdvafm7nm1USTQ7RFiT+e5qKGqFTDjOFK9eQOY+agE9g81ADnHJzV0Wn9andfIOIg 9J1UAjZZv05CGQ5eLnOR3Gx3TDKfiGjq1dxuhbQSsNT5W04B5HyCmORVJoqV+200WPlQ NpnpumLxlkVW58HaQY/kP5NMfoX5ULEmJGNWq4QbRF+tCJiG+9eumE8AWirYxmZAuowF IMpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yLFe5kpkF6jXO/xRlmCgs7a3+Yfob2206V0va7b1NLk=; b=gZSQ33iHvKX4Lguo3JNvMPUvJcitPlCMnZ0+e9Zmn3SSLxyittVssYTvmCgIJGnQv5 /Kj3n90mhhh/XI7X3PMgOwThyoDag/oKT96cC+eiAfTciS/GgTEo2sVKO92sDRTAOVcB QcdEeIwdhx9Cp3FitM9/nn6EuQSUUzxrPBICHDbxicMEueItcFX/4gN8PzeDWhuqCasS JBlVbW36486s4ziPiOWZKOJXBy25B5VUMEmYznPryd3p4RA9TT+Pi1qa9EnAdKZwoIrH GPq5allzjSxe6PQhpFS0OgPNwqckqkcqJ3z3x5hNTPXAAYGGG47cYa7bDJkSIkHqBc6b XyYQ==
X-Gm-Message-State: AOAM533hser0QKQo21dYnttxxUxwtNBmXeqGSXS+xh8PXjWgVy0p/nNv Mw2qhodeUdYtNO8zPz4oKbf6L7jI3JPySB0bSmZgUg==
X-Google-Smtp-Source: ABdhPJwy6yn8VZm2XvPrRXxiGrFoVqxlkQDITzJAbb/46bVkWWwPqOTmfl1uNRA8qfGD3Z5CwMTo6R1gNec1oeOzg7s=
X-Received: by 2002:ac8:7454:: with SMTP id h20mr14429019qtr.84.1596815462160; Fri, 07 Aug 2020 08:51:02 -0700 (PDT)
MIME-Version: 1.0
References: <5692e18e-afbb-9294-1074-3b81dafe8803@network-heretics.com> <59C4CA26-A1EB-4CF4-B973-BC2BBF53A094@gmail.com> <CAL02cgTZt-9+QWPT1aWXcOgpEwuNV2uHnVi5dGm7V5y_8_U1SQ@mail.gmail.com> <0cceb0f2-b5fe-a194-7ce8-68cc537f9cd1@lounge.org> <CAL02cgTV-cfTPO2wrKz0H2E=FLhagu-qs7fwx6jXeJDH-2cSHA@mail.gmail.com> <B956D783-71F5-4413-85C0-81B04F9E0EEE@gmail.com>
In-Reply-To: <B956D783-71F5-4413-85C0-81B04F9E0EEE@gmail.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Fri, 07 Aug 2020 11:50:48 -0400
Message-ID: <CAL02cgR1nb6Ar2Gf-w2id6rB7z5=wquYjFCAXPPOdV6dw+BU-g@mail.gmail.com>
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: Dan Harkins <dharkins@lounge.org>, IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000064f28c05ac4b9236"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/279yDflsmrfFvyiTAq8ZCzryk-Q>
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, 07 Aug 2020 15:51:06 -0000

On Fri, Aug 7, 2020 at 11:14 AM Stewart Bryant <stewart.bryant@gmail.com>
wrote:

>
> "Call them "professionally wounded" or "snowflakes" if you want, but the
> road this leads down is toward a  senescent, obsolescent, irrelevant IETF.
> People have better things to do with their time than engage with an
> organization that doesn't care about them."
>
> I  don’t think it is the language we use in our documents or the language
> we use in our discussions that is the cause of the IETF becoming
> obsolescent or irrelevant. It is our inability to set aside  our technical
> religion and continually reexamine the fundamentals, together with  the
> imbalance in power and money between the service providers and the OTT
> providers which leads to lack of investment that has set us on that path.
>

This seems like the arguments that it's not CO2 that's causing climate
change, it's natural cycles or whatever.  Like, that may be true, but the
CO2 / toxicity certainly isn't *helping* the situation.

--Richard




>
> Stewart
>
>
>