idnits 2.17.1 draft-ietf-nomcom-rfc2727bis-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 40 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 6 instances of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 6, 2003) is 7570 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '3' is defined on line 1369, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 2777 (ref. '1') (Obsoleted by RFC 3797) -- Obsolete informational reference (is this intentional?): RFC 2727 (ref. '2') (Obsoleted by RFC 3777) -- Obsolete informational reference (is this intentional?): RFC 2282 (ref. '3') (Obsoleted by RFC 2727) Summary: 3 errors (**), 0 flaws (~~), 4 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Galvin, Ed. 3 Internet-Draft eList eXpress LLC 4 Expires: February 4, 2004 August 6, 2003 6 IAB and IESG Selection, Confirmation, and Recall Process: Operation 7 of the Nominating and Recall Committees 8 draft-ietf-nomcom-rfc2727bis-07.txt 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that other 17 groups may also distribute working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at http:// 25 www.ietf.org/ietf/1id-abstracts.txt. 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 This Internet-Draft will expire on February 4, 2004. 32 Copyright Notice 34 Copyright (C) The Internet Society (2003). All Rights Reserved. 36 Abstract 38 The process by which the members of the IAB and IESG are selected, 39 confirmed, and recalled is specified. This document is a 40 self-consistent, organized compilation of the process as it was known 41 at the time of publication. 43 Discussion of this Draft 45 Please direct all comments, suggestions, and questions regarding this 46 draft to the following mailing list: 48 ietf-nomcom@lists.elistx.com 50 To subscribe to that mailing list you may send a message with the 51 single word "subscribe" in the body to: 53 ietf-nomcom-request@lists.elistx.com 55 Or you may visit the web-based subscription manager at: 57 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 3. General . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 64 4. Nominating Committee Selection . . . . . . . . . . . . . . . . 11 65 5. Nominating Committee Operation . . . . . . . . . . . . . . . . 19 66 6. Dispute Resolution Process . . . . . . . . . . . . . . . . . . 25 67 7. Member Recall . . . . . . . . . . . . . . . . . . . . . . . . 27 68 8. Changes From RFC2727 . . . . . . . . . . . . . . . . . . . . . 29 69 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 31 70 10. Security Considerations . . . . . . . . . . . . . . . . . . . 33 71 Informative References . . . . . . . . . . . . . . . . . . . . 34 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 34 73 A. Oral Tradition . . . . . . . . . . . . . . . . . . . . . . . . 35 74 B. Nominating Committee Timeline . . . . . . . . . . . . . . . . 36 75 Intellectual Property and Copyright Statements . . . . . . . . 39 77 1. Introduction 79 This document is a revision of and supercedes RFC2727. [2] It is a 80 complete specification of the process by which members of the IAB and 81 IESG are selected, confirmed, and recalled as of the date of its 82 approval. 84 The following two assumptions continue to be true of this 85 specification. 87 1. The Internet Research Task Force (IRTF) and Internet Research 88 Steering Group (IRSG) are not a part of the process described 89 here. 91 2. The organization (and re-organization) of the IESG is not a part 92 of the process described here. 94 The time frames specified here use IETF meetings as a frame of 95 reference. The time frames assume that the IETF meets three times 96 per calendar year with approximately equal amounts of time between 97 them. The meetings are referred to as the First IETF, Second IETF, or 98 Third IETF as needed. 100 The next section lists the words and phrases commonly used throughout 101 this document with their intended meaning. 103 The majority of this document is divided into four major topics as 104 follows. 106 General: This a set of rules and constraints that apply to the 107 selection and confirmation process as a whole. 109 Nominating Committee Selection: This is the process by which the 110 volunteers who will serve on the committee are recognized. 112 Nominating Committee Operation: This is the set of principles, rules, 113 and constraints that guide the activities of the nominating 114 committee, including the confirmation process. 116 Member Recall: This is the process by which the behavior of a sitting 117 member of the IESG or IAB may be questioned, perhaps resulting in 118 the removal of the sitting member. 120 A final section describes how this document differs from its 121 predecessor: RFC2727. [2] 123 An appendix of useful facts and practices collected from previous 124 nominating committees is also included. 126 2. Definitions 128 The following words and phrases are commonly used throughout this 129 document. They are listed here with their intended meaning for the 130 convenience of the reader. 132 candidate: A nominee who has been selected to be considered for 133 confirmation by a confirming body. 135 confirmed candidate: A candidate that has been reviewed and approved 136 by a confirming body. 138 nominating committee term: The term begins when its members are 139 officially announced, which is expected to be prior to the Third 140 IETF to ensure it is fully operational at the Third IETF. The 141 term ends at the Third IETF (not three meetings) after the next 142 nominating committee's term begins. 144 nominee: A person who is being or has been considered for one or more 145 open positions of the IESG or IAB. 147 sitting member: A person who is currently serving a term of 148 membership in the IESG, IAB or ISOC Board of Trustees. 150 3. General 152 The following set of rules apply to the process as a whole. If 153 necessary, a paragraph discussing the interpretation of each rule is 154 included. 156 1. The annual process is expected to be completed within 7 months. 158 The annual process is expected to be completed one month prior to 159 the Friday of the week before the First IETF. It is expected to 160 begin at least 8 months prior to the Friday of the week before 161 the First IETF. 163 The process officially begins with the announcement of the Chair 164 of the committee. The process officially ends when all confirmed 165 candidates have been announced. 167 The annual process is comprised of three major components as 168 follows. 170 1. The selection and organization of the nominating committee 171 members. 173 2. The selection of candidates by the nominating committee. 175 3. The confirmation of the candidates. 177 There is an additional month set aside between when the annual 178 process is expected to end and the term of the new candidates is 179 to begin. This time may be used during unusual circumstances to 180 extend the time allocated for any of the components listed above. 182 2. The principal functions of the nominating committee are to review 183 each open IESG and IAB position and to either nominate its 184 incumbent or a superior candidate. 186 Although there is no term limit for serving in any IESG or IAB 187 position, the nominating committee may use length of service as 188 one of its criteria for evaluating an incumbent. 190 The nominating committee does not select the open positions to be 191 reviewed; it is instructed as to which positions to review. 193 The nominating committee will be given the title of the positions 194 to be reviewed and a brief description of the desirable set of 195 qualifications of the candidate that is nominated to fill each 196 position. 198 Incumbents must notify the nominating committee if they wish to 199 be nominated. 201 The nominating committee does not confirm its candidates; it 202 presents its candidates to the appropriate confirming body as 203 indicated below. 205 A superior candidate is one who the nominating committee believes 206 would contribute in such a way as to improve or enhance the body 207 to which he or she is nominated. 209 3. One-half of each of the then current IESG and IAB positions is 210 selected to be reviewed each year. 212 The intent of this rule to ensure the review of approximately 213 one-half of each of the IESG and IAB sitting members each year. 214 It is recognized that circumstances may exist that will require 215 the nominating committee to review more or less than one-half of 216 the current positions, e.g., if the IESG or IAB have re-organized 217 prior to this process and created new positions, if there are an 218 odd number of current positions, or if a member unexpectedly 219 resigns. 221 4. Confirmed candidates are expected to serve at least a 2 year 222 term. 224 The intent of this rule is to ensure that members of the IESG and 225 IAB serve the number of years that best facilitates the review of 226 one-half of the members each year. 228 It is consistent with this rule for the nominating committee to 229 choose one or more of the currently open positions to which it 230 may assign a term greater than 2 years in order to ensure the 231 ideal application of this rule in the future. 233 It is consistent with this rule for the nominating committee to 234 choose one or more of the currently open positions that share 235 responsibilities with other positions (both those being reviewed 236 and those sitting) to which it may assign a term greater than 2 237 years to ensure that all such members will not be reviewed at the 238 same time. 240 All sitting member terms end during the First IETF meeting 241 corresponding to the end of the term for which they were 242 confirmed. All confirmed candidate terms begin during the First 243 IETF meeting corresponding to the beginning of the term for which 244 they were confirmed. Normally, the confirmed candidate's term 245 begins when the currently sitting member's term ends on the last 246 day of the meeting. A term may begin or end no sooner than the 247 first day of the meeting and no later than the last day of the 248 meeting as determined by the mutual agreement of the currently 249 sitting member and the confirmed candidate. The confirmed 250 candidate's term may overlap the sitting member's term during the 251 meeting as determined by their mutual agreement. 253 5. Mid-term vacancies are filled by the same rules as documented 254 here with four qualifications. 256 First, when there is only one official nominating committee the 257 body with the mid-term vacancy relegates the responsibility to 258 fill the vacancy to it. If the mid-term vacancy occurs during 259 the period of time that the term of the prior year's nominating 260 committee overlaps with the term of the current year's nominating 261 committee, the body with the mid-term vacancy must relegate the 262 responsibility to fill the vacancy to the prior year's nominating 263 committee. 265 Second, if it is the case that the nominating committee is 266 reconvening to fill the mid-term vacancy, then the candidate 267 selection and confirmation process is expected to be completed 268 within 6 weeks, with all other time periods otherwise unspecified 269 prorated accordingly. 271 Third, the confirming body has two weeks from the day it is 272 notified of a candidate to reject the candidate, otherwise the 273 candidate is assumed to have been confirmed. 275 Fourth, the term of the confirmed candidate will be either: 277 1. the remainder of the term of the open position if that 278 remainder is not less than one year. 280 2. the remainder of the term of the open position plus the next 281 2 year term if that remainder is less than one year. 283 In both cases a year is the period of time from a First IETF 284 meeting to the next First IETF meeting. 286 6. All deliberations and supporting information that relates to 287 specific nominees, candidates, and confirmed candidates are 288 confidential. 290 The nominating committee and confirming body members will be 291 exposed to confidential information as a result of their 292 deliberations, their interactions with those they consult, and 293 from those who provide requested supporting information. All 294 members and all other participants are expected to handle this 295 information in a manner consistent with its sensitivity. 297 It is consistent with this rule for current nominating committee 298 members who have served on prior nominating committees to advise 299 the current committee on deliberations and results of the prior 300 committee, as necessary and appropriate. 302 7. Unless otherwise specified, the advice and consent model is used 303 throughout the process. This model is characterized as follows. 305 1. The IETF Executive Director informs the nominating committee 306 of the IESG and IAB positions to be reviewed. 308 The IESG and IAB are responsible for providing a list of the 309 qualifications desired of the candidates selected for their 310 respective open positions to the Executive Director. The 311 lists are to be provided to the nominating committee for its 312 consideration. 314 2. The nominating committee selects candidates and advises each 315 confirming body of its respective candidates. 317 3. The confirming bodies review their respective candidates, 318 they may at their discretion communicate with the nominating 319 committee, and then consent to some, all, or none of the 320 candidates. 322 The sitting IAB members review the IESG candidates. 324 The Internet Society Board of Trustees reviews the IAB 325 candidates. 327 The confirming bodies conduct their review using all 328 information and any means acceptable to them, including but 329 not limited to the supporting information provided by the 330 nominating committee, information known personally to members 331 of the confirming bodies and shared within the confirming 332 body, the results of interactions within the confirming 333 bodies, and the confirming bodies interpretation of what is 334 in the best interests of the IETF community. 336 If all of the candidates are confirmed, the job of the 337 nominating committee with respect to those open positions is 338 complete. 340 If some or none of the candidates submitted to a confirming 341 body are confirmed, the confirming body should communicate 342 with the nominating committee both to explain the reason why 343 all the candidates were not confirmed and to understand the 344 nominating committee's rationale for its candidates. 346 The confirming body may reject individual candidates, in 347 which case the nominating committee must select alternate 348 candidates for the rejected candidates. 350 Any additional time required by the nominating committee 351 should not exceed its maximum time allotment. 353 4. A confirming body decides whether it confirms each candidate 354 using a confirmation decision rule chosen by the confirming 355 body. 357 If a confirming body has no specific confirmation decision 358 rule, then confirming a given candidate should require at 359 least one-half of the confirming body's sitting members to 360 agree to that confirmation. 362 The decision may be made by conducting a formal vote, by 363 asserting consensus based on informal exchanges (e.g. email), 364 or by any other mechanism that is used to conduct the normal 365 business of the confirming body. 367 Regardless of which decision rule the confirming body uses, 368 any candidate that is not confirmed under that rule is 369 considered to be rejected. 371 The confirming body must make its decision within a 372 reasonable timeframe. The results from the confirming body 373 must be reported promptly to the nominating committee. 375 8. The following rules apply to nominees who are currently sitting 376 members of the IESG or IAB, and who are not sitting in an open 377 position being filled by the nominating committe. 379 The confirmation of a candidate to an open position does not 380 automatically create a vacancy in the IESG or IAB position 381 currently occupied by the candidate. The mid-term vacancy can 382 not exist until, first, the candidate formally resigns from the 383 current position and, second, the body with the vacancy formally 384 decides for itself that it wants the nominating committee to fill 385 the mid-term vacancy. 387 The resignation should be effective as of when the term of the 388 new position begins. The resignation may remain confidential to 389 the IAB, IESG, and nominating committee until the confirmed 390 candidate is announced for the new position. 392 Filling a mid-term vacancy is a separate and independent action 393 from the customary action of filling open positions. In 394 particular, a nominating committee must complete its job with 395 respect to filling the open positions and then separately submit 396 a candidate to fill a mid-term vacancy. 398 It is consistent with these rules for the announcements of a 399 resignation, of the existence of a mid-term vacancy, and of the 400 confirmed candidates to all occur at the same time as long as the 401 actual sequence of events that occurred did so in the following 402 order. 404 * The nominating committee completes the advice and consent 405 process for the candidate already sitting on another body. 407 * The newly confirmed candidate resigns from their current 408 position. 410 * The body with the new mid-term vacancy requests that the 411 nominating committee fill the position. 413 * The Executive Director of the IETF informs the nominating 414 committee of the mid-term vacancy. 416 * The nominating committee acts on the request to fill the 417 mid-term vacancy 419 9. All announcements must be made using at least the mechanism used 420 by the IETF Secretariat for its announcements, including a notice 421 on the IETF web site. 423 As of the publication of this document the current mechanism is 424 an email message to both the "ietf" and the "ietf-announce" 425 mailing lists. 427 4. Nominating Committee Selection 429 The following set of rules apply to the creation of the nominating 430 committee and the selection of its members. 432 1. The process of selecting and organizing the members of the 433 nominating committee is expected to be completed within 3 434 months. 436 The selection and organization process must be completed at 437 least one month prior to the Third IETF. This ensures the 438 nominating committee is fully operational and available for 439 interviews and consultation during the Third IETF. 441 2. The term of a nominating committee is expected to be 15 months. 443 It is the intent of this rule that the end of a nominating 444 committee's term overlap by approximately three months the 445 beginning of the term of the next nominating committee. 447 The term of a nominating committee begins when its members are 448 officially announced. The term ends at the Third IETF (not 449 three meetings) after the next nominating committee's term 450 begins. 452 A term is expected to begin at least two months prior to the 453 Third IETF to ensure the nominating committee has at least one 454 month to get organized before preparing for the Third IETF. 456 A nominating committee is expected to complete any 457 work-in-progress before it is dissolved at the end of its term. 459 During the period of time that the terms of the nominating 460 committees overlap, all mid-term vacancies are to be relegated 461 to the prior year's nominating committee. The prior year's 462 nominating committee has no other responsibilities during the 463 overlap period. At all times other than the overlap period 464 there is exactly one official nominating committee and it is 465 responsible for all mid-term vacancies. 467 When the prior year's nominating committee is filling a mid-term 468 vacancy during the period of time that the terms overlap, the 469 nominating committees operate independently. However, some 470 coordination is needed between them. Since the prior year's 471 Chair is a non-voting advisor to the current nominating 472 committee the coordination is expected to be straightforward. 474 3. The nominating committee comprises at least a Chair, 10 voting 475 volunteers, 2 liaisons, and an advisor. 477 Any committee member may propose the addition of an advisor to 478 participate in some or all of the deliberations of the 479 committee. The addition must be approved by all members of the 480 committee according to its established voting mechanism. 481 Advisors participate as individuals. 483 Any committee member may propose the addition of a liaison from 484 other unrepresented organizations to participate in some or all 485 of the deliberations of the committee. The addition must be 486 approved by all members of the committee according to its 487 established voting mechanism. Liaisons participate as 488 representatives of their respective organizations. 490 The Chair is selected according to rules stated elsewhere in 491 this document. 493 The 10 voting volunteers are selected according to rules stated 494 elsewhere in this document. 496 The IESG and IAB liaisons are selected according to rules stated 497 elsewhere in this document. 499 The Chair of last year's nominating committee serves as an 500 advisor according to rules stated elsewhere in this document. 502 None of the Chair, liaisons, or advisors vote on the selection 503 of candidates. They do vote on all other issues before the 504 committee unless otherwise specified. 506 4. The Chair of the nominating committee is responsible for 507 ensuring the nominating committee completes its assigned duties 508 in a timely fashion and performs in the best interests of the 509 IETF community. 511 The Chair must be thoroughly familiar with the rules and 512 guidance indicated throughout this document. The Chair must 513 ensure the nominating committee completes its assigned duties in 514 a manner that is consistent with this document. 516 The Chair must attest by proclamation at a plenary session of 517 the First IETF that the results of the committee represent its 518 best effort and the best interests of the IETF community. 520 The Chair does not vote on the selection of candidates. 522 5. The Internet Society President appoints the Chair, who must meet 523 the same requirements for membership in the nominating committee 524 as a voting volunteer. 526 The nominating committee Chair must agree to invest the time 527 necessary to ensure that the nominating committee completes its 528 assigned duties and to perform in the best interests of the IETF 529 community in that role. 531 The appointment must be completed no later than the Second IETF 532 meeting to ensure it can be announced during a plenary session 533 at that meeting. The appointment must be completed as soon as 534 necessary to ensure the annual process can complete at the time 535 specified elsewhere in this document. 537 6. A Chair, in consultation with the Internet Society President, 538 may appoint a temporary substitute. 540 There are a variety of ordinary circumstances that may arise 541 from time to time that could result in a Chair being unavailable 542 to oversee the activities of the committee. The Chair, in 543 consultation with the Internet Society President, may appoint a 544 substitute from a pool comprised of the liaisons currently 545 serving on the committee and the prior year's Chair or designee. 547 Any such appointment must be temporary and does not absolve the 548 Chair of any or all responsibility for ensuring the nominating 549 committee completes its assigned duties in a timely fashion. 551 7. Liaisons are responsible for ensuring the nominating committee 552 in general and the Chair in particular execute their assigned 553 duties in the best interests of the IETF community. 555 Liaisons are expected to represent the views of their respective 556 organizations during the deliberations of the committee. They 557 should provide information as requested or when they believe it 558 would be helpful to the committee. 560 Liaisons from the IESG and IAB are expected to provide 561 information to the nominating committee regarding the operation, 562 responsibility, and composition of their respective bodies. 564 Liaisons are expected to convey questions from the committee to 565 their respective organizations and responses to those questions 566 to the committee, as requested by the committee. 568 Liaisons from the IESG, IAB, and Internet Society Board of 569 Trustees are expected to review the operation and executing 570 process of the nominating committee and to report any concerns 571 or issues to the Chair of the nominating committee immediately. 572 If they can not resolve the issue between themselves liaisons 573 must report the issue to their respective bodies. If their 574 respective body agrees that there is an issue the liaison must 575 report it according to the dispute resolution process stated 576 elsewhere in this document. 578 Liaisons from confirming bodies are expected to assist the 579 committee in preparing the testimony it is required to provide 580 with its candidates. 582 Liaisons may have other nominating committee responsibilities as 583 required by their respective organizations or requested by the 584 nominating committee, except that such responsibilities may not 585 conflict with any other provisions of this document. 587 Liaisons do not vote on the selection of candidates. 589 8. The sitting IAB and IESG members each appoint a liaison from 590 their current membership, someone who is not sitting in an open 591 position, to serve on the nominating committee. 593 9. The Internet Society Board of Trustees may appoint a liaison to 594 the nominating committee. 596 10. An advisor is responsible for such duties as specified by the 597 invitation that resulted in the appointment. 599 Advisors do not vote on the selection of candidates. 601 11. The Chair of the prior year's nominating committee serves as an 602 advisor to the current committee. 604 The prior year's Chair is expected to review the actions and 605 activities of the current Chair and to report any concerns or 606 issues to the nominating committee Chair immediately. If they 607 can not resolve the issue between themselves the prior year's 608 Chair must report it according to the dispute resolution process 609 stated elsewhere in this document. 611 The prior year's Chair may select a designee from a pool 612 composed of the voting volunteers of the prior year's committee 613 and all prior Chairs if the Chair is unavailable. If the prior 614 year's Chair is unavailable or is unable or unwilling to make 615 such a designation in a timely fashion, the Chair of the current 616 year's committee may select a designee in consultation with the 617 Internet Society President. 619 Selecting a prior year's committee member as the designee 620 permits the experience of the prior year's deliberations to be 621 readily available to the current committee. Selecting an 622 earlier prior year Chair as the designee permits the experience 623 of being a Chair as well as that Chair's committee deliberations 624 to be readily available to the current committee. 626 All references to "prior year's Chair" in this document refer to 627 the person serving in that role, whether it is the actual prior 628 year's Chair or a designee. 630 12. Voting volunteers are responsible for completing the tasks of 631 the nominating committee in a timely fashion. 633 Each voting volunteer is expected to participate in all 634 activities of the nominating committee with a level of effort 635 approximately equal to all other voting volunteers. Specific 636 tasks to be completed are established and managed by the Chair 637 according to rules stated elsewhere in this document. 639 13. The Chair must establish and announce milestones for the 640 selection of the nominating committee members. 642 There is a defined time period during which the selection 643 process must be completed. The Chair must establish a set of 644 milestones which, if met in a timely fashion, will result in the 645 completion of the process on time. 647 14. The Chair obtains the list of IESG and IAB positions to be 648 reviewed and announces it along with a solicitation for names of 649 volunteers from the IETF community willing to serve on the 650 nominating committee. 652 The solicitation must permit the community at least 30 days 653 during which they may choose to volunteer to be selected for the 654 nominating committee. 656 The list of open positions is published with the solicitation to 657 facilitate community members choosing between volunteering for 658 an open position and volunteering for the nominating committee. 660 15. Members of the IETF community must have attended at least 3 of 661 the last 5 IETF meetings in order to volunteer. 663 The 5 meetings are the five most recent meetings that ended 664 prior to the date on which the solicitation for nominating 665 committee volunteers was submitted for distribution to the IETF 666 community. 668 The IETF Secretariat is responsible for confirming that 669 volunteers have met the attendance requirement. 671 Volunteers must provide their full name, email address, and 672 primary company or organization affiliation (if any) when 673 volunteering. 675 Volunteers are expected to be familiar with the IETF processes 676 and procedures, which are readily learned by active 677 participation in a working group and especially by serving as a 678 document editor or working group chair. 680 16. Members of the Internet Society Board of Trustees, sitting 681 members of the IAB, and sitting members of the IESG may not 682 volunteer to serve on the nominating committee. 684 17. The Chair announces both the list of the pool of volunteers from 685 which the 10 voting volunteers will be randomly selected and the 686 method with which the selection will be completed. 688 The announcement should be made at least 1 week prior to the 689 date on which the random selection will occur. 691 The pool of volunteers must be enumerated or otherwise indicated 692 according to the needs of the selection method to be used. 694 The announcement must specify the data that will be used as 695 input to the selection method. The method must depend on random 696 data whose value is not known or available until the date on 697 which the random selection will occur. 699 It must be possible to independently verify that the selection 700 method used is both fair and unbiased. A method is fair if each 701 eligible volunteer is equally likely to be selected. A method 702 is unbiased if no one can influence its outcome in favor of a 703 specific outcome. 705 It must be possible to repeat the selection method, either 706 through iteration or by restarting in such a way as to remain 707 fair and unbiased. This is necessary to replace selected 708 volunteers should they become unavailable after selection. 710 The selection method must produce an ordered list of volunteers. 712 One possible selection method is described in RFC2777 [1]. 714 18. The Chair randomly selects the 10 voting volunteers from the 715 pool of names of volunteers and announces the members of the 716 nominating committee. 718 No more than two volunteers with the same primary affiliation 719 may be selected for the nominating committee. The Chair reviews 720 the primary affiliation of each volunteer selected by the method 721 in turn. If the primary affiliation for a volunteer is the same 722 as two previously selected volunteers, that volunteer is removed 723 from consideration and the method is repeated to identify the 724 next eligible volunteer. 726 There must be at least two announcements of all members of the 727 nominating committee. 729 The first announcement should occur as soon after the random 730 selection as is reasonable for the Chair. The community must 731 have at least 1 week during which any member may challenge the 732 results of the random selection. 734 The challenge must be made in writing (email is acceptable) to 735 the Chair. The Chair has 48 hours to review the challenge and 736 offer a resolution to the member. If the resolution is not 737 accepted by the member, that member may report the challenge 738 according to the dispute resolution process stated elsewhere in 739 this document. 741 If a selected volunteer, upon reading the announcement with the 742 list of selected volunteers, finds that two or more other 743 volunteers have the same affiliation, then the volunteer should 744 notify the Chair who will determine the appropriate action. 746 During at least the 1 week challenge period the Chair must 747 contact each of the members and confirm their willingness and 748 availability to serve. The Chair should make every reasonable 749 effort to contact each member. 751 * If the Chair is unable to contact a liaison the problem is 752 referred to the respective organization to resolve. The 753 Chair should allow a reasonable amount of time for the 754 organization to resolve the problem and then may proceed 755 without the liaison. 757 * If the Chair is unable to contact an advisor the Chair may 758 elect to proceed without the advisor, except for the prior 759 year's Chair for whom the Chair must consult with the 760 Internet Society President as stated elsewhere in this 761 document. 763 * If the Chair is unable to contact a voting volunteer the 764 Chair must repeat the random selection process in order to 765 replace the unavailable volunteer. There should be at least 766 1 day between the announcement of the iteration and the 767 selection process. 769 After at least 1 week and confirming that 10 voting volunteers 770 are ready to serve, the Chair makes the second announcement of 771 the members of the nominating committee, which officially begins 772 the term of the nominating committee. 774 19. The Chair works with the members of the committee to organize 775 itself in preparation for completing its assigned duties. 777 The committee has approximately one month during which it can 778 self-organize. Its responsibilities during this time include 779 but are not limited to the following. 781 * Setting up a regular teleconference schedule. 783 * Setting up an internal web site. 785 * Setting up a mailing list for internal discussions. 787 * Setting up an email address for receiving community input. 789 * Establishing operational procedures. 791 * Establishing milestones in order to monitor the progress of 792 the selection process. 794 5. Nominating Committee Operation 796 The following rules apply to the operation of the nominating 797 committee. If necessary, a paragraph discussing the interpretation 798 of each rule is included. 800 The rules are organized approximately in the order in which they 801 would be invoked. 803 1. All rules and special circumstances not otherwise specified are 804 at the discretion of the committee. 806 Exceptional circumstances will occasionally arise during the 807 normal operation of the nominating committee. This rule is 808 intended to foster the continued forward progress of the 809 committee. 811 Any member of the committee may propose a rule for adoption by 812 the committee. The rule must be approved by all members of the 813 committee according to its established voting mechanism. 815 All members of the committee should consider whether the 816 exception is worthy of mention in the next revision of this 817 document and follow-up accordingly. 819 2. The process of selecting candidates to be confirmed by their 820 respective confirming body is expected to be completed within 3 821 months. 823 The selection process must be completed at least two month's 824 prior to the First IETF. This ensures the nominating committee 825 has sufficient time to complete the confirmation process. 827 3. The process of confirming the candidates is expected to be 828 completed within 1 month. 830 The confirmation process must be completed at least one month 831 prior to the First IETF. 833 4. The Chair must establish for the nominating committee a set of 834 milestones for the candidate selection and confirmation process. 836 There is a defined time period during which the candidate 837 selection and confirmation process must be completed. The Chair 838 must establish a set of milestones which, if met in a timely 839 fashion, will result in the completion of the process on time. 840 The Chair should allow time for iterating the activities of the 841 committee if one or more candidates is not confirmed. 843 The Chair should ensure that all committee members are aware of 844 the milestones. 846 5. The Chair must establish a voting mechanism. 848 The committee must be able to objectively determine when a 849 decision has been made during its deliberations. The criteria 850 for determining closure must be established and known to all 851 members of the nominating committee. 853 6. At least a quorum of committee members must participate in a 854 vote. 856 Only voting volunteers vote on a candidate selection. For a 857 candidate selection vote a quorum is comprised of at least 7 of 858 the voting volunteers. 860 At all other times a quorum is present if at least 75% of the 861 nominating committee members are participating. 863 7. Any member of the nominating committee may propose to the 864 committee that any other member except the Chair be recalled. 865 The process for recalling the Chair is defined elsewhere in this 866 document. 868 There are a variety of ordinary circumstances that may arise 869 that could result in one or more members of the committee being 870 unavailable to complete their assigned duties, for example 871 health concerns, family issues, or a change of priorities at 872 work. A committee member may choose to resign for unspecified 873 personal reasons. In addition, the committee may not function 874 well as a group because a member may be disruptive or otherwise 875 uncooperative. 877 Regardless of the circumstances, if individual committee members 878 can not work out their differences between themselves, the 879 entire committee may be called upon to discuss and review the 880 circumstances. If a resolution is not forthcoming a vote may be 881 conducted. A member may recalled if at least a quorum of all 882 committee members agree, including the vote of the member being 883 recalled. 885 If a liaison member is recalled the committee must notify the 886 affected organization and must allow a reasonable amount of time 887 for a replacement to be identified by the organization before 888 proceeding. 890 If an advisor member other than the prior year's Chair is 891 recalled, the committee may choose to proceed without the 892 advisor. In the case of the prior year's Chair, the Internet 893 Society President must be notified and the current Chair must be 894 allowed a reasonable amount of time to consult with the Internet 895 Society President to identify a replacement before proceeding. 897 If a voting volunteer member is recalled the committee may 898 choose to proceed with only 9 voting volunteers at its own 899 discretion. In all other cases the Chair must repeat the random 900 selection process including an announcement of the iteration 901 prior to the actual selection as stated elsewhere in this 902 document. 904 A change in the primary affiliation of a voting volunteer during 905 the term of the nominating committee is not a cause to request 906 the recall of that volunteer, even if the change would result in 907 more than two voting volunteers with the same affiliation. 909 8. Only the prior year's Chair may request the recall of the 910 current Chair. 912 It is the responsibility of the prior year's Chair to ensure the 913 current Chair completes the assigned tasks in a manner 914 consistent with this document and in the best interests of the 915 IETF community. 917 Any member of the committee who has an issue or concern 918 regarding the Chair should report it to the prior year's Chair 919 immediately. The prior year's Chair is expected to report it to 920 the Chair immediately. If they can not resolve the issue 921 between themselves the prior year's Chair must report it 922 according to the dispute resolution process stated elsewhere in 923 this document. 925 9. All members of the nominating committee may participate in all 926 deliberations. 928 The emphasis of this rule is that no member can be explicitly 929 excluded from any deliberation. However, a member may 930 individually choose not to participate in a deliberation. 932 10. The Chair announces the open positions to be reviewed and the 933 call for nominees. 935 The call for nominees must include a request for comments 936 regarding the past performance of incumbents, which will be 937 considered during the deliberations of the nominating committee. 939 The call must request that a nomination include a valid, working 940 email address, a telephone number, or both for the nominee. The 941 nomination must include the set of skills or expertise the 942 nominator believes the nominee has that would be desirable. 944 11. Any member of the IETF community may nominate any member of the 945 IETF community for any open position, whose eligibility to serve 946 will be confirmed by the nominating committee. 948 A self-nomination is permitted. 950 Nominating committee members are not eligible to be considered 951 for filling any open position by the nominating committee on 952 which they serve. They become ineligible as soon as the term of 953 the nominating committee on which they serve officially begins. 954 They remain ineligible for the duration of that nominating 955 committee's term. 957 Although each nominating committee's term overlaps with the 958 following nominating committee's term, nominating committee 959 members are eligible for nomination by the following committee 960 if not otherwise disqualified. 962 Members of the IETF community who were recalled from any IESG or 963 IAB position during the previous two years are not eligible to 964 be considered for filling any open position. 966 12. The nominating committee selects candidates based on its 967 understanding of the IETF community's consensus of the 968 qualifications required to fill the open positions. 970 The intent of this rule is to ensure that the nominating 971 committee consults with a broad base of the IETF community for 972 input to its deliberations. In particular, the nominating 973 committee must determine if the desired qualifications for the 974 open positions matches its understanding of the qualifications 975 desired by the IETF community. 977 The consultations are permitted to include names of nominees, if 978 all parties to the consultation agree to observe the same 979 confidentiality rules as the nominating committee itself. 981 A broad base of the community should include the existing 982 members of the IAB and IESG, especially sitting members who 983 share responsibilities with open positions, e.g., co-Area 984 Directors. 986 Only voting volunteer members vote to select candidates. 988 13. Nominees should be advised that they are being considered and 989 must consent to their nomination prior to being chosen as 990 candidates. 992 Although the nominating committee will make every reasonable 993 effort to contact and to remain in contact with nominees, any 994 nominee whose contact information changes during the process and 995 who wishes to still be considered should inform the nominating 996 committee of the changes. 998 A nominee's consent must be written (email is acceptable) and 999 must include a commitment to provide the resources necessary to 1000 fill the open position and an assurance that the nominee will 1001 perform the duties of the position for which they are being 1002 considered in the best interests of the IETF community. 1004 Consenting to a nomination must occur prior to a nominee being a 1005 candidate and may occur as soon after the nomination as needed 1006 by the nominating committee. 1008 Consenting to a nomination must not imply the nominee will be a 1009 candidate. 1011 The nominating committee should help nominees provide 1012 justification to their employers. 1014 14. The nominating committee advises the confirming bodies of their 1015 candidates, specifying a single candidate for each open position 1016 and testifying as to how each candidate meets the qualifications 1017 of an open position. 1019 For each candidate, the testimony must include a brief statement 1020 of the qualifications for the position that is being filled, 1021 which may be exactly the qualifications that were requested. If 1022 the qualifications differ from the desired qualifications 1023 originally requested a brief statement explaining the difference 1024 must be included. 1026 The testimony may include either or both of a brief resume of 1027 the candidate and a brief summary of the deliberations of the 1028 nominating committee. 1030 15. Confirmed candidates must consent to their confirmation and 1031 rejected candidates and nominees must be notified before 1032 confirmed candidates are announced. 1034 It is not necessary to notify and get consent from all confirmed 1035 candidates together. 1037 A nominee may not know they were a candidate. This permits a 1038 candidate to be rejected by a confirming body without the 1039 nominee knowing about the rejection. 1041 Rejected nominees, who consented to their nomination, and 1042 rejected candidates must be notified prior to announcing the 1043 confirmed candidates. 1045 It is not necessary to announce all confirmed candidates 1046 together. 1048 The nominating committee must ensure that all confirmed 1049 candidates are prepared to serve prior to announcing their 1050 confirmation. 1052 16. The nominating committee should archive the information it has 1053 collected or produced for a period of time not to exceed its 1054 term. 1056 The purpose of the archive is to assist the nominating committee 1057 should it be necessary for it to fill a mid-term vacancy. 1059 The existence of an archive, how it is implemented, and what 1060 information to archive is at the discretion of the committee. 1061 The decision must be approved by a quorum of the voting 1062 volunteer members. 1064 The implementation of the archive should make every reasonable 1065 effort to ensure that the confidentiality of the information it 1066 contains is maintained. 1068 6. Dispute Resolution Process 1070 The dispute resolution process described here is to be used as 1071 indicated elsewhere in this document. Its applicability in other 1072 circumstances is beyond the scope of this document. 1074 The nominating committee operates under a strict rule of 1075 confidentiality. For this reason when process issues arise it is 1076 best to make every reasonable effort to resolve them within the 1077 committee. However, when circumstances do not permit this or no 1078 resolution is forthcoming, the process described here is to be used. 1080 The following rules apply to the process. 1082 1. The results of this process are final and binding. There is no 1083 appeal. 1085 2. The process begins with the submission of a request as described 1086 below to the Internet Society President. 1088 3. As soon as the process begins, the nominating committee may 1089 continue those activities that are unrelated to the issue to be 1090 resolved except that it must not submit any candidates to a 1091 confirming body until the issue is resolved. 1093 4. All parties to the process are subject to the same 1094 confidentiality rules as each member of the nominating committee. 1096 5. The process should be completed within two weeks. 1098 The process is as follows. 1100 1. The party seeking resolution submits a written request (email is 1101 acceptable) to the Internet Society President detailing the issue 1102 to be resolved. 1104 2. The Internet Society President appoints an arbiter to investigate 1105 and resolve the issue. A self-appointment is permitted. 1107 3. The arbiter investigates the issue making every reasonable effort 1108 to understand both sides of the issue. Since the arbiter is 1109 subject to the same confidentiality obligations as all nominating 1110 committee members, all members are expect to cooperate fully with 1111 the arbiter and to provide all relevant information to the 1112 arbiter for review. 1114 4. After consultation with the two principal parties to the issue, 1115 the arbiter decides a resolution. Whatever actions are necessary 1116 to execute the resolution are immediately begun and completed as 1117 quickly as possible. 1119 5. The arbiter summarizes the issue, the resolution, and the 1120 rationale for the resolution for the Internet Society President. 1122 6. In consultation with the Internet Society President, the arbiter 1123 prepares a report of the dispute and its resolution. The report 1124 should include all information that in the judgement of the 1125 arbiter does not violate the confidentiality requirements of the 1126 nominating committee. 1128 7. The Chair includes the dispute report when reporting on the 1129 activities of the nominating committee to the IETF community. 1131 7. Member Recall 1133 The following rules apply to the recall process. If necessary, a 1134 paragraph discussing the interpretation of each rule is included. 1136 1. At any time, at least 20 members of the IETF community, who are 1137 qualified to be voting members of a nominating committee, may 1138 request by signed petition (email is acceptable) to the Internet 1139 Society President the recall of any sitting IAB or IESG member. 1141 All individual and collective qualifications of nominating 1142 committee eligibility are applicable, including that no more than 1143 two signatories may have the same primary affiliation. 1145 Each signature must include a full name, email address, and 1146 primary company or organization affiliation. 1148 The petition must include a statement of justification for the 1149 recall and all relevant and appropriate supporting documentation. 1151 The petition and its signatories must be announced to the IETF 1152 community. 1154 2. Internet Society President shall appoint a Recall Committee 1155 Chair. 1157 The Internet Society President must not evaluate the recall 1158 request. It is explicitly the responsibility of the IETF 1159 community to evaluate the behavior of its leaders. 1161 3. The recall committee is created according to the same rules as is 1162 the nominating committee with the qualifications that both the 1163 person being investigated and the parties requesting the recall 1164 must not be a member of the recall committee in any capacity. 1166 4. The recall committee operates according to the same rules as the 1167 nominating committee with the qualification that there is no 1168 confirmation process. 1170 5. The recall committee investigates the circumstances of the 1171 justification for the recall and votes on its findings. 1173 The investigation must include at least both an opportunity for 1174 the member being recalled to present a written statement and 1175 consultation with third parties. 1177 6. A 3/4 majority of the members who vote on the question is 1178 required for a recall. 1180 7. If a sitting member is recalled the open position is to be filled 1181 according to the mid-term vacancy rules. 1183 8. Changes From RFC2727 1185 This section describes the substantive changes from RFC2727, listed 1186 approximately in the order in which they appear in the document. 1188 1. A section with definitions for words and phrases used throughout 1189 the document was inserted. 1191 2. The role of term limits as a selection criterion was clarified. 1193 3. The NOMCOM must now be provided with a brief description of the 1194 desirable set of qualifications for the candidate to be 1195 nominated for each position. 1197 4. Because of the overlapping terms of successive nominating 1198 committees, the specific committee responsible for a mid-term 1199 vacancy was specified. 1201 5. The characterization of the advice and consent model was revised 1202 to permit the confirming body to communicate with the nominating 1203 committee during the approval process. 1205 6. A general rule was added to define that all announcements are 1206 made with the usual IETF Secretariat mechanism. 1208 7. Details regarding the expected timeline of the selection and 1209 operation of the committee were made even more explicit. An 1210 Appendix was added that captures all the details for the 1211 convenience of the reader. 1213 8. The term of the nominating committee was extended to 1214 approximately 15 months such that it explicitly overlaps by 1215 approximately 3 months the next year's nominating committee's 1216 term. 1218 9. The terms voting member and non-voting member were replaced by 1219 voting volunteers, liaisons, and advisors. All members vote at 1220 all times except that the only voting volunteers vote on a 1221 candidate selection. 1223 10. The responsibilities of the Chair, liaisons, advisors, and 1224 voting volunteers is now explicitly stated. 1226 11. Processes for recalling members of the committee were added. 1228 12. Liaisons and advisors are no longer required to meet the usual 1229 requirements for nominating committee membership. 1231 13. The Internet Society Board of Trustees may appoint a non-voting 1232 liaison. 1234 14. The eligibility qualifications for the nominating committee was 1235 changed to require attendance at 3 out of 5 of the last five 1236 meetings, to require volunteers to submit identifying contact 1237 information, and to request that volunteers be familiar with 1238 IETF processes and procedures. 1240 15. Some additional clarification was added to the method used to 1241 select volunteers. 1243 16. The process for selecting the 10 voting volunteers had several 1244 clarifications and additional requirements added, including a 1245 challenge process and the requirement to disallow more than two 1246 volunteers with the same primary affiliation. 1248 17. Nominations for open positions should include both contact 1249 information and a description of the skills or expertise the 1250 nominator believes the nominee possesses. 1252 18. Nominees are requested to keep the nominating committee informed 1253 of changes in their contact information. Editorially, the 1254 distinction between a nominee and candidate was emphasized. 1256 19. A description of a testimony to be provided with each candidate 1257 to a confirming body by the nominating committee is specified. 1259 20. The rules regarding the announcement of confirmed candidates 1260 were substantially rewritten to make it easier to understand. 1262 21. The nominating committee is permitted to keep an archive for the 1263 duration of its term of the information it collects and produces 1264 for its own internal use. 1266 22. A dispute resolution process for addressing process concerns was 1267 added. 1269 23. The process for recalling a sitting member of the IAB and IESG 1270 requires at least 20 eligible members of the IETF community to 1271 sign a petition requesting the recall. 1273 24. The section on Security Considerations was expanded. 1275 25. Appendix A, Oral Tradition, has been added. 1277 26. Appendix B, Nominating Committee Timeline, has been added as a 1278 convenience to the reader. 1280 9. Acknowledgements 1282 There have been a number of people involved with the development of 1283 this document over the years as it has progressed from RFC2027 1284 through RFC2282 and RFC2727 to its current version. 1286 A great deal of credit goes to the first three Nominating Committee 1287 Chairs: 1289 1993 - Jeff Case 1291 1994 - Fred Baker 1293 1995 - John Curran 1295 who had the pleasure of operating without the benefit of a documented 1296 process. It was their fine work and oral tradition that became the 1297 first version of this document. 1299 Of course we can not overlook the bug discovery burden that each of 1300 the Chairs since the first publication have had to endure: 1302 1996 - Guy Almes 1304 1997 - Geoff Huston 1306 1998 - Mike St. Johns 1308 1999 - Donald Eastlake 1310 2000 - Avri Doria 1312 2001 - Bernard Adoba 1314 2002 - Ted T'so 1316 2003 - Phil Roberts 1318 The bulk of the early credit goes to the members of the POISSON 1319 Working Group, previously the POISED Working Group. The prose here 1320 would not be what it is were it not for the attentive and insightful 1321 review of its members. Specific acknowledgement must be extended to 1322 Scott Bradner and John Klensin, who consistently contributed to the 1323 improvement of the first three versions of this document. 1325 In January 2002 a new working group was formed, the Nominating 1326 Committee Working Group (nomcom), to revise the RFC2727 version. 1327 This working group was guided by the efforts of a design team whose 1328 members were as follows: 1330 Bernard Adoba 1332 Harald Alvestrand - Chair of the IETF 1334 Leslie Daigle - Chair of the IAB 1336 Avri Doria - Chair of the Working Group 1338 James Galvin - Editor of the Document 1340 Joel Halpern 1342 Thomas Narten 1344 10. Security Considerations 1346 Any selection, confirmation, or recall process necessarily involves 1347 investigation into the qualifications and activities of prospective 1348 candidates. The investigation may reveal confidential or otherwise 1349 private information about candidates to those participating in the 1350 process. Each person who participates in any aspect of the process 1351 must maintain the confidentiality of any and all information not 1352 explicitly identified as suitable for public dissemination. 1354 When the nominating committee decides it is necessary to share 1355 confidential or otherwise private information with others, the 1356 dissemination must be minimal and must include a prior commitment 1357 from all persons consulted to observe the same confidentiality rules 1358 as the nominating committee itself. 1360 Informative References 1362 [1] Eastlake, D., "Publicly Verifiable Nomcom Random Selection", RFC 1363 2777, February 2000. 1365 [2] Galvin, J., "IAB and IESG Selection, Confirmation, and Recall 1366 Process: Operation of the Nominating and Recall Committees", BCP 1367 10, RFC 2727, February 2000. 1369 [3] Galvin, J., "IAB and IESG Selection, Confirmation, and Recall 1370 Process: Operation of the Nominating and Recall Committees", BCP 1371 10, RFC 2282, February 1998. 1373 Author's Address 1375 James M. Galvin (editor) 1376 eList eXpress LLC 1377 607 Trixsam Road 1378 Sykesville, MD 21784 1379 US 1381 Phone: +1 410-549-4619 1382 Fax: +1 410-795-7978 1383 EMail: galvin+ietf@elistx.com 1384 URI: http://www.elistx.com/ 1386 Appendix A. Oral Tradition 1388 Over the years various nominating committees have learned through 1389 oral tradition passed on by liaisons that there are certain 1390 consistencies in the process and information considered during 1391 deliberations. Some items from that oral tradition are collected 1392 here to facilitate its consideration by future nominating committees. 1394 1. It has been found that experience as an IETF Working Group Chair 1395 or an IRTF Research Group Chair is helpful in giving a nominee 1396 experience of what the job of an Area Director involves. It is 1397 also helps a nominating committee judge the technical, people, 1398 and process management skills of the nominee. 1400 2. No person should serve on both the IESG and the IAB concurrently, 1401 except the IETF Chair who serves on both bodies by definition. 1403 3. The strength of the IAB is found in part in the balance of the 1404 demographics of its members (e.g., national distribution, years 1405 of experience, gender, etc.), the combined skill set of its 1406 members, and the combined sectors (e.g., industry, academia, 1407 etc.) represented by its members. 1409 4. There are no term limits explicitly because the issue of 1410 continuity versus turnover should be evaluated each year 1411 according to the expectations of the IETF community, as it is 1412 understood by each nominating committee. 1414 5. The number of nominating committee members with the same primary 1415 affiliation is limited in order to avoid the appearance of 1416 improper bias in choosing the leadership of the IETF. Rather 1417 than defining precise rules for how to define "affiliation," the 1418 IETF community depends on the honor and integrity of the 1419 participants to make the process work. 1421 Appendix B. Nominating Committee Timeline 1423 This appendix is included for the convenience of the reader and is 1424 not to be interpreted as the definitive timeline. It is intended to 1425 capture the detail described elsewhere in this document in one place. 1426 Although every effort has been made to ensure the description here is 1427 consistent with the description elsewhere, if there are any conflicts 1428 the definitive rule is the one in the main body of this document. 1430 The only absolute in the timeline rules for the annual process is 1431 that it must be completed by the First IETF of the year after the 1432 nominating committee begins its term. This is supported by the fact 1433 that the confirmed candidate terms begin during the week of the First 1434 IETF. 1436 The overall annual process is designed to be completed in 7 months. 1437 It is expected to start 8 months prior to the First IETF. The 7 1438 months is split between three major components of the process as 1439 follows. 1441 1. First is the selection and organization of the committee members. 1442 Three months are allotted for this process. 1444 2. Second is the selection of the candidates by the nominating 1445 committee. Three months are allotted for this process. 1447 3. Third is the confirmation of the candidates by their respective 1448 confirming bodies. One month is allotted for this process 1450 The following figure captures the details of the milestones within 1451 each component. For illustrative purposes the figure presumes the 1452 Friday before the First IETF is March 1. 1454 0. BEGIN 8 Months Prior to First IETF (approx. July 1); Internet 1455 Society President appoints the Chair. The appointment must be 1456 done no later than the Second IETF or 8 months prior to the First 1457 IETF, whichever comes first. The Chair must be announced and 1458 recognized during a plenary session of the Second IETF. 1460 1. The Chair establishes and announces milestones to ensure the 1461 timely selection of the nominating committee members. 1463 2. The Chair contacts the IESG, IAB, and Internet Society Board of 1464 Trustees and requests a liaison. The Chair contacts the prior 1465 year's Chair and requests an advisor. The Chair obtains the list 1466 of IESG and IAB open positions and descriptions from the IETF 1467 Executive Director. 1469 3. The Chair announces the solicitation for voting volunteer members 1470 that must remain open for at least 30 days. The announcement must 1471 be done no later than 7 months and 2 weeks prior to the First IETF 1472 (approx. July 15). 1474 4. After the solicitation closes the Chair announces the pool of 1475 volunteers and the date of the random selection, which must be at 1476 least 1 week in the future. The announcement must be done no 1477 later than 6 months and 2 weeks prior to the First IETF 1478 (approx. August 15). 1480 5. On the appointed day the random selection occurs and the Chair 1481 announces the members of the committee and the 1 week challenge 1482 period. The announcement must be done no later than 6 months and 1483 1 week prior to the First IETF (approx. August 22). 1485 6. During the challenge period the Chair contacts each of the 1486 committee members and confirms their availability to participate. 1488 7. After the challenge period closes the Chair announces the members of 1489 the committee and its term begins. The announcement must be done no 1490 later than 6 months prior to the First IETF (approx. September 1). 1492 8. The committee has one month during which it is to self-organize in 1493 preparation for completing its assigned duties. This must be done no 1494 later than 5 months prior to the First IETF (approx. October 1). 1496 9. END the Committee Member Selection Process; BEGIN the Selection of 1497 Candidates; Time is at least 5 months prior to the First IETF 1498 (approx. October 1). 1500 10. The Chair establishes and announces the milestones to ensure the 1501 timely selection of the candidates, including a call for 1502 nominations for the open positions. The announcement must be done 1503 no later than 5 months prior to the First IETF (approx. October 1504 1). 1506 11. Over the next 3 months the nominating committee collects input 1507 and deliberates. It should plan to conduct interviews and other 1508 consultations during the Third IETF. The committee must complete 1509 its candidate selection no later than 2 months prior to the First 1510 IETF (approx. January 1). 1512 12. END the Selection of Candidates; BEGIN the Confirmation of 1513 Candidates; Time is at least 2 months prior to the First IETF 1514 (approx. January 1); 1516 13. The committee presents its candidates to their respective confirming 1517 bodies. The presentation must be done no later than 2 months prior 1518 to the First IETF (approx. January 1). 1520 14. The confirming bodies have 1 month to deliberate and, in 1521 communication with the nominating committee, accept or reject 1522 candidates. 1524 15. The Chair announces the confirmed candidates. The announcement 1525 must be done no later than 1 month prior to the First IETF 1526 (approx. February 1). 1528 Figure 1: The Timeline 1530 Intellectual Property Statement 1532 The IETF takes no position regarding the validity or scope of any 1533 intellectual property or other rights that might be claimed to 1534 pertain to the implementation or use of the technology described in 1535 this document or the extent to which any license under such rights 1536 might or might not be available; neither does it represent that it 1537 has made any effort to identify any such rights. Information on the 1538 IETF's procedures with respect to rights in standards-track and 1539 standards-related documentation can be found in BCP-11. Copies of 1540 claims of rights made available for publication and any assurances of 1541 licenses to be made available, or the result of an attempt made to 1542 obtain a general license or permission for the use of such 1543 proprietary rights by implementors or users of this specification can 1544 be obtained from the IETF Secretariat. 1546 The IETF invites any interested party to bring to its attention any 1547 copyrights, patents or patent applications, or other proprietary 1548 rights which may cover technology that may be required to practice 1549 this standard. Please address the information to the IETF Executive 1550 Director. 1552 Full Copyright Statement 1554 Copyright (C) The Internet Society (2003). All Rights Reserved. 1556 This document and translations of it may be copied and furnished to 1557 others, and derivative works that comment on or otherwise explain it 1558 or assist in its implementation may be prepared, copied, published 1559 and distributed, in whole or in part, without restriction of any 1560 kind, provided that the above copyright notice and this paragraph are 1561 included on all such copies and derivative works. However, this 1562 document itself may not be modified in any way, such as by removing 1563 the copyright notice or references to the Internet Society or other 1564 Internet organizations, except as needed for the purpose of 1565 developing Internet standards in which case the procedures for 1566 copyrights defined in the Internet Standards process must be 1567 followed, or as required to translate it into languages other than 1568 English. 1570 The limited permissions granted above are perpetual and will not be 1571 revoked by the Internet Society or its successors or assignees. 1573 This document and the information contained herein is provided on an 1574 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1575 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1576 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1577 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1578 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1580 Acknowledgment 1582 Funding for the RFC Editor function is currently provided by the 1583 Internet Society.