idnits 2.17.1 draft-hildebrand-rfc3677bis-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 6, 2016) is 3002 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'ISOC-By-Laws' -- Obsolete informational reference (is this intentional?): RFC 7437 (Obsoleted by RFC 8713) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Hildebrand 3 Internet-Draft Cisco Systems 4 Obsoletes: 3677 (if approved) L. Daigle 5 Intended status: Standards Track February 6, 2016 6 Expires: August 9, 2016 8 IETF ISOC Board of Trustee Appointment Procedures 9 draft-hildebrand-rfc3677bis-00 11 Abstract 13 This memo, which obsoletes RFC3677, outlines the process by which the 14 IETF makes a selection of an Internet Society (ISOC) Board of 15 Trustees appointment. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on August 9, 2016. 34 Copyright Notice 36 Copyright (c) 2016 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 1.1. Overview of Selection Process . . . . . . . . . . . . . . 2 53 1.2. Rationale . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Desirable Qualifications and Selection Criteria for an IETF- 55 Nominated ISOC Trustee . . . . . . . . . . . . . . . . . . . 3 56 3. IETF ISOC Board of Trustees Selection Process . . . . . . . . 4 57 3.1. Nominations and Eligibility . . . . . . . . . . . . . . . 4 58 3.2. Selection . . . . . . . . . . . . . . . . . . . . . . . . 4 59 3.3. Confirmation . . . . . . . . . . . . . . . . . . . . . . 5 60 3.4. Timeframe . . . . . . . . . . . . . . . . . . . . . . . . 5 61 3.4.1. Timing of Fourth Appointment . . . . . . . . . . . . 5 62 3.4.2. Further Changes to Number and Timing of Appointments 6 63 3.5. Mid-term Vacancies . . . . . . . . . . . . . . . . . . . 6 64 3.5.1. Interim Appointment Process . . . . . . . . . . . . . 6 65 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 66 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 67 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 68 6.1. Normative References . . . . . . . . . . . . . . . . . . 6 69 6.2. Informative References . . . . . . . . . . . . . . . . . 7 70 Appendix A. IAB Members at the time of this writing . . . . . . 7 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 73 1. Introduction 75 The Internet Society (ISOC) provides organizational and financial 76 support for the IETF. As stipulated in [ISOC-By-Laws] (and 77 originally specified in [RFC3677]) the IETF is called upon to name 78 Trustees to its Board (BoT), with staggered 3 year terms. In 79 general, this requires that the IETF name one or more Trustees each 80 year. 82 This memo outlines the process by which the IETF makes that 83 selection. This process will also be used in the event of mid-term 84 vacancies that may arise with IETF nominated Board positions. 86 1.1. Overview of Selection Process 88 In brief, this document describes the timeframe and procedures for 89 the IAB to solicit public input and make a selection for the open 90 position each year. 92 1.2. Rationale 94 An alternative approach to making a selection for these positions 95 would be to use the IETF's NomCom ([RFC7437] and its revisions). 96 However, that NomCom is chartered and defined specifically to the 97 task of making selections for IETF organization tasks, and the ISOC 98 BoT appointment process does not fit that in 2 ways: 100 1. the timeframe of the appointment does not mesh with the IETF 101 appointment cycle 103 2. the nature of the deliberations and the type of information 104 solicited would be significantly different for an external 105 appointment, such as this appointment to the ISOC BoT 107 The first issue (timing) could be resolved fairly easily for this 108 specific appointment. The second issue is more general, and not 109 reasonably reconciled with the IETF NomCom task as currently 110 specified. 112 The process described in [RFC7437] is oriented toward soliciting 113 feedback from the IETF community with respect to individuals and 114 technical positions with which they have personal experience. To 115 make a good decision on external appointments, in general, the NomCom 116 would have to understand the requirements for those positions, and 117 attempt to evaluate candidates for a very different set of skills 118 than is required of IAB/IESG members. It might also require 119 soliciting feedback from outside the IETF community. There is no 120 question that the individuals that constitute the IETF NomCom each 121 year have the competence to carry out such a search; the issue is 122 that it is a very different task, would require additional time and 123 resources, and therefore is a side effort that could very well 124 undermine the effectiveness of the NomCom in carrying out its primary 125 task for the IETF. 127 By contrast, the IAB is chartered to be responsible for IETF external 128 liaisons, is a standing body that works with ISOC (and the ISOC 129 Board), and therefore has a working knowledge of the requirements of 130 the specific position discussed here. 132 At some future point, if there is a more general need to make 133 external appointments, the IETF may consider broadening the scope of 134 the IETF NomCom role, or create a separate nominating committee for 135 such external non-liaison appointments. This document proposes that 136 is not necessary or desirable for the purposes of this one annual 137 appointment. 139 2. Desirable Qualifications and Selection Criteria for an IETF- 140 Nominated ISOC Trustee 142 Candidates for an ISOC Trustee should have a demonstrable involvement 143 in the IETF with a particular focus on active participation in IETF 144 Working Groups. 146 The candidate is expected to possess clearly demonstrated technical 147 competence in Internet technology, and be able to articulate 148 technology issues such that the ISOC Board can be provided with sound 149 technical perspectives. The candidate is also expected to be able to 150 understand the respective roles and responsibilities of the IETF and 151 ISOC and be able to articulate these roles within both organizational 152 communities. 154 The candidate will also be expected to exercise all the duties of an 155 ISOC Board member, including fiduciary responsibility, setting of 156 policies, oversight of the operation of the Society, representing the 157 interests of the members and stakeholders of the Society and 158 participation in all Board meetings and Board activity programs. 160 The candidate is not a representative or a delegate of the IETF and 161 is not chartered to represent the IETF or the IETF Standards Process 162 within the ISOC Board or the broader ISOC community. However it is 163 expected that the candidate would be able to call on experts in the 164 IETF community as required, to ensure that the ISOC Board receives 165 the highest quality technical advice available. 167 3. IETF ISOC Board of Trustees Selection Process 169 3.1. Nominations and Eligibility 171 Each year, the IAB will make a public call for nominations on the 172 ietf-announce@ietf.org mailing list. The public call will specify 173 the manner by which nominations will be accepted and the means by 174 which the list of nominees will be published. 176 Self-nominations are permitted. Along with the name and contact 177 information for each candidate, details about the candidate's 178 background and qualifications for the position should be attached to 179 the nomination. All IETF participants, including working group 180 chairs, IETF NomCom members, IAB and IESG members are eligible for 181 nomination. 183 IAB and IESG members who accept nomination will recuse themselves 184 from selection and confirmation discussions respectively. 186 3.2. Selection 188 The IAB will publish the list of nominated persons, review the 189 nomination material, and make a selection. 191 The selection criteria will include additional consideration of any 192 nominated candidates who are concurrently members of the IAB or IESG 193 members such that at the time of selection no more than two of the 194 three IETF-appointed ISOC Trustees are IAB and IESG members. 196 3.3. Confirmation 198 The IESG will act as the confirming body for the selection. In the 199 event that the IESG determines not to confirm the nominated 200 candidate, the IESG will provide the IAB with the basis for this 201 determination and the IAB will nominate another candidate. 203 3.4. Timeframe 205 ISOC expects to seat new Board members at its annual general meeting 206 in June of each year. Basic timeframe requirements for the IETF 207 process are as follows: 209 o 4-6 weeks for solicitation of nominations 211 o 4-6 weeks for review of nominees, deliberation and selection 213 o 4-6 weeks for confirmation (and re-selection as necessary) and 214 delivery to ISOC 216 In January of each year, the IAB will announce the specific dates for 217 the IETF ISOC Trustee selection process for that year (taking into 218 account the particular dates of the first IETF meeting of the year, 219 etc), following the guidelines above. 221 3.4.1. Timing of Fourth Appointment 223 There was a change to the ISOC by-laws in 2013 such that the IAB 224 appoints a total of four Board members, with that change taking 225 effect in 2015. Every third year, the IAB will appoint two ISOC 226 Board members instead of one. 228 For clarity, this means the following number of Board members will be 229 appointed in the given years: 231 o 2015: 2 233 o 2016: 1 235 o 2017: 1 237 o 2018: 2 239 o 2019: 1 240 o 2020: 1 242 o etc. 244 3.4.2. Further Changes to Number and Timing of Appointments 246 If ISOC further modifies [ISOC-By-Laws] concerning the number of IAB 247 appointments to the ISOC Board or the timing thereof, the IAB will 248 make reasonable modifications to the processes embodied in this 249 document, without requiring further modification to this document. 250 Such changes will be announced via IAB statement. 252 3.5. Mid-term Vacancies 254 This document describes the process for the general, annual 255 appointment of ISOC Trustees to fill the seats of Trustees whose 256 terms are ending. However, if an IETF-appointed Trustee is unable to 257 serve his or her full term, the IAB may, at its discretion, 258 immediately select a replacement to serve the remainder of the term 259 using the interim process defined in Section 3.5.1. If the IAB does 260 not invoke the interim process, the next annual selection process 261 will fill the vacancy (if the vacant term does not end at that point) 262 as well as the regular appointment for that selection cycle. 264 3.5.1. Interim Appointment Process 266 If the IAB elects to fill the mid-term vacancy before the next annual 267 selection, a separate timeline will be announced and the rest of the 268 process described in this document will be followed. 270 4. IANA Considerations 272 This document has no actions for IANA 274 5. Security Considerations 276 This document does not describe any technical protocols and has no 277 implications for network security. 279 6. References 281 6.1. Normative References 283 [ISOC-By-Laws] 284 The Internet Society, "Amended and restated By-Laws of the 285 Internet Society", July 2013, 286 . 289 6.2. Informative References 291 [RFC3677] Daigle, L., Ed. and Internet Architecture Board, "IETF 292 ISOC Board of Trustee Appointment Procedures", BCP 77, 293 RFC 3677, DOI 10.17487/RFC3677, December 2003, 294 . 296 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 297 Confirmation, and Recall Process: Operation of the 298 Nominating and Recall Committees", BCP 10, RFC 7437, 299 DOI 10.17487/RFC7437, January 2015, 300 . 302 Appendix A. IAB Members at the time of this writing 304 Jari Arkko 306 Mary Barnes 308 Marc Blanchet 310 Ralph Droms 312 Ted Hardie 314 Joe Hildebrand 316 Russ Housley 318 Erik Nordmark 320 Robert Sparks 322 Andrew Sullivan 324 Dave Thaler 326 Brian Trammell 328 Suzanne Woolf 330 Authors' Addresses 332 Joe Hildebrand 333 Cisco Systems 335 Email: jhildebr@cisco.com 336 Leslie Daigle 338 Email: ldaigle@thinkingcat.com