<?xml version="1.0" encoding="UTF-8"?> version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC7776 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7776.xml">
<!ENTITY RFC7437 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7437.xml">
]>
<?xml-stylesheet type="text/xsl" href="http://xml.resource.org/authoring/rfc2629.xslt" ?>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<?rfc comments="yes" ?>
<?rfc inline="yes" ?> "rfc2629-xhtml.ent">
<rfc
xmlns:xi="http://www.w3.org/2001/XInclude"
number="8716"
updates="7776"
obsoletes=""
category="bcp" seriesNo="25" docName="draft-ietf-iasa2-rfc7776bis-03"
consensus="true"
submissionType="IETF"
ipr="trust200902" updates="7776">
sortRefs="true"
symRefs="true"
xml:lang="en"
docName="draft-ietf-iasa2-rfc7776bis-03"
tocInclude="true"
version="3">
  <!-- xml2rfc v2v3 conversion 2.34.0 -->
  <front>
    <title abbrev="Anti-Harassment LLC Update">Update to the IETF
    Anti-Harassment Procedures for the Replacement of the IAOC IETF Administrative
    Oversight Committee (IAOC) with the IETF Administration LLC</title>
    <seriesInfo name="RFC" value="8716"/>
    <seriesInfo name="BCP" value="25"/>
    <author fullname="Pete Resnick" initials="P." surname="Resnick">
      <organization>Episteme Technology Consulting LLC</organization>
      <address>
        <postal>
          <street>503 West Indiana Avenue</street>
          <city>Urbana</city>
          <region>Illinois</region>
          <country>United States</country> States of America</country>
          <code>61801-4941</code>
        </postal>
        <phone>+1 217 337 1905</phone>
        <email>resnick@episteme.net</email>
      </address>
    </author>
    <author fullname="Adrian Farrel" initials="A." surname="Farrel">
      <organization>Old Dog Consulting</organization>
      <address>
        <email>adrian@olddog.co.uk</email>
      </address>
    </author>
    <date /> month="January" year="2020"/>
    <area>General</area>
    <workgroup>IASA 2.0</workgroup>
    <keyword>Harassment</keyword>
    <keyword>Ombudsteam</keyword>
    <keyword>IAOC</keyword>
    <keyword>IETF Administrative Administration LLC</keyword>
    <abstract>
      <t>The IETF Anti-Harassment Procedures are described in RFC 7776.</t>
      <t>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.</t>
      <t>RFC 7776 contained updates to RFC 7437.  draft-ietf-iasa2-rfc7437bis  RFC 8713 has incorporated those updates, so this document also updates RFC 7776 to remove those updates.</t>
    </abstract>

        <note title="NOTE

<!-- [rfced] AD: FYI, regarding the following text, upon publication, we will
update the metadata for RFC Editor RFCs 7437 and Readers of this Document">
          <t>When published as an RFC
             <list style="symbols">
               <t>All references 7776 to and mentions of draft-ietf-iasa2-rfc7437bis in this document should be replaced by remove the RFC Updated by / Updates
relationship. Please let us know if that results from draft-ietf-iasa2-rfc7437bis.</t>
               <t>The string "XXXX" should be replaced with is not the intention.

Abstract:
   RFC number assigned 7776 contained updates to the RFC that results from draft-ietf-iasa2-rfc7437bis.</t>
               <t>This note should be removed.</t>
             </list></t>
          <t>*** END OF NOTE ***</t>
        </note> 7437.  RFC 8713 has incorporated
   those updates, so this document also updates RFC 7776 to remove those
   updates.
-->
  </front>
  <middle>
    <section anchor="intro" title="Introduction"> numbered="true" toc="default">
      <name>Introduction</name>
      <t>The IETF Anti-Harassment Procedures are described in RFC 7776 <xref target="RFC7776" />. format="default"/>.  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.</t>
      <t>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 term terms and to update a reference.</t>
      <t>RFC 7776 contained updates to [RFC7437].  [I-D.ietf-iasa2-rfc7437bis] <xref target="RFC7437" format="default"/>.  <xref target="RFC8713" format="default"/> has incorporated those updates, so this document also updates RFC 7776 to remove those updates.</t>
      <t>This document makes no other changes to the procedures described in RFC 7776.</t>
    </section>
    <section anchor="changes" title="Changes numbered="true" toc="default">
      <name>Changes to RFC 7776"> 7776</name>
      <section anchor="changes3" title="Changes numbered="true" toc="default">
        <name>Changes to Section 3.4">
            <t>Section 3.4 of RFC 7776 <xref 3.4</name>

        <t><xref target="RFC7776" /> section="3.4" sectionFormat="of"
	format="default"/> is about Qualifications the qualifications and Training. training of the Ombudsteam.  The last paragraph of that section is replaced as follows:</t>
        <t>OLD
               <list style="none">
                  <t>In
        </t>
          <blockquote>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.</t>
               </list></t> budget.</blockquote>
        <t>NEW
               <list style="none">
                  <t>In
        </t>
          <blockquote>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.</t>
               </list></t> budget.</blockquote>
        <t>END</t>
      </section>
      <section anchor="changes5" title="Changes numbered="true" toc="default">
        <name>Changes to Section 5">
            <t>Section 5 of RFC  7776 <xref 5</name>

        <t><xref target="RFC7776" /> section="5" sectionFormat="of" format="default"/> is about Remedies (available remedies available to the Ombudsteam). Ombudsteam.  The last paragraph of that section is replaced as follows:</t>
        <t>OLD
               <list style="none">
                  <t>Where
        </t>
          <blockquote>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.</t>
               </list></t> appropriate.</blockquote>
        <t>NEW
               <list style="none">
                  <t>Where
        </t>
          <blockquote>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.</t>
               </list></t> appropriate.</blockquote>
        <t>END</t>
      </section>
      <section anchor="changesref" title="Changes numbered="true" toc="default">
        <name>Changes to References to RFC 7437"> 7437</name>
        <t>RFC 7776 updated RFC 7437 <xref target="RFC7437" /> format="default"/> by allowing the Obmudsteam Ombudsteam to form a recall petition.  This document does not change any of the associated processes, however processes. However,
               during the process of documenting the replacement of the IAOC by the IETF Administration LLC, RFC 7437 has been obsoleted by <xref target="I-D.ietf-iasa2-rfc7437bis"/>, target="RFC8713" format="default"/>, and as part
               of that work, <xref target="I-D.ietf-iasa2-rfc7437bis"/> target="RFC8713" format="default"/> has included the update from RFC 7776.</t>
        <t>This document updates RFC 7776 to remove the update of RFC 7437.</t>

        <section anchor="changemeta" title="Changes numbered="true" toc="default">
          <name>Changes to Metadata"> Metadata</name>
          <t>The following change is made to the metadata at the head of <xref target="RFC7776"/>:</t> target="RFC7776" format="default"/>:</t>
          <t>OLD
                 <list style="none">
                    <t>Updates:
          </t>
            <blockquote>Updates: 2418, 7437</t>
                 </list></t> 7437</blockquote>
          <t>NEW
                 <list style="none">
                    <t>Updates: 2418</t>
                 </list></t>
          </t>
            <blockquote>Updates: 2418</blockquote>
          <t>END</t>
        </section>
        <section anchor="changeab" title="Changes numbered="true" toc="default">
          <name>Changes to the Abstract"> Abstract</name>
          <t>The following change is made to text in the Abstract of <xref target="RFC7776"/>:</t> target="RFC7776" format="default"/>:</t>
          <t>DELETE
                 <list style="none">
                    <t>This
          </t>
            <blockquote>This document updates RFC 7437 by allowing the Ombudsteam to form a recall petition without further signatories.</t>
                 </list></t> signatories.</blockquote>
          <t>END</t>
        </section>
        <section anchor="change5-1" title="Changes numbered="true" toc="default">
          <name>Changes to Section 5.1"> 5.1</name>
          <t>The following change is made to text in Section 5.1 of <xref target="RFC7776"/></t> target="RFC7776" section="5.1" sectionFormat="of" format="default"/>:</t>
          <t>OLD
                 <list style="symbols">
                   <t>Many
          </t>
          <blockquote>
          <ul spacing="normal">
            <li>Many IETF management positions are appointed by the NomCom with confirmation from the IESG, IAB, or ISOC.  <xref target="RFC7437" /> format="default"/> describes the
                      recall procedure for such appointments.  This document updates <xref target="RFC7437" /> format="default"/> 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 <xref target="RFC7437" />: format="default"/>: 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.</t>
                 </list></t> remedy.</li></ul></blockquote>
          <t>NEW
                 <list style="symbols">
                   <t>The
          </t>
          <blockquote>
          <ul spacing="normal">
            <li>The Ombudsteam may form a recall petition on its own without requiring signatures from the community as described in <xref target="I-D.ietf-iasa2-rfc7437bis"/>.</t>
                 </list></t> target="RFC8713" format="default"/>.</li></ul></blockquote>
          <t>END</t>
        </section>
      </section>
    </section>
    <section title="IANA Considerations"> numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This document makes has no request for IANA action.</t> actions.</t>
    </section>
    <section title="Security Considerations"> numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>This document has no implications for Internet security.</t>
    </section>
  </middle>
  <back>

        <references title="Normative References">
            &RFC7776;
            <?rfc include="reference.I-D.ietf-iasa2-rfc7437bis"?>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7776.xml"/>
        <!-- draft-ietf-iasa2-rfc7437bis [RFC8713] in cluster -->
        <reference anchor="RFC8713" target="https://rfc-editor.org/info/rfc8713">
          <front>
            <title>IAB, IESG, and IETF LLC Selection, Confirmation, and
                         Recall Process: Operation of the IETF Nominating and
                         Recall Committees</title>
            <author initials="M." surname="Kucherawy" role="editor">
              <organization/>
            </author>
            <author initials="R." surname="Hinden" role="editor">
              <organization/>
            </author>
            <author initials="J." surname="Livingood" role="editor">
              <organization/>
            </author>
            <date month="January" year="2020"/>
          </front>
          <seriesInfo name="BCP" value="10"/>
          <seriesInfo name="RFC" value="8713"/>
          <seriesInfo name="DOI" value="10.17487/RFC8713"/>
        </reference>
      </references>
      <references>
        <name>Informative References</name>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7437.xml"/>
      </references>

        <references title="Informative References">
            &RFC7437;
    </references>
    <section title="Acknowledgements"> numbered="false" toc="default">
      <name>Acknowledgements</name>
      <t>Thanks to Jason Livingwood <contact fullname="Jason Livingood"/> for suggesting the need for this document.</t>
            <t>Subramanian Moonesamy, Sean Turner, Jon Peterson, Roman Danyliw,

      <t><contact fullname="Subramanian Moonesamy"/>, <contact fullname="Sean
      Turner"/>, <contact fullname="Jon Peterson"/>, <contact fullname="Roman
      Danyliw"/>, and Barry Leiba <contact fullname="Barry Leiba"/> raised useful points
      during their reviews of this work.</t>
    </section>
  </back>
</rfc>