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

Colin Perkins <> Thu, 06 October 2022 09:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1549DC14F741 for <>; Thu, 6 Oct 2022 02:00:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Status: No, score=-7.107 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, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iMJx62PSXypG for <>; Thu, 6 Oct 2022 02:00:13 -0700 (PDT)
Received: from ( [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id A5FAAC14CF08 for <>; Thu, 6 Oct 2022 02:00:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=mythic-beasts-k1; h=Date:Subject:To:From; bh=EgHSx6ve39DYgrwVWKubHLZRv4WL4hgcPROBdGI/GwI=; b=qYKVyBhg+fs6TE7L7njgJjXsCe LRio//J/nt6zruVDXRIPDLVtv2pKmmstw8Q5MKvG8RoOceU0GLrYzjvC5KAcDoIDWl9uYAvCIfKQg oYZovRHlJhyXJgvyk064gR5yFjBraUMFySyXDg2cWegsrTYqC+aPbQNV7JC01a1X8kLYys3pGoDu8 NmB9e3qNGekbINM/ZJBZlMUFCd9gUXKMGhrItkXUsPB3zBV6hjX5AoYJF3pwfLlVJWjB3MWvsieA4 Ro+jn+AOfxrJ5gY6yxslKA8Poqjv9fcRFyaqeCPGZtxyAov8grxcnjpWrK3A7Hlry8CIAGsADzCka qfMnyovA==;
Received: from [] (port=36116 helo=[]) by with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <>) id 1ogMjj-001nqI-67; Thu, 06 Oct 2022 10:00:11 +0100
From: Colin Perkins <>
To: tom petch <>
Date: Thu, 06 Oct 2022 10:00:05 +0100
X-Mailer: MailMate (1.14r5920)
Message-ID: <>
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <4D6C23FCA0D271F939E9E266@PSB> <>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
X-BlackCat-Spam-Score: 24
Archived-At: <>
Subject: Re: [Last-Call] Last Call: BCP 83 PR-Action Against Dan Harkins by the IETF
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Last Calls <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 06 Oct 2022 09:00:18 -0000


On 5 Oct 2022, at 9:55, tom petch wrote:

> On 03/10/2022 23:22, John C Klensin wrote:
>> --On Tuesday, October 4, 2022 09:02 +1300 Brian E Carpenter
>> <> wrote:
>>> Keith, you wrote:
>>>> Whether or not it's warranted, it's clearly a personal attack
>>>> on Dan.
>>> No. It's directed very explicitly at a particular pattern of
>>> behaviour on some specific mailing lists. It doesn't say that
>>> he may no longer contribute, say, to Security Area activities.
>> Brian, while I agree about the "pattern of behavior" my
>> understanding of the BCP, Marshall's intent at the time, and
>> what we have done since, Dan (or anyone else similarly
>> sanctioned) could participate on other mailing lists and in
>> other activities but only as long as the maintainers of those
>> lists felt his behavior was appropriate to their work and either
>> represented a change of behavior from the behaviors cited in the
>> PR-action proposal.   If they concluded they were seeing the
>> same patterns of disruption-causing behavior that caused the
>> PR-action for the IETF list and other lists, they could ban him
>> there too and do so without further warnings, etc.
> Indeed.
> When I read the first message of this thread, I thought that the person cited was a familiar name but from the IRTF (and from the Security Area, not from the mailing lists that are specified).  Since this is an IETF action, then I imagine that it would be up to the IRSG to decide whether or not action is warranted for IRTF lists.  I see no such sign - I do not know if the IRTF has any equivalent procedure.  Certainly in other matters, such as determining consensus, I see the IRTF as being more encompassing than the IETF.

The RG Chairs are responsible for moderating the research group lists, with support from the IRTF Chair.

This PR-Action is by the IESG and is to restrict posting to a specific set of IETF mailing lists.