Last Call: BCP 83 PR-Action for Timothy Mcsweeney
IETF Chair <chair@ietf.org> Sat, 08 June 2024 14:40 UTC
Return-Path: <chair@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF93C14F691; Sat, 8 Jun 2024 07:40:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Chair <chair@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Last Call: BCP 83 PR-Action for Timothy Mcsweeney
X-Test-IDTracker: no
X-IETF-IDTracker: 12.15.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171785763936.33553.13380053453419884540@ietfa.amsl.com>
Date: Sat, 08 Jun 2024 07:40:39 -0700
Message-ID-Hash: SAAZR2G7EW4D2PZIBRYPMOWZZMYXYLP2
X-Message-ID-Hash: SAAZR2G7EW4D2PZIBRYPMOWZZMYXYLP2
X-MailFrom: chair@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: last-call@ietf.org
X-Mailman-Version: 3.3.9rc4
Reply-To: last-call@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/h8fLHUoBsu4kwBytW1wIfTCqV9U>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
The IESG has initiated a posting rights (PR) action that would restrict the posting rights of Timothy Mcsweeney per the procedures in BCP 83 (RFC 3683). Specifically, his posting privileges to the ietf@ietf.org discussion list would be suspended. In the IESG's assessment, this individual’s recent post [1] was an egregious example of misogynistic harassment inconsistent with the IETF Guidelines for Conduct (RFC 7154), IETF Anti-Harassment Policy [2], and “abusive of the consensus-driven process” (per Section 2 of RFC 3683). The IESG recognizes the role of a progressive disciplinary process, to include the escalatory moderation practices of the IETF Discussion list moderators per RFC 9245 and [3]. Additionally, the IESG appreciates the role of the Ombudsteam and the IETF Anti-Harassment Procedures (RFC 7776). However, the IESG feels that this particular response of a PR is warranted in this situation. The IESG plans to make a decision and is soliciting final community comments on this action. Please send substantive comments to the last-call@ietf.org mailing lists by 6 July 2024 [4]. 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. Note: Comments should be limited to the criteria described in BCP 83 (Section 1 of RFC3683), notably on whether the individual in question has engaged in behavior that is "unprofessional commentary, regardless of the general subject" in a manner disruptive enough to warrant this action. Roman Danyliw IETF Chair, on behalf of the IESG — [1] https://mailarchive.ietf.org/arch/msg/ietf/NjNux65wUXXQaMmgENuwoopZPjI/ [2] https://datatracker.ietf.org/doc/statement-iesg-ietf-anti-harassment-policy-20131103/ [3] https://github.com/ietf/Moderators/blob/main/sop.md [4] PR actions require an IETF Last Call (IETF LC). The four-week duration of this IETF LC is consistent with that of an AD-sponsored document action.