IETF Anti-Harassment Procedures
RFC 7776
| Document | Type |
RFC - Best Current Practice
(March 2016; No errata)
Updated by RFC 8716
Was draft-farrresnickel-harassment (individual in gen area)
|
|
|---|---|---|---|
| Last updated | 2018-12-20 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | Ines Robles | ||
| Shepherd write-up | Show (last changed 2015-09-23) | ||
| IESG | IESG state | RFC 7776 (Best Current Practice) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Jari Arkko | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) P. Resnick
Request for Comments: 7776 Qualcomm Technologies, Inc.
BCP: 25 A. Farrel
Updates: 2418, 7437 Juniper Networks
Category: Best Current Practice March 2016
ISSN: 2070-1721
IETF Anti-Harassment Procedures
Abstract
IETF Participants must not engage in harassment while at IETF
meetings, virtual meetings, or social events or while participating
in mailing lists. This document lays out procedures for managing and
enforcing this policy.
This document updates RFC 2418 by defining new working group
guidelines and procedures. This document updates RFC 7437 by
allowing the Ombudsteam to form a recall petition without further
signatories.
Status of This Memo
This memo documents an Internet Best Current Practice.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7776.
Resnick & Farrel Best Current Practice [Page 1]
RFC 7776 Anti-Harassment Procedures March 2016
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The Ombudsteam . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Size of the Ombudsteam . . . . . . . . . . . . . . . . . 5
3.2. Appointing the Ombudsteam . . . . . . . . . . . . . . . . 5
3.3. Professional Advisors . . . . . . . . . . . . . . . . . . 5
3.4. Qualifications and Training . . . . . . . . . . . . . . . 6
3.5. Term of Service . . . . . . . . . . . . . . . . . . . . . 6
3.6. Compensation . . . . . . . . . . . . . . . . . . . . . . 6
3.7. Removal . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.8. Disputes with the IETF Chair Regarding the Ombudsteam . . 7
4. Handling Reports of Harassment . . . . . . . . . . . . . . . 7
4.1. Ombudsteam Operating Practices . . . . . . . . . . . . . 8
5. Remedies . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.1. Remedies for Respondents in IETF Positions . . . . . . . 11
5.2. Purpose of Remedies . . . . . . . . . . . . . . . . . . . 13
6. Disputes with the Ombudsteam . . . . . . . . . . . . . . . . 14
7. Conflicts of Interest . . . . . . . . . . . . . . . . . . . . 15
8. Confidentiality . . . . . . . . . . . . . . . . . . . . . . . 15
9. Security Considerations . . . . . . . . . . . . . . . . . . . 16
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
10.1. Normative References . . . . . . . . . . . . . . . . . . 16
10.2. Informative References . . . . . . . . . . . . . . . . . 17
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
Resnick & Farrel Best Current Practice [Page 2]
RFC 7776 Anti-Harassment Procedures March 2016
1. Introduction
The IETF has general policies for managing disruptive behavior in the
context of IETF activities. In particular, [RFC7154] provides a set
of guidelines for personal interaction in the IETF, and [RFC2418] and
[RFC3934] give guidelines for how to deal with disruptive behavior
that occurs in the context of IETF working group face-to-face
meetings and on mailing lists.
However, there is other problematic behavior that may be more
personal and that can occur in the context of IETF activities
(meetings, mailing list discussions, or social events) that does not
directly disrupt working group progress but nonetheless is
Show full document text