Re: [Last-Call] Last Call: BCP 83 PR-Action Against Dan Harkins

Rob Sayre <sayrer@gmail.com> Wed, 05 October 2022 05:20 UTC

Return-Path: <sayrer@gmail.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF865C14CE36; Tue, 4 Oct 2022 22:20:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5C3ugYttHxx8; Tue, 4 Oct 2022 22:20:18 -0700 (PDT)
Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8009DC1524C0; Tue, 4 Oct 2022 22:19:54 -0700 (PDT)
Received: by mail-ej1-x634.google.com with SMTP id bj12so33076151ejb.13; Tue, 04 Oct 2022 22:19:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=uuO6or5fk5PtVRiUvCDuxkI2UeSYs7XrZr1gQPlZ7eg=; b=Ix/iudCvgzxOSHDSLbv/LPYmiC8dGbsPRQRLDP5P77k88e0rqGfgMNODLoEYszC8ks wGVsXLByW1vyIzZHcGm+G2R+IAyPecYv4Pqm3lFmhizlncHO2lgFH4IY7Crpu6XrMA8m nZQbZVNBVnHaIwRvllcSL2U7VS6khC9LFCuA5cQonjuYctOHcFDd44tfjDgkKYtq5i/w lfzl0T4imiCe7xj3/Z+PClnK/gpMFJy2MCAHyY6Xx9uF1Pup4uir4fxShqFdlRapxO3G 4pOfaXvFPZ2T4oZbpb0+fnPoZnSzCGSgIYhGjwBgDzcbeveuRLFvf0YBdEJnHASZoOGZ a8IQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=uuO6or5fk5PtVRiUvCDuxkI2UeSYs7XrZr1gQPlZ7eg=; b=E9aIsbPYUekX2ByXhNI0aLN7f9LchjF/p6kKlMrkIfTgfyGDK1G05BxXofOsu2cPPZ imWPrPLaPTlcoR3W7RLrV0Qg0f2OpSt7YbW7/sxGTcPj0JkN+SPHvWDgGYR1t8ANNBsh awx9v9Uewj6ImRKeKUXEcrqJtSzm2dtTMIFWYJhRFEoP5LNG47X/v47puleqvJpvcEqR SP9xmO1/EI08FqOrimJCvJbXDggFBwDSXR8UAdA1Z+3B+8h5FtkquPMkA1SYSLndcgzZ fnjA4kwbbqxOmOxCOeQNiTjNsEhVSucfZgyiXnD00yd+wYB/B0SVlQ2+0H4osIv+T7J4 28sQ==
X-Gm-Message-State: ACrzQf2HGYKDxTBQmnSDp53Knv7SEo+s64Btni28HDs8Wsy6yQnIe9Xk Msxf8+vqvlCPQ9cq2bscMlJe8nJ2997aVgk6Rj3qdtOz
X-Google-Smtp-Source: AMsMyM7e1B0+YhGv/geQEBlKVrNprqE/Y+Z1+lAKE7Eh8qTjcaSCGssUKulKgrKDquu/CMwA6GJBnnMwy0uBcXauHuo=
X-Received: by 2002:a17:906:9fc1:b0:761:9192:504f with SMTP id hj1-20020a1709069fc100b007619192504fmr22401591ejc.116.1664947192855; Tue, 04 Oct 2022 22:19:52 -0700 (PDT)
MIME-Version: 1.0
References: <CFE25E25-D131-468E-9923-80350D6216F3@ietf.org> <2cb88b4b-b49c-d703-81b1-9862e4dcbc03@huitema.net> <A7C18CAE-D402-4982-9B3D-4014AE231C7F@nostrum.com>
In-Reply-To: <A7C18CAE-D402-4982-9B3D-4014AE231C7F@nostrum.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Tue, 04 Oct 2022 22:19:41 -0700
Message-ID: <CAChr6SzpnbuuQmhfpa+XJf_jGSnXMKE7iucFW0byPu9wtFBy5Q@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: Christian Huitema <huitema@huitema.net>, IETF Chair <chair@ietf.org>, last-call@ietf.org
Content-Type: multipart/alternative; boundary="00000000000000030205ea42bac8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/zZyJZAMolEv0wPsGBZo6_IU0r2A>
Subject: Re: [Last-Call] Last Call: BCP 83 PR-Action Against Dan Harkins
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2022 05:20:19 -0000

Well, in this message, from the PR action, he just calls me stupid.

https://mailarchive.ietf.org/arch/msg/gendispatch/68a4amMa1aiaRUPzPGgXdiY9gHg/

I’m not stupid.

thanks,
Rob

On Tue, Oct 4, 2022 at 22:06 Ben Campbell <ben@nostrum.com> wrote:

> I have, for the last several days, been trying to compose a response, and
> haven’t gotten it right yet. But Christian expressed it perfectly. That is,
> I would support the PR-action, but I have reservations. It is not clear to
> me that the growing consensus separates "unpopular opinions" from the
> "abusive messaging patterns”.
>
> Don’t get me wrong; I think there is enough to support the PR-Action based
> strictly on the latter. But Lar’s message could be interpreted to also be
> concerned with the former. I would like the IESG to clarify the distinction
> and draw some bright lines.
>
> Ben.
>
> > On Oct 4, 2022, at 11:19 PM, Christian Huitema <huitema@huitema.net>
> wrote:
> >
> >
> > On 9/29/2022 9:15 AM, IETF Chair wrote:
> >> Following community feedback after various incidents, as documented
> below, the
> >> IESG has initiated a posting rights (PR) action that would restrict the
> posting
> >> rights of Dan Harkins, as per the procedures found in BCP 83 (RFC 3683).
> >> Specifically, his posting privileges to these lists would be suspended:
> >>
> >> * admin-discuss
> >> * gendispatch
> >> * ietf
> >> * terminology
> >>
> >> In the IESG's opinion, this individual has a history of sending emails
> that are
> >> inconsistent with the IETF Guidelines for Conduct (RFC 7154) and thereby
> >> "disrupt the consensus-driven process" (RFC 3683). Among these are
> contributions
> >> that:
> >>
> >> * Express racism in the form of denying, belittling, and ridiculing
> anti-racist
> >>   sentiment and efforts
> >>
> >> * Are rude and abusive, and often amount to insulting ridicule
> >
> > I understand that that the IESG want the "rude and abusive" behavior to
> stop. I am however concerned that the action as written doesn't distinguish
> clearly between censoring unpopular positions and censoring abusive
> messaging patterns.
> >
> > I looked at Dan's posts listed in the last call, and I find a mix of
> reasonable arguments followed by attacks, with quite a bit of trolling.
> Take for example
> https://mailarchive.ietf.org/arch/msg/gendispatch/i-d7HlWgrkmrVlC7JZQSXDwIJCQ/.
> It argues that a word like "master key" is an established term of the art
> whose origin is not tainted by racism, and that the IETF (or the IEEE)
> should not attempt a systematic replacement. Whether one agrees or not,
> that's a reasonable argument during a discussion of terminology. But then,
> the message goes on with a rant about the political priorities and personal
> ethics of the proponents of such replacements, and the IETF can do without
> these kind of attacks. It can also certainly do with the kind of trolling
> found in
> https://mailarchive.ietf.org/arch/msg/gendispatch/-On8AHrdnnCMlJOOyb1M1nlYMpk/,
> in which Dan pretends to be offended by the use of the word "native" in
> some computer languages.
> >
> > The IESG should clarify that unpopular opinions, per se, are OK. We need
> many voices in any debate. Indeed, in the terminology debate, the IETF
> eventually adopted the NIST guideline. This was significantly different
> from the original proposal, but probably closer to IETF consensus.
> >
> > I am concerned that the sentence about "expressing racism by denying
> anti-racist sentiment" can be misinterpreted, or misused. Clearly,
> attacking or belittling people because of their race, religion, sexual
> practices or culture has no place in the IETF. Personal attacks against
> proponents of specific anti-racist actions is also wrong. But some
> proposals motivated by anti-racism may well be misguided. Like any other
> proposals, they should be debated based on their merits.
> >
> > I would like the IESG to rewrite its message and clearly indicate that
> they are censoring personal attacks, ridiculing and trolling, but not
> censoring the debate itself.
> >
> > -- Christian Huitema
> >
> > --
> > last-call mailing list
> > last-call@ietf.org
> > https://www.ietf.org/mailman/listinfo/last-call
>
> --
> last-call mailing list
> last-call@ietf.org
> https://www.ietf.org/mailman/listinfo/last-call
>