draft-ietf-iasa2-trust-rationale-01.txt   draft-ietf-iasa2-trust-rationale-02.txt 
Internet Engineering Task Force J. Arkko Internet Engineering Task Force J. Arkko
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Informational October 5, 2018 Intended status: Informational October 8, 2018
Expires: April 8, 2019 Expires: April 11, 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-01 draft-ietf-iasa2-trust-rationale-02
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
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 8, 2019. This Internet-Draft will expire on April 11, 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 2, line 39 skipping to change at page 2, line 39
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
This document is published to capture the rationale for the changes This document is published to capture the rationale for the changes
introduced in [I-D.ietf-iasa2-trust-update]. introduced in [I-D.ietf-iasa2-trust-update].
At the time [I-D.ietf-iasa2-trust-update] was published, IETF At the time [I-D.ietf-iasa2-trust-update] was published, IETF
administrative structure changes ("IASA 2.0") had an impact on the administrative structure changes ("IASA 2.0") had an impact on the
IETF Trust [RFC4071] [RFC4371] [I-D.ietf-iasa2-struct]. This is IETF Trust [RFC4071] [RFC4371] [I-D.ietf-iasa2-struct]. This is
because members of the IETF's Internet Administrative Oversight because members of the IETF Administrative Oversight Committee
Committee (IAOC), which was being phased out, had served as Trustees (IAOC), which was being phased out, had served as Trustees of the
of the IETF Trust. A minimal change regarding the selection of the IETF Trust. A minimal change regarding the selection of the trustees
trustees is implemented by [I-D.ietf-iasa2-trust-update]. is implemented by [I-D.ietf-iasa2-trust-update].
This companion memo provides some background on the details of the This companion memo provides some background on the details of the
past IETF Trust arrangements, explains the effect of the rules in the past IETF Trust arrangements, explains the effect of the rules in the
founding documents during the transition to the new arrangement, and founding documents during the transition to the new arrangement, and
provides a rationale for the update. provides a rationale for the update.
2. Background 2. Background
The purpose of the Internet Engineering Task Force (IETF) Trust is to The purpose of the IETF Trust is to acquire, hold, maintain, and
acquire, hold, maintain, and license certain existing and future license certain existing and future intellectual property and other
intellectual property and other property used in connection with the property used in connection with the administration of the IETF
administration of the IETF [RFC4371]. The intellectual property is, [RFC4371]. The intellectual property is, for instance, rights that
for instance, rights that the IETF contributors grant for text in the IETF contributors grant for text in RFCs and Internet-Drafts.
RFCs and Internet-Drafts. The IETF Trust also manages trademarks The IETF Trust also manages trademarks such as "IETF" and domain
such as "IETF" and domain names such as "ietf.org". The IETF Trust names such as "ietf.org". The IETF Trust is also serving the broader
is also serving the broader Internet community by holding domains and Internet community by holding domains and trademarks associated with
trademarks associated with Internet Assigned Numbers Authority (IANA) Internet Assigned Numbers Authority (IANA) [RFC7979].
[RFC7979].
The IETF Trust is a legal entity, registered in the Commonwealth of The IETF Trust is a legal entity, registered in the Commonwealth of
Virginia [Trust-FD]. Virginia [Trust-FD].
Previously, the members of the IAOC also serve as ex officio Trustees Previously, the members of the IAOC also served as ex officio
of the IETF Trust. The founding documents specify persons eligible Trustees of the IETF Trust. The founding documents specify persons
to become trustees as having to be then-current members of the IAOC eligible to become trustees as having to be then-current members of
[Trust-FD]. The documents also specify that if for any reason there the IAOC [Trust-FD]. The documents also specify that if for any
are fewer than three individuals serving as Trustees, then the reason there are fewer than three individuals serving as Trustees,
Internet Engineering Steering Group (IESG), or the IESG's successor then the Internet Engineering Steering Group (IESG), or the IESG's
as the leadership of the IETF, shall appoint one or more individuals successor as the leadership of the IETF, shall appoint one or more
to serve in a temporary capacity as Trustee(s) until eligible persons individuals to serve in a temporary capacity as Trustee(s) until
can be found. eligible persons can be found.
In the previous system there were eight IAOC members. Two were named In the previous system there were eight IAOC members. Two were named
by the IETF Nominating Committee (NomCom), one by the IESG, one by by the IETF Nominating Committee (NomCom), one by the IESG, one by
the Internet Architecture Board (IAB), and one by the Internet the Internet Architecture Board (IAB), and one by the Internet
Society (ISOC) Board of Trustees. In addition, there were three ex- Society (ISOC) Board of Trustees. In addition, there were three ex
officio members via their roles as IETF Chair, ISOC CEO, and IAB officio members via their roles as IETF Chair, ISOC CEO, and IAB
Chair. In addition, the IETF Administrative Director (IAD) served Chair. In addition, the IETF Administrative Director (IAD) served
also as one of the trustees. also as one of the trustees.
3. General Approach 3. General Approach
There were two basic approaches to resolving the issue with the There were two basic approaches to resolving the issue with the
trustees, when the IAOC ceased to exist. One could imagine merging trustees, when the IAOC ceased to exist. One could have imagined
all IETF Trust functions in the new IASA structure and under the new merging all IETF Trust functions in the new IASA structure and under
legal entity. This memo advocated a second approach where the IETF the new legal entity. This memo advocated a second approach where
Trust is kept independent. the IETF Trust is kept independent.
The rationale for advocating the second approach is in part to The rationale for advocating the second approach is in part to
minimize changes to the IETF Trust while the IETF's administrative minimize changes to the IETF Trust while the IETF's administrative
structure is undergoing major change. In addition, the IETF Trust structure is undergoing major change. In addition, the IETF Trust
and other administrative IETF process are quite different. While and other administrative IETF processes are quite different. While
very important, the IETF Trust is a low activity entity where changes very important, the IETF Trust is a low-activity entity where changes
are minimal and gradual, and there are no pressing issues. are minimal and gradual, and there are no pressing issues.
4. Changing the Way Trustees Are Selected 4. Changing the Way Trustees Are Selected
At the time when the trustees served on both the IETF Trust and the 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 Trust in 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, the new model, some of those arrangements were able to be rethought,
both in terms of the number and source of the trustees, as well as both in terms of the number and source of the trustees, as well as
the desired qualifications and length of terms. the desired qualifications and length of terms.
skipping to change at page 4, line 42 skipping to change at page 4, line 42
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, or even the new IETF
Administration LLC legal entity (but the Internet Society is perhaps Administration LLC legal entity (but the Internet Society is perhaps
more focused on the broad use of the IETF Trust assets and not merely more focused on the broad use of the IETF Trust assets and not merely
administrative aspects). 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. 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.
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 at the same time. was no pressing need to change all the components of the IAOC and its
As discussed above (Section 2), the IESG holds the ability to dependent organizations at the same time. As discussed above
continue to name trustees. And once the updated procedures were in (Section 2), the IESG holds the ability to continue to name trustees.
place, the IETF Trust has its management nominated in the usual
manner, and the exceptional IESG process is no longer needed. And once the updated procedures were in place, the IETF Trust has its
management nominated in the usual manner, and the exceptional IESG
process is 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 Tero Kivinen, Russ Housley, and Meral Shirazipour for space, and Adrian Farrel, Tero Kivinen, Russ Housley, and Meral
careful review. 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>.
[RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for [RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for
IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371, IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371,
January 2006, <https://www.rfc-editor.org/info/rfc4371>. January 2006, <https://www.rfc-editor.org/info/rfc4371>.
[RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection,
Confirmation, and Recall Process: Operation of the
Nominating and Recall Committees", BCP 10, RFC 7437,
DOI 10.17487/RFC7437, January 2015, <https://www.rfc-
editor.org/info/rfc7437>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-iasa2-struct] [I-D.ietf-iasa2-struct]
Haberman, B., Hall, J., and J. Livingood, "Record of Haberman, B., Hall, J., and J. Livingood, "Record of
Proposed Structure of the IETF Administrative Support Proposed Structure of the IETF Administrative Support
Activity (IASA), Version 2.0", draft-ietf-iasa2-struct-06 Activity (IASA), Version 2.0", draft-ietf-iasa2-struct-06
(work in progress), September 2018. (work in progress), September 2018.
[I-D.ietf-iasa2-trust-update] [I-D.ietf-iasa2-trust-update]
Arkko, J. and T. Hardie, "Update to the Selection of Arkko, J. and T. Hardie, "Update to the Selection of
Trustees for the IETF Trust", draft-ietf-iasa2-trust- Trustees for the IETF Trust", draft-ietf-iasa2-trust-
update-00 (work in progress), September 2018. update-00 (work in progress), September 2018.
[RFC5378] Bradner, S., Ed. and J. Contreras, Ed., "Rights
Contributors Provide to the IETF Trust", BCP 78, RFC 5378,
DOI 10.17487/RFC5378, November 2008, <https://www.rfc-
editor.org/info/rfc5378>.
[RFC7979] Lear, E., Ed. and R. Housley, Ed., "Response to the IANA [RFC7979] Lear, E., Ed. and R. Housley, Ed., "Response to the IANA
Stewardship Transition Coordination Group (ICG) Request Stewardship Transition Coordination Group (ICG) Request
for Proposals on the IANA Protocol Parameters Registries", for Proposals on the IANA Protocol Parameters Registries",
RFC 7979, DOI 10.17487/RFC7979, August 2016, RFC 7979, DOI 10.17487/RFC7979, August 2016,
<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-02.txt made some
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.
The version draft-ietf-iasa2-trust-rationale-00.txt includes only The version draft-ietf-iasa2-trust-rationale-00.txt includes only
editorial and language updates. editorial and language updates.
 End of changes. 15 change blocks. 
53 lines changed or deleted 48 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/