<?xml version="1.0" encoding="US-ASCII"?> version='1.0' encoding='utf-8'?>
<!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" ?> "rfc2629-xhtml.ent">

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="bcp" docName="draft-ietf-iasa2-trust-update-02" number="8714"
     submissionType="IETF" consensus="yes" ipr="trust200902" updates="4071,4371"> 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>
    <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"/>
    <seriesInfo name="BCP" value="101"/>
    <author fullname="Jari Arkko" initials="J." surname="Arkko">
      <organization>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>
    <date month="October" year="2018" /> month="February" year="2020"/>
    <area>General</area>

    <workgroup>Internet Engineering Task Force</workgroup>
    <workgroup>IASA2</workgroup>
    <keyword>IETF administration</keyword>
    <keyword>intellectual property</keyword>
    <keyword>leadership selection</keyword>
    <keyword>IASA</keyword>
    <abstract>
      <t>This memo updates the process for selection of trustees Trustees for the IETF
      Trust. Previously, the Internet IETF Administrative Oversight Committee (IAOC)
      members also acted as trustees, Trustees, but the IAOC
      has been eliminated as part of an update of to the structure of
      the Internet IETF Administrative Support Activity (IASA). This memo
      specifies that the trustees Trustees shall be selected separately.</t>
      <t>This memo updates RFCs 4071 and 4371 with regards obsoletes RFC 4371.  The changes relate only
         to the selection of trustees. Trustees. All other aspects of the IETF Trust
	 remain as they are today.</t> today.
      </t>
    </abstract>
  </front>
  <middle>
    <section title="Introduction"> numbered="true" toc="default">
      <name>Introduction</name>
      <t>This memo updates the process for selection of trustees Trustees for the IETF
      Trust. Previously, the Internet IETF Administrative Oversight Committee (IAOC)
      members also acted as trustees, Trustees, but the IAOC has been eliminated as part
      of an update of to the structure of the Internet IETF Administrative Support
      Activity (IASA). This memo specifies that the trustees Trustees shall be selected separately.</t>
      separately. See <xref target="selection" format="default"/>.</t>
      <t>This memo updates RFCs 4071 and 4371 with regards obsoletes <xref target="RFC4371"/>.  The changes relate only to the
      selection of trustees. Trustees.  All other aspects of the IETF Trust remain as
      they are today.</t> today. <xref target="ietf-trust" format="default"/> copies the
      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
      for these specific changes, see <xref
      target="I-D.ietf-iasa2-trust-rationale"/>.</t> target="RFC8715" format="default"/>.</t>
    </section>
    <section anchor="ietf-trust" numbered="true" toc="default">
      <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" title="Selection numbered="true" toc="default">
      <name>Selection of Trustees"> Trustees</name>
      <t>This document revises the original Trustee selection procedures
      defined in <xref target="RFC4071"/> target="RFC4071" format="default"/> and <xref target="RFC4371"/>, target="RFC4371" format="default"/>
      to eliminate the requirement that trustees Trustees be drawn from the
      members of the IAOC.</t>
      <t>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 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 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 terms of the appointed trustees Trustees 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 body may may, at its discretion discretion,
      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 the initial trustee Trustee selections according to the
      procedures in this document are complete, and at each subsequent
      annual meeting of the IETF Trust once (once new trustees Trustees are seated, seated),
      the trustees Trustees shall elect one Trustee to serve as IETF Trust Chair by a
      majority vote of the IETF Trust
      one trustee to serve as Trust.</t>
      <t>Trustees appointed by the IETF Trust Chair.</t>

      <t>The processes regarding NomCom appointments and recalls of
      Trustees for may be recalled according to
      the IETF Trust follow those recall process described in <xref
      target="RFC7437"/>. For target="BCP10" format="default"/>.
       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>
    <section title="Security Considerations"> numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>This memo has no security implications for the Internet.</t>
    </section>
    <section title="IANA Considerations"> numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This memo requests document has no action from IANA.</t> IANA actions.</t>
    </section>
  </middle>
  <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</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="February" year="2020"/>
  </front>
  <seriesInfo name="BCP" value="10"/>
  <seriesInfo name="RFC" value="8713"/>
</reference>

        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4071.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4371.xml"/>

      </references>
      <references>
        <name>Informative References</name>
        <!-- I-D.ietf-iasa2-trust-rationale-03: I-D exists-->
        <reference anchor="RFC8715"
		   target="https://rfc-editor.org/info/rfc8715">
          <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>
    <section anchor="ack" title="Acknowledgements"> numbered="false" toc="default">
      <name>Acknowledgements</name>
      <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. 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 also like to thank Alissa Cooper, Andrew Sullivan, Brian
      Carpenter, Lucy Lynch, and John Levine <contact fullname="Alissa Cooper"/>, <contact
      fullname="Andrew Sullivan"/>, <contact fullname="Brian
      Carpenter"/>, <contact fullname="Lucy Lynch"/>, and <contact fullname="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 <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.</t>

    </section>

  </middle>

  <back>

    <references title="Normative References">
      &RFC4071;
      &RFC4371;
      &RFC7437;
    </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 review. Finally, the IETF
	  Trust</title>

	  <author initials='J' surname='Arkko' fullname='Jari Arkko'>
	    <organization />
	  </author>

	  <date month='September' year='2018' />

	</front>
	<seriesInfo name='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' />
      </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 the cases other than the nomcom
      appointment, specified how IETF Trust chair is chosen, and
      required that an open process be used by the IESG for the
      selections.</t>

      <t>The version draft-ietf-iasa2-trust-update-01.txt has taken
      into account last call comments. The changes are: 1)
      Clarification of the role of the IETF Trust Chair to
      indicate which trustee positions are up for selection, similar authors would like to how RFC
      7437 requires thank the IETF Executive Director to do it. 2)
      The addition of empty security and IANA consideration
      sections. 3) The clarification
      authors of <xref target="RFC4371" format="default"/>, as the staggering rules for
      NomCom selections. 4) Updated text regarding the application of
      rules from that RFC 7437. 5) Update draft title to be correct remains in
      terms of specifying a process rather than the actual persons.
      6) Update the text regarding desirable expertise to use the
      same language as in RFC 7437 instead of the "list of desired
      qualifications".</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> document.
</t>
    </section>
  </back>
</rfc>