rfc8712xml2.original.xml   rfc8712.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2026 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.2026.xml">
<!ENTITY RFC2028 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.2028.xml">
<!ENTITY RFC2031 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.2031.xml">
<!ENTITY RFC2850 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.2850.xml">
<!ENTITY RFC3677 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.3677.xml">
<!ENTITY RFC4033 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.4033.xml">
<!ENTITY RFC4071 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.4071.xml">
<!ENTITY RFC4371 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.4371.xml">
<!ENTITY RFC5378 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.5378.xml">
<!ENTITY RFC6756 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.6756.xml">
<!ENTITY RFC7437 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.7437.xml">
<!ENTITY RFC8200 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.8200.xml">
<!ENTITY I-D.ietf-iasa2-rfc4071bis SYSTEM "http://xml.resource.org/public/rfc/bi
bxml3/reference.I-D.ietf-iasa2-rfc4071bis.xml">
<!ENTITY I-D.ietf-iasa2-trust-rationale SYSTEM "http://xml.resource.org/public/r
fc/bibxml3/reference.I-D.ietf-iasa2-trust-rationale.xml">
<!ENTITY I-D.ietf-iasa2-trust-update SYSTEM "http://xml.resource.org/public/rfc/
bibxml3/reference.I-D.ietf-iasa2-trust-update.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<rfc category="info" docName="draft-ietf-iasa2-rfc2031bis-08" ipr="trust200902"
obsoletes="2031">
<front> <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<title abbrev="The IETF-ISOC Relationship"> <rfc
xmlns:xi="http://www.w3.org/2001/XInclude"
number="8712"
updates=""
obsoletes="2031"
category="info"
submissionType="IETF"
consensus="true"
ipr="trust200902"
sortRefs="true"
symRefs="true"
xml:lang="en"
docName="draft-ietf-iasa2-rfc2031bis-08"
tocInclude="true"
version="3">
<!-- xml2rfc v2v3 conversion 2.34.0 -->
<front>
<title abbrev="The IETF-ISOC Relationship">
The IETF-ISOC Relationship The IETF-ISOC Relationship
</title> </title>
<seriesInfo name="RFC" value="8712"/>
<author fullname="Gonzalo Camarillo" initials="G." surname="Camarillo"> <author fullname="Gonzalo Camarillo" initials="G." surname="Camarillo">
<organization>Ericsson</organization> <organization>Ericsson</organization>
<address> <address>
<email>Gonzalo.Camarillo@ericsson.com</email> <email>Gonzalo.Camarillo@ericsson.com</email>
</address> </address>
</author> </author>
<author fullname="Jason Livingood" initials="J." surname="Livingood">
<author fullname="Jason Livingood" initials="J." surname="Livingood"> <organization>Comcast</organization>
<organization>Comcast</organization> <address>
<address> <email>jason_livingood@comcast.com</email>
<email>jason_livingood@comcast.com</email> </address>
</address> </author>
</author> <date month="February" year="2020"/>
<area>General</area>
<date month="August" year="2019" /> <workgroup>IETF Administrative Support Activity 2</workgroup>
<keyword>IASA</keyword>
<area>General</area> <abstract>
<t>
<workgroup>IETF Administrative Support Activity 2</workgroup> This document summarizes the Internet Engineering Task Force (IETF) -
<abstract>
<t>
This document summarises the Internet Engineering Task Force (IETF) -
Internet Society (ISOC) relationship, following a major revision to Internet Society (ISOC) relationship, following a major revision to
the structure of the IETF Administrative Support Activity (IASA) in the structure of the IETF Administrative Support Activity (IASA) in
2018. The IASA was revised under a new "IASA 2.0" structure by the 2018. The IASA was revised under a new "IASA 2.0" structure by the
IASA2 Working Group, which changed the IETF's administrative, legal, IASA2 Working Group, which changed the IETF's administrative, legal,
and financial structure. As a result, it also changed the relationship and financial structure. As a result, it also changed the relationship
between the IETF and ISOC, which made it necessary to revise RFC 2031. between the IETF and ISOC, which made it necessary to revise RFC 2031.
</t> </t>
</abstract>
</abstract> </front>
<middle>
</front> <section numbered="true" toc="default">
<name>Introduction and History</name>
<middle> <t>
<section title="Introduction and History">
<t>
The Internet Society provides a corporate home for the administrative The Internet Society provides a corporate home for the administrative
entity that supports the Internet Engineering Task Force (IETF), the entity that supports the Internet Engineering Task Force (IETF), the
Internet Architecture Board (IAB), and the Internet Research Task Internet Architecture Board (IAB), and the Internet Research Task
Force (IRTF), and supports the work of these groups through a variety Force (IRTF), and supports the work of these groups through a variety
of programs. of programs.
</t> </t>
<t>
<t>
The Internet Engineering Task Force (IETF) is the body that is The Internet Engineering Task Force (IETF) is the body that is
responsible for the development and maintenance of the Internet responsible for the development and maintenance of the Internet
Standards. The IETF is primarily a volunteer organization. Its driving Standards. The IETF is primarily a volunteer organization. Its driving
force is a group of dedicated high-quality engineers from all over the force is a group of dedicated, high-quality engineers from all over the
world. In a structure of working groups, these engineers exchange world. In a structure of working groups, these engineers exchange
ideas and experience, and through discussion and collaboration (both ideas and experience, and through discussion and collaboration (both
electronically and face-to-face) they strive to achieve rough electronically and face-to-face), they strive to achieve rough
consensus and implement the standards through running code. consensus and implement the standards through running code.
</t> </t>
<t>
<t> The growth of the Internet over several decades has also led to the
The growth of the Internet over several decades also led to the
growth of the IETF. More and more people, organizations, and companies growth of the IETF. More and more people, organizations, and companies
rely on Internet Standards. Non-technical issues, such as legal, rely on Internet Standards. Nontechnical issues, such as legal,
administrative, and financial issues had long been an undesirable but administrative, and financial issues had long been an undesirable but
unavoidable part of the IETF. To address these issues in 1995 the IETF unavoidable part of the IETF. To address these issues, the IETF
established the Poised95 Working Group. Its goal was to structure and established the Poised95 Working Group in 1995. Its goal was to structure and
document the IETF processes in order to maximize the flexibility and document the IETF processes in order to maximize the flexibility and
freedom of IETF engineers so that they could work in the way the IETF freedom of IETF engineers so that they could work in the way the IETF
had always been most successful and to honour the IETF credo: "Rough had always been most successful and to honor the IETF credo: "Rough
consensus and running code". consensus and running code".
</t> </t>
<t>
<t>
The Poised95 Working Group concluded that the Internet Society (ISOC), The Poised95 Working Group concluded that the Internet Society (ISOC),
which was formed in 1992, was the best organization to handle all of which was formed in 1992, was the best organization to handle all of
these legal, administrative, and financial tasks on behalf of and in these legal, administrative, and financial tasks on behalf of, and in
close cooperation with the IETF. This led to documenting things such close cooperation with, the IETF. This led to documenting things such
as the IETF standards process <xref target="RFC2026"/>, the IETF as the IETF standards process <xref target="RFC2026" format="default"/>, the IET
organizational structure <xref target="RFC2028"/>, the IETF Nominating F
Committee (NomCom) procedures <eref target="BCP10"/>, and the IETF-ISOC organizational structure <xref target="RFC2028" format="default"/>, the IETF Nom
relationship <xref target="RFC2031"/>. inating
</t> Committee (NomCom) procedures <xref target="RFC2027"/>, and the IETF-ISOC
relationship <xref target="RFC2031" format="default"/>.
<t> </t>
<t>
As time passed and operational experience accumulated, additional As time passed and operational experience accumulated, additional
structure was necessary. As a result, the Internet Administrative structure was necessary. As a result, the Internet Administrative
Support Activity (IASA) was defined in 2005 and documented in <xref Support Activity (IASA) was defined in 2005 and documented in <xref target="RFC4
target="RFC4071"/> and <xref target="RFC4371"/>. 071" format="default"/> and <xref target="RFC4371" format="default"/>.
</t> </t>
<t>
<t>
In 2018, the IASA was revised under a new "IASA 2.0" structure by the In 2018, the IASA was revised under a new "IASA 2.0" structure by the
IASA2 Working Group, which made significant revisions to the IETF's IASA2 Working Group, which made significant revisions to the IETF's
administrative, legal, and financial structure. One critical outcome administrative, legal, and financial structure. One critical outcome
was the formation, in close cooperation between the IETF and was the formation, in close cooperation between the IETF and
ISOC, of the IETF Administration Limited Liability Company (IETF LLC) ISOC, of the IETF Administration Limited Liability Company (IETF LLC)
as a subsidiary of ISOC. as a subsidiary of ISOC.
</t> </t>
<t>
<t> As a result of the IASA 2.0 structure <xref target="RFC8711" format="default"/>
As a result of the IASA 2.0 structure <xref and formation of the IETF LLC, the
target="I-D.ietf-iasa2-rfc4071bis"/> and formation of the IETF LLC, the
relationship between the IETF and ISOC has changed. This document relationship between the IETF and ISOC has changed. This document
summarises the current state of the IETF-ISOC relationship at a high summarizes the current state of the IETF-ISOC relationship at a high
level and replaces <xref target="RFC2031"/>. level and replaces <xref target="RFC2031" format="default"/>.
</t> </t>
</section>
</section> <section numbered="true" toc="default">
<name>Philosophical Relationship with ISOC</name>
<section title="Philosophical Relationship with ISOC"> <t>
<t>
ISOC and the IETF have historically been philosophically ISOC and the IETF have historically been philosophically
aligned. ISOC's connection with the IETF community has always played aligned. ISOC's connection with the IETF community has always played
an important role in its policy work, which has not changed. ISOC has always bee n and an important role in its policy work, which has not changed. ISOC has always bee n and
continues to be an advocate continues to be an advocate
for multistakeholder processes, which includes the technical for multistakeholder processes, which includes the technical
community. Open standards are an explicit part of one of the focus community. Open standards are an explicit part of one of the focus
areas in ISOC's mission: Advancing the development and application of areas in ISOC's mission: advancing the development and application of
Internet infrastructure, technologies, and open standards <eref target="ISOC-Mis Internet infrastructure, technologies, and open standards <xref target="ISOC-Mis
sion"/>. sion"/>.
</t> </t>
</section>
</section> <section numbered="true" toc="default">
<name>Main Division of Responsibilities between IETF and ISOC</name>
<section title="Main Division of Responsibilities between IETF and ISOC"> <t>
<t>
The IETF remains responsible for the development and quality of the The IETF remains responsible for the development and quality of the
Internet Standards. Apart from the roles described below, the IETF and Internet Standards. Apart from the roles described below, the IETF and
ISOC acknowledge that ISOC as an organization has no direct influence whatsoever on the ISOC acknowledge that ISOC as an organization has no direct influence whatsoever on the
technical content of Internet Standards (though ISOC employees may independently continue to technical content of Internet Standards (though ISOC employees may independently continue to
make technical contributions as individuals). make technical contributions as individuals).
</t> </t>
</section> </section>
<section anchor="standards" numbered="true" toc="default">
<section anchor="standards" title="ISOC's Role in the IETF Standards Process"> <name>ISOC's Role in the IETF Standards Process</name>
<t>
<t>
ISOC plays a small role in the IETF standards process. In particular, ISOC plays a small role in the IETF standards process. In particular,
ISOC assists the standards process by appointing the IETF NomCom chair ISOC assists the standards process by appointing the IETF NomCom chair
and by confirming IAB candidates who are put forward by the IETF and by confirming IAB candidates who are put forward by the IETF
NomCom, as described in <xref target="RFC7437"/>, and by acting as the NomCom, as described in <xref target="RFC8713" format="default"/>, and by acting
last resort in the appeals process, as described in <xref as the
target="RFC2026"/>. last resort in the appeals process, as described in <xref target="RFC2026" forma
</t> t="default"/>.
</t>
<t> <t>
ISOC maintains liaison relationships and memberships in other ISOC maintains liaison relationships and memberships in other
Standards Development Organizations (SDOs) and related organizations, Standards Development Organizations (SDOs) and related organizations,
which directly benefits the IETF. For example, ISOC is a Sector Member which directly benefits the IETF. For example, ISOC is a Sector Member
of the ITU-T. As a result, ISOC delegates are afforded the same rights of the ITU-T. As a result, ISOC delegates are afforded the same rights
as other ITU-T Sector Members <xref target="RFC6756"/>. as other ITU-T Sector Members <xref target="RFC6756" format="default"/>.
</t> </t>
<t>
<t> ISOC also supports the IETF standards process indirectly (e.g.,
ISOC also supports the IETF standards process more indirectly (e.g.,
by promoting it in relevant communities) through several by promoting it in relevant communities) through several
programs. For example, ISOC's Policymakers Program to the IETF programs. For example, ISOC's Policymakers Programme to the IETF
(usually referred to simply as ISOC's policy fellows program) gives (usually referred to simply as ISOC's IETF Policy Program) gives
policy experts an opportunity to interact directly with the IETF policy experts an opportunity to interact directly with the IETF
technical community. ISOC also performs technical work using the technical community. ISOC also performs technical work using the
standards developed in the IETF as its basis. An example of that is standards developed in the IETF as its basis. An example of that is
ISOC's Deploy360 program, which helps encourage and support the ISOC's work in encouraging and supporting the deployment
deployment of IETF standards like DNSSEC <xref of IETF standards.
target="RFC4033"/> and IPv6 <xref </t>
target="RFC8200"/>. <t>
</t>
<t>
Otherwise, the involvement of ISOC's employees in the IETF standards Otherwise, the involvement of ISOC's employees in the IETF standards
process (e.g., as document editors or in leadership positions) is as process (e.g., as document editors or in leadership positions) is as
individual contributors rather than on institutional grounds. individual contributors rather than on institutional grounds.
</t> </t>
</section>
</section> <section numbered="true" toc="default">
<name>The IETF's Role in ISOC</name>
<section title="The IETF's Role in ISOC"> <t>
The IETF plays a role in the governance of ISOC. Per ISOC's bylaws,
<t>
The IETF plays a role in the governance of ISOC. Per ISOC's by-laws,
the IETF appoints a set of trustees to the ISOC Board. The process by the IETF appoints a set of trustees to the ISOC Board. The process by
which the IETF makes those appointments is defined in <xref which the IETF makes those appointments is defined in <xref target="RFC3677" for
target="RFC3677"/>. mat="default"/>.
</t> </t>
<t>
<t> The charter of the IAB (Internet Architecture Board) <xref target="RFC2850" form
The charter of the IAB (Internet Architecture Board) <xref at="default"/> states that "the IAB acts as a source of advice and
target="RFC2850"/> states that "the IAB acts as a source of advice and
guidance to the Board of Trustees and Officers of the Internet Society guidance to the Board of Trustees and Officers of the Internet Society
concerning technical, architectural, procedural, and (where concerning technical, architectural, procedural, and (where
appropriate) policy matters pertaining to the Internet and its appropriate) policy matters pertaining to the Internet and its
enabling technologies". This connection between the IAB and ISOC enabling technologies". This connection between the IAB and ISOC
ensures that ISOC's proposals in the policy area are based on a sound ensures that ISOC's proposals in the policy area are based on a sound
understanding of the relevant technologies and architectures. ISOC's understanding of the relevant technologies and architectures. ISOC's
strong connection to the Internet technical community has always been strong connection to the Internet technical community has always been
one of its main strengths. one of its main strengths.
</t> </t>
</section>
</section> <section numbered="true" toc="default">
<name>Legal Relationship with ISOC</name>
<section title="Legal Relationship with ISOC"> <t>
The IETF LLC is a disregarded Limited Liability Company (LLC) of the Internet So
<t> ciety that was
The IETF LLC is a disregarded Limited Liability Company (LLC) of the Internet So
ciety -
established to provide a corporate legal framework for facilitating current and established to provide a corporate legal framework for facilitating current and
future activities related to the IETF, IAB, and IRTF. It was established by the future activities related to the IETF, IAB, and IRTF. It was established by the
ISOC/IETF LLC Agreement <xref target="OpAgreement"/> on August 27, 2018, and ISOC / IETF LLC Agreement <xref target="OpAgreement" format="default"/> on Augus t 27, 2018, and
governs the relationship between the IETF LLC and ISOC. governs the relationship between the IETF LLC and ISOC.
</t> </t>
<t>
<t> The IETF Trust, documented in <xref target="RFC5378" format="default"/>, and upd
The IETF Trust, documented in <xref target="RFC5378"/>, and updated in ated in
<xref target="I-D.ietf-iasa2-trust-rationale"/> and <xref <xref target="RFC8714" format="default"/> and <xref target="RFC8715" format="def
target="I-D.ietf-iasa2-trust-update"/>, provides legal protection for ault"/>, provides legal protection for
the RFC series of documents and other aspects of the IETF. This the RFC Series of documents and other aspects of the IETF. This
includes things such as protection for trademarks, copyrights, and includes things such as protection for trademarks, copyrights, and
intellectual property rights. As part of the IETF Trust arrangement, intellectual property rights. As part of the IETF Trust arrangement,
IETF standards documents can be freely downloaded, copied, and IETF standards documents can be freely downloaded, copied, and
distributed without financial or other distribution restrictions, distributed without financial or other distribution restrictions,
though all rights to change these documents lie with the IETF. The though all rights to change these documents lie with the IETF. The
IETF Trust also provides legal protection in case of disputes over IETF Trust also provides legal protection in case of disputes over
intellectual property rights and other rights. The creation of the intellectual property rights and other rights. The creation of the
IETF LLC has changed the way that the IETF Trust's trustees are IETF LLC has changed the way that the IETF Trust's trustees are
selected but did not change the purpose or operation of the Trust. One selected but did not change the purpose or operation of the Trust. One
of the IETF Trust's trustees is appointed by the ISOC's Board of of the IETF Trust's trustees is appointed by the ISOC's Board of
Trustees. Trustees.
</t> </t>
</section>
</section> <section numbered="true" toc="default">
<name>Financial and Administrative Relationship with ISOC</name>
<section title="Financial and Administrative Relationship with ISOC"> <t>
Under the terms of the Operating Agreement <xref target="OpAgreement" format="de
<t> fault"/> between ISOC and the IETF, ISOC has agreed to
Under the terms of the Operating Agreement <xref
target="OpAgreement"/> between ISOC and the IETF, ISOC has agreed to
provide significant funding support for the IETF. In addition, provide significant funding support for the IETF. In addition,
the IETF LLC is responsible for creating and the IETF LLC is responsible for creating and
managing an annual operating budget for the IETF; for negotiating, managing an annual operating budget for the IETF; for negotiating,
signing, and overseeing contracts; for fundraising; for maintaining signing, and overseeing contracts; for fundraising; for maintaining
bank accounts; and for liability insurance. The IETF LLC is managed by bank accounts; and for liability insurance. The IETF LLC is managed by
a Board of Directors, one of whom is appointed by the ISOC's Board of a Board of Directors, one of whom is appointed by the ISOC's Board of
Trustees. The intention is that ISOC and the IETF LLC operate at arm's Trustees. The intention is that ISOC and the IETF LLC operate at arm's
length. length.
</t> </t>
<t>
<t>
The IETF LLC establishes contracts with third parties to provide The IETF LLC establishes contracts with third parties to provide
different types of services to the IETF. Note that it is possible that different types of services to the IETF. Note that it is possible that
some of those services may be provided by ISOC or involve ISOC staff. some of those services may be provided by ISOC or involve ISOC staff.
</t> </t>
<t>
<t>
Under the new IASA 2.0 structure, the IETF LLC is solely responsible for Under the new IASA 2.0 structure, the IETF LLC is solely responsible for
its administration, including the IETF Trust, IAB, IESG, IETF its administration, including the IETF Trust, IAB, IESG, IETF
working groups, and other IETF processes. A further exploration of working groups, and other IETF processes. A further exploration of
this can be found in Section 4 of <xref this can be found in <xref target="RFC8711" sectionFormat="of" section="4" forma
target="I-D.ietf-iasa2-rfc4071bis"/>. t="default"/>.
</t> </t>
</section>
</section> <section numbered="true" toc="default">
<name>IANA Considerations</name>
<section title="IANA Considerations"> <t>This document has no IANA actions.</t>
</section>
<t>This document introduces no new IANA considerations.</t> <section numbered="true" toc="default">
<name>Security Considerations</name>
</section> <t>This document introduces no new security considerations.</t>
</section>
<section title="Security Considerations"> <section numbered="true" toc="default">
<name>Privacy Considerations</name>
<t>This document introduces no new privacy considerations.</t>
</section>
<t>This document introduces no new security considerations.</t> </middle>
<back>
<references>
<name>References</name>
<references>
<name>Normative References</name>
<!-- draft-ietf-iasa2-rfc4071bis-11 [RFC8711] in cluster -->
<reference anchor="RFC8711" target="https://www.rfc-editor.org/info/rfc8
711">
<front>
<title>Structure of the IETF Administrative Support Activity, Versio
n 2.0</title>
<author initials="B." surname="Haberman">
<organization/>
</author>
<author initials="J." surname="Hall">
<organization/>
</author>
<author initials="J." surname="Livingood">
<organization/>
</author>
<date month="February" year="2020"/>
</front>
<seriesInfo name='BCP' value='101'/>
<seriesInfo name="RFC" value="8711"/>
<seriesInfo name="DOI" value="10.17487/RFC8711"/>
</reference>
</references>
<references>
<name>Informative References</name>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.2026.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.2027.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.2028.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.2031.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.2850.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.3677.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.4071.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.4371.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.5378.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.6756.xml"/>
<!-- draft-ietf-iasa2-rfc7437bis-09 - in cluster: RFC8713 -->
<reference anchor="RFC8713" target="https://rfc-editor.org/info/rfc8713"
>
<front>
<title>IAB, IESG, IETF Trust, and IETF LLC Selection,
Confirmation, and Recall Process: Operation of the IETF Nominating
and Recall Committees</title>
</section> <author initials="M." surname="Kucherawy" role="editor">
<organization/>
</author>
<section title="Privacy Considerations"> <author initials="R." surname="Hinden" role="editor">
<organization/>
</author>
<t>This document introduces no new privacy considerations.</t> <author initials="J." surname="Livingood" role="editor">
<organization/>
</author>
</section> <date month="February" year="2020"/>
</front>
<seriesInfo name="BCP" value="10"/>
<seriesInfo name="RFC" value="8713"/>
<seriesInfo name="DOI" value="10.17487/RFC8713"/>
<section anchor="ack" title="Acknowledgements"> </reference>
<t> <!-- draft-ietf-iasa2-trust-update-03 - in cluster: RFC8714 -->
The authors would like to thank Erik Huizer for his contribution as <reference anchor='RFC8714' target="https://www.rfc-editor.org/info/rfc87
the author of <xref target="RFC2031"/>, which this document 14">
replaces. <front>
</t> <title>Update to the Process for Selection of Trustees for the IETF T
rust</title>
</section> <author initials='J' surname='Arkko' fullname='Jari Arkko'>
<organization />
</author>
<section anchor="changes" title="Changes from Previous Versions"> <author initials='T' surname='Hardie' fullname='Ted Hardie'>
<t>RFC Editor: Please remove this section upon publication.</t> <organization />
<t>-00: Initial version published</t> </author>
<t>-01: Several key updates to prepare WGLC based on WG feedback</t>
<t>-02: Fixed nits identified by Brian Carpenter on 12-21-2018, and text
on the tax status from John Levine.</t>
<t>-03: As we entered IESG review, added a short description of what ISOC
does (in relation to the IETF)
that can be used in external material by both the IETF and ISOC.<
/t>
<t>-04: Clarification adding text to Section 6 on legal issue.</t>
<t>-05: Fix nits</t>
<t>-06: Fix nits and other changes from IESG review</t>
<t>-07: Fixed one missed nit from IESG review</t>
<t>-08: Fixed two typographical errors</t>
</section>
</middle> <date month="February" year="2020"/>
<back> </front>
<seriesInfo name='BCP' value='101'/>
<seriesInfo name="RFC" value="8714"/>
<seriesInfo name="DOI" value="10.17487/RFC8714"/>
<references title="Normative References"> </reference>
&I-D.ietf-iasa2-rfc4071bis;
</references>
<references title="Informative References"> <!-- draft-ietf-iasa2-trust-rationale-03 - in cluster: RFC8715 -->
<reference anchor='RFC8715' target="https://www.rfc-editor.org/info/rfc87
15">
<front>
<title>IETF Administrative Support Activity 2.0: Update to the
Process for Selection of Trustees for the IETF Trust</title>
&RFC2026; <author initials='J' surname='Arkko' fullname='Jari Arkko'>
&RFC2028; <organization />
&RFC2031; </author>
&RFC2850;
&RFC3677;
&RFC4033;
&RFC4071;
&RFC4371;
&RFC5378;
&RFC6756;
&RFC7437;
&RFC8200;
&I-D.ietf-iasa2-trust-rationale; <date month="February" year="2020"/>
&I-D.ietf-iasa2-trust-update;
<reference anchor="BCP10" target="https://www.rfc-editor.org/refs/ref-bcp </front>
10.txt"> <seriesInfo name="RFC" value="8715"/>
<front> <seriesInfo name="DOI" value="10.17487/RFC8715"/>
<title>BCP10</title>
<author/>
<date/>
</front>
</reference> </reference>
<reference anchor="ISOC-Mission" target="https://www.internetsociety.org/ <!-- URL https://www.internetsociety.org/mission/ works -->
mission/"> <reference anchor="ISOC-Mission" target="https://www.internetsociety.org
<front> /mission/">
<title>ISOC Mission</title> <front>
<author/> <title>Internet Society Mission</title>
<date/> <author>
</front> <organization>Internet Society</organization>
</reference> </author>
</front>
</reference>
<reference anchor='OpAgreement' target="https://www.ietf.org/documents/180/I <reference anchor="OpAgreement" target="https://www.ietf.org/documents/1
ETF-LLC-Agreement.pdf"> 80/IETF-LLC-Agreement.pdf">
<front> <front>
<title abbrev='Operating Agreement'>Limited Liability Company <title abbrev="Operating Agreement">Limited Liability Company
Agreement of IETF Administration LLC</title> Agreement of IETF Administration LLC</title>
<author /> <author>
<date month='August' year='2018' /> <organization/>
</front> </author>
</reference> <date month="August" year="2018"/>
</front>
</references> </reference>
</references>
</back> </references>
<section anchor="ack" numbered="false" toc="default">
<name>Acknowledgements</name>
<t>
The authors would like to thank <contact fullname="Erik Huizer"/> for his contri
bution as
the author of <xref target="RFC2031" format="default"/>, which this document
replaces.
</t>
</section>
</back>
</rfc> </rfc>
 End of changes. 52 change blocks. 
298 lines changed or deleted 301 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/