rfc8716xml2.original.xml   rfc8716.xml 
<?xml version="1.0" encoding="UTF-8"?> <?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<!ENTITY RFC7776 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC <rfc
.7776.xml"> xmlns:xi="http://www.w3.org/2001/XInclude"
<!ENTITY RFC7437 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC number="8716"
.7437.xml"> updates="7776"
]> obsoletes=""
<?xml-stylesheet type="text/xsl" href="http://xml.resource.org/authoring/rfc2629 category="bcp"
.xslt" ?> consensus="true"
<?rfc strict="yes" ?> submissionType="IETF"
<?rfc toc="yes"?> ipr="trust200902"
<?rfc tocdepth="4"?> sortRefs="true"
<?rfc symrefs="yes"?> symRefs="true"
<?rfc sortrefs="yes" ?> xml:lang="en"
<?rfc compact="yes" ?> docName="draft-ietf-iasa2-rfc7776bis-03"
<?rfc subcompact="no" ?> tocInclude="true"
<?rfc comments="yes" ?> version="3">
<?rfc inline="yes" ?> <!-- xml2rfc v2v3 conversion 2.34.0 -->
<rfc category="bcp" seriesNo="25" docName="draft-ietf-iasa2-rfc7776bis-03" ipr=" <front>
trust200902" updates="7776"> <title abbrev="Anti-Harassment LLC Update">Update to the IETF
<front> Anti-Harassment Procedures for the Replacement of the IETF Administrative
<title abbrev="Anti-Harassment LLC Update">Update to the IETF Anti-Haras Oversight Committee (IAOC) with the IETF Administration LLC</title>
sment Procedures for the Replacement of the IAOC with the IETF Administration LL <seriesInfo name="RFC" value="8716"/>
C</title> <seriesInfo name="BCP" value="25"/>
<author fullname="Pete Resnick" initials="P." surname="Resnick"> <author fullname="Pete Resnick" initials="P." surname="Resnick">
<organization>Episteme Technology Consulting LLC</organization> <organization>Episteme Technology Consulting LLC</organization>
<address> <address>
<postal> <postal>
<street>503 West Indiana Avenue</street> <street>503 West Indiana Avenue</street>
<city>Urbana</city> <city>Urbana</city>
<region>Illinois</region> <region>Illinois</region>
<country>United States</country> <country>United States of America</country>
<code>61801-4941</code> <code>61801-4941</code>
</postal> </postal>
<phone>+1 217 337 1905</phone> <phone>+1 217 337 1905</phone>
<email>resnick@episteme.net</email> <email>resnick@episteme.net</email>
</address> </address>
</author> </author>
<author fullname="Adrian Farrel" initials="A." <author fullname="Adrian Farrel" initials="A." surname="Farrel">
surname="Farrel"> <organization>Old Dog Consulting</organization>
<organization>Old Dog Consulting</organization> <address>
<email>adrian@olddog.co.uk</email>
<address> </address>
<email>adrian@olddog.co.uk</email> </author>
</address> <date month="January" year="2020"/>
</author> <area>General</area>
<workgroup>IASA 2.0</workgroup>
<date /> <keyword>Harassment</keyword>
<keyword>Ombudsteam</keyword>
<keyword>IAOC</keyword>
<keyword>IETF 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 repl
aced by the IETF LLC Executive Director. This document updates RFC 7776 to amen
d these terms.</t>
<t>RFC 7776 contained updates to RFC 7437. RFC 8713 has incorporated thos
e updates, so this document also updates RFC 7776 to remove those updates.</t>
</abstract>
<area>General</area> <!-- [rfced] AD: FYI, regarding the following text, upon publication, we will
<workgroup>IASA 2.0</workgroup> update the metadata for RFCs 7437 and 7776 to remove the Updated by / Updates
relationship. Please let us know if that is not the intention.
<keyword>Harassment</keyword> Abstract:
<keyword>Ombudsteam</keyword> RFC 7776 contained updates to RFC 7437. RFC 8713 has incorporated
<keyword>IAOC</keyword> those updates, so this document also updates RFC 7776 to remove those
<keyword>IETF Administrative LLC</keyword> updates.
-->
</front>
<middle>
<section anchor="intro" numbered="true" toc="default">
<name>Introduction</name>
<t>The IETF Anti-Harassment Procedures are described in RFC 7776 <xref tar
get="RFC7776" format="default"/>. Those procedures include direction for the IE
TF Chair and Ombudsteam to take advice from the IETF Administrative Oversight Co
mmittee (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 terms and to update a reference.</
t>
<t>RFC 7776 contained updates to <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" numbered="true" toc="default">
<name>Changes to RFC 7776</name>
<section anchor="changes3" numbered="true" toc="default">
<name>Changes to Section 3.4</name>
<abstract> <t><xref target="RFC7776" section="3.4" sectionFormat="of"
<t>The IETF Anti-Harassment Procedures are described in RFC 7776.</t format="default"/> is about the qualifications and training of the Ombuds
> team. The last paragraph of that section is replaced as follows:</t>
<t>The IETF Administrative Oversight Committee (IAOC) has been repla <t>OLD
ced by the IETF Administration LLC, and the IETF Administrative Director has bee </t>
n replaced by the IETF LLC Executive Director. This document updates RFC 7776 t <blockquote>In determining the appropriate training, the IETF Chair an
o amend these terms.</t> d Ombudsteam shall take professional advice and will consult with the IETF Admin
<t>RFC 7776 contained updates to RFC 7437. draft-ietf-iasa2-rfc7437 istrative Oversight Committee (IAOC) with respect to the overall IETF budget.</b
bis has incorporated those updates, so this document also updates RFC 7776 to re lockquote>
move those updates.</t> <t>NEW
</abstract> </t>
<blockquote>In determining the appropriate training, the IETF Chair an
d Ombudsteam shall take professional advice and will consult with the IETF Admin
istration LLC with respect to the overall IETF budget.</blockquote>
<t>END</t>
</section>
<section anchor="changes5" numbered="true" toc="default">
<name>Changes to Section 5</name>
<note title="NOTE for RFC Editor and Readers of this Document"> <t><xref target="RFC7776" section="5" sectionFormat="of" format="default
<t>When published as an RFC "/> is about remedies available to the Ombudsteam. The last paragraph of that s
<list style="symbols"> ection is replaced as follows:</t>
<t>All references to and mentions of draft-ietf-iasa2-rfc7437bis <t>OLD
in this document should be replaced by the RFC that results from draft-ietf-iasa </t>
2-rfc7437bis.</t> <blockquote>Where specific action is required to ensure that a remedy
<t>The string "XXXX" should be replaced with the RFC number assig is realized or enforced, the Ombudsteam will make a request in writing to the IE
ned to the RFC that results from draft-ietf-iasa2-rfc7437bis.</t> TF Secretariat and/or IETF Administrative Director (IAD) to take action as appro
<t>This note should be removed.</t> priate.</blockquote>
</list></t> <t>NEW
<t>*** END OF NOTE ***</t> </t>
</note> <blockquote>Where specific action is required to ensure that a remedy
</front> is realized or enforced, the Ombudsteam will make a request in writing to the IE
TF Secretariat and/or IETF LLC Executive Director to take action as appropriate.
</blockquote>
<t>END</t>
</section>
<section anchor="changesref" numbered="true" toc="default">
<name>Changes to References to RFC 7437</name>
<t>RFC 7776 updated RFC 7437 <xref target="RFC7437" format="default"/> b
y allowing the Ombudsteam to form a recall petition. This document does not cha
nge 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 <xref target="RFC871
3" format="default"/>, and as part
of that work, <xref target="RFC8713" format="default"/> has inclu
ded the update from RFC 7776.</t>
<t>This document updates RFC 7776 to remove the update of RFC 7437.</t>
<middle> <section anchor="changemeta" numbered="true" toc="default">
<section anchor="intro" title="Introduction"> <name>Changes to Metadata</name>
<t>The IETF Anti-Harassment Procedures are described in RFC 7776 <xr <t>The following change is made to the metadata at the head of <xref t
ef target="RFC7776" />. Those procedures include direction for the IETF Chair a arget="RFC7776" format="default"/>:</t>
nd Ombudsteam to take advice from the IETF Administrative Oversight Committee (I <t>OLD
AOC) with respect to the budget available for training.</t> </t>
<t>The IAOC has been replaced by the IETF Administration LLC, and th <blockquote>Updates: 2418, 7437</blockquote>
e IETF Administrative Director has been replaced by the IETF LLC Executive Direc <t>NEW
tor. This document updates RFC 7776 to amend these term and to update a referen </t>
ce.</t> <blockquote>Updates: 2418</blockquote>
<t>RFC 7776 contained updates to [RFC7437]. [I-D.ietf-iasa2-rfc7437 <t>END</t>
bis] has incorporated those updates, so this document also updates RFC 7776 to r
emove those updates.</t>
<t>This document makes no other changes to the procedures described
in RFC 7776.</t>
</section> </section>
<section anchor="changeab" numbered="true" toc="default">
<section anchor="changes" title="Changes to RFC 7776"> <name>Changes to the Abstract</name>
<t>The following change is made to text in the Abstract of <xref targe
<section anchor="changes3" title="Changes to Section 3.4"> t="RFC7776" format="default"/>:</t>
<t>Section 3.4 of RFC 7776 <xref target="RFC7776" /> is about Qualif <t>DELETE
ications and Training. The last paragraph of that section is replaced as follow </t>
s:</t> <blockquote>This document updates RFC 7437 by allowing the Ombudstea
<t>OLD m to form a recall petition without further signatories.</blockquote>
<list style="none"> <t>END</t>
<t>In determining the appropriate training, the IETF Chair and </section>
Ombudsteam shall take professional advice and will consult with the IETF Admini <section anchor="change5-1" numbered="true" toc="default">
strative Oversight Committee (IAOC) with respect to the overall IETF budget.</t> <name>Changes to Section 5.1</name>
</list></t> <t>The following change is made to text in <xref target="RFC7776" sect
<t>NEW ion="5.1" sectionFormat="of" format="default"/>:</t>
<list style="none"> <t>OLD
<t>In determining the appropriate training, the IETF Chair and </t>
Ombudsteam shall take professional advice and will consult with the IETF Admini <blockquote>
stration LLC with respect to the overall IETF budget.</t> <ul spacing="normal">
</list></t> <li>Many IETF management positions are appointed by the NomCom with
<t>END</t> confirmation from the IESG, IAB, or ISOC. <xref target="RFC7437" format="defaul
</section> t"/> describes the
recall procedure for such appointments. This document upd
<section anchor="changes5" title="Changes to Section 5"> ates <xref target="RFC7437" format="default"/> by allowing the Ombudsteam to for
<t>Section 5 of RFC 7776 <xref target="RFC7776" /> is about Remedie m a recall petition on
s (available to the Ombudsteam). The last paragraph of that section is replaced
as follows:</t>
<t>OLD
<list style="none">
<t>Where specific action is required to ensure that a remedy i
s realized or enforced, the Ombudsteam will make a request in writing to the IET
F Secretariat and/or IETF Administrative Director (IAD) to take action as approp
riate.</t>
</list></t>
<t>NEW
<list style="none">
<t>Where specific action is required to ensure that a remedy i
s realized or enforced, the Ombudsteam will make a request in writing to the IET
F Secretariat and/or IETF LLC Executive Director to take action as appropriate.<
/t>
</list></t>
<t>END</t>
</section>
<section anchor="changesref" title="Changes to References to RFC 7437"
>
<t>RFC 7776 updated RFC 7437 <xref target="RFC7437" /> by allowing t
he Obmudsteam to form a recall petition. This document does not change any of t
he associated 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.ie
tf-iasa2-rfc7437bis"/>, and as part
of that work, <xref target="I-D.ietf-iasa2-rfc7437bis"/> has incl
uded 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 to Metadata">
<t>The following change is made to the metadata at the head of <xr
ef target="RFC7776"/>:</t>
<t>OLD
<list style="none">
<t>Updates: 2418, 7437</t>
</list></t>
<t>NEW
<list style="none">
<t>Updates: 2418</t>
</list></t>
<t>END</t>
</section>
<section anchor="changeab" title="Changes to the Abstract">
<t>The following change is made to text in the Abstract of <xref t
arget="RFC7776"/>:</t>
<t>DELETE
<list style="none">
<t>This document updates RFC 7437 by allowing the Ombudsteam
to form a recall petition without further signatories.</t>
</list></t>
<t>END</t>
</section>
<section anchor="change5-1" title="Changes to Section 5.1">
<t>The following change is made to text in Section 5.1 of <xref ta
rget="RFC7776"/></t>
<t>OLD
<list style="symbols">
<t>Many IETF management positions are appointed by the NomCom
with confirmation from the IESG, IAB, or ISOC. <xref target="RFC7437" /> descr
ibes the
recall procedure for such appointments. This document upd
ates <xref target="RFC7437" /> by allowing the Ombudsteam to form a recall petit
ion on
its own and without requiring 20 signatories from the comm unity. Such a petition shall be treated in all ways like any other recall petit ion as its own and without requiring 20 signatories from the comm unity. Such a petition shall be treated in all ways like any other recall petit ion as
described in <xref target="RFC7437" />: that is, the fact of the petition and its signatories (the Ombudsteam) shall be announced to the I ETF described in <xref target="RFC7437" format="default"/>: th at is, the fact of the petition and its signatories (the Ombudsteam) shall be an nounced to the IETF
community, and a Recall Committee Chair shall be appointed to complete the Recall Committee process. It is expected that the Recall Commi ttee will community, and a Recall Committee Chair shall be appointed to complete the Recall Committee process. It is expected that the Recall Commi ttee will
receive a briefing from the Ombudsteam explaining why reca receive a briefing from the Ombudsteam explaining why reca
ll is considered an appropriate remedy.</t> ll is considered an appropriate remedy.</li></ul></blockquote>
</list></t> <t>NEW
<t>NEW </t>
<list style="symbols"> <blockquote>
<t>The Ombudsteam may form a recall petition on its own witho <ul spacing="normal">
ut requiring signatures from the community as described in <xref target="I-D.iet <li>The Ombudsteam may form a recall petition on its own without req
f-iasa2-rfc7437bis"/>.</t> uiring signatures from the community as described in <xref target="RFC8713" form
</list></t> at="default"/>.</li></ul></blockquote>
<t>END</t> <t>END</t>
</section>
</section>
</section>
<section title="IANA Considerations">
<t>This document makes no request for IANA action.</t>
</section>
<section title="Security Considerations">
<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>
<references title="Informative References">
&RFC7437;
</references>
<section title="Acknowledgements">
<t>Thanks to Jason Livingwood for suggesting the need for this docum
ent.</t>
<t>Subramanian Moonesamy, Sean Turner, Jon Peterson, Roman Danyliw,
and Barry Leiba raised useful points during their reviews of this work.</t>
</section> </section>
</section>
</section>
<section numbered="true" toc="default">
<name>IANA Considerations</name>
<t>This document has no IANA actions.</t>
</section>
<section numbered="true" toc="default">
<name>Security Considerations</name>
<t>This document has no implications for Internet security.</t>
</section>
</middle>
<back>
<references>
<name>References</name>
<references>
<name>Normative References</name>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.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/refer
ence.RFC.7437.xml"/>
</references>
</references>
<section numbered="false" toc="default">
<name>Acknowledgements</name>
<t>Thanks to <contact fullname="Jason Livingood"/> for suggesting the need
for this document.</t>
</back> <t><contact fullname="Subramanian Moonesamy"/>, <contact fullname="Sean
Turner"/>, <contact fullname="Jon Peterson"/>, <contact fullname="Roman
Danyliw"/>, and <contact fullname="Barry Leiba"/> raised useful points
during their reviews of this work.</t>
</section>
</back>
</rfc> </rfc>
 End of changes. 11 change blocks. 
229 lines changed or deleted 239 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/