rfc8715xml2.original.xml		rfc8715.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 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/bibxml
	3/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" ?>
	<rfc category="info" docName="draft-ietf-iasa2-trust-rationale-03" ipr="trust200
	902">
			<rfc xmlns:xi="http://www.w3.org/2001/XInclude" number="8715"
			docName="draft-ietf-iasa2-trust-rationale-03" 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>		<front>
	<title abbrev="IASA 2.0 and IETF Trust">		<title abbrev="IASA 2.0 and IETF Trust">
	Discussion of the IASA 2.0 Changes as They Relate to the IETF		Discussion of the IASA 2.0 Changes as They Relate to the IETF Trust</title
	Trust</title>		>
			<seriesInfo name="RFC" value="8715"/>
	<author fullname="Jari Arkko" initials="J."		<author fullname="Jari Arkko" initials="J." surname="Arkko">
	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>
			<date month="January" 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 document captures the rationale for the
	<t>This document is published to capture the rationale for the		changes introduced in RFC 8714, "Update to the Process for Selection of
	changes introduced in RFC NNNN (RFC Editor: please replace NNNN		Trustees for the IETF Trust".</t>
	with the RFC number of <xref		<t>At the time RFC 8714 was published, the changes to the IETF
	target="I-D.ietf-iasa2-trust-update"/>), Update to the Process for Selecti		Administrative Support Activity, Version 2.0 (IASA 2.0) had an impact on t
	on		he IETF
	of Trustees for the IETF Trust.</t>
	<t>At the time RFC NNNN was published, IETF administrative
	structure changes ("IASA 2.0") had an impact on the IETF
	Trust because members of the IETF Administrative Oversight		Trust because members of the IETF Administrative Oversight
	Committee (IAOC), which was being phased out, had served as		Committee (IAOC), which was being phased out, had served as
	Trustees of the IETF Trust. This document provides		Trustees of the IETF Trust. This document provides
	background on the past IETF Trust arrangements, explains the		background on the past IETF Trust arrangements, explains the
	effect of the rules in the founding documents during the		effect of the rules in the founding documents during the
	transition to the new arrangement, and provides a rationale for		transition to the new arrangement, and provides a rationale for
	the update.</t>		the update.</t>
	</abstract>		</abstract>
	</front>		</front>
	<middle>		<middle>
			<section numbered="true" toc="default">
			<name>Introduction</name>
			<t>This document captures the rationale for the
			changes introduced in <xref target="RFC8714" format="default"/>.</t>
	<section title="Introduction">		<t>At the time <xref target="RFC8714" format="default"/> was
			published, the changes to the IETF Administrative Support Activity,
	<t>This document is published to capture the rationale for the		Version 2.0 (IASA 2.0) had an impact on the IETF Trust <xref
	changes introduced in <xref		target="RFC4071" format="default"/> <xref target="RFC4371"
	target="I-D.ietf-iasa2-trust-update"/>.</t>		format="default"/> <xref target="RFC8711" format="default"/>. This
	<t>At the time <xref target="I-D.ietf-iasa2-trust-update"/> was
	published, IETF administrative structure changes ("IASA 2.0")
	had an impact on the IETF Trust <xref target="RFC4071"/> <xref
	target="RFC4371"/> <xref target="I-D.ietf-iasa2-struct"/>. This
	is because members of the IETF Administrative		is because members of the IETF Administrative
	Oversight Committee (IAOC), which was being phased out, had		Oversight Committee (IAOC), which was being phased out, had
	served as Trustees of the IETF Trust. A minimal change		served as Trustees of the IETF Trust. A minimal change
	regarding the selection of the trustees is implemented by <xref		regarding the selection of the 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		<t>This companion memo provides some background on the details
	of the past IETF Trust arrangements, explains the effect of		of the past IETF Trust arrangements, explains the effect of
	the rules in the founding documents during the transition to the new		the rules in the founding documents during the transition to the new
	arrangement, and provides a rationale for the update.</t>		arrangement, and provides a rationale for the update.</t>
	</section>		</section>
			<section anchor="background" numbered="true" toc="default">
	<section anchor="background" title="Background">		<name>Background</name>
	<t>The purpose of the IETF Trust is to acquire, hold, maintain,		<t>The purpose of the IETF Trust is to acquire, hold, maintain,
	and license certain existing and future intellectual property		and license certain existing and future intellectual property
	and other property used in connection with the administration of		and other property used in connection with the administration of
	the IETF <xref target="RFC4371"/>. The intellectual property is,		the IETF <xref target="RFC8714" format="default"/>. The intellectual prope rty is,
	for instance, rights that the IETF contributors grant for text		for instance, rights that the IETF contributors grant for text
	in RFCs and Internet-Drafts. The IETF Trust also manages		in RFCs and Internet-Drafts. The IETF Trust also manages
	trademarks such as "IETF" and domain names such as		trademarks such as "IETF" and domain names such as
	"ietf.org". The IETF Trust is also serving the broader Internet		"ietf.org". The IETF Trust is also serving the broader Internet
	community by holding domains and trademarks associated with		community by holding domains and trademarks associated with the Internet A
	Internet Assigned Numbers Authority (IANA) <xref		ssigned Numbers Authority (IANA) <xref target="RFC7979" format="default"/>.</t>
	target="RFC7979"/>.</t>
	<t>The IETF Trust is a legal entity, registered in the		<t>The IETF Trust is a legal entity, registered in the
	Commonwealth of Virginia <xref target="Trust-FD"/>.</t>		Commonwealth of Virginia <xref target="Trust-FD" format="default"/>.</t>
	<t>Previously, the members of the IAOC also served as ex officio		<t>Previously, the members of the IAOC also served as ex officio
	Trustees of the IETF Trust. The founding documents specify		Trustees of the IETF Trust. The founding documents specify
	persons eligible to become trustees as having to be then-current		persons eligible to become Trustees as having to be then-current
	members of the IAOC <xref target="Trust-FD"/>. The documents		members of the IAOC <xref target="Trust-FD" format="default"/>. The docum
			ents
	also specify that if for any reason there are fewer than three		also specify that if for any reason there are fewer than three
	individuals serving as Trustees, then the Internet Engineering		individuals serving as Trustees, then the Internet Engineering
	Steering Group (IESG), or the IESG's successor as the leadership		Steering Group (IESG), or the IESG's successor as the leadership
	of the IETF, shall appoint one or more individuals to serve in a		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>		temporary capacity as Trustee(s) until eligible persons can be found.</t>
			<!-- [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).
	<t>In the previous system there were eight IAOC members. Two were		In the previous system, there were eight IAOC members. Two were
	named by the IETF Nominating Committee (NomCom), one by the		named by the IETF Nominating Committee (NomCom), one by the Internet
	IESG, one by the Internet Architecture Board (IAB), and one by		Engineering Steering Group (IESG), one by the Internet Architecture
	the Internet Society (ISOC) Board of Trustees. In addition, there		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,		were three ex officio members via their roles as IETF Chair, ISOC CEO,
	and IAB Chair. In addition, the IETF Administrative Director (IAD)		and IAB Chair. In addition, the IETF Administrative Director (IAD)
	served also as one of the trustees.</t>		served also as one of the Trustees.</t>
	</section>		</section>
			<section anchor="approach" numbered="true" toc="default">
	<section anchor="approach" title="General Approach">		<name>General Approach</name>
	<t>There were two basic approaches to resolving the issue with		<t>There were two basic approaches to resolving the issue with
	the trustees, when the IAOC ceased to exist. One could have imagined		the Trustees once the IAOC ceased to exist. One approach would be to
	merging all IETF Trust functions in the new IASA structure and		merge all IETF Trust functions in the new IASA structure and
	under the new legal entity. This memo advocated a second		under the new legal entity. However, this memo advocates a second
	approach where the IETF Trust is kept independent.</t>		approach where the IETF Trust is kept independent.</t>
			<t>The rationale for advocating the second approach is, in part,
	<t>The rationale for advocating the second approach is in part
	to minimize changes to the IETF Trust while the IETF's		to minimize changes to the IETF Trust while the IETF's
	administrative structure is undergoing major change. In		administrative structure is undergoing major change. In
	addition, the IETF Trust and other administrative IETF processes		addition, the IETF Trust and other administrative IETF processes
	are quite different. While very important, the IETF Trust is a		are quite different. While very important, the IETF Trust is a
	low-activity entity where changes are minimal and gradual, and		low-activity entity where changes are minimal and gradual, and
	there are no pressing issues.</t>		there are no pressing issues.</t>
	</section>		</section>
			<section anchor="selection" numbered="true" toc="default">
	<section anchor="selection" title="Changing the Way Trustees Are Selected">		<name>Changing the Way Trustees Are Selected</name>
			<t>When the Trustees were serving on both the IETF Trust and the
	<t>At the time when the trustees served on both the IETF Trust and the
	IAOC, many of the requirements for naming a particular group of		IAOC, many of the requirements for naming a particular group of
	people were driven by the IAOC's requirements. For the IETF		people were driven by the IAOC's requirements. For the IETF
	Trust in the new model, some of those arrangements were able to be		Trust in the new model, some of those arrangements were
	rethought, both in terms of the number and source of the		rethought, both in terms of the number and source of the
	trustees, as well as the desired qualifications and length of		Trustees, as well as the desired qualifications and length of
	terms.</t>		terms.</t>
			<t>Several options were possible, of course.
	<t>Several options were possible, of course. A newly designed		A newly designed selection process could have been devised, but in this
	naming process could have been devised. The argument here is for a relativ		document we argue for limited change based largely on the fact that a) the IE
	ely		TF
	limited change, however, largely on the basis of the IETF Trust		Trust arrangements worked generally well, b) the expected time commitment
	arrangements generally working well, and on the relatively modest		is expected to be modest, and c) the assets need very careful management.</t>
	expected time commitments combined with the need for very careful		<t>As a result, a smaller group of Trustees appeared sufficient.</t>
	management of the assets.</t>		<t>In addition, the terms set for the
			Trustees selected from the IETF community could be longer than
	<t>As a result, a smaller group of trustees appeared sufficient.</t>		the two-year period typical of other IETF bodies.</t>
	<t>In addition, the terms for the
	trustees selected from the IETF community could be set to longer than
	the two year period typical of other IETF bodies.</t>
	<t>One could have continued the practice of having the chairs and CEOs		<t>One could have continued the practice of having the chairs and CEOs
	from IETF, IAB, and Internet Society be trustees as well, but		from the IETF, IAB, and Internet Society be Trustees as well, but
	this may not be necessary. In general, the tasks of the IETF		this may not be necessary. In general, the tasks of the IETF
	Trust are well defined, and while there is a need for		Trust are well defined, and while there is a need for
	coordination, it does not need to be at the level of chairs or		coordination, it does not need to be at the level of chairs or
	CEOs.</t>		CEOs.</t>
			<t>Given all this, one approach was to have Trustees appointed
	<t>Given all this, one approach was to have trustees appointed		by the NomCom, the IESG, and the ISOC Board of Trustees. (One might also
	by the NomCom, IESG, and ISOC Board of Trustees. (One might also
	have considered the IETF Administration LLC legal entity instead		have considered the IETF Administration LLC legal entity instead
	of the Internet Society for this role. But the Internet Society		of the Internet Society for this role, but the Internet Society
	is perhaps more suitable for the role, given their focus on the		is perhaps more suitable for the role given their focus on the
	broad use of the IETF Trust assets and not merely administrative		broad use of the IETF Trust assets and not merely administrative
	aspects).</t>		aspects.)</t>
			<t>If the same principles used for previous appointments continued to be
	<t>If the same principles would continue to be used as were used		used, then appointments performed by the NomCom would need to be
	in previous appointments, then appointments performed by the		confirmed by another entity. This could be, for instance, either the
	NomCom would need to be confirmed by another entity, which could		IESG or the IAB. The IESG had previously been the confirming body for
	be, for instance, either the IESG or the IAB. The IESG had		the IAOC, so it has been retained in that role for the Trustees.</t>
	previously been the confirming body for the IAOC, so it has been
	retained in that role for the trustees.</t>
	</section>		</section>
			<section anchor="transition" numbered="true" toc="default">
	<section anchor="transition" title="Transition">		<name>Transition</name>
			<t>When the new entity for the IETF Administration LLC was set up,
	<t>When the new entity for IETF Administration LLC was set up,
	the IAOC was expected to be discontinued soon		the IAOC was expected to be discontinued soon
	thereafter. Fortunately, there was no pressing need to change		thereafter. Fortunately, there was no pressing need to change
	all the components of the IAOC and its dependent organizations		all the components of the IAOC and its dependent organizations
	at the same time. As discussed above (<xref		at the same time. As discussed in <xref target="background" format="defaul
	target="background"/>), the IESG holds the ability to continue		t"/>, the IESG holds the ability to continue
	to name trustees. And once the updated procedures were in place,		to name Trustees. Once the updated procedures were in place,
	the IETF Trust had its management nominated in the usual manner,		the IETF Trust had its management nominated in the usual manner,
	and the exceptional IESG process was no longer needed.</t>		and the IESG's exception process was no longer needed.</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 title="IANA Considerations">
	<t>This memo requests no action from IANA.</t>
	</section>		</section>
			<section numbered="true" toc="default">
	<section anchor="ack" title="Acknowledgements">		<name>IANA Considerations</name>
			<t>This document has no IANA actions.</t>
	<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>
	</section>		</section>
	</middle>		</middle>
	<back>		<back>
			<references>
			<name>References</name>
			<references>
			<name>Normative References</name>
			<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
			nce.RFC.4071.xml"/>
			<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
			nce.RFC.4371.xml"/>
			</references>
	<references title="Normative References">		<references>
	&RFC4071;		<name>Informative References</name>
	&RFC4371;		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
	</references>		ence.RFC.7979.xml"/>
			<!-- draft-ietf-iasa2-trust-update-02: I-D exists -->
	<references title="Informative References">		<reference anchor="RFC8714" target="https://rfc-editor.org/info/rfc8714"
			>
	&RFC7979;		<front>
	&I-D.ietf-iasa2-struct;		<title>Update to the Process for Selection of Trustees for the
			IETF Trust</title>
	<reference anchor='I-D.ietf-iasa2-trust-update'>		<author initials="J." surname="Arkko">
	<front>		<organization/>
	<title>Update to the Selection of Trustees for the IETF Trust</title>		</author>
			<author initials="T." surname="Hardie" >
	<author initials='J' surname='Arkko' fullname='Jari Arkko'>		<organization/>
	<organization />		</author>
	</author>		<date month="January" year="2020"/>
			</front>
	<author initials='T' surname='Hardie' fullname='Ted Hardie'>		<seriesInfo name="BCP" value="101"/>
	<organization />		<seriesInfo name="RFC" value="8715"/>
	</author>		<seriesInfo name="DOI" value="10.17487/RFC8715"/>
			</reference>
	<date month='September' year='2018' />
	</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-trus
	t-update-00.txt' />
	</reference>
	<reference anchor="Trust-FD">		<reference anchor="Trust-FD" target="https://trustee.ietf.org/founding-d
	<front>		ocuments.html">
	<title>Founding Documents</title>		<front>
	<author surname="IETF Trust"></author>		<title>Founding Documents</title>
	<date month='February' year='2014 (https://trustee.ietf.org/founding-do		<author>
	cuments.html)'/>		<organization>IETF Trust</organization>
	</front>		</author>
	<format type='HTML'		</front>
	target='https://trustee.ietf.org/founding-documents.html'/>		</reference>
	</reference>
			<!-- draft-ietf-iasa2-struct-06: I-D expired Replaced by draft-ietf-iasa2-rfc407
			1bis -->
			<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 initials="J." surname="Hall">
			<organization/>
			</author>
			<author initials="J." surname="Livingood">
			<organization/>
			</author>
			<date month="January" year="2020"/>
			</front>
			<seriesInfo name="BCP" value="101"/>
			<seriesInfo name="RFC" value="8711"/>
			<seriesInfo name="DOI" value="10.17487/RFC8711"/>
			</reference>
			</references>
	</references>		</references>
			<section anchor="ack" numbered="false" toc="default">
	<section anchor="changes" title="Changes from Previous Versions">		<name>Acknowledgements</name>
			<t>The author would like to thank other members of the earlier
	<t>RFC Editor: Please remove this section upon publication.</t>		IASA 2.0 design team: <contact fullname="Brian Haberman"/>, <contact fulln
			ame="Eric Rescorla"/>,
	<t>The version draft-ietf-iasa2-trust-rationale-03.txt made		<contact fullname="Jason Livingood"/>, <contact fullname="Joe Hall"/>, and
	some editorial corrections.</t>		<contact fullname="Leslie Daigle"/>. The author would
			also like to thank <contact fullname="Alissa Cooper"/>, <contact
	<t>The version draft-ietf-iasa2-trust-rationale-02.txt made		fullname="Ted Hardie"/>, <contact fullname="Andrew Sullivan"/>,
	some editorial corrections.</t>		<contact fullname="Brian Carpenter"/>, <contact fullname="Lucy Lynch"/>, a
			nd
	<t>The version draft-ietf-iasa2-trust-rationale-01.txt includes		<contact fullname="John Levine"/> for interesting
	changes relating to last call comments. The changes are 1)		discussions in this problem space, and <contact fullname="Adrian Farrel"/>
	indication of why this document is being published 2) updates to		,
	references, 3) the addition of empty security and IANA		<contact fullname="Tero Kivinen"/>, <contact fullname="Russ Housley"/>,
	consideration sections, 4) editorial changes necessary for a		<contact fullname="Benjamin Kaduk"/>, <contact fullname="Adam Roach"/>,
	document that is also read later, and not just used in		and <contact fullname="Meral Shirazipour"/> for careful review.</t>
	discussions at this time.</t>
	<t>The version draft-ietf-iasa2-trust-rationale-00.txt includes
	only editorial and language updates.</t>
	<t>The version draft-arkko-iasa2-trust-rationale-00.txt was the
	initial version.</t>
	</section>		</section>
	</back>		</back>
	</rfc>		</rfc>
End of changes. 53 change blocks.
	234 lines changed or deleted		188 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/