+1 to Rob. I fully support the PR action here as originally written by the IESG.
Additionally, I also support the expansion to other lists as proposed by Tim.
Tim's latest messages [1,2,3] add to an already large body of unacceptable
behavior, and demonstrates his unwillingness to change.
David (no hats)
I support this PR action. Same justification as Lars.
I also support Tim’s proposal here to be banned from all IETF lists, here:
[Last-Call] Re: Last Call: BCP 83 PR-Action for Timothy Mcsweeney (ietf.org)
Regards,
Rob
Hi,
thank you for taking this step. This individual’s participation has not been in good faith for a number of years at least, and most if not all of their emails I have seen have the intent to cause disruption and division.
Thanks,
Lars
--
Sent from a mobile device; please excuse typos.
> On Jun 8, 2024, at 23:42, IETF Chair <chair@xxxxxxxx> wrote:
>
> 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@xxxxxxxx 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@xxxxxxxx mailing lists by 6 July 2024 [4]. Exceptionally, comments may be sent to iesg@xxxxxxxx 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.
>
> _______________________________________________
> IETF-Announce mailing list -- ietf-announce@xxxxxxxx
> To unsubscribe send an email to ietf-announce-leave@xxxxxxxx
--
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx
--
last-call mailing list --
last-call@xxxxxxxx
To unsubscribe send an email to
last-call-leave@xxxxxxxx
--
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx
