6. Security Considerations
This section preserves the RFC text for IETF community moderation, including disruptive participation, the moderator team, procedures, transparency, appeals, reinstatement, and relationships to the Ombudsteam and IETF LLC.
Original RFC Text
6. Security Considerations
The usual security considerations [RFC3552] do not apply to this
memo.
There is the potential abuse of the moderation procedures by
moderators, working group chairs, and potentially others that could
lead to censorship of legitimate participation. This potential risk
is mitigated in eight ways:
1. Section 4 requires the moderator team to first establish
procedures that are intended to apply uniformly across the IETF.
2. Section 1.2 explicitly states that viewpoints outside the rough
consensus are not in and of themselves disruptive.
3. Section 4 provides transparency by requiring that moderation
actions that restrict participation privileges be immediately
reported to the affected person and to the moderator team, and
periodically reported to the IESG.
4. Section 4 also requires that the community be informed in the
case of suspensions lasting longer than 14 days.
5. Section 4.1 lays out an appeals process in the case of
disagreements.
6. If moderators find that the procedures themselves are leading to
inappropriate moderation, Section 4 allows them to update those
procedures in consultation with the community and with the
approval of the IESG.
7. If IETF participants believe that either the IESG or the IAB are
not performing their respective oversight functions as described
in this document, they may comment to the NomCom [BCP10] or the
community at large.
8. Finally, if it appears that these processes are not functioning
properly, the policies stated in this memo may be amended. They
are not set in stone.
Moderation actions are intended to limit the likelihood of disruptive
behavior by a few IETF participants that may discourage participation
by other IETF participants.