idnits 2.17.1 draft-ietf-iasa2-rfc7437bis-09.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 draft header indicates that this document obsoletes RFC8318, but the abstract doesn't seem to directly say this. It does mention RFC8318 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 11, 2019) is 1723 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) -- Looks like a reference, but probably isn't: '0' on line 1752 -- Looks like a reference, but probably isn't: '1' on line 1758 -- Looks like a reference, but probably isn't: '6' on line 1728 -- Looks like a reference, but probably isn't: '17' on line 1744 -- Looks like a reference, but probably isn't: '4' on line 1762 ** Obsolete normative reference: RFC 3777 (Obsoleted by RFC 7437) ** Obsolete normative reference: RFC 7437 (Obsoleted by RFC 8713) -- Duplicate reference: RFC3777, mentioned in 'Err232', was also mentioned in 'RFC3777'. -- Obsolete informational reference (is this intentional?): RFC 3777 (ref. 'Err232') (Obsoleted by RFC 7437) -- Duplicate reference: RFC3777, mentioned in 'Err4179', was also mentioned in 'Err232'. -- Obsolete informational reference (is this intentional?): RFC 3777 (ref. 'Err4179') (Obsoleted by RFC 7437) -- Obsolete informational reference (is this intentional?): RFC 8318 (Obsoleted by RFC 8713) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Kucherawy, Ed. 3 Internet-Draft 4 Obsoletes: 7437, 8318 (if approved) R. Hinden, Ed. 5 Intended status: Best Current Practice Check Point Software 6 Expires: January 12, 2020 J. Livingood, Ed. 7 Comcast 8 July 11, 2019 10 IAB, IESG, IETF Trust and IETF LLC Selection, Confirmation, and Recall 11 Process: Operation of the IETF Nominating and Recall Committees 12 draft-ietf-iasa2-rfc7437bis-09 14 Abstract 16 The process by which the members of the IAB and IESG, some Trustees 17 of the IETF Trust, and some Directors of the IETF LLC are selected, 18 confirmed, and recalled is specified in this document. This document 19 is based on RFC7437. Only those updates required to reflect the 20 changes introduced by IASA 2.0 have been included. Any other changes 21 will be addressed in future documents. 23 This document obsoletes RFC7437 and RFC8318. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on January 12, 2020. 42 Copyright Notice 44 Copyright (c) 2019 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 61 3. General . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 62 3.1. Completion Due . . . . . . . . . . . . . . . . . . . . . 6 63 3.2. Nominating Committee Principal Functions . . . . . . . . 7 64 3.3. Positions To Be Reviewed . . . . . . . . . . . . . . . . 7 65 3.4. Term Lengths . . . . . . . . . . . . . . . . . . . . . . 7 66 3.5. Mid-term Vacancies . . . . . . . . . . . . . . . . . . . 9 67 3.6. Confidentiality . . . . . . . . . . . . . . . . . . . . . 10 68 3.7. Advice and Consent Model . . . . . . . . . . . . . . . . 11 69 3.7.1. Positions To Be Reviewed . . . . . . . . . . . . . . 11 70 3.7.2. Candidate Selection . . . . . . . . . . . . . . . . . 11 71 3.7.3. Candidate Review . . . . . . . . . . . . . . . . . . 11 72 3.7.4. Confirmation . . . . . . . . . . . . . . . . . . . . 12 73 3.8. Sitting Members, Directors and Trustees . . . 12 74 3.9. Announcements . . . . . . . . . . . . . . . . . . . . . . 13 75 4. Nominating Committee Selection . . . . . . . . . . . . . . . 14 76 4.1. Timeline . . . . . . . . . . . . . . . . . . . . . . . . 14 77 4.2. Term . . . . . . . . . . . . . . . . . . . . . . . . . . 14 78 4.3. Structure . . . . . . . . . . . . . . . . . . . . . . . . 15 79 4.4. Chair Duties . . . . . . . . . . . . . . . . . . . . . . 16 80 4.5. Chair Selection . . . . . . . . . . . . . . . . . . . . . 16 81 4.6. Temporary Chair . . . . . . . . . . . . . . . . . . . . . 16 82 4.7. Liaisons . . . . . . . . . . . . . . . . . . . . . . . . 17 83 4.8. Liaison Appointment . . . . . . . . . . . . . . . . . . . 17 84 4.9. Advisors . . . . . . . . . . . . . . . . . . . . . . . . 18 85 4.10. Past Chair . . . . . . . . . . . . . . . . . . . . . . . 18 86 4.11. Voting Volunteers . . . . . . . . . . . . . . . . . . . . 18 87 4.12. Milestones . . . . . . . . . . . . . . . . . . . . . . . 19 88 4.13. Open Positions . . . . . . . . . . . . . . . . . . . . . 19 89 4.14. Volunteer Qualification . . . . . . . . . . . . . . . . . 19 90 4.15. Not Qualified . . . . . . . . . . . . . . . . . . . . . . 20 91 4.16. Selection Process . . . . . . . . . . . . . . . . . . . . 20 92 4.17. Announcement of Selection Results . . . . . . . . . . . . 21 93 4.18. Committee Organization . . . . . . . . . . . . . . . . . 22 94 5. Nominating Committee Operation . . . . . . . . . . . . . . . 22 95 5.1. Discretion . . . . . . . . . . . . . . . . . . . . . . . 23 96 5.2. Selection Timeline . . . . . . . . . . . . . . . . . . . 23 97 5.3. Confirmation Timeline . . . . . . . . . . . . . . . . . . 23 98 5.4. Milestones . . . . . . . . . . . . . . . . . . . . . . . 23 99 5.5. Voting Mechanism . . . . . . . . . . . . . . . . . . . . 24 100 5.6. Voting Quorum . . . . . . . . . . . . . . . . . . . . . . 24 101 5.7. Voting Member Recall . . . . . . . . . . . . . . . . . . 24 102 5.8. Chair Recall . . . . . . . . . . . . . . . . . . . . . . 25 103 5.9. Deliberations . . . . . . . . . . . . . . . . . . . . . . 25 104 5.10. Call for Nominees . . . . . . . . . . . . . . . . . . . . 25 105 5.11. Nominations . . . . . . . . . . . . . . . . . . . . . . . 26 106 5.12. Candidate Selection . . . . . . . . . . . . . . . . . . . 26 107 5.13. Consent to Nomination . . . . . . . . . . . . . . . . . . 27 108 5.14. Notifying Confirming Bodies . . . . . . . . . . . . . . . 27 109 5.15. Confirming Candidates . . . . . . . . . . . . . . . . . . 28 110 5.16. Archives . . . . . . . . . . . . . . . . . . . . . . . . 28 111 6. Dispute Resolution Process . . . . . . . . . . . . . . . . . 28 112 7. Member, Trustee, and Director Recall . . . . . . . . . . . . 30 113 7.1. Petition . . . . . . . . . . . . . . . . . . . . . . . . 30 114 7.1.1. Community Petition . . . . . . . . . . . . . . . . . 30 115 7.1.2. Ombudsteam Petition . . . . . . . . . . . . . . . . . 31 116 7.2. Recall Committee Chair . . . . . . . . . . . . . . . . . 31 117 7.3. Recall Committee Creation . . . . . . . . . . . . . . . . 31 118 7.4. Recall Committee Rules . . . . . . . . . . . . . . . . . 31 119 7.5. Recall Committee Operation . . . . . . . . . . . . . . . 31 120 7.6. 3/4 Majority . . . . . . . . . . . . . . . . . . . . . . 31 121 7.7. Position To Be Filled . . . . . . . . . . . . . . . . . . 32 122 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 123 9. Security Considerations . . . . . . . . . . . . . . . . . . . 32 124 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 125 10.1. Normative References . . . . . . . . . . . . . . . . . . 32 126 10.2. Informative References . . . . . . . . . . . . . . . . . 33 127 Appendix A. Changes Since RFC 3777 . . . . . . . . . . . . . . . 33 128 Appendix B. Changes Since RFC 7437 . . . . . . . . . . . . . . . 34 129 Appendix C. Oral Tradition . . . . . . . . . . . . . . . . . . . 35 130 Appendix D. Nominating Committee Timeline . . . . . . . . . . . 35 131 Appendix E. Acknowledgments . . . . . . . . . . . . . . . . . . 38 132 Appendix F. Change log [RFC Editor: Please remove] . . . . . . . 38 133 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 41 135 1. Introduction 137 This document is a revision of [RFC7437] that updates it to be 138 consistent with the IETF Administrative Support Activity (IASA) 2.0 139 changes. RFC 7437 was based on [RFC3777] that consolidated and 140 updated other RFCs that updated that document into a single 141 specification. The result is a complete specification of the process 142 by which members of the Internet Architecture Board (IAB) and 143 Internet Engineering Steering Group (IESG), some Trustees of the IETF 144 Trust, and some Directors of the IETF Administration LLC (IETF LLC), 145 are selected, confirmed, and recalled. 147 This revision addresses only the changes required for IASA 2.0; 148 should the community agree on other changes, they will be addressed 149 in future documents. 151 Section 2 of [I-D.ietf-iasa2-trust-update] provides further details 152 about the IETF Trust Trustees positions that are filled by the IETF 153 Nominating Committee (NomCom). 155 Section 5 of [I-D.ietf-iasa2-rfc4071bis] provides further details 156 about the IETF LLC Director positions that are filled by the NomCom. 158 The following two assumptions continue to be true of this 159 specification: 161 1. The Internet Research Task Force (IRTF) and Internet Research 162 Steering Group (IRSG) are not a part of the process described 163 here. 165 2. The organization (and reorganization) of the IESG is not a part 166 of the process described here. 168 The time frames specified here use IETF meetings as a frame of 169 reference. The time frames assume that the IETF meets three times 170 per calendar year with approximately equal amounts of time between 171 them. The meetings are referred to as the First IETF, Second IETF, 172 or Third IETF as needed. 174 The next section lists the words and phrases commonly used throughout 175 this document with their intended meaning. 177 The majority of this document is divided into four major topics as 178 follows: 180 General: This is a set of rules and constraints that apply to the 181 selection and confirmation process as a whole. 183 Nominating Committee Selection: This is the process by which the 184 volunteers who will serve on the NomCom are selected. 186 Nominating Committee Operation: This is the set of principles, 187 rules, and constraints that guide the activities of the NomCom, 188 including the confirmation process. 190 Member, Trustee, and Director Recall: This is the process by which 191 the behavior of a sitting member of the IESG, or IAB, IETF Trust 192 Trustee, or IETF LLC Director may be questioned, perhaps resulting 193 in the removal of the sitting member. See Section 2 for a 194 description of what a sitting member means for each of these 195 groups. 197 A final section describes how this document differs from [RFC3777] 198 and [RFC7437]. 200 An appendix of useful facts and practices collected from previous 201 NomComs is also included. 203 This document updates the IAB, IESG, and IAOC Selection, 204 Confirmation, and Recall Process to be aligned with IASA 2.0 Model 205 [I-D.ietf-iasa2-rfc4071bis] that creates a IETF Administration 206 Limited Liability Company ("IETF LLC") managed by a Board of 207 Directors ("IETF LLC Board"). This document obsoletes [RFC7437] and 208 [RFC8318]. 210 2. Definitions 212 The following words and phrases are commonly used throughout this 213 document. They are listed here with their intended meaning for the 214 convenience of the reader. 216 Candidate: A nominee who has been selected to be considered for 217 confirmation by a confirming body. 219 Confirmed Candidate: A candidate that has been reviewed and approved 220 by a confirming body. 222 Nominating Committee Term: The term begins when its members are 223 officially announced, which is expected to be prior to the Third 224 IETF to ensure it is fully operational at the Third IETF. The 225 term ends at the Third IETF (not three meetings) after the next 226 NomCom's term begins. 228 IETF Executive Director: The person charged with day-to-day 229 operation of the IETF's administrative functions. (See 230 Section 4.1 of [I-D.ietf-iasa2-rfc4071bis]). Note: This was 231 previously the name of the IETF Secretariat position that is now 232 called the "Managing Director, IETF Secretariat". 234 Managing Director, IETF Secretariat: The person charged with 235 operation of the IETF Secretariat function. (See Section 2 of 236 [RFC3710] and [I-D.ietf-iasa2-consolidated-upd]). 238 Nominee: A person who is being or has been considered for one or 239 more open positions of the IESG, IAB, IETF Trust Trustee or IETF 240 LLC. 242 Sitting Member: A person who is currently serving as a member of the 243 IESG or IAB. 245 Sitting Director: A person who is currently serving as a Director of 246 the IETF LLC. 248 Sitting IETF Trust Trustee: A person who is currently serving as a 249 Trustee of the IETF Trust. 251 3. General 253 The following set of rules apply to the process as a whole. If 254 necessary, a paragraph discussing the interpretation of each rule is 255 included. 257 3.1. Completion Due 259 The completion of the annual process is due within seven months. 261 The completion of the annual process is due one month prior to the 262 Friday of the week before the First IETF. It is expected to begin at 263 least eight months prior to the Friday of the week before the First 264 IETF. 266 The process officially begins with the announcement of the Chair of 267 the committee. The process officially ends when all confirmed 268 candidates have been announced. 270 The annual process is comprised of three major components as follows: 272 1. The selection and organization of the NomCom members. 274 2. The selection of candidates by the NomCom. 276 3. The confirmation of the candidates. 278 There is an additional month set aside between when the annual 279 process is expected to end and the term of the new candidates is to 280 begin. This time may be used during unusual circumstances to extend 281 the time allocated for any of the components listed above. 283 3.2. Nominating Committee Principal Functions 285 The principal functions of the NomCom are to review each open IESG, 286 IAB, IETF Trust, and IETF LLC Director position and to select either 287 its incumbent or a superior candidate. 289 Although there is no term limit for serving in any IESG, IAB, or IETF 290 Trust position, the NomCom may use length of service as one of its 291 criteria for evaluating an incumbent. 293 The NomCom does not select the open positions to be reviewed; it is 294 instructed as to which positions to review. 296 The NomCom will be given the titles of the positions to be reviewed 297 and a brief summary of the desired expertise of the candidate that is 298 selected to fill each position. 300 Incumbents must notify the NomCom if they wish to be nominated. 302 The NomCom does not confirm its candidates; it presents its 303 candidates to the appropriate confirming body as indicated below. 305 A superior candidate is one who the NomCom believes would contribute 306 in such a way as to improve or enhance the body to which he or she is 307 nominated. 309 3.3. Positions To Be Reviewed 311 Approximately one-half of each of the then current IESG and IAB 312 positions, one IETF Trust position, and one IETF LLC Director 313 position, is selected to be reviewed each year. 315 The intent of this rule is to ensure the review of approximately one- 316 half of each of the IESG and IAB sitting members, one of the three 317 NomCom nominated IETF LLC Director positions, and one of the three 318 nominated IETF Trust Trustee positions, each year. It is recognized 319 that circumstances may exist that will require the NomCom to review 320 more or less than the usual number of positions, e.g., if the IESG, 321 IAB, IETF Trust, or IETF LLC Board have reorganized prior to this 322 process and created new positions, if there are an odd number of 323 current positions, or if a member, a director, or a trustee 324 unexpectedly resigns. 326 3.4. Term Lengths 328 Confirmed IESG and IAB candidates are expected to serve at least a 329 two-year term. The intent of this rule is to ensure that members of 330 the IESG and IAB serve the number of years that best facilitates the 331 review of one-half of the members each year. 333 Confirmed IETF LLC Director candidates are expected to serve at least 334 a three-year term, except if a nominating or selection body decides 335 to use a shorter term to allow for initial staggered appointments. 336 Please refer to Section 6 of [I-D.ietf-iasa2-rfc4071bis] for 337 additional guidance on term length and term limits for the IETF LLC 338 Board. 340 Confirmed IETF Trust Trustee candidates are expected to serve at 341 least a three-year term, except if a nominating or selection body 342 decides to use a shorter term to allow for initial staggered 343 appointments. Please refer to Section 2. of 344 [I-D.ietf-iasa2-trust-update] for additional guidance on term length 345 and term limits for the IETF Trust. 347 The term of a confirmed candidate selected according to the mid-term 348 vacancy rules may be less than a full term (two years for IESG and 349 IAB, three years for the IETF Trust and IETF LLC), as stated 350 elsewhere in this document. 352 It is consistent with this rule for the NomCom to choose one or more 353 of the currently open positions to which it may assign a term of not 354 more than three years in order to ensure the ideal application of 355 this rule in the future. 357 It is consistent with this rule for the NomCom to choose one or more 358 of the currently open positions that share responsibilities with 359 other positions (both those being reviewed and those sitting) to 360 which it may assign a term of not more than three years to ensure 361 that all such members, directors, or trustees will not be reviewed at 362 the same time. 364 All sitting member terms end during the First IETF meeting 365 corresponding to the end of the term for which they were confirmed. 366 All confirmed candidate terms begin during the First IETF meeting 367 corresponding to the beginning of the term for which they were 368 confirmed. 370 For confirmed candidates of the IESG, the terms begin no later than 371 when the currently sitting members' terms end on the last day of the 372 meeting. A term may begin or end no sooner than the first day of the 373 meeting and no later than the last day of the meeting as determined 374 by the mutual agreement of the currently sitting member and the 375 confirmed candidate. A confirmed candidate's term may overlap the 376 sitting member's term during the meeting as determined by their 377 mutual agreement. 379 For confirmed candidates of the IAB, the terms overlap with the terms 380 of the sitting members for the entire week of the meeting. 382 For confirmed Trustee candidates of the IETF Trust, the term begins 383 at the next IETF Trust meeting or as dictated by the policies and 384 procedures of the IETF Trust. 386 For confirmed Director candidates of the IETF LLC, the term begins at 387 the next appropriate IETF LLC Board meeting or as dictated by the 388 policies and procedures of the IETF LLC Board. 390 For candidates confirmed under the mid-term vacancy rules, the term 391 begins as soon as possible after the confirmation. 393 3.5. Mid-term Vacancies 395 Mid-term vacancies are filled by the same rules as documented here 396 with four qualifications, namely: 398 1. When there is only one official NomCom, the body with the mid- 399 term vacancy relegates the responsibility to fill the vacancy to 400 it. If the mid-term vacancy occurs during the period of time 401 that the term of the prior year's NomCom overlaps with the term 402 of the current year's NomCom, the body with the mid-term vacancy 403 must relegate the responsibility to fill the vacancy to the prior 404 year's NomCom. 406 2. If it is the case that the NomCom is reconvening to fill the mid- 407 term vacancy, then the completion of the candidate selection and 408 confirmation process is due within six weeks, with all other time 409 periods otherwise unspecified prorated accordingly. 411 3. The confirming body has two weeks from the day it is notified of 412 a candidate to reject the candidate, otherwise the candidate is 413 assumed to have been confirmed. 415 4. The term of the confirmed candidate will be either: 417 A. the remainder of the term of the open position if that 418 remainder is not less than one year or 420 B. the remainder of the term of the open position plus the next 421 two-year term for IESG and IAB positions or three-year term 422 for IETF LLC Director and IETF Trust positions if that 423 remainder is less than one year. 425 In both cases, a year is the period of time from a First IETF meeting 426 to the next First IETF meeting. 428 3.6. Confidentiality 430 All deliberations and supporting information that relates to specific 431 nominees, candidates, and confirmed candidates are confidential. 433 The NomCom and confirming body members will be exposed to 434 confidential information as a result of their deliberations, their 435 interactions with those they consult, and from those who provide 436 requested supporting information. All members and all other 437 participants are expected to handle this information in a manner 438 consistent with its sensitivity. 440 It is consistent with this rule for current NomCom members who have 441 served on prior NomComs to advise the current committee on 442 deliberations and results of the prior committee, as necessary and 443 appropriate. 445 The list of nominees willing to be considered for positions under 446 review in the current NomCom cycle is not confidential. The NomCom 447 may disclose a list of names of nominees who are willing to be 448 considered for positions under review to the community, in order to 449 obtain feedback from the community on these nominees. 451 The list of nominees disclosed for a specific position should contain 452 only the names of nominees who are willing to be considered for the 453 position under review. 455 The NomCom may choose not to include some names in the disclosed 456 list, at their discretion. 458 The NomCom may disclose an updated list, at its discretion. For 459 example, the NomCom might disclose an updated list if it identifies 460 errors/omissions in a previously disclosed version of the disclosed 461 list, or if the NomCom finds it necessary to call for additional 462 nominees, and these nominees indicate a willingness to be considered 463 before the NomCom has completed its deliberations. 465 Nominees may choose to ask people to provide feedback to the NomCom 466 but should not encourage any public statements of support. NomComs 467 should consider nominee-encouraged lobbying and campaigning to be 468 unacceptable behavior. 470 IETF community members are encouraged to provide feedback on nominees 471 to the NomCom but should not post statements of support/non-support 472 for nominees in any public forum. 474 3.7. Advice and Consent Model 476 Unless otherwise specified, the advice and consent model is used 477 throughout the process. This model is characterized as follows. 479 3.7.1. Positions To Be Reviewed 481 The chair of the IESG, IAB, IETF Trust and IETF LLC Board each 482 informs the NomCom of their respective positions to be reviewed. 484 The IESG, IAB, IETF Trust and IETF LLC are responsible for providing 485 a summary of the expertise desired of the candidates selected for 486 their respective open positions. The summaries are provided to the 487 NomCom for its consideration. 489 3.7.2. Candidate Selection 491 The NomCom selects candidates based on its understanding of the IETF 492 community's consensus of the qualifications required and advises each 493 confirming body of its respective candidates. 495 3.7.3. Candidate Review 497 The confirming bodies review their respective candidates, they may at 498 their discretion communicate with the NomCom, and then consent to 499 some, all, or none of the candidates. 501 The sitting IAB members review the IESG candidates. 503 The Internet Society Board of Trustees reviews the IAB candidates. 505 The sitting IESG members review the IETF Trust Trustee candidates. 507 The IETF LLC Director candidate is reviewed as specified in 508 [I-D.ietf-iasa2-rfc4071bis]. 510 The confirming bodies conduct their review using all information and 511 any means acceptable to them, including but not limited to the 512 supporting information provided by the NomCom, information known 513 personally to members of the confirming bodies and shared within the 514 confirming body, the results of interactions within the confirming 515 bodies, and the confirming bodies' interpretation of what is in the 516 best interests of the IETF community. 518 If all of the candidates are confirmed, the job of the NomCom with 519 respect to those open positions is complete. 521 If some or none of the candidates submitted to a confirming body are 522 confirmed, the confirming body should communicate with the NomCom 523 both to explain the reason why all the candidates were not confirmed 524 and to understand the NomCom's rationale for its candidates. 526 The confirming body may reject individual candidates, in which case 527 the NomCom must select alternate candidates for the rejected 528 candidates. 530 Any additional time required by the NomCom should not exceed its 531 maximum time allotment. 533 3.7.4. Confirmation 535 A confirming body decides whether it confirms each candidate using a 536 confirmation decision rule chosen by the confirming body. 538 If a confirming body has no specific confirmation decision rule, then 539 confirming a given candidate should require at least one-half of the 540 confirming body's sitting members to agree to that confirmation. 542 The decision may be made by conducting a formal vote, by asserting 543 consensus based on informal exchanges (e.g., email), or by any other 544 mechanism that is used to conduct the normal business of the 545 confirming body. 547 Regardless of which decision rule the confirming body uses, any 548 candidate that is not confirmed under that rule is considered to be 549 rejected. 551 The confirming body must make its decision within a reasonable time 552 frame. The results from the confirming body must be reported 553 promptly to the NomCom. 555 3.8. Sitting Members, Directors and Trustees 557 The following rules apply to nominees and candidates who are 558 currently sitting members of the IESG or IAB, IETF Trust Trustees, or 559 IETF LLC Directors and who are not sitting in an open position being 560 filled by the NomCom. 562 The confirmation of a candidate to an open position does not 563 automatically create a vacancy in the IESG, IAB, IETF Trust, or IETF 564 LLC Board position currently occupied by the candidate. The mid-term 565 vacancy cannot exist until, first, the candidate formally resigns 566 from the current position and, second, the body with the vacancy 567 formally decides for itself that it wants the NomCom to fill the mid- 568 term vacancy according to the rules for a mid-term vacancy documented 569 elsewhere in this document. 571 The resignation should be effective as of when the term of the new 572 position begins. The resignation may remain confidential to the 573 IESG, IAB, IETF Trust, IETF LLC Board, and NomCom until the confirmed 574 candidate is announced for the new position. The process, according 575 to rules set out elsewhere in this document, of filling the seat 576 vacated by the confirmed candidate may begin as soon as the vacancy 577 is publicly announced. 579 Filling a mid-term vacancy is a separate and independent action from 580 the customary action of filling open positions. In particular, a 581 NomCom must complete its job with respect to filling the open 582 positions and then separately proceed with the task of filling the 583 mid-term vacancy according to the rules for a mid-term vacancy 584 documented elsewhere in this document. 586 However, the following exception is permitted in the case where the 587 candidate for an open position is currently a sitting member of the 588 IAB. It is consistent with these rules for the announcements of a 589 resignation of a sitting member of the IAB and of the confirmed 590 candidate for the mid-term vacancy created by that sitting member on 591 the IAB to all occur at the same time as long as the actual sequence 592 of events that occurred did so in the following order: 594 1. The NomCom completes the advice and consent process for the open 595 position being filled by the candidate currently sitting on the 596 IAB. 598 2. The newly confirmed candidate resigns from their current position 599 on the IAB. 601 3. The IAB Chair (or the Managing Director, IETF Secretariat, if no 602 Chair has been named or the vacancy was created via the departure 603 of the IAB Chair) informs the NomCom of the mid-term vacancy. 605 4. The NomCom acts on the request to fill the mid-term vacancy. 607 3.9. Announcements 609 All announcements must be made using at least the mechanism used by 610 the IETF Secretariat for its announcements, including a notice on the 611 IETF web site. 613 As of the publication of this document, the current mechanism is an 614 email message to both the "ietf" and the "ietf-announce" mailing 615 lists. 617 4. Nominating Committee Selection 619 The following set of rules apply to the creation of the NomCom and 620 the selection of its members. 622 4.1. Timeline 624 The completion of the process of selecting and organizing the members 625 of the NomCom is due within three months. 627 The completion of the selection and organization process is due at 628 least one month prior to the Third IETF. This ensures the NomCom is 629 fully operational and available for interviews and consultation 630 during the Third IETF. 632 4.2. Term 634 The term of a NomCom is expected to be 15 months. 636 It is the intent of this rule that the end of a NomCom's term overlap 637 by approximately three months the beginning of the term of the next 638 NomCom. 640 The term of a NomCom begins when its members are officially 641 announced. The term ends at the Third IETF (not three meetings), 642 i.e., the IETF meeting after the next NomCom's term begins. 644 A term is expected to begin at least two months prior to the Third 645 IETF to ensure the NomCom has at least one month to get organized 646 before preparing for the Third IETF. 648 A NomCom is expected to complete any work in progress before it is 649 dissolved at the end of its term. 651 During the period of time when the terms of the NomComs overlap, all 652 mid-term vacancies are to be relegated to the prior year's NomCom. 653 The prior year's NomCom has no other responsibilities during the 654 overlap period. At all times other than the overlap period, there is 655 exactly one official NomCom and it is responsible for all mid-term 656 vacancies. 658 When the prior year's NomCom is filling a mid-term vacancy during the 659 period of time that the terms overlap, the NomCom operate 660 independently. However, some coordination is needed between them. 661 Since the prior year's Chair is a non-voting advisor to the current 662 NomCom, the coordination is expected to be straightforward. 664 4.3. Structure 666 The NomCom comprises at least a Chair, 10 voting volunteers, two 667 liaisons, and an advisor. 669 Any committee member may propose the addition of an advisor to 670 participate in some or all of the deliberations of the committee. 671 The addition must be approved by the committee according to its 672 established voting mechanism. Advisors participate as individuals. 674 Committee members are encouraged to propose the addition of 675 advisor(s) who are knowledgeable about the operations of the IETF 676 Trust and/or IETF LLC Board, whether or not that NomCom is reviewing 677 an IETF Trust Trustee or IETF LLC Director position. The NomCom may 678 choose to ask the IETF Trust and/or IETF LLC Board to suggest 679 advisors who are knowledgeable about their operations but may select 680 any advisor they vote to approve. 682 Any committee member may propose the addition of a liaison from other 683 unrepresented organizations to participate in some or all of the 684 deliberations of the committee. The addition must be approved by the 685 committee according to its established voting mechanism. Liaisons 686 participate as representatives of their respective organizations. 688 The Chair is selected according to rules stated elsewhere in this 689 document. 691 The 10 voting volunteers are selected according to rules stated 692 elsewhere in this document. 694 The IESG and IAB liaisons are selected according to rules stated 695 elsewhere in this document. 697 The Internet Society Board of Trustees may appoint a liaison to the 698 NomCom at its own discretion. 700 The IETF Trust may appoint a liaison to the NomCom at its own 701 discretion. 703 The IETF LLC Board may appoint a liaison to the NomCom at its own 704 discretion. 706 The Chair of the prior year's NomCom serves as an advisor according 707 to rules stated elsewhere in this document. 709 The Chair, liaisons, and advisors do not vote on the selection of 710 candidates. They do vote on all other issues before the committee 711 unless otherwise specified in this document. 713 4.4. Chair Duties 715 The Chair of the NomCom is responsible for ensuring the NomCom 716 completes its assigned duties in a timely fashion and performs in the 717 best interests of the IETF community. 719 The Chair must be thoroughly familiar with the rules and guidance 720 indicated throughout this document. The Chair must ensure the NomCom 721 completes its assigned duties in a manner that is consistent with 722 this document. 724 The Chair must attest by proclamation at a plenary session of the 725 First IETF that the results of the committee represent its best 726 effort and the best interests of the IETF community. 728 The Chair does not vote on the selection of candidates. 730 4.5. Chair Selection 732 The Internet Society President appoints the Chair, who must meet the 733 same requirements for membership in the NomCom as a voting volunteer. 735 The NomCom Chair must agree to invest the time necessary to ensure 736 that the NomCom completes its assigned duties and to perform in the 737 best interests of the IETF community in that role. 739 The appointment is due no later than the Second IETF meeting to 740 ensure it can be announced during a plenary session at that meeting. 741 The completion of the appointment is necessary to ensure the annual 742 process can complete at the time specified elsewhere in this 743 document. 745 4.6. Temporary Chair 747 A Chair, in consultation with the Internet Society President, may 748 appoint a temporary substitute for the Chair position. 750 There are a variety of ordinary circumstances that may arise from 751 time to time that could result in a Chair being unavailable to 752 oversee the activities of the committee. The Chair, in consultation 753 with the Internet Society President, may appoint a substitute from a 754 pool comprised of the liaisons currently serving on the committee and 755 the prior year's Chair or designee. 757 Any such appointment must be temporary and does not absolve the Chair 758 of any or all responsibility for ensuring the NomCom completes its 759 assigned duties in a timely fashion. 761 4.7. Liaisons 763 Liaisons are responsible for ensuring the NomCom in general and the 764 Chair in particular execute their assigned duties in the best 765 interests of the IETF community. 767 Liaisons are expected to represent the views of their respective 768 organizations during the deliberations of the committee. They should 769 provide information as requested or when they believe it would be 770 helpful to the committee. 772 Liaisons are expected to provide information to the NomCom regarding 773 the operation, responsibility, and composition of their respective 774 bodies. 776 Liaisons are expected to convey questions from the committee to their 777 respective organizations and responses to those questions to the 778 committee, as requested by the committee. 780 Liaisons are expected to review the operation and executing process 781 of the NomCom and to report any concerns or issues to the Chair of 782 the NomCom immediately. If they cannot resolve the issue between 783 themselves, liaisons must report it according to the dispute 784 resolution process stated elsewhere in this document. 786 Liaisons from confirming bodies are expected to assist the committee 787 in preparing the testimony it is required to provide with its 788 candidates. 790 Liaisons may have other NomCom responsibilities as required by their 791 respective organizations or requested by the NomCom, except that such 792 responsibilities may not conflict with any other provisions of this 793 document. 795 Liaisons do not vote on the selection of candidates. 797 4.8. Liaison Appointment 799 The sitting IAB and IESG members each appoint a liaison from their 800 current membership, someone who is not sitting in an open position, 801 to serve on the NomCom. 803 The sitting IETF Trust Trustees and IETF LLC Directors each may 804 appoint a liaison from their current membership, someone who is not 805 sitting in an open position, to serve on the NomCom. 807 4.9. Advisors 809 An advisor is responsible for such duties as specified by the 810 invitation that resulted in the appointment. 812 Advisors do not vote on the selection of candidates. 814 4.10. Past Chair 816 The Chair of the prior year's NomCom serves as an advisor to the 817 current committee. 819 The prior year's Chair is expected to review the actions and 820 activities of the current Chair and to report any concerns or issues 821 to the NomCom Chair immediately. If they cannot resolve the issue 822 between themselves, the prior year's Chair must report it according 823 to the dispute resolution process stated elsewhere in this document. 825 The prior year's Chair may select a designee from a pool composed of 826 the voting volunteers of the prior year's committee and all prior 827 Chairs if the Chair is unavailable. If the prior year's Chair is 828 unavailable or is unable or unwilling to make such a designation in a 829 timely fashion, the Chair of the current year's committee may select 830 a designee in consultation with the Internet Society President. 832 Selecting a prior year's committee member as the designee permits the 833 experience of the prior year's deliberations to be readily available 834 to the current committee. Selecting an earlier prior year Chair as 835 the designee permits the experience of being a Chair as well as that 836 Chair's committee deliberations to be readily available to the 837 current committee. 839 All references to "prior year's Chair" in this document refer to the 840 person serving in that role, whether it is the actual prior year's 841 Chair or a designee. 843 4.11. Voting Volunteers 845 Voting volunteers are responsible for completing the tasks of the 846 NomCom in a timely fashion. 848 Each voting volunteer is expected to participate in all activities of 849 the NomCom with a level of effort approximately equal to all other 850 voting volunteers. Specific tasks to be completed are established 851 and managed by the Chair according to rules stated elsewhere in this 852 document. 854 4.12. Milestones 856 The Chair must establish and announce milestones for the selection of 857 the NomCom members. 859 There is a defined time period during which the selection process is 860 due to be completed. The Chair must establish a set of milestones 861 which, if met in a timely fashion, will result in the completion of 862 the process on time. 864 4.13. Open Positions 866 The Chair (or the Managing Director, IETF Secretariat, if no Chair 867 has been named four weeks after the First IETF meeting of the year) 868 obtains the list of positions to be reviewed and announces it along 869 with a solicitation for names of volunteers from the IETF community 870 willing to serve on the NomCom. 872 If the Managing Director, IETF Secretariat issues the solicitation 873 for volunteers, the Managing Director, IETF Secretariat must also 874 collect responses to the solicitation and provide the names of 875 volunteers to the incoming NomCom Chair when the incoming NomCom 876 Chair is named. 878 At the Chair's request, the IETF Secretariat may perform other 879 clerical support tasks, as long as the task being performed does not 880 require NomCom Chair judgment, in the NomCom Chair's opinion, and as 881 long as the community is appropriately notified that this request is 882 being made. This request may come from the incoming NomCom Chair (if 883 one has been selected for this NomCom cycle) or the previous NomCom 884 Chair (if the search for an incoming NomCom Chair is still underway). 886 The solicitation must permit the community at least 30 days during 887 which they may choose to volunteer to be selected for the NomCom. 889 The list of open positions is published with the solicitation to 890 facilitate community members choosing between volunteering for an 891 open position and volunteering for the NomCom. 893 4.14. Volunteer Qualification 895 Members of the IETF community must have attended at least three of 896 the last five IETF meetings in order to volunteer. 898 The five meetings are the five most recent meetings that ended prior 899 to the date on which the solicitation for NomCom volunteers was 900 submitted for distribution to the IETF community. 902 The IETF Secretariat is responsible for confirming that volunteers 903 have met the attendance requirement. 905 Volunteers must provide their full name, email address, and primary 906 company or organization affiliation (if any) when volunteering. 908 Volunteers are expected to be familiar with the IETF processes and 909 procedures, which are readily learned by active participation in a 910 working group and especially by serving as a document editor or 911 working group chair. 913 4.15. Not Qualified 915 Any person who serves on the Internet Society Board of Trustees, the 916 IETF Trust, the IETF LLC Board of Directors, the IAB, or the IESG, 917 including those who serve on these bodies in ex officio positions, 918 may not volunteer to serve as voting members of the NomCom. In 919 addition, employees or contractors of the IETF LLC may not volunteer 920 to serve as voting members of the NomCom. Liaisons to these bodies 921 from other bodies or organizations are not excluded by this rule. 923 4.16. Selection Process 925 The Chair announces both the list of the pool of volunteers from 926 which the 10 voting volunteers will be randomly selected and the 927 method with which the selection will be completed. 929 The announcement should be made at least one week prior to the date 930 on which the random selection will occur. 932 The pool of volunteers must be enumerated or otherwise indicated 933 according to the needs of the selection method to be used. 935 The announcement must specify the data that will be used as input to 936 the selection method. The method must depend on random data whose 937 value is not known or available until the date on which the random 938 selection will occur. 940 It must be possible to independently verify that the selection method 941 used is both fair and unbiased. A method is fair if each eligible 942 volunteer is equally likely to be selected. A method is unbiased if 943 no one can influence its outcome in favor of a specific outcome. 945 It must be possible to repeat the selection method, either through 946 iteration or by restarting in such a way as to remain fair and 947 unbiased. This is necessary to replace selected volunteers should 948 they become unavailable after selection. 950 The selection method must produce an ordered list of volunteers. 952 One possible selection method is described in [RFC3797]. 954 4.17. Announcement of Selection Results 956 The Chair randomly selects the 10 voting volunteers from the pool of 957 names of volunteers and announces the members of the NomCom. 959 No more than two volunteers with the same primary affiliation may be 960 selected for the NomCom. The Chair reviews the primary affiliation 961 of each volunteer selected by the method in turn. If the primary 962 affiliation for a volunteer is the same as two previously selected 963 volunteers, that volunteer is removed from consideration and the 964 method is repeated to identify the next eligible volunteer. 966 There must be at least two announcements of all members of the 967 NomCom. 969 The first announcement should occur as soon after the random 970 selection as is reasonable for the Chair. The community must have at 971 least one week during which any member may challenge the results of 972 the random selection. 974 The challenge must be made in writing (email is acceptable) to the 975 Chair. The Chair has 48 hours to review the challenge and offer a 976 resolution to the member. If the resolution is not accepted by the 977 member, that member may report the challenge according to the dispute 978 resolution process stated elsewhere in this document. 980 If a selected volunteer, upon reading the announcement with the list 981 of selected volunteers, finds that two or more other volunteers have 982 the same affiliation, then the volunteer should notify the Chair who 983 will determine the appropriate action. 985 During at least the one week challenge period, the Chair must contact 986 each of the members and confirm their willingness and availability to 987 serve. The Chair should make every reasonable effort to contact each 988 member. 990 o If the Chair is unable to contact a liaison, the problem is 991 referred to the respective organization to resolve. The Chair 992 should allow a reasonable amount of time for the organization to 993 resolve the problem and then may proceed without the liaison. 995 o If the Chair is unable to contact an advisor, the Chair may elect 996 to proceed without the advisor, except for the prior year's Chair 997 for whom the Chair must consult with the Internet Society 998 President as stated elsewhere in this document. 1000 o If the Chair is unable to contact a voting volunteer, the Chair 1001 must repeat the random selection process in order to replace the 1002 unavailable volunteer. There should be at least one day between 1003 the announcement of the iteration and the selection process. 1005 After at least one week and confirming that 10 voting volunteers are 1006 ready to serve, the Chair makes the second announcement of the 1007 members of the NomCom, which officially begins the term of the 1008 NomCom. 1010 4.18. Committee Organization 1012 The Chair works with the members of the committee to organize itself 1013 in preparation for completing its assigned duties. 1015 The committee has approximately one month during which it can self- 1016 organize. Its responsibilities during this time include but are not 1017 limited to the following: 1019 o Setting up a regular teleconference schedule. 1021 o Setting up an internal web site. 1023 o Setting up a mailing list for internal discussions. 1025 o Setting up an email address for receiving community input. 1027 o Establishing operational procedures. 1029 o Establishing milestones in order to monitor the progress of the 1030 selection process. 1032 5. Nominating Committee Operation 1034 The following rules apply to the operation of the NomCom. If 1035 necessary, a paragraph discussing the interpretation of each rule is 1036 included. 1038 The rules are organized approximately in the order in which they 1039 would be invoked. 1041 5.1. Discretion 1043 All rules and special circumstances not otherwise specified are at 1044 the discretion of the committee. 1046 Exceptional circumstances will occasionally arise during the normal 1047 operation of the NomCom. This rule is intended to foster the 1048 continued forward progress of the committee. 1050 Any member of the committee may propose a rule for adoption by the 1051 committee. The rule must be approved by the committee according to 1052 its established voting mechanism. 1054 All members of the committee should consider whether the exception is 1055 worthy of mention in the next revision of this document and follow-up 1056 accordingly. 1058 5.2. Selection Timeline 1060 The completion of the process of selecting candidates to be confirmed 1061 by their respective confirming body is due within three months. 1063 The completion of the selection process is due at least two months 1064 prior to the First IETF. This ensures the NomCom has sufficient time 1065 to complete the confirmation process. 1067 5.3. Confirmation Timeline 1069 The completion of the process of confirming the candidates is due 1070 within one month. 1072 The completion of the confirmation process is due at least one month 1073 prior to the First IETF. 1075 5.4. Milestones 1077 The Chair must establish a set of NomCom milestones for the candidate 1078 selection and confirmation process. 1080 There is a defined time period during which the candidate selection 1081 and confirmation process must be completed. The Chair must establish 1082 a set of milestones that, if met in a timely fashion, will result in 1083 the completion of the process on time. The Chair should allow time 1084 for iterating the activities of the committee if one or more 1085 candidates are not confirmed. 1087 The Chair should ensure that all committee members are aware of the 1088 milestones. 1090 5.5. Voting Mechanism 1092 The Chair must establish a voting mechanism. 1094 The committee must be able to objectively determine when a decision 1095 has been made during its deliberations. The criteria for determining 1096 closure must be established and known to all members of the NomCom. 1098 5.6. Voting Quorum 1100 At least a quorum of committee members must participate in a vote. 1102 Only voting volunteers vote on a candidate selection. For a 1103 candidate selection vote, a quorum is comprised of at least seven of 1104 the voting volunteers. 1106 At all other times, a quorum is present if at least 75% of the NomCom 1107 members are participating. 1109 5.7. Voting Member Recall 1111 Any member of the NomCom may propose to the committee that any other 1112 member except the Chair be recalled. The process for recalling the 1113 Chair is defined elsewhere in this document. 1115 There are a variety of ordinary circumstances that may arise that 1116 could result in one or more members of the committee being 1117 unavailable to complete their assigned duties, for example, health 1118 concerns, family issues, or a change of priorities at work. A 1119 committee member may choose to resign for unspecified personal 1120 reasons. In addition, the committee may not function well as a group 1121 because a member may be disruptive or otherwise uncooperative. 1123 Regardless of the circumstances, if individual committee members 1124 cannot work out their differences between themselves, the entire 1125 committee may be called upon to discuss and review the circumstances. 1126 If a resolution is not forthcoming, a vote may be conducted. A 1127 member may be recalled if at least a quorum of all committee members 1128 agree, including the vote of the member being recalled. 1130 If a liaison member is recalled, the committee must notify the 1131 affected organization and must allow a reasonable amount of time for 1132 a replacement to be identified by the organization before proceeding. 1134 If an advisor member other than the prior year's Chair is recalled, 1135 the committee may choose to proceed without the advisor. In the case 1136 of the prior year's Chair, the Internet Society President must be 1137 notified and the current Chair must be allowed a reasonable amount of 1138 time to consult with the Internet Society President to identify a 1139 replacement before proceeding. 1141 If a single voting volunteer position on the NomCom is vacated, 1142 regardless of the circumstances, the committee may choose to proceed 1143 with only nine voting volunteers at its own discretion. In all other 1144 cases, a new voting member must be selected, and the Chair must 1145 repeat the random selection process including an announcement of the 1146 iteration prior to the actual selection as stated elsewhere in this 1147 document. 1149 A change in the primary affiliation of a voting volunteer during the 1150 term of the NomCom is not a cause to request the recall of that 1151 volunteer, even if the change would result in more than two voting 1152 volunteers with the same affiliation. 1154 5.8. Chair Recall 1156 Only the prior year's Chair may request the recall of the current 1157 Chair. 1159 It is the responsibility of the prior year's Chair to ensure the 1160 current Chair completes the assigned tasks in a manner consistent 1161 with this document and in the best interests of the IETF community. 1163 Any member of the committee who has an issue or concern regarding the 1164 Chair should report it to the prior year's Chair immediately. The 1165 prior year's Chair is expected to report it to the Chair immediately. 1166 If they cannot resolve the issue between themselves, the prior year's 1167 Chair must report it according to the dispute resolution process 1168 stated elsewhere in this document. 1170 5.9. Deliberations 1172 All members of the NomCom may participate in all deliberations. 1174 The emphasis of this rule is that no member can be explicitly 1175 excluded from any deliberation. However, a member may individually 1176 choose not to participate in a deliberation. 1178 5.10. Call for Nominees 1180 The Chair announces the open positions to be reviewed, the desired 1181 expertise provided by the Managing Director, IETF Secretariat, and 1182 the call for nominees. 1184 The call for nominees must include a request for comments regarding 1185 the past performance of incumbents, which will be considered during 1186 the deliberations of the NomCom. 1188 The call must request that a nomination include a valid, working 1189 email address, a telephone number, or both for the nominee. The 1190 nomination must include the set of skills or expertise the nominator 1191 believes the nominee has that would be desirable. 1193 5.11. Nominations 1195 Any member of the IETF community may nominate any member of the IETF 1196 community for any open position, whose eligibility to serve will be 1197 confirmed by the NomCom. 1199 A self-nomination is permitted. 1201 NomCom members are not eligible to be considered for filling any open 1202 position by the NomCom on which they serve. They become ineligible 1203 as soon as the term of the NomCom on which they serve officially 1204 begins. They remain ineligible for the duration of that NomCom's 1205 term. 1207 Although each NomCom's term overlaps with the following NomCom's 1208 term, NomCom members are eligible for nomination by the following 1209 committee if not otherwise disqualified. 1211 Members of the IETF community who were recalled from any IESG, IAB, 1212 IETF Trust, or IETF LLC Board position during the previous two years 1213 are not eligible to be considered for filling any open position. 1215 5.12. Candidate Selection 1217 The NomCom selects candidates based on its understanding of the IETF 1218 community's consensus of the qualifications required to fill the open 1219 positions. 1221 The intent of this rule is to ensure that the NomCom consults with a 1222 broad base of the IETF community for input to its deliberations. In 1223 particular, the NomCom must determine if the desired expertise for 1224 the open positions matches its understanding of the qualifications 1225 desired by the IETF community. 1227 The consultations are permitted to include names of nominees, if all 1228 parties to the consultation agree to observe the same confidentiality 1229 rules as the NomCom itself, or the names are public as discussed in 1230 Section 3.6. Feedback on individual nominees should always be 1231 confidential. 1233 A broad base of the community should include the existing members of 1234 the IESG and IAB, IETF Trust Trustees, and IETF LLC Directors, 1235 especially sitting members who share responsibilities with open 1236 positions, e.g., co-Area Directors, and working group chairs, 1237 especially those in the areas with open positions. 1239 Only voting volunteer members vote to select candidates. 1241 5.13. Consent to Nomination 1243 Nominees should be advised that they are being considered and must 1244 consent to their nomination prior to being chosen as candidates. 1246 Although the NomCom will make every reasonable effort to contact and 1247 to remain in contact with nominees, any nominee whose contact 1248 information changes during the process and who wishes to still be 1249 considered should inform the NomCom of the changes. 1251 A nominee's consent must be written (email is acceptable) and must 1252 include a commitment to provide the resources necessary to fill the 1253 open position and an assurance that the nominee will perform the 1254 duties of the position for which they are being considered in the 1255 best interests of the IETF community. 1257 Consenting to a nomination must occur prior to a nominee being a 1258 candidate and may occur as soon after the nomination as needed by the 1259 NomCom. 1261 Consenting to a nomination must not imply the nominee will be a 1262 candidate. 1264 The NomCom should help nominees provide justification to their 1265 employers. 1267 5.14. Notifying Confirming Bodies 1269 The NomCom advises the confirming bodies of their candidates, 1270 specifying a single candidate for each open position and testifying 1271 as to how each candidate meets the qualifications of an open 1272 position. 1274 For each candidate, the testimony must include a brief statement of 1275 the qualifications for the position that is being filled, which may 1276 be exactly the expertise that was requested. If the qualifications 1277 differ from the expertise originally requested, a brief statement 1278 explaining the difference must be included. 1280 The testimony may include a brief resume of the candidate and/or a 1281 brief summary of the deliberations of the NomCom. 1283 5.15. Confirming Candidates 1285 Confirmed candidates must consent to their confirmation, and rejected 1286 candidates and nominees must be notified before confirmed candidates 1287 are announced. 1289 It is not necessary to notify and get consent from all confirmed 1290 candidates together. 1292 A nominee may not know they were a candidate. This permits a 1293 candidate to be rejected by a confirming body without the nominee 1294 knowing about the rejection. 1296 Rejected nominees, who consented to their nomination, and rejected 1297 candidates must be notified prior to announcing the confirmed 1298 candidates. 1300 It is not necessary to announce all confirmed candidates together. 1302 The NomCom must ensure that all confirmed candidates are prepared to 1303 serve prior to announcing their confirmation. 1305 5.16. Archives 1307 The NomCom should archive the information it has collected or 1308 produced for a period of time but not to exceed its term. 1310 The purpose of the archive is to assist the NomCom should it be 1311 necessary for it to fill a mid-term vacancy. 1313 The existence of an archive, how it is implemented, and what 1314 information to archive is at the discretion of the committee. The 1315 decision must be approved by a quorum of the voting volunteer 1316 members. 1318 The implementation of the archive should make every reasonable effort 1319 to ensure that the confidentiality of the information it contains is 1320 maintained. 1322 6. Dispute Resolution Process 1324 The dispute resolution process described here is to be used as 1325 indicated elsewhere in this document. Its applicability in other 1326 circumstances is beyond the scope of this document. 1328 The NomCom operates under a strict rule of confidentiality. For this 1329 reason, when process issues arise, it is best to make every 1330 reasonable effort to resolve them within the committee. However, 1331 when circumstances do not permit this, or no resolution is 1332 forthcoming, the process described here is to be used. 1334 The following rules apply to the process. 1336 1. The results of this process are final and binding. There is no 1337 appeal. 1339 2. The process begins with the submission of a request as described 1340 below to the Internet Society President. 1342 3. As soon as the process begins, the NomCom may continue those 1343 activities that are unrelated to the issue to be resolved except 1344 that it must not submit any candidates to a confirming body until 1345 the issue is resolved. 1347 4. All parties to the process are subject to the same 1348 confidentiality rules as each member of the NomCom. 1350 5. The process should be completed within two weeks. 1352 The process is as follows: 1354 1. The party seeking resolution submits a written request (email is 1355 acceptable) to the Internet Society President detailing the issue 1356 to be resolved. 1358 2. The Internet Society President appoints an arbiter to investigate 1359 and resolve the issue. A self-appointment is permitted. 1361 3. The arbiter investigates the issue making every reasonable effort 1362 to understand both sides of the issue. Since the arbiter is 1363 subject to the same confidentiality obligations as all NomCom 1364 members, all members are expected to cooperate fully with the 1365 arbiter and to provide all relevant information to the arbiter 1366 for review. 1368 4. After consultation with the two principal parties to the issue, 1369 the arbiter decides on a resolution. Whatever actions are 1370 necessary to execute the resolution are immediately begun and 1371 completed as quickly as possible. 1373 5. The arbiter summarizes the issue, the resolution, and the 1374 rationale for the resolution for the Internet Society President. 1376 6. In consultation with the Internet Society President, the arbiter 1377 prepares a report of the dispute and its resolution. The report 1378 should include all information that in the judgment of the 1379 arbiter does not violate the confidentiality requirements of the 1380 NomCom. 1382 7. The Chair includes the dispute report when reporting on the 1383 activities of the NomCom to the IETF community. 1385 7. Member, Trustee, and Director Recall 1387 The following rules apply to the recall process. If necessary, a 1388 paragraph discussing the interpretation of each rule is included. 1390 It applies to IESG and IAB Members, the NomCom appointed IETF Trust 1391 Trustees, and the NomCom appointed IETF LLC Directors. 1393 7.1. Petition 1395 At any time, a signed petition (email is acceptable) may be submitted 1396 to the Internet Society President to request the recall of any 1397 sitting IESG or IAB member, or NomCom appointed IETF Trust Trustee, 1398 or NomCom appointed IETF LLC Director. There are two different types 1399 of petitions: a petition by participants of the IETF community, and a 1400 petition by the Ombudsteam as described in [RFC7776]. 1402 7.1.1. Community Petition 1404 A recall petition can be made by at least 20 members of the IETF 1405 community who are qualified to be voting members of a NomCom. All 1406 individual and collective qualifications of NomCom eligibility are 1407 applicable, including that no more than two signatories may have the 1408 same primary affiliation. 1410 Each signature must include a full name, email address, and primary 1411 company or organization affiliation. 1413 The IETF Secretariat is responsible for confirming that each 1414 signatory is qualified to be a voting member of a NomCom. A valid 1415 petition must be signed by at least 20 qualified signatories. 1417 The petition must include a statement of justification for the recall 1418 and all relevant and appropriate supporting documentation. 1420 The petition and its signatories must be announced to the IETF 1421 community. 1423 7.1.2. Ombudsteam Petition 1425 The Ombudsteam process allows the Ombudsteam to form a recall 1426 petition on its own without requiring 20 signatories from the 1427 community. As defined in [RFC7776], the petition and its signatories 1428 (the Ombudsteam) shall be announced to the IETF community, and a 1429 Recall Committee Chair shall be appointed to complete the Recall 1430 Committee process. It is expected that the Recall Committee will 1431 receive a briefing from the Ombudsteam explaining why recall is 1432 considered an appropriate remedy. 1434 7.2. Recall Committee Chair 1436 The Internet Society President shall appoint a Recall Committee 1437 Chair. 1439 The Internet Society President must not evaluate the recall request. 1440 It is explicitly the responsibility of the IETF community to evaluate 1441 the behavior of its leaders. 1443 7.3. Recall Committee Creation 1445 The recall committee is created according to the same rules as is the 1446 NomCom with the qualifications that both the person being 1447 investigated and the parties requesting the recall must not be a 1448 member of the recall committee in any capacity. 1450 7.4. Recall Committee Rules 1452 The recall committee operates according to the same rules as the 1453 NomCom with the qualification that there is no confirmation process. 1455 7.5. Recall Committee Operation 1457 The recall committee investigates the circumstances of the 1458 justification for the recall and votes on its findings. 1460 The investigation must include at least both an opportunity for the 1461 member being recalled to present a written statement and consultation 1462 with third parties. 1464 7.6. 3/4 Majority 1466 A 3/4 majority of the members who vote on the question is required 1467 for a recall. 1469 7.7. Position To Be Filled 1471 If a sitting member is recalled, the open position is to be filled 1472 according to the mid-term vacancy rules. 1474 8. IANA Considerations 1476 No IANA actions required. 1478 9. Security Considerations 1480 Any selection, confirmation, or recall process necessarily involves 1481 investigation into the qualifications and activities of prospective 1482 candidates. The investigation may reveal confidential or otherwise 1483 private information about candidates to those participating in the 1484 process. Each person who participates in any aspect of the process 1485 must maintain the confidentiality of any and all information not 1486 explicitly identified as suitable for public dissemination. 1488 When the NomCom decides it is necessary to share confidential or 1489 otherwise private information with others, the dissemination must be 1490 minimal and must include a prior commitment from all persons 1491 consulted to observe the same confidentiality rules as the NomCom 1492 itself. 1494 10. References 1496 10.1. Normative References 1498 [I-D.ietf-iasa2-consolidated-upd] 1499 Klensin, J., "Consolidated IASA 2.0 Updates of IETF 1500 Administrative Terminology", draft-ietf-iasa2- 1501 consolidated-upd-07 (work in progress), March 2019. 1503 [I-D.ietf-iasa2-rfc4071bis] 1504 Haberman, B., Hall, J., and J. Livingood, "Structure of 1505 the IETF Administrative Support Activity, Version 2.0", 1506 draft-ietf-iasa2-rfc4071bis-11 (work in progress), April 1507 2019. 1509 [I-D.ietf-iasa2-trust-update] 1510 Arkko, J. and T. Hardie, "Update to the Process for 1511 Selection of Trustees for the IETF Trust", draft-ietf- 1512 iasa2-trust-update-03 (work in progress), February 2019. 1514 [RFC3777] Galvin, J., Ed., "IAB and IESG Selection, Confirmation, 1515 and Recall Process: Operation of the Nominating and Recall 1516 Committees", RFC 3777, DOI 10.17487/RFC3777, June 2004, 1517 . 1519 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 1520 Confirmation, and Recall Process: Operation of the 1521 Nominating and Recall Committees", BCP 10, RFC 7437, DOI 1522 10.17487/RFC7437, January 2015, . 1525 [RFC7776] Resnick, P. and A. Farrel, "IETF Anti-Harassment 1526 Procedures", BCP 25, RFC 7776, DOI 10.17487/RFC7776, March 1527 2016, . 1529 10.2. Informative References 1531 [Err232] RFC Errata, "Erratum ID 232", RFC 3777. 1533 [Err4179] RFC Errata, "Erratum ID 4179", RFC 3777. 1535 [RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, DOI 10.17487/ 1536 RFC3710, February 2004, . 1539 [RFC3797] Eastlake 3rd, D., "Publicly Verifiable Nominations 1540 Committee (NomCom) Random Selection", RFC 3797, DOI 1541 10.17487/RFC3797, June 2004, . 1544 [RFC8318] Dawkins, S., "IAB, IESG, and IAOC Selection, Confirmation, 1545 and Recall Process: IAOC Advisor for the Nominating 1546 Committee", BCP 10, RFC 8318, DOI 10.17487/RFC8318, 1547 January 2018, . 1549 Appendix A. Changes Since RFC 3777 1551 o Converted source file from nroff to XML, resulting in some 1552 reformatting. 1554 o Applied errata for RFC 3777 ([Err232] and [Err4179]). 1556 o Applied RFC 5078 update. 1558 o Applied RFC 5633 update. 1560 o Applied RFC 5680 update. 1562 o Applied RFC 6859 update. 1564 o Corrected a few grammatical errors. 1566 o Added a reference to RFC 3710. 1568 Appendix B. Changes Since RFC 7437 1570 o Changed all mentions of the Internet Administrative Oversight 1571 committee (IAOC), and replaced it with the appropriate references 1572 to the IETF Administration LLC (IETF LLC). This included making 1573 changes on an as needed basis to some aspects of the process for 1574 the IETF LLC, in accordance with IASA2. 1576 o Revised definition of IETF Executive Director, and added 1577 definition of "Managing Director, IETF Secretariat". Changed text 1578 to "Managing Director, IETF Secretariat" where appropriate. 1580 o Added references to appropriate IASA2 documents. 1582 o Modified the Advice and Consent model to enable IESG, IAB, and 1583 IETF LLC to communicate directly with the NomCom rather than via 1584 the Managing Director, IETF Secretariat. 1586 o Updated removal text to reflect the new LLC rules, which enables 1587 removal via the LLC or the IETF recall process, except for the 1588 ISOC-appointed Director. 1590 o Updated the document to clarify that there are members of the IAB 1591 and IESG, Trustees of the IETF Trust, and Director of the IETF 1592 LLC. 1594 o Updated document to also specify procedures for the NomCom 1595 appointed IETF Trust Trustees. 1597 o Revised Abstract and Introduction to provide current context. 1599 o Changed "nominating committee" to "NomCom" throughout the document 1600 because it is what most use to describe the IETF Nominating 1601 Committee. 1603 o Added that the IETF Trust Trustees and IETF LLC Directors, each 1604 may appoint a liaison to the NomCom. 1606 o Incorporated the update to RFC7437 done by RFC7776. 1608 o Incorporated the update to RFC7437 done by [RFC8318] and updated 1609 it to refer to the IETF Trust and IETF LLC, instead of the IAOC. 1611 o Editorial changes. 1613 Appendix C. Oral Tradition 1615 Over the years, various NomComs have learned through oral tradition 1616 passed on by liaisons that there are certain consistencies in the 1617 process and information considered during deliberations. Some items 1618 from that oral tradition are collected here to facilitate its 1619 consideration by future NomComs. 1621 1. It has been found that experience as an IETF Working Group Chair 1622 or an IRTF Research Group Chair is helpful in giving a nominee 1623 experience of what the job of an Area Director involves. It also 1624 helps a NomCom judge the technical, people, and process 1625 management skills of the nominee. 1627 2. No person should serve both on the IAB and as an Area Director, 1628 except the IETF Chair whose roles as an IAB member and Area 1629 Director of the General Area are set out elsewhere. 1631 3. The strength of the IAB is found in part in the balance of the 1632 demographics of its members (e.g., national distribution, years 1633 of experience, gender, etc.), the combined skill set of its 1634 members, and the combined sectors (e.g., industry, academia, 1635 etc.) represented by its members. 1637 4. There are no term limits for IAB and IESG members explicitly 1638 because the issue of continuity versus turnover should be 1639 evaluated each year according to the expectations of the IETF 1640 community, as it is understood by each NomCom. 1642 5. The number of NomCom members with the same primary affiliation is 1643 limited in order to avoid the appearance of improper bias in 1644 choosing the leadership of the IETF. Rather than defining 1645 precise rules for how to define "affiliation", the IETF community 1646 depends on the honor and integrity of the participants to make 1647 the process work. 1649 Appendix D. Nominating Committee Timeline 1651 This appendix is included for the convenience of the reader and is 1652 not to be interpreted as the definitive timeline. It is intended to 1653 capture the detail described elsewhere in this document in one place. 1654 Although every effort has been made to ensure the description here is 1655 consistent with the description elsewhere, if there are any conflicts 1656 the definitive rule is the one in the main body of this document. 1658 The only absolute in the timeline rules for the annual process is 1659 that its completion is due by the First IETF of the year after the 1660 NomCom begins its term. This is supported by the fact that the 1661 confirmed candidate terms begin during the week of the First IETF. 1663 The overall annual process is designed to be completed in seven 1664 months. It is expected to start nine months prior to the First IETF. 1665 The time is split between three major components of the process 1666 roughly as follows: 1668 1. First is the selection and organization of the committee members. 1669 Three months are allotted for this process. 1671 2. Second is the selection of the candidates by the NomCom. Four 1672 months are allotted for this process. 1674 3. Third is the confirmation of the candidates by their respective 1675 confirming bodies. Two months are allotted for this process. 1677 The following list captures the details of the milestones within each 1678 component. For illustrative purposes, the list presumes the Friday 1679 before the First IETF is March 1. Numbers shown in square brackets 1680 indicate the expected number of weeks at each step. 1682 1. BEGIN Eight Months Prior to First IETF (approx. June 1); 1683 Internet Society President appoints the Chair. The appointment 1684 must be done no later than the Second IETF or eight months prior 1685 to the First IETF, whichever comes first. The Chair must be 1686 announced and recognized during a plenary session of the Second 1687 IETF. [0] 1689 2. The Chair establishes and announces milestones to ensure the 1690 timely selection of the NomCom members. [1] 1692 3. The Chair contacts the IESG, IAB, and Internet Society Board of 1693 Trustees, IETF Trust, and IETF LLC and requests a liaison. The 1694 Chair contacts the prior year's Chair and requests an advisor. 1695 The Chair obtains the list of IESG, IAB, IETF Trust, and IETF 1696 LLC open positions and descriptions from the chairs of each 1697 group. [0] 1699 4. The Chair announces the solicitation for voting volunteer 1700 members that must remain open for at least 30 days. The 1701 announcement must be done no later than seven months and two 1702 weeks prior to the First IETF (approx. June 15). [6] 1704 5. After the solicitation closes, the Chair announces the pool of 1705 volunteers and the date of the random selection, which must be 1706 at least one week in the future. The announcement must be done 1707 no later than six months and two weeks prior to the First IETF 1708 (approx. July 15). [1] 1710 6. On the appointed day, the random selection occurs and the Chair 1711 announces the members of the committee and the one week 1712 challenge period. The announcement must be done no later than 1713 six months and one week prior to the First IETF (approx. July 1714 22). [1] 1716 7. During the challenge period, the Chair contacts each of the 1717 committee members and confirms their availability to 1718 participate. [0] 1720 8. After the challenge period closes, the Chair announces the 1721 members of the committee and its term begins. The announcement 1722 must be done no later than six months prior to the First IETF 1723 (approx. August 1). [1] 1725 9. The committee has one month during which it is to self-organize 1726 in preparation for completing its assigned duties. This must be 1727 done no later than five months prior to the First IETF (approx. 1728 September 15). [6] 1730 10. END the Committee Member Selection Process; BEGIN the Selection 1731 of Candidates; Time is at least five months prior to the First 1732 IETF (approx. September 22). [0] 1734 11. The Chair establishes and announces the milestones to ensure the 1735 timely selection of the candidates, including a call for 1736 nominations for the open positions. The announcement must be 1737 done no later than five months prior to the First IETF (approx. 1738 October 1). [1] 1740 12. Over the next three months, the NomCom collects input and 1741 deliberates. It should plan to conduct interviews and other 1742 consultations during the Third IETF. The committee is due to 1743 complete its candidate selection no later than two months prior 1744 to the First IETF (approx. January 1). [17] 1746 13. END the Selection of Candidates; BEGIN the Confirmation of 1747 Candidates; Time is at least two months prior to the First IETF 1748 (approx. January 1). [0] 1750 14. The committee presents its candidates to their respective 1751 confirming bodies. The presentation must be done no later than 1752 two months prior to the First IETF (approx. January 1). [0] 1754 15. The confirming bodies have one month to deliberate and, in 1755 communication with the NomCom, accept or reject candidates. [4] 1757 16. The Chair notifies and advises unsuccessful nominees that they 1758 have not been selected. [1] 1760 17. The Chair announces the confirmed candidates. The announcement 1761 must be done no later than one month prior to the First IETF 1762 (approx. February 1). [4] 1764 Appendix E. Acknowledgments 1766 A great deal of work went into the RFCs that preceded this one. The 1767 2014 NomCom and this editor would like to thank all of them once 1768 again for the time and energy it took to get us to where we are now. 1769 In no particular order, we acknowledge: 1771 Jeff Case Fred Baker John Curran 1772 Guy Almes Geoff Huston Mike St. Johns 1773 Donald Eastlake Avri Doria Bernard Adoba 1774 Ted T'so Phil Roberts Jim Galvin 1775 Harald Alvestrand Leslie Daigle Joel Halpern 1776 Thomas Narten Spencer Dawkins Barry Leiba 1777 Lars Eggert Ross Callon Brian Carpenter 1778 Robert Elz Bernie Hoeneisen John Klensin 1779 Danny McPherson S. Moonesamy Scott Bradner 1780 Ralph Droms Pekka Savola 1782 Allison Mankin and Russ White provided early reviews and feedback 1783 about this document. 1785 Jari Arkko was very helpful by independently verifying that the 1786 previous text from all the merged documents was marshaled correctly 1787 into this one, and Adrian Farrel and Brian Carpenter caught the nits 1788 that fell through the cracks. 1790 Appendix F. Change log [RFC Editor: Please remove] 1792 draft-ietf-iasa2-rfc74337bis-09, 2019-July-11 1794 * Added text to Abstract noting that this revision addresses only 1795 the changes required for IASA 2.0 and other changes will be 1796 addressed in future documents. 1797 * Editorial changes based on IESG reviews: 1799 + Remove RFC3747 from Abstract because this document is only 1800 based on RFC7437. 1802 + Making member, director, and trustee terminology consistent. 1803 + Changed "nominated" to "selected" in Section 3.2. 1804 + Add Trustee to end of second paragraph of Section 3.7.1. 1805 + Correct section reference to [I-D.ietf-iasa2-rfc4071bis] in 1806 Section 3.4 1807 + Clarify that there are two and three terms in Section 3.5. 1808 bullet 4. B. 1809 + Add Trustee to Section 3.8 section title and first 1810 paragraph. 1811 + Clarify that there are only term limits for IAB and IESG 1812 members in Appendix C bullet 4. 1813 + Add IETF Trust and IETF LLC to Appendix D bullet 3. 1814 + Spelled out IETF Administrative Support Activity (IASA) on 1815 first use in Section 1. 1816 + Minor editorial changes 1818 draft-ietf-iasa2-rfc74337bis-08, 2019-June-26 1820 * Added a paragraph to Section 1 "Introduction" noting that this 1821 revision addresses only the changes required for IASA 2.0 and 1822 that should the community agree on other changes, they will be 1823 addressed in future documents. 1825 draft-ietf-iasa2-rfc74337bis-07, 2019-June-7 1827 * Added reference to [I-D.ietf-iasa2-consolidated-upd] in 1828 Section 2. 1829 * Changed reference to RFC3710 to Informational. 1830 * Removed step 3 from IAB mid-term vacancies in Section 3.8 as it 1831 was redundant with step 4. 1832 * Correct summary below for -06 version. 1833 * Editorial changes. 1835 draft-ietf-iasa2-rfc74337bis-06, 2019-March-26 1837 * Removed IETF LLC from the list of positions who don't have term 1838 limits in Section 3.2. 1839 * Added IETF Trust to the list of positions who can be recalled 1840 in Section 5.11. 1841 * Editorial changes. 1843 draft-ietf-iasa2-rfc74337bis-05, 2019-January-11: 1845 * Changed text to point to appropriate Sections of 1846 [I-D.ietf-iasa2-rfc4071bis]. 1847 * Editorial changes. 1849 draft-ietf-iasa2-rfc74337bis-04, 2019-January-3: 1851 * Added IETF Trust to the title. 1852 * Changed references to point to current IASA 2.0 structure 1853 document [I-D.ietf-iasa2-rfc4071bis] 1854 * Added IETF Trust to a few places it was missing. 1855 * Editorial changes. 1857 draft-ietf-iasa2-rfc74337bis-03, 2018-October-22: 1859 * Revised Section 7 to focus on repeal of the the NomCom appoint 1860 LLC Director positions. 1861 * Added that the IETF Trust Trustees and IETF LLC Directors, each 1862 may appoint a liaison to the NomCom. 1863 * Incorporated the update to RFC7437 done by RFC7776. 1864 * Incorporated the update to RFC7437 done by [RFC8318] and 1865 updated it to refer to the IETF Trust and IETF LLC. instead of 1866 the IAOC. 1867 * Editorial changes. 1869 draft-ietf-iasa2-rfc74337bis-02, 2018-October-19: 1871 * Added "IETF" before Nominating and Recall Committees in the 1872 title. 1873 * Added leading capitalization to Trustee(s) and Director(s) for 1874 consistency. 1875 * Fixed other minor grammatical, spelling, or abbreviation nits. 1877 draft-ietf-iasa2-rfc74337bis-01, 2018-October-16: 1879 * Modified the Advice and Consent model to enable IESG, IAB, and 1880 IETF LLC to communicate directly with the NomCom rather than 1881 via the Managing Director, IETF Secretariat. 1882 * Updated member removal text to reflect the new LLC rules, which 1883 enables removal via the LLC or the IETF recall process, except 1884 for the ISOC-appointed Director. 1885 * Removed discussion text from the volunteer eligibility section. 1886 This means that IETF LLC employees and contractors cannot 1887 volunteer for the NomCom but does not extend that prohibition 1888 to ISOC employees and contractors. 1890 * Updated the document to clarify that there are members of the 1891 IAB and IESG, Trustees of the IETF Trust, and Directors of the 1892 IETF LLC. 1893 * Removed ISOC Board of Trustees members from the definition of 1894 "sitting members" because it doesn't apply. 1895 * Updated document to also include procedures for the NomCom 1896 appointed IETF Trust Trustees. 1897 * Revised Abstract and Introduction to provide current context. 1898 * Changed "nominating committee" to "NomCom" throughout the 1899 document because it is what most use to describe the IETF 1900 Nominating Committee. 1901 * Added an no-actions IANA Considerations Section. 1902 * Editorial changes. 1904 draft-ietf-iasa2-rfc74337bis-00, 2018-October-12: 1905 Initial bis draft, Changes include: 1907 * Changed all mentions of the Internet Administrative Oversight 1908 committee (IAOC), and replaced it with the appropriate 1909 references to the IETF Administration LLC (IETF LLC). This 1910 included making changes on an as needed basis to some aspects 1911 of the process for the IETF LLC, in accordance with IASA2. 1912 * Revised definition of IETF Executive Director, and added 1913 definition of "Managing Director, IETF Secretariat". Changed 1914 text to "Managing Director, IETF Secretariat" where 1915 appropriate. 1916 * Added references to appropriate IASA2 documents. 1917 * Corrected a few grammatical errors. 1919 Authors' Addresses 1921 Murray S. Kucherawy (editor) 1922 270 Upland Drive 1923 San Francisco, CA 94127 1924 United States 1926 Email: superuser@gmail.com 1928 Robert M. Hinden (editor) 1929 Check Point Software 1930 San Carlos, CA 1931 USA 1933 Email: bob.hinden@gmail.com 1934 Jason Livingood (editor) 1935 Comcast 1936 Philadelphia, PA 1937 USA 1939 Email: jason_livingood@comcast.com