Update to the IETF Anti-Harassment Procedures for the Replacement of the IETF Administrative Oversight Committee (IAOC) with the IETF Administration LLC Episteme Technology Consulting LLC
503 West Indiana Avenue Urbana Illinois United States of America 61801-4941 +1 217 337 1905 resnick@episteme.net
Old Dog Consulting
adrian@olddog.co.uk
General IASA 2.0 Harassment Ombudsteam IAOC IETF Administration LLC IASA The IETF Anti-Harassment Procedures are described in RFC 7776. The IETF Administrative Oversight Committee (IAOC) has been replaced by the IETF Administration LLC, and the IETF Administrative Director has been replaced by the IETF LLC Executive Director. This document updates RFC 7776 to amend these terms. RFC 7776 contained updates to RFC 7437. RFC 8713 has incorporated those updates, so this document also updates RFC 7776 to remove those updates.
Introduction The IETF Anti-Harassment Procedures are described in RFC 7776 . Those procedures include direction for the IETF Chair and Ombudsteam to take advice from the IETF Administrative Oversight Committee (IAOC) with respect to the budget available for training. The IAOC has been replaced by the IETF Administration LLC, and the IETF Administrative Director has been replaced by the IETF LLC Executive Director. This document updates RFC 7776 to amend these terms and to update a reference. RFC 7776 contained updates to . has incorporated those updates, so this document also updates RFC 7776 to remove those updates. This document makes no other changes to the procedures described in RFC 7776.
Changes to RFC 7776
Changes to Section 3.4 is about the qualifications and training of the Ombudsteam. The last paragraph of that section is replaced as follows: OLD
In determining the appropriate training, the IETF Chair and Ombudsteam shall take professional advice and will consult with the IETF Administrative Oversight Committee (IAOC) with respect to the overall IETF budget.
NEW
In determining the appropriate training, the IETF Chair and Ombudsteam shall take professional advice and will consult with the IETF Administration LLC with respect to the overall IETF budget.
END
Changes to Section 5 is about remedies available to the Ombudsteam. The last paragraph of that section is replaced as follows: OLD
Where specific action is required to ensure that a remedy is realized or enforced, the Ombudsteam will make a request in writing to the IETF Secretariat and/or IETF Administrative Director (IAD) to take action as appropriate.
NEW
Where specific action is required to ensure that a remedy is realized or enforced, the Ombudsteam will make a request in writing to the IETF Secretariat and/or IETF LLC Executive Director to take action as appropriate.
END
Changes to References to RFC 7437 RFC 7776 updated RFC 7437 by allowing the Ombudsteam to form a recall petition. This document does not change any of the associated processes. However, during the process of documenting the replacement of the IAOC by the IETF Administration LLC, RFC 7437 has been obsoleted by , and as part of that work, has included the update from RFC 7776. This document updates RFC 7776 to remove the update of RFC 7437.
Changes to Metadata The following change is made to the metadata at the head of : OLD
Updates: 2418, 7437
NEW
Updates: 2418
END
Changes to the Abstract The following change is made to text in the Abstract of : DELETE
This document updates RFC 7437 by allowing the Ombudsteam to form a recall petition without further signatories.
END
Changes to Section 5.1 The following change is made to text in : OLD
  • Many IETF management positions are appointed by the NomCom with confirmation from the IESG, IAB, or ISOC. describes the recall procedure for such appointments. This document updates by allowing the Ombudsteam to form a recall petition on its own and without requiring 20 signatories from the community. Such a petition shall be treated in all ways like any other recall petition as described in : that is, the fact of the petition and its signatories (the Ombudsteam) shall be announced to the IETF community, and a Recall Committee Chair shall be appointed to complete the Recall Committee process. It is expected that the Recall Committee will receive a briefing from the Ombudsteam explaining why recall is considered an appropriate remedy.
NEW
  • The Ombudsteam may form a recall petition on its own without requiring signatures from the community as described in .
END
IANA Considerations This document has no IANA actions.
Security Considerations This document has no implications for Internet security.
References Normative References IAB, IESG, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees Informative References
Acknowledgements Thanks to for suggesting the need for this document. , , , , and raised useful points during their reviews of this work.