idnits 2.17.1 draft-ietf-nomcom-rfc2727bis-03.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 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 3 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 (February 21, 2003) is 7734 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 1326, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2777 (ref. '1') (Obsoleted by RFC 3797) ** Obsolete normative reference: RFC 2727 (ref. '2') (Obsoleted by RFC 3777) ** Obsolete normative reference: RFC 2282 (ref. '3') (Obsoleted by RFC 2727) Summary: 7 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Galvin 3 Internet-Draft eList eXpress LLC 4 Expires: August 22, 2003 February 21, 2003 6 IAB and IESG Selection, Confirmation, and Recall Process: Operation 7 of the Nominating and Recall Committees 8 draft-ietf-nomcom-rfc2727bis-03.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 August 22, 2003. 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 . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 3. General . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 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 8.1 Changes Between Draft-02 and Draft-03 . . . . . . . . . . . . 29 70 8.2 Changes Between Draft-01 and Draft-02 . . . . . . . . . . . . 29 71 8.3 Changes Between RFC2727 and Draft-01 . . . . . . . . . . . . . 30 72 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 32 73 10. Security Considerations . . . . . . . . . . . . . . . . . . . 33 74 References . . . . . . . . . . . . . . . . . . . . . . . . . . 34 75 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 34 76 A. Oral Tradition . . . . . . . . . . . . . . . . . . . . . . . . 35 77 B. Nominating Committee Timeline . . . . . . . . . . . . . . . . 36 78 Intellectual Property and Copyright Statements . . . . . . . . 39 80 1. Introduction 82 This document is a revision of and supercedes RFC2727. [2] It is a 83 complete specification of the process by which members of the IAB and 84 IESG are selected, confirmed, and recalled as of the date of its 85 approval. However, these procedures are subject to change and such 86 change takes effect immediately upon its approval, regardless of 87 whether this document has yet been revised. 89 The following two assumptions continue to be true of this 90 specification. 92 1. The Internet Research Task Force (IRTF) and Internet Research 93 Steering Group (IRSG) are not a part of the process described 94 here. 96 2. The organization (and re-organization) of the IESG is not a part 97 of the process described here. 99 The time frames specified here use IETF meetings as a frame of 100 reference. The time frames assume that the IETF meets three times 101 per calendar year with approximately equal amounts of time between 102 them. The meetings are referred to as the First IETF, Second IETF, or 103 Third IETF as needed. 105 The next section lists the words and phrases commonly used throughout 106 this document with their intended meaning. 108 The majority of this document is divided into four major topics as 109 follows. 111 General: This a set of rules and constraints that apply to the 112 selection and confirmation process as a whole. 114 Nominating Committee Selection: This is the process by which the 115 volunteers who will serve on the committee are recognized. 117 Nominating Committee Operation: This is the set of principles, rules, 118 and constraints that guide the activities of the nominating 119 committee, including the confirmation process. 121 Member Recall: This is the process by which the behavior of a sitting 122 member of the IESG or IAB may be questioned, perhaps resulting in 123 the removal of the sitting member. 125 A final section describes how this document differs from its 126 predecessor: RFC2727. [2] 127 An appendix of useful facts and practices collected from previous 128 nominating committees is also included. 130 2. Definitions 132 The following words and phrases are commonly used throughout this 133 document. They are listed here with their intended meaning for the 134 convenience of the reader. 136 candidate: A nominee who has been selected to be considered for 137 confirmation by a confirming body. 139 confirmed candidate: A candidate that has been reviewed and approved 140 by a confirming body. 142 nominating committee term: The term begins when its members are 143 officially announced, which is expected to be prior to the Third 144 IETF to ensure it is fully operational at the Third IETF. The 145 term ends at the Third IETF (not three meetings) after the next 146 nominating committee's term begins. 148 nominee: A person who is being or has been considered for one or more 149 open positions of the IESG or IAB. 151 sitting member: A person who is currently serving a term of 152 membership in the IESG, IAB or ISOC Board of Trustees. 154 3. General 156 The following set of rules apply to the process as a whole. If 157 necessary, a paragraph discussing the interpretation of each rule is 158 included. 160 1. The annual process is expected to be completed within 7 months. 162 The annual process is expected to be completed one month prior to 163 the friday of the week before the First IETF. It is expected to 164 begin at least 8 months prior to the Friday of the week before 165 the First IETF. 167 The process officially begins with the announcement of the Chair 168 of the committee. The process officially ends when all confirmed 169 candidates have been announced. 171 The annual process is comprised of three major components as 172 follows. 174 1. The selection and organization of the nominating committee 175 members. 177 2. The selection of candidates by the nominating committee. 179 3. The confirmation of the candidates. 181 There is an additional month set aside between when the annual 182 process is expected to end and the term of the new candidates is 183 to begin. This time may be used during unusual circumstances to 184 extend the time allocated for any of the components listed above. 186 2. The principal functions of the nominating committee are to review 187 the open IESG and IAB positions and to either nominate its 188 incumbent or a superior candidate. 190 Although there is no term limit for serving in any IESG or IAB 191 position, the nominating committee may use length of service as 192 one of its criterion for evaluating an incumbent. 194 The nominating committee does not select the open positions to be 195 reviewed; it is instructed as to which positions to review. 197 The nominating committee will be given the title of the position 198 to be reviewed and a brief description of the desirable set of 199 qualifications of the candidate that is nominated to fill each 200 position. 202 Incumbents must notify the nominating committee if they wish to 203 be nominated. 205 The nominating committee does not confirm its candidates; it 206 presents its candidates to the appropriate confirming body as 207 indicated below. 209 A superior candidate is one for whom the nominating committee 210 believes would contribute in such a way as to improve or 211 otherwise be more desirable to the body to which it was 212 nominated. 214 3. One-half of each of the then current IESG and IAB positions is 215 selected to be reviewed each year. 217 The intent of this rule to ensure the review of approximately 218 one-half of each of the IESG and IAB sitting members each year. 219 It is recognized that circumstances may exist that will require 220 the nominating committee to review more or less than one-half of 221 the current positions, e.g., if the IESG or IAB have re-organized 222 prior to this process and created new positions, or if there are 223 an odd number of current positions. 225 4. Confirmed candidates are expected to serve at least a 2 year 226 term. 228 The intent of this rule is to ensure that members of the IESG and 229 IAB serve the number of years that best facilitates the review of 230 one-half of the members each year. 232 It is consistent with this rule for the nominating committee to 233 choose one or more of the currently open positions to which it 234 may assign a term greater than 2 years in order to ensure the 235 ideal application of this rule in the future. 237 It is consistent with this rule for the nominating committee to 238 choose one or more of the currently open positions that share 239 responsibilities with other positions (both those being reviewed 240 and those sitting) to which it may assign a term greater than 2 241 years to ensure that all such members will not be reviewed at the 242 same time. 244 All sitting member terms end during the First IETF meeting 245 corresponding to the end of the term for which they were 246 confirmed. All confirmed candidate terms begin during the First 247 IETF meeting corresponding to the beginning of the term for which 248 they were confirmed. Normally, the confirmed candidate's term 249 begins when the currently sitting member's term ends on the last 250 day of the meeting. A term may begin or end no sooner than the 251 first day of the meeting and no later than the last day of the 252 meeting as determined by the mutual agreement of the currently 253 sitting member and the confirmed candidate. The confirmed 254 candidate's term may overlap the sitting member's term during the 255 meeting as determined by their mutual agreement. 257 5. Mid-term vacancies are filled by the same rules as documented 258 here with four qualifications. 260 First, when there is only one official nominating committee the 261 body with the mid-term vacancy must relegate the responsibility 262 to fill the vacancy to it. If the mid-term vacancy occurs during 263 the period of time that the term of the prior year's nominating 264 committee overlaps with the term of the current year's nominating 265 committee, the body with the mid-term vacancy must relegate the 266 responsibility to fill the vacancy to the prior year's nominating 267 committee. 269 Second, if it is the case that the nominating committee is 270 reconvening to fill the mid-term vacancy, then the candidate 271 selection and confirmation process is expected to be completed 272 within 6 weeks, with all other time periods otherwise unspecified 273 prorated accordingly. 275 Third, the confirming body has two weeks from the day it is 276 notified of a candidate to reject the candidate, otherwise the 277 candidate is assumed to have been confirmed. 279 Fourth, the term of the confirmed candidate will be either: 281 1. the remainder of the term of the open position if that 282 remainder is not less than one year. 284 2. the remainder of the term of the open position plus the next 285 2 year term if that remainder is less than one year. 287 6. All deliberations and supporting information that relates to 288 specific nominees, candidates, and confirmed candidates are 289 confidential. 291 The nominating committee and confirming body members will be 292 exposed to confidential information as a result of their 293 deliberations, their interactions with those they consult, and 294 from those who provide requested supporting information. All 295 members and all other participants are expected to handle this 296 information in a manner consistent with its sensitivity. 298 It is consistent with this rule for current nominating committee 299 members who have served on prior nominating committees to advise 300 the current committee on deliberations and results of the prior 301 committee, as necessary and appropriate. 303 7. Unless otherwise specified, the advice and consent model is used 304 throughout the process. This model is characterized as follows. 306 1. The IETF Executive Director informs the nominating committee 307 of the IESG and IAB positions to be reviewed. 309 The IESG and IAB are responsible for providing a list of the 310 qualifications desired of the candidates selected for their 311 respective open positions to the Executive Director. The 312 lists are to be provided to the nominating comittee for its 313 consideration. 315 2. The nominating committee selects candidates and advises each 316 confirming body of its respective slate of candidates. 318 3. The confirming bodies review their respective slate of 319 candidates and, in consultation with the nominating 320 committee, consent to some, all, or none of the candidates. 322 The sitting IAB members review the IESG candidates. 324 The Internet Society Board of Trustees reviews the IAB 325 candidates. 327 If the entire slate of candidates submitted to a confirming 328 body is confirmed, the job of the nominating committee with 329 respect to those open positions is complete. 331 If some or none of the candidates submitted to a confirming 332 body are confirmed, the confirming body continues to consult 333 with the nominating committee both to explain the reason why 334 all the candidates were not confirmed and to understand the 335 nominating committee's rationale for the slate. During the 336 course of the consultation the nominating committee may 337 re-examine the slate of candidates and may change it in any 338 way. 340 The confirming body may reject individual candidates, in 341 which case the nominating committee must select alternate 342 candidates for the rejected candidates. 344 Any additional time required by the nominating committee 345 should not exceed its maximum time allotment. 347 4. The confirming bodies decide their consent according to a 348 mechanism of their own choosing, which must ensure that at 349 least one-half of the sitting members agree with the 350 decision. 352 At least one-half of the sitting members of the confirming 353 bodies must agree to either confirm or reject each individual 354 nominee. The agreement must be decided within a reasonable 355 timeframe. The agreement may be decided by conducting a 356 formal vote, by asserting consensus based on informal 357 exchanges (email), or by whatever mechanism is used to 358 conduct the normal business of the confirming body. 360 8. All announcements must be made using at least the mechanism used 361 by the IETF secretariat for its announcements, including a notice 362 on the IETF web site. 364 As of the publication of this document the current mechanism is 365 an email message to both the "ietf" and the "ietf-announce" 366 mailing lists. 368 4. Nominating Committee Selection 370 The following set of rules apply to the creation of the nominating 371 committee and the selection of its members. 373 1. The process of selecting and organizing the members of the 374 nominating committee is expected to be completed within 3 375 months. 377 The selection and organization process must be completed at 378 least one month prior to the Third IETF. This ensures the 379 nominating committee is fully operational and available for 380 interviews and consultation during the Third IETF. 382 2. The term of a nominating committee is expected to be 15 months. 384 It is the intent of this rule that the end of a nominating 385 committee's term overlap by approximately three months the 386 beginning of the term of the next nominating committee. 388 The term of a nominating committee begins when its members are 389 officially announced. The term ends at the Third IETF (not 390 three meetings) after the next nominating committee's term 391 begins. 393 A term is expected to begin at least two months prior to the 394 Third IETF to ensure the nominating committee has at least one 395 month to get organized before preparing for the Third IETF. 397 A nominating committee is expected to complete any 398 work-in-progress before it is dissolved at the end of its term. 400 During the period of time that the terms of the nominating 401 committees overlap, all mid-term vacancies are to be relegated 402 to the prior year's nominating committee. The prior year's 403 nominating committee has no other responsibilities during the 404 overlap period. At all times other than the overlap period 405 there is exactly one official nominating committee and it is 406 responsible for all mid-term vacancies. 408 When the prior year's nominating committee is filling a mid-term 409 vacancy during the period of time that the terms overlap, the 410 nominating committees operate independently. However, some 411 coordination is needed between them. Since the prior year's 412 Chair is a non-voting advisor to the current nominating 413 committee the coordination is expected to be straightforward. 415 3. The nominating committee comprises at least a Chair, 10 voting 416 volunteers, 2 liaisons, and an advisor. 418 Any committee member may propose the addition of an advisor to 419 participate in some or all of the deliberations of the 420 committee. The addition must be approved by all members of the 421 committee according to its established voting mechanism. 422 Advisors participate as individuals. 424 Any committee member may propose the addition of a liaison from 425 other unrepresented organizations to participate in some or all 426 of the deliberations of the committee. The addition must be 427 approved by all members of the committee according to its 428 established voting mechanism. Liaisons participate as 429 representatives of their respective organizations. 431 The Chair is selected according to rules stated elsewhere in 432 this document. 434 The 10 voting volunteers are selected according to rules stated 435 elsewhere in this document. 437 The IESG and IAB liaisons are selected according to rules stated 438 elsewhere in this document. 440 The Chair of last year's nominating committee serves as an 441 advisor according to rules stated elsewhere in this document. 443 None of the Chair, liaisons, or advisors vote on the selection 444 of candidates. They do vote on all other issues before the 445 committee unless otherwise specified. 447 4. The Chair of the nominating committee is responsible for 448 ensuring the nominating committee completes its assigned duties 449 in a timely fashion and performs in the best interests of the 450 IETF community. 452 The Chair must be thoroughly familiar with the rules and 453 guidance indicated throughout this document. The Chair must 454 ensure the nominating committee completes its assigned duties in 455 a manner that is consistent with this document. 457 The Chair must attest by proclamation at a plenary session of 458 the First IETF that the results of the committee represent its 459 best effort and the best interests of the IETF community. 461 The Chair does not vote on the selection of candidates. 463 5. The Internet Society President appoints the Chair, who must meet 464 the same requirements for membership in the nominating committee 465 as a voting volunteer. 467 The nominating committee Chair must agree to invest the time 468 necessary to ensure that the nominating committee completes its 469 assigned duties and to perform in the best interests of the IETF 470 community in that role. 472 The appointment must be completed no later than the Second IETF 473 meeting to ensure it can be announced during a plenary session 474 at that meeting. The appointment must be completed as soon as 475 necessary to ensure the annual process can complete at the time 476 specified elsewhere in this document. 478 6. A Chair, in consultation with the Internet Society President, 479 may appoint a temporary substitute. 481 There are a variety of ordinary circumstances that may arise 482 from time to time that could result in a Chair being unavailable 483 to oversee the activities of the committee. The Chair, in 484 consultation with the Internet Society President, may appoint a 485 substitute from a pool comprised of the liaisons currently 486 serving on the committee and the prior year's Chair or designee. 488 Any such appointment must be temporary and does not absolve the 489 Chair of any or all responsibility for ensuring the nominating 490 committee completes its assigned duties in a timely fashion. 492 7. Liaisons are responsible for ensuring the nominating committee 493 in general and the Chair in particular execute their assigned 494 duties in the best interest of the IETF community. 496 Liaisons are expected to represent the views of their respective 497 organizations during the deliberations of the committee. They 498 should provide information as requested or when they believe it 499 would be helpful to the committee. 501 Liaisons from the IESG and IAB are expected to provide 502 information to the nominating committee regarding the operation, 503 responsibility, and composition of their respective bodies. 505 Liaisons are expected to convey questions from the committee to 506 their respective organizations and responses to those questions 507 to the committee, as requested by the committee. 509 Liaisons from the IESG, IAB, and Internet Society Board of 510 Trustees are expected to review the operation and executing 511 process of the nominating committee and to report any concerns 512 or issues to the Chair of the nominating committee immediately. 513 If they can not resolve the issue between themselves liaisons 514 must report the issue to their respective bodies. If their 515 respective body agrees that there is an issue the liaison must 516 report it according to the dispute resolution process stated 517 elsewhere in this document. 519 Liaisons from confirming bodies are expected to assist the 520 committee in preparing the testimony it is required to provide 521 with its slate of candidates. 523 Liaisons may have other nominating committee responsibilities as 524 required by their respective organizations or requested by the 525 nominating committee, except that such responsibilities may not 526 conflict with any other provisions of this document. 528 Liaisons do not vote on the selection of candidates. 530 8. The sitting IAB and IESG members each appoint a liaison to the 531 nominating committee from their current membership who is not 532 sitting in an open position. 534 9. The Internet Society Board of Trustees may appoint a liaison to 535 the nominating committee. 537 10. An advisor is responsible for such duties as specified by the 538 invitation that resulted in the appointment. 540 Advisors do not vote on the selection of candidates. 542 11. The Chair of the prior year's nominating committee serves as an 543 advisor to the current committee. 545 The prior year's Chair is expected to review the actions and 546 activities of the current Chair and to report any concerns or 547 issues to the nominating committee Chair immediately. If they 548 can not resolve the issue between them the prior year's Chair 549 must report it according to the dispute resolution process 550 stated elsewhere in this document. 552 The prior year's Chair may select a designee from a pool 553 composed of the voting volunteers of the prior year's committee 554 and all prior Chairs if the Chair is unavailable. If the prior 555 year's Chair is unavailable or is unable or unwilling to make 556 such a designation in a timely fashion, the Chair of the current 557 year's committee may select a designee in consultation with the 558 Internet Society President. 560 Selecting a prior year's committee member as the designee 561 permits the experience of the prior year's deliberations to be 562 readily available to the current committee. Selecting an 563 earlier prior year Chair as the designee permits the experience 564 of being a Chair as well as that Chair's committee deliberations 565 to be readily available to the current committee. 567 12. Voting volunteers are responsible for completing the tasks of 568 the nominating committee in a timely fashion. 570 Each voting volunteer is expected to participate in all 571 activities of the nominating committee with a level of effort 572 approximately equal to all other voting volunteers. Specific 573 tasks to be completed are established and managed by the Chair 574 according to rules stated elsewhere in this document. 576 13. The Chair must establish and announce milestones for the 577 selection of the nominating committee members. 579 There is a defined time period during which the selection 580 process must be completed. The Chair must establish a set of 581 milestones which, if met in a timely fashion, will result in the 582 completion of the process on time. 584 14. The Chair obtains the list of IESG and IAB positions to be 585 reviewed and announces it along with a solicitation for names of 586 volunteers from the IETF community willing to serve on the 587 nominating committee. 589 The solicitation must permit the community at least 30 days 590 during which they may choose to volunteer to be selected for the 591 nominating committee. 593 The list of open positions is published with the solicitation to 594 facilitate community members choosing between volunteering for 595 an open position and volunteering for the nominating committee. 597 15. Members of the IETF community must have attended at least 3 of 598 the last 5 IETF meetings in order to volunteer. 600 The 5 meetings are the five most recent meetings that ended 601 prior to the date on which the solicitation for nominating 602 committee volunteers was submitted for distribution to the IETF 603 community. 605 The IETF Secretariat is responsible for confirming that 606 volunteers have met the attendance requirement. 608 Volunteers must provide their full name, email address, and 609 primary company or organization affiliation (if any) when 610 volunteering. 612 Volunteers are expected to be familiar with the IETF processes 613 and procedures, which are readily learned by active 614 participation in a working group and especially by serving as a 615 document editor or working group chair. 617 16. Members of the Internet Society Board of Trustees, sitting 618 members of the IAB, and sitting members of the IESG may not 619 volunteer. 621 17. The Chair announces both the list of the pool of volunteers from 622 which the 10 voting volunteers will be randomly selected and the 623 method with which the selection will be completed. 625 The announcement should be made at least 1 week prior to the 626 date on which the random selection will occur. 628 The pool of volunteers must be enumerated or otherwise indicated 629 according to the needs of the method to be used. 631 The announcement must specify the data that will be used as 632 input to the method. The method must depend on random data 633 whose value is not known or available until the date on which 634 the random selection will occur. 636 It must be possible to independently verify that the method used 637 is both fair and unbiased. A method is fair if each eligible 638 volunteer is equally likely to be selected. A method is 639 unbiased if no one can influence its outcome in favor of a 640 specific outcome. 642 It must be possible to repeat the method, either through 643 iteration or by restarting in such a way as to remain fair and 644 unbiased. This is necessary to replace selected volunteers 645 should they become unavailable after selection. 647 The method must produce an ordered list of volunteers. 649 One possible method is described in RFC2777 [1]. 651 18. The Chair randomly selects the 10 voting volunteers from the 652 pool of names of volunteers and announces the members of the 653 nominating committee. 655 No more than two volunteers with the same primary affiliation 656 may be selected for the nominating committee. The Chair reviews 657 the primary affiliation of each volunteer selected by the method 658 in turn. If the primary affiliation for a volunteer is the same 659 as two previously selected volunteers, that volunteer is removed 660 from consideration and the method is repeated to identify the 661 next eligible volunteer. 663 There must be at least two announcements of all members of the 664 nominating committee. 666 The first announcement should occur as soon after the random 667 selection as is reasonable for the Chair. The community must 668 have at least 1 week during which any member may challenge the 669 results of the random selection. 671 The challenge must be made in writing (email is acceptable) to 672 the Chair. The Chair has 48 hours to review the challenge and 673 offer a resolution to the member. If the resolution is not 674 accepted by the member, that member may report the challenge 675 according to the dispute resolution process stated elsewhere in 676 this document. 678 If a selected volunteer, upon reading the announcement with the 679 list of selected volunteers, finds that two or more other 680 volunteers have the same affiliation, then the volunteer should 681 notify the Chair who will determine the appropriate action. 683 During at least the 1 week challenge period the Chair must 684 contact each of the members and confirm their willingness and 685 availability to serve. The Chair should make every reasonable 686 effort to contact each member. 688 * If the Chair is unable to contact a liaison the problem is 689 referred to the respective organization to resolve. The 690 Chair should allow a reasonable amount of time for the 691 organization to resolve and then may proceed without the 692 liaison. 694 * If the Chair is unable to contact an advisor the Chair may 695 elect to proceed without the advisor, except for the prior 696 year's Chair for whom the Chair must consult with the 697 Internet Society President as stated elsewhere in this 698 document. 700 * If the Chair is unable to contact a voting volunteer the 701 Chair must iterate the random selection process in order to 702 replace the unavailable volunteer. There should be at least 703 1 day between the announcement of the iteration and the 704 selection process. 706 After at least 1 week and confirming that 10 voting volunteers 707 are ready to serve, the Chair makes the second announcement of 708 the members of the nominating committee, which officially begins 709 the term of the nominating committee. 711 19. The Chair works with the members of the committee to organize 712 itself in preparation for completing its assigned duties. 714 The committee has approximately one month during which it can 715 self-organize. Its responsibilities during this time include 716 but are not limited to the following. 718 * Setting up a regular teleconference schedule. 720 * Setting up an internal web site. 722 * Setting up a mailing list for internal discussions. 724 * Setting up an email address for receiving community input. 726 * Establishing operational procedures. 728 * Establishing milestones in order to monitor the progress of 729 the selection process. 731 5. Nominating Committee Operation 733 The following rules apply to the operation of the nominating 734 committee. If necessary, a paragraph discussing the interpretation 735 of each rule is included. 737 The rules are organized approximately in the order in which they 738 would be invoked. 740 1. All rules and special circumstances not otherwise specified are 741 at the discretion of the committee. 743 Exceptional circumstances will occasionally arise during the 744 normal operation of the nominating committee. This rule is 745 intended to foster the continued forward progress of the 746 committee. 748 Any member of the committee may propose a rule for adoption by 749 the committee. The rule must be approved by all members of the 750 committee according to its established voting mechanism. 752 All members of the committee should consider whether the 753 exception is worthy of mention in the next revision of this 754 document and followup accordingly. 756 2. The process of selecting candidates to be confirmed by their 757 respective confirming body is expected to be completed within 3 758 months. 760 The selection process must be completed at least two month's 761 prior to the First IETF. This ensures the nominating committee 762 has sufficient time to complete the confirmation process. 764 3. The process of confirming the candidates is expected to be 765 completed within 1 month. 767 The confirmation process must be completed at least one month 768 prior to the First IETF. 770 4. The Chair must establish for the nominating committee a set of 771 milestones for the candidate selection and confirmation process. 773 There is a defined time period during which the candidate 774 selection and confirmation process must be completed. The Chair 775 must establish a set of milestones which, if met in a timely 776 fashion, will result in the completion of the process on time. 777 The Chair should allow time for iterating the activities of the 778 committee if one or more candidates is not confirmed. 780 The Chair should ensure that all committee members are aware of 781 the milestones. 783 5. The Chair must establish a voting mechanism. 785 The committee must be able to objectively determine when a 786 decision has been made during its deliberations. The criteria 787 for determining closure must be established and known to all 788 members of the nominating committee. 790 6. At least a quorum of committee members must participate in a 791 vote. 793 Only voting volunteers vote on a candidate selection. For a 794 candidate selection vote a quorum is comprised of at least 7 of 795 the voting volunteers. 797 At all other times a quorum is present if at least 75% of the 798 nominating committee members are participating. 800 7. Any member of the nominating committee may propose to the 801 committee that any other member except the Chair be recalled. 802 The process for recalling the Chair is defined elsewhere in this 803 document. 805 There are a variety of ordinary circumstances that may arise 806 that could result in one or more members of the committee being 807 unavailable to complete their assigned duties, for example 808 health concerns, family issues, or a change of priorities at 809 work. A committee member may choose to resign for unspecified 810 personal reasons. In addition, the committee may not function 811 well as a group because a member may be disruptive or otherwise 812 uncooperative. 814 Regardless of the circumstances, if individual committee members 815 can not work out their differences between themselves, the 816 entire committee may be called upon to discuss and review the 817 circumstances. If a resolution is not forthcoming a vote may be 818 conducted. A member may recalled if at least a quorum of all 819 committee members agree, including the vote of the member being 820 recalled. 822 If a liaison member is recalled the committee must notify the 823 affected organization and must allow a reasonable amount of time 824 for a replacement to be identified by the organization before 825 proceeding. 827 If an advisor member other than the prior year's Chair is 828 recalled, the committee may choose to proceed without the 829 advisor. In the case of the prior year's Chair, the Internet 830 Society President must be notified and the current Chair must be 831 allowed a reasonable amount of time to consult with the Internet 832 Society President to identify a replacement before proceeding. 834 If a voting volunteer member is recalled the committee may 835 choose to proceed with only 9 voting volunteers at its own 836 discretion. In all other cases the Chair must iterate the 837 random selection process including an announcement of the 838 iteration prior to the actual selection as stated elsewhere in 839 this document. 841 A change in the primary affiliation of a voting volunteer during 842 the term of the nominating committee is not a cause to request 843 the recall of that volunteer, even if the change would result in 844 more than two voting volunteers with the same affiliation. 846 8. Only the prior year's Chair may request the recall of the 847 current Chair. 849 It is the responsibility of the prior year's Chair to ensure the 850 current Chair completes the assigned tasks in a manner 851 consistent with this document and in the best interests of the 852 IETF community. 854 Any member of the committee who has an issue or concern 855 regarding the Chair should report it to the prior year's Chair 856 immediately. The prior year's Chair is expected to report it to 857 the Chair immediately. If they can not resolve the issue 858 between them the prior year's Chair must report it according to 859 the dispute resolution process stated elsewhere in this 860 document. 862 9. All members of the nominating committee may participate in all 863 deliberations. 865 The emphasis of this rule is that no member can be explicitly 866 excluded from any deliberation. However, a member may 867 individually choose not to participate in a deliberation. 869 10. The Chair announces the open positions to be reviewed and the 870 call for nominees. 872 The call for nominees must include a request for comments 873 regarding the past performance of incumbents, which will be 874 considered during the deliberations of the nominating committee. 876 The call must request that a nomination include a valid, working 877 email address, a telephone number, or both for the nominee. The 878 nomination must include the set of skills or expertise the 879 nominator believes the nominee has that would be desirable. 881 11. Any member of the IETF community may nominate any member of the 882 IETF community for any open position, whose eligibility to serve 883 will be confirmed by the nominating committee. 885 A self-nomination is permitted. 887 Nominating committee members are not eligible to be considered 888 for filling any open position. They become ineligible as soon 889 as the term of the nominating committee on which they serve 890 officially begins. They remain ineligible for the duration of 891 that nominating committee's term. 893 Members of the IETF community who were recalled from any IESG or 894 IAB position during the previous two years are not eligible to 895 be considered for filling any open position. 897 12. The nominating committee selects candidates based on its 898 understanding of the IETF community's consensus of the 899 qualifications required to fill the open positions. 901 The intent of this rule is to ensure that the nominating 902 committee consults with a broad base of the IETF community for 903 input to its deliberations. In particular, the nominating 904 committee must determine if the desired qualifications for the 905 open positions matches its understanding of the qualifications 906 desired by the IETF community. 908 The consultations are permitted to include names of nominees, if 909 all parties to the consultation agree to observe the same 910 confidentiality rules as the nominating committee itself. 912 A broad base of the community should include the existing 913 members of the IAB and IESG, especially sitting members who 914 share responsibilities with open positions, e.g., co-Area 915 Directors. 917 Only voting volunteer members vote to select candidates. 919 13. Nominees should be advised that they are being considered and 920 must consent to their nomination prior to being chosen as 921 candidates. 923 Although the nominating committee will make every reasonable 924 effort to contact and to remain in contact with nominees, any 925 nominee whose contact information changes during the process and 926 who wishes to still be considered should inform the nominating 927 committee of the changes. 929 A nominee's consent must be written (email is acceptable) and 930 must include a commitment to provide the resources necessary to 931 fill the open position and an assurance that the nominee will 932 perform the duties of the position for which they are being 933 considered in the best interests of the IETF community. 935 Consenting to a nomination must occur prior to a nominee being a 936 candidate and may occur as soon after the nomination as needed 937 by the nominating committee. 939 Consenting to a nomination must not imply the nominee will be a 940 candidate. 942 The nominating committee should help nominees provide 943 justification to their employers. 945 14. The nominating committee advises the confirming bodies of their 946 candidates, specifying a single candidate for each open position 947 and testifying as to how each candidate meets the qualifications 948 of an open position. 950 For each candidate, the testimony must include a brief statement 951 of the qualifications for the position that is being filled, 952 which may be exactly the qualifications that were requested. If 953 the qualifications differ from the desired qualifications 954 originally requested a brief statement explaining the difference 955 must be included. 957 The testimony may include either or both a brief resume of the 958 candidate or a brief summary of the deliberations of the 959 nominating committee. 961 15. Confirmed candidates must consent to their confirmation and 962 rejected candidates and nominees must be notified before 963 confirmed candidates are announced. 965 It is not necessary to notify and get consent from all confirmed 966 candidates together. Waiting to notify them all together 967 permits the nominating committee to reconsider its selection if 968 necessary. 970 A nominee may not know they were a candidate. This permits a 971 candidate to be rejected by a confirming body without the 972 nominee knowing about the rejection. 974 Rejected nominees who consented to their nomination must be 975 notified prior to announcing the confirmed candidates. Rejected 976 candidates must be notified prior to announcing the confirmed 977 candidates. Waiting to notify them until after the slate of 978 candidates has been confirmed permits the nominating committee 979 to reconsider its selection if necessary. 981 It is not necessary to announce all confirmed candidates 982 together. Waiting to announce them all together permits the 983 nominating committee to reconsider its selection if necessary. 985 The nominating committee must ensure that all confirmed 986 candidates are prepared to serve prior to announcing their 987 confirmation. 989 16. The nominating committee should archive the information it has 990 collected or produced for a period of time not to exceed its 991 term. 993 The purpose of the archive is to assist the nominating committee 994 should it be necessary for it to fill a mid-term vacancy. 996 The existence of an archive, how it is implemented, and what 997 information to archive is at the discretion of the committee. 998 The decision must be approved by a quorum of the voting 999 volunteer members. 1001 The implementation of the archive should make every reasonable 1002 effort to ensure that the confidentiality of the information it 1003 contains is maintained. 1005 6. Dispute Resolution Process 1007 The dispute resolution process described here is to be used as 1008 indicated elsewhere in this document. Its applicability in other 1009 circumstances is beyond the scope of this document. 1011 The nominating committee operates under a strict rule of 1012 confidentiality. For this reason when process issues arise it is 1013 best to make every reasonable effort to resolve them within the 1014 committee. However, when circumstances do not permit this or no 1015 resolution is forthcoming, the process described here is to be used. 1017 The following rules apply to the process. 1019 1. The results of this process are final and binding. There is no 1020 appeal. 1022 2. The process begins with the submission of a request as described 1023 below to the Internet Society President. 1025 3. As soon as the process begins, the nominating committee may 1026 continue those activities that are unrelated to the issue to be 1027 resolved except that it must not submit any slate of candidates 1028 to a confirming body until the issue is resolved. 1030 4. All parties to the process are subject to the same 1031 confidentiality rules as each member of the nominating committee. 1033 5. The process should be completed within two weeks. 1035 The process is as follows. 1037 1. The party seeking resolution submits a written request (email is 1038 acceptable) to the Internet Society President detailing the issue 1039 to be resolved. 1041 2. The Internet Society President appoints an arbiter to investigate 1042 and resolve the issue. A self-appointment is permitted. 1044 3. The arbiter investigates the issue making every reasonable effort 1045 to understand both sides of the issue. Since the arbiter is 1046 subject to the same confidentiality obligations as all nominating 1047 committee members, all members are expect to cooperate fully with 1048 the arbiter and to provide all relevant information to the 1049 arbiter for review. 1051 4. After consultation with the two principal parties to the issue, 1052 the arbiter decides a resolution. Whatever actions are necessary 1053 to execute the resolution are immediately begun and completed as 1054 quickly as possible. 1056 5. The arbiter summarizes the issue, the resolution, and the 1057 rationale for the resolution for the Internet Society President. 1059 6. In consultation with the Internet Society President, the arbiter 1060 prepares a report of the dispute and its resolution. The report 1061 should include all information that in the judgement of the 1062 arbiter does not violate the confidentiality requirements of the 1063 nominating committee. 1065 7. The Chair includes the dispute report when reporting on the 1066 activities of the nominating committee to the IETF community. 1068 7. Member Recall 1070 The following rules apply to the recall process. If necessary, a 1071 paragraph discussing the interpretation of each rule is included. 1073 1. At any time, at least 20 members of the IETF community, who are 1074 qualified to be voting members of a nominating committee, may 1075 request by signed petition (email is acceptable) to the Internet 1076 Society President the recall of any sitting IAB or IESG member. 1078 All individual and collective qualifications of nominating 1079 committee eligibility are applicable, including that no two 1080 signatories may have the same primary affiliation. 1082 Each signature must include a full name, email address, and 1083 primary company or organization affiliation. 1085 The petition must include a statement of justifcation for the 1086 recall and all relevant and appropriate supporting documentation. 1088 The petition and its signatories must be announced to the IETF 1089 community. 1091 2. Internet Society President shall appoint a Recall Committee 1092 Chair. 1094 The Internet Society President must not evaluate the recall 1095 request. It is explicitly the responsibility of the IETF 1096 community to evaluate the behavior of its leaders. 1098 3. The recall committee is created according to the same rules as is 1099 the nominating committee with the qualifications that both the 1100 person being investigated and the parties requesting the recall 1101 must not be a member of the recall committee in any capacity. 1103 4. The recall committee operates according to the same rules as the 1104 nominating committee with the qualification that there is no 1105 confirmation process. 1107 5. The recall committee investigates the circumstances of the 1108 justification for the recall and votes on its findings. 1110 The investigation must include at least both an opportunity for 1111 the member being recalled to present a written statement and 1112 consultation with third parties. 1114 6. A 3/4 majority of the members who vote on the question is 1115 required for a recall. 1117 7. If a sitting member is recalled the open position is to be filled 1118 according to the mid-term vacancy rules. 1120 8. Changes From RFC2727 1122 This section describes the changes from RFC2727 that are currently 1123 incorporated in this draft. The changes represent a proposal to the 1124 working group for it to review and approve, with any additional 1125 changes the consensus of the working group determines are necessary. 1126 Comments, suggestions, or questions should be directed to the mailing 1127 list for this working group. 1129 This proposal does not respond to all of the open issues before this 1130 working group. There are additional issues yet to be resolved that 1131 are not covered in this proposal. 1133 Editorial changes are not described here, only substantive changes. 1134 They are listed here in the order in which they appear in the 1135 document. 1137 8.1 Changes Between Draft-02 and Draft-03 1139 1. The "superior candidate" definition was moved to be with its one 1140 and only use in the document. 1142 2. The eligibility qualifications for the nominating committee was 1143 changed to require attendance at 3 out of 5 of the last five 1144 meetings, to require volunteers to submit identifying contact 1145 information, and to request that volunteers be familiar with IETF 1146 processes and procedures. 1148 3. The method used to select volunteers is now required to produce 1149 an ordered list of volunteers. 1151 4. The process for selecting the 10 voting volunteers had several 1152 clarifications and additional requirements added, including a 1153 challenge process and the requirement to disallow more than two 1154 volunteers with the same primary affiliation. 1156 5. The process for recalling a sitting member of the IAB and IESG 1157 now requires at least 20 eligible members of the IETF commuity to 1158 sign a petition requesting the recall. 1160 8.2 Changes Between Draft-01 and Draft-02 1162 1. The term of the nominating committee was extended to 1163 approximately 15 months such that it explicitly overlaps by 1164 approximately 3 months the next year's nominating committee's 1165 term. 1167 2. The terms voting member and non-voting member were replaced by 1168 voting volunteers, liaisons, and advisors. All members vote at 1169 all times except that the only voting volunteers vote on a 1170 candidate selection. 1172 3. Details regarding the expected timeline of the operation of the 1173 committee were made even more explicit. An Appendix was added 1174 that captures all the details for the convenience of the reader. 1176 4. The responsibilities of the Chair, liaisons, advisors, and voting 1177 volunteers is now explicitly stated. 1179 5. Some additional clarification of the random selection process was 1180 added. 1182 6. A process for recalling members of the committee excluding the 1183 Chair was added 1185 7. A process for recalling the Chair of the committee was added. 1187 8. A dispute resolution process for addressing process concerns was 1188 added. 1190 8.3 Changes Between RFC2727 and Draft-01 1192 1. A section with definitions for words and phrases used throughout 1193 the document was inserted. Suggestions for additional entries 1194 are welcome. 1196 2. A comment about term limits was added to Section 3 Rule 1. 1198 3. In Section 3 Rule 1 the NOMCOM must now be provided with a brief 1199 description of the desirable set of qualifications for the 1200 candidate to be nominated for each position. 1202 4. In Section 3 Rule 5 the body with the mid-term vacancy may now 1203 choose either to reconvene the current NOMCOM to fill it or to 1204 wait for the next NOMCOM to fill it. 1206 5. The characterization of the advice and consent model (Section 3 1207 Rule 7) was revised to require the nominating committee and the 1208 confirming body to consult during the approval process. 1210 6. In Section 3 Rule 8 was added to define that all announcements 1211 are made with the usual IETF secretariat mechanism. 1213 7. Section 4, Nominating Committee Selection, was re-organized so 1214 that explicit timeframes could be specified for the various 1215 steps in the selection process. The following suggestions are 1216 included in the re-organization. 1218 1. The selection process must be completed within 2 months. 1220 2. A term was defined for a nominating committee. 1222 3. Liaisons and advisors are no longer required to meet the 1223 usual requirements for nominating committee membership. 1225 4. The Chair must be appointed by and announced during the 1226 Second IETF. 1228 5. The IETF community can challenge the results of the 1229 selection process that determined the members of the 1230 nominating committee. 1232 6. The Internet Society Board of Trustees may appoint a 1233 non-voting liaison. 1235 8. In Section 5 Rule 7 nominations for open positions should 1236 include both contact information and a description of the skills 1237 or expertise the nominator believes the nominee possesses. 1239 9. In Section 5 Rule 12 nominees are requested to keep the 1240 nominating committee informed of changes in their contact 1241 information. Editorially, the distinction between a nominee and 1242 candidate was emphasized. 1244 10. In Section 5 Rule 13 a description of a testimony to be provided 1245 with a slate to a confirming body by the nominating committee is 1246 specified. 1248 11. Section 5 Rule 14 regarding the announcement of confirmed 1249 candidates was substantially rewritten to make it easier to 1250 understand. 1252 12. In Section 5 Rule 15 was added stating that the nominating 1253 committee is permitted to keep an archive for the duration of 1254 its term of the information it collects and produces for its use 1255 during its term. 1257 13. Section 9, Security Considerations, was expanded. 1259 14. Appendix A, Oral Tradition, has been added. Suggestions for 1260 additional information to include are welcome. 1262 9. Acknowledgements 1264 There have been a number of people involved with the development of 1265 this document over the years. A great deal of credit goes to the 1266 first three Nominating Committee Chairs: 1268 1993 - Jeff Case 1270 1994 - Fred Baker 1272 1995 - John Curran 1274 who had the pleasure of operating without the benefit of a documented 1275 process. It was their fine work and oral tradition that became the 1276 first version of this document. Of course we can not overlook the 1277 bug discovery burden that each of the Chairs since the first 1278 publication have had to endure: 1280 1996 - Guy Almes 1282 1997 - Geoff Houston 1284 1998 - Mike St. Johns 1286 1999 - Donald Eastlake 1288 2000 - Avri Doria 1290 2001 - Bernard Adoba 1292 2002 - Ted T'so 1294 Of course the bulk of the credit goes to the members of the POISSON 1295 Working Group, previously the POISED Working Group. The prose here 1296 would not be what it is were it not for the attentive and insightful 1297 review of its members. Specific acknowledgement must be extended to 1298 Scott Bradner and John Klensin, who have consistently contributed to 1299 the improvement of this document throughout its evolution. 1301 10. Security Considerations 1303 Any selection, confirmation, or recall process necessarily involves 1304 investigation into the qualifications and activities of prospective 1305 candidates. The investigation may reveal confidential or otherwise 1306 private information about candidates to those participating in the 1307 process. Each person who participates in any aspect of the process 1308 must maintain the confidentiality of any and all information not 1309 explicitly identified as suitable for public dissemination. 1311 When the nominating committee decides it is necessary to share 1312 confidential or otherwise private information with others, the 1313 dissemination must be minimal and must include a prior committment 1314 from all persons consulted to observe the same confidentiality rules 1315 as the nominating committee itself. 1317 References 1319 [1] Eastlake, D., "Publicly Verifiable Nomcom Random Selection", RFC 1320 2777, February 2000. 1322 [2] Galvin, J., "IAB and IESG Selection, Confirmation, and Recall 1323 Process: Operation of the Nominating and Recall Committees", BCP 1324 10, RFC 2727, February 2000. 1326 [3] Galvin, J., "IAB and IESG Selection, Confirmation, and Recall 1327 Process: Operation of the Nominating and Recall Committees", BCP 1328 10, RFC 2282, February 1998. 1330 Author's Address 1332 James M. Galvin 1333 eList eXpress LLC 1334 607 Trixsam Road 1335 Sykesville, MD 21784 1336 US 1338 Phone: +1 410-549-4619 1339 Fax: +1 410-795-7978 1340 EMail: galvin+ietf@elistx.com 1341 URI: http://www.elistx.com/ 1343 Appendix A. Oral Tradition 1345 Over the years various nominating committees have learned through 1346 oral tradition passed on by liaisons that there are certain 1347 consistencies in the process and information considered during 1348 deliberations. Some items from that oral tradition are collected 1349 here to facilitate its consideration by future nominating committees. 1351 1. It has been found that experience as an IETF Working Group Chair 1352 or an IRTF Research Group Chair is helpful in giving a nominee 1353 experience of what the job of an Area Director involves. It is 1354 also helps a nominating committee judge the technical, people, 1355 and process management skills of the nominee. 1357 2. No person should ever be nominated to serve on both the IESG and 1358 the IAB concurrently; this does not apply to the IETF Chair who 1359 serves on both bodies by definition. 1361 3. The strength of the IAB is found in part in the balance of the 1362 demographics of its members (e.g., national distribution, years 1363 of experience, gender, etc.), the combined skill set of its 1364 members, and the combined sectors (e.g., industry, academia, 1365 etc.) represented by its members. 1367 4. There are no term limits explicitly because the issue of 1368 continuity versus turnover should be evaluated each year 1369 according to the expectations of the IETF community, as it is 1370 understood by each nominating committee. 1372 5. The number of nominating committee members with the same primary 1373 affiliation is limited in order to avoid the appearance of 1374 improper bias in choosing the leadership of the IETF. Rather 1375 than defining precise rules for how to define "affiliation," the 1376 IETF community depends on the honor and integrity of the 1377 participants to make the process work. 1379 Appendix B. Nominating Committee Timeline 1381 This appendix is included for the convenience of the reader and is 1382 not to be interpreted as the definitive timeline. It is intended to 1383 capture the detail described elsewhere in this document in one place. 1384 Although every effort has been made to ensure the description here is 1385 consistent with the description elsewhere, if there are any conflicts 1386 the definitive rule is the one in the main body of this document. 1388 The only absolute in the timeline rules for the annual process is 1389 that it must be completed by the First IETF of the year after the 1390 nominating committee begins its term. This is supported by the fact 1391 that the confirmed candidate terms begin during the week of the First 1392 IETF. 1394 The overall annual process is designed to be completed in 7 months. 1395 It is expected to start 8 months prior to the First IETF. The 7 1396 months is split between three major components of the process as 1397 follows. 1399 1. First is the selection and organization of the committee members. 1400 Three months are allotted for this process. 1402 2. Second is the selection of the candidates by the nominating 1403 committee. Three months are allotted for this process. 1405 3. Third is the confirmation of the candidates by their respective 1406 confirming bodies. One month is allotted for this process 1408 The following figure captures the details of the milestones within 1409 each component. For illustrative purposes the figure presumes the 1410 Friday before the First IETF is March 1. 1412 0. BEGIN 8 Months Prior to First IETF (approx. July 1); Internet 1413 Society President appoints the Chair. The appointment must be 1414 done no later than the Second IETF or 8 months prior to the First 1415 IETF, whichever comes first. The Chair must be announced and 1416 recognized during a plenary session of the Second IETF. 1418 1. The Chair establishes and announces milestones to ensure the 1419 timely selection of the nominating committee members. 1421 2. The Chair contacts the IESG, IAB, and Internet Society Board of 1422 Trustees and requests a liaison. The Chair contacts the prior 1423 year's Chair and requests an advisor. The Chair obtains the list 1424 of IESG and IAB open positions and descriptions from the IETF 1425 Executive Director. 1427 3. The Chair announces the solicitation for voting volunteer members 1428 that must remain open for at least 30 days. The announcement must 1429 be done no later than 7 months and 2 weeks prior to the First IETF 1430 (approx. July 15). 1432 4. After the solicitation closes the Chair announces the pool of 1433 volunteers and the date of the random selection, which must be at 1434 least 1 week in the future. The announcement must be done no 1435 later than 6 months and 2 weeks prior to the First IETF 1436 (approx. August 15). 1438 5. On the appointed day the random selection occurs and the Chair 1439 announces the members of the committee and the 1 week challenge 1440 period. The announcement must be done no later than 6 months and 1441 1 week prior to the First IETF (approx. August 22). 1443 6. During the challenge period the Chair contacts each of the 1444 committee members and confirms their availability to participate. 1446 7. After the challenge period closes the Chair announces the members of 1447 the committee and its term begins. The announcement must be done no 1448 later than 6 months prior to the First IETF (approx. September 1). 1450 8. The committee has one month during which it is to self-organize in 1451 preparation for completing its assigned duties. This must be done no 1452 later than 5 months prior to the First IETF (approx. October 1). 1454 9. END the Committee Member Selection Process; BEGIN the Selection of 1455 Candidates; Time is at least 5 months prior to the First IETF 1456 (approx. October 1). 1458 10. The Chair establishes and announces the milestones to ensure the 1459 timely selection of the candidates, including a call for 1460 nominations for the open positions. The announcement must be done 1461 no later than 5 months prior to the First IETF (approx. October 1462 1). 1464 11. Over the next 3 months the nominating committee collects input 1465 and deliberates. It should plan to conduct interviews and other 1466 consultations during the Third IETF. The committee must complete 1467 its candidate selection no later than 2 months prior to the First 1468 IETF (approx. January 1). 1470 12. END the Selection of Candidates; BEGIN the Confirmation of 1471 Candidates; Time is at least 2 months prior to the First IETF 1472 (approx. January 1); 1474 13. The committee presents its slate of candidates to their 1475 respective confirming bodies. The presentation must be done no 1476 later than 2 months prior to the First IETF (approx. January 1). 1478 14. The confirming bodies have 1 month to deliberate and, in 1479 consultation with the nominating committee, accept or reject 1480 candidates on the slate. 1482 15. The Chair announces the confirmed candidates. The announcement 1483 must be done no later than 1 month prior to the First IETF 1484 (approx. February 1). 1486 Figure 1: The Timeline 1488 Intellectual Property Statement 1490 The IETF takes no position regarding the validity or scope of any 1491 intellectual property or other rights that might be claimed to 1492 pertain to the implementation or use of the technology described in 1493 this document or the extent to which any license under such rights 1494 might or might not be available; neither does it represent that it 1495 has made any effort to identify any such rights. Information on the 1496 IETF's procedures with respect to rights in standards-track and 1497 standards-related documentation can be found in BCP-11. Copies of 1498 claims of rights made available for publication and any assurances of 1499 licenses to be made available, or the result of an attempt made to 1500 obtain a general license or permission for the use of such 1501 proprietary rights by implementors or users of this specification can 1502 be obtained from the IETF Secretariat. 1504 The IETF invites any interested party to bring to its attention any 1505 copyrights, patents or patent applications, or other proprietary 1506 rights which may cover technology that may be required to practice 1507 this standard. Please address the information to the IETF Executive 1508 Director. 1510 Full Copyright Statement 1512 Copyright (C) The Internet Society (2003). All Rights Reserved. 1514 This document and translations of it may be copied and furnished to 1515 others, and derivative works that comment on or otherwise explain it 1516 or assist in its implementation may be prepared, copied, published 1517 and distributed, in whole or in part, without restriction of any 1518 kind, provided that the above copyright notice and this paragraph are 1519 included on all such copies and derivative works. However, this 1520 document itself may not be modified in any way, such as by removing 1521 the copyright notice or references to the Internet Society or other 1522 Internet organizations, except as needed for the purpose of 1523 developing Internet standards in which case the procedures for 1524 copyrights defined in the Internet Standards process must be 1525 followed, or as required to translate it into languages other than 1526 English. 1528 The limited permissions granted above are perpetual and will not be 1529 revoked by the Internet Society or its successors or assignees. 1531 This document and the information contained herein is provided on an 1532 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1533 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1534 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1535 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1536 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1538 Acknowledgement 1540 Funding for the RFC Editor function is currently provided by the 1541 Internet Society.