Re: Effective discourse in the IETF

Ted Lemon <mellon@fugue.com> Wed, 03 July 2019 16:50 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 F32EA120335 for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 09:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 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_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=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 fO6ugXvFLMcU for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 09:50:13 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 42AA212038E for <ietf@ietf.org>; Wed, 3 Jul 2019 09:50:13 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id a15so4355403qtn.7 for <ietf@ietf.org>; Wed, 03 Jul 2019 09:50:13 -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=pWWew8jB7fAzlwIV2ZYKZsnw3QinS/McTdkUeSyWLxQ=; b=LaEVdBnlbdFdaFYPtyUbZzY+kcwk4eXiSOeVZ/ZDhtOaArqxTI1Cnsy3+g+egA7N7E iCFQibuF7uiAHRTGwiggKptqW4UmBoGeLEUoV5MQG6lZl8l01wn7fchO3orOXLSZzAUu kA5i1uqNf19VNW2ww0uIFsSnV1QnBOm/t0S1JB6zXN4WH8NcfZ/FPyjtP5AKqnbM6ns3 DNv17U39B444+lXqE33O8oVPK6NLoQuhmiB1oBQXscFfBvLqi2RsiOyU80SSzhk99U6e UZe16GlNUkVubnA4QDvAj9hKE0UcG88wWXa2KkaWoCD7CU7+w6GU24W6czTY4WPD8LEw zEwg==
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=pWWew8jB7fAzlwIV2ZYKZsnw3QinS/McTdkUeSyWLxQ=; b=gfr+i3Jdn28KhD7IrkNqd2Lu3YzDZwN38XMgo/hydtEDzB1CMfy6Dd3zfSBJdFNIeH 2Ymo0QlwSu57qX7boP+NcqkFHk+rn8b/4BWnL+qlSvNcJReZ3e3Sg1te1h1C9fGyZ01w msK0MlbR5ZTrsH7c3dR18ycia9LXCzFNbV+PS8i8ojbnyZjM9TwMd91dsdx5fCEtz0by pF5KOjOoZPZIhoGDnyycmy33JJh/3BzBYzvLcwc9791gnDd/ypphWaDHNqlCz+9gD77T wHSajMXmdj8wF7/jTgjnvKrTikdNUdidZ54/IFcrIlapHpYPzkI82nkd2SW/kWJ22DoQ HV6g==
X-Gm-Message-State: APjAAAWSpkMJEeXVZ904APu0hT4PXJaMhA7oAlmIPIZnveYanoxtgJ6n iUTdmzJ9k+XuVfpdVZBPbxYUxQ==
X-Google-Smtp-Source: APXvYqw/AyjEKlaxum4GeeB0m0uxV15w9gche4YKKXU5Z9l78QXuwnSxFoKnDC7n5iyHaNPfWGaTnw==
X-Received: by 2002:ac8:3907:: with SMTP id s7mr32736808qtb.374.1562172612260; Wed, 03 Jul 2019 09:50:12 -0700 (PDT)
Received: from ?IPv6:2001:470:c1a2:1:a062:1585:ff05:9bdc? ([2001:470:c1a2:1:a062:1585:ff05:9bdc]) by smtp.gmail.com with ESMTPSA id f19sm1154978qtq.5.2019.07.03.09.50.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jul 2019 09:50:11 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <2F8E5587-BEA9-4353-8699-115476260889@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0408F0C0-9E31-432D-8475-81E8C5EF1779"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Effective discourse in the IETF
Date: Wed, 03 Jul 2019 12:50:09 -0400
In-Reply-To: <0D8EF53D-7ADA-4641-A8D0-47FB0BDA9F38@akamai.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
To: "Salz, Rich" <rsalz@akamai.com>
References: <0D8EF53D-7ADA-4641-A8D0-47FB0BDA9F38@akamai.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Zno4neOD1awyaX25IGvfLHq2P0o>
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: Wed, 03 Jul 2019 16:50:22 -0000

On Jul 3, 2019, at 12:27 PM, Salz, Rich <rsalz@akamai.com> wrote:
> The world has moved on, and that’s a good thing. What used to be acceptable in terms of communication, isn’t; the bar has been raised. If the IETF wants to draw from global membership, it’s going to need to modify (and/or mollify) behavior that used to be acceptable. There is a whole wide world of cultures and genders that can, and should, have something to say about how to make the world better, and *we need to be nice* and *we need to be welcoming.* That doesn’t mean we have to accept poor technical solutions, but we can and should do a better job talking to each other.

To be clear, Rich, the reason I shared those books is that I think the IETF would benefit greatly from some of us who are vocal reading them.   I certainly benefited from reading them.   I am not suggesting that we go back to the bad old days of excusing deliberate rudeness.

I think we do need to be nice and welcoming, but we also need to speak up when we see something happening that seems wrong.  When that speech is dismissed, the result of this is that the speaker has no choice but to be silenced or speak louder.   If we ignore this aspect of the feedback cycle, the only possible outcome is that unwanted speech will be suppressed, either through self-censorship or through PR-action once the volume gets too high.

I took a course last year called the altMBA where all we did was write, criticize each other, and then reflect on the criticism.   Okay, that’s a gross oversimplification, but the point is that the value of that cycle was immense.  When people got up their courage and really offered generous criticism, which included saying things like “this doesn’t make sense to me” and “I don’t think you are right about this,” it was incredibly useful.   We were explicitly told to expect this kind of criticism, and requested to offer it, and that’s why it worked.   We have to encourage both sides of the criticism loop, not just one.

I don’t mean that the IETF needs to turn into the altMBA, but I hear a lot of people really completely ignoring the responsibility that participants have when they are being criticized, and just talking about the responsibilities of critics.  And not even talking about the importance of criticism.  That’s not going to work.  I think we could benefit by thinking about this more seriously, and not just sloganing about it, although I will make my attempt as well:

Yes, we can and should do a better job of talking to each other.  But that’s a shared responsibility.