Received: from mail-qv1-xf34.google.com (mail-qv1-xf34.google.com
 [IPv6:2607:f8b0:4864:20::f34])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange x25519 server-signature ECDSA (prime256v1) server-digest
 SHA256)
	(No client certificate requested)
	by mx.ietf.org (Postfix) with ESMTPS id 73CF946
	for <ietf@ietf.org>; Sun, 15 Nov 2026 17:20:43 +0000 (UTC)
Authentication-Results: mx.ietf.org;
	dkim=pass header.d=gmail.com header.s=20260707 header.b=a0d7xs+5;
	spf=pass (mx.ietf.org: domain of abdussalambaryun@gmail.com designates
 2607:f8b0:4864:20::f34 as permitted sender)
 smtp.mailfrom=abdussalambaryun@gmail.com;
	dmarc=pass (policy=none) header.from=gmail.com;
	arc=pass ("google.com:s=arc-20260327:i=1")
Received: by mail-qv1-xf34.google.com with SMTP id
 6a1803df08f44-91ea2e29d90so46263696d6.1
        for <ietf@ietf.org>; Sun, 15 Nov 2026 09:20:43 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1794763237; cv=none;
        d=google.com; s=arc-20260327;
        b=UpM3Bor1JgTSg1xKmEV5WsM4nfQp8ialgU5F4eP25YDRGT3yqQAofZ6QBATRZBz+hE
         AM/98kqs3gTwJGUSpQhZIlYrWoM6wn3ifO/Tcll2FWIUQjWOm+NuAaK/TblSIPhtBxdb
         GC5ermWtQQnbRk9jFGbK3bRmoZJPo+wONimmUnpKK/ls43+6aUVxFjn8HMRMU2LrCgh9
         I1sefpwiIK/eykpJqSkLcVxRtdU8kreRRh28l9au6YNyNFJd1ErYjvuyNpi5ZgWkh4aG
         /MkIW4kQqdF5rA5UtHvZ574KksJqQwyyFu1NSSRDRNMLfVU0xH767WVTxbT1wTS4Wq8M
         9DPA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com;
 s=arc-20260327;
        h=cc:to:subject:message-id:date:from:in-reply-to:references
         :mime-version:dkim-signature;
        bh=xmergLFqel4UivFMw74nsO8YY8sKu28lvhnkUw/H5/Q=;
        fh=+UrMnVSgTkgQv3j67NWdi/fehkBwpkM0Hzzniis0Wcw=;
        b=X1Qj4ddDIov4Gq86aMAO4B4W/+skITDdkXTjt3iifxTEil5l63Tj1Ap8705PmRfQOD
         M67RyEgYHKfBZVyWRoBSihzsYA3vVd4rjqFgVv0u4BdHuoxCT1iz19yEZpV9+JYdkiHa
         sfYCNXBeZtaVKrP99SeYDfslvXhGkdqmw93kRY9SkBq5kcH5HShs7mEQhT1Zcuqv63f3
         JOHXHsxmhBsY8nJKngT/ipKZda7HdC5SvL1hlVoUDBzgNQmibfvot2AjPq6x33Fm/6ZA
         8fYu0l5oDGTI3pXtUf7++ectDmA3oJOEfQzv7hSjgQcQvdeE5ilQh9PqMF9Bp6SIN5d9
         kmoQ==;
        darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20260707; t=1794763237; x=1795368037; darn=ietf.org;
        h=content-type:cc:to:subject:message-id:date:from:in-reply-to
         :references:mime-version:from:to:cc:subject:date:message-id:reply-to
         :content-type;
        bh=xmergLFqel4UivFMw74nsO8YY8sKu28lvhnkUw/H5/Q=;
        b=a0d7xs+54fnnkmLCqzB0MzROD+CK7woveipxMcCEEGLmql8xEjr29A8NWuwUHs5Yiw
         OuGLL9/+U1aEYN9nhscjY+oYoREmb+9CQ3BoY+el6PyCEUk6CGdK0zp93L2rUGY/bS9u
         dI1IJ2YNPvvZ/H7CJfLbsVKeRGqVoNAl3tg+TVKmM4GzCUm9ygHk9bWZDfSNMjp5S5MG
         85gpFFKCR8ICT2BNEfo61TLyR0XE1H710vFto1X99aL0eMPGBMTlK8hwFYQWNefcuQja
         WuHfwwpboZkduSjQCgGopm7cSCqELp1k4rV92wHpN35vq0V4ubMAHgxlk2FNKz3LPh/A
         Iwyg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20260707; t=1794763237; x=1795368037;
        h=content-type:cc:to:subject:message-id:date:from:in-reply-to
         :references:mime-version:x-gm-gg:x-gm-message-state:from:to:cc
         :subject:date:message-id:reply-to:content-type;
        bh=xmergLFqel4UivFMw74nsO8YY8sKu28lvhnkUw/H5/Q=;
        b=hIO7idcM6ZZs8LjphwJ50MYysCIECQNW6f6Hc3L0G4et5VH4O1i8osj6+msanuTCtV
         1uTeHJSw0eo3gUQMnR4/6pD/gHMcGuxVBFSGz4czZHh0PwZjt9vR74bFZMFvvy6gPFbV
         xjX9dxq+2d9klhUS3lXoXX++j7Hu050xRtTlRvQVdrF/kla4yK3VsOnRkLDRmo5vq7ME
         EH8rrq/EQNvuMViHEMKJQPgsR5+vS1sYIie1TO3GHmGsWR79/EYALCVNvuVmuiatN2b/
         XWFOwmPB6g0tBKlpLvnzLrBUfjM3by2zPTdkTRSN1PRSQg5sF88eDQhBovbIeJG//SDj
         Lpgg==
X-Forwarded-Encrypted: i=1;
 AL+hErEXomaWxYw6/hSnypvHgi1Nq1U+uz2/Z7TNWYiWEFILffuC1kw4noIgUmNr8eT47vjh7ltF@ietf.org
X-Gm-Message-State: APuU4Z/zuGKIsVlRZEoWbCQq0kyBnfw23VYDdoLAZn/+QRwJmYelxM7k
	WXL/UGQoFNaGU8Zlvu4Ke0GQ0yA8EJFjq9UDnh+4mIrfC9sv0plak+OANxA3y5Ist0BHtcrsNko
	jqcVhSfBVhNFaG/0UBLdGeSZ/78NTvS2LTw==
X-Gm-Gg: AYBFou0fQTh4VwIjy5rUs7d0xGAcHq0xlTKdoIrMSW2nuQBCWpc4jspC3PsxlV9lIHn
	PcohRa3IEEMyjD+kLw+pcxju/BeZdDtlhRVXwsSCguVR7gDII0gm6wKSUcAeoIQjLRjh/qWPjOv
	IDq8RZCz4prgeEBvwOGFw332ICObAu5lxLKzfxIaDjNeipfnYt/LM5RE/A+4upkgFkBos4+/Xzg
	4p+K9QBARGD2pKzo5cfaE54gi8nK8OaOdvZE2ErMCl30f2cPwyJHFWfXyeuSsINoQtDUaGC/Dea
	pl5y1mzfxOaeHNXtT5WbNcdo8yFeLcAd9kmoQfKiIp1fM1DBWkKvrhBSqm1fuVuIzgkOGiymaxX
	79WoBgLDF9rMjP64n0GBlA4yumkUtJo3mlhE=
X-Received: by 2002:a05:6214:29e8:b0:91e:85d8:f3ee with SMTP id
 6a1803df08f44-91f2426de74mr118765756d6.3.1794763236476; Sun, 15 Nov 2026
 09:20:36 -0800 (PST)
MIME-Version: 1.0
References: <364e7c73-6146-4f86-9bf6-db5443c42e4a@app.fastmail.com>
In-Reply-To: <364e7c73-6146-4f86-9bf6-db5443c42e4a@app.fastmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Sun, 15 Nov 2026 19:20:23 +0200
X-Gm-Features: AclHuK8n9t28sZ8d2zEX499yPU06WFNGNMfITSyQ9VexWfOBdCjlDt0YVkac-WA
Message-ID: 
 <CADnDZ8_Q0=4s1Lw-jU0obBUFbDx+cuN+ZvqWRL81DheRkHveqw@mail.gmail.com>
Subject: Re: [Mod-discuss] Moderator Team Procedures - For Community Input
To: Bron Gondwana <brong@fastmailteam.com>
Content-Type: multipart/alternative; boundary="0000000000002a8dd8066053e144"
X-Spamd-Bar: -------------------
Message-ID-Hash: OO2UFUIXCD6DCU6TZTBDYOY7INMM2Z7L
X-Message-ID-Hash: OO2UFUIXCD6DCU6TZTBDYOY7INMM2Z7L
X-MailFrom: abdussalambaryun@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop;
 banned-address; header-match-ietf.ietf.org-0; header-match-ietf.ietf.org-1;
 header-match-ietf.ietf.org-2; header-match-ietf.ietf.org-3; emergency;
 member-moderation; nonmember-moderation; administrivia; implicit-dest;
 max-recipients; max-size; news-moderation; no-subject; digests;
 suspicious-header
CC: Moderation Discussion <mod-discuss@ietf.org>, ietf@ietf.org
X-Mailman-Version: 3.3.10
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list,
 intended for discussion of technical, procedural, operational,
 and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/ietf/HlOa0Z5eSNIcOpDrlO2O1dgIDys>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>

--0000000000002a8dd8066053e144
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Bron,

I tried to read the list or procedure, but it looks full of details,
and I think the moderator team can decide what is disruptive depending on
the situation. However, thanks for your message informing us of this, I
will agree on what the team decides because I believe it will be for the
best of all.

best wishes
AB

On Thu, Oct 22, 2026 at 1:57=E2=80=AFAM Bron Gondwana <brong=3D
40fastmailteam.com@dmarc.ietf.org> wrote:

> Hello IETF Community,
>
> Since being instantiated at the Vienna IETF, the Moderator Team has been
> refining our procedures.  Our planned timeline is:
>
>    1. Now until IETF127 - open up discussion of these procedures on the
>    mod-discuss list
>    2. At IETF127 - discussion in person with interested parties
>    3. After IETF127 - discuss feedback amongst ourselves and revise
>    procedures if needed
>    4. Later this year or early next year - ask the IESG to approve
>    procedures and set a date upon which they come into effect
>
> We hope that, at the latest, these procedures will be in effect by the
> start of IETF128.
>
> The procedures are published in Github here:
> https://github.com/ietf-moderators/procedures - I will also paste the
> procedures file at the end of this email.
>
> *Seeking feedback or clarifying questions in the following ways:*
>
>    - In public to the mod-discuss@ietf.org list
>    - In private to ietf-moderators@ietf.org (an alias to the 6 of us)
>    - As issues or pull requests on the Github repository.
>
>
> Regards, your Moderator Team (Bron, Chris, Martin, Mohit, Murray, Susan)
>
> Procedures follow:
> Introduction
> RFC9945 <https://www.rfc-editor.org/rfc/rfc9945.html> says that the IETF
> community will treat people with kindness and grace, but not endless
> patience. It sets up a policy for the moderation of disruptive
> participation across the IETF's various public contribution channels and
> discussion forums. It establishes guardrails for moderation and a moderat=
or
> team. This team is required to develop a set of moderation procedures and
> facilitate their consistent implementation with chairs and administrators=
.
> This document defines those moderation procedures.
> Scope
> These procedures apply to all public online IETF forums, as described in
> Section 3 of RFC9945: mailing lists, chat groups, and other systems that
> the IETF or its working groups have chosen to use, such as GitHub
> repositories, wikis, and issue trackers.
> They do not apply to the forums of the IRTF, the IAB, the RSWG, the RSAB,
> or the Independent Submission Stream, unless that body explicitly agrees.
> Some of those forums are hosted on IETF infrastructure, so the address of=
 a
> list is not always a reliable guide. The moderator team maintains the
> current list of forums in and out of scope in scope.md
> <https://github.com/ietf-moderators/procedures/blob/main/scope.md>, and
> updates it as other bodies opt in.
> ResponsibilitiesModerator team
> The moderator team can be contacted at ietf-moderators@ietf.org.
> Participants may use this address to report disruption, to ask for an
> incident to be rescinded or a sanction reduced, or to ask any question
> about these procedures. Administrators use it to notify the moderator tea=
m
> of reports and actions taken.
>
>    - Define these proposed procedures, with community input, for approval
>    by IESG
>    - Act as administrators of plenary lists
>    - ietf@ietf.org
>       - last-call@ietf.org
>       - Plenary session Zulip chat
>    - Act as administrator of last resort
>    - If there is no defined administrator
>       - If administrators are unresponsive
>       - In cases of disruption across multiple lists
>    - Provide training and guidance to administrators
>    - Maintain the incident register
>    - Respond to requests and perform actions in a timely manner (defined
>    as "SHOULD be within 48 hours, MUST be within one week").
>    - Revise these procedures based on experience, following the same
>    community input and approval process.
>    - Extend sanctions to multiple lists where appropriate
>
> Administrators
>
>    - Implement the approved procedures
>    - Record incidents, and the sanctions applied, in the incident registe=
r
>    - Notify moderator team of reports and actions taken
>    - May rescind their own incidents, and reduce the sanctions on them.
>
> Administrator proceduresIncidents
> An *incident* is a single occasion on which an administrator finds that a
> participant's conduct in an IETF forum was disruptive. The participant
> whose conduct it was is the *respondent* of that incident.
> What counts as disruption
> Disruption can take any of these forms.
>
>    - Uncivil commentary
>    - Attacking people
>       - Attacking groups of people
>       - Attacking an idea in an insulting or excessively hostile manner
>       - Clearly lacking in respect and courtesy (the expectations of
>       RFC7154 <https://datatracker.ietf.org/doc/html/rfc7154>)
>       - Inciting hate
>    - Messages unrelated to the list's purpose
>    - Behavior that hinders the work of the group
>    - Sealioning: the disingenuous action by a commenter of making an
>    ostensible effort to engage in sincere and serious civil debate, usual=
ly by
>    asking persistent questions of the other commenter. The questions appe=
ar as
>    an effort to learn, but degrade the progress of technical debate and t=
he
>    goodwill of the list participants. See the descriptions from
>    Merriam-Webster
>    <https://www.merriam-webster.com/wordplay/sealioning-internet-trolling=
>
>     and Wikipedia <https://en.wikipedia.org/wiki/Sealioning>.
>    - Astroturfing
>    - Messages containing confidential information
>    - Repeated inclusion of derivative rights notices
>    - As per the IESG statement
>       <https://datatracker.ietf.org/doc/statement-iesg-statement-on-clari=
fying-derivative-works-rights/>
>    - Messages containing slop
>
> Counting incidents
>
>    - A connected series of messages - one thread, or several messages
>    over a short period making the same disruption - is *one* incident,
>    not one per message.
>    - Incidents are counted per participant across the whole IETF, not per
>    list. An incident recorded by the administrator of one list counts whe=
n the
>    administrator of another list acts later.
>    - An *eligible incident* is one that has not been rescinded and whose
>    conduct occurred within the past five years. Only eligible incidents a=
re
>    counted.
>    - All forms of disruption share a single count. It does not matter
>    whether the earlier incidents were of the same kind as the one being
>    handled now.
>    - Every incident MUST be recorded in the incident register, and
>    notified to the respondent and to co-administrators.
>
> Incident register
> Incidents are recorded in the *incident register*, maintained by the
> moderator team.
> What the register records
> For each incident:
>
>    - An identifier
>    - The date of the conduct, and the date it was recorded
>    - The forum(s) in which it occurred
>    - The form of disruption
>    - The respondent
>    - The action-taker
>    - The sanction applied, if any: whether hold or ban, its duration, and
>    when it ends
>    - Whether it has been rescinded, by whom, when, and why
>    - Whether a sanction has been reduced, by whom, when, and why
>    - The private detail: the messages, the reasoning, and correspondence
>    with the respondent
>
> One human always takes the action, and is recorded as the *action-taker*.
> Where administrators decided jointly, one of them still takes the action
> and is the action-taker for that incident. They may name the others in th=
e
> private detail, but that grants no additional access.
> Datatracker accounts
> Incidents are recorded against the respondent's Datatracker account, not
> against an email address, so every address on that account shares a singl=
e
> incident count.
> If the respondent does not already have a Datatracker account, the
> moderator team creates one, linked to the email address from which the
> disruption came.
> If disruption from another address is identified as coming from the same
> person, the moderator team identifies their existing account and records
> the incident against it. The other address is not added to the account. I=
f
> the identification turns out to be wrong, the remedy is to rescind the
> incident.
> Who sees what
> Who Sees
> The action-taker, at the point of recording an incident the maximum
> sanction available for the respondent based on the sanction ladder
> The action-taker, the respondent, the moderator team, the IESG, and legal
> counsel the full detail of that incident
> Any respondent the history of incidents recorded against them, the
> maximum sanction available against them, and any current sanction in forc=
e
> The moderator team, the IESG, and legal counsel every incident, and every
> participant's incident count and history
> Once a year the moderator team publishes a report giving the number of
> incidents recorded in that year, with a count of each type and severity o=
f
> sanction applied and whatever commentary the team wishes to add.
> Rescinding an incident
> Rescinding an incident withdraws the finding: the incident is treated as
> never having been recorded. Any of the following may rescind an incident,
> acting alone and recording a reason:
>
>    - The action-taker, for their own incidents
>    - The moderator team
>    - The IESG
>
> No other administrator may rescind an incident, even a co-administrator o=
f
> the same forum who took part in the decision. They ask the moderator team
> or the IESG instead.
> The respondent may ask any of them to rescind an incident.
> A rescinded incident is no longer eligible: it is removed from the count
> and from the calculation of sanctions available against this respondent. =
It
> remains visible in full (marked rescinded) to the action-taker, the
> respondent, the moderator team, the IESG, and legal counsel.
> When an incident is rescinded, any sanctions currently in effect on the
> respondent are reviewed to see if they should be reduced or removed.
> If a public statement was made about the incident, whoever rescinds it
> sends a correction to the same forums, saying that the finding has been
> withdrawn, unless the respondent asks that none be sent.
> It is appropriate to rescind an incident when it is found that the
> determination of disruption was made in error. If the incident did occur
> but the respondent is determined to be willing to improve their behavior,
> then reducing the sanction (see below) is a better choice.
> A finding may also be in error because the respondent's account was
> compromised and the messages were not theirs. A hold may still be
> appropriate until the account is secured, and repeated compromises are a
> reason to keep it.
> Reducing a sanction
> Reducing a sanction lifts it, or brings its end date forward. It changes
> the sanction, not the finding: the incident stays in the register and sta=
ys
> eligible, and the sanction ladder is unaffected.
> Any of the following may reduce a sanction, acting alone and recording a
> reason:
>
>    - The action-taker, for their own incidents
>    - The moderator team
>    - The IESG
>
> As with rescinding, no other administrator may reduce a sanction;
> co-administrators ask the moderator team or the IESG.
> The respondent may ask any of them to reduce a sanction, for example by
> undertaking to change their behavior. Reduction is a grace and not a righ=
t.
> Whoever reduces a sanction notifies the respondent and the administrators
> of the affected forums. If the sanction is lifted immediately, follow
> "Removal of a sanction" below now; if its end date is brought forward,
> follow it on or before the new end date.
> Until the register exists
> The register has yet to be built. Until it is, the moderator team
> maintains the record, and an administrator handling an incident asks the
> moderator team what sanctions are available.
> Existing posting rights actions
> RFC9945 obsoletes the posting rights (PR) actions of RFC3683
> <https://www.rfc-editor.org/rfc/rfc3683.html>. When these procedures take
> effect, the moderator team handles each PR action listed on the IESG's PR
> actions page
> <https://www.ietf.org/about/groups/iesg/posting-rights-actions/> as
> follows:
>
>    - If the PR action was approved or last updated within the past five
>    years, record three incidents against its respondent in the register, =
each
>    dated on the date of that approval or update. A PR action always follo=
ws
>    several incidents of disruption, so the respondent does not start from
>    zero; their next incident is their fourth.
>    - If it was approved or last updated more than five years ago, record
>    nothing, as any incidents it represented would no longer be eligible.
>
> In either case, remove the restrictions the PR action imposed by setting
> the list default action for the respondent on every affected list, and se=
nd
> them a private message saying so and linking to this procedure.
> Requirements for the tools team
> The register must:
>
>    - Record each incident with the fields listed above.
>    - Provide a method for administrators, the moderator team, and the
>    IESG to create entries in the register, displaying the maximum sanctio=
n
>    available in days, and allowing entry of any number of days equal to o=
r
>    less than the maximum allowed.
>    - Either apply the recorded sanction automatically or provide
>    instructions on how to apply it, and remind the action-taker and the
>    administrators of the affected forums when it is due to expire.
>    - Record incidents against the respondent's Datatracker account, so
>    that counts are collected across all addresses on that account.
>    - Allow the moderator team to create a Datatracker account for a
>    respondent who has none, linked to the address from which the disrupti=
on
>    came.
>    - Allow the moderator team to record an incident from any address
>    against an existing account, without adding that address to the accoun=
t.
>    - Record exactly one action-taker per incident, and restrict the
>    private detail of an incident to the action-taker, the respondent, the
>    moderator team, the IESG, and legal counsel. Anyone named in the priva=
te
>    detail gains no additional access by being named.
>    - Allow the action-taker, the moderator team and the IESG to rescind
>    an incident, recording who rescinded it, when, and why.
>    - Allow the action-taker, the moderator team and the IESG to reduce a
>    sanction, recording who reduced it, when, and why, and notify the
>    respondent and the administrators of the affected forums.
>    - Compute each participant's count from eligible incidents only, so
>    that an incident leaves the count when it is rescinded or five years a=
fter
>    the date of the conduct, while the record is retained.
>    - Offer a five-year maximum for any incident occurring within one year
>    after the end of a previous five-year sanction, whatever the responden=
t's
>    count.
>    - When an incident is rescinded, remove it from every view except
>    those of the parties who see its full detail, recalculate affected cou=
nts,
>    reduce any sanction still in force to the recalculated maximum (or pro=
vide
>    instructions for same), notify the respondent and the administrators o=
f the
>    affected forums, and remind whoever rescinded it to send a correction =
if a
>    public statement was made.
>    - Display to the moderator team an aggregate count of incidents
>    recorded each year, by type and severity of sanction applied.
>
> SanctionsThe sanction ladder
> The number of eligible incidents, *including the one being handled*, sets
> the maximum sanction available. The incident register computes this and
> tells the acting administrator the maximum. Any sanction up to and
> including that maximum may be applied - or none at all. In general, the
> minimal action necessary should be taken.
> Eligible incidents (including this one) Maximum sanction
> 1 notice only
> 2 7 days
> 3 28 days (1 month)
> 4 90 days (3 months)
> 5 365 days (one year)
> 6 or more 1825 days (5 years)
> A sanction is a *hold for moderation* or a *ban*, of any duration up to
> the maximum. No sanction may exceed five years. A respondent is immediate=
ly
> eligible for another five-year sanction if an incident occurs within one
> year after the end of a previous five-year sanction, whatever their
> incident count at that time.
> A single incident, however serious, unlocks nothing beyond a notice. Wher=
e
> conduct is serious enough that the ladder is plainly an inadequate
> response, refer the matter to the Ombudsteam (if it may be harassment
> <https://datatracker.ietf.org/doc/statement-iesg-ietf-anti-harassment-pol=
icy-20131103/>)
> or raise it with the IESG. These procedures do not give administrators a
> route around the ladder.
> Choosing between a hold and a ban
> A hold for moderation is the default: the respondent's messages are
> reviewed before delivery, so non-disruptive messages still reach the list=
.
> A ban stops messages reaching the list at all. Prefer a ban only where a
> hold will not work:
>
>    - the volume of held messages is unmanageable for the administrators,
>    or
>    - the respondent is using the moderation queue itself disruptively.
>
> A hold already in force may be converted to a ban for the remainder of it=
s
> duration, and MUST be notified as such. Converting a hold does not extend
> it; a longer sanction requires a new incident.
> Actions not gated by the incident count
> *Private notice to the respondent.* Mandatory for every incident. See
> "Handling disruption" below.
> *Public statement.* At the administrator's judgment, for any incident.
> Send it to all IETF forums that the original message was sent to.
>
>    - Advise why the message falls short of our standards
>    - Include links to RFC7154
>    <https://datatracker.ietf.org/doc/html/rfc7154> and this procedure
>    - If a sanction has been applied, consider whether to mention it
>    - If longer than 14 days, it MUST be mentioned
>       - If 14 days or less, it MAY be
>       - If the respondent requests, it MUST be
>    - If the incident is later rescinded, a correction follows (see
>    "Rescinding an incident")
>
> *Central address block* and *hiding a message from the mail archive* are
> not sanctions on the ladder. They are anti-spam and confidentiality
> measures, covered in the relevant subsections below.
> Handling disruption
> If the disruption may also be harassment
> <https://datatracker.ietf.org/doc/statement-iesg-ietf-anti-harassment-pol=
icy-20131103/>,
> report it to the Ombudsteam. Their work is strictly confidential and take=
s
> time. Do not assume they will take action, so in all cases the procedures
> in this document should still be followed. Any actions they take will be =
in
> addition to these procedures.
> Otherwise, follow this procedure for every incident:
>
>    1. Discuss the message(s) with your co-administrators and decide
>    whether the conduct was disruptive. If it was, this is an incident.
>    2. Record the incident in the register. It will tell you the maximum
>    sanction available for the respondent.
>    3. Choose a sanction, up to that maximum, or none, and record it.
>    4. Send a private message to the respondent:
>    - Advising why the conduct falls short of our standards
>       - Noting that prior incidents were taken into account, if the
>       maximum sanction shows there were any
>       - Including a link to this procedure
>       - Advising the sanction applied, if any, and its duration
>       - If a hold is applied, saying that non-disruptive messages will be
>       allowed through to the list in a timely manner
>       - Adding anything the relevant subsection below requires
>    5. Notify your co-administrators.
>    6. Consider whether to send a public statement.
>
> In examining email threads for disruptions, administrators should judge
> disruptions on qualitative (quality of technical content) and quantitativ=
e
> (number of times a mail message post causes a problem). An administrator =
is
> uniquely qualified to judge the technical content on whether the
> information provides a substantive additions to the discussion whether th=
e
> discussions agrees with or disagrees with the draft or issue the Working
> Group is discussing. Quantitative counts can be generated by hand or by
> IETF tools.
> If the disruption is occurring in multiple forums, the moderation team
> have the ability to extend sanctions across all IETF forums.
> Handling uncivil commentary
> Include links to RFC7154 <https://datatracker.ietf.org/doc/html/rfc7154> =
in
> the private message.
> Handling messages unrelated to the list's purpose
> Consider if the message(s) would fit the purpose of another IETF list.
> If so, send a reply to the list, requesting that further discussion occur=
s
> on that list and not this one. [Add best practice with respect to
> cc/bcc/reply-to]
> For messages outside the remit of the IETF, treat as spam.
> Handling astroturfing
> Astroturfing is a campaign to make a position appear to have wider suppor=
t
> than is the case. There are three types for the purposes of this document=
:
>
>    1. A participant pretends to be multiple people in order to simulate a
>    larger faction. If an administrator comes across credible evidence of =
this
>    behavior, it is an incident.
>    2. A group of participants uses false associations to appear that a
>    point of view comes from more than one employer. For example, three
>    employees of example.com pretend to be from abc.com, def.com, and
>    ghi.com to suggest there is broad industry support for a position. If
>    the administrator finds evidence the stated affiliation is false and
>    deceitful, it is an incident.
>    3. A stated affiliation is true but omits important disclosures. For
>    example, a professor uses their university affiliation while also unde=
r
>    contract to a corporation with a financial interest in the question. T=
he
>    administrator SHOULD remind the participant of the interest. If the
>    participant does not then disclose, the administrator SHOULD directly
>    announce it to the list. If the administrator believes the lack of
>    disclosure is a deliberate attempt to deceive, it is an incident.
>
> Nothing in this section should be construed as a requirement for
> administrators to launch extensive investigations into the true identitie=
s
> and/or affiliations of participants.
> Handling spam
> Spam is not handled as an incident. It is dealt with as below, unless the
> sender is believed to be a genuine participant, in which case it is treat=
ed
> as disruption and the procedure above applies. If a genuine participant's
> account appears to have been compromised, record the incident as usual; s=
ee
> "Rescinding an incident" for how to withdraw it once that is established.
> Spam definition
> Disruptive posting
> <https://chairs.ietf.org/mailing-lists/disruptive-posting> identifies two
> types:
>
>    - Messages unrelated to the IETF
>    - Advertising
>
> It notes this is a non-exhaustive list. These procedures add:
>
>    - Messages with no indication that the sender is a real person
>    - Messages with no indication that the sender has an understanding of
>    how the IETF works
>
> Spam procedure
> If the sender has been automatically held for moderation because they are
> not a subscriber to any IETF list:
>
>    - Decide if they are likely to be a genuine newcomer
>    - If yes, reject with newcomer-rejection-message.txt
>       <https://github.com/ietf-moderators/procedures/blob/main/newcomer-r=
ejection-message.txt>
>       - If no, discard
>
> If it has been held for another reason:
>
>    - Reject or discard as needed
>
> Otherwise, the spam has already been delivered to subscribers.
>
>    - Consider whether it should remain in the mail archive
>    - If appropriate, ask support@ietf.org to hide it
>    - If the sender address may have been spoofed:
>    - Does the tools team need to tighten controls?
>       - Does the sender need to tighten DMARC?
>    - If the sender is believed to be genuine:
>    - Treat as disruption
>
> Dealing with repeated spam
> As per the advice in Spam control <https://chairs.ietf.org/mailing-lists>=
:
>
>    - Ask support@ietf.org to block the address centrally
>    - For immediate results, ban this sender from the affected list
>    (optional)
>
> Handling behavior that hinders the work of the group
> This is conduct that may be civil and on topic but obstructs progress: fo=
r
> example, repeatedly arguing against an approved charter, reopening a
> consensus call without new information, or making the same point in reply
> after reply so that other voices are drowned out.
> Disagreement, however persistent, is not disruption. The test is whether
> the conduct adds to the discussion, not whether the administrator agrees
> with it. Asking the chairs to revisit a decision with new information, or
> appealing under RFC2026
> <https://www.rfc-editor.org/rfc/rfc2026.html#section-6.5>, is never
> disruption.
> Unless the conduct is egregious, first ask the participant to stop; it is
> an incident if it continues.
> In the private message, additionally identify the specific conduct, and
> say that it is the conduct being addressed, not their technical position.
> Handling messages containing confidential information
> Report the message to support@ietf.org.
> This is in addition to, not instead of, handling the incident under the
> procedure above.
> Handling repeated inclusion of derivative rights notices
> Outside of an internet-draft, IESG Statement on Clarifying Derivative
> Works Rights
> <https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-=
derivative-works-rights/> says
> that notices that claim that derivative rights are being withheld for a
> Contribution are not conformant to IETF policies. Repeated inclusion of
> such notices is a disruption.
> In the private message, additionally:
>
>    - Refer to the IESG Statement on Clarifying Derivative Works Rights
>    <https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifyi=
ng-derivative-works-rights/>
>    - Advise why this notice is not conformant to IETF policies
>    - Say that messages without the notice will be allowed through to the
>    list in a timely manner
>
> Handling slop
> "Slop" is voluminous, low-quality content that does not appear to have
> been checked by someone knowledgeable in the field. Slop can be uncivil,
> spam, or unrelated to the list's purpose, in which case it can be handled
> in accordance with the procedures above. Slop is often the product of AI,
> though administrators are not expected to determine if the content was
> written by a human. There might be a nugget of a good point in hundreds o=
f
> words, or it could be complete nonsense.
> Administrators should assess if a message is slop:
>
>    - Does it use hundreds of words to make a simple point, or no point at
>    all?
>    - Is no one engaging meaningfully with the technical content of the
>    message?
>
> If an administrator judges that a message is slop, it counts as an
> incident.
> Handling messages held for moderation
> Assess the message in a timely manner.
>
>    - If it is spam, follow the spam procedure
>    <https://github.com/ietf-moderators/procedures/blob/main/procedures.md=
#spam-procedure>
>    - If it is non-disruptive, allow it through
>    - If disruptive, reject with a reason as to why
>
> Rejecting a held message is not by itself a new incident. If the held
> messages amount to a fresh occasion of disruption, handle it under
> "Handling disruption" above.
> If the volume of held messages is unmanageable, the hold may be converted
> to a ban for its remaining duration - see "Choosing between a hold and a
> ban".
> If the respondent is only sending non-disruptive messages:
>
>    - You have the option to temporarily remove hold for moderation.
>    - If disruption recurs, the hold may be reinstated without notice for
>    the remainder of the sanction period.
>
> Removal of a sanction
> On or before the end of the sanction period:
>
>    1. Remove the hold or ban by setting the list default action for the
>    respondent
>    2. Send a private message to the respondent confirming the sanction is
>    no longer in place, and referring to what the currently-approved proce=
dure
>    says will happen if there is a further incident
>
> Removing a sanction does not remove the incident from the count. It
> continues to count for five years from the date of the incident.
> Chat moderation
> Moderation of Zulip chat has different procedures reflecting the
> synchronous nature of discussion. However, a chat message violates policy
> if it would violate policy as an email to the list, and vice versa.
> The Sanctions Ladder does not apply to chat moderation.
> An Administrator detects a message that violates policy. Spam and message=
s
> containing confidential information should immediately be deleted.
> Otherwise, the Administrator sends a public message to the offender
> indicating that further lapses will be moderated.
> On a second offense in the same session, the message is deleted and the
> user is blocked from participation it the chat for the remainder of the
> session.
> Open questions
>
>    1. How do chairs delegate administration responsibility, and how do we
>    track that?
>    2. How do we identify the administrators of non-WG lists
>    <https://datatracker.ietf.org/list/nonwg>?
>
>
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd / Fastmail US LLC
>   brong@fastmailteam.com
>
> _______________________________________________
> Mod-discuss mailing list -- mod-discuss@ietf.org
> To unsubscribe send an email to mod-discuss-leave@ietf.org
>

--0000000000002a8dd8066053e144
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Bron,<div><br></div><div>I tried to read the list or pr=
ocedure, but it looks full of details,=C2=A0</div><div>and I think the mode=
rator team can decide what is disruptive depending on the situation. Howeve=
r, thanks for your message informing us of this, I will agree on what the t=
eam decides because I believe=C2=A0it will be for the best of all.</div><di=
v><br></div><div>best=C2=A0wishes</div><div>AB</div></div><br><div class=3D=
"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">O=
n Thu, Oct 22, 2026 at 1:57=E2=80=AFAM Bron Gondwana &lt;brong=3D<a href=3D=
"mailto:40fastmailteam.com@dmarc.ietf.org">40fastmailteam.com@dmarc.ietf.or=
g</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
><u></u><div><div style=3D"font-family:Arial">Hello IETF Community,</div><d=
iv style=3D"font-family:Arial"><br></div><div style=3D"font-family:Arial">S=
ince being instantiated at the Vienna IETF, the Moderator Team has been ref=
ining our procedures.=C2=A0 Our planned timeline is:</div><ol><li style=3D"=
font-family:Arial">Now until IETF127 - open up discussion of these procedur=
es on the mod-discuss list</li><li style=3D"font-family:Arial">At IETF127 -=
 discussion in person with interested parties</li><li style=3D"font-family:=
Arial">After IETF127 - discuss feedback amongst ourselves and revise proced=
ures if needed</li><li style=3D"font-family:Arial">Later this year or early=
 next year - ask the IESG to approve procedures and set a date upon which t=
hey come into effect</li></ol><div style=3D"font-family:Arial">We hope that=
, at the latest, these procedures will be in effect by the start of IETF128=
.</div><div style=3D"font-family:Arial"><br></div><div style=3D"font-family=
:Arial">The procedures are published in Github here:=C2=A0<a href=3D"https:=
//github.com/ietf-moderators/procedures" target=3D"_blank">https://github.c=
om/ietf-moderators/procedures</a>=C2=A0- I will also paste the procedures f=
ile at the end of this email.</div><div style=3D"font-family:Arial"><br></d=
iv><div style=3D"font-family:Arial"><b>Seeking feedback or clarifying quest=
ions in the following ways:</b></div><ul><li style=3D"font-family:Arial">In=
 public to the <a href=3D"mailto:mod-discuss@ietf.org" target=3D"_blank">mo=
d-discuss@ietf.org</a>=C2=A0list</li><li style=3D"font-family:Arial">In pri=
vate to <a href=3D"mailto:ietf-moderators@ietf.org" target=3D"_blank">ietf-=
moderators@ietf.org</a>=C2=A0(an alias to the 6 of us)</li><li style=3D"fon=
t-family:Arial">As issues or pull requests on the Github repository.</li></=
ul><div style=3D"font-family:Arial"><br></div><div style=3D"font-family:Ari=
al">Regards, your Moderator Team (Bron, Chris, Martin, Mohit, Murray, Susan=
)</div><div style=3D"font-family:Arial"><br></div><div style=3D"font-family=
:Arial">Procedures follow:</div><h1>Introduction</h1><div style=3D"font-fam=
ily:Arial;text-align:start"><a href=3D"https://www.rfc-editor.org/rfc/rfc99=
45.html" target=3D"_blank">RFC9945</a>=C2=A0says that the IETF community wi=
ll treat people with kindness and grace, but not endless patience. It sets =
up a policy for the moderation of disruptive participation across the IETF&=
#39;s various public contribution channels and discussion forums. It establ=
ishes guardrails for moderation and a moderator team. This team is required=
 to develop a set of moderation procedures and facilitate their consistent =
implementation with chairs and administrators. This document defines those =
moderation procedures.</div><h2>Scope</h2><div style=3D"font-family:Arial;t=
ext-align:start">These procedures apply to all public online IETF forums, a=
s described in Section 3 of RFC9945: mailing lists, chat groups, and other =
systems that the IETF or its working groups have chosen to use, such as Git=
Hub repositories, wikis, and issue trackers.</div><div style=3D"font-family=
:Arial;text-align:start">They do not apply to the forums of the IRTF, the I=
AB, the RSWG, the RSAB, or the Independent Submission Stream, unless that b=
ody explicitly agrees. Some of those forums are hosted on IETF infrastructu=
re, so the address of a list is not always a reliable guide. The moderator =
team maintains the current list of forums in and out of scope in=C2=A0<a hr=
ef=3D"https://github.com/ietf-moderators/procedures/blob/main/scope.md" tar=
get=3D"_blank">scope.md</a>, and updates it as other bodies opt in.</div><h=
1>Responsibilities</h1><h2>Moderator team</h2><div style=3D"font-family:Ari=
al;text-align:start">The moderator team can be contacted at=C2=A0<a href=3D=
"mailto:ietf-moderators@ietf.org" target=3D"_blank">ietf-moderators@ietf.or=
g</a>. Participants may use this address to report disruption, to ask for a=
n incident to be rescinded or a sanction reduced, or to ask any question ab=
out these procedures. Administrators use it to notify the moderator team of=
 reports and actions taken.</div><ul><li style=3D"font-family:Arial">Define=
 these proposed procedures, with community input, for approval by IESG</li>=
<li style=3D"font-family:Arial"><div>Act as administrators of plenary lists=
</div><ul><li style=3D"font-family:Arial"><a href=3D"mailto:ietf@ietf.org" =
target=3D"_blank">ietf@ietf.org</a></li><li style=3D"font-family:Arial"><a =
href=3D"mailto:last-call@ietf.org" target=3D"_blank">last-call@ietf.org</a>=
</li><li style=3D"font-family:Arial">Plenary session Zulip chat</li></ul></=
li><li style=3D"font-family:Arial"><div>Act as administrator of last resort=
</div><ul><li style=3D"font-family:Arial">If there is no defined administra=
tor</li><li style=3D"font-family:Arial">If administrators are unresponsive<=
/li><li style=3D"font-family:Arial">In cases of disruption across multiple =
lists</li></ul></li><li style=3D"font-family:Arial">Provide training and gu=
idance to administrators</li><li style=3D"font-family:Arial">Maintain the i=
ncident register</li><li style=3D"font-family:Arial">Respond to requests an=
d perform actions in a timely manner (defined as &quot;SHOULD be within 48 =
hours, MUST be within one week&quot;).</li><li style=3D"font-family:Arial">=
Revise these procedures based on experience, following the same community i=
nput and approval process.</li><li style=3D"font-family:Arial">Extend sanct=
ions to multiple lists where appropriate</li></ul><h2>Administrators</h2><u=
l><li style=3D"font-family:Arial">Implement the approved procedures</li><li=
 style=3D"font-family:Arial">Record incidents, and the sanctions applied, i=
n the incident register</li><li style=3D"font-family:Arial">Notify moderato=
r team of reports and actions taken</li><li style=3D"font-family:Arial">May=
 rescind their own incidents, and reduce the sanctions on them.</li></ul><h=
1>Administrator procedures</h1><h2>Incidents</h2><div style=3D"font-family:=
Arial;text-align:start">An=C2=A0<b>incident</b>=C2=A0is a single occasion o=
n which an administrator finds that a participant&#39;s conduct in an IETF =
forum was disruptive. The participant whose conduct it was is the=C2=A0<b>r=
espondent</b>=C2=A0of that incident.</div><h3>What counts as disruption</h3=
><div style=3D"font-family:Arial;text-align:start">Disruption can take any =
of these forms.</div><ul><li style=3D"font-family:Arial"><div>Uncivil comme=
ntary</div><ul><li style=3D"font-family:Arial">Attacking people</li><li sty=
le=3D"font-family:Arial">Attacking groups of people</li><li style=3D"font-f=
amily:Arial">Attacking an idea in an insulting or excessively hostile manne=
r</li><li style=3D"font-family:Arial">Clearly lacking in respect and courte=
sy (the expectations of=C2=A0<a href=3D"https://datatracker.ietf.org/doc/ht=
ml/rfc7154" target=3D"_blank">RFC7154</a>)</li><li style=3D"font-family:Ari=
al">Inciting hate</li></ul></li><li style=3D"font-family:Arial">Messages un=
related to the list&#39;s purpose</li><li style=3D"font-family:Arial">Behav=
ior that hinders the work of the group</li><li style=3D"font-family:Arial">=
Sealioning: the disingenuous action by a commenter of making an ostensible =
effort to engage in sincere and serious civil debate, usually by asking per=
sistent questions of the other commenter. The questions appear as an effort=
 to learn, but degrade the progress of technical debate and the goodwill of=
 the list participants. See the descriptions from=C2=A0<a href=3D"https://w=
ww.merriam-webster.com/wordplay/sealioning-internet-trolling" target=3D"_bl=
ank">Merriam-Webster</a>=C2=A0and=C2=A0<a href=3D"https://en.wikipedia.org/=
wiki/Sealioning" target=3D"_blank">Wikipedia</a>.</li><li style=3D"font-fam=
ily:Arial">Astroturfing</li><li style=3D"font-family:Arial">Messages contai=
ning confidential information</li><li style=3D"font-family:Arial"><div>Repe=
ated inclusion of derivative rights notices</div><ul><li style=3D"font-fami=
ly:Arial">As per the=C2=A0<a href=3D"https://datatracker.ietf.org/doc/state=
ment-iesg-statement-on-clarifying-derivative-works-rights/" target=3D"_blan=
k">IESG statement</a></li></ul></li><li style=3D"font-family:Arial">Message=
s containing slop</li></ul><h3>Counting incidents</h3><ul><li style=3D"font=
-family:Arial">A connected series of messages - one thread, or several mess=
ages over a short period making the same disruption - is=C2=A0<b>one</b>=C2=
=A0incident, not one per message.</li><li style=3D"font-family:Arial">Incid=
ents are counted per participant across the whole IETF, not per list. An in=
cident recorded by the administrator of one list counts when the administra=
tor of another list acts later.</li><li style=3D"font-family:Arial">An=C2=
=A0<b>eligible incident</b>=C2=A0is one that has not been rescinded and who=
se conduct occurred within the past five years. Only eligible incidents are=
 counted.</li><li style=3D"font-family:Arial">All forms of disruption share=
 a single count. It does not matter whether the earlier incidents were of t=
he same kind as the one being handled now.</li><li style=3D"font-family:Ari=
al">Every incident MUST be recorded in the incident register, and notified =
to the respondent and to co-administrators.</li></ul><h2>Incident register<=
/h2><div style=3D"font-family:Arial;text-align:start">Incidents are recorde=
d in the=C2=A0<b>incident register</b>, maintained by the moderator team.</=
div><h3>What the register records</h3><div style=3D"font-family:Arial;text-=
align:start">For each incident:</div><ul><li style=3D"font-family:Arial">An=
 identifier</li><li style=3D"font-family:Arial">The date of the conduct, an=
d the date it was recorded</li><li style=3D"font-family:Arial">The forum(s)=
 in which it occurred</li><li style=3D"font-family:Arial">The form of disru=
ption</li><li style=3D"font-family:Arial">The respondent</li><li style=3D"f=
ont-family:Arial">The action-taker</li><li style=3D"font-family:Arial">The =
sanction applied, if any: whether hold or ban, its duration, and when it en=
ds</li><li style=3D"font-family:Arial">Whether it has been rescinded, by wh=
om, when, and why</li><li style=3D"font-family:Arial">Whether a sanction ha=
s been reduced, by whom, when, and why</li><li style=3D"font-family:Arial">=
The private detail: the messages, the reasoning, and correspondence with th=
e respondent</li></ul><div style=3D"font-family:Arial;text-align:start">One=
 human always takes the action, and is recorded as the=C2=A0<b>action-taker=
</b>. Where administrators decided jointly, one of them still takes the act=
ion and is the action-taker for that incident. They may name the others in =
the private detail, but that grants no additional access.</div><h3>Datatrac=
ker accounts</h3><div style=3D"font-family:Arial;text-align:start">Incident=
s are recorded against the respondent&#39;s Datatracker account, not agains=
t an email address, so every address on that account shares a single incide=
nt count.</div><div style=3D"font-family:Arial;text-align:start">If the res=
pondent does not already have a Datatracker account, the moderator team cre=
ates one, linked to the email address from which the disruption came.</div>=
<div style=3D"font-family:Arial;text-align:start">If disruption from anothe=
r address is identified as coming from the same person, the moderator team =
identifies their existing account and records the incident against it. The =
other address is not added to the account. If the identification turns out =
to be wrong, the remedy is to rescind the incident.</div><h3>Who sees what<=
/h3><table style=3D"box-sizing:border-box;border-collapse:collapse;margin-t=
op:0px;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-=
alternates:normal;font-variant-numeric:tabular-nums;font-variant-east-asian=
:normal;width:max-content;max-width:100%;display:block;overflow:auto"><thea=
d style=3D"box-sizing:border-box"><tr style=3D"box-sizing:border-box"><th s=
tyle=3D"box-sizing:border-box;padding:6px 13px;font-weight:600">Who</th><th=
 style=3D"box-sizing:border-box;padding:6px 13px;font-weight:600">Sees</th>=
</tr></thead><tbody style=3D"box-sizing:border-box"><tr style=3D"box-sizing=
:border-box"><td style=3D"box-sizing:border-box;padding:6px 13px">The actio=
n-taker, at the point of recording an incident</td><td style=3D"box-sizing:=
border-box;padding:6px 13px">the maximum sanction available for the respond=
ent based on the sanction ladder</td></tr><tr style=3D"box-sizing:border-bo=
x"><td style=3D"box-sizing:border-box;padding:6px 13px">The action-taker, t=
he respondent, the moderator team, the IESG, and legal counsel</td><td styl=
e=3D"box-sizing:border-box;padding:6px 13px">the full detail of that incide=
nt</td></tr><tr style=3D"box-sizing:border-box"><td style=3D"box-sizing:bor=
der-box;padding:6px 13px">Any respondent</td><td style=3D"box-sizing:border=
-box;padding:6px 13px">the history of incidents recorded against them, the =
maximum sanction available against them, and any current sanction in force<=
/td></tr><tr style=3D"box-sizing:border-box"><td style=3D"box-sizing:border=
-box;padding:6px 13px">The moderator team, the IESG, and legal counsel</td>=
<td style=3D"box-sizing:border-box;padding:6px 13px">every incident, and ev=
ery participant&#39;s incident count and history</td></tr></tbody></table><=
div style=3D"font-family:Arial;text-align:start">Once a year the moderator =
team publishes a report giving the number of incidents recorded in that yea=
r, with a count of each type and severity of sanction applied and whatever =
commentary the team wishes to add.</div><h3>Rescinding an incident</h3><div=
 style=3D"font-family:Arial;text-align:start">Rescinding an incident withdr=
aws the finding: the incident is treated as never having been recorded. Any=
 of the following may rescind an incident, acting alone and recording a rea=
son:</div><ul><li style=3D"font-family:Arial">The action-taker, for their o=
wn incidents</li><li style=3D"font-family:Arial">The moderator team</li><li=
 style=3D"font-family:Arial">The IESG</li></ul><div style=3D"font-family:Ar=
ial;text-align:start">No other administrator may rescind an incident, even =
a co-administrator of the same forum who took part in the decision. They as=
k the moderator team or the IESG instead.</div><div style=3D"font-family:Ar=
ial;text-align:start">The respondent may ask any of them to rescind an inci=
dent.</div><div style=3D"font-family:Arial;text-align:start">A rescinded in=
cident is no longer eligible: it is removed from the count and from the cal=
culation of sanctions available against this respondent. It remains visible=
 in full (marked rescinded) to the action-taker, the respondent, the modera=
tor team, the IESG, and legal counsel.</div><div style=3D"font-family:Arial=
;text-align:start">When an incident is rescinded, any sanctions currently i=
n effect on the respondent are reviewed to see if they should be reduced or=
 removed.</div><div style=3D"font-family:Arial;text-align:start">If a publi=
c statement was made about the incident, whoever rescinds it sends a correc=
tion to the same forums, saying that the finding has been withdrawn, unless=
 the respondent asks that none be sent.</div><div style=3D"font-family:Aria=
l;text-align:start">It is appropriate to rescind an incident when it is fou=
nd that the determination of disruption was made in error. If the incident =
did occur but the respondent is determined to be willing to improve their b=
ehavior, then reducing the sanction (see below) is a better choice.</div><d=
iv style=3D"font-family:Arial;text-align:start">A finding may also be in er=
ror because the respondent&#39;s account was compromised and the messages w=
ere not theirs. A hold may still be appropriate until the account is secure=
d, and repeated compromises are a reason to keep it.</div><h3>Reducing a sa=
nction</h3><div style=3D"font-family:Arial;text-align:start">Reducing a san=
ction lifts it, or brings its end date forward. It changes the sanction, no=
t the finding: the incident stays in the register and stays eligible, and t=
he sanction ladder is unaffected.</div><div style=3D"font-family:Arial;text=
-align:start">Any of the following may reduce a sanction, acting alone and =
recording a reason:</div><ul><li style=3D"font-family:Arial">The action-tak=
er, for their own incidents</li><li style=3D"font-family:Arial">The moderat=
or team</li><li style=3D"font-family:Arial">The IESG</li></ul><div style=3D=
"font-family:Arial;text-align:start">As with rescinding, no other administr=
ator may reduce a sanction; co-administrators ask the moderator team or the=
 IESG.</div><div style=3D"font-family:Arial;text-align:start">The responden=
t may ask any of them to reduce a sanction, for example by undertaking to c=
hange their behavior. Reduction is a grace and not a right.</div><div style=
=3D"font-family:Arial;text-align:start">Whoever reduces a sanction notifies=
 the respondent and the administrators of the affected forums. If the sanct=
ion is lifted immediately, follow &quot;Removal of a sanction&quot; below n=
ow; if its end date is brought forward, follow it on or before the new end =
date.</div><h3>Until the register exists</h3><div style=3D"font-family:Aria=
l;text-align:start">The register has yet to be built. Until it is, the mode=
rator team maintains the record, and an administrator handling an incident =
asks the moderator team what sanctions are available.</div><h3>Existing pos=
ting rights actions</h3><div style=3D"font-family:Arial;text-align:start">R=
FC9945 obsoletes the posting rights (PR) actions of=C2=A0<a href=3D"https:/=
/www.rfc-editor.org/rfc/rfc3683.html" target=3D"_blank">RFC3683</a>. When t=
hese procedures take effect, the moderator team handles each PR action list=
ed on the=C2=A0<a href=3D"https://www.ietf.org/about/groups/iesg/posting-ri=
ghts-actions/" target=3D"_blank">IESG&#39;s PR actions page</a>=C2=A0as fol=
lows:</div><ul><li style=3D"font-family:Arial">If the PR action was approve=
d or last updated within the past five years, record three incidents agains=
t its respondent in the register, each dated on the date of that approval o=
r update. A PR action always follows several incidents of disruption, so th=
e respondent does not start from zero; their next incident is their fourth.=
</li><li style=3D"font-family:Arial">If it was approved or last updated mor=
e than five years ago, record nothing, as any incidents it represented woul=
d no longer be eligible.</li></ul><div style=3D"font-family:Arial;text-alig=
n:start">In either case, remove the restrictions the PR action imposed by s=
etting the list default action for the respondent on every affected list, a=
nd send them a private message saying so and linking to this procedure.</di=
v><h3>Requirements for the tools team</h3><div style=3D"font-family:Arial;t=
ext-align:start">The register must:</div><ul><li style=3D"font-family:Arial=
">Record each incident with the fields listed above.</li><li style=3D"font-=
family:Arial">Provide a method for administrators, the moderator team, and =
the IESG to create entries in the register, displaying the maximum sanction=
 available in days, and allowing entry of any number of days equal to or le=
ss than the maximum allowed.</li><li style=3D"font-family:Arial">Either app=
ly the recorded sanction automatically or provide instructions on how to ap=
ply it, and remind the action-taker and the administrators of the affected =
forums when it is due to expire.</li><li style=3D"font-family:Arial">Record=
 incidents against the respondent&#39;s Datatracker account, so that counts=
 are collected across all addresses on that account.</li><li style=3D"font-=
family:Arial">Allow the moderator team to create a Datatracker account for =
a respondent who has none, linked to the address from which the disruption =
came.</li><li style=3D"font-family:Arial">Allow the moderator team to recor=
d an incident from any address against an existing account, without adding =
that address to the account.</li><li style=3D"font-family:Arial">Record exa=
ctly one action-taker per incident, and restrict the private detail of an i=
ncident to the action-taker, the respondent, the moderator team, the IESG, =
and legal counsel. Anyone named in the private detail gains no additional a=
ccess by being named.</li><li style=3D"font-family:Arial">Allow the action-=
taker, the moderator team and the IESG to rescind an incident, recording wh=
o rescinded it, when, and why.</li><li style=3D"font-family:Arial">Allow th=
e action-taker, the moderator team and the IESG to reduce a sanction, recor=
ding who reduced it, when, and why, and notify the respondent and the admin=
istrators of the affected forums.</li><li style=3D"font-family:Arial">Compu=
te each participant&#39;s count from eligible incidents only, so that an in=
cident leaves the count when it is rescinded or five years after the date o=
f the conduct, while the record is retained.</li><li style=3D"font-family:A=
rial">Offer a five-year maximum for any incident occurring within one year =
after the end of a previous five-year sanction, whatever the respondent&#39=
;s count.</li><li style=3D"font-family:Arial">When an incident is rescinded=
, remove it from every view except those of the parties who see its full de=
tail, recalculate affected counts, reduce any sanction still in force to th=
e recalculated maximum (or provide instructions for same), notify the respo=
ndent and the administrators of the affected forums, and remind whoever res=
cinded it to send a correction if a public statement was made.</li><li styl=
e=3D"font-family:Arial">Display to the moderator team an aggregate count of=
 incidents recorded each year, by type and severity of sanction applied.</l=
i></ul><h2>Sanctions</h2><h3>The sanction ladder</h3><div style=3D"font-fam=
ily:Arial;text-align:start">The number of eligible incidents,=C2=A0<b>inclu=
ding the one being handled</b>, sets the maximum sanction available. The in=
cident register computes this and tells the acting administrator the maximu=
m. Any sanction up to and including that maximum may be applied - or none a=
t all. In general, the minimal action necessary should be taken.</div><tabl=
e style=3D"box-sizing:border-box;border-collapse:collapse;margin-top:0px;fo=
nt-variant-ligatures:normal;font-variant-caps:normal;font-variant-alternate=
s:normal;font-variant-numeric:tabular-nums;font-variant-east-asian:normal;w=
idth:max-content;max-width:100%;display:block;overflow:auto"><thead style=
=3D"box-sizing:border-box"><tr style=3D"box-sizing:border-box"><th style=3D=
"box-sizing:border-box;padding:6px 13px;font-weight:600">Eligible incidents=
 (including this one)</th><th style=3D"box-sizing:border-box;padding:6px 13=
px;font-weight:600">Maximum sanction</th></tr></thead><tbody style=3D"box-s=
izing:border-box"><tr style=3D"box-sizing:border-box"><td style=3D"box-sizi=
ng:border-box;padding:6px 13px">1</td><td style=3D"box-sizing:border-box;pa=
dding:6px 13px">notice only</td></tr><tr style=3D"box-sizing:border-box"><t=
d style=3D"box-sizing:border-box;padding:6px 13px">2</td><td style=3D"box-s=
izing:border-box;padding:6px 13px">7 days</td></tr><tr style=3D"box-sizing:=
border-box"><td style=3D"box-sizing:border-box;padding:6px 13px">3</td><td =
style=3D"box-sizing:border-box;padding:6px 13px">28 days (1 month)</td></tr=
><tr style=3D"box-sizing:border-box"><td style=3D"box-sizing:border-box;pad=
ding:6px 13px">4</td><td style=3D"box-sizing:border-box;padding:6px 13px">9=
0 days (3 months)</td></tr><tr style=3D"box-sizing:border-box"><td style=3D=
"box-sizing:border-box;padding:6px 13px">5</td><td style=3D"box-sizing:bord=
er-box;padding:6px 13px">365 days (one year)</td></tr><tr style=3D"box-sizi=
ng:border-box"><td style=3D"box-sizing:border-box;padding:6px 13px">6 or mo=
re</td><td style=3D"box-sizing:border-box;padding:6px 13px">1825 days (5 ye=
ars)</td></tr></tbody></table><div style=3D"font-family:Arial;text-align:st=
art">A sanction is a=C2=A0<b>hold for moderation</b>=C2=A0or a=C2=A0<b>ban<=
/b>, of any duration up to the maximum. No sanction may exceed five years. =
A respondent is immediately eligible for another five-year sanction if an i=
ncident occurs within one year after the end of a previous five-year sancti=
on, whatever their incident count at that time.</div><div style=3D"font-fam=
ily:Arial;text-align:start">A single incident, however serious, unlocks not=
hing beyond a notice. Where conduct is serious enough that the ladder is pl=
ainly an inadequate response, refer the matter to the Ombudsteam (if it may=
 be=C2=A0<a href=3D"https://datatracker.ietf.org/doc/statement-iesg-ietf-an=
ti-harassment-policy-20131103/" target=3D"_blank">harassment</a>) or raise =
it with the IESG. These procedures do not give administrators a route aroun=
d the ladder.</div><h3>Choosing between a hold and a ban</h3><div style=3D"=
font-family:Arial;text-align:start">A hold for moderation is the default: t=
he respondent&#39;s messages are reviewed before delivery, so non-disruptiv=
e messages still reach the list.</div><div style=3D"font-family:Arial;text-=
align:start">A ban stops messages reaching the list at all. Prefer a ban on=
ly where a hold will not work:</div><ul><li style=3D"font-family:Arial">the=
 volume of held messages is unmanageable for the administrators, or</li><li=
 style=3D"font-family:Arial">the respondent is using the moderation queue i=
tself disruptively.</li></ul><div style=3D"font-family:Arial;text-align:sta=
rt">A hold already in force may be converted to a ban for the remainder of =
its duration, and MUST be notified as such. Converting a hold does not exte=
nd it; a longer sanction requires a new incident.</div><h3>Actions not gate=
d by the incident count</h3><div style=3D"font-family:Arial;text-align:star=
t"><b>Private notice to the respondent.</b>=C2=A0Mandatory for every incide=
nt. See &quot;Handling disruption&quot; below.</div><div style=3D"font-fami=
ly:Arial;text-align:start"><b>Public statement.</b>=C2=A0At the administrat=
or&#39;s judgment, for any incident. Send it to all IETF forums that the or=
iginal message was sent to.</div><ul><li style=3D"font-family:Arial">Advise=
 why the message falls short of our standards</li><li style=3D"font-family:=
Arial">Include links to=C2=A0<a href=3D"https://datatracker.ietf.org/doc/ht=
ml/rfc7154" target=3D"_blank">RFC7154</a>=C2=A0and this procedure</li><li s=
tyle=3D"font-family:Arial"><div>If a sanction has been applied, consider wh=
ether to mention it</div><ul><li style=3D"font-family:Arial">If longer than=
 14 days, it MUST be mentioned</li><li style=3D"font-family:Arial">If 14 da=
ys or less, it MAY be</li><li style=3D"font-family:Arial">If the respondent=
 requests, it MUST be</li></ul></li><li style=3D"font-family:Arial">If the =
incident is later rescinded, a correction follows (see &quot;Rescinding an =
incident&quot;)</li></ul><div style=3D"font-family:Arial;text-align:start">=
<b>Central address block</b>=C2=A0and=C2=A0<b>hiding a message from the mai=
l archive</b>=C2=A0are not sanctions on the ladder. They are anti-spam and =
confidentiality measures, covered in the relevant subsections below.</div><=
h2>Handling disruption</h2><div style=3D"font-family:Arial;text-align:start=
">If the disruption may also be=C2=A0<a href=3D"https://datatracker.ietf.or=
g/doc/statement-iesg-ietf-anti-harassment-policy-20131103/" target=3D"_blan=
k">harassment</a>, report it to the Ombudsteam. Their work is strictly conf=
idential and takes time. Do not assume they will take action, so in all cas=
es the procedures in this document should still be followed. Any actions th=
ey take will be in addition to these procedures.</div><div style=3D"font-fa=
mily:Arial;text-align:start">Otherwise, follow this procedure for every inc=
ident:</div><ol><li style=3D"font-family:Arial"><div>Discuss the message(s)=
 with your co-administrators and decide whether the conduct was disruptive.=
 If it was, this is an incident.</div></li><li style=3D"font-family:Arial">=
<div>Record the incident in the register. It will tell you the maximum sanc=
tion available for the respondent.</div></li><li style=3D"font-family:Arial=
"><div>Choose a sanction, up to that maximum, or none, and record it.</div>=
</li><li style=3D"font-family:Arial"><div>Send a private message to the res=
pondent:</div><ul><li style=3D"font-family:Arial">Advising why the conduct =
falls short of our standards</li><li style=3D"font-family:Arial">Noting tha=
t prior incidents were taken into account, if the maximum sanction shows th=
ere were any</li><li style=3D"font-family:Arial">Including a link to this p=
rocedure</li><li style=3D"font-family:Arial">Advising the sanction applied,=
 if any, and its duration</li><li style=3D"font-family:Arial">If a hold is =
applied, saying that non-disruptive messages will be allowed through to the=
 list in a timely manner</li><li style=3D"font-family:Arial">Adding anythin=
g the relevant subsection below requires</li></ul></li><li style=3D"font-fa=
mily:Arial"><div>Notify your co-administrators.</div></li><li style=3D"font=
-family:Arial"><div>Consider whether to send a public statement.</div></li>=
</ol><div style=3D"font-family:Arial;text-align:start">In examining email t=
hreads for disruptions, administrators should judge disruptions on qualitat=
ive (quality of technical content) and quantitative (number of times a mail=
 message post causes a problem). An administrator is uniquely qualified to =
judge the technical content on whether the information provides a substanti=
ve additions to the discussion whether the discussions agrees with or disag=
rees with the draft or issue the Working Group is discussing. Quantitative =
counts can be generated by hand or by IETF tools.</div><div style=3D"font-f=
amily:Arial;text-align:start">If the disruption is occurring in multiple fo=
rums, the moderation team have the ability to extend sanctions across all I=
ETF forums.</div><h3>Handling uncivil commentary</h3><div style=3D"font-fam=
ily:Arial;text-align:start">Include links to=C2=A0<a href=3D"https://datatr=
acker.ietf.org/doc/html/rfc7154" target=3D"_blank">RFC7154</a>=C2=A0in the =
private message.</div><h3>Handling messages unrelated to the list&#39;s pur=
pose</h3><div style=3D"font-family:Arial;text-align:start">Consider if the =
message(s) would fit the purpose of another IETF list.</div><div style=3D"f=
ont-family:Arial;text-align:start">If so, send a reply to the list, request=
ing that further discussion occurs on that list and not this one. [Add best=
 practice with respect to cc/bcc/reply-to]</div><div style=3D"font-family:A=
rial;text-align:start">For messages outside the remit of the IETF, treat as=
 spam.</div><h3>Handling astroturfing</h3><div style=3D"font-family:Arial;t=
ext-align:start">Astroturfing is a campaign to make a position appear to ha=
ve wider support than is the case. There are three types for the purposes o=
f this document:</div><ol><li style=3D"font-family:Arial"><div>A participan=
t pretends to be multiple people in order to simulate a larger faction. If =
an administrator comes across credible evidence of this behavior, it is an =
incident.</div></li><li style=3D"font-family:Arial"><div>A group of partici=
pants uses false associations to appear that a point of view comes from mor=
e than one employer. For example, three employees of <a href=3D"http://exam=
ple.com" target=3D"_blank">example.com</a> pretend to be from <a href=3D"ht=
tp://abc.com" target=3D"_blank">abc.com</a>, <a href=3D"http://def.com" tar=
get=3D"_blank">def.com</a>, and <a href=3D"http://ghi.com" target=3D"_blank=
">ghi.com</a> to suggest there is broad industry support for a position. If=
 the administrator finds evidence the stated affiliation is false and decei=
tful, it is an incident.</div></li><li style=3D"font-family:Arial"><div>A s=
tated affiliation is true but omits important disclosures. For example, a p=
rofessor uses their university affiliation while also under contract to a c=
orporation with a financial interest in the question. The administrator SHO=
ULD remind the participant of the interest. If the participant does not the=
n disclose, the administrator SHOULD directly announce it to the list. If t=
he administrator believes the lack of disclosure is a deliberate attempt to=
 deceive, it is an incident.</div></li></ol><div style=3D"font-family:Arial=
;text-align:start">Nothing in this section should be construed as a require=
ment for administrators to launch extensive investigations into the true id=
entities and/or affiliations of participants.</div><h3>Handling spam</h3><d=
iv style=3D"font-family:Arial;text-align:start">Spam is not handled as an i=
ncident. It is dealt with as below, unless the sender is believed to be a g=
enuine participant, in which case it is treated as disruption and the proce=
dure above applies. If a genuine participant&#39;s account appears to have =
been compromised, record the incident as usual; see &quot;Rescinding an inc=
ident&quot; for how to withdraw it once that is established.</div><h4>Spam =
definition</h4><div style=3D"font-family:Arial;text-align:start"><a href=3D=
"https://chairs.ietf.org/mailing-lists/disruptive-posting" target=3D"_blank=
">Disruptive posting</a>=C2=A0identifies two types:</div><ul><li style=3D"f=
ont-family:Arial">Messages unrelated to the IETF</li><li style=3D"font-fami=
ly:Arial">Advertising</li></ul><div style=3D"font-family:Arial;text-align:s=
tart">It notes this is a non-exhaustive list. These procedures add:</div><u=
l><li style=3D"font-family:Arial">Messages with no indication that the send=
er is a real person</li><li style=3D"font-family:Arial">Messages with no in=
dication that the sender has an understanding of how the IETF works</li></u=
l><h4>Spam procedure</h4><div style=3D"font-family:Arial;text-align:start">=
If the sender has been automatically held for moderation because they are n=
ot a subscriber to any IETF list:</div><ul><li style=3D"font-family:Arial">=
<div>Decide if they are likely to be a genuine newcomer</div><ul><li style=
=3D"font-family:Arial">If yes, reject with=C2=A0<a href=3D"https://github.c=
om/ietf-moderators/procedures/blob/main/newcomer-rejection-message.txt" tar=
get=3D"_blank">newcomer-rejection-message.txt</a></li><li style=3D"font-fam=
ily:Arial">If no, discard</li></ul></li></ul><div style=3D"font-family:Aria=
l;text-align:start">If it has been held for another reason:</div><ul><li st=
yle=3D"font-family:Arial">Reject or discard as needed</li></ul><div style=
=3D"font-family:Arial;text-align:start">Otherwise, the spam has already bee=
n delivered to subscribers.</div><ul><li style=3D"font-family:Arial"><div>C=
onsider whether it should remain in the mail archive</div><ul><li style=3D"=
font-family:Arial">If appropriate, ask=C2=A0<a href=3D"mailto:support@ietf.=
org" target=3D"_blank">support@ietf.org</a>=C2=A0to hide it</li></ul></li><=
li style=3D"font-family:Arial"><div>If the sender address may have been spo=
ofed:</div><ul><li style=3D"font-family:Arial">Does the tools team need to =
tighten controls?</li><li style=3D"font-family:Arial">Does the sender need =
to tighten DMARC?</li></ul></li><li style=3D"font-family:Arial"><div>If the=
 sender is believed to be genuine:</div><ul><li style=3D"font-family:Arial"=
>Treat as disruption</li></ul></li></ul><h4>Dealing with repeated spam</h4>=
<div style=3D"font-family:Arial;text-align:start">As per the advice in=C2=
=A0<a href=3D"https://chairs.ietf.org/mailing-lists" target=3D"_blank">Spam=
 control</a>:</div><ul><li style=3D"font-family:Arial">Ask=C2=A0<a href=3D"=
mailto:support@ietf.org" target=3D"_blank">support@ietf.org</a>=C2=A0to blo=
ck the address centrally</li><li style=3D"font-family:Arial">For immediate =
results, ban this sender from the affected list (optional)</li></ul><h3>Han=
dling behavior that hinders the work of the group</h3><div style=3D"font-fa=
mily:Arial;text-align:start">This is conduct that may be civil and on topic=
 but obstructs progress: for example, repeatedly arguing against an approve=
d charter, reopening a consensus call without new information, or making th=
e same point in reply after reply so that other voices are drowned out.</di=
v><div style=3D"font-family:Arial;text-align:start">Disagreement, however p=
ersistent, is not disruption. The test is whether the conduct adds to the d=
iscussion, not whether the administrator agrees with it. Asking the chairs =
to revisit a decision with new information, or appealing under=C2=A0<a href=
=3D"https://www.rfc-editor.org/rfc/rfc2026.html#section-6.5" target=3D"_bla=
nk">RFC2026</a>, is never disruption.</div><div style=3D"font-family:Arial;=
text-align:start">Unless the conduct is egregious, first ask the participan=
t to stop; it is an incident if it continues.</div><div style=3D"font-famil=
y:Arial;text-align:start">In the private message, additionally identify the=
 specific conduct, and say that it is the conduct being addressed, not thei=
r technical position.</div><h3>Handling messages containing confidential in=
formation</h3><div style=3D"font-family:Arial;text-align:start">Report the =
message to=C2=A0<a href=3D"mailto:support@ietf.org" target=3D"_blank">suppo=
rt@ietf.org</a>.</div><div style=3D"font-family:Arial;text-align:start">Thi=
s is in addition to, not instead of, handling the incident under the proced=
ure above.</div><h3>Handling repeated inclusion of derivative rights notice=
s</h3><div style=3D"font-family:Arial;text-align:start">Outside of an inter=
net-draft,=C2=A0<a href=3D"https://datatracker.ietf.org/doc/statement-iesg-=
statement-on-clarifying-derivative-works-rights/" target=3D"_blank">IESG St=
atement on Clarifying Derivative Works Rights</a>=C2=A0says that notices th=
at claim that derivative rights are being withheld for a Contribution are n=
ot conformant to IETF policies. Repeated inclusion of such notices is a dis=
ruption.</div><div style=3D"font-family:Arial;text-align:start">In the priv=
ate message, additionally:</div><ul><li style=3D"font-family:Arial">Refer t=
o the=C2=A0<a href=3D"https://datatracker.ietf.org/doc/statement-iesg-state=
ment-on-clarifying-derivative-works-rights/" target=3D"_blank">IESG Stateme=
nt on Clarifying Derivative Works Rights</a></li><li style=3D"font-family:A=
rial">Advise why this notice is not conformant to IETF policies</li><li sty=
le=3D"font-family:Arial">Say that messages without the notice will be allow=
ed through to the list in a timely manner</li></ul><h3>Handling slop</h3><d=
iv style=3D"font-family:Arial;text-align:start">&quot;Slop&quot; is volumin=
ous, low-quality content that does not appear to have been checked by someo=
ne knowledgeable in the field. Slop can be uncivil, spam, or unrelated to t=
he list&#39;s purpose, in which case it can be handled in accordance with t=
he procedures above. Slop is often the product of AI, though administrators=
 are not expected to determine if the content was written by a human. There=
 might be a nugget of a good point in hundreds of words, or it could be com=
plete nonsense.</div><div style=3D"font-family:Arial;text-align:start">Admi=
nistrators should assess if a message is slop:</div><ul><li style=3D"font-f=
amily:Arial">Does it use hundreds of words to make a simple point, or no po=
int at all?</li><li style=3D"font-family:Arial">Is no one engaging meaningf=
ully with the technical content of the message?</li></ul><div style=3D"font=
-family:Arial;text-align:start">If an administrator judges that a message i=
s slop, it counts as an incident.</div><h2>Handling messages held for moder=
ation</h2><div style=3D"font-family:Arial;text-align:start">Assess the mess=
age in a timely manner.</div><ul><li style=3D"font-family:Arial">If it is s=
pam, follow the=C2=A0<a href=3D"https://github.com/ietf-moderators/procedur=
es/blob/main/procedures.md#spam-procedure" target=3D"_blank">spam procedure=
</a></li><li style=3D"font-family:Arial">If it is non-disruptive, allow it =
through</li><li style=3D"font-family:Arial">If disruptive, reject with a re=
ason as to why</li></ul><div style=3D"font-family:Arial;text-align:start">R=
ejecting a held message is not by itself a new incident. If the held messag=
es amount to a fresh occasion of disruption, handle it under &quot;Handling=
 disruption&quot; above.</div><div style=3D"font-family:Arial;text-align:st=
art">If the volume of held messages is unmanageable, the hold may be conver=
ted to a ban for its remaining duration - see &quot;Choosing between a hold=
 and a ban&quot;.</div><div style=3D"font-family:Arial;text-align:start">If=
 the respondent is only sending non-disruptive messages:</div><ul><li style=
=3D"font-family:Arial">You have the option to temporarily remove hold for m=
oderation.</li><li style=3D"font-family:Arial">If disruption recurs, the ho=
ld may be reinstated without notice for the remainder of the sanction perio=
d.</li></ul><h2>Removal of a sanction</h2><div style=3D"font-family:Arial;t=
ext-align:start">On or before the end of the sanction period:</div><ol><li =
style=3D"font-family:Arial">Remove the hold or ban by setting the list defa=
ult action for the respondent</li><li style=3D"font-family:Arial">Send a pr=
ivate message to the respondent confirming the sanction is no longer in pla=
ce, and referring to what the currently-approved procedure says will happen=
 if there is a further incident</li></ol><div style=3D"font-family:Arial;te=
xt-align:start">Removing a sanction does not remove the incident from the c=
ount. It continues to count for five years from the date of the incident.</=
div><h1>Chat moderation</h1><div style=3D"font-family:Arial;text-align:star=
t">Moderation of Zulip chat has different procedures reflecting the synchro=
nous nature of discussion. However, a chat message violates policy if it wo=
uld violate policy as an email to the list, and vice versa.</div><div style=
=3D"font-family:Arial;text-align:start">The Sanctions Ladder does not apply=
 to chat moderation.</div><div style=3D"font-family:Arial;text-align:start"=
>An Administrator detects a message that violates policy. Spam and messages=
 containing confidential information should immediately be deleted. Otherwi=
se, the Administrator sends a public message to the offender indicating tha=
t further lapses will be moderated.</div><div style=3D"font-family:Arial;te=
xt-align:start">On a second offense in the same session, the message is del=
eted and the user is blocked from participation it the chat for the remaind=
er of the session.</div><h1>Open questions</h1><ol><li style=3D"font-family=
:Arial">How do chairs delegate administration responsibility, and how do we=
 track that?</li><li style=3D"font-family:Arial">How do we identify the adm=
inistrators of=C2=A0<a href=3D"https://datatracker.ietf.org/list/nonwg" tar=
get=3D"_blank">non-WG lists</a>?</li></ol><div style=3D"font-family:Arial">=
<br></div><div id=3D"m_-6098973746533477556sig56629417"><div>--</div><div>=
=C2=A0 Bron Gondwana, CEO, Fastmail Pty Ltd / Fastmail US LLC</div><div>=C2=
=A0 <a href=3D"mailto:brong@fastmailteam.com" target=3D"_blank">brong@fastm=
ailteam.com</a></div><div><br></div></div></div>___________________________=
____________________<br>
Mod-discuss mailing list -- <a href=3D"mailto:mod-discuss@ietf.org" target=
=3D"_blank">mod-discuss@ietf.org</a><br>
To unsubscribe send an email to <a href=3D"mailto:mod-discuss-leave@ietf.or=
g" target=3D"_blank">mod-discuss-leave@ietf.org</a><br>
</blockquote></div>

--0000000000002a8dd8066053e144--
