idnits 2.17.1 draft-ietf-iasa2-rfc7437bis-08.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 (June 26, 2019) is 1756 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 1750 -- Looks like a reference, but probably isn't: '1' on line 1756 -- Looks like a reference, but probably isn't: '6' on line 1726 -- Looks like a reference, but probably isn't: '17' on line 1742 -- Looks like a reference, but probably isn't: '4' on line 1760 ** 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: December 28, 2019 J. Livingood, Ed. 7 Comcast 8 June 26, 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-08 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 RFC3777 and RFC7437 and has been updated to reflect the 20 changes introduced by IASA 2.0. 22 This document obsoletes RFC7437 and RFC8318. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on December 28, 2019. 41 Copyright Notice 43 Copyright (c) 2019 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 60 3. General . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 61 3.1. Completion Due . . . . . . . . . . . . . . . . . . . . . 6 62 3.2. Nominating Committee Principal Functions . . . . . . . . 6 63 3.3. Positions To Be Reviewed . . . . . . . . . . . . . . . . 7 64 3.4. Term Lengths . . . . . . . . . . . . . . . . . . . . . . 7 65 3.5. Mid-term Vacancies . . . . . . . . . . . . . . . . . . . 9 66 3.6. Confidentiality . . . . . . . . . . . . . . . . . . . . . 9 67 3.7. Advice and Consent Model . . . . . . . . . . . . . . . . 10 68 3.7.1. Positions To Be Reviewed . . . . . . . . . . . . . . 10 69 3.7.2. Candidate Selection . . . . . . . . . . . . . . . . . 11 70 3.7.3. Candidate Review . . . . . . . . . . . . . . . . . . 11 71 3.7.4. Confirmation . . . . . . . . . . . . . . . . . . . . 12 72 3.8. Sitting Members and Directors . . . . . . . . . . . . . . 12 73 3.9. Announcements . . . . . . . . . . . . . . . . . . . . . . 13 74 4. Nominating Committee Selection . . . . . . . . . . . . . . . 13 75 4.1. Timeline . . . . . . . . . . . . . . . . . . . . . . . . 13 76 4.2. Term . . . . . . . . . . . . . . . . . . . . . . . . . . 14 77 4.3. Structure . . . . . . . . . . . . . . . . . . . . . . . . 14 78 4.4. Chair Duties . . . . . . . . . . . . . . . . . . . . . . 15 79 4.5. Chair Selection . . . . . . . . . . . . . . . . . . . . . 16 80 4.6. Temporary Chair . . . . . . . . . . . . . . . . . . . . . 16 81 4.7. Liaisons . . . . . . . . . . . . . . . . . . . . . . . . 16 82 4.8. Liaison Appointment . . . . . . . . . . . . . . . . . . . 17 83 4.9. Advisors . . . . . . . . . . . . . . . . . . . . . . . . 17 84 4.10. Past Chair . . . . . . . . . . . . . . . . . . . . . . . 17 85 4.11. Voting Volunteers . . . . . . . . . . . . . . . . . . . . 18 86 4.12. Milestones . . . . . . . . . . . . . . . . . . . . . . . 18 87 4.13. Open Positions . . . . . . . . . . . . . . . . . . . . . 19 88 4.14. Volunteer Qualification . . . . . . . . . . . . . . . . . 19 89 4.15. Not Qualified . . . . . . . . . . . . . . . . . . . . . . 20 90 4.16. Selection Process . . . . . . . . . . . . . . . . . . . . 20 91 4.17. Announcement of Selection Results . . . . . . . . . . . . 20 92 4.18. Committee Organization . . . . . . . . . . . . . . . . . 22 93 5. Nominating Committee Operation . . . . . . . . . . . . . . . 22 94 5.1. Discretion . . . . . . . . . . . . . . . . . . . . . . . 22 95 5.2. Selection Timeline . . . . . . . . . . . . . . . . . . . 23 96 5.3. Confirmation Timeline . . . . . . . . . . . . . . . . . . 23 97 5.4. Milestones . . . . . . . . . . . . . . . . . . . . . . . 23 98 5.5. Voting Mechanism . . . . . . . . . . . . . . . . . . . . 23 99 5.6. Voting Quorum . . . . . . . . . . . . . . . . . . . . . . 23 100 5.7. Voting Member Recall . . . . . . . . . . . . . . . . . . 24 101 5.8. Chair Recall . . . . . . . . . . . . . . . . . . . . . . 25 102 5.9. Deliberations . . . . . . . . . . . . . . . . . . . . . . 25 103 5.10. Call for Nominees . . . . . . . . . . . . . . . . . . . . 25 104 5.11. Nominations . . . . . . . . . . . . . . . . . . . . . . . 25 105 5.12. Candidate Selection . . . . . . . . . . . . . . . . . . . 26 106 5.13. Consent to Nomination . . . . . . . . . . . . . . . . . . 26 107 5.14. Notifying Confirming Bodies . . . . . . . . . . . . . . . 27 108 5.15. Confirming Candidates . . . . . . . . . . . . . . . . . . 27 109 5.16. Archives . . . . . . . . . . . . . . . . . . . . . . . . 28 110 6. Dispute Resolution Process . . . . . . . . . . . . . . . . . 28 111 7. Member, Trustee, and Director Recall . . . . . . . . . . . . 29 112 7.1. Petition . . . . . . . . . . . . . . . . . . . . . . . . 30 113 7.1.1. Community Petition . . . . . . . . . . . . . . . . . 30 114 7.1.2. Ombudsteam Petition . . . . . . . . . . . . . . . . . 30 115 7.2. Recall Committee Chair . . . . . . . . . . . . . . . . . 30 116 7.3. Recall Committee Creation . . . . . . . . . . . . . . . . 31 117 7.4. Recall Committee Rules . . . . . . . . . . . . . . . . . 31 118 7.5. Recall Committee Operation . . . . . . . . . . . . . . . 31 119 7.6. 3/4 Majority . . . . . . . . . . . . . . . . . . . . . . 31 120 7.7. Position To Be Filled . . . . . . . . . . . . . . . . . . 31 121 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 122 9. Security Considerations . . . . . . . . . . . . . . . . . . . 31 123 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 124 10.1. Normative References . . . . . . . . . . . . . . . . . . 32 125 10.2. Informative References . . . . . . . . . . . . . . . . . 32 126 Appendix A. Changes Since RFC 3777 . . . . . . . . . . . . . . . 33 127 Appendix B. Changes Since RFC 7437 . . . . . . . . . . . . . . . 33 128 Appendix C. Oral Tradition . . . . . . . . . . . . . . . . . . . 34 129 Appendix D. Nominating Committee Timeline . . . . . . . . . . . 35 130 Appendix E. Acknowledgments . . . . . . . . . . . . . . . . . . 37 131 Appendix F. Change log [RFC Editor: Please remove] . . . . . . . 38 132 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 134 1. Introduction 136 This document is a revision of [RFC7437] that updates it to be 137 consistent with the IASA 2.0 changes. RFC 7437 was based on 138 [RFC3777] that consolidated and updated other RFCs that updated that 139 document into a single specification. The result is a complete 140 specification of the process by which members of the Internet 141 Architecture Board (IAB) and Internet Engineering Steering Group 142 (IESG), some Trustees of the IETF Trust, and some Directors of the 143 IETF Administration LLC (IETF LLC), are selected, confirmed, and 144 recalled. 146 This revision addresses only the changes required for IASA 2.0; 147 should the community agree on other changes, they will be addressed 148 in future documents. 150 Section 2 of [I-D.ietf-iasa2-trust-update] provides further details 151 about the IETF Trust Trustees positions that are filled by the IETF 152 Nominating Committee (NomCom). 154 Section 5 of [I-D.ietf-iasa2-rfc4071bis] provides further details 155 about the IETF LLC Board Director positions that are filled by the 156 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 Board position and to nominate 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 nominated 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 Board position, 313 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 Board Director positions, and one of the 318 three nominated IETF Trust Trustee positions, each year. It is 319 recognized that circumstances may exist that will require the NomCom 320 to review more or less than the usual number of positions, e.g., if 321 the IESG, IAB, IETF Trust, or IETF LLC Board have reorganized prior 322 to this process and created new positions, if there are an odd number 323 of current positions, or if a member or Director unexpectedly 324 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 Board Director candidates are expected to serve at 334 least a three-year term, except if a nominating or selection body 335 decides to use a shorter term to allow for initial staggered 336 appointments. Please refer to Section 5 of 338 [I-D.ietf-iasa2-rfc4071bis] for additional guidance on terms length 339 and term limits for the IETF LLC Board. 341 Confirmed IETF Trust Trustee candidates are expected to serve at 342 least a three-year term, except if a nominating or selection body 343 decides to use a shorter term to allow for initial staggered 344 appointments. Please refer to Section 2. of 345 [I-D.ietf-iasa2-trust-update] for additional guidance on terms length 346 and term limits for the IETF Trust. 348 The term of a confirmed candidate selected according to the mid-term 349 vacancy rules may be less than a full term (two years for IESG and 350 IAB, three years for the IETF Trust and IETF LLC), as stated 351 elsewhere in this document. 353 It is consistent with this rule for the NomCom to choose one or more 354 of the currently open positions to which it may assign a term of not 355 more than three years in order to ensure the ideal application of 356 this rule in the future. 358 It is consistent with this rule for the NomCom to choose one or more 359 of the currently open positions that share responsibilities with 360 other positions (both those being reviewed and those sitting) to 361 which it may assign a term of not more than three years to ensure 362 that all such members or Directors will not be reviewed at the same 363 time. 365 All sitting member terms end during the First IETF meeting 366 corresponding to the end of the term for which they were confirmed. 367 All confirmed candidate terms begin during the First IETF meeting 368 corresponding to the beginning of the term for which they were 369 confirmed. 371 For confirmed candidates of the IESG, the terms begin no later than 372 when the currently sitting members' terms end on the last day of the 373 meeting. A term may begin or end no sooner than the first day of the 374 meeting and no later than the last day of the meeting as determined 375 by the mutual agreement of the currently sitting member and the 376 confirmed candidate. A confirmed candidate's term may overlap the 377 sitting member's term during the meeting as determined by their 378 mutual agreement. 380 For confirmed candidates of the IAB, the terms overlap with the terms 381 of the sitting members for the entire week of the meeting. 383 For confirmed Trustee candidates of the IETF Trust, the term begins 384 at the next IETF Trust meeting or as dictated by the policies and 385 procedures of the IETF Trust. 387 For confirmed Director candidates of the IETF LLC, the term begins at 388 the next appropriate IETF LLC Board meeting or as dictated by the 389 policies and procedures of the IETF LLC Board. 391 For candidates confirmed under the mid-term vacancy rules, the term 392 begins as soon as possible after the confirmation. 394 3.5. Mid-term Vacancies 396 Mid-term vacancies are filled by the same rules as documented here 397 with four qualifications, namely: 399 1. When there is only one official NomCom, the body with the mid- 400 term vacancy relegates the responsibility to fill the vacancy to 401 it. If the mid-term vacancy occurs during the period of time 402 that the term of the prior year's NomCom overlaps with the term 403 of the current year's NomCom, the body with the mid-term vacancy 404 must relegate the responsibility to fill the vacancy to the prior 405 year's NomCom. 407 2. If it is the case that the NomCom is reconvening to fill the mid- 408 term vacancy, then the completion of the candidate selection and 409 confirmation process is due within six weeks, with all other time 410 periods otherwise unspecified prorated accordingly. 412 3. The confirming body has two weeks from the day it is notified of 413 a candidate to reject the candidate, otherwise the candidate is 414 assumed to have been confirmed. 416 4. The term of the confirmed candidate will be either: 418 A. the remainder of the term of the open position if that 419 remainder is not less than one year or 421 B. the remainder of the term of the open position plus the next 422 two-year term if that remainder is less than one year. 424 In both cases, a year is the period of time from a First IETF meeting 425 to the next First IETF meeting. 427 3.6. Confidentiality 429 All deliberations and supporting information that relates to specific 430 nominees, candidates, and confirmed candidates are confidential. 432 The NomCom and confirming body members will be exposed to 433 confidential information as a result of their deliberations, their 434 interactions with those they consult, and from those who provide 435 requested supporting information. All members and all other 436 participants are expected to handle this information in a manner 437 consistent with its sensitivity. 439 It is consistent with this rule for current NomCom members who have 440 served on prior NomComs to advise the current committee on 441 deliberations and results of the prior committee, as necessary and 442 appropriate. 444 The list of nominees willing to be considered for positions under 445 review in the current NomCom cycle is not confidential. The NomCom 446 may disclose a list of names of nominees who are willing to be 447 considered for positions under review to the community, in order to 448 obtain feedback from the community on these nominees. 450 The list of nominees disclosed for a specific position should contain 451 only the names of nominees who are willing to be considered for the 452 position under review. 454 The NomCom may choose not to include some names in the disclosed 455 list, at their discretion. 457 The NomCom may disclose an updated list, at its discretion. For 458 example, the NomCom might disclose an updated list if it identifies 459 errors/omissions in a previously disclosed version of the disclosed 460 list, or if the NomCom finds it necessary to call for additional 461 nominees, and these nominees indicate a willingness to be considered 462 before the NomCom has completed its deliberations. 464 Nominees may choose to ask people to provide feedback to the NomCom 465 but should not encourage any public statements of support. NomComs 466 should consider nominee-encouraged lobbying and campaigning to be 467 unacceptable behavior. 469 IETF community members are encouraged to provide feedback on nominees 470 to the NomCom but should not post statements of support/non-support 471 for nominees in any public forum. 473 3.7. Advice and Consent Model 475 Unless otherwise specified, the advice and consent model is used 476 throughout the process. This model is characterized as follows. 478 3.7.1. Positions To Be Reviewed 480 The chair of the IESG, IAB, IETF Trust and IETF LLC Board each 481 informs the NomCom of their respective positions to be reviewed. 483 The IESG, IAB, IETF Trust and IETF LLC are responsible for providing 484 a summary of the expertise desired of the candidates selected for 485 their respective open positions. The summaries are provided to the 486 NomCom for its consideration. 488 3.7.2. Candidate Selection 490 The NomCom selects candidates based on its understanding of the IETF 491 community's consensus of the qualifications required and advises each 492 confirming body of its respective candidates. 494 3.7.3. Candidate Review 496 The confirming bodies review their respective candidates, they may at 497 their discretion communicate with the NomCom, and then consent to 498 some, all, or none of the candidates. 500 The sitting IAB members review the IESG candidates. 502 The Internet Society Board of Trustees reviews the IAB candidates. 504 The sitting IESG members review the IETF Trust Trustee Candidates. 506 The IETF LLC Board candidate is reviewed as specified in 507 [I-D.ietf-iasa2-rfc4071bis]. 509 The confirming bodies conduct their review using all information and 510 any means acceptable to them, including but not limited to the 511 supporting information provided by the NomCom, information known 512 personally to members of the confirming bodies and shared within the 513 confirming body, the results of interactions within the confirming 514 bodies, and the confirming bodies' interpretation of what is in the 515 best interests of the IETF community. 517 If all of the candidates are confirmed, the job of the NomCom with 518 respect to those open positions is complete. 520 If some or none of the candidates submitted to a confirming body are 521 confirmed, the confirming body should communicate with the NomCom 522 both to explain the reason why all the candidates were not confirmed 523 and to understand the NomCom's rationale for its candidates. 525 The confirming body may reject individual candidates, in which case 526 the NomCom must select alternate candidates for the rejected 527 candidates. 529 Any additional time required by the NomCom should not exceed its 530 maximum time allotment. 532 3.7.4. Confirmation 534 A confirming body decides whether it confirms each candidate using a 535 confirmation decision rule chosen by the confirming body. 537 If a confirming body has no specific confirmation decision rule, then 538 confirming a given candidate should require at least one-half of the 539 confirming body's sitting members to agree to that confirmation. 541 The decision may be made by conducting a formal vote, by asserting 542 consensus based on informal exchanges (e.g., email), or by any other 543 mechanism that is used to conduct the normal business of the 544 confirming body. 546 Regardless of which decision rule the confirming body uses, any 547 candidate that is not confirmed under that rule is considered to be 548 rejected. 550 The confirming body must make its decision within a reasonable time 551 frame. The results from the confirming body must be reported 552 promptly to the NomCom. 554 3.8. Sitting Members and Directors 556 The following rules apply to nominees and candidates who are 557 currently sitting members of the IESG or IAB, or IETF LLC Board 558 Directors and who are not sitting in an open position being filled by 559 the NomCom. 561 The confirmation of a candidate to an open position does not 562 automatically create a vacancy in the IESG, IAB, IETF Trust, or IETF 563 LLC Board position currently occupied by the candidate. The mid-term 564 vacancy cannot exist until, first, the candidate formally resigns 565 from the current position and, second, the body with the vacancy 566 formally decides for itself that it wants the NomCom to fill the mid- 567 term vacancy according to the rules for a mid-term vacancy documented 568 elsewhere in this document. 570 The resignation should be effective as of when the term of the new 571 position begins. The resignation may remain confidential to the 572 IESG, IAB, IETF Trust, IETF LLC Board, and NomCom until the confirmed 573 candidate is announced for the new position. The process, according 574 to rules set out elsewhere in this document, of filling the seat 575 vacated by the confirmed candidate may begin as soon as the vacancy 576 is publicly announced. 578 Filling a mid-term vacancy is a separate and independent action from 579 the customary action of filling open positions. In particular, a 580 NomCom must complete its job with respect to filling the open 581 positions and then separately proceed with the task of filling the 582 mid-term vacancy according to the rules for a mid-term vacancy 583 documented elsewhere in this document. 585 However, the following exception is permitted in the case where the 586 candidate for an open position is currently a sitting member of the 587 IAB. It is consistent with these rules for the announcements of a 588 resignation of a sitting member of the IAB and of the confirmed 589 candidate for the mid-term vacancy created by that sitting member on 590 the IAB to all occur at the same time as long as the actual sequence 591 of events that occurred did so in the following order: 593 1. The NomCom completes the advice and consent process for the open 594 position being filled by the candidate currently sitting on the 595 IAB. 597 2. The newly confirmed candidate resigns from their current position 598 on the IAB. 600 3. The IAB Chair (or the Managing Director, IETF Secretariat, if no 601 Chair has been named or the vacancy was created via the departure 602 of the IAB Chair) informs the NomCom of the mid-term vacancy. 604 4. The NomCom acts on the request to fill the mid-term vacancy. 606 3.9. Announcements 608 All announcements must be made using at least the mechanism used by 609 the IETF Secretariat for its announcements, including a notice on the 610 IETF web site. 612 As of the publication of this document, the current mechanism is an 613 email message to both the "ietf" and the "ietf-announce" mailing 614 lists. 616 4. Nominating Committee Selection 618 The following set of rules apply to the creation of the NomCom and 619 the selection of its members. 621 4.1. Timeline 623 The completion of the process of selecting and organizing the members 624 of the NomCom is due within three months. 626 The completion of the selection and organization process is due at 627 least one month prior to the Third IETF. This ensures the NomCom is 628 fully operational and available for interviews and consultation 629 during the Third IETF. 631 4.2. Term 633 The term of a NomCom is expected to be 15 months. 635 It is the intent of this rule that the end of a NomCom's term overlap 636 by approximately three months the beginning of the term of the next 637 NomCom. 639 The term of a NomCom begins when its members are officially 640 announced. The term ends at the Third IETF (not three meetings), 641 i.e., the IETF meeting after the next NomCom's term begins. 643 A term is expected to begin at least two months prior to the Third 644 IETF to ensure the NomCom has at least one month to get organized 645 before preparing for the Third IETF. 647 A NomCom is expected to complete any work in progress before it is 648 dissolved at the end of its term. 650 During the period of time when the terms of the NomComs overlap, all 651 mid-term vacancies are to be relegated to the prior year's NomCom. 652 The prior year's NomCom has no other responsibilities during the 653 overlap period. At all times other than the overlap period, there is 654 exactly one official NomCom and it is responsible for all mid-term 655 vacancies. 657 When the prior year's NomCom is filling a mid-term vacancy during the 658 period of time that the terms overlap, the NomCom operate 659 independently. However, some coordination is needed between them. 660 Since the prior year's Chair is a non-voting advisor to the current 661 NomCom, the coordination is expected to be straightforward. 663 4.3. Structure 665 The NomCom comprises at least a Chair, 10 voting volunteers, two 666 liaisons, and an advisor. 668 Any committee member may propose the addition of an advisor to 669 participate in some or all of the deliberations of the committee. 670 The addition must be approved by the committee according to its 671 established voting mechanism. Advisors participate as individuals. 673 Committee members are encouraged to propose the addition of 674 advisor(s) who are knowledgeable about the operations of the IETF 675 Trust and/or IETF LLC Board, whether or not that NomCom is reviewing 676 an IETF Trust Trustee or IETF LLC Board Director position. The 677 NomCom may choose to ask the IETF Trust and/or IETF LLC Board to 678 suggest advisors who are knowledgeable about their operations but may 679 select any advisor they vote to approve. 681 Any committee member may propose the addition of a liaison from other 682 unrepresented organizations to participate in some or all of the 683 deliberations of the committee. The addition must be approved by the 684 committee according to its established voting mechanism. Liaisons 685 participate as representatives of their respective organizations. 687 The Chair is selected according to rules stated elsewhere in this 688 document. 690 The 10 voting volunteers are selected according to rules stated 691 elsewhere in this document. 693 The IESG and IAB liaisons are selected according to rules stated 694 elsewhere in this document. 696 The Internet Society Board of Trustees may appoint a liaison to the 697 NomCom at its own discretion. 699 The IETF Trust may appoint a liaison to the NomCom at its own 700 discretion. 702 The IETF LLC Board may appoint a liaison to the NomCom at its own 703 discretion. 705 The Chair of last year's NomCom serves as an advisor according to 706 rules stated elsewhere in this document. 708 The Chair, liaisons, and advisors do not vote on the selection of 709 candidates. They do vote on all other issues before the committee 710 unless otherwise specified in this document. 712 4.4. Chair Duties 714 The Chair of the NomCom is responsible for ensuring the NomCom 715 completes its assigned duties in a timely fashion and performs in the 716 best interests of the IETF community. 718 The Chair must be thoroughly familiar with the rules and guidance 719 indicated throughout this document. The Chair must ensure the NomCom 720 completes its assigned duties in a manner that is consistent with 721 this document. 723 The Chair must attest by proclamation at a plenary session of the 724 First IETF that the results of the committee represent its best 725 effort and the best interests of the IETF community. 727 The Chair does not vote on the selection of candidates. 729 4.5. Chair Selection 731 The Internet Society President appoints the Chair, who must meet the 732 same requirements for membership in the NomCom as a voting volunteer. 734 The NomCom Chair must agree to invest the time necessary to ensure 735 that the NomCom completes its assigned duties and to perform in the 736 best interests of the IETF community in that role. 738 The appointment is due no later than the Second IETF meeting to 739 ensure it can be announced during a plenary session at that meeting. 740 The completion of the appointment is necessary to ensure the annual 741 process can complete at the time specified elsewhere in this 742 document. 744 4.6. Temporary Chair 746 A Chair, in consultation with the Internet Society President, may 747 appoint a temporary substitute for the Chair position. 749 There are a variety of ordinary circumstances that may arise from 750 time to time that could result in a Chair being unavailable to 751 oversee the activities of the committee. The Chair, in consultation 752 with the Internet Society President, may appoint a substitute from a 753 pool comprised of the liaisons currently serving on the committee and 754 the prior year's Chair or designee. 756 Any such appointment must be temporary and does not absolve the Chair 757 of any or all responsibility for ensuring the NomCom completes its 758 assigned duties in a timely fashion. 760 4.7. Liaisons 762 Liaisons are responsible for ensuring the NomCom in general and the 763 Chair in particular execute their assigned duties in the best 764 interests of the IETF community. 766 Liaisons are expected to represent the views of their respective 767 organizations during the deliberations of the committee. They should 768 provide information as requested or when they believe it would be 769 helpful to the committee. 771 Liaisons are expected to provide information to the NomCom regarding 772 the operation, responsibility, and composition of their respective 773 bodies. 775 Liaisons are expected to convey questions from the committee to their 776 respective organizations and responses to those questions to the 777 committee, as requested by the committee. 779 Liaisons are expected to review the operation and executing process 780 of the NomCom and to report any concerns or issues to the Chair of 781 the NomCom immediately. If they cannot resolve the issue between 782 themselves, liaisons must report it according to the dispute 783 resolution process stated elsewhere in this document. 785 Liaisons from confirming bodies are expected to assist the committee 786 in preparing the testimony it is required to provide with its 787 candidates. 789 Liaisons may have other NomCom responsibilities as required by their 790 respective organizations or requested by the NomCom, except that such 791 responsibilities may not conflict with any other provisions of this 792 document. 794 Liaisons do not vote on the selection of candidates. 796 4.8. Liaison Appointment 798 The sitting IAB and IESG members each appoint a liaison from their 799 current membership, someone who is not sitting in an open position, 800 to serve on the NomCom. 802 The sitting IETF Trust Trustees and IETF LLC Board Directors each may 803 appoint a liaison from their current membership, someone who is not 804 sitting in an open position, to serve on the NomCom. 806 4.9. Advisors 808 An advisor is responsible for such duties as specified by the 809 invitation that resulted in the appointment. 811 Advisors do not vote on the selection of candidates. 813 4.10. Past Chair 815 The Chair of the prior year's NomCom serves as an advisor to the 816 current committee. 818 The prior year's Chair is expected to review the actions and 819 activities of the current Chair and to report any concerns or issues 820 to the NomCom Chair immediately. If they cannot resolve the issue 821 between themselves, the prior year's Chair must report it according 822 to the dispute resolution process stated elsewhere in this document. 824 The prior year's Chair may select a designee from a pool composed of 825 the voting volunteers of the prior year's committee and all prior 826 Chairs if the Chair is unavailable. If the prior year's Chair is 827 unavailable or is unable or unwilling to make such a designation in a 828 timely fashion, the Chair of the current year's committee may select 829 a designee in consultation with the Internet Society President. 831 Selecting a prior year's committee member as the designee permits the 832 experience of the prior year's deliberations to be readily available 833 to the current committee. Selecting an earlier prior year Chair as 834 the designee permits the experience of being a Chair as well as that 835 Chair's committee deliberations to be readily available to the 836 current committee. 838 All references to "prior year's Chair" in this document refer to the 839 person serving in that role, whether it is the actual prior year's 840 Chair or a designee. 842 4.11. Voting Volunteers 844 Voting volunteers are responsible for completing the tasks of the 845 NomCom in a timely fashion. 847 Each voting volunteer is expected to participate in all activities of 848 the NomCom with a level of effort approximately equal to all other 849 voting volunteers. Specific tasks to be completed are established 850 and managed by the Chair according to rules stated elsewhere in this 851 document. 853 4.12. Milestones 855 The Chair must establish and announce milestones for the selection of 856 the NomCom members. 858 There is a defined time period during which the selection process is 859 due to be completed. The Chair must establish a set of milestones 860 which, if met in a timely fashion, will result in the completion of 861 the process on time. 863 4.13. Open Positions 865 The Chair (or the Managing Director, IETF Secretariat, if no Chair 866 has been named four weeks after the First IETF meeting of the year) 867 obtains the list of positions to be reviewed and announces it along 868 with a solicitation for names of volunteers from the IETF community 869 willing to serve on the NomCom. 871 If the Managing Director, IETF Secretariat issues the solicitation 872 for volunteers, the Managing Director, IETF Secretariat must also 873 collect responses to the solicitation and provide the names of 874 volunteers to the incoming NomCom Chair when the incoming NomCom 875 Chair is named. 877 At the Chair's request, the IETF Secretariat may perform other 878 clerical support tasks, as long as the task being performed does not 879 require NomCom Chair judgment, in the NomCom Chair's opinion, and as 880 long as the community is appropriately notified that this request is 881 being made. This request may come from the incoming NomCom Chair (if 882 one has been selected for this NomCom cycle) or the previous NomCom 883 Chair (if the search for an incoming NomCom Chair is still underway). 885 The solicitation must permit the community at least 30 days during 886 which they may choose to volunteer to be selected for the NomCom. 888 The list of open positions is published with the solicitation to 889 facilitate community members choosing between volunteering for an 890 open position and volunteering for the NomCom. 892 4.14. Volunteer Qualification 894 Members of the IETF community must have attended at least three of 895 the last five IETF meetings in order to volunteer. 897 The five meetings are the five most recent meetings that ended prior 898 to the date on which the solicitation for NomCom volunteers was 899 submitted for distribution to the IETF community. 901 The IETF Secretariat is responsible for confirming that volunteers 902 have met the attendance requirement. 904 Volunteers must provide their full name, email address, and primary 905 company or organization affiliation (if any) when volunteering. 907 Volunteers are expected to be familiar with the IETF processes and 908 procedures, which are readily learned by active participation in a 909 working group and especially by serving as a document editor or 910 working group chair. 912 4.15. Not Qualified 914 Any person who serves on the Internet Society Board of Trustees, the 915 IETF Trust, the IETF LLC Board of Directors, the IAB, or the IESG, 916 including those who serve on these bodies in ex officio positions, 917 may not volunteer to serve as voting members of the NomCom. In 918 addition, employees or contractors of the IETF LLC may not volunteer 919 to serve as voting members of the NomCom. Liaisons to these bodies 920 from other bodies or organizations are not excluded by this rule. 922 4.16. Selection Process 924 The Chair announces both the list of the pool of volunteers from 925 which the 10 voting volunteers will be randomly selected and the 926 method with which the selection will be completed. 928 The announcement should be made at least one week prior to the date 929 on which the random selection will occur. 931 The pool of volunteers must be enumerated or otherwise indicated 932 according to the needs of the selection method to be used. 934 The announcement must specify the data that will be used as input to 935 the selection method. The method must depend on random data whose 936 value is not known or available until the date on which the random 937 selection will occur. 939 It must be possible to independently verify that the selection method 940 used is both fair and unbiased. A method is fair if each eligible 941 volunteer is equally likely to be selected. A method is unbiased if 942 no one can influence its outcome in favor of a specific outcome. 944 It must be possible to repeat the selection method, either through 945 iteration or by restarting in such a way as to remain fair and 946 unbiased. This is necessary to replace selected volunteers should 947 they become unavailable after selection. 949 The selection method must produce an ordered list of volunteers. 951 One possible selection method is described in [RFC3797]. 953 4.17. Announcement of Selection Results 955 The Chair randomly selects the 10 voting volunteers from the pool of 956 names of volunteers and announces the members of the NomCom. 958 No more than two volunteers with the same primary affiliation may be 959 selected for the NomCom. The Chair reviews the primary affiliation 960 of each volunteer selected by the method in turn. If the primary 961 affiliation for a volunteer is the same as two previously selected 962 volunteers, that volunteer is removed from consideration and the 963 method is repeated to identify the next eligible volunteer. 965 There must be at least two announcements of all members of the 966 NomCom. 968 The first announcement should occur as soon after the random 969 selection as is reasonable for the Chair. The community must have at 970 least one week during which any member may challenge the results of 971 the random selection. 973 The challenge must be made in writing (email is acceptable) to the 974 Chair. The Chair has 48 hours to review the challenge and offer a 975 resolution to the member. If the resolution is not accepted by the 976 member, that member may report the challenge according to the dispute 977 resolution process stated elsewhere in this document. 979 If a selected volunteer, upon reading the announcement with the list 980 of selected volunteers, finds that two or more other volunteers have 981 the same affiliation, then the volunteer should notify the Chair who 982 will determine the appropriate action. 984 During at least the one week challenge period, the Chair must contact 985 each of the members and confirm their willingness and availability to 986 serve. The Chair should make every reasonable effort to contact each 987 member. 989 o If the Chair is unable to contact a liaison, the problem is 990 referred to the respective organization to resolve. The Chair 991 should allow a reasonable amount of time for the organization to 992 resolve the problem and then may proceed without the liaison. 994 o If the Chair is unable to contact an advisor, the Chair may elect 995 to proceed without the advisor, except for the prior year's Chair 996 for whom the Chair must consult with the Internet Society 997 President as stated elsewhere in this document. 999 o If the Chair is unable to contact a voting volunteer, the Chair 1000 must repeat the random selection process in order to replace the 1001 unavailable volunteer. There should be at least one day between 1002 the announcement of the iteration and the selection process. 1004 After at least one week and confirming that 10 voting volunteers are 1005 ready to serve, the Chair makes the second announcement of the 1006 members of the NomCom, which officially begins the term of the 1007 NomCom. 1009 4.18. Committee Organization 1011 The Chair works with the members of the committee to organize itself 1012 in preparation for completing its assigned duties. 1014 The committee has approximately one month during which it can self- 1015 organize. Its responsibilities during this time include but are not 1016 limited to the following: 1018 o Setting up a regular teleconference schedule. 1020 o Setting up an internal web site. 1022 o Setting up a mailing list for internal discussions. 1024 o Setting up an email address for receiving community input. 1026 o Establishing operational procedures. 1028 o Establishing milestones in order to monitor the progress of the 1029 selection process. 1031 5. Nominating Committee Operation 1033 The following rules apply to the operation of the NomCom. If 1034 necessary, a paragraph discussing the interpretation of each rule is 1035 included. 1037 The rules are organized approximately in the order in which they 1038 would be invoked. 1040 5.1. Discretion 1042 All rules and special circumstances not otherwise specified are at 1043 the discretion of the committee. 1045 Exceptional circumstances will occasionally arise during the normal 1046 operation of the NomCom. This rule is intended to foster the 1047 continued forward progress of the committee. 1049 Any member of the committee may propose a rule for adoption by the 1050 committee. The rule must be approved by the committee according to 1051 its established voting mechanism. 1053 All members of the committee should consider whether the exception is 1054 worthy of mention in the next revision of this document and follow-up 1055 accordingly. 1057 5.2. Selection Timeline 1059 The completion of the process of selecting candidates to be confirmed 1060 by their respective confirming body is due within three months. 1062 The completion of the selection process is due at least two months 1063 prior to the First IETF. This ensures the NomCom has sufficient time 1064 to complete the confirmation process. 1066 5.3. Confirmation Timeline 1068 The completion of the process of confirming the candidates is due 1069 within one month. 1071 The completion of the confirmation process is due at least one month 1072 prior to the First IETF. 1074 5.4. Milestones 1076 The Chair must establish a set of NomCom milestones for the candidate 1077 selection and confirmation process. 1079 There is a defined time period during which the candidate selection 1080 and confirmation process must be completed. The Chair must establish 1081 a set of milestones that, if met in a timely fashion, will result in 1082 the completion of the process on time. The Chair should allow time 1083 for iterating the activities of the committee if one or more 1084 candidates are not confirmed. 1086 The Chair should ensure that all committee members are aware of the 1087 milestones. 1089 5.5. Voting Mechanism 1091 The Chair must establish a voting mechanism. 1093 The committee must be able to objectively determine when a decision 1094 has been made during its deliberations. The criteria for determining 1095 closure must be established and known to all members of the NomCom. 1097 5.6. Voting Quorum 1099 At least a quorum of committee members must participate in a vote. 1101 Only voting volunteers vote on a candidate selection. For a 1102 candidate selection vote, a quorum is comprised of at least seven of 1103 the voting volunteers. 1105 At all other times, a quorum is present if at least 75% of the NomCom 1106 members are participating. 1108 5.7. Voting Member Recall 1110 Any member of the NomCom may propose to the committee that any other 1111 member except the Chair be recalled. The process for recalling the 1112 Chair is defined elsewhere in this document. 1114 There are a variety of ordinary circumstances that may arise that 1115 could result in one or more members of the committee being 1116 unavailable to complete their assigned duties, for example, health 1117 concerns, family issues, or a change of priorities at work. A 1118 committee member may choose to resign for unspecified personal 1119 reasons. In addition, the committee may not function well as a group 1120 because a member may be disruptive or otherwise uncooperative. 1122 Regardless of the circumstances, if individual committee members 1123 cannot work out their differences between themselves, the entire 1124 committee may be called upon to discuss and review the circumstances. 1125 If a resolution is not forthcoming, a vote may be conducted. A 1126 member may be recalled if at least a quorum of all committee members 1127 agree, including the vote of the member being recalled. 1129 If a liaison member is recalled, the committee must notify the 1130 affected organization and must allow a reasonable amount of time for 1131 a replacement to be identified by the organization before proceeding. 1133 If an advisor member other than the prior year's Chair is recalled, 1134 the committee may choose to proceed without the advisor. In the case 1135 of the prior year's Chair, the Internet Society President must be 1136 notified and the current Chair must be allowed a reasonable amount of 1137 time to consult with the Internet Society President to identify a 1138 replacement before proceeding. 1140 If a single voting volunteer position on the NomCom is vacated, 1141 regardless of the circumstances, the committee may choose to proceed 1142 with only nine voting volunteers at its own discretion. In all other 1143 cases, a new voting member must be selected, and the Chair must 1144 repeat the random selection process including an announcement of the 1145 iteration prior to the actual selection as stated elsewhere in this 1146 document. 1148 A change in the primary affiliation of a voting volunteer during the 1149 term of the NomCom is not a cause to request the recall of that 1150 volunteer, even if the change would result in more than two voting 1151 volunteers with the same affiliation. 1153 5.8. Chair Recall 1155 Only the prior year's Chair may request the recall of the current 1156 Chair. 1158 It is the responsibility of the prior year's Chair to ensure the 1159 current Chair completes the assigned tasks in a manner consistent 1160 with this document and in the best interests of the IETF community. 1162 Any member of the committee who has an issue or concern regarding the 1163 Chair should report it to the prior year's Chair immediately. The 1164 prior year's Chair is expected to report it to the Chair immediately. 1165 If they cannot resolve the issue between themselves, the prior year's 1166 Chair must report it according to the dispute resolution process 1167 stated elsewhere in this document. 1169 5.9. Deliberations 1171 All members of the NomCom may participate in all deliberations. 1173 The emphasis of this rule is that no member can be explicitly 1174 excluded from any deliberation. However, a member may individually 1175 choose not to participate in a deliberation. 1177 5.10. Call for Nominees 1179 The Chair announces the open positions to be reviewed, the desired 1180 expertise provided by the Managing Director, IETF Secretariat, and 1181 the call for nominees. 1183 The call for nominees must include a request for comments regarding 1184 the past performance of incumbents, which will be considered during 1185 the deliberations of the NomCom. 1187 The call must request that a nomination include a valid, working 1188 email address, a telephone number, or both for the nominee. The 1189 nomination must include the set of skills or expertise the nominator 1190 believes the nominee has that would be desirable. 1192 5.11. Nominations 1194 Any member of the IETF community may nominate any member of the IETF 1195 community for any open position, whose eligibility to serve will be 1196 confirmed by the NomCom. 1198 A self-nomination is permitted. 1200 NomCom members are not eligible to be considered for filling any open 1201 position by the NomCom on which they serve. They become ineligible 1202 as soon as the term of the NomCom on which they serve officially 1203 begins. They remain ineligible for the duration of that NomCom's 1204 term. 1206 Although each NomCom's term overlaps with the following NomCom's 1207 term, NomCom members are eligible for nomination by the following 1208 committee if not otherwise disqualified. 1210 Members of the IETF community who were recalled from any IESG, IAB, 1211 IETF Trust, or IETF LLC Board position during the previous two years 1212 are not eligible to be considered for filling any open position. 1214 5.12. Candidate Selection 1216 The NomCom selects candidates based on its understanding of the IETF 1217 community's consensus of the qualifications required to fill the open 1218 positions. 1220 The intent of this rule is to ensure that the NomCom consults with a 1221 broad base of the IETF community for input to its deliberations. In 1222 particular, the NomCom must determine if the desired expertise for 1223 the open positions matches its understanding of the qualifications 1224 desired by the IETF community. 1226 The consultations are permitted to include names of nominees, if all 1227 parties to the consultation agree to observe the same confidentiality 1228 rules as the NomCom itself, or the names are public as discussed in 1229 Section 3.6. Feedback on individual nominees should always be 1230 confidential. 1232 A broad base of the community should include the existing members of 1233 the IESG and IAB, IETF Trust Trustees, and IETF LLC Board Directors, 1234 especially sitting members who share responsibilities with open 1235 positions, e.g., co-Area Directors, and working group chairs, 1236 especially those in the areas with open positions. 1238 Only voting volunteer members vote to select candidates. 1240 5.13. Consent to Nomination 1242 Nominees should be advised that they are being considered and must 1243 consent to their nomination prior to being chosen as candidates. 1245 Although the NomCom will make every reasonable effort to contact and 1246 to remain in contact with nominees, any nominee whose contact 1247 information changes during the process and who wishes to still be 1248 considered should inform the NomCom of the changes. 1250 A nominee's consent must be written (email is acceptable) and must 1251 include a commitment to provide the resources necessary to fill the 1252 open position and an assurance that the nominee will perform the 1253 duties of the position for which they are being considered in the 1254 best interests of the IETF community. 1256 Consenting to a nomination must occur prior to a nominee being a 1257 candidate and may occur as soon after the nomination as needed by the 1258 NomCom. 1260 Consenting to a nomination must not imply the nominee will be a 1261 candidate. 1263 The NomCom should help nominees provide justification to their 1264 employers. 1266 5.14. Notifying Confirming Bodies 1268 The NomCom advises the confirming bodies of their candidates, 1269 specifying a single candidate for each open position and testifying 1270 as to how each candidate meets the qualifications of an open 1271 position. 1273 For each candidate, the testimony must include a brief statement of 1274 the qualifications for the position that is being filled, which may 1275 be exactly the expertise that was requested. If the qualifications 1276 differ from the expertise originally requested, a brief statement 1277 explaining the difference must be included. 1279 The testimony may include a brief resume of the candidate and/or a 1280 brief summary of the deliberations of the NomCom. 1282 5.15. Confirming Candidates 1284 Confirmed candidates must consent to their confirmation, and rejected 1285 candidates and nominees must be notified before confirmed candidates 1286 are announced. 1288 It is not necessary to notify and get consent from all confirmed 1289 candidates together. 1291 A nominee may not know they were a candidate. This permits a 1292 candidate to be rejected by a confirming body without the nominee 1293 knowing about the rejection. 1295 Rejected nominees, who consented to their nomination, and rejected 1296 candidates must be notified prior to announcing the confirmed 1297 candidates. 1299 It is not necessary to announce all confirmed candidates together. 1301 The NomCom must ensure that all confirmed candidates are prepared to 1302 serve prior to announcing their confirmation. 1304 5.16. Archives 1306 The NomCom should archive the information it has collected or 1307 produced for a period of time but not to exceed its term. 1309 The purpose of the archive is to assist the NomCom should it be 1310 necessary for it to fill a mid-term vacancy. 1312 The existence of an archive, how it is implemented, and what 1313 information to archive is at the discretion of the committee. The 1314 decision must be approved by a quorum of the voting volunteer 1315 members. 1317 The implementation of the archive should make every reasonable effort 1318 to ensure that the confidentiality of the information it contains is 1319 maintained. 1321 6. Dispute Resolution Process 1323 The dispute resolution process described here is to be used as 1324 indicated elsewhere in this document. Its applicability in other 1325 circumstances is beyond the scope of this document. 1327 The NomCom operates under a strict rule of confidentiality. For this 1328 reason, when process issues arise, it is best to make every 1329 reasonable effort to resolve them within the committee. However, 1330 when circumstances do not permit this, or no resolution is 1331 forthcoming, the process described here is to be used. 1333 The following rules apply to the process. 1335 1. The results of this process are final and binding. There is no 1336 appeal. 1338 2. The process begins with the submission of a request as described 1339 below to the Internet Society President. 1341 3. As soon as the process begins, the NomCom may continue those 1342 activities that are unrelated to the issue to be resolved except 1343 that it must not submit any candidates to a confirming body until 1344 the issue is resolved. 1346 4. All parties to the process are subject to the same 1347 confidentiality rules as each member of the NomCom. 1349 5. The process should be completed within two weeks. 1351 The process is as follows: 1353 1. The party seeking resolution submits a written request (email is 1354 acceptable) to the Internet Society President detailing the issue 1355 to be resolved. 1357 2. The Internet Society President appoints an arbiter to investigate 1358 and resolve the issue. A self-appointment is permitted. 1360 3. The arbiter investigates the issue making every reasonable effort 1361 to understand both sides of the issue. Since the arbiter is 1362 subject to the same confidentiality obligations as all NomCom 1363 members, all members are expected to cooperate fully with the 1364 arbiter and to provide all relevant information to the arbiter 1365 for review. 1367 4. After consultation with the two principal parties to the issue, 1368 the arbiter decides on a resolution. Whatever actions are 1369 necessary to execute the resolution are immediately begun and 1370 completed as quickly as possible. 1372 5. The arbiter summarizes the issue, the resolution, and the 1373 rationale for the resolution for the Internet Society President. 1375 6. In consultation with the Internet Society President, the arbiter 1376 prepares a report of the dispute and its resolution. The report 1377 should include all information that in the judgment of the 1378 arbiter does not violate the confidentiality requirements of the 1379 NomCom. 1381 7. The Chair includes the dispute report when reporting on the 1382 activities of the NomCom to the IETF community. 1384 7. Member, Trustee, and Director Recall 1386 The following rules apply to the recall process. If necessary, a 1387 paragraph discussing the interpretation of each rule is included. 1389 It applies to IESG and IAB Members, the NomCom appointed IETF Trust 1390 Trustees, and the NomCom appointed IETF LLC Directors. 1392 7.1. Petition 1394 At any time, a signed petition (email is acceptable) may be submitted 1395 to the Internet Society President to request the recall of any 1396 sitting IESG or IAB member, or NomCom appointed IETF Trust Trustee, 1397 or NomCom appointed IETF LLC Director. There are two different types 1398 of petitions: a petition by participants of the IETF community, and a 1399 petition by the Ombudsteam as described in [RFC7776]. 1401 7.1.1. Community Petition 1403 A recall petition can be made by at least 20 members of the IETF 1404 community who are qualified to be voting members of a NomCom. All 1405 individual and collective qualifications of NomCom eligibility are 1406 applicable, including that no more than two signatories may have the 1407 same primary affiliation. 1409 Each signature must include a full name, email address, and primary 1410 company or organization affiliation. 1412 The IETF Secretariat is responsible for confirming that each 1413 signatory is qualified to be a voting member of a NomCom. A valid 1414 petition must be signed by at least 20 qualified signatories. 1416 The petition must include a statement of justification for the recall 1417 and all relevant and appropriate supporting documentation. 1419 The petition and its signatories must be announced to the IETF 1420 community. 1422 7.1.2. Ombudsteam Petition 1424 The Ombudsteam process allows the Ombudsteam to form a recall 1425 petition on its own without requiring 20 signatories from the 1426 community. As defined in [RFC7776], the petition and its signatories 1427 (the Ombudsteam) shall be announced to the IETF community, and a 1428 Recall Committee Chair shall be appointed to complete the Recall 1429 Committee process. It is expected that the Recall Committee will 1430 receive a briefing from the Ombudsteam explaining why recall is 1431 considered an appropriate remedy. 1433 7.2. Recall Committee Chair 1435 The Internet Society President shall appoint a Recall Committee 1436 Chair. 1438 The Internet Society President must not evaluate the recall request. 1439 It is explicitly the responsibility of the IETF community to evaluate 1440 the behavior of its leaders. 1442 7.3. Recall Committee Creation 1444 The recall committee is created according to the same rules as is the 1445 NomCom with the qualifications that both the person being 1446 investigated and the parties requesting the recall must not be a 1447 member of the recall committee in any capacity. 1449 7.4. Recall Committee Rules 1451 The recall committee operates according to the same rules as the 1452 NomCom with the qualification that there is no confirmation process. 1454 7.5. Recall Committee Operation 1456 The recall committee investigates the circumstances of the 1457 justification for the recall and votes on its findings. 1459 The investigation must include at least both an opportunity for the 1460 member being recalled to present a written statement and consultation 1461 with third parties. 1463 7.6. 3/4 Majority 1465 A 3/4 majority of the members who vote on the question is required 1466 for a recall. 1468 7.7. Position To Be Filled 1470 If a sitting member is recalled, the open position is to be filled 1471 according to the mid-term vacancy rules. 1473 8. IANA Considerations 1475 No IANA actions required. 1477 9. Security Considerations 1479 Any selection, confirmation, or recall process necessarily involves 1480 investigation into the qualifications and activities of prospective 1481 candidates. The investigation may reveal confidential or otherwise 1482 private information about candidates to those participating in the 1483 process. Each person who participates in any aspect of the process 1484 must maintain the confidentiality of any and all information not 1485 explicitly identified as suitable for public dissemination. 1487 When the NomCom decides it is necessary to share confidential or 1488 otherwise private information with others, the dissemination must be 1489 minimal and must include a prior commitment from all persons 1490 consulted to observe the same confidentiality rules as the NomCom 1491 itself. 1493 10. References 1495 10.1. Normative References 1497 [I-D.ietf-iasa2-consolidated-upd] 1498 Klensin, J., "Consolidated IASA 2.0 Updates of IETF 1499 Administrative Terminology", draft-ietf-iasa2- 1500 consolidated-upd-07 (work in progress), March 2019. 1502 [I-D.ietf-iasa2-rfc4071bis] 1503 Haberman, B., Hall, J., and J. Livingood, "Structure of 1504 the IETF Administrative Support Activity, Version 2.0", 1505 draft-ietf-iasa2-rfc4071bis-11 (work in progress), April 1506 2019. 1508 [I-D.ietf-iasa2-trust-update] 1509 Arkko, J. and T. Hardie, "Update to the Process for 1510 Selection of Trustees for the IETF Trust", draft-ietf- 1511 iasa2-trust-update-03 (work in progress), February 2019. 1513 [RFC3777] Galvin, J., Ed., "IAB and IESG Selection, Confirmation, 1514 and Recall Process: Operation of the Nominating and Recall 1515 Committees", RFC 3777, DOI 10.17487/RFC3777, June 2004, 1516 . 1518 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 1519 Confirmation, and Recall Process: Operation of the 1520 Nominating and Recall Committees", BCP 10, RFC 7437, DOI 1521 10.17487/RFC7437, January 2015, . 1524 [RFC7776] Resnick, P. and A. Farrel, "IETF Anti-Harassment 1525 Procedures", BCP 25, RFC 7776, DOI 10.17487/RFC7776, March 1526 2016, . 1528 10.2. Informative References 1530 [Err232] RFC Errata, "Erratum ID 232", RFC 3777. 1532 [Err4179] RFC Errata, "Erratum ID 4179", RFC 3777. 1534 [RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, DOI 10.17487/ 1535 RFC3710, February 2004, . 1538 [RFC3797] Eastlake 3rd, D., "Publicly Verifiable Nominations 1539 Committee (NomCom) Random Selection", RFC 3797, DOI 1540 10.17487/RFC3797, June 2004, . 1543 [RFC8318] Dawkins, S., "IAB, IESG, and IAOC Selection, Confirmation, 1544 and Recall Process: IAOC Advisor for the Nominating 1545 Committee", BCP 10, RFC 8318, DOI 10.17487/RFC8318, 1546 January 2018, . 1548 Appendix A. Changes Since RFC 3777 1550 o Converted source file from nroff to XML, resulting in some 1551 reformatting. 1553 o Applied errata for RFC 3777 ([Err232] and [Err4179]). 1555 o Applied RFC 5078 update. 1557 o Applied RFC 5633 update. 1559 o Applied RFC 5680 update. 1561 o Applied RFC 6859 update. 1563 o Corrected a few grammatical errors. 1565 o Added a reference to RFC 3710. 1567 Appendix B. Changes Since RFC 7437 1569 o Changed all mentions of the Internet Administrative Oversight 1570 committee (IAOC), and replaced it with the appropriate references 1571 to the IETF Administration LLC (IETF LLC). This included making 1572 changes on an as needed basis to some aspects of the process for 1573 the IETF LLC, in accordance with IASA2. 1575 o Revised definition of IETF Executive Director, and added 1576 definition of "Managing Director, IETF Secretariat". Changed text 1577 to "Managing Director, IETF Secretariat" where appropriate. 1579 o Added references to appropriate IASA2 documents. 1581 o Modified the Advice and Consent model to enable IESG, IAB, and 1582 IETF LLC to communicate directly with the NomCom rather than via 1583 the Managing Director, IETF Secretariat. 1585 o Updated removal text to reflect the new LLC rules, which enables 1586 removal via the LLC or the IETF recall process, except for the 1587 ISOC-appointed Director. 1589 o Updated the document to clarify that there are members of the IAB 1590 and IESG, Trustees of the IETF Trust, and Director of the IETF 1591 LLC. 1593 o Updated document to also specify procedures for the NomCom 1594 appointed IETF Trust Trustees. 1596 o Revised Abstract and Introduction to provide current context. 1598 o Changed "nominating committee" to "NomCom" throughout the document 1599 because it is what most use to describe the IETF Nominating 1600 Committee. 1602 o Added that the IETF Trust Trustees and IETF LLC Directors, each 1603 may appoint a liaison to the NomCom. 1605 o Incorporated the update to RFC7437 done by RFC7776. 1607 o Incorporated the update to RFC7437 done by [RFC8318] and updated 1608 it to refer to the IETF Trust and IETF LLC, instead of the IAOC. 1610 o Editorial changes. 1612 Appendix C. Oral Tradition 1614 Over the years, various NomComs have learned through oral tradition 1615 passed on by liaisons that there are certain consistencies in the 1616 process and information considered during deliberations. Some items 1617 from that oral tradition are collected here to facilitate its 1618 consideration by future NomComs. 1620 1. It has been found that experience as an IETF Working Group Chair 1621 or an IRTF Research Group Chair is helpful in giving a nominee 1622 experience of what the job of an Area Director involves. It also 1623 helps a NomCom judge the technical, people, and process 1624 management skills of the nominee. 1626 2. No person should serve both on the IAB and as an Area Director, 1627 except the IETF Chair whose roles as an IAB member and Area 1628 Director of the General Area are set out elsewhere. 1630 3. The strength of the IAB is found in part in the balance of the 1631 demographics of its members (e.g., national distribution, years 1632 of experience, gender, etc.), the combined skill set of its 1633 members, and the combined sectors (e.g., industry, academia, 1634 etc.) represented by its members. 1636 4. There are no term limits explicitly because the issue of 1637 continuity versus turnover should be evaluated each year 1638 according to the expectations of the IETF community, as it is 1639 understood by each NomCom. 1641 5. The number of NomCom members with the same primary affiliation is 1642 limited in order to avoid the appearance of improper bias in 1643 choosing the leadership of the IETF. Rather than defining 1644 precise rules for how to define "affiliation", the IETF community 1645 depends on the honor and integrity of the participants to make 1646 the process work. 1648 Appendix D. Nominating Committee Timeline 1650 This appendix is included for the convenience of the reader and is 1651 not to be interpreted as the definitive timeline. It is intended to 1652 capture the detail described elsewhere in this document in one place. 1653 Although every effort has been made to ensure the description here is 1654 consistent with the description elsewhere, if there are any conflicts 1655 the definitive rule is the one in the main body of this document. 1657 The only absolute in the timeline rules for the annual process is 1658 that its completion is due by the First IETF of the year after the 1659 NomCom begins its term. This is supported by the fact that the 1660 confirmed candidate terms begin during the week of the First IETF. 1662 The overall annual process is designed to be completed in seven 1663 months. It is expected to start nine months prior to the First IETF. 1664 The time is split between three major components of the process 1665 roughly as follows: 1667 1. First is the selection and organization of the committee members. 1668 Three months are allotted for this process. 1670 2. Second is the selection of the candidates by the NomCom. Four 1671 months are allotted for this process. 1673 3. Third is the confirmation of the candidates by their respective 1674 confirming bodies. Two months are allotted for this process. 1676 The following list captures the details of the milestones within each 1677 component. For illustrative purposes, the list presumes the Friday 1678 before the First IETF is March 1. Numbers shown in square brackets 1679 indicate the expected number of weeks at each step. 1681 1. BEGIN Eight Months Prior to First IETF (approx. June 1); 1682 Internet Society President appoints the Chair. The appointment 1683 must be done no later than the Second IETF or eight months prior 1684 to the First IETF, whichever comes first. The Chair must be 1685 announced and recognized during a plenary session of the Second 1686 IETF. [0] 1688 2. The Chair establishes and announces milestones to ensure the 1689 timely selection of the NomCom members. [1] 1691 3. The Chair contacts the IESG, IAB, and Internet Society Board of 1692 Trustees and requests a liaison. The Chair contacts the prior 1693 year's Chair and requests an advisor. The Chair obtains the 1694 list of IESG, IAB, IETF Trust, and IETF LLC open positions and 1695 descriptions from the chairs of each group. [0] 1697 4. The Chair announces the solicitation for voting volunteer 1698 members that must remain open for at least 30 days. The 1699 announcement must be done no later than seven months and two 1700 weeks prior to the First IETF (approx. June 15). [6] 1702 5. After the solicitation closes, the Chair announces the pool of 1703 volunteers and the date of the random selection, which must be 1704 at least one week in the future. The announcement must be done 1705 no later than six months and two weeks prior to the First IETF 1706 (approx. July 15). [1] 1708 6. On the appointed day, the random selection occurs and the Chair 1709 announces the members of the committee and the one week 1710 challenge period. The announcement must be done no later than 1711 six months and one week prior to the First IETF (approx. July 1712 22). [1] 1714 7. During the challenge period, the Chair contacts each of the 1715 committee members and confirms their availability to 1716 participate. [0] 1718 8. After the challenge period closes, the Chair announces the 1719 members of the committee and its term begins. The announcement 1720 must be done no later than six months prior to the First IETF 1721 (approx. August 1). [1] 1723 9. The committee has one month during which it is to self-organize 1724 in preparation for completing its assigned duties. This must be 1725 done no later than five months prior to the First IETF (approx. 1726 September 15). [6] 1728 10. END the Committee Member Selection Process; BEGIN the Selection 1729 of Candidates; Time is at least five months prior to the First 1730 IETF (approx. September 22). [0] 1732 11. The Chair establishes and announces the milestones to ensure the 1733 timely selection of the candidates, including a call for 1734 nominations for the open positions. The announcement must be 1735 done no later than five months prior to the First IETF (approx. 1736 October 1). [1] 1738 12. Over the next three months, the NomCom collects input and 1739 deliberates. It should plan to conduct interviews and other 1740 consultations during the Third IETF. The committee is due to 1741 complete its candidate selection no later than two months prior 1742 to the First IETF (approx. January 1). [17] 1744 13. END the Selection of Candidates; BEGIN the Confirmation of 1745 Candidates; Time is at least two months prior to the First IETF 1746 (approx. January 1). [0] 1748 14. The committee presents its candidates to their respective 1749 confirming bodies. The presentation must be done no later than 1750 two months prior to the First IETF (approx. January 1). [0] 1752 15. The confirming bodies have one month to deliberate and, in 1753 communication with the NomCom, accept or reject candidates. [4] 1755 16. The Chair notifies and advises unsuccessful nominees that they 1756 have not been selected. [1] 1758 17. The Chair announces the confirmed candidates. The announcement 1759 must be done no later than one month prior to the First IETF 1760 (approx. February 1). [4] 1762 Appendix E. Acknowledgments 1764 A great deal of work went into the RFCs that preceded this one. The 1765 2014 NomCom and this editor would like to thank all of them once 1766 again for the time and energy it took to get us to where we are now. 1767 In no particular order, we acknowledge: 1769 Jeff Case Fred Baker John Curran 1770 Guy Almes Geoff Huston Mike St. Johns 1771 Donald Eastlake Avri Doria Bernard Adoba 1772 Ted T'so Phil Roberts Jim Galvin 1773 Harald Alvestrand Leslie Daigle Joel Halpern 1774 Thomas Narten Spencer Dawkins Barry Leiba 1775 Lars Eggert Ross Callon Brian Carpenter 1776 Robert Elz Bernie Hoeneisen John Klensin 1777 Danny McPherson S. Moonesamy Scott Bradner 1778 Ralph Droms Pekka Savola 1780 Allison Mankin and Russ White provided early reviews and feedback 1781 about this document. 1783 Jari Arkko was very helpful by independently verifying that the 1784 previous text from all the merged documents was marshaled correctly 1785 into this one, and Adrian Farrel and Brian Carpenter caught the nits 1786 that fell through the cracks. 1788 Appendix F. Change log [RFC Editor: Please remove] 1790 draft-ietf-iasa2-rfc74337bis-08, 2019-June-26 1792 * Added a paragraph to Section 1 "Introduction" noting that this 1793 revision addresses only the changes required for IASA 2.0 and 1794 that should the community agree on other changes, they will be 1795 addressed in future documents. 1797 draft-ietf-iasa2-rfc74337bis-07, 2019-June-7 1799 * Added reference to [I-D.ietf-iasa2-consolidated-upd] in 1800 Section 2. 1801 * Changed reference to RFC3710 to Informational. 1802 * Removed step 3 from IAB mid-term vacancies in Section 3.8 as it 1803 was redundant with step 4. 1804 * Correct summary below for -06 version. 1805 * Editorial changes. 1807 draft-ietf-iasa2-rfc74337bis-06, 2019-March-26 1809 * Removed IETF LLC from the list of positions who don't have term 1810 limits in Section 3.2. 1811 * Added IETF Trust to the list of positions who can be recalled 1812 in Section 5.11. 1813 * Editorial changes. 1815 draft-ietf-iasa2-rfc74337bis-05, 2019-January-11: 1817 * Changed text to point to appropriate Sections of 1818 [I-D.ietf-iasa2-rfc4071bis]. 1819 * Editorial changes. 1821 draft-ietf-iasa2-rfc74337bis-04, 2019-January-3: 1823 * Added IETF Trust to the title. 1824 * Changed references to point to current IASA 2.0 structure 1825 document [I-D.ietf-iasa2-rfc4071bis] 1826 * Added IETF Trust to a few places it was missing. 1827 * Editorial changes. 1829 draft-ietf-iasa2-rfc74337bis-03, 2018-October-22: 1831 * Revised Section 7 to focus on repeal of the the NomCom appoint 1832 LLC Director positions. 1833 * Added that the IETF Trust Trustees and IETF LLC Directors, each 1834 may appoint a liaison to the NomCom. 1835 * Incorporated the update to RFC7437 done by RFC7776. 1836 * Incorporated the update to RFC7437 done by [RFC8318] and 1837 updated it to refer to the IETF Trust and IETF LLC. instead of 1838 the IAOC. 1839 * Editorial changes. 1841 draft-ietf-iasa2-rfc74337bis-02, 2018-October-19: 1843 * Added "IETF" before Nominating and Recall Committees in the 1844 title. 1845 * Added leading capitalization to Trustee(s) and Director(s) for 1846 consistency. 1847 * Fixed other minor grammatical, spelling, or abbreviation nits. 1849 draft-ietf-iasa2-rfc74337bis-01, 2018-October-16: 1851 * Modified the Advice and Consent model to enable IESG, IAB, and 1852 IETF LLC to communicate directly with the NomCom rather than 1853 via the Managing Director, IETF Secretariat. 1854 * Updated member removal text to reflect the new LLC rules, which 1855 enables removal via the LLC or the IETF recall process, except 1856 for the ISOC-appointed Director. 1858 * Removed discussion text from the volunteer eligibility section. 1859 This means that IETF LLC employees and contractors cannot 1860 volunteer for the NomCom but does not extend that prohibition 1861 to ISOC employees and contractors. 1862 * Updated the document to clarify that there are members of the 1863 IAB and IESG, Trustees of the IETF Trust, and Directors of the 1864 IETF LLC. 1865 * Removed ISOC Board of Trustees members from the definition of 1866 "sitting members" because it doesn't apply. 1867 * Updated document to also include procedures for the NomCom 1868 appointed IETF Trust Trustees. 1869 * Revised Abstract and Introduction to provide current context. 1870 * Changed "nominating committee" to "NomCom" throughout the 1871 document because it is what most use to describe the IETF 1872 Nominating Committee. 1873 * Added an no-actions IANA Considerations Section. 1874 * Editorial changes. 1876 draft-ietf-iasa2-rfc74337bis-00, 2018-October-12: 1877 Initial bis draft, Changes include: 1879 * Changed all mentions of the Internet Administrative Oversight 1880 committee (IAOC), and replaced it with the appropriate 1881 references to the IETF Administration LLC (IETF LLC). This 1882 included making changes on an as needed basis to some aspects 1883 of the process for the IETF LLC, in accordance with IASA2. 1884 * Revised definition of IETF Executive Director, and added 1885 definition of "Managing Director, IETF Secretariat". Changed 1886 text to "Managing Director, IETF Secretariat" where 1887 appropriate. 1888 * Added references to appropriate IASA2 documents. 1889 * Corrected a few grammatical errors. 1891 Authors' Addresses 1893 Murray S. Kucherawy (editor) 1894 270 Upland Drive 1895 San Francisco, CA 94127 1896 United States 1898 Email: superuser@gmail.com 1899 Robert M. Hinden (editor) 1900 Check Point Software 1901 San Carlos, CA 1902 USA 1904 Email: bob.hinden@gmail.com 1906 Jason Livingood (editor) 1907 Comcast 1908 Philadelphia, PA 1909 USA 1911 Email: jason_livingood@comcast.com