<?xmlversion="1.0" encoding="US-ASCII"?> <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <!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" ?>version='1.0' encoding='utf-8'?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="bcp"docName="draft-ietf-iasa2-trust-update-02"consensus="true" docName="draft-ietf-iasa2-trust-update-03" indexInclude="true" ipr="trust200902"updates="4071,4371">number="8714" obsoletes="4371" prepTime="2020-02-26T17:17:28" scripts="Common,Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="4" tocInclude="true" xml:lang="en"> <link href="https://datatracker.ietf.org/doc/draft-ietf-iasa2-trust-update-03" rel="prev"/> <link href="https://dx.doi.org/10.17487/rfc8714" rel="alternate"/> <link href="urn:issn:2070-1721" rel="alternate"/> <front> <title abbrev="Trustees for the IETF Trust">Update to the Process for Selection of Trustees for the IETF Trust</title> <seriesInfo name="RFC" value="8714" stream="IETF"/> <seriesInfo name="BCP" value="101" stream="IETF"/> <author fullname="Jari Arkko" initials="J." surname="Arkko"><organization>Ericsson</organization><organization showOnFrontPage="true">Ericsson</organization> <address> <postal><street></street><street/> <city>Kauniainen</city><region></region><region/> <code>02700</code> <country>Finland</country> </postal> <email>jari.arkko@piuha.net</email> </address> </author> <author fullname="Ted Hardie" initials="T." surname="Hardie"> <address> <email>ted.ietf@gmail.com</email> </address> </author> <datemonth="October" year="2018" />month="02" year="2020"/> <area>General</area><workgroup>Internet Engineering Task Force</workgroup> <abstract> <t>This<workgroup>IASA2</workgroup> <keyword>IETF administration</keyword> <keyword>intellectual property</keyword> <keyword>leadership selection</keyword> <keyword>IASA</keyword> <abstract pn="section-abstract"> <t pn="section-abstract-1">This memo updates the process for selection oftrusteesTrustees for the IETF Trust. Previously, theInternetIETF Administrative Oversight Committee (IAOC) members also acted astrustees,Trustees, but the IAOC has been eliminated as part of an updateofto the structure of theInternetIETF Administrative Support Activity (IASA). This memo specifies that thetrusteesTrustees shall be selected separately.</t><t>This<t pn="section-abstract-2">This memoupdates RFCs 4071 and 4371 with regardsobsoletes RFC 4371. The changes relate only to the selection oftrustees.Trustees. All other aspects of the IETF Trust remain as they aretoday.</t>today. </t> </abstract> <boilerplate> <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1"> <name slugifiedName="name-status-of-this-memo">Status of This Memo</name> <t pn="section-boilerplate.1-1"> This memo documents an Internet Best Current Practice. </t> <t pn="section-boilerplate.1-2"> This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 7841. </t> <t pn="section-boilerplate.1-3"> Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at <eref target="https://www.rfc-editor.org/info/rfc8714" brackets="none"/>. </t> </section> <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2"> <name slugifiedName="name-copyright-notice">Copyright Notice</name> <t pn="section-boilerplate.2-1"> Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. </t> <t pn="section-boilerplate.2-2"> This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. </t> </section> </boilerplate> <toc> <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1"> <name slugifiedName="name-table-of-contents">Table of Contents</name> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1"> <li pn="section-toc.1-1.1"> <t keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t> </li> <li pn="section-toc.1-1.2"> <t keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-ietf-trust">IETF Trust</xref></t> </li> <li pn="section-toc.1-1.3"> <t keepWithNext="true" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-selection-of-trustees">Selection of Trustees</xref></t> </li> <li pn="section-toc.1-1.4"> <t keepWithNext="true" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t> </li> <li pn="section-toc.1-1.5"> <t keepWithNext="true" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t> </li> <li pn="section-toc.1-1.6"> <t keepWithNext="true" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.6.2"> <li pn="section-toc.1-1.6.2.1"> <t keepWithNext="true" pn="section-toc.1-1.6.2.1.1"><xref derivedContent="6.1" format="counter" sectionFormat="of" target="section-6.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t> </li> <li pn="section-toc.1-1.6.2.2"> <t keepWithNext="true" pn="section-toc.1-1.6.2.2.1"><xref derivedContent="6.2" format="counter" sectionFormat="of" target="section-6.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t> </li> </ul> </li> <li pn="section-toc.1-1.7"> <t keepWithNext="true" pn="section-toc.1-1.7.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t> </li> <li pn="section-toc.1-1.8"> <t keepWithNext="true" pn="section-toc.1-1.8.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t> </li> </ul> </section> </toc> </front> <middle> <sectiontitle="Introduction"> <t>Thisnumbered="true" toc="include" removeInRFC="false" pn="section-1"> <name slugifiedName="name-introduction">Introduction</name> <t pn="section-1-1">This memo updates the process for selection oftrusteesTrustees for the IETF Trust. Previously, theInternetIETF Administrative Oversight Committee (IAOC) members also acted astrustees,Trustees, but the IAOC has been eliminated as part of an updateofto the structure of theInternetIETF Administrative Support Activity (IASA). This memo specifies that thetrusteesTrustees shall be selectedseparately.</t> <t>Thisseparately. See <xref target="selection" format="default" sectionFormat="of" derivedContent="Section 3"/>.</t> <t pn="section-1-2">This memoupdates RFCs 4071 and 4371 with regardsobsoletes <xref target="RFC4371" format="default" sectionFormat="of" derivedContent="RFC4371"/>. The changes relate only to the selection oftrustees.Trustees. All other aspects of the IETF Trust remain as they aretoday.</t> <t>Fortoday. <xref target="ietf-trust" format="default" sectionFormat="of" derivedContent="Section 2"/> copies the definition as it was in <xref target="RFC4371" format="default" sectionFormat="of" derivedContent="RFC4371"/>, only leaving out the part about Trustee selection and adding a reference to the IETF Trust website. </t> <t pn="section-1-3">For a discussion of why this change is needed and a rationale for these specific changes, see <xreftarget="I-D.ietf-iasa2-trust-rationale"/>.</t>target="RFC8715" format="default" sectionFormat="of" derivedContent="RFC8715"/>.</t> </section> <sectionanchor="selection" title="Selectionanchor="ietf-trust" numbered="true" toc="include" removeInRFC="false" pn="section-2"> <name slugifiedName="name-ietf-trust">IETF Trust</name> <t pn="section-2-1">A Trust ("the IETF Trust") has been formed for the purpose ofTrustees"> <t>Thisacquiring, 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 pn="section-2-2">Further details of the IETF Trust may be found at the IETF Trust's website, <<eref target="https://trustee.ietf.org/" brackets="none"/>>.</t> </section> <section anchor="selection" numbered="true" toc="include" removeInRFC="false" pn="section-3"> <name slugifiedName="name-selection-of-trustees">Selection of Trustees</name> <t pn="section-3-1">This document revises the original Trustee selection procedures defined in <xreftarget="RFC4071"/>target="RFC4071" format="default" sectionFormat="of" derivedContent="RFC4071"/> and <xreftarget="RFC4371"/>,target="RFC4371" format="default" sectionFormat="of" derivedContent="RFC4371"/> to eliminate the requirement thattrusteesTrustees be drawn from the members of the IAOC.</t><t>In<t pn="section-3-2">In this newly revised IETF Trust structure, there will be five Trustees. Three shall be appointed by the IETF Nominating Committee (NomCom) and confirmed by the Internet Engineering Steering Group (IESG), one shall be appointed by the IESG, and one shall be appointed by the Internet Society (ISOC) Board of Trustees. The appointments by the IESG and the ISOC Board of Trustees do not require confirmation.</t><t>The<t pn="section-3-3">The IETF Trust Chair informs the nominating committee of the Trustee positions to be reviewed. The IETF Trust will provide a summary of the expertise desired of the Trustee candidates to each appointing body.</t><t>A<t pn="section-3-4">A change to the Trust Agreement is required to put this change into effect, and this document requests that the current Trustees make this change at the earliest convenient time and no later than the end of the 104th IETF meeting in March 2019.</t><t>The<t pn="section-3-5">The terms of the appointedtrusteesTrustees from the IETF NomCom shall be three years. The initial selection shall be one, two, and three year terms in order to initially stagger the terms. The other appointments by the IESG and the ISOC Board of Trustees shall be two year terms, with the initial terms being one and two years, respectively. The goal of the staggered initial terms is to minimize potential Trustee turnover in any single year. To maintain the staggered terms, each appointing bodymaymay, at itsdiscretiondiscretion, appoint Trustees for shorter terms as needed in exceptional situations, e.g., for mid-term vacancies or when an appointment is not ready by the time of the first IETF meeting of the year.</t><t>Once<t pn="section-3-6">Once the initialtrusteeTrustee selections according to the procedures in this document are complete, and at each subsequent annual meeting of the IETF Trustonce(once newtrusteesTrustees areseated,seated), thetrusteesTrustees shall elect one Trustee to serve as IETF Trust Chair by a majority vote of the IETFTrust one trustee to serve asTrust.</t> <t pn="section-3-7">Trustees appointed by the IETFTrust Chair.</t> <t>The processes regardingNomComappointments and recalls of Trustees formay be recalled according to theIETF Trust follow thoserecall process described in <xreftarget="RFC7437"/>. For the appointmentstarget="BCP10" format="default" sectionFormat="of" derivedContent="BCP10"/>. Trustees appointed by the IESG or by the ISOC Board of Directors may be recalled by the appointing body. For appointments made by the IESG, the IESG is expected to run an open selection process and to consider the necessary skill set and conflicts of interest as part of that process.</t> </section> <sectiontitle="Security Considerations"> <t>Thisnumbered="true" toc="include" removeInRFC="false" pn="section-4"> <name slugifiedName="name-security-considerations">Security Considerations</name> <t pn="section-4-1">This memo has no security implications for the Internet.</t> </section> <sectiontitle="IANA Considerations"> <t>This memo requestsnumbered="true" toc="include" removeInRFC="false" pn="section-5"> <name slugifiedName="name-iana-considerations">IANA Considerations</name> <t pn="section-5-1">This document has noaction 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>IANA actions.</t> </section> </middle> <back> <referencestitle="Normative References"> &RFC4071; &RFC4371; &RFC7437; </references>pn="section-6"> <name slugifiedName="name-references">References</name> <referencestitle="Informative References">pn="section-6.1"> <name slugifiedName="name-normative-references">Normative References</name> <referenceanchor='I-D.ietf-iasa2-trust-rationale'>anchor="BCP10" target="https://www.rfc-editor.org/info/bcp10" quoteTitle="true" derivedAnchor="BCP10"> <front><title>Discussion of the Effects<title>IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation ofIASA 2.0 Changes as They Relate tothe IETFTrust</title>Nominating and Recall Committees</title> <author initials="M." surname="Kucherawy" role="editor"> <organization showOnFrontPage="true"/> </author> <authorinitials='J' surname='Arkko' fullname='Jari Arkko'>initials="R." surname="Hinden" role="editor"> <organization/>showOnFrontPage="true"/> </author> <author initials="J." surname="Livingood" role="editor"> <organization showOnFrontPage="true"/> </author> <datemonth='September' year='2018' />month="February" year="2020"/> </front> <seriesInfoname='Internet-Draft' value='draft-ietf-iasa2-trust-rationale-00' /> <format type='TXT' target='http://www.ietf.org/internet-drafts/draft-ietf-iasa2-trust-rationale-00.txt' />name="BCP" value="10"/> <seriesInfo name="RFC" value="8713"/> </reference></references> <section anchor="changes" title="Changes from Previous Versions"> <t>RFC Editor: Please remove this section upon publication.</t> <t>The version draft-itef-iasa2-trust-update-02.txt made some editorial corrections, as well as clarifying that no confirmation is needed in<reference anchor="RFC4071" target="https://www.rfc-editor.org/info/rfc4071" quoteTitle="true" derivedAnchor="RFC4071"> <front> <title>Structure of thecases other thanIETF Administrative Support Activity (IASA)</title> <author initials="R." surname="Austein" fullname="R. Austein" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="B." surname="Wijnen" fullname="B. Wijnen" role="editor"> <organization showOnFrontPage="true"/> </author> <date year="2005" month="April"/> <abstract> <t>This document describes the structure of thenomcom appointment, specified howIETFTrust chair is chosen, and required thatAdministrative Support Activity (IASA) as anopen process be used by the IESG foractivity housed within theselections.</t> <t>The version draft-ietf-iasa2-trust-update-01.txt has taken into account last call comments. The changes are: 1) Clarification ofInternet Society (ISOC). It defines theroleroles and responsibilities of the IETFTrust Chair to indicate which trustee positions are up for selection, similar to how RFC 7437 requiresAdministrative Oversight Committee (IAOC), the IETFExecutiveAdministrative Directorto do it. 2) The addition of empty security(IAD), andIANA consideration sections. 3) The clarificationISOC in the fiscal and administrative support of thestaggeringIETF standards process. It also defines the membership and selection rules forNomCom selections. 4) Updated text regardingtheapplication of rules from RFC 7437. 5)IAOC. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="101"/> <seriesInfo name="RFC" value="4071"/> <seriesInfo name="DOI" value="10.17487/RFC4071"/> </reference> <reference anchor="RFC4371" target="https://www.rfc-editor.org/info/rfc4371" quoteTitle="true" derivedAnchor="RFC4371"> <front> <title>BCP 101 Updatedraft titlefor IPR Trust</title> <author initials="B." surname="Carpenter" fullname="B. Carpenter" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="L." surname="Lynch" fullname="L. Lynch" role="editor"> <organization showOnFrontPage="true"/> </author> <date year="2006" month="January"/> <abstract> <t>This document updates BCP 101 tobe correct in termstake account ofspecifying a process rather thantheactual persons. 6) Updatenew IETF Intellectual Property Trust. This document specifies an Internet Best Current Practices for thetext regarding desirable expertiseInternet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="101"/> <seriesInfo name="RFC" value="4371"/> <seriesInfo name="DOI" value="10.17487/RFC4371"/> </reference> </references> <references pn="section-6.2"> <name slugifiedName="name-informative-references">Informative References</name> <reference anchor="RFC8715" target="https://www.rfc-editor.org/info/rfc8715" quoteTitle="true" derivedAnchor="RFC8715"> <front> <title>IETF Administrative Support Activity 2.0: Update tousethesame language as in RFC 7437 insteadProcess for Selection of Trustees for the"listIETF Trust</title> <author initials="J." surname="Arkko"> <organization showOnFrontPage="true"/> </author> <date month="February" year="2020"/> </front> <seriesInfo name="RFC" value="8715"/> <seriesInfo name="DOI" value="10.17487/RFC8715"/> </reference> </references> </references> <section anchor="ack" numbered="false" toc="include" removeInRFC="false" pn="section-appendix.a"> <name slugifiedName="name-acknowledgements">Acknowledgements</name> <t pn="section-appendix.a-1">The authors would like to thank members ofdesired qualifications".</t> <t>The version draft-ietf-iasa2-trust-update-00.txt correctedthedesired document status to BCP, and made several editorial and language updates. This versionearlier IASA 2.0 design team: <contact fullname="Brian Haberman"/>, <contact fullname="Eric Rescorla"/>, <contact fullname="Jari Arkko"/>, <contact fullname="Jason Livingood"/>, <contact fullname="Joe Hall"/>, and <contact fullname="Leslie Daigle"/>. The authors would alsoupdated the wordinglike to thank <contact fullname="Alissa Cooper"/>, <contact fullname="Andrew Sullivan"/>, <contact fullname="Brian Carpenter"/>, <contact fullname="Lucy Lynch"/>, and <contact fullname="John Levine"/> forthe requestinteresting discussions in this problem space. The authors would also like to thank <contact fullname="Russ Housley"/>, <contact fullname="Bob Hinden"/>, <contact fullname="Scott Mansfield"/>, <contact fullname="Alexey Melnikov"/>, <contact fullname="Suresh Krishnan"/>, <contact fullname="Mirja Kühlewind"/>, <contact fullname="Ben Campbell"/>, <contact fullname="Spencer Dawkins"/>, <contact fullname="Martin Vigoreux"/>, <contact fullname="Benjamin Kaduk"/>, and <contact fullname="Adrian Farrel"/> for careful review. Finally, thecurrent trustees to adopt this change, from "earliest convenience"authors would like to"earliest convenient time".</t> <t>The version draft-arkko-iasa2-trust-update-00.txt wasthank theinitial version.</t>authors of <xref target="RFC4371" format="default" sectionFormat="of" derivedContent="RFC4371"/>, as the text from that RFC remains in this document. </t> </section> <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b"> <name slugifiedName="name-authors-addresses">Authors' Addresses</name> <author fullname="Jari Arkko" initials="J." surname="Arkko"> <organization showOnFrontPage="true">Ericsson</organization> <address> <postal> <street/> <city>Kauniainen</city> <region/> <code>02700</code> <country>Finland</country> </postal> <email>jari.arkko@piuha.net</email> </address> </author> <author fullname="Ted Hardie" initials="T." surname="Hardie"> <address> <email>ted.ietf@gmail.com</email> </address> </author> </section> </back> </rfc>