idnits 2.17.1 draft-ietf-iasa2-rfc7437bis-07.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 7, 2019) is 1785 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 1745 -- Looks like a reference, but probably isn't: '1' on line 1751 -- Looks like a reference, but probably isn't: '6' on line 1721 -- Looks like a reference, but probably isn't: '17' on line 1737 -- Looks like a reference, but probably isn't: '4' on line 1755 ** 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 9, 2019 J. Livingood, Ed. 7 Comcast 8 June 7, 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-07 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 9, 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 Section 2 of [I-D.ietf-iasa2-trust-update] provides further details 147 about the IETF Trust Trustees positions that are filled by the IETF 148 Nominating Committee (NomCom). 150 Section 5 of [I-D.ietf-iasa2-rfc4071bis] provides further details 151 about the IETF LLC Board Director positions that are filled by the 152 NomCom. 154 The following two assumptions continue to be true of this 155 specification: 157 1. The Internet Research Task Force (IRTF) and Internet Research 158 Steering Group (IRSG) are not a part of the process described 159 here. 161 2. The organization (and reorganization) of the IESG is not a part 162 of the process described here. 164 The time frames specified here use IETF meetings as a frame of 165 reference. The time frames assume that the IETF meets three times 166 per calendar year with approximately equal amounts of time between 167 them. The meetings are referred to as the First IETF, Second IETF, 168 or Third IETF as needed. 170 The next section lists the words and phrases commonly used throughout 171 this document with their intended meaning. 173 The majority of this document is divided into four major topics as 174 follows: 176 General: This is a set of rules and constraints that apply to the 177 selection and confirmation process as a whole. 179 Nominating Committee Selection: This is the process by which the 180 volunteers who will serve on the NomCom are selected. 182 Nominating Committee Operation: This is the set of principles, 183 rules, and constraints that guide the activities of the NomCom, 184 including the confirmation process. 186 Member, Trustee, and Director Recall: This is the process by which 187 the behavior of a sitting member of the IESG, or IAB, IETF Trust 188 Trustee, or IETF LLC Director may be questioned, perhaps resulting 189 in the removal of the sitting member. See Section 2 for a 190 description of what a sitting member means for each of these 191 groups. 193 A final section describes how this document differs from [RFC3777] 194 and [RFC7437]. 196 An appendix of useful facts and practices collected from previous 197 NomComs is also included. 199 This document updates the IAB, IESG, and IAOC Selection, 200 Confirmation, and Recall Process to be aligned with IASA 2.0 Model 201 [I-D.ietf-iasa2-rfc4071bis] that creates a IETF Administration 202 Limited Liability Company ("IETF LLC") managed by a Board of 203 Directors ("IETF LLC Board"). This document obsoletes [RFC7437] and 204 [RFC8318]. 206 2. Definitions 208 The following words and phrases are commonly used throughout this 209 document. They are listed here with their intended meaning for the 210 convenience of the reader. 212 Candidate: A nominee who has been selected to be considered for 213 confirmation by a confirming body. 215 Confirmed Candidate: A candidate that has been reviewed and approved 216 by a confirming body. 218 Nominating Committee Term: The term begins when its members are 219 officially announced, which is expected to be prior to the Third 220 IETF to ensure it is fully operational at the Third IETF. The 221 term ends at the Third IETF (not three meetings) after the next 222 NomCom's term begins. 224 IETF Executive Director: The person charged with day-to-day 225 operation of the IETF's administrative functions. (See 226 Section 4.1 of [I-D.ietf-iasa2-rfc4071bis]). Note: This was 227 previously the name of the IETF Secretariat position that is now 228 called the "Managing Director, IETF Secretariat". 230 Managing Director, IETF Secretariat: The person charged with 231 operation of the IETF Secretariat function. (See Section 2 of 232 [RFC3710] and [I-D.ietf-iasa2-consolidated-upd]). 234 Nominee: A person who is being or has been considered for one or 235 more open positions of the IESG, IAB, IETF Trust Trustee or IETF 236 LLC. 238 Sitting Member: A person who is currently serving as a member of the 239 IESG or IAB. 241 Sitting Director: A person who is currently serving as a Director of 242 the IETF LLC. 244 Sitting IETF Trust Trustee: A person who is currently serving as a 245 Trustee of the IETF Trust. 247 3. General 249 The following set of rules apply to the process as a whole. If 250 necessary, a paragraph discussing the interpretation of each rule is 251 included. 253 3.1. Completion Due 255 The completion of the annual process is due within seven months. 257 The completion of the annual process is due one month prior to the 258 Friday of the week before the First IETF. It is expected to begin at 259 least eight months prior to the Friday of the week before the First 260 IETF. 262 The process officially begins with the announcement of the Chair of 263 the committee. The process officially ends when all confirmed 264 candidates have been announced. 266 The annual process is comprised of three major components as follows: 268 1. The selection and organization of the NomCom members. 270 2. The selection of candidates by the NomCom. 272 3. The confirmation of the candidates. 274 There is an additional month set aside between when the annual 275 process is expected to end and the term of the new candidates is to 276 begin. This time may be used during unusual circumstances to extend 277 the time allocated for any of the components listed above. 279 3.2. Nominating Committee Principal Functions 281 The principal functions of the NomCom are to review each open IESG, 282 IAB, IETF Trust, and IETF LLC Board position and to nominate either 283 its incumbent or a superior candidate. 285 Although there is no term limit for serving in any IESG, IAB, or IETF 286 Trust position, the NomCom may use length of service as one of its 287 criteria for evaluating an incumbent. 289 The NomCom does not select the open positions to be reviewed; it is 290 instructed as to which positions to review. 292 The NomCom will be given the titles of the positions to be reviewed 293 and a brief summary of the desired expertise of the candidate that is 294 nominated to fill each position. 296 Incumbents must notify the NomCom if they wish to be nominated. 298 The NomCom does not confirm its candidates; it presents its 299 candidates to the appropriate confirming body as indicated below. 301 A superior candidate is one who the NomCom believes would contribute 302 in such a way as to improve or enhance the body to which he or she is 303 nominated. 305 3.3. Positions To Be Reviewed 307 Approximately one-half of each of the then current IESG and IAB 308 positions, one IETF Trust position, and one IETF LLC Board position, 309 is selected to be reviewed each year. 311 The intent of this rule is to ensure the review of approximately one- 312 half of each of the IESG and IAB sitting members, one of the three 313 NomCom nominated IETF LLC Board Director positions, and one of the 314 three nominated IETF Trust Trustee positions, each year. It is 315 recognized that circumstances may exist that will require the NomCom 316 to review more or less than the usual number of positions, e.g., if 317 the IESG, IAB, IETF Trust, or IETF LLC Board have reorganized prior 318 to this process and created new positions, if there are an odd number 319 of current positions, or if a member or Director unexpectedly 320 resigns. 322 3.4. Term Lengths 324 Confirmed IESG and IAB candidates are expected to serve at least a 325 two-year term. The intent of this rule is to ensure that members of 326 the IESG and IAB serve the number of years that best facilitates the 327 review of one-half of the members each year. 329 Confirmed IETF LLC Board Director candidates are expected to serve at 330 least a three-year term, except if a nominating or selection body 331 decides to use a shorter term to allow for initial staggered 332 appointments. Please refer to Section 5 of 333 [I-D.ietf-iasa2-rfc4071bis] for additional guidance on terms length 334 and term limits for the IETF LLC Board. 336 Confirmed IETF Trust Trustee candidates are expected to serve at 337 least a three-year term, except if a nominating or selection body 338 decides to use a shorter term to allow for initial staggered 339 appointments. Please refer to Section 2. of 340 [I-D.ietf-iasa2-trust-update] for additional guidance on terms length 341 and term limits for the IETF Trust. 343 The term of a confirmed candidate selected according to the mid-term 344 vacancy rules may be less than a full term (two years for IESG and 345 IAB, three years for the IETF Trust and IETF LLC), as stated 346 elsewhere in this document. 348 It is consistent with this rule for the NomCom to choose one or more 349 of the currently open positions to which it may assign a term of not 350 more than three years in order to ensure the ideal application of 351 this rule in the future. 353 It is consistent with this rule for the NomCom to choose one or more 354 of the currently open positions that share responsibilities with 355 other positions (both those being reviewed and those sitting) to 356 which it may assign a term of not more than three years to ensure 357 that all such members or Directors will not be reviewed at the same 358 time. 360 All sitting member terms end during the First IETF meeting 361 corresponding to the end of the term for which they were confirmed. 362 All confirmed candidate terms begin during the First IETF meeting 363 corresponding to the beginning of the term for which they were 364 confirmed. 366 For confirmed candidates of the IESG, the terms begin no later than 367 when the currently sitting members' terms end on the last day of the 368 meeting. A term may begin or end no sooner than the first day of the 369 meeting and no later than the last day of the meeting as determined 370 by the mutual agreement of the currently sitting member and the 371 confirmed candidate. A confirmed candidate's term may overlap the 372 sitting member's term during the meeting as determined by their 373 mutual agreement. 375 For confirmed candidates of the IAB, the terms overlap with the terms 376 of the sitting members for the entire week of the meeting. 378 For confirmed Trustee candidates of the IETF Trust, the term begins 379 at the next IETF Trust meeting or as dictated by the policies and 380 procedures of the IETF Trust. 382 For confirmed Director candidates of the IETF LLC, the term begins at 383 the next appropriate IETF LLC Board meeting or as dictated by the 384 policies and procedures of the IETF LLC Board. 386 For candidates confirmed under the mid-term vacancy rules, the term 387 begins as soon as possible after the confirmation. 389 3.5. Mid-term Vacancies 391 Mid-term vacancies are filled by the same rules as documented here 392 with four qualifications, namely: 394 1. When there is only one official NomCom, the body with the mid- 395 term vacancy relegates the responsibility to fill the vacancy to 396 it. If the mid-term vacancy occurs during the period of time 397 that the term of the prior year's NomCom overlaps with the term 398 of the current year's NomCom, the body with the mid-term vacancy 399 must relegate the responsibility to fill the vacancy to the prior 400 year's NomCom. 402 2. If it is the case that the NomCom is reconvening to fill the mid- 403 term vacancy, then the completion of the candidate selection and 404 confirmation process is due within six weeks, with all other time 405 periods otherwise unspecified prorated accordingly. 407 3. The confirming body has two weeks from the day it is notified of 408 a candidate to reject the candidate, otherwise the candidate is 409 assumed to have been confirmed. 411 4. The term of the confirmed candidate will be either: 413 A. the remainder of the term of the open position if that 414 remainder is not less than one year or 416 B. the remainder of the term of the open position plus the next 417 two-year term if that remainder is less than one year. 419 In both cases, a year is the period of time from a First IETF meeting 420 to the next First IETF meeting. 422 3.6. Confidentiality 424 All deliberations and supporting information that relates to specific 425 nominees, candidates, and confirmed candidates are confidential. 427 The NomCom and confirming body members will be exposed to 428 confidential information as a result of their deliberations, their 429 interactions with those they consult, and from those who provide 430 requested supporting information. All members and all other 431 participants are expected to handle this information in a manner 432 consistent with its sensitivity. 434 It is consistent with this rule for current NomCom members who have 435 served on prior NomComs to advise the current committee on 436 deliberations and results of the prior committee, as necessary and 437 appropriate. 439 The list of nominees willing to be considered for positions under 440 review in the current NomCom cycle is not confidential. The NomCom 441 may disclose a list of names of nominees who are willing to be 442 considered for positions under review to the community, in order to 443 obtain feedback from the community on these nominees. 445 The list of nominees disclosed for a specific position should contain 446 only the names of nominees who are willing to be considered for the 447 position under review. 449 The NomCom may choose not to include some names in the disclosed 450 list, at their discretion. 452 The NomCom may disclose an updated list, at its discretion. For 453 example, the NomCom might disclose an updated list if it identifies 454 errors/omissions in a previously disclosed version of the disclosed 455 list, or if the NomCom finds it necessary to call for additional 456 nominees, and these nominees indicate a willingness to be considered 457 before the NomCom has completed its deliberations. 459 Nominees may choose to ask people to provide feedback to the NomCom 460 but should not encourage any public statements of support. NomComs 461 should consider nominee-encouraged lobbying and campaigning to be 462 unacceptable behavior. 464 IETF community members are encouraged to provide feedback on nominees 465 to the NomCom but should not post statements of support/non-support 466 for nominees in any public forum. 468 3.7. Advice and Consent Model 470 Unless otherwise specified, the advice and consent model is used 471 throughout the process. This model is characterized as follows. 473 3.7.1. Positions To Be Reviewed 475 The chair of the IESG, IAB, IETF Trust and IETF LLC Board each 476 informs the NomCom of their respective positions to be reviewed. 478 The IESG, IAB, IETF Trust and IETF LLC are responsible for providing 479 a summary of the expertise desired of the candidates selected for 480 their respective open positions. The summaries are provided to the 481 NomCom for its consideration. 483 3.7.2. Candidate Selection 485 The NomCom selects candidates based on its understanding of the IETF 486 community's consensus of the qualifications required and advises each 487 confirming body of its respective candidates. 489 3.7.3. Candidate Review 491 The confirming bodies review their respective candidates, they may at 492 their discretion communicate with the NomCom, and then consent to 493 some, all, or none of the candidates. 495 The sitting IAB members review the IESG candidates. 497 The Internet Society Board of Trustees reviews the IAB candidates. 499 The sitting IESG members review the IETF Trust Trustee Candidates. 501 The IETF LLC Board candidate is reviewed as specified in 502 [I-D.ietf-iasa2-rfc4071bis]. 504 The confirming bodies conduct their review using all information and 505 any means acceptable to them, including but not limited to the 506 supporting information provided by the NomCom, information known 507 personally to members of the confirming bodies and shared within the 508 confirming body, the results of interactions within the confirming 509 bodies, and the confirming bodies' interpretation of what is in the 510 best interests of the IETF community. 512 If all of the candidates are confirmed, the job of the NomCom with 513 respect to those open positions is complete. 515 If some or none of the candidates submitted to a confirming body are 516 confirmed, the confirming body should communicate with the NomCom 517 both to explain the reason why all the candidates were not confirmed 518 and to understand the NomCom's rationale for its candidates. 520 The confirming body may reject individual candidates, in which case 521 the NomCom must select alternate candidates for the rejected 522 candidates. 524 Any additional time required by the NomCom should not exceed its 525 maximum time allotment. 527 3.7.4. Confirmation 529 A confirming body decides whether it confirms each candidate using a 530 confirmation decision rule chosen by the confirming body. 532 If a confirming body has no specific confirmation decision rule, then 533 confirming a given candidate should require at least one-half of the 534 confirming body's sitting members to agree to that confirmation. 536 The decision may be made by conducting a formal vote, by asserting 537 consensus based on informal exchanges (e.g., email), or by any other 538 mechanism that is used to conduct the normal business of the 539 confirming body. 541 Regardless of which decision rule the confirming body uses, any 542 candidate that is not confirmed under that rule is considered to be 543 rejected. 545 The confirming body must make its decision within a reasonable time 546 frame. The results from the confirming body must be reported 547 promptly to the NomCom. 549 3.8. Sitting Members and Directors 551 The following rules apply to nominees and candidates who are 552 currently sitting members of the IESG or IAB, or IETF LLC Board 553 Directors and who are not sitting in an open position being filled by 554 the NomCom. 556 The confirmation of a candidate to an open position does not 557 automatically create a vacancy in the IESG, IAB, IETF Trust, or IETF 558 LLC Board position currently occupied by the candidate. The mid-term 559 vacancy cannot exist until, first, the candidate formally resigns 560 from the current position and, second, the body with the vacancy 561 formally decides for itself that it wants the NomCom to fill the mid- 562 term vacancy according to the rules for a mid-term vacancy documented 563 elsewhere in this document. 565 The resignation should be effective as of when the term of the new 566 position begins. The resignation may remain confidential to the 567 IESG, IAB, IETF Trust, IETF LLC Board, and NomCom until the confirmed 568 candidate is announced for the new position. The process, according 569 to rules set out elsewhere in this document, of filling the seat 570 vacated by the confirmed candidate may begin as soon as the vacancy 571 is publicly announced. 573 Filling a mid-term vacancy is a separate and independent action from 574 the customary action of filling open positions. In particular, a 575 NomCom must complete its job with respect to filling the open 576 positions and then separately proceed with the task of filling the 577 mid-term vacancy according to the rules for a mid-term vacancy 578 documented elsewhere in this document. 580 However, the following exception is permitted in the case where the 581 candidate for an open position is currently a sitting member of the 582 IAB. It is consistent with these rules for the announcements of a 583 resignation of a sitting member of the IAB and of the confirmed 584 candidate for the mid-term vacancy created by that sitting member on 585 the IAB to all occur at the same time as long as the actual sequence 586 of events that occurred did so in the following order: 588 1. The NomCom completes the advice and consent process for the open 589 position being filled by the candidate currently sitting on the 590 IAB. 592 2. The newly confirmed candidate resigns from their current position 593 on the IAB. 595 3. The IAB Chair (or the Managing Director, IETF Secretariat, if no 596 Chair has been named or the vacancy was created via the departure 597 of the IAB Chair) informs the NomCom of the mid-term vacancy. 599 4. The NomCom acts on the request to fill the mid-term vacancy. 601 3.9. Announcements 603 All announcements must be made using at least the mechanism used by 604 the IETF Secretariat for its announcements, including a notice on the 605 IETF web site. 607 As of the publication of this document, the current mechanism is an 608 email message to both the "ietf" and the "ietf-announce" mailing 609 lists. 611 4. Nominating Committee Selection 613 The following set of rules apply to the creation of the NomCom and 614 the selection of its members. 616 4.1. Timeline 618 The completion of the process of selecting and organizing the members 619 of the NomCom is due within three months. 621 The completion of the selection and organization process is due at 622 least one month prior to the Third IETF. This ensures the NomCom is 623 fully operational and available for interviews and consultation 624 during the Third IETF. 626 4.2. Term 628 The term of a NomCom is expected to be 15 months. 630 It is the intent of this rule that the end of a NomCom's term overlap 631 by approximately three months the beginning of the term of the next 632 NomCom. 634 The term of a NomCom begins when its members are officially 635 announced. The term ends at the Third IETF (not three meetings), 636 i.e., the IETF meeting after the next NomCom's term begins. 638 A term is expected to begin at least two months prior to the Third 639 IETF to ensure the NomCom has at least one month to get organized 640 before preparing for the Third IETF. 642 A NomCom is expected to complete any work in progress before it is 643 dissolved at the end of its term. 645 During the period of time when the terms of the NomComs overlap, all 646 mid-term vacancies are to be relegated to the prior year's NomCom. 647 The prior year's NomCom has no other responsibilities during the 648 overlap period. At all times other than the overlap period, there is 649 exactly one official NomCom and it is responsible for all mid-term 650 vacancies. 652 When the prior year's NomCom is filling a mid-term vacancy during the 653 period of time that the terms overlap, the NomCom operate 654 independently. However, some coordination is needed between them. 655 Since the prior year's Chair is a non-voting advisor to the current 656 NomCom, the coordination is expected to be straightforward. 658 4.3. Structure 660 The NomCom comprises at least a Chair, 10 voting volunteers, two 661 liaisons, and an advisor. 663 Any committee member may propose the addition of an advisor to 664 participate in some or all of the deliberations of the committee. 665 The addition must be approved by the committee according to its 666 established voting mechanism. Advisors participate as individuals. 668 Committee members are encouraged to propose the addition of 669 advisor(s) who are knowledgeable about the operations of the IETF 670 Trust and/or IETF LLC Board, whether or not that NomCom is reviewing 671 an IETF Trust Trustee or IETF LLC Board Director position. The 672 NomCom may choose to ask the IETF Trust and/or IETF LLC Board to 673 suggest advisors who are knowledgeable about their operations but may 674 select any advisor they vote to approve. 676 Any committee member may propose the addition of a liaison from other 677 unrepresented organizations to participate in some or all of the 678 deliberations of the committee. The addition must be approved by the 679 committee according to its established voting mechanism. Liaisons 680 participate as representatives of their respective organizations. 682 The Chair is selected according to rules stated elsewhere in this 683 document. 685 The 10 voting volunteers are selected according to rules stated 686 elsewhere in this document. 688 The IESG and IAB liaisons are selected according to rules stated 689 elsewhere in this document. 691 The Internet Society Board of Trustees may appoint a liaison to the 692 NomCom at its own discretion. 694 The IETF Trust may appoint a liaison to the NomCom at its own 695 discretion. 697 The IETF LLC Board may appoint a liaison to the NomCom at its own 698 discretion. 700 The Chair of last year's NomCom serves as an advisor according to 701 rules stated elsewhere in this document. 703 The Chair, liaisons, and advisors do not vote on the selection of 704 candidates. They do vote on all other issues before the committee 705 unless otherwise specified in this document. 707 4.4. Chair Duties 709 The Chair of the NomCom is responsible for ensuring the NomCom 710 completes its assigned duties in a timely fashion and performs in the 711 best interests of the IETF community. 713 The Chair must be thoroughly familiar with the rules and guidance 714 indicated throughout this document. The Chair must ensure the NomCom 715 completes its assigned duties in a manner that is consistent with 716 this document. 718 The Chair must attest by proclamation at a plenary session of the 719 First IETF that the results of the committee represent its best 720 effort and the best interests of the IETF community. 722 The Chair does not vote on the selection of candidates. 724 4.5. Chair Selection 726 The Internet Society President appoints the Chair, who must meet the 727 same requirements for membership in the NomCom as a voting volunteer. 729 The NomCom Chair must agree to invest the time necessary to ensure 730 that the NomCom completes its assigned duties and to perform in the 731 best interests of the IETF community in that role. 733 The appointment is due no later than the Second IETF meeting to 734 ensure it can be announced during a plenary session at that meeting. 735 The completion of the appointment is necessary to ensure the annual 736 process can complete at the time specified elsewhere in this 737 document. 739 4.6. Temporary Chair 741 A Chair, in consultation with the Internet Society President, may 742 appoint a temporary substitute for the Chair position. 744 There are a variety of ordinary circumstances that may arise from 745 time to time that could result in a Chair being unavailable to 746 oversee the activities of the committee. The Chair, in consultation 747 with the Internet Society President, may appoint a substitute from a 748 pool comprised of the liaisons currently serving on the committee and 749 the prior year's Chair or designee. 751 Any such appointment must be temporary and does not absolve the Chair 752 of any or all responsibility for ensuring the NomCom completes its 753 assigned duties in a timely fashion. 755 4.7. Liaisons 757 Liaisons are responsible for ensuring the NomCom in general and the 758 Chair in particular execute their assigned duties in the best 759 interests of the IETF community. 761 Liaisons are expected to represent the views of their respective 762 organizations during the deliberations of the committee. They should 763 provide information as requested or when they believe it would be 764 helpful to the committee. 766 Liaisons are expected to provide information to the NomCom regarding 767 the operation, responsibility, and composition of their respective 768 bodies. 770 Liaisons are expected to convey questions from the committee to their 771 respective organizations and responses to those questions to the 772 committee, as requested by the committee. 774 Liaisons are expected to review the operation and executing process 775 of the NomCom and to report any concerns or issues to the Chair of 776 the NomCom immediately. If they cannot resolve the issue between 777 themselves, liaisons must report it according to the dispute 778 resolution process stated elsewhere in this document. 780 Liaisons from confirming bodies are expected to assist the committee 781 in preparing the testimony it is required to provide with its 782 candidates. 784 Liaisons may have other NomCom responsibilities as required by their 785 respective organizations or requested by the NomCom, except that such 786 responsibilities may not conflict with any other provisions of this 787 document. 789 Liaisons do not vote on the selection of candidates. 791 4.8. Liaison Appointment 793 The sitting IAB and IESG members each appoint a liaison from their 794 current membership, someone who is not sitting in an open position, 795 to serve on the NomCom. 797 The sitting IETF Trust Trustees and IETF LLC Board Directors each may 798 appoint a liaison from their current membership, someone who is not 799 sitting in an open position, to serve on the NomCom. 801 4.9. Advisors 803 An advisor is responsible for such duties as specified by the 804 invitation that resulted in the appointment. 806 Advisors do not vote on the selection of candidates. 808 4.10. Past Chair 810 The Chair of the prior year's NomCom serves as an advisor to the 811 current committee. 813 The prior year's Chair is expected to review the actions and 814 activities of the current Chair and to report any concerns or issues 815 to the NomCom Chair immediately. If they cannot resolve the issue 816 between themselves, the prior year's Chair must report it according 817 to the dispute resolution process stated elsewhere in this document. 819 The prior year's Chair may select a designee from a pool composed of 820 the voting volunteers of the prior year's committee and all prior 821 Chairs if the Chair is unavailable. If the prior year's Chair is 822 unavailable or is unable or unwilling to make such a designation in a 823 timely fashion, the Chair of the current year's committee may select 824 a designee in consultation with the Internet Society President. 826 Selecting a prior year's committee member as the designee permits the 827 experience of the prior year's deliberations to be readily available 828 to the current committee. Selecting an earlier prior year Chair as 829 the designee permits the experience of being a Chair as well as that 830 Chair's committee deliberations to be readily available to the 831 current committee. 833 All references to "prior year's Chair" in this document refer to the 834 person serving in that role, whether it is the actual prior year's 835 Chair or a designee. 837 4.11. Voting Volunteers 839 Voting volunteers are responsible for completing the tasks of the 840 NomCom in a timely fashion. 842 Each voting volunteer is expected to participate in all activities of 843 the NomCom with a level of effort approximately equal to all other 844 voting volunteers. Specific tasks to be completed are established 845 and managed by the Chair according to rules stated elsewhere in this 846 document. 848 4.12. Milestones 850 The Chair must establish and announce milestones for the selection of 851 the NomCom members. 853 There is a defined time period during which the selection process is 854 due to be completed. The Chair must establish a set of milestones 855 which, if met in a timely fashion, will result in the completion of 856 the process on time. 858 4.13. Open Positions 860 The Chair (or the Managing Director, IETF Secretariat, if no Chair 861 has been named four weeks after the First IETF meeting of the year) 862 obtains the list of positions to be reviewed and announces it along 863 with a solicitation for names of volunteers from the IETF community 864 willing to serve on the NomCom. 866 If the Managing Director, IETF Secretariat issues the solicitation 867 for volunteers, the Managing Director, IETF Secretariat must also 868 collect responses to the solicitation and provide the names of 869 volunteers to the incoming NomCom Chair when the incoming NomCom 870 Chair is named. 872 At the Chair's request, the IETF Secretariat may perform other 873 clerical support tasks, as long as the task being performed does not 874 require NomCom Chair judgment, in the NomCom Chair's opinion, and as 875 long as the community is appropriately notified that this request is 876 being made. This request may come from the incoming NomCom Chair (if 877 one has been selected for this NomCom cycle) or the previous NomCom 878 Chair (if the search for an incoming NomCom Chair is still underway). 880 The solicitation must permit the community at least 30 days during 881 which they may choose to volunteer to be selected for the NomCom. 883 The list of open positions is published with the solicitation to 884 facilitate community members choosing between volunteering for an 885 open position and volunteering for the NomCom. 887 4.14. Volunteer Qualification 889 Members of the IETF community must have attended at least three of 890 the last five IETF meetings in order to volunteer. 892 The five meetings are the five most recent meetings that ended prior 893 to the date on which the solicitation for NomCom volunteers was 894 submitted for distribution to the IETF community. 896 The IETF Secretariat is responsible for confirming that volunteers 897 have met the attendance requirement. 899 Volunteers must provide their full name, email address, and primary 900 company or organization affiliation (if any) when volunteering. 902 Volunteers are expected to be familiar with the IETF processes and 903 procedures, which are readily learned by active participation in a 904 working group and especially by serving as a document editor or 905 working group chair. 907 4.15. Not Qualified 909 Any person who serves on the Internet Society Board of Trustees, the 910 IETF Trust, the IETF LLC Board of Directors, the IAB, or the IESG, 911 including those who serve on these bodies in ex officio positions, 912 may not volunteer to serve as voting members of the NomCom. In 913 addition, employees or contractors of the IETF LLC may not volunteer 914 to serve as voting members of the NomCom. Liaisons to these bodies 915 from other bodies or organizations are not excluded by this rule. 917 4.16. Selection Process 919 The Chair announces both the list of the pool of volunteers from 920 which the 10 voting volunteers will be randomly selected and the 921 method with which the selection will be completed. 923 The announcement should be made at least one week prior to the date 924 on which the random selection will occur. 926 The pool of volunteers must be enumerated or otherwise indicated 927 according to the needs of the selection method to be used. 929 The announcement must specify the data that will be used as input to 930 the selection method. The method must depend on random data whose 931 value is not known or available until the date on which the random 932 selection will occur. 934 It must be possible to independently verify that the selection method 935 used is both fair and unbiased. A method is fair if each eligible 936 volunteer is equally likely to be selected. A method is unbiased if 937 no one can influence its outcome in favor of a specific outcome. 939 It must be possible to repeat the selection method, either through 940 iteration or by restarting in such a way as to remain fair and 941 unbiased. This is necessary to replace selected volunteers should 942 they become unavailable after selection. 944 The selection method must produce an ordered list of volunteers. 946 One possible selection method is described in [RFC3797]. 948 4.17. Announcement of Selection Results 950 The Chair randomly selects the 10 voting volunteers from the pool of 951 names of volunteers and announces the members of the NomCom. 953 No more than two volunteers with the same primary affiliation may be 954 selected for the NomCom. The Chair reviews the primary affiliation 955 of each volunteer selected by the method in turn. If the primary 956 affiliation for a volunteer is the same as two previously selected 957 volunteers, that volunteer is removed from consideration and the 958 method is repeated to identify the next eligible volunteer. 960 There must be at least two announcements of all members of the 961 NomCom. 963 The first announcement should occur as soon after the random 964 selection as is reasonable for the Chair. The community must have at 965 least one week during which any member may challenge the results of 966 the random selection. 968 The challenge must be made in writing (email is acceptable) to the 969 Chair. The Chair has 48 hours to review the challenge and offer a 970 resolution to the member. If the resolution is not accepted by the 971 member, that member may report the challenge according to the dispute 972 resolution process stated elsewhere in this document. 974 If a selected volunteer, upon reading the announcement with the list 975 of selected volunteers, finds that two or more other volunteers have 976 the same affiliation, then the volunteer should notify the Chair who 977 will determine the appropriate action. 979 During at least the one week challenge period, the Chair must contact 980 each of the members and confirm their willingness and availability to 981 serve. The Chair should make every reasonable effort to contact each 982 member. 984 o If the Chair is unable to contact a liaison, the problem is 985 referred to the respective organization to resolve. The Chair 986 should allow a reasonable amount of time for the organization to 987 resolve the problem and then may proceed without the liaison. 989 o If the Chair is unable to contact an advisor, the Chair may elect 990 to proceed without the advisor, except for the prior year's Chair 991 for whom the Chair must consult with the Internet Society 992 President as stated elsewhere in this document. 994 o If the Chair is unable to contact a voting volunteer, the Chair 995 must repeat the random selection process in order to replace the 996 unavailable volunteer. There should be at least one day between 997 the announcement of the iteration and the selection process. 999 After at least one week and confirming that 10 voting volunteers are 1000 ready to serve, the Chair makes the second announcement of the 1001 members of the NomCom, which officially begins the term of the 1002 NomCom. 1004 4.18. Committee Organization 1006 The Chair works with the members of the committee to organize itself 1007 in preparation for completing its assigned duties. 1009 The committee has approximately one month during which it can self- 1010 organize. Its responsibilities during this time include but are not 1011 limited to the following: 1013 o Setting up a regular teleconference schedule. 1015 o Setting up an internal web site. 1017 o Setting up a mailing list for internal discussions. 1019 o Setting up an email address for receiving community input. 1021 o Establishing operational procedures. 1023 o Establishing milestones in order to monitor the progress of the 1024 selection process. 1026 5. Nominating Committee Operation 1028 The following rules apply to the operation of the NomCom. If 1029 necessary, a paragraph discussing the interpretation of each rule is 1030 included. 1032 The rules are organized approximately in the order in which they 1033 would be invoked. 1035 5.1. Discretion 1037 All rules and special circumstances not otherwise specified are at 1038 the discretion of the committee. 1040 Exceptional circumstances will occasionally arise during the normal 1041 operation of the NomCom. This rule is intended to foster the 1042 continued forward progress of the committee. 1044 Any member of the committee may propose a rule for adoption by the 1045 committee. The rule must be approved by the committee according to 1046 its established voting mechanism. 1048 All members of the committee should consider whether the exception is 1049 worthy of mention in the next revision of this document and follow-up 1050 accordingly. 1052 5.2. Selection Timeline 1054 The completion of the process of selecting candidates to be confirmed 1055 by their respective confirming body is due within three months. 1057 The completion of the selection process is due at least two months 1058 prior to the First IETF. This ensures the NomCom has sufficient time 1059 to complete the confirmation process. 1061 5.3. Confirmation Timeline 1063 The completion of the process of confirming the candidates is due 1064 within one month. 1066 The completion of the confirmation process is due at least one month 1067 prior to the First IETF. 1069 5.4. Milestones 1071 The Chair must establish a set of NomCom milestones for the candidate 1072 selection and confirmation process. 1074 There is a defined time period during which the candidate selection 1075 and confirmation process must be completed. The Chair must establish 1076 a set of milestones that, if met in a timely fashion, will result in 1077 the completion of the process on time. The Chair should allow time 1078 for iterating the activities of the committee if one or more 1079 candidates are not confirmed. 1081 The Chair should ensure that all committee members are aware of the 1082 milestones. 1084 5.5. Voting Mechanism 1086 The Chair must establish a voting mechanism. 1088 The committee must be able to objectively determine when a decision 1089 has been made during its deliberations. The criteria for determining 1090 closure must be established and known to all members of the NomCom. 1092 5.6. Voting Quorum 1094 At least a quorum of committee members must participate in a vote. 1096 Only voting volunteers vote on a candidate selection. For a 1097 candidate selection vote, a quorum is comprised of at least seven of 1098 the voting volunteers. 1100 At all other times, a quorum is present if at least 75% of the NomCom 1101 members are participating. 1103 5.7. Voting Member Recall 1105 Any member of the NomCom may propose to the committee that any other 1106 member except the Chair be recalled. The process for recalling the 1107 Chair is defined elsewhere in this document. 1109 There are a variety of ordinary circumstances that may arise that 1110 could result in one or more members of the committee being 1111 unavailable to complete their assigned duties, for example, health 1112 concerns, family issues, or a change of priorities at work. A 1113 committee member may choose to resign for unspecified personal 1114 reasons. In addition, the committee may not function well as a group 1115 because a member may be disruptive or otherwise uncooperative. 1117 Regardless of the circumstances, if individual committee members 1118 cannot work out their differences between themselves, the entire 1119 committee may be called upon to discuss and review the circumstances. 1120 If a resolution is not forthcoming, a vote may be conducted. A 1121 member may be recalled if at least a quorum of all committee members 1122 agree, including the vote of the member being recalled. 1124 If a liaison member is recalled, the committee must notify the 1125 affected organization and must allow a reasonable amount of time for 1126 a replacement to be identified by the organization before proceeding. 1128 If an advisor member other than the prior year's Chair is recalled, 1129 the committee may choose to proceed without the advisor. In the case 1130 of the prior year's Chair, the Internet Society President must be 1131 notified and the current Chair must be allowed a reasonable amount of 1132 time to consult with the Internet Society President to identify a 1133 replacement before proceeding. 1135 If a single voting volunteer position on the NomCom is vacated, 1136 regardless of the circumstances, the committee may choose to proceed 1137 with only nine voting volunteers at its own discretion. In all other 1138 cases, a new voting member must be selected, and the Chair must 1139 repeat the random selection process including an announcement of the 1140 iteration prior to the actual selection as stated elsewhere in this 1141 document. 1143 A change in the primary affiliation of a voting volunteer during the 1144 term of the NomCom is not a cause to request the recall of that 1145 volunteer, even if the change would result in more than two voting 1146 volunteers with the same affiliation. 1148 5.8. Chair Recall 1150 Only the prior year's Chair may request the recall of the current 1151 Chair. 1153 It is the responsibility of the prior year's Chair to ensure the 1154 current Chair completes the assigned tasks in a manner consistent 1155 with this document and in the best interests of the IETF community. 1157 Any member of the committee who has an issue or concern regarding the 1158 Chair should report it to the prior year's Chair immediately. The 1159 prior year's Chair is expected to report it to the Chair immediately. 1160 If they cannot resolve the issue between themselves, the prior year's 1161 Chair must report it according to the dispute resolution process 1162 stated elsewhere in this document. 1164 5.9. Deliberations 1166 All members of the NomCom may participate in all deliberations. 1168 The emphasis of this rule is that no member can be explicitly 1169 excluded from any deliberation. However, a member may individually 1170 choose not to participate in a deliberation. 1172 5.10. Call for Nominees 1174 The Chair announces the open positions to be reviewed, the desired 1175 expertise provided by the Managing Director, IETF Secretariat, and 1176 the call for nominees. 1178 The call for nominees must include a request for comments regarding 1179 the past performance of incumbents, which will be considered during 1180 the deliberations of the NomCom. 1182 The call must request that a nomination include a valid, working 1183 email address, a telephone number, or both for the nominee. The 1184 nomination must include the set of skills or expertise the nominator 1185 believes the nominee has that would be desirable. 1187 5.11. Nominations 1189 Any member of the IETF community may nominate any member of the IETF 1190 community for any open position, whose eligibility to serve will be 1191 confirmed by the NomCom. 1193 A self-nomination is permitted. 1195 NomCom members are not eligible to be considered for filling any open 1196 position by the NomCom on which they serve. They become ineligible 1197 as soon as the term of the NomCom on which they serve officially 1198 begins. They remain ineligible for the duration of that NomCom's 1199 term. 1201 Although each NomCom's term overlaps with the following NomCom's 1202 term, NomCom members are eligible for nomination by the following 1203 committee if not otherwise disqualified. 1205 Members of the IETF community who were recalled from any IESG, IAB, 1206 IETF Trust, or IETF LLC Board position during the previous two years 1207 are not eligible to be considered for filling any open position. 1209 5.12. Candidate Selection 1211 The NomCom selects candidates based on its understanding of the IETF 1212 community's consensus of the qualifications required to fill the open 1213 positions. 1215 The intent of this rule is to ensure that the NomCom consults with a 1216 broad base of the IETF community for input to its deliberations. In 1217 particular, the NomCom must determine if the desired expertise for 1218 the open positions matches its understanding of the qualifications 1219 desired by the IETF community. 1221 The consultations are permitted to include names of nominees, if all 1222 parties to the consultation agree to observe the same confidentiality 1223 rules as the NomCom itself, or the names are public as discussed in 1224 Section 3.6. Feedback on individual nominees should always be 1225 confidential. 1227 A broad base of the community should include the existing members of 1228 the IESG and IAB, IETF Trust Trustees, and IETF LLC Board Directors, 1229 especially sitting members who share responsibilities with open 1230 positions, e.g., co-Area Directors, and working group chairs, 1231 especially those in the areas with open positions. 1233 Only voting volunteer members vote to select candidates. 1235 5.13. Consent to Nomination 1237 Nominees should be advised that they are being considered and must 1238 consent to their nomination prior to being chosen as candidates. 1240 Although the NomCom will make every reasonable effort to contact and 1241 to remain in contact with nominees, any nominee whose contact 1242 information changes during the process and who wishes to still be 1243 considered should inform the NomCom of the changes. 1245 A nominee's consent must be written (email is acceptable) and must 1246 include a commitment to provide the resources necessary to fill the 1247 open position and an assurance that the nominee will perform the 1248 duties of the position for which they are being considered in the 1249 best interests of the IETF community. 1251 Consenting to a nomination must occur prior to a nominee being a 1252 candidate and may occur as soon after the nomination as needed by the 1253 NomCom. 1255 Consenting to a nomination must not imply the nominee will be a 1256 candidate. 1258 The NomCom should help nominees provide justification to their 1259 employers. 1261 5.14. Notifying Confirming Bodies 1263 The NomCom advises the confirming bodies of their candidates, 1264 specifying a single candidate for each open position and testifying 1265 as to how each candidate meets the qualifications of an open 1266 position. 1268 For each candidate, the testimony must include a brief statement of 1269 the qualifications for the position that is being filled, which may 1270 be exactly the expertise that was requested. If the qualifications 1271 differ from the expertise originally requested, a brief statement 1272 explaining the difference must be included. 1274 The testimony may include a brief resume of the candidate and/or a 1275 brief summary of the deliberations of the NomCom. 1277 5.15. Confirming Candidates 1279 Confirmed candidates must consent to their confirmation, and rejected 1280 candidates and nominees must be notified before confirmed candidates 1281 are announced. 1283 It is not necessary to notify and get consent from all confirmed 1284 candidates together. 1286 A nominee may not know they were a candidate. This permits a 1287 candidate to be rejected by a confirming body without the nominee 1288 knowing about the rejection. 1290 Rejected nominees, who consented to their nomination, and rejected 1291 candidates must be notified prior to announcing the confirmed 1292 candidates. 1294 It is not necessary to announce all confirmed candidates together. 1296 The NomCom must ensure that all confirmed candidates are prepared to 1297 serve prior to announcing their confirmation. 1299 5.16. Archives 1301 The NomCom should archive the information it has collected or 1302 produced for a period of time but not to exceed its term. 1304 The purpose of the archive is to assist the NomCom should it be 1305 necessary for it to fill a mid-term vacancy. 1307 The existence of an archive, how it is implemented, and what 1308 information to archive is at the discretion of the committee. The 1309 decision must be approved by a quorum of the voting volunteer 1310 members. 1312 The implementation of the archive should make every reasonable effort 1313 to ensure that the confidentiality of the information it contains is 1314 maintained. 1316 6. Dispute Resolution Process 1318 The dispute resolution process described here is to be used as 1319 indicated elsewhere in this document. Its applicability in other 1320 circumstances is beyond the scope of this document. 1322 The NomCom operates under a strict rule of confidentiality. For this 1323 reason, when process issues arise, it is best to make every 1324 reasonable effort to resolve them within the committee. However, 1325 when circumstances do not permit this, or no resolution is 1326 forthcoming, the process described here is to be used. 1328 The following rules apply to the process. 1330 1. The results of this process are final and binding. There is no 1331 appeal. 1333 2. The process begins with the submission of a request as described 1334 below to the Internet Society President. 1336 3. As soon as the process begins, the NomCom may continue those 1337 activities that are unrelated to the issue to be resolved except 1338 that it must not submit any candidates to a confirming body until 1339 the issue is resolved. 1341 4. All parties to the process are subject to the same 1342 confidentiality rules as each member of the NomCom. 1344 5. The process should be completed within two weeks. 1346 The process is as follows: 1348 1. The party seeking resolution submits a written request (email is 1349 acceptable) to the Internet Society President detailing the issue 1350 to be resolved. 1352 2. The Internet Society President appoints an arbiter to investigate 1353 and resolve the issue. A self-appointment is permitted. 1355 3. The arbiter investigates the issue making every reasonable effort 1356 to understand both sides of the issue. Since the arbiter is 1357 subject to the same confidentiality obligations as all NomCom 1358 members, all members are expected to cooperate fully with the 1359 arbiter and to provide all relevant information to the arbiter 1360 for review. 1362 4. After consultation with the two principal parties to the issue, 1363 the arbiter decides on a resolution. Whatever actions are 1364 necessary to execute the resolution are immediately begun and 1365 completed as quickly as possible. 1367 5. The arbiter summarizes the issue, the resolution, and the 1368 rationale for the resolution for the Internet Society President. 1370 6. In consultation with the Internet Society President, the arbiter 1371 prepares a report of the dispute and its resolution. The report 1372 should include all information that in the judgment of the 1373 arbiter does not violate the confidentiality requirements of the 1374 NomCom. 1376 7. The Chair includes the dispute report when reporting on the 1377 activities of the NomCom to the IETF community. 1379 7. Member, Trustee, and Director Recall 1381 The following rules apply to the recall process. If necessary, a 1382 paragraph discussing the interpretation of each rule is included. 1384 It applies to IESG and IAB Members, the NomCom appointed IETF Trust 1385 Trustees, and the NomCom appointed IETF LLC Directors. 1387 7.1. Petition 1389 At any time, a signed petition (email is acceptable) may be submitted 1390 to the Internet Society President to request the recall of any 1391 sitting IESG or IAB member, or NomCom appointed IETF Trust Trustee, 1392 or NomCom appointed IETF LLC Director. There are two different types 1393 of petitions: a petition by participants of the IETF community, and a 1394 petition by the Ombudsteam as described in [RFC7776]. 1396 7.1.1. Community Petition 1398 A recall petition can be made by at least 20 members of the IETF 1399 community who are qualified to be voting members of a NomCom. All 1400 individual and collective qualifications of NomCom eligibility are 1401 applicable, including that no more than two signatories may have the 1402 same primary affiliation. 1404 Each signature must include a full name, email address, and primary 1405 company or organization affiliation. 1407 The IETF Secretariat is responsible for confirming that each 1408 signatory is qualified to be a voting member of a NomCom. A valid 1409 petition must be signed by at least 20 qualified signatories. 1411 The petition must include a statement of justification for the recall 1412 and all relevant and appropriate supporting documentation. 1414 The petition and its signatories must be announced to the IETF 1415 community. 1417 7.1.2. Ombudsteam Petition 1419 The Ombudsteam process allows the Ombudsteam to form a recall 1420 petition on its own without requiring 20 signatories from the 1421 community. As defined in [RFC7776], the petition and its signatories 1422 (the Ombudsteam) shall be announced to the IETF community, and a 1423 Recall Committee Chair shall be appointed to complete the Recall 1424 Committee process. It is expected that the Recall Committee will 1425 receive a briefing from the Ombudsteam explaining why recall is 1426 considered an appropriate remedy. 1428 7.2. Recall Committee Chair 1430 The Internet Society President shall appoint a Recall Committee 1431 Chair. 1433 The Internet Society President must not evaluate the recall request. 1434 It is explicitly the responsibility of the IETF community to evaluate 1435 the behavior of its leaders. 1437 7.3. Recall Committee Creation 1439 The recall committee is created according to the same rules as is the 1440 NomCom with the qualifications that both the person being 1441 investigated and the parties requesting the recall must not be a 1442 member of the recall committee in any capacity. 1444 7.4. Recall Committee Rules 1446 The recall committee operates according to the same rules as the 1447 NomCom with the qualification that there is no confirmation process. 1449 7.5. Recall Committee Operation 1451 The recall committee investigates the circumstances of the 1452 justification for the recall and votes on its findings. 1454 The investigation must include at least both an opportunity for the 1455 member being recalled to present a written statement and consultation 1456 with third parties. 1458 7.6. 3/4 Majority 1460 A 3/4 majority of the members who vote on the question is required 1461 for a recall. 1463 7.7. Position To Be Filled 1465 If a sitting member is recalled, the open position is to be filled 1466 according to the mid-term vacancy rules. 1468 8. IANA Considerations 1470 No IANA actions required. 1472 9. Security Considerations 1474 Any selection, confirmation, or recall process necessarily involves 1475 investigation into the qualifications and activities of prospective 1476 candidates. The investigation may reveal confidential or otherwise 1477 private information about candidates to those participating in the 1478 process. Each person who participates in any aspect of the process 1479 must maintain the confidentiality of any and all information not 1480 explicitly identified as suitable for public dissemination. 1482 When the NomCom decides it is necessary to share confidential or 1483 otherwise private information with others, the dissemination must be 1484 minimal and must include a prior commitment from all persons 1485 consulted to observe the same confidentiality rules as the NomCom 1486 itself. 1488 10. References 1490 10.1. Normative References 1492 [I-D.ietf-iasa2-consolidated-upd] 1493 Klensin, J., "Consolidated IASA 2.0 Updates of IETF 1494 Administrative Terminology", draft-ietf-iasa2- 1495 consolidated-upd-07 (work in progress), March 2019. 1497 [I-D.ietf-iasa2-rfc4071bis] 1498 Haberman, B., Hall, J., and J. Livingood, "Structure of 1499 the IETF Administrative Support Activity, Version 2.0", 1500 draft-ietf-iasa2-rfc4071bis-11 (work in progress), April 1501 2019. 1503 [I-D.ietf-iasa2-trust-update] 1504 Arkko, J. and T. Hardie, "Update to the Process for 1505 Selection of Trustees for the IETF Trust", draft-ietf- 1506 iasa2-trust-update-03 (work in progress), February 2019. 1508 [RFC3777] Galvin, J., Ed., "IAB and IESG Selection, Confirmation, 1509 and Recall Process: Operation of the Nominating and Recall 1510 Committees", RFC 3777, DOI 10.17487/RFC3777, June 2004, 1511 . 1513 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 1514 Confirmation, and Recall Process: Operation of the 1515 Nominating and Recall Committees", BCP 10, RFC 7437, DOI 1516 10.17487/RFC7437, January 2015, . 1519 [RFC7776] Resnick, P. and A. Farrel, "IETF Anti-Harassment 1520 Procedures", BCP 25, RFC 7776, DOI 10.17487/RFC7776, March 1521 2016, . 1523 10.2. Informative References 1525 [Err232] RFC Errata, "Erratum ID 232", RFC 3777. 1527 [Err4179] RFC Errata, "Erratum ID 4179", RFC 3777. 1529 [RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, DOI 10.17487/ 1530 RFC3710, February 2004, . 1533 [RFC3797] Eastlake 3rd, D., "Publicly Verifiable Nominations 1534 Committee (NomCom) Random Selection", RFC 3797, DOI 1535 10.17487/RFC3797, June 2004, . 1538 [RFC8318] Dawkins, S., "IAB, IESG, and IAOC Selection, Confirmation, 1539 and Recall Process: IAOC Advisor for the Nominating 1540 Committee", BCP 10, RFC 8318, DOI 10.17487/RFC8318, 1541 January 2018, . 1543 Appendix A. Changes Since RFC 3777 1545 o Converted source file from nroff to XML, resulting in some 1546 reformatting. 1548 o Applied errata for RFC 3777 ([Err232] and [Err4179]). 1550 o Applied RFC 5078 update. 1552 o Applied RFC 5633 update. 1554 o Applied RFC 5680 update. 1556 o Applied RFC 6859 update. 1558 o Corrected a few grammatical errors. 1560 o Added a reference to RFC 3710. 1562 Appendix B. Changes Since RFC 7437 1564 o Changed all mentions of the Internet Administrative Oversight 1565 committee (IAOC), and replaced it with the appropriate references 1566 to the IETF Administration LLC (IETF LLC). This included making 1567 changes on an as needed basis to some aspects of the process for 1568 the IETF LLC, in accordance with IASA2. 1570 o Revised definition of IETF Executive Director, and added 1571 definition of "Managing Director, IETF Secretariat". Changed text 1572 to "Managing Director, IETF Secretariat" where appropriate. 1574 o Added references to appropriate IASA2 documents. 1576 o Modified the Advice and Consent model to enable IESG, IAB, and 1577 IETF LLC to communicate directly with the NomCom rather than via 1578 the Managing Director, IETF Secretariat. 1580 o Updated removal text to reflect the new LLC rules, which enables 1581 removal via the LLC or the IETF recall process, except for the 1582 ISOC-appointed Director. 1584 o Updated the document to clarify that there are members of the IAB 1585 and IESG, Trustees of the IETF Trust, and Director of the IETF 1586 LLC. 1588 o Updated document to also specify procedures for the NomCom 1589 appointed IETF Trust Trustees. 1591 o Revised Abstract and Introduction to provide current context. 1593 o Changed "nominating committee" to "NomCom" throughout the document 1594 because it is what most use to describe the IETF Nominating 1595 Committee. 1597 o Added that the IETF Trust Trustees and IETF LLC Directors, each 1598 may appoint a liaison to the NomCom. 1600 o Incorporated the update to RFC7437 done by RFC7776. 1602 o Incorporated the update to RFC7437 done by [RFC8318] and updated 1603 it to refer to the IETF Trust and IETF LLC, instead of the IAOC. 1605 o Editorial changes. 1607 Appendix C. Oral Tradition 1609 Over the years, various NomComs have learned through oral tradition 1610 passed on by liaisons that there are certain consistencies in the 1611 process and information considered during deliberations. Some items 1612 from that oral tradition are collected here to facilitate its 1613 consideration by future NomComs. 1615 1. It has been found that experience as an IETF Working Group Chair 1616 or an IRTF Research Group Chair is helpful in giving a nominee 1617 experience of what the job of an Area Director involves. It also 1618 helps a NomCom judge the technical, people, and process 1619 management skills of the nominee. 1621 2. No person should serve both on the IAB and as an Area Director, 1622 except the IETF Chair whose roles as an IAB member and Area 1623 Director of the General Area are set out elsewhere. 1625 3. The strength of the IAB is found in part in the balance of the 1626 demographics of its members (e.g., national distribution, years 1627 of experience, gender, etc.), the combined skill set of its 1628 members, and the combined sectors (e.g., industry, academia, 1629 etc.) represented by its members. 1631 4. There are no term limits explicitly because the issue of 1632 continuity versus turnover should be evaluated each year 1633 according to the expectations of the IETF community, as it is 1634 understood by each NomCom. 1636 5. The number of NomCom members with the same primary affiliation is 1637 limited in order to avoid the appearance of improper bias in 1638 choosing the leadership of the IETF. Rather than defining 1639 precise rules for how to define "affiliation", the IETF community 1640 depends on the honor and integrity of the participants to make 1641 the process work. 1643 Appendix D. Nominating Committee Timeline 1645 This appendix is included for the convenience of the reader and is 1646 not to be interpreted as the definitive timeline. It is intended to 1647 capture the detail described elsewhere in this document in one place. 1648 Although every effort has been made to ensure the description here is 1649 consistent with the description elsewhere, if there are any conflicts 1650 the definitive rule is the one in the main body of this document. 1652 The only absolute in the timeline rules for the annual process is 1653 that its completion is due by the First IETF of the year after the 1654 NomCom begins its term. This is supported by the fact that the 1655 confirmed candidate terms begin during the week of the First IETF. 1657 The overall annual process is designed to be completed in seven 1658 months. It is expected to start nine months prior to the First IETF. 1659 The time is split between three major components of the process 1660 roughly as follows: 1662 1. First is the selection and organization of the committee members. 1663 Three months are allotted for this process. 1665 2. Second is the selection of the candidates by the NomCom. Four 1666 months are allotted for this process. 1668 3. Third is the confirmation of the candidates by their respective 1669 confirming bodies. Two months are allotted for this process. 1671 The following list captures the details of the milestones within each 1672 component. For illustrative purposes, the list presumes the Friday 1673 before the First IETF is March 1. Numbers shown in square brackets 1674 indicate the expected number of weeks at each step. 1676 1. BEGIN Eight Months Prior to First IETF (approx. June 1); 1677 Internet Society President appoints the Chair. The appointment 1678 must be done no later than the Second IETF or eight months prior 1679 to the First IETF, whichever comes first. The Chair must be 1680 announced and recognized during a plenary session of the Second 1681 IETF. [0] 1683 2. The Chair establishes and announces milestones to ensure the 1684 timely selection of the NomCom members. [1] 1686 3. The Chair contacts the IESG, IAB, and Internet Society Board of 1687 Trustees and requests a liaison. The Chair contacts the prior 1688 year's Chair and requests an advisor. The Chair obtains the 1689 list of IESG, IAB, IETF Trust, and IETF LLC open positions and 1690 descriptions from the chairs of each group. [0] 1692 4. The Chair announces the solicitation for voting volunteer 1693 members that must remain open for at least 30 days. The 1694 announcement must be done no later than seven months and two 1695 weeks prior to the First IETF (approx. June 15). [6] 1697 5. After the solicitation closes, the Chair announces the pool of 1698 volunteers and the date of the random selection, which must be 1699 at least one week in the future. The announcement must be done 1700 no later than six months and two weeks prior to the First IETF 1701 (approx. July 15). [1] 1703 6. On the appointed day, the random selection occurs and the Chair 1704 announces the members of the committee and the one week 1705 challenge period. The announcement must be done no later than 1706 six months and one week prior to the First IETF (approx. July 1707 22). [1] 1709 7. During the challenge period, the Chair contacts each of the 1710 committee members and confirms their availability to 1711 participate. [0] 1713 8. After the challenge period closes, the Chair announces the 1714 members of the committee and its term begins. The announcement 1715 must be done no later than six months prior to the First IETF 1716 (approx. August 1). [1] 1718 9. The committee has one month during which it is to self-organize 1719 in preparation for completing its assigned duties. This must be 1720 done no later than five months prior to the First IETF (approx. 1721 September 15). [6] 1723 10. END the Committee Member Selection Process; BEGIN the Selection 1724 of Candidates; Time is at least five months prior to the First 1725 IETF (approx. September 22). [0] 1727 11. The Chair establishes and announces the milestones to ensure the 1728 timely selection of the candidates, including a call for 1729 nominations for the open positions. The announcement must be 1730 done no later than five months prior to the First IETF (approx. 1731 October 1). [1] 1733 12. Over the next three months, the NomCom collects input and 1734 deliberates. It should plan to conduct interviews and other 1735 consultations during the Third IETF. The committee is due to 1736 complete its candidate selection no later than two months prior 1737 to the First IETF (approx. January 1). [17] 1739 13. END the Selection of Candidates; BEGIN the Confirmation of 1740 Candidates; Time is at least two months prior to the First IETF 1741 (approx. January 1). [0] 1743 14. The committee presents its candidates to their respective 1744 confirming bodies. The presentation must be done no later than 1745 two months prior to the First IETF (approx. January 1). [0] 1747 15. The confirming bodies have one month to deliberate and, in 1748 communication with the NomCom, accept or reject candidates. [4] 1750 16. The Chair notifies and advises unsuccessful nominees that they 1751 have not been selected. [1] 1753 17. The Chair announces the confirmed candidates. The announcement 1754 must be done no later than one month prior to the First IETF 1755 (approx. February 1). [4] 1757 Appendix E. Acknowledgments 1759 A great deal of work went into the RFCs that preceded this one. The 1760 2014 NomCom and this editor would like to thank all of them once 1761 again for the time and energy it took to get us to where we are now. 1762 In no particular order, we acknowledge: 1764 Jeff Case Fred Baker John Curran 1765 Guy Almes Geoff Huston Mike St. Johns 1766 Donald Eastlake Avri Doria Bernard Adoba 1767 Ted T'so Phil Roberts Jim Galvin 1768 Harald Alvestrand Leslie Daigle Joel Halpern 1769 Thomas Narten Spencer Dawkins Barry Leiba 1770 Lars Eggert Ross Callon Brian Carpenter 1771 Robert Elz Bernie Hoeneisen John Klensin 1772 Danny McPherson S. Moonesamy Scott Bradner 1773 Ralph Droms Pekka Savola 1775 Allison Mankin and Russ White provided early reviews and feedback 1776 about this document. 1778 Jari Arkko was very helpful by independently verifying that the 1779 previous text from all the merged documents was marshaled correctly 1780 into this one, and Adrian Farrel and Brian Carpenter caught the nits 1781 that fell through the cracks. 1783 Appendix F. Change log [RFC Editor: Please remove] 1785 draft-ietf-iasa2-rfc74337bis-07, 2019-June-7 1787 * Added reference to [I-D.ietf-iasa2-consolidated-upd] in 1788 Section 2. 1789 * Changed reference to RFC3710 to Informational. 1790 * Removed step 3 from IAB mid-term vacancies in Section 3.8 as it 1791 was redundant with step 4. 1792 * Correct summary below for -06 version. 1793 * Editorial changes. 1795 draft-ietf-iasa2-rfc74337bis-06, 2019-March-26 1797 * Removed IETF LLC from the list of positions who don't have term 1798 limits in Section 3.2. 1799 * Added IETF Trust to the list of positions who can be recalled 1800 in Section 5.11. 1801 * Editorial changes. 1803 draft-ietf-iasa2-rfc74337bis-05, 2019-January-11: 1805 * Changed text to point to appropriate Sections of 1806 [I-D.ietf-iasa2-rfc4071bis]. 1807 * Editorial changes. 1809 draft-ietf-iasa2-rfc74337bis-04, 2019-January-3: 1811 * Added IETF Trust to the title. 1812 * Changed references to point to current IASA 2.0 structure 1813 document [I-D.ietf-iasa2-rfc4071bis] 1814 * Added IETF Trust to a few places it was missing. 1815 * Editorial changes. 1817 draft-ietf-iasa2-rfc74337bis-03, 2018-October-22: 1819 * Revised Section 7 to focus on repeal of the the NomCom appoint 1820 LLC Director positions. 1821 * Added that the IETF Trust Trustees and IETF LLC Directors, each 1822 may appoint a liaison to the NomCom. 1823 * Incorporated the update to RFC7437 done by RFC7776. 1824 * Incorporated the update to RFC7437 done by [RFC8318] and 1825 updated it to refer to the IETF Trust and IETF LLC. instead of 1826 the IAOC. 1827 * Editorial changes. 1829 draft-ietf-iasa2-rfc74337bis-02, 2018-October-19: 1831 * Added "IETF" before Nominating and Recall Committees in the 1832 title. 1833 * Added leading capitalization to Trustee(s) and Director(s) for 1834 consistency. 1835 * Fixed other minor grammatical, spelling, or abbreviation nits. 1837 draft-ietf-iasa2-rfc74337bis-01, 2018-October-16: 1839 * Modified the Advice and Consent model to enable IESG, IAB, and 1840 IETF LLC to communicate directly with the NomCom rather than 1841 via the Managing Director, IETF Secretariat. 1842 * Updated member removal text to reflect the new LLC rules, which 1843 enables removal via the LLC or the IETF recall process, except 1844 for the ISOC-appointed Director. 1845 * Removed discussion text from the volunteer eligibility section. 1846 This means that IETF LLC employees and contractors cannot 1847 volunteer for the NomCom but does not extend that prohibition 1848 to ISOC employees and contractors. 1849 * Updated the document to clarify that there are members of the 1850 IAB and IESG, Trustees of the IETF Trust, and Directors of the 1851 IETF LLC. 1853 * Removed ISOC Board of Trustees members from the definition of 1854 "sitting members" because it doesn't apply. 1855 * Updated document to also include procedures for the NomCom 1856 appointed IETF Trust Trustees. 1857 * Revised Abstract and Introduction to provide current context. 1858 * Changed "nominating committee" to "NomCom" throughout the 1859 document because it is what most use to describe the IETF 1860 Nominating Committee. 1861 * Added an no-actions IANA Considerations Section. 1862 * Editorial changes. 1864 draft-ietf-iasa2-rfc74337bis-00, 2018-October-12: 1865 Initial bis draft, Changes include: 1867 * Changed all mentions of the Internet Administrative Oversight 1868 committee (IAOC), and replaced it with the appropriate 1869 references to the IETF Administration LLC (IETF LLC). This 1870 included making changes on an as needed basis to some aspects 1871 of the process for the IETF LLC, in accordance with IASA2. 1872 * Revised definition of IETF Executive Director, and added 1873 definition of "Managing Director, IETF Secretariat". Changed 1874 text to "Managing Director, IETF Secretariat" where 1875 appropriate. 1876 * Added references to appropriate IASA2 documents. 1877 * Corrected a few grammatical errors. 1879 Authors' Addresses 1881 Murray S. Kucherawy (editor) 1882 270 Upland Drive 1883 San Francisco, CA 94127 1884 United States 1886 Email: superuser@gmail.com 1888 Robert M. Hinden (editor) 1889 Check Point Software 1890 San Carlos, CA 1891 USA 1893 Email: bob.hinden@gmail.com 1894 Jason Livingood (editor) 1895 Comcast 1896 Philadelphia, PA 1897 USA 1899 Email: jason_livingood@comcast.com