Hi Ted,
On Mon, Jun 10, 2024 at 10:33 PM Ted Lemon <mellon@xxxxxxxxx> wrote:
I'm a bit confused: I thought that we also had a 6-month ban. Am I remembering this wrong? IIRC there was one applied to a certain expert on distributed naming databases years back.
There are two independent actions.
We have the ietf@xxxxxxxx moderator team's action [1] that is already in effect for 14-days as a Level 2 escalation. The moderator's team SOP [2] stops at L2 for now.
There is the independent PR-action last-call [3] which is ongoing, IESG will make a decision and after that there could be a ban for at least 1 year. This is as per BCP 83.
Hope this helps!
Thanks!
Dhruv
--On Mon, Jun 10, 2024 at 12:42 PM Chris Box <chris.box.ietf@xxxxxxxxx> wrote:On Mon, 10 Jun 2024 at 17:12, Michael Douglass <mikeadouglass@xxxxxxxxx> wrote:The response to that offensive posting has left me near speechless. If that didn't warrant an immediate and permanent ban what does?
This just reinforces the view that the IETF does not take this kind of behavior seriously.
Michael if I understand you correctly, your position is that the standard operating procedures should not max out at a 14-day posting restriction, as they currently do.To be clear, are you asking for a Level 3 (or perhaps 4) which implements a posting restriction of indefinite duration?--Chris
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
