draft-ietf-iasa2-trust-rationale-02.txt		draft-ietf-iasa2-trust-rationale.txt
	Internet Engineering Task Force J. Arkko		Internet Engineering Task Force J. Arkko
	Internet-Draft Ericsson		Internet-Draft Ericsson
	Intended status: Informational October 8, 2018		Intended status: Informational October 11, 2018
	Expires: April 11, 2019		Expires: April 14, 2019
	Discussion of the IASA 2.0 Changes as They Relate to the IETF Trust		Discussion of the IASA 2.0 Changes as They Relate to the IETF Trust
	draft-ietf-iasa2-trust-rationale-02		draft-ietf-iasa2-trust-rationale-03
	Abstract		Abstract
	This document is published to capture the rationale for the changes		This document is published to capture the rationale for the changes
	introduced in RFC NNNN (RFC Editor: please replace NNNN with the RFC		introduced in RFC NNNN (RFC Editor: please replace NNNN with the RFC
	number of [I-D.ietf-iasa2-trust-update]), Update to the Process for		number of [I-D.ietf-iasa2-trust-update]), Update to the Process for
	Selection of Trustees for the IETF Trust.		Selection of Trustees for the IETF Trust.
	At the time RFC NNNN was published, IETF administrative structure		At the time RFC NNNN was published, IETF administrative structure
	changes ("IASA 2.0") had an impact on the IETF Trust because members		changes ("IASA 2.0") had an impact on the IETF Trust because members
	of the IETF Administrative Oversight Committee (IAOC) IAOC, which was		of the IETF Administrative Oversight Committee (IAOC), which was
	being phased out, had served as Trustees of the IETF Trust. This		being phased out, had served as Trustees of the IETF Trust. This
	document provides background on the past IETF Trust arrangements,		document provides background on the past IETF Trust arrangements,
	explains the effect of the rules in the founding documents during the		explains the effect of the rules in the founding documents during the
	transition to the new arrangement, and provides a rationale for the		transition to the new arrangement, and provides a rationale for the
	update.		update.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	skipping to change at page 1, line 42		skipping to change at page 1, line 42
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on April 11, 2019.		This Internet-Draft will expire on April 14, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2018 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 4, line 34		skipping to change at page 4, line 34
	community could be set to longer than the two year period typical of		community could be set to longer than the two year period typical of
	other IETF bodies.		other IETF bodies.
	One could have continued the practice of having the chairs and CEOs		One could have continued the practice of having the chairs and CEOs
	from IETF, IAB, and Internet Society be trustees as well, but this		from IETF, IAB, and Internet Society be trustees as well, but this
	may not be necessary. In general, the tasks of the IETF Trust are		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		well defined, and while there is a need for coordination, it does not
	need to be at the level of chairs or CEOs.		need to be at the level of chairs or CEOs.
	Given all this, one approach was to have trustees appointed by the		Given all this, one approach was to have trustees appointed by the
	NomCom, IESG, and ISOC Board of Trustees, or even the new IETF		NomCom, IESG, and ISOC Board of Trustees. (One might also have
	Administration LLC legal entity (but the Internet Society is perhaps		considered the IETF Administration LLC legal entity instead of the
	more focused on the broad use of the IETF Trust assets and not merely		Internet Society for this role. But the Internet Society is perhaps
	administrative aspects).		more suitable for the role, given their focus on the broad use of the
			IETF Trust assets and not merely administrative aspects).
	If the same principles would continue to be used as were used in		If the same principles would continue to be used as were used in
	previous appointments, then appointments performed by the NomCom		previous appointments, then appointments performed by the NomCom
	would need to be confirmed by another entity, which could be, for		would need to be confirmed by another entity, which could be, for
	instance, either the IESG or the IAB. The IESG had previously been		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		the confirming body for the IAOC, so it has been retained in that
	role for the trustees.		role for the trustees.
	5. Transition		5. Transition
	When the new entity for IETF Administration LLC was set up, the IAOC		When the new entity for IETF Administration LLC was set up, the IAOC
	was expected to be discontinued soon thereafter. Fortunately, there		was expected to be discontinued soon thereafter. Fortunately, there
	was no pressing need to change all the components of the IAOC and its		was no pressing need to change all the components of the IAOC and its
	dependent organizations at the same time. As discussed above		dependent organizations at the same time. As discussed above
	(Section 2), the IESG holds the ability to continue to name trustees.		(Section 2), the IESG holds the ability to continue to name trustees.
			And once the updated procedures were in place, the IETF Trust had its
	And once the updated procedures were in place, the IETF Trust has its
	management nominated in the usual manner, and the exceptional IESG		management nominated in the usual manner, and the exceptional IESG
	process is no longer needed.		process was no longer needed.
	6. Security Considerations		6. Security Considerations
	This memo has no security implications for the Internet.		This memo has no security implications for the Internet.
	7. IANA Considerations		7. IANA Considerations
	This memo requests no action from IANA.		This memo requests no action from IANA.
	8. Acknowledgements		8. Acknowledgements
	The author would like to thank other members of the earlier IASA 2.0		The author would like to thank other members of the earlier IASA 2.0
	design team who were Brian Haberman, Eric Rescorla, Jason Livingood,		design team who were Brian Haberman, Eric Rescorla, Jason Livingood,
	Joe Hall, and Leslie Daigle. The authors would also like to thank		Joe Hall, and Leslie Daigle. The authors would also like to thank
	Alissa Cooper, Ted Hardie, Andrew Sullivan, Brian Carpenter, Lucy		Alissa Cooper, Ted Hardie, Andrew Sullivan, Brian Carpenter, Lucy
	Lynch, and John Levine for interesting discussions in this problem		Lynch, and John Levine for interesting discussions in this problem
	space, and Adrian Farrel, Tero Kivinen, Russ Housley, and Meral		space, and Adrian Farrel, Tero Kivinen, Russ Housley, Benjamin Kaduk,
	Shirazipour for careful review.		Adam Roach and Meral Shirazipour for careful review.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the		[RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the
	IETF Administrative Support Activity (IASA)", BCP 101,		IETF Administrative Support Activity (IASA)", BCP 101,
	RFC 4071, DOI 10.17487/RFC4071, April 2005,		RFC 4071, DOI 10.17487/RFC4071, April 2005,
	<https://www.rfc-editor.org/info/rfc4071>.		<https://www.rfc-editor.org/info/rfc4071>.
	skipping to change at page 6, line 19		skipping to change at page 6, line 19
	<https://www.rfc-editor.org/info/rfc7979>.		<https://www.rfc-editor.org/info/rfc7979>.
	[Trust-FD]		[Trust-FD]
	IETF Trust, , "Founding Documents", February 2014		IETF Trust, , "Founding Documents", February 2014
	(https://trustee.ietf.org/founding-documents.html).		(https://trustee.ietf.org/founding-documents.html).
	Appendix A. Changes from Previous Versions		Appendix A. Changes from Previous Versions
	RFC Editor: Please remove this section upon publication.		RFC Editor: Please remove this section upon publication.
			The version draft-ietf-iasa2-trust-rationale-03.txt made some
			editorial corrections.
	The version draft-ietf-iasa2-trust-rationale-02.txt made some		The version draft-ietf-iasa2-trust-rationale-02.txt made some
	editorial corrections.		editorial corrections.
	The version draft-ietf-iasa2-trust-rationale-01.txt includes changes		The version draft-ietf-iasa2-trust-rationale-01.txt includes changes
	relating to last call comments. The changes are 1) indication of why		relating to last call comments. The changes are 1) indication of why
	this document is being published 2) updates to references, 3) the		this document is being published 2) updates to references, 3) the
	addition of empty security and IANA consideration sections, 4)		addition of empty security and IANA consideration sections, 4)
	editorial changes necessary for a document that is also read later,		editorial changes necessary for a document that is also read later,
	and not just used in discussions at this time.		and not just used in discussions at this time.
End of changes. 9 change blocks.
	14 lines changed or deleted		17 lines changed or added
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/