idnits 2.17.1 draft-ietf-iasa2-trust-rationale-03.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 abstract seems to contain references ([I-D.ietf-iasa2-trust-update]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 11, 2018) is 2024 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 4071 (Obsoleted by RFC 8711) ** Obsolete normative reference: RFC 4371 (Obsoleted by RFC 8714) == Outdated reference: A later version (-03) exists of draft-ietf-iasa2-trust-update-00 Summary: 3 errors (**), 0 flaws (~~), 2 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 October 11, 2018 5 Expires: April 14, 2019 7 Discussion of the IASA 2.0 Changes as They Relate to the IETF Trust 8 draft-ietf-iasa2-trust-rationale-03 10 Abstract 12 This document is published to capture the rationale for the changes 13 introduced in RFC NNNN (RFC Editor: please replace NNNN with the RFC 14 number of [I-D.ietf-iasa2-trust-update]), Update to the Process for 15 Selection of Trustees for the IETF Trust. 17 At the time RFC NNNN was published, IETF administrative structure 18 changes ("IASA 2.0") had an impact on the IETF Trust because members 19 of the IETF Administrative Oversight Committee (IAOC), which was 20 being phased out, had served as Trustees of the IETF Trust. This 21 document provides background on the past IETF Trust arrangements, 22 explains the effect of the rules in the founding documents during the 23 transition to the new arrangement, and provides a rationale for the 24 update. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on April 14, 2019. 43 Copyright Notice 45 Copyright (c) 2018 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 3. General Approach . . . . . . . . . . . . . . . . . . . . . . 3 63 4. Changing the Way Trustees Are Selected . . . . . . . . . . . 4 64 5. Transition . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 66 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 67 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 68 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 69 9.1. Normative References . . . . . . . . . . . . . . . . . . 5 70 9.2. Informative References . . . . . . . . . . . . . . . . . 5 71 Appendix A. Changes from Previous Versions . . . . . . . . . . . 6 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 74 1. Introduction 76 This document is published to capture the rationale for the changes 77 introduced in [I-D.ietf-iasa2-trust-update]. 79 At the time [I-D.ietf-iasa2-trust-update] was published, IETF 80 administrative structure changes ("IASA 2.0") had an impact on the 81 IETF Trust [RFC4071] [RFC4371] [I-D.ietf-iasa2-struct]. This is 82 because members of the IETF Administrative Oversight Committee 83 (IAOC), which was being phased out, had served as Trustees of the 84 IETF Trust. A minimal change regarding the selection of the trustees 85 is implemented by [I-D.ietf-iasa2-trust-update]. 87 This companion memo provides some background on the details of the 88 past IETF Trust arrangements, explains the effect of the rules in the 89 founding documents during the transition to the new arrangement, and 90 provides a rationale for the update. 92 2. Background 94 The purpose of the IETF Trust is to acquire, hold, maintain, and 95 license certain existing and future intellectual property and other 96 property used in connection with the administration of the IETF 97 [RFC4371]. The intellectual property is, for instance, rights that 98 the IETF contributors grant for text in RFCs and Internet-Drafts. 99 The IETF Trust also manages trademarks such as "IETF" and domain 100 names such as "ietf.org". The IETF Trust is also serving the broader 101 Internet community by holding domains and trademarks associated with 102 Internet Assigned Numbers Authority (IANA) [RFC7979]. 104 The IETF Trust is a legal entity, registered in the Commonwealth of 105 Virginia [Trust-FD]. 107 Previously, the members of the IAOC also served as ex officio 108 Trustees of the IETF Trust. The founding documents specify persons 109 eligible to become trustees as having to be then-current members of 110 the IAOC [Trust-FD]. The documents also specify that if for any 111 reason there are fewer than three individuals serving as Trustees, 112 then the Internet Engineering Steering Group (IESG), or the IESG's 113 successor as the leadership of the IETF, shall appoint one or more 114 individuals to serve in a temporary capacity as Trustee(s) until 115 eligible persons can be found. 117 In the previous system there were eight IAOC members. Two were named 118 by the IETF Nominating Committee (NomCom), one by the IESG, one by 119 the Internet Architecture Board (IAB), and one by the Internet 120 Society (ISOC) Board of Trustees. In addition, there were three ex 121 officio members via their roles as IETF Chair, ISOC CEO, and IAB 122 Chair. In addition, the IETF Administrative Director (IAD) served 123 also as one of the trustees. 125 3. General Approach 127 There were two basic approaches to resolving the issue with the 128 trustees, when the IAOC ceased to exist. One could have imagined 129 merging all IETF Trust functions in the new IASA structure and under 130 the new legal entity. This memo advocated a second approach where 131 the IETF Trust is kept independent. 133 The rationale for advocating the second approach is in part to 134 minimize changes to the IETF Trust while the IETF's administrative 135 structure is undergoing major change. In addition, the IETF Trust 136 and other administrative IETF processes are quite different. While 137 very important, the IETF Trust is a low-activity entity where changes 138 are minimal and gradual, and there are no pressing issues. 140 4. Changing the Way Trustees Are Selected 142 At the time when the trustees served on both the IETF Trust and the 143 IAOC, many of the requirements for naming a particular group of 144 people were driven by the IAOC's requirements. For the IETF Trust in 145 the new model, some of those arrangements were able to be rethought, 146 both in terms of the number and source of the trustees, as well as 147 the desired qualifications and length of terms. 149 Several options were possible, of course. A newly designed naming 150 process could have been devised. The argument here is for a 151 relatively limited change, however, largely on the basis of the IETF 152 Trust arrangements generally working well, and on the relatively 153 modest expected time commitments combined with the need for very 154 careful management of the assets. 156 As a result, a smaller group of trustees appeared sufficient. 158 In addition, the terms for the trustees selected from the IETF 159 community could be set to longer than the two year period typical of 160 other IETF bodies. 162 One could have continued the practice of having the chairs and CEOs 163 from IETF, IAB, and Internet Society be trustees as well, but this 164 may not be necessary. In general, the tasks of the IETF Trust are 165 well defined, and while there is a need for coordination, it does not 166 need to be at the level of chairs or CEOs. 168 Given all this, one approach was to have trustees appointed by the 169 NomCom, IESG, and ISOC Board of Trustees. (One might also have 170 considered the IETF Administration LLC legal entity instead of the 171 Internet Society for this role. But the Internet Society is perhaps 172 more suitable for the role, given their focus on the broad use of the 173 IETF Trust assets and not merely administrative aspects). 175 If the same principles would continue to be used as were used in 176 previous appointments, then appointments performed by the NomCom 177 would need to be confirmed by another entity, which could be, for 178 instance, either the IESG or the IAB. The IESG had previously been 179 the confirming body for the IAOC, so it has been retained in that 180 role for the trustees. 182 5. Transition 184 When the new entity for IETF Administration LLC was set up, the IAOC 185 was expected to be discontinued soon thereafter. Fortunately, there 186 was no pressing need to change all the components of the IAOC and its 187 dependent organizations at the same time. As discussed above 188 (Section 2), the IESG holds the ability to continue to name trustees. 189 And once the updated procedures were in place, the IETF Trust had its 190 management nominated in the usual manner, and the exceptional IESG 191 process was no longer needed. 193 6. Security Considerations 195 This memo has no security implications for the Internet. 197 7. IANA Considerations 199 This memo requests no action from IANA. 201 8. Acknowledgements 203 The author would like to thank other members of the earlier IASA 2.0 204 design team who were Brian Haberman, Eric Rescorla, Jason Livingood, 205 Joe Hall, and Leslie Daigle. The authors would also like to thank 206 Alissa Cooper, Ted Hardie, Andrew Sullivan, Brian Carpenter, Lucy 207 Lynch, and John Levine for interesting discussions in this problem 208 space, and Adrian Farrel, Tero Kivinen, Russ Housley, Benjamin Kaduk, 209 Adam Roach and Meral Shirazipour for careful review. 211 9. References 213 9.1. Normative References 215 [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the 216 IETF Administrative Support Activity (IASA)", BCP 101, 217 RFC 4071, DOI 10.17487/RFC4071, April 2005, 218 . 220 [RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for 221 IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371, 222 January 2006, . 224 9.2. Informative References 226 [I-D.ietf-iasa2-struct] 227 Haberman, B., Hall, J., and J. Livingood, "Record of 228 Proposed Structure of the IETF Administrative Support 229 Activity (IASA), Version 2.0", draft-ietf-iasa2-struct-06 230 (work in progress), September 2018. 232 [I-D.ietf-iasa2-trust-update] 233 Arkko, J. and T. Hardie, "Update to the Selection of 234 Trustees for the IETF Trust", draft-ietf-iasa2-trust- 235 update-00 (work in progress), September 2018. 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 Appendix A. Changes from Previous Versions 249 RFC Editor: Please remove this section upon publication. 251 The version draft-ietf-iasa2-trust-rationale-03.txt made some 252 editorial corrections. 254 The version draft-ietf-iasa2-trust-rationale-02.txt made some 255 editorial corrections. 257 The version draft-ietf-iasa2-trust-rationale-01.txt includes changes 258 relating to last call comments. The changes are 1) indication of why 259 this document is being published 2) updates to references, 3) the 260 addition of empty security and IANA consideration sections, 4) 261 editorial changes necessary for a document that is also read later, 262 and not just used in discussions at this time. 264 The version draft-ietf-iasa2-trust-rationale-00.txt includes only 265 editorial and language updates. 267 The version draft-arkko-iasa2-trust-rationale-00.txt was the initial 268 version. 270 Author's Address 272 Jari Arkko 273 Ericsson 274 Kauniainen 02700 275 Finland 277 Email: jari.arkko@piuha.net