rfc8714xml2.original.xml   rfc8714.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<!ENTITY RFC7437 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.7437.xml">
<!ENTITY RFC4071 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.4071.xml">
<!ENTITY RFC4371 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.4371.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="bcp" docName="draft-ietf-iasa2-trust-update-02" ipr="trust200902"
updates="4071,4371">
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="bcp" number="8714"
submissionType="IETF" consensus="yes" ipr="trust200902" obsoletes="4371"
updates="" xml:lang="en" tocInclude="true" tocDepth="4" symRefs="true"
sortRefs="true" version="3" docName="draft-ietf-iasa2-trust-update-03">
<!-- xml2rfc v2v3 conversion 2.37.3 -->
<front> <front>
<title abbrev="Trustees for the IETF Trust">Update to the Process for Select ion of Trustees for the IETF Trust</title> <title abbrev="Trustees for the IETF Trust">Update to the Process for Select ion of Trustees for the IETF Trust</title>
<seriesInfo name="RFC" value="8714"/>
<author fullname="Jari Arkko" initials="J." <seriesInfo name="BCP" value="101"/>
surname="Arkko"> <author fullname="Jari Arkko" initials="J." surname="Arkko">
<organization>Ericsson</organization> <organization>Ericsson</organization>
<address> <address>
<postal> <postal>
<street></street> <street/>
<city>Kauniainen</city> <city>Kauniainen</city>
<region/>
<region></region>
<code>02700</code> <code>02700</code>
<country>Finland</country> <country>Finland</country>
</postal> </postal>
<email>jari.arkko@piuha.net</email> <email>jari.arkko@piuha.net</email>
</address> </address>
</author> </author>
<author fullname="Ted Hardie" initials="T." surname="Hardie">
<author fullname="Ted Hardie" initials="T."
surname="Hardie">
<address> <address>
<email>ted.ietf@gmail.com</email> <email>ted.ietf@gmail.com</email>
</address> </address>
</author> </author>
<date month="February" year="2020"/>
<date month="October" year="2018" />
<area>General</area> <area>General</area>
<workgroup>IASA2</workgroup>
<workgroup>Internet Engineering Task Force</workgroup> <keyword>IETF administration</keyword>
<keyword>intellectual property</keyword>
<keyword>leadership selection</keyword>
<keyword>IASA</keyword>
<abstract> <abstract>
<t>This memo updates the process for selection of Trustees for the IETF
<t>This memo updates the process for selection of trustees for the IETF Trust. Previously, the IETF Administrative Oversight Committee (IAOC)
Trust. Previously, the Internet Administrative Oversight members also acted as Trustees, but the IAOC
Committee (IAOC) members also acted as trustees, but the IAOC has been eliminated as part of an update to the structure of
has been eliminated as part of an update of the structure of the IETF Administrative Support Activity (IASA). This memo
the Internet Administrative Support Activity (IASA). This memo specifies that the Trustees shall be selected separately.</t>
specifies that the trustees shall be selected separately.</t> <t>This memo obsoletes RFC 4371. The changes relate only
to the selection of Trustees. All other aspects of the IETF Trust
<t>This memo updates RFCs 4071 and 4371 with regards to the remain as they are today.
selection of trustees. All other aspects of the IETF Trust </t>
remain as they are today.</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section numbered="true" toc="default">
<section title="Introduction"> <name>Introduction</name>
<t>This memo updates the process for selection of Trustees for the IETF
<t>This memo updates the process for selection of trustees for the IETF Trust. Previously, the IETF Administrative Oversight Committee (IAOC)
Trust. Previously, the Internet Administrative Oversight members also acted as Trustees, but the IAOC has been eliminated as part
Committee (IAOC) members also acted as trustees, but the IAOC of an update to the structure of the IETF Administrative Support
has been eliminated as part of an update of the structure of Activity (IASA). This memo specifies that the Trustees shall be selected
the Internet Administrative Support Activity (IASA). This memo separately. See <xref target="selection" format="default"/>.</t>
specifies that the trustees shall be selected separately.</t> <t>This memo obsoletes <xref target="RFC4371"/>. The changes relate only
to the
<t>This memo updates RFCs 4071 and 4371 with regards to the selection of Trustees. All other aspects of the IETF Trust remain as
selection of trustees. All other aspects of the IETF Trust they are today. <xref target="ietf-trust" format="default"/> copies the
remain as they are today.</t> definition as it was in <xref target="RFC4371"/>,
only leaving out the part about Trustee selection and adding a reference
to the IETF Trust website.
</t>
<t>For a discussion of why this change is needed and a rationale <t>For a discussion of why this change is needed and a rationale
for these specific changes, see <xref for these specific changes, see <xref target="RFC8715" format="default"/>.
target="I-D.ietf-iasa2-trust-rationale"/>.</t> </t>
</section> </section>
<section anchor="ietf-trust" numbered="true" toc="default">
<section anchor="selection" title="Selection of Trustees"> <name>IETF Trust</name>
<t>A Trust ("the IETF Trust") has been formed for the purpose of
acquiring, holding, maintaining, and licensing certain existing and
future intellectual property and other property used in connection
with the administration of the IETF. The Trust was formed by the
signatures of its Settlors and initial Trustees. The Settlors, who
contributed initial intellectual property to the Trust, were ISOC and
the Corporation for National Research Initiatives. The Beneficiary
of the IETF Trust is the IETF as a whole.</t>
<t>Further details of the IETF Trust may be found at the IETF Trust's
website, &lt;<eref target="https://trustee.ietf.org/"/>&gt;.</t>
</section>
<section anchor="selection" numbered="true" toc="default">
<name>Selection of Trustees</name>
<t>This document revises the original Trustee selection procedures <t>This document revises the original Trustee selection procedures
defined in <xref target="RFC4071"/> and <xref target="RFC4371"/>, defined in <xref target="RFC4071" format="default"/> and <xref target="RFC
to eliminate the requirement that trustees be drawn from the 4371" format="default"/>
to eliminate the requirement that Trustees be drawn from the
members of the IAOC.</t> members of the IAOC.</t>
<t>In this newly revised IETF Trust structure, there will be <t>In this newly revised IETF Trust structure, there will be
five Trustees. Three shall be appointed by the IETF Nominating five Trustees. Three shall be appointed by the IETF Nominating
Committee (NomCom) and confirmed by the Internet Engineering Committee (NomCom) and confirmed by the Internet Engineering
Steering Group (IESG), one shall be appointed by the IESG, and Steering Group (IESG), one shall be appointed by the IESG, and
one shall be appointed by the Internet Society (ISOC) Board of one shall be appointed by the Internet Society (ISOC) Board of
Trustees. The appointments by the IESG and ISOC Board of Trustees. The appointments by the IESG and the ISOC Board of
Trustees do not require confirmation.</t> Trustees do not require confirmation.</t>
<t>The IETF Trust Chair informs the nominating committee <t>The IETF Trust Chair informs the nominating committee
of the Trustee positions to be reviewed. The IETF Trust will of the Trustee positions to be reviewed. The IETF Trust will
provide a summary of the expertise desired of the Trustee provide a summary of the expertise desired of the Trustee
candidates to each appointing body.</t> candidates to each appointing body.</t>
<t>A change to the Trust Agreement is required to put this <t>A change to the Trust Agreement is required to put this
change into effect, and this document requests that the current change into effect, and this document requests that the current
Trustees make this change at the earliest convenient time and no Trustees make this change at the earliest convenient time and no
later than the end of the 104th IETF meeting in March 2019.</t> later than the end of the 104th IETF meeting in March 2019.</t>
<t>The terms of the appointed Trustees from the IETF NomCom shall be
<t>The terms of the appointed trustees from IETF NomCom shall be
three years. The initial selection shall be one, two, and three three years. The initial selection shall be one, two, and three
year terms in order to initially stagger the terms. The other year terms in order to initially stagger the terms. The other
appointments by the IESG and the ISOC Board of Trustees shall be appointments by the IESG and the ISOC Board of Trustees shall be
two year terms, with the initial terms being one and two years, two year terms, with the initial terms being one and two years,
respectively. respectively.
The goal of the staggered initial terms is to minimize potential The goal of the staggered initial terms is to minimize potential
Trustee turnover in any single year. To maintain the Trustee turnover in any single year. To maintain the
staggered terms, each appointing body may at its discretion staggered terms, each appointing body may, at its discretion,
appoint Trustees for shorter terms as needed in exceptional appoint Trustees for shorter terms as needed in exceptional
situations, e.g., for mid-term vacancies or when an appointment situations, e.g., for mid-term vacancies or when an appointment
is not ready by the time of the first IETF of the year.</t> is not ready by the time of the first IETF meeting of the year.</t>
<t>Once the initial Trustee selections according to the
<t>Once the initial trustee selections according to the
procedures in this document are complete, and at each subsequent procedures in this document are complete, and at each subsequent
annual meeting of the IETF Trust once new trustees are seated, annual meeting of the IETF Trust (once new Trustees are seated),
the trustees shall elect by a majority vote of the IETF Trust the Trustees shall elect one Trustee to serve as IETF Trust Chair by a
one trustee to serve as IETF Trust Chair.</t> majority vote of the IETF Trust.</t>
<t>Trustees appointed by the IETF NomCom may be recalled according to
<t>The processes regarding NomCom appointments and recalls of the recall process described in <xref target="BCP10" format="default"/>.
Trustees for the IETF Trust follow those described in <xref Trustees appointed by the IESG or by the ISOC Board of Directors may be
target="RFC7437"/>. For the appointments by the IESG, the recalled by the appointing body. For appointments made by the IESG, the
IESG is expected to run an open selection process and to consider IESG is expected to run an open selection process and to consider the
the necessary skill set and conflicts of interest as part of necessary skill set and conflicts of interest as part of that process.</t
that process.</t> >
</section> </section>
<section numbered="true" toc="default">
<section title="Security Considerations"> <name>Security Considerations</name>
<t>This memo has no security implications for the Internet.</t> <t>This memo has no security implications for the Internet.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="IANA Considerations"> <name>IANA Considerations</name>
<t>This document has no IANA actions.</t>
<t>This memo requests no action from IANA.</t>
</section>
<section anchor="ack" title="Acknowledgements">
<t>The authors would like to thank members of the earlier IASA
2.0 design team who were Brian Haberman, Eric Rescorla, Jari
Arkko, Jason Livingood, Joe Hall, and Leslie Daigle. The authors
would also like to thank Alissa Cooper, Andrew Sullivan, Brian
Carpenter, Lucy Lynch, and John Levine for interesting
discussions in this problem space. The authors would also like
to thank Russ Housley, Bob Hinden, Scott Mansfield, Alexey
Melnikov, Suresh Krishnan, Mirja Kuhlewind, Ben Campbell,
Spencer Dawkins, Martin Vigoreux, Benjamin Kaduk, and Adrian
Farrel for careful review.</t>
</section> </section>
</middle> </middle>
<back> <back>
<references>
<name>References</name>
<references>
<name>Normative References</name>
<reference anchor="BCP10" target="https://rfc-editor.org/info/bcp10">
<front>
<title>IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and
Recall Process: Operation of the IETF Nominating and Recall Committees</titl
e>
<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="February" year="2020"/>
</front>
<seriesInfo name="BCP" value="10"/>
<seriesInfo name="RFC" value="8713"/>
</reference>
<references title="Normative References"> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
&RFC4071; ence.RFC.4071.xml"/>
&RFC4371; <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
&RFC7437; ence.RFC.4371.xml"/>
</references>
<references title="Informative References">
<reference anchor='I-D.ietf-iasa2-trust-rationale'>
<front>
<title>Discussion of the Effects of IASA 2.0 Changes as They Relate to
the IETF
Trust</title>
<author initials='J' surname='Arkko' fullname='Jari Arkko'>
<organization />
</author>
<date month='September' year='2018' />
</front> </references>
<seriesInfo name='Internet-Draft' value='draft-ietf-iasa2-trust-rationale <references>
-00' /> <name>Informative References</name>
<format type='TXT' <!-- I-D.ietf-iasa2-trust-rationale-03: I-D exists-->
target='http://www.ietf.org/internet-drafts/draft-ietf-iasa2-trus <reference anchor="RFC8715"
t-rationale-00.txt' /> target="https://rfc-editor.org/info/rfc8715">
</reference> <front>
<title>IETF Administrative Support Activity 2.0: Update to the
Process for Selection of Trustees for the IETF Trust</title>
<author initials="J." surname="Arkko">
<organization/>
</author>
<date month="February" year="2020"/>
</front>
<seriesInfo name="RFC" value="8715"/>
<seriesInfo name="DOI" value="10.17487/RFC8715"/>
</reference>
</references>
</references> </references>
<section anchor="ack" numbered="false" toc="default">
<section anchor="changes" title="Changes from Previous Versions"> <name>Acknowledgements</name>
<t>The authors would like to thank members of the earlier IASA
<t>RFC Editor: Please remove this section upon publication.</t> 2.0 design team: <contact fullname="Brian Haberman"/>, <contact
fullname="Eric Rescorla"/>, <contact fullname="Jari
<t>The version draft-itef-iasa2-trust-update-02.txt made some Arkko"/>, <contact fullname="Jason Livingood"/>, <contact fullname="Joe Ha
editorial corrections, as well as clarifying that no ll"/>,
confirmation is needed in the cases other than the nomcom and <contact fullname="Leslie Daigle"/>. The authors
appointment, specified how IETF Trust chair is chosen, and would also like to thank <contact fullname="Alissa Cooper"/>, <contact
required that an open process be used by the IESG for the fullname="Andrew Sullivan"/>, <contact fullname="Brian
selections.</t> Carpenter"/>, <contact fullname="Lucy Lynch"/>, and <contact fullname="Joh
n Levine"/> for interesting
<t>The version draft-ietf-iasa2-trust-update-01.txt has taken discussions in this problem space. The authors would also like
into account last call comments. The changes are: 1) to thank <contact fullname="Russ Housley"/>, <contact fullname="Bob Hinden
Clarification of the role of the IETF Trust Chair to "/>,
indicate which trustee positions are up for selection, similar to how RFC <contact fullname="Scott Mansfield"/>, <contact fullname="Alexey
7437 requires the IETF Executive Director to do it. 2) Melnikov"/>, <contact fullname="Suresh Krishnan"/>, <contact fullname="Mir
The addition of empty security and IANA consideration ja
sections. 3) The clarification of the staggering rules for K├╝hlewind"/>, <contact fullname="Ben Campbell"/>,
NomCom selections. 4) Updated text regarding the application of <contact fullname="Spencer Dawkins"/>, <contact fullname="Martin Vigoreux"
rules from RFC 7437. 5) Update draft title to be correct in />,
terms of specifying a process rather than the actual persons. <contact fullname="Benjamin Kaduk"/>, and <contact fullname="Adrian
6) Update the text regarding desirable expertise to use the Farrel"/> for careful review. Finally, the authors would like to thank the
same language as in RFC 7437 instead of the "list of desired authors of <xref target="RFC4371" format="default"/>, as the text from tha
qualifications".</t> t RFC remains in this document.
</t>
<t>The version draft-ietf-iasa2-trust-update-00.txt corrected
the desired document status to BCP, and made several editorial
and language updates. This version also updated the wording for
the request for the current trustees to adopt this change, from
"earliest convenience" to "earliest convenient time".</t>
<t>The version draft-arkko-iasa2-trust-update-00.txt was the
initial version.</t>
</section> </section>
</back> </back>
</rfc> </rfc>
 End of changes. 39 change blocks. 
189 lines changed or deleted 156 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/