<?xml version="1.0" encoding="US-ASCII"?> version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [

<!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">
<!ENTITY RFC7979 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7979.xml">
<!ENTITY I-D.ietf-iasa2-struct SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-iasa2-struct.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 category="info" xmlns:xi="http://www.w3.org/2001/XInclude" number="8715"
     docName="draft-ietf-iasa2-trust-rationale-03" ipr="trust200902"> category="info"
     submissionType="IETF" consensus="yes" ipr="trust200902" obsoletes=""
     updates="" xml:lang="en" tocInclude="true" tocDepth="4" symRefs="true"
     sortRefs="true" version="3" >
  <!-- xml2rfc v2v3 conversion 2.37.3 -->
  <front>
    <title abbrev="IASA 2.0 and IETF Trust">
      Discussion of the IASA 2.0 Changes as They Relate to the IETF Trust</title>
    <seriesInfo name="RFC" value="8715"/>
    <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>
    <date month="October" year="2018" /> month="January" 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 document is published to capture captures the rationale for the
      changes introduced in RFC NNNN (RFC Editor: please replace NNNN
      with the RFC number of <xref
      target="I-D.ietf-iasa2-trust-update"/>), Update 8714, "Update to the Process for Selection of
      Trustees for the IETF Trust.</t> Trust".</t>
      <t>At the time RFC NNNN 8714 was published, IETF administrative
      structure the changes ("IASA 2.0") to the IETF
      Administrative Support Activity, Version 2.0 (IASA 2.0) had an impact on the IETF
      Trust because members of the IETF Administrative Oversight
      Committee (IAOC), which was being phased out, had served as
      Trustees of the IETF Trust. This document provides
      background on the past IETF Trust arrangements, explains the
      effect of the rules in the founding documents during the
      transition to the new arrangement, and provides a rationale for
      the update.</t>
    </abstract>
  </front>
  <middle>
    <section title="Introduction"> numbered="true" toc="default">
      <name>Introduction</name>
      <t>This document is published to capture captures the rationale for the
      changes introduced in <xref
      target="I-D.ietf-iasa2-trust-update"/>.</t> target="RFC8714" format="default"/>.</t>

      <t>At the time <xref target="I-D.ietf-iasa2-trust-update"/> target="RFC8714" format="default"/> was
      published, IETF administrative structure the changes ("IASA 2.0") to the IETF Administrative Support Activity,
      Version 2.0 (IASA 2.0) had an impact on the IETF Trust <xref target="RFC4071"/>
      target="RFC4071" format="default"/> <xref
      target="RFC4371"/> target="RFC4371"
      format="default"/> <xref target="I-D.ietf-iasa2-struct"/>. target="RFC8711" format="default"/>. This
      is because members of the IETF Administrative
      Oversight Committee (IAOC), which was being phased out, had
      served as Trustees of the IETF Trust.  A minimal change
      regarding the selection of the trustees Trustees is implemented by <xref
      target="I-D.ietf-iasa2-trust-update"/>.</t>
      target="RFC8714" format="default"/>.</t>
      <t>This companion memo provides some background on the details
      of the past IETF Trust arrangements, explains the effect of
      the rules in the founding documents during the transition to the new
      arrangement, and provides a rationale for the update.</t>
    </section>
    <section anchor="background" title="Background"> numbered="true" toc="default">
      <name>Background</name>
      <t>The purpose of the IETF Trust is to acquire, hold, maintain,
      and license certain existing and future intellectual property
      and other property used in connection with the administration of
      the IETF <xref target="RFC4371"/>. target="RFC8714" format="default"/>. The intellectual property is,
      for instance, rights that the IETF contributors grant for text
      in RFCs and Internet-Drafts. The IETF Trust also manages
      trademarks such as "IETF" and domain names such as
      "ietf.org". The IETF Trust is also serving the broader Internet
      community by holding domains and trademarks associated with the Internet Assigned Numbers Authority (IANA) <xref
      target="RFC7979"/>.</t> target="RFC7979" format="default"/>.</t>
      <t>The IETF Trust is a legal entity, registered in the
      Commonwealth of Virginia <xref target="Trust-FD"/>.</t> target="Trust-FD" format="default"/>.</t>
      <t>Previously, the members of the IAOC also served as ex officio
      Trustees of the IETF Trust. The founding documents specify
      persons eligible to become trustees Trustees as having to be then-current
      members of the IAOC <xref target="Trust-FD"/>. target="Trust-FD" format="default"/>.  The documents
      also specify that if for any reason there are fewer than three
      individuals serving as Trustees, then the Internet Engineering
      Steering Group (IESG), or the IESG's successor as the leadership
      of the IETF, shall appoint one or more individuals to serve in a
      temporary capacity as Trustee(s) until eligible persons can be found.</t>

      <t>In
<!-- [rfced] We believe the IAD is not being counted as part of the eight
Trustees.  Perhaps this should be explained?  Otherwise, it seems as as though
there were nine Trustees (2 NomCom + 1 IESG + 1 IAB + 1 ISOC + 3 ex officio
members + 1 IAD).

   In the previous system system, there were eight IAOC members.  Two were
   named by the IETF Nominating Committee (NomCom), one by the
      IESG, Internet
   Engineering Steering Group (IESG), one by the Internet Architecture
   Board (IAB), and one by the Internet Society (ISOC) Board of
   Trustees.  There were three ex officio members via their roles as
   IETF Chair, ISOC CEO, and IAB Chair.  In addition, the IETF
   Administrative Director (IAD) served also as one of the Trustees.
-->
      <t>In the previous system, there were eight IAOC members. Two were
      named by the IETF Nominating Committee (NomCom), one by the Internet
      Engineering Steering Group (IESG), one by the Internet Architecture Board (IAB), and one by
      the Internet Society (ISOC) Board of Trustees. There
      were three ex officio members via their roles as IETF Chair, ISOC CEO,
      and IAB Chair. In addition, the IETF Administrative Director (IAD)
      served also as one of the trustees.</t> Trustees.</t>
    </section>
    <section anchor="approach" title="General Approach"> numbered="true" toc="default">
      <name>General Approach</name>
      <t>There were two basic approaches to resolving the issue with
      the trustees, when Trustees once the IAOC ceased to exist.  One could have imagined
      merging approach would be to
      merge all IETF Trust functions in the new IASA structure and
      under the new legal entity. This However, this memo advocated advocates a second
      approach where the IETF Trust is kept independent.</t>
      <t>The rationale for advocating the second approach is is, in part part,
      to minimize changes to the IETF Trust while the IETF's
      administrative structure is undergoing major change.  In
      addition, the IETF Trust and other administrative IETF processes
      are quite different. While very important, the IETF Trust is a
      low-activity entity where changes are minimal and gradual, and
      there are no pressing issues.</t>
    </section>
    <section anchor="selection" title="Changing numbered="true" toc="default">
      <name>Changing the Way Trustees Are Selected">

      <t>At the time when Selected</name>
      <t>When the trustees served Trustees were serving on both the IETF Trust and the
      IAOC, many of the requirements for naming a particular group of
      people were driven by the IAOC's requirements.  For the IETF
      Trust in the new model, some of those arrangements were able to be
      rethought, both in terms of the number and source of the
      trustees,
      Trustees, as well as the desired qualifications and length of
      terms.</t>
      <t>Several options were possible, of course.
   A newly designed
      naming selection process could have been devised. The argument here is devised, but in this
   document we argue for a relatively limited change, however, change based largely on the basis of fact that a) the IETF
   Trust arrangements worked generally working well, and on b) the relatively modest expected time commitments combined with commitment
   is expected to be modest, and c) the assets need for very careful
      management of the assets.</t> management.</t>
      <t>As a result, a smaller group of trustees Trustees appeared sufficient.</t>
      <t>In addition, the terms set for the
      trustees
      Trustees selected from the IETF community could be set to longer than
      the two year two-year period typical of other IETF bodies.</t>
      <t>One could have continued the practice of having the chairs and CEOs
      from the IETF, IAB, and Internet Society be trustees Trustees as well, but
      this may not be necessary. In general, the tasks of the IETF
      Trust are well defined, and while there is a need for
      coordination, it does not need to be at the level of chairs or
      CEOs.</t>
      <t>Given all this, one approach was to have trustees Trustees appointed
      by the NomCom, the IESG, and the ISOC Board of Trustees. (One might also
      have considered the IETF Administration LLC legal entity instead
      of the Internet Society for this role. But role, but the Internet Society
      is perhaps more suitable for the role, role given their focus on the
      broad use of the IETF Trust assets and not merely administrative
      aspects).</t>
      aspects.)</t>
      <t>If the same principles would continue to be used as were used
      in for previous appointments, appointments continued to be
      used, then appointments performed by the NomCom would need to be
      confirmed by another entity, which entity. This could be, for instance, either the
      IESG or the IAB. The IESG had previously been the confirming body for
      the IAOC, so it has been retained in that role for the trustees.</t> Trustees.</t>
    </section>
    <section anchor="transition" title="Transition"> numbered="true" toc="default">
      <name>Transition</name>
      <t>When the new entity for the IETF Administration LLC was set up,
      the IAOC was expected to be discontinued soon
      thereafter. Fortunately, there was no pressing need to change
      all the components of the IAOC and its dependent organizations
      at the same time. As discussed above (<xref
      target="background"/>), in <xref target="background" format="default"/>, the IESG holds the ability to continue
      to name trustees. And once Trustees. Once the updated procedures were in place,
      the IETF Trust had its management nominated in the usual manner,
      and the exceptional IESG IESG's exception process was no longer needed.</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>

    </section>

    <section anchor="ack" title="Acknowledgements">

      <t>The author would like to thank other members of the earlier
      IASA 2.0 design team who were Brian Haberman, Eric Rescorla,
      Jason Livingood, Joe Hall, and Leslie Daigle. The authors would
      also like to thank Alissa Cooper, Ted Hardie, Andrew Sullivan,
      Brian Carpenter, Lucy Lynch, and John Levine for interesting
      discussions in this problem space, and Adrian Farrel, Tero
      Kivinen, Russ Housley, Benjamin Kaduk, Adam Roach and Meral
      Shirazipour for careful review.</t> IANA actions.</t>
    </section>
  </middle>
  <back>

    <references title="Normative References">
      &RFC4071;
      &RFC4371;
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
       <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 title="Informative References">

      &RFC7979;
      &I-D.ietf-iasa2-struct;

      <references>
        <name>Informative References</name>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7979.xml"/>
        <!-- draft-ietf-iasa2-trust-update-02: I-D exists -->
        <reference anchor='I-D.ietf-iasa2-trust-update'> anchor="RFC8714" target="https://rfc-editor.org/info/rfc8714">
          <front>
            <title>Update to the Process for Selection of Trustees for the
	    IETF Trust</title>
            <author initials='J' surname='Arkko' fullname='Jari Arkko'>
	    <organization /> initials="J." surname="Arkko">
              <organization/>
            </author>
            <author initials='T' surname='Hardie' fullname='Ted Hardie'>
	    <organization /> initials="T." surname="Hardie" >
              <organization/>
            </author>
            <date month='September' year='2018' /> month="January" year="2020"/>
          </front>
          <seriesInfo name='Internet-Draft' value='draft-ietf-iasa2-trust-update-00' />
	<format type='TXT'
		target='http://www.ietf.org/internet-drafts/draft-ietf-iasa2-trust-update-00.txt' /> name="BCP" value="101"/>
          <seriesInfo name="RFC" value="8715"/>
          <seriesInfo name="DOI" value="10.17487/RFC8715"/>
        </reference>

        <reference anchor="Trust-FD"> anchor="Trust-FD" target="https://trustee.ietf.org/founding-documents.html">
          <front>
            <title>Founding Documents</title>
            <author>
              <organization>IETF Trust</organization>
            </author>
          </front>
        </reference>

<!-- draft-ietf-iasa2-struct-06: I-D expired Replaced by draft-ietf-iasa2-rfc4071bis -->
        <reference anchor="RFC8711" target="https://rfc-editor.org/info/rfc8711">
          <front>
            <title>Structure of the IETF Administrative Support Activity,
	    Version 2.0</title>
            <author initials="B." surname="Haberman">
              <organization/>
            </author>
            <author surname="IETF Trust"></author> initials="J." surname="Hall">
              <organization/>
            </author>
            <author initials="J." surname="Livingood">
              <organization/>
            </author>
            <date month='February' year='2014 (https://trustee.ietf.org/founding-documents.html)'/> month="January" year="2020"/>
          </front>
        <format type='HTML'
		target='https://trustee.ietf.org/founding-documents.html'/>
          <seriesInfo name="BCP" value="101"/>
          <seriesInfo name="RFC" value="8711"/>
          <seriesInfo name="DOI" value="10.17487/RFC8711"/>
        </reference>
      </references>
    </references>
    <section anchor="changes" title="Changes from Previous Versions">

      <t>RFC Editor: Please remove this section upon publication.</t>

      <t>The version draft-ietf-iasa2-trust-rationale-03.txt made
      some editorial corrections.</t>

      <t>The version draft-ietf-iasa2-trust-rationale-02.txt made
      some editorial corrections.</t> anchor="ack" numbered="false" toc="default">
      <name>Acknowledgements</name>
      <t>The version draft-ietf-iasa2-trust-rationale-01.txt includes
      changes relating author would like to last call comments. The changes are 1)
      indication thank other members of why this document is being published 2) updates to
      references, 3) the addition of empty security and IANA
      consideration sections, 4) editorial changes necessary for a
      document that is earlier
      IASA 2.0 design team: <contact fullname="Brian Haberman"/>, <contact fullname="Eric Rescorla"/>,
      <contact fullname="Jason Livingood"/>, <contact fullname="Joe Hall"/>, and
	<contact fullname="Leslie Daigle"/>. The author would
      also read later, and not just used in like to thank <contact fullname="Alissa Cooper"/>, <contact
      fullname="Ted Hardie"/>, <contact fullname="Andrew Sullivan"/>,
      <contact fullname="Brian Carpenter"/>, <contact fullname="Lucy Lynch"/>, and
	<contact fullname="John Levine"/> for interesting
      discussions at in this time.</t>

      <t>The version draft-ietf-iasa2-trust-rationale-00.txt includes
      only editorial problem space, and language updates.</t>

      <t>The version draft-arkko-iasa2-trust-rationale-00.txt was the
      initial version.</t> <contact fullname="Adrian Farrel"/>,
      <contact fullname="Tero Kivinen"/>, <contact fullname="Russ Housley"/>,
      <contact fullname="Benjamin Kaduk"/>, <contact fullname="Adam Roach"/>,
      and <contact fullname="Meral Shirazipour"/> for careful review.</t>
    </section>
  </back>
</rfc>