[Mod-discuss] Re: [TLS] Re: PR-Action Approved: Ken Kubota

[Chris Hughes <[e-mail]>]

I think Ken did their job... Rational minds will clearly not go the
non-standards approach and look for better alternatives. It's happened
before.

On Fri, Oct 16, 2026 at 7:06 AM Alexander Burke <alex=
[e-mail]> wrote:

> Hello,
>
> Perhaps George R. R. Martin said it best: "When you tear out a man's
> tongue, you are not proving him a liar, you're only telling the world
> that you fear what he might say."
>
> As for words of my own, I don't really have any that accurately describe
> how I feel about how the TLS mailing list and related processes are run,
> but it certainly doesn't make me want to try to contribute; I'll focus
> my energy on the other SDOs I work with instead. It's a shame.
>
> So long, and thanks for all the fish.
>
> --
> Alexander Burke, CISSP, CIPP/E, CIPM, FIP
>
>
> On 2026-10-16 07:49, IETF Chair wrote:
> > # Last Call Result
> >
> > The IESG received feedback from the community in response to the IETF
> Last Call on the proposed RFC 3683 PR-action for Ken Kubota [1]. After
> evaluating this feedback, the IESG has concluded there is rough consensus
> to proceed with the PR-action.
> >
> > Per the terms described in Section 2 of RFC 3683, the administrators of
> the ietf, tls, sshm, and mod-discuss lists are directed to suspend Ken
> Kubota’s posting privileges.  Additionally, this same section advises
> “maintainers of any IETF mailing list may, at their discretion, also remove
> posting rights to that IETF mailing list.”
> >
> > # Highlights from the Community Feedback
> >
> > The IESG thanks the community for providing this feedback and highlights
> the following feedback.
> >
> > ## Additional Justification for Action
> >
> > In addition to the messages outlined in [1], the following additional
> message was requested during the IETF Last Call to be added to the record
> motivating this PR action by the community:
> >
> > *
> https://mailarchive.ietf.org/arch/msg/ietf/OrvxKgjrEOMb95KAWoJYSilDxiY/
> >
> > ## Recommendations for PR actions
> >
> > The community made the following recommendations regarding PR actions:
> >
> > * Ensuring that the subject of the PR action is directly notified in
> addition to using the [e-mail] mailing list.
> >
> > * Harmonizing active PR actions with the new RFC 9945-defined procedures.
> >
> > ## Implementing RFC9945
> >
> > The community expressed an urgency to fully implement the procedures of
> RFC 9945.
> >
> > # Conclusion
> >
> > The IESG reiterates that the purpose of this action is to minimize
> disruptive behavior by a single participant.  The IESG also reaffirms that
> a diverse set of opinions in the standards process is both important for
> the IETF and actively encouraged.
> >
> > Per RFC 9945, the IETF Moderator Team [2] is authoring the first draft
> of the new moderation procedures.  For discussion about IETF moderation
> procedures use [e-mail] [3].
> >
> > Roman Danyliw
> > (as IETF Chair, for the IESG)
> >
> > [1]
> https://mailarchive.ietf.org/arch/msg/last-call/JZXmLcVXUPtYWfMC2MMpPVOsTNM/
> > [2] https://datatracker.ietf.org/group/ietfmoderators/about/
> > [3]
> https://mailarchive.ietf.org/arch/msg/ietf-announce/kVletyOqMHSiXpsLAeqaB4CPsdQ/
> > _______________________________________________
> > TLS mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
>
> _______________________________________________
> TLS mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>