idnits 2.17.1 draft-ietf-iasa2-trust-update-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 (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 (September 7, 2018) is 2057 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: 5 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 September 7, 2018 6 Expires: March 11, 2019 8 Update to the Selection of Trustees for the IETF Trust 9 draft-ietf-iasa2-trust-update-00 11 Abstract 13 This memo updates the selection of trustees for the IETF Trust. 14 Previously, the Internet Administrative Oversight Committee (IAOC) 15 members also acted as trustees but the IAOC has been eliminated as 16 part of an update of the structure of the Internet Administrative 17 Support Activity (IASA). This memo specifies that the trustees shall 18 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 March 11, 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. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 61 4. Changes from Previous Versions . . . . . . . . . . . . . . . 3 62 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 5.1. Normative References . . . . . . . . . . . . . . . . . . 3 64 5.2. Informative References . . . . . . . . . . . . . . . . . 4 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 67 1. Introduction 69 This memo updates the selection of trustees for the IETF Trust. 70 Previously, the Internet Administrative Oversight Committee (IAOC) 71 members also acted as trustees but the IAOC has been eliminated as 72 part of an update of the structure of the Internet Administrative 73 Support Activity (IASA). This memo specifies that the trustees shall 74 be selected separately. 76 This memo updates RFCs 4071 and 4371 with regards to the selection of 77 trustees. All other aspects of the IETF Trust remain as they are 78 today. 80 For a discussion of why this change is needed and a rationale for 81 these specific changes, see [I-D.ietf-iasa2-trust-rationale]. 83 2. Selection of Trustees 85 This document revises the original Trustee selection procedures 86 defined in [RFC4071] and [RFC4371], to eliminate the requirement that 87 trustees be drawn from the members of the IAOC. 89 In this newly revised IETF Trust structure, there will be five 90 Trustees. Three shall appointed by the IETF Nominating Committee 91 (NomCom) and confirmed by the Internet Engineering Steering Group 92 (IESG), one shall be appointed by the IESG, and one shall be 93 appointed by the Internet Society (ISOC) Board of Trustees. 95 The IETF Trust will provide a list of desired qualifications for the 96 Trustee positions to each appointing body. 98 A change to the Trust Agreement is required to put this change into 99 effect, and this document requests that the current Trustees make 100 this change at the earliest convenient time and no later than the end 101 of the 104th IETF meeting in March 2019. 103 The terms of the appointed trustees from IETF NomCom shall be three 104 years. The initial selection shall be one, two, and three year terms 105 in order to initially stagger the terms and thus miminize potential 106 annual Trustee turnover. The other appointments by the IESG and the 107 ISOC Board of Trustees shall be two year terms, with the initial 108 terms being one and two years, respectively. 110 IETF rules regarding recalls and other NomCom-related processes 111 continue to apply [RFC7437]. 113 3. Acknowledgements 115 The authors would like to thank members of the earlier IASA 2.0 116 design team who were Brian Haberman, Eric Rescorla, Jari Arkko, Jason 117 Livingood, Joe Hall, and Leslie Daigle. The authors would also like 118 to thank Alissa Cooper, Andrew Sullivan, Brian Carpenter, Lucy Lynch, 119 and John Levine for interesting discussions in this problem space. 121 4. Changes from Previous Versions 123 RFC Editor: Please remove this section upon publication. 125 The version draft-ietf-iasa2-trust-update-00.txt corrected the 126 desired document status to BCP, and made several editorial and 127 language updates. This version also updated the wording for the 128 request for the current trustees to adopt this change, from "earliest 129 convenience" to "earliest convenient time". 131 The version draft-arkko-iasa2-trust-update-00.txt was the initial 132 version. 134 5. References 136 5.1. Normative References 138 [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the 139 IETF Administrative Support Activity (IASA)", BCP 101, 140 RFC 4071, DOI 10.17487/RFC4071, April 2005, 141 . 143 [RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for 144 IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371, 145 January 2006, . 147 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 148 Confirmation, and Recall Process: Operation of the 149 Nominating and Recall Committees", BCP 10, RFC 7437, 150 DOI 10.17487/RFC7437, January 2015, . 153 5.2. Informative References 155 [I-D.ietf-iasa2-trust-rationale] 156 Arkko, J., "Discussion of the Effects of IASA 2.0 Changes 157 as They Relate to the IETF Trust", draft-ietf-iasa2-trust- 158 rationale-00 (work in progress), September 2018. 160 Authors' Addresses 162 Jari Arkko 163 Ericsson 164 Kauniainen 02700 165 Finland 167 Email: jari.arkko@piuha.net 169 Ted Hardie 171 Email: ted.ietf@gmail.com