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

"Bless, Roland (TM)" <roland.bless@kit.edu> Mon, 03 October 2022 11:31 UTC

Return-Path: <roland.bless@kit.edu>
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 EC902C1522CD; Mon, 3 Oct 2022 04:31:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, 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
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 N1QiqaOIbXsd; Mon, 3 Oct 2022 04:31:29 -0700 (PDT)
Received: from iramx1.ira.uni-karlsruhe.de (iramx1.ira.uni-karlsruhe.de [IPv6:2a00:1398:2::10:80]) (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 17039C14CF0B; Mon, 3 Oct 2022 04:31:28 -0700 (PDT)
Received: from [2a00:1398:2:4006:5c96:cb69:35c1:81be] (helo=i72vorta.tm.kit.edu) by iramx1.ira.uni-karlsruhe.de with esmtpsa port 25 iface 2a00:1398:2::10:8 id 1ofJfP-0000dU-PC; Mon, 03 Oct 2022 13:31:23 +0200
Received: from [IPV6:::1] (ip6-localhost [IPv6:::1]) by i72vorta.tm.kit.edu (Postfix) with ESMTPS id 82644D00164; Mon, 3 Oct 2022 13:31:23 +0200 (CEST)
Message-ID: <873f2809-dd04-fe10-724b-567ac898782b@kit.edu>
Date: Mon, 03 Oct 2022 13:31:23 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.11.0
Content-Language: en-US
To: last-call@ietf.org, IETF Chair <chair@ietf.org>
References: <CFE25E25-D131-468E-9923-80350D6216F3@ietf.org>
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
In-Reply-To: <CFE25E25-D131-468E-9923-80350D6216F3@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-ATIS-AV: ClamAV (iramx1.ira.uni-karlsruhe.de)
X-ATIS-Checksum: v3zoCAcc32ckk
X-ATIS-Timestamp: iramx1.ira.uni-karlsruhe.de esmtpsa 1664796683.819160918
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/RbNE7Fd4Ey1qJiVmEyVh9mlP94Q>
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: Mon, 03 Oct 2022 11:31:34 -0000

Hi,

I reviewed most of the cited emails and support the IESG's opinion as
well as the PR action. I think that this has been overdue and his
reactions here on this list are more than just a confirmation that this
is actually required.

Regards,
  Roland

On 29.09.22 at 18:15 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
> 
> (Links to examples of such emails sent to the lists above during the last two
> years are provided at the end of this email.)
> 
> Multiple attempts have been made to enter into a private discussion with this
> individual, both by IESG and community members, to communicate disquiet with his
> conduct on the lists. These attempts to restore respectful and courteous conduct
> on the lists have been rebuffed with communication that can be considered both
> antagonistic and hostile, and the pattern of behavior observed has continued.
> 
> The IESG also notes that the following actions have already been taken in
> response to the individual's actions:
> 
> * Two I-Ds were removed from the public archive due to their offensive nature:
>    https://datatracker.ietf.org/doc/html/draft-les-white-intersectional-dots
>    https://datatracker.ietf.org/doc/html/draft-les-white-tls-preferred-pronouns
>    (following these links displays the tombstone notice explaining their removal)
> 
> * His posting rights were restricted on the admin-discuss mailing list:
>    https://mailarchive.ietf.org/arch/msg/admin-discuss/ZANH2VPN-U8VMvvOWLb5l03FdCs/
> 
> * A final public warning was issued on the gendispatch mailing list:
>    https://mailarchive.ietf.org/arch/msg/gendispatch/68a4amMa1aiaRUPzPGgXdiY9gHg/
> 
> None of the attempts to discuss his participation style or warn the individual
> have led to any improvements. The IESG therefore believes that a PR action is
> the correct response to his continued problematic behavior across a number of
> different lists.
> 
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> last-call@ietf.org mailing lists by 27 October 2022. Exceptionally, comments may
> be sent to iesg@ietf.org instead. If sending private feedback to the IESG,
> please indicate if you would be open to having your comments anonymized and
> shared in a summary.
> 
> Please note: Comments should be limited to the criteria described in BCP 83,
> notably on whether the individual in question has engaged in postings that are
> "unprofessional commentary, regardless of the general subject" in a manner
> disruptive enough to warrant this action.
> 
> Lars Eggert
> IETF Chair, on behalf of the IESG
> –-
> 
> Examples of problematic emails during the last two years include:
> 
> * https://mailarchive.ietf.org/arch/msg/gendispatch/zdq3F0PV40Cyw5ooj0orOWaYyUw/
> * https://mailarchive.ietf.org/arch/msg/gendispatch/i-d7HlWgrkmrVlC7JZQSXDwIJCQ/
> * https://mailarchive.ietf.org/arch/msg/gendispatch/YhPI9zZ_3xfidt5V-ORRnET36yY/
> * https://mailarchive.ietf.org/arch/msg/gendispatch/B33zk8VfOYt4b4Cj-kIHXG3AXdg/
> * https://mailarchive.ietf.org/arch/msg/gendispatch/d3iDS4WNkCJA3aMFnX2HjP4tsps/
> * https://mailarchive.ietf.org/arch/msg/gendispatch/-On8AHrdnnCMlJOOyb1M1nlYMpk/
> * https://mailarchive.ietf.org/arch/msg/terminology/n6UMvDuYLKmmvpP1ajICFvf634M/
> * https://mailarchive.ietf.org/arch/msg/terminology/QCdjDbokmlARcwVqQ1TV3Rlz7eQ/
> * https://mailarchive.ietf.org/arch/msg/terminology/X6OF0MBKAzyLhYaAfAxS6srXRNw/
> * https://mailarchive.ietf.org/arch/msg/terminology/idJhG1MsLmKHyRlaAafcW2JF6Z8/
> * https://mailarchive.ietf.org/arch/msg/ipsec/LoGSVatZ4EsYRq4K52rmvRZTndk/
> * https://mailarchive.ietf.org/arch/msg/ietf/pl2lVqhtF4Z-0YuTjhCOmdyi1qE/
> * https://mailarchive.ietf.org/arch/msg/ietf/DFgnF_j8py_eMBGI1IUFdMahTKw/
> * https://mailarchive.ietf.org/arch/msg/terminology/T3oCpY3BbTNLXWAWsCnFvahRLUQ/
> * https://mailarchive.ietf.org/arch/msg/admin-discuss/xLuz4WTCm5ibIiMVN5ID8OWsCI0/
>