idnits 2.17.1 draft-ietf-iasa2-trust-rationale-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 7, 2018) is 2052 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC7437' is defined on line 213, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-iasa2-trust-update' is defined on line 227, but no explicit reference was found in the text == Unused Reference: 'RFC5378' is defined on line 232, but no explicit reference was found in the text ** Obsolete normative reference: RFC 4071 (Obsoleted by RFC 8711) ** Obsolete normative reference: RFC 4371 (Obsoleted by RFC 8714) ** Obsolete normative reference: RFC 7437 (Obsoleted by RFC 8713) == Outdated reference: A later version (-03) exists of draft-ietf-iasa2-trust-update-00 Summary: 5 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force J. Arkko 3 Internet-Draft Ericsson 4 Intended status: Informational September 7, 2018 5 Expires: March 11, 2019 7 Discussion of the IASA 2.0 Changes as They Relate to the IETF Trust 8 draft-ietf-iasa2-trust-rationale-00 10 Abstract 12 The IASA 2.0 changes will have an impact on the IETF Trust because 13 members of the IET Administrative Oversight Committee (IAOC) IAOC, 14 which is being phased out, have served as Trustees of the IETF Trust. 15 This discussion document provides background on the current IETF 16 Trust arrangements, explains the effect of the rules in the founding 17 documents during a transition to a new arrangement, and provides a 18 rationale for the update. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on March 11, 2019. 37 Copyright Notice 39 Copyright (c) 2018 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 2 56 3. General Approach . . . . . . . . . . . . . . . . . . . . . . 3 57 4. Changing the Way Trustees Are Selected . . . . . . . . . . . 3 58 5. Transition . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 60 7. Changes from Previous Versions . . . . . . . . . . . . . . . 5 61 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 62 8.1. Normative References . . . . . . . . . . . . . . . . . . 5 63 8.2. Informative References . . . . . . . . . . . . . . . . . 5 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 66 1. Introduction 68 The IASA 2.0 changes will have an impact on the IETF Trust [RFC4071] 69 [RFC4371] [I-D.hall-iasa2-struct]. This is because members of the 70 IETF's Internet Administrative Oversight Committee (IAOC), which is 71 being phased out, have served as Trustees of the IETF Trust. A 72 proposal for a minimal change regarding this has been provided 73 separately in draft-ietf-iasa2-trust-update. 75 This companion memo provides some background on the details of the 76 current IETF Trust arrangements, explains the effect of the rules in 77 the founding documents during a transition to a new arrangement, and 78 provides a rationale for the update. 80 This memo is provided only for discussion. There is no intention to 81 publish this memo as an RFC. 83 2. Background 85 The purpose of the Internet Engineering Task Force (IETF) Trust is to 86 acquire, hold, maintain, and license certain existing and future 87 intellectual property and other property used in connection with the 88 administration of the IETF [RFC4371]. The intellectual property is, 89 for instance, rights that the IETF contributors grant for text in 90 RFCs and Internet Drafts. The IETF Trust also manages trademarks 91 such as "IETF" and domain names such as "ietf.org". The IETF Trust 92 is also serving the broader Internet community by holding domains and 93 trademarks associated with Internet Assigned Numbers Authority (IANA) 94 [RFC7979]. 96 The IETF Trust is a legal entity, registered in the Commonwealth of 97 Virginia [Trust-FD]. 99 Currently, the members of the IAOC also serve as ex officio Trustees 100 of the IETF Trust. The founding documents specify persons eligible 101 to become trustees as having to be then-current members of the IAOC 102 [Trust-FD]. The documents also specify that if for any reason there 103 are fewer than three individuals serving as Trustees, then the 104 Internet Engineering Steering Group (IESG), or the IESG's successor 105 as the leadership of the IETF, shall appoint one or more individuals 106 to serve in a temporary capacity as Trustee(s) until eligible persons 107 can be found. 109 In the current system there are eight IAOC members. Two are named by 110 the IETF Nominating Committee (NomCom), one by the IESG, one by the 111 Internet Architecture Board (IAB), and one by the Internet Society 112 (ISOC) Board of Trustees. In addition, there are three ex-officio 113 members via their roles as IETF Chair, ISOC CEO, and IAB Chair. In 114 addition, the IETF Administrative Director (IAD) serves also as one 115 of the trustees. 117 3. General Approach 119 There are two basic approaches to resolving the issue with the 120 trustees, if the IAOC ceases to exist. One could imagine merging all 121 IETF Trust functions in the new IASA structure and under the planned 122 new legal entity. This memo advocates a second approach where the 123 IETF Trust is kept independent. 125 The rationale for advocating the second approach is in part to 126 minimize changes to the IETF Trust while the IETF's administrative 127 structure is undergoing major change. In addition, the IETF Trust 128 and other administrative IETF process are quite different. While 129 very important, the IETF Trust is a low activity entity where changes 130 are minimal and gradual, and there are no pressing issues. 132 4. Changing the Way Trustees Are Selected 134 At the time when the trustees served on both the IETF Trust and the 135 IAOC, many of the requirements for naming a particular group of 136 people were driven by the IAOC's requirements. For the IETF Trust in 137 the new model, some of those arrangements can be rethought, both in 138 terms of the number and source of the trustees, as well as the 139 desired qualifications and length of terms. 141 Several options are possible, of course. A newly designed naming 142 process could be devised. This memo argues for relatively limited 143 change, however, largely on the basis of the IETF Trust arrangements 144 generally working well, and on the relatively modest expected time 145 commitments combined with the need for very careful management of the 146 assets. 148 As a result, a smaller group of trustees appears sufficient. 150 In addition, the terms for the trustees selected from the IETF 151 community could be set to longer than the two year period typical of 152 other IETF bodies. 154 One could continue the practice of having the chairs and CEOs from 155 IETF, IAB, and Internet Society be trustees as well, but this may not 156 be necessary. In general, the tasks of the IETF Trust are well 157 defined, and while there is a need for coordination, it does not need 158 to be at the level of chairs or CEOs. 160 Given all this, one approach is to have trustees appointed by the 161 NomCom, IESG, and ISOC Board of Trustees, or even the new IETF 162 Administration LLC legal entity (but he Internet Society is perhaps 163 more focused on the broad use of the IETF Trust assets and not merely 164 administrative aspects). 166 If the same principles continue to be used as are used in today's 167 appointments, then appointments performed by the NomCom need to be 168 confirmed by another entity, which could be, for instance, either the 169 IESG or the IAB. 171 5. Transition 173 When new entity for IETF Administration LLC is set up, soon 174 thereafter the IAOC will be discontinued. Fortunately, there's no 175 pressing need to change all the components at the same time. As 176 discussed above (Section 2), the IESG holds the ability to continue 177 to name trustees. Once the changes suggested in Section 4 are in 178 place, the IETF Trust will have management nominated in the usual 179 manner, and the exceptional IESG process is no longer needed. 181 6. Acknowledgements 183 The author would like to thank other members of the earlier IASA 2.0 184 design team who were Brian Haberman, Eric Rescorla, Jason Livingood, 185 Joe Hall, and Leslie Daigle. The authors would also like to thank 186 Alissa Cooper, Ted Hardie, Andrew Sullivan, Brian Carpenter, Lucy 187 Lynch, and John Levine for interesting discussions in this problem 188 space. 190 7. Changes from Previous Versions 192 RFC Editor: Please remove this section upon publication. 194 The version draft-ietf-iasa2-trust-rationale-00.txt includes only 195 editorial and language updates. 197 The version draft-arkko-iasa2-trust-rationale-00.txt was the initial 198 version. 200 8. References 202 8.1. Normative References 204 [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the 205 IETF Administrative Support Activity (IASA)", BCP 101, 206 RFC 4071, DOI 10.17487/RFC4071, April 2005, 207 . 209 [RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for 210 IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371, 211 January 2006, . 213 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 214 Confirmation, and Recall Process: Operation of the 215 Nominating and Recall Committees", BCP 10, RFC 7437, 216 DOI 10.17487/RFC7437, January 2015, . 219 8.2. Informative References 221 [I-D.hall-iasa2-struct] 222 Haberman, B., Hall, J., and J. Livingood, "Proposed 223 Structure of the IETF Administrative Support Activity 224 (IASA), Version 2.0 (for Discussion)", draft-hall- 225 iasa2-struct-04 (work in progress), June 2018. 227 [I-D.ietf-iasa2-trust-update] 228 Arkko, J. and T. Hardie, "Update to the Selection of 229 Trustees for the IETF Trust", draft-ietf-iasa2-trust- 230 update-00 (work in progress), September 2018. 232 [RFC5378] Bradner, S., Ed. and J. Contreras, Ed., "Rights 233 Contributors Provide to the IETF Trust", BCP 78, RFC 5378, 234 DOI 10.17487/RFC5378, November 2008, . 237 [RFC7979] Lear, E., Ed. and R. Housley, Ed., "Response to the IANA 238 Stewardship Transition Coordination Group (ICG) Request 239 for Proposals on the IANA Protocol Parameters Registries", 240 RFC 7979, DOI 10.17487/RFC7979, August 2016, 241 . 243 [Trust-FD] 244 IETF Trust, , "Founding Documents", February 2014 245 (https://trustee.ietf.org/founding-documents.html). 247 Author's Address 249 Jari Arkko 250 Ericsson 251 Kauniainen 02700 252 Finland 254 Email: jari.arkko@piuha.net