idnits 2.17.1 draft-ietf-iasa2-trust-update-02.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC4071, updated by this document, for RFC5378 checks: 2004-11-18) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 11, 2018) is 2022 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** 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-rationale-00 Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). 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 Updates: 4071,4371 (if approved) T. Hardie 5 Intended status: Best Current Practice October 11, 2018 6 Expires: April 14, 2019 8 Update to the Process for Selection of Trustees for the IETF Trust 9 draft-ietf-iasa2-trust-update-02 11 Abstract 13 This memo updates the process for selection of trustees for the IETF 14 Trust. Previously, the Internet Administrative Oversight Committee 15 (IAOC) members also acted as trustees, but the IAOC has been 16 eliminated as part of an update of the structure of the Internet 17 Administrative Support Activity (IASA). This memo specifies that the 18 trustees shall be selected separately. 20 This memo updates RFCs 4071 and 4371 with regards to the selection of 21 trustees. All other aspects of the IETF Trust remain as they are 22 today. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on April 14, 2019. 41 Copyright Notice 43 Copyright (c) 2018 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Selection of Trustees . . . . . . . . . . . . . . . . . . . . 2 60 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 61 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 62 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 63 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 65 6.2. Informative References . . . . . . . . . . . . . . . . . 4 66 Appendix A. Changes from Previous Versions . . . . . . . . . . . 4 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 69 1. Introduction 71 This memo updates the process for selection of trustees for the IETF 72 Trust. Previously, the Internet Administrative Oversight Committee 73 (IAOC) members also acted as trustees, but the IAOC has been 74 eliminated as part of an update of the structure of the Internet 75 Administrative Support Activity (IASA). This memo specifies that the 76 trustees shall be selected separately. 78 This memo updates RFCs 4071 and 4371 with regards to the selection of 79 trustees. All other aspects of the IETF Trust remain as they are 80 today. 82 For a discussion of why this change is needed and a rationale for 83 these specific changes, see [I-D.ietf-iasa2-trust-rationale]. 85 2. Selection of Trustees 87 This document revises the original Trustee selection procedures 88 defined in [RFC4071] and [RFC4371], to eliminate the requirement that 89 trustees be drawn from the members of the IAOC. 91 In this newly revised IETF Trust structure, there will be five 92 Trustees. Three shall be appointed by the IETF Nominating Committee 93 (NomCom) and confirmed by the Internet Engineering Steering Group 94 (IESG), one shall be appointed by the IESG, and one shall be 95 appointed by the Internet Society (ISOC) Board of Trustees. The 96 appointments by the IESG and ISOC Board of Trustees do not require 97 confirmation. 99 The IETF Trust Chair informs the nominating committee of the Trustee 100 positions to be reviewed. The IETF Trust will provide a summary of 101 the expertise desired of the Trustee candidates to each appointing 102 body. 104 A change to the Trust Agreement is required to put this change into 105 effect, and this document requests that the current Trustees make 106 this change at the earliest convenient time and no later than the end 107 of the 104th IETF meeting in March 2019. 109 The terms of the appointed trustees from IETF NomCom shall be three 110 years. The initial selection shall be one, two, and three year terms 111 in order to initially stagger the terms. The other appointments by 112 the IESG and the ISOC Board of Trustees shall be two year terms, with 113 the initial terms being one and two years, respectively. The goal of 114 the staggered initial terms is to minimize potential Trustee turnover 115 in any single year. To maintain the staggered terms, each appointing 116 body may at its discretion appoint Trustees for shorter terms as 117 needed in exceptional situations, e.g., for mid-term vacancies or 118 when an appointment is not ready by the time of the first IETF of the 119 year. 121 Once the initial trustee selections according to the procedures in 122 this document are complete, and at each subsequent annual meeting of 123 the IETF Trust once new trustees are seated, the trustees shall elect 124 by a majority vote of the IETF Trust one trustee to serve as IETF 125 Trust Chair. 127 The processes regarding NomCom appointments and recalls of Trustees 128 for the IETF Trust follow those described in [RFC7437]. For the 129 appointments by the IESG, the IESG is expected to run an open 130 selection process and to consider the necessary skill set and 131 conflicts of interest as part of that process. 133 3. Security Considerations 135 This memo has no security implications for the Internet. 137 4. IANA Considerations 139 This memo requests no action from IANA. 141 5. Acknowledgements 143 The authors would like to thank members of the earlier IASA 2.0 144 design team who were Brian Haberman, Eric Rescorla, Jari Arkko, Jason 145 Livingood, Joe Hall, and Leslie Daigle. The authors would also like 146 to thank Alissa Cooper, Andrew Sullivan, Brian Carpenter, Lucy Lynch, 147 and John Levine for interesting discussions in this problem space. 148 The authors would also like to thank Russ Housley, Bob Hinden, Scott 149 Mansfield, Alexey Melnikov, Suresh Krishnan, Mirja Kuhlewind, Ben 150 Campbell, Spencer Dawkins, Martin Vigoreux, Benjamin Kaduk, and 151 Adrian Farrel for careful review. 153 6. References 155 6.1. Normative References 157 [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the 158 IETF Administrative Support Activity (IASA)", BCP 101, 159 RFC 4071, DOI 10.17487/RFC4071, April 2005, 160 . 162 [RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for 163 IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371, 164 January 2006, . 166 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 167 Confirmation, and Recall Process: Operation of the 168 Nominating and Recall Committees", BCP 10, RFC 7437, 169 DOI 10.17487/RFC7437, January 2015, . 172 6.2. Informative References 174 [I-D.ietf-iasa2-trust-rationale] 175 Arkko, J., "Discussion of the Effects of IASA 2.0 Changes 176 as They Relate to the IETF Trust", draft-ietf-iasa2-trust- 177 rationale-00 (work in progress), September 2018. 179 Appendix A. Changes from Previous Versions 181 RFC Editor: Please remove this section upon publication. 183 The version draft-itef-iasa2-trust-update-02.txt made some editorial 184 corrections, as well as clarifying that no confirmation is needed in 185 the cases other than the nomcom appointment, specified how IETF Trust 186 chair is chosen, and required that an open process be used by the 187 IESG for the selections. 189 The version draft-ietf-iasa2-trust-update-01.txt has taken into 190 account last call comments. The changes are: 1) Clarification of the 191 role of the IETF Trust Chair to indicate which trustee positions are 192 up for selection, similar to how RFC 7437 requires the IETF Executive 193 Director to do it. 2) The addition of empty security and IANA 194 consideration sections. 3) The clarification of the staggering rules 195 for NomCom selections. 4) Updated text regarding the application of 196 rules from RFC 7437. 5) Update draft title to be correct in terms of 197 specifying a process rather than the actual persons. 6) Update the 198 text regarding desirable expertise to use the same language as in RFC 199 7437 instead of the "list of desired qualifications". 201 The version draft-ietf-iasa2-trust-update-00.txt corrected the 202 desired document status to BCP, and made several editorial and 203 language updates. This version also updated the wording for the 204 request for the current trustees to adopt this change, from "earliest 205 convenience" to "earliest convenient time". 207 The version draft-arkko-iasa2-trust-update-00.txt was the initial 208 version. 210 Authors' Addresses 212 Jari Arkko 213 Ericsson 214 Kauniainen 02700 215 Finland 217 Email: jari.arkko@piuha.net 219 Ted Hardie 221 Email: ted.ietf@gmail.com