| rfc9945v1.txt | rfc9945.txt | |||
|---|---|---|---|---|
| skipping to change at line 104 ¶ | skipping to change at line 104 ¶ | |||
| This memo makes the following changes to existing processes: | This memo makes the following changes to existing processes: | |||
| * Obsoletes [RFC3683] as the "posting rights" (PR) action it defines | * Obsoletes [RFC3683] as the "posting rights" (PR) action it defines | |||
| is replaced by processes defined herein; | is replaced by processes defined herein; | |||
| * Obsoletes [RFC3934] as it replaces working group moderation | * Obsoletes [RFC3934] as it replaces working group moderation | |||
| procedures; | procedures; | |||
| * Obsoletes Section 3 of [RFC9245] and the second paragraph of | * Obsoletes Section 3 of [RFC9245] and the second paragraph of | |||
| Section 4 of [RFC9245], as the moderator team replaces the IETF | Section 4 of [RFC9245], as the IETF moderator team defined in this | |||
| discussion list moderation team. | document replaces the IETF discussion list moderator team. | |||
| * Updates Section 6.1 of [RFC2418], because the moderator team will | * Updates Section 6.1 of [RFC2418], because the moderator team will | |||
| work together with working group chairs to moderate disruptive | work together with working group chairs to moderate disruptive | |||
| behavior. | behavior. | |||
| The processes described in this memo are solely applicable to IETF | The processes described in this memo are solely applicable to IETF | |||
| activities, and not to other related organizations, such as the | activities, and not to other related organizations, such as the | |||
| Internet Research Task Force (IRTF), the Internet Architecture Board | Internet Research Task Force (IRTF), the Internet Architecture Board | |||
| (IAB), the RFC Series Working Group (RSWG), the RFC Series Approval | (IAB), the RFC Series Working Group (RSWG), the RFC Series Approval | |||
| Board (RSAB), or the Independent RFC Submission Stream, without their | Board (RSAB), or the Independent RFC Submission Stream, without their | |||
| skipping to change at line 169 ¶ | skipping to change at line 169 ¶ | |||
| * Balance transparency against both privacy of individuals involved | * Balance transparency against both privacy of individuals involved | |||
| and further disruption to the community; | and further disruption to the community; | |||
| * Allow moderation decisions to be reconsidered; and | * Allow moderation decisions to be reconsidered; and | |||
| * Provide the broadest possible latitude to all people doing | * Provide the broadest possible latitude to all people doing | |||
| moderation, so that they have the flexibility to address a broad | moderation, so that they have the flexibility to address a broad | |||
| range of individuals and circumstances. | range of individuals and circumstances. | |||
| Questions about the processes detailed below should be answered | Questions about the processes detailed below should be answered with | |||
| through the lens of these aims. | these goals in mind. | |||
| The objective is explicitly *not* punishment, but to maintain an | The objective is explicitly *not* punishment, but to maintain an | |||
| open, welcoming, non-hostile environment in which all may participate | open, welcoming, non-hostile environment in which all may participate | |||
| on an equal footing, regardless of their role in the IETF or past | on an equal footing, regardless of their role in the IETF or past | |||
| technical contributions. | technical contributions. | |||
| 2. IETF Moderator Team | 2. IETF Moderator Team | |||
| This memo defines a consistent approach to moderating the IETF's | This memo defines a consistent approach to moderating the IETF's | |||
| various public online fora. A moderator team for the IETF will | various public online fora. A moderator team for the IETF will | |||
| skipping to change at line 199 ¶ | skipping to change at line 199 ¶ | |||
| The IESG appoints and recalls moderators. The moderator team | The IESG appoints and recalls moderators. The moderator team | |||
| initially consists of no fewer than five individuals. The moderator | initially consists of no fewer than five individuals. The moderator | |||
| team may expand or contract based on operational experience. In | team may expand or contract based on operational experience. In | |||
| selecting members, the IESG will take into account geographic | selecting members, the IESG will take into account geographic | |||
| coverage, expected and unexpected absences, and team diversity. | coverage, expected and unexpected absences, and team diversity. | |||
| Because the IESG and IAB are in the appeals chain for moderator team | Because the IESG and IAB are in the appeals chain for moderator team | |||
| decisions (see Section 4.1), the IESG must not appoint a moderator | decisions (see Section 4.1), the IESG must not appoint a moderator | |||
| who is serving on the IESG or IAB. Individuals serving on other | who is serving on the IESG or IAB. Individuals serving on other | |||
| bodies to which the NomCom appoints members, such as the IETF Trust | bodies to which the NomCom appoints members, such as the IETF Trust | |||
| or the LLC Board, as well as LLC staff and contractors, shall also be | or the IETF LLC Board, as well as IETF LLC staff and contractors | |||
| excluded from serving on the moderator team. If a moderator assumes | shall also be excluded from serving on the moderator team. If a | |||
| any such role, they shall step down from the moderator team soon | moderator assumes any such role, they shall step down from the | |||
| after. | moderator team soon after. | |||
| 2.1.1. Team Diversity | 2.1.1. Team Diversity | |||
| Due to the global nature of the IETF, the membership of this team | Due to the global nature of the IETF, the membership of this team | |||
| should reflect a diversity of time zones and other participant | should reflect a diversity of time zones and other participant | |||
| characteristics that lets it operate effectively around the clock and | characteristics that lets it operate effectively around the clock and | |||
| throughout the year. Ideally, the moderators should be able to | throughout the year. Ideally, the moderators should be able to | |||
| respond to issues within a few hours. | respond to issues within a few hours. | |||
| Team diversity is also important to ensure any participant observing | Team diversity also improves the likelihood that any participant | |||
| disruptive behavior can identify a moderator they feel comfortable | experiencing or observing disruptive behavior can identify a | |||
| contacting. | moderator they feel comfortable contacting. | |||
| 2.2. Training | 2.2. Training | |||
| The IETF is committed to providing and/or funding training for | The IETF is committed to providing and/or funding training for | |||
| administrators and moderators as necessary. The IESG will negotiate | administrators and moderators as necessary. The IESG will negotiate | |||
| any required funding or resources with IETF Administration LLC | any required funding or resources with IETF Administration LLC | |||
| [RFC8711]. | [RFC8711]. | |||
| 3. Scope and Responsibilities | 3. Scope and Responsibilities | |||
| skipping to change at line 401 ¶ | skipping to change at line 401 ¶ | |||
| A suspension of participation privileges imposed prior to this | A suspension of participation privileges imposed prior to this | |||
| process shall be reconsidered only in accordance with the processes | process shall be reconsidered only in accordance with the processes | |||
| in place at the time of the suspension, even if the corresponding RFC | in place at the time of the suspension, even if the corresponding RFC | |||
| has been formally obsoleted. | has been formally obsoleted. | |||
| 5. Relationship to Other IETF Functions | 5. Relationship to Other IETF Functions | |||
| 5.1. Relation to the Ombudsteam | 5.1. Relation to the Ombudsteam | |||
| Administrators and moderators shall complement the efforts of the | Administrators and moderators shall complement the efforts of the | |||
| IETF Ombudsteam [OT], whose focus on anti-harassment and operation | IETF Ombudsteam [OT], whose focus on anti-harassment shall remain | |||
| shall remain unchanged. Administrators and moderators should always | unchanged. Administrators and moderators should always report | |||
| report suspected harassment. They should nonetheless take any | suspected harassment. They should nonetheless take any necessary | |||
| necessary actions regarding disruptive behavior. | actions regarding disruptive behavior. | |||
| 5.2. Relation to the IETF LLC | 5.2. Relation to the IETF LLC | |||
| The Board of Directors of the IETF Administration LLC (IETF LLC) has | The Board of Directors of the IETF Administration LLC (IETF LLC) has | |||
| fiduciary duty for the overall organization, which includes the duty | fiduciary duty for the overall organization, which includes the duty | |||
| to protect the organization from serious legal risk that may arise | to protect the organization from serious legal risk that may arise | |||
| from the behavior of IETF participants. | from the behavior of IETF participants. | |||
| This protection may include the need for the IETF LLC to take | This protection may include the need for the IETF LLC to take | |||
| emergency moderation actions. These emergency actions are expected | emergency moderation actions. These emergency actions are expected | |||
| skipping to change at line 680 ¶ | skipping to change at line 680 ¶ | |||
| IESG statement [DP] clarifies that the IESG tasks list administrators | IESG statement [DP] clarifies that the IESG tasks list administrators | |||
| with moderation. And the IETF list for general discussions has, | with moderation. And the IETF list for general discussions has, | |||
| mostly for historic reasons, a team of moderators that are not list | mostly for historic reasons, a team of moderators that are not list | |||
| administrators and operate by a different set of processes [RFC9245]. | administrators and operate by a different set of processes [RFC9245]. | |||
| Note that the term "moderation" can refer both to _preemptive_ | Note that the term "moderation" can refer both to _preemptive_ | |||
| moderation, where administrators review attempted participation | moderation, where administrators review attempted participation | |||
| before it occurs (such as reviewing messages to a mailing list), and | before it occurs (such as reviewing messages to a mailing list), and | |||
| _reactive_ moderation, where administrators intervene after | _reactive_ moderation, where administrators intervene after | |||
| disruptive participation has occurred. Historically, the IETF has | disruptive participation has occurred. Historically, the IETF has | |||
| mainly practiced reactive moderation, with a spectrum from gentle | mainly practiced reactive moderation, employing actions ranging from | |||
| reminders on- and off-list, all the way to suspension of posting | gentle reminders on- and off-list, all the way to suspension of | |||
| rights and other ways of participating or communicating. It is up to | posting rights and other ways of participating or communicating. It | |||
| the moderators and administrators to decide which mix of preemptive | is up to the moderators and administrators to decide which mix of | |||
| and reactive moderation to employ as part of their procedures. | preemptive and reactive moderation to employ as part of their | |||
| procedures. | ||||
| In addition, [RFC3683] defines a process for revoking an individual's | In addition, [RFC3683] defines a process for revoking an individual's | |||
| posting rights to IETF mailing lists following a community Last Call | posting rights to IETF mailing lists following a community Last Call | |||
| of a "posting rights" action (PR-action) proposed by the IESG, often | of a "posting rights" action (PR-action) proposed by the IESG, often | |||
| in response to complaints from the community. | in response to complaints from the community. | |||
| Experience and community input suggests that an evolution of the | Experience and community input suggests that an evolution of the | |||
| existing processes is necessary. | existing processes is necessary. | |||
| A.2. Problems with the Previous Approach | A.2. Problems with the Previous Approach | |||
| skipping to change at line 733 ¶ | skipping to change at line 734 ¶ | |||
| * For a given mailing list, participants may not feel comfortable | * For a given mailing list, participants may not feel comfortable | |||
| reporting disruptive behavior to a chair or list administrator, | reporting disruptive behavior to a chair or list administrator, | |||
| for various reasons. For mailing lists not associated with | for various reasons. For mailing lists not associated with | |||
| working groups, list administrators are not even publicly | working groups, list administrators are not even publicly | |||
| identified -- they can only be contacted through an anonymous | identified -- they can only be contacted through an anonymous | |||
| alias address. This exacerbates the problem, because participants | alias address. This exacerbates the problem, because participants | |||
| may not be comfortable reporting disruptive behavior to an | may not be comfortable reporting disruptive behavior to an | |||
| anonymous party. | anonymous party. | |||
| * The IETF offers participation not only through in-person meetings | * Moderation processes have been defined for only two channels of | |||
| and mailing lists, which are the two channels of participation for | participation in the IETF: in-person meetings and mailing lists. | |||
| which moderation processes are currently defined. IETF business | However, IETF business now happens in a number of fora (e.g., chat | |||
| also happens in chat groups, remote meeting participation systems, | groups, remote meeting participation systems, virtual meetings, | |||
| virtual meetings, wikis, GitHub repositories, and more. How | wikis, and GitHub repositories). Procedures for moderating | |||
| disruptive behavior is moderated in these fora is currently | disruptive behavior in these fora are currently undefined. | |||
| undefined. | ||||
| Appendix B. Non-Normative Examples of Disruptive Behavior | Appendix B. Non-Normative Examples of Disruptive Behavior | |||
| The list below describes some types of disruptive behavior, but it is | The list below describes some types of disruptive behavior, but it is | |||
| non-exhaustive. | non-exhaustive. | |||
| * Discussion of subjects unrelated to a forum's charter or scope; | * Discussion of subjects unrelated to a forum's charter or scope; | |||
| * Uncivil commentary, regardless of the general subject; | * Uncivil commentary, regardless of the general subject; | |||
| End of changes. 7 change blocks. | ||||
| 27 lines changed or deleted | 27 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||