idnits 2.17.1 draft-ietf-nomcom-rfc2727bis-04.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 41 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 5 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 (May 8, 2003) is 7657 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 1363, 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 (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Galvin, Editor 3 Internet-Draft eList eXpress LLC 4 Expires: November 6, 2003 May 8, 2003 6 IAB and IESG Selection, Confirmation, and Recall Process: Operation 7 of the Nominating and Recall Committees 8 draft-ietf-nomcom-rfc2727bis-04.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 November 6, 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 . . . . . . . . . . . . . . . . 12 65 5. Nominating Committee Operation . . . . . . . . . . . . . . . . 20 66 6. Dispute Resolution Process . . . . . . . . . . . . . . . . . . 26 67 7. Member Recall . . . . . . . . . . . . . . . . . . . . . . . . 28 68 8. Changes From RFC2727 . . . . . . . . . . . . . . . . . . . . . 30 69 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 32 70 10. Security Considerations . . . . . . . . . . . . . . . . . . . 34 71 References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 35 73 A. Oral Tradition . . . . . . . . . . . . . . . . . . . . . . . . 36 74 B. Nominating Committee Timeline . . . . . . . . . . . . . . . . 37 75 Intellectual Property and Copyright Statements . . . . . . . . 40 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. However, these procedures are subject to change and such 83 change takes effect immediately upon its approval, regardless of 84 whether this document has yet been revised. 86 The following two assumptions continue to be true of this 87 specification. 89 1. The Internet Research Task Force (IRTF) and Internet Research 90 Steering Group (IRSG) are not a part of the process described 91 here. 93 2. The organization (and re-organization) of the IESG is not a part 94 of the process described here. 96 The time frames specified here use IETF meetings as a frame of 97 reference. The time frames assume that the IETF meets three times 98 per calendar year with approximately equal amounts of time between 99 them. The meetings are referred to as the First IETF, Second IETF, or 100 Third IETF as needed. 102 The next section lists the words and phrases commonly used throughout 103 this document with their intended meaning. 105 The majority of this document is divided into four major topics as 106 follows. 108 General: This a set of rules and constraints that apply to the 109 selection and confirmation process as a whole. 111 Nominating Committee Selection: This is the process by which the 112 volunteers who will serve on the committee are recognized. 114 Nominating Committee Operation: This is the set of principles, rules, 115 and constraints that guide the activities of the nominating 116 committee, including the confirmation process. 118 Member Recall: This is the process by which the behavior of a sitting 119 member of the IESG or IAB may be questioned, perhaps resulting in 120 the removal of the sitting member. 122 A final section describes how this document differs from its 123 predecessor: RFC2727. [2] 124 An appendix of useful facts and practices collected from previous 125 nominating committees is also included. 127 2. Definitions 129 The following words and phrases are commonly used throughout this 130 document. They are listed here with their intended meaning for the 131 convenience of the reader. 133 candidate: A nominee who has been selected to be considered for 134 confirmation by a confirming body. 136 confirmed candidate: A candidate that has been reviewed and approved 137 by a confirming body. 139 nominating committee term: The term begins when its members are 140 officially announced, which is expected to be prior to the Third 141 IETF to ensure it is fully operational at the Third IETF. The 142 term ends at the Third IETF (not three meetings) after the next 143 nominating committee's term begins. 145 nominee: A person who is being or has been considered for one or more 146 open positions of the IESG or IAB. 148 sitting member: A person who is currently serving a term of 149 membership in the IESG, IAB or ISOC Board of Trustees. 151 3. General 153 The following set of rules apply to the process as a whole. If 154 necessary, a paragraph discussing the interpretation of each rule is 155 included. 157 1. The annual process is expected to be completed within 7 months. 159 The annual process is expected to be completed one month prior to 160 the Friday of the week before the First IETF. It is expected to 161 begin at least 8 months prior to the Friday of the week before 162 the First IETF. 164 The process officially begins with the announcement of the Chair 165 of the committee. The process officially ends when all confirmed 166 candidates have been announced. 168 The annual process is comprised of three major components as 169 follows. 171 1. The selection and organization of the nominating committee 172 members. 174 2. The selection of candidates by the nominating committee. 176 3. The confirmation of the candidates. 178 There is an additional month set aside between when the annual 179 process is expected to end and the term of the new candidates is 180 to begin. This time may be used during unusual circumstances to 181 extend the time allocated for any of the components listed above. 183 2. The principal functions of the nominating committee are to review 184 each open IESG and IAB position and to either nominate its 185 incumbent or a superior candidate. 187 Although there is no term limit for serving in any IESG or IAB 188 position, the nominating committee may use length of service as 189 one of its criteria for evaluating an incumbent. 191 The nominating committee does not select the open positions to be 192 reviewed; it is instructed as to which positions to review. 194 The nominating committee will be given the title of the positions 195 to be reviewed and a brief description of the desirable set of 196 qualifications of the candidate that is nominated to fill each 197 position. 199 Incumbents must notify the nominating committee if they wish to 200 be nominated. 202 The nominating committee does not confirm its candidates; it 203 presents its candidates to the appropriate confirming body as 204 indicated below. 206 A superior candidate is one who the nominating committee believes 207 would contribute in such a way as to improve or enhance the body 208 to which he or she is nominated. 210 3. One-half of each of the then current IESG and IAB positions is 211 selected to be reviewed each year. 213 The intent of this rule to ensure the review of approximately 214 one-half of each of the IESG and IAB sitting members each year. 215 It is recognized that circumstances may exist that will require 216 the nominating committee to review more or less than one-half of 217 the current positions, e.g., if the IESG or IAB have re-organized 218 prior to this process and created new positions, if there are an 219 odd number of current positions, or if a member unexpectedly 220 resigns. 222 4. Confirmed candidates are expected to serve at least a 2 year 223 term. 225 The intent of this rule is to ensure that members of the IESG and 226 IAB serve the number of years that best facilitates the review of 227 one-half of the members each year. 229 It is consistent with this rule for the nominating committee to 230 choose one or more of the currently open positions to which it 231 may assign a term greater than 2 years in order to ensure the 232 ideal application of this rule in the future. 234 It is consistent with this rule for the nominating committee to 235 choose one or more of the currently open positions that share 236 responsibilities with other positions (both those being reviewed 237 and those sitting) to which it may assign a term greater than 2 238 years to ensure that all such members will not be reviewed at the 239 same time. 241 All sitting member terms end during the First IETF meeting 242 corresponding to the end of the term for which they were 243 confirmed. All confirmed candidate terms begin during the First 244 IETF meeting corresponding to the beginning of the term for which 245 they were confirmed. Normally, the confirmed candidate's term 246 begins when the currently sitting member's term ends on the last 247 day of the meeting. A term may begin or end no sooner than the 248 first day of the meeting and no later than the last day of the 249 meeting as determined by the mutual agreement of the currently 250 sitting member and the confirmed candidate. The confirmed 251 candidate's term may overlap the sitting member's term during the 252 meeting as determined by their mutual agreement. 254 5. Mid-term vacancies are filled by the same rules as documented 255 here with four qualifications. 257 First, when there is only one official nominating committee the 258 body with the mid-term vacancy relegates the responsibility to 259 fill the vacancy to it. If the mid-term vacancy occurs during 260 the period of time that the term of the prior year's nominating 261 committee overlaps with the term of the current year's nominating 262 committee, the body with the mid-term vacancy must relegate the 263 responsibility to fill the vacancy to the prior year's nominating 264 committee. 266 Second, if it is the case that the nominating committee is 267 reconvening to fill the mid-term vacancy, then the candidate 268 selection and confirmation process is expected to be completed 269 within 6 weeks, with all other time periods otherwise unspecified 270 prorated accordingly. 272 Third, the confirming body has two weeks from the day it is 273 notified of a candidate to reject the candidate, otherwise the 274 candidate is assumed to have been confirmed. 276 Fourth, the term of the confirmed candidate will be either: 278 1. the remainder of the term of the open position if that 279 remainder is not less than one year. 281 2. the remainder of the term of the open position plus the next 282 2 year term if that remainder is less than one year. 284 In both cases a year is the period of time from a First IETF 285 meeting to the next First IETF meeting. 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 committee for its 313 consideration. 315 2. The nominating committee selects candidates and advises each 316 confirming body of its respective candidates. 318 3. The confirming bodies review their respective candidates and, 319 in consultation with the nominating committee, consent to 320 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 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. The confirming bodies decide their consent according to a 354 mechanism of their own choosing, which must ensure that at 355 least one-half of the sitting members agree with the 356 decision. 358 At least one-half of the sitting members of the confirming 359 bodies must agree to either confirm or reject each individual 360 nominee. The agreement must be decided within a reasonable 361 timeframe. The agreement may be decided by conducting a 362 formal vote, by asserting consensus based on informal 363 exchanges (email), or by whatever mechanism is used to 364 conduct the normal business of the confirming body. 366 8. The following rules apply if a candidate to be submitted to a 367 confirming body is a sitting member of the IESG, IAB, or ISOC 368 Board of Trustees, and the candidate is not serving in an open 369 position being filled by the nominating committee. 371 The confirmation of a candidate to an open position does not 372 automatically create a vacancy in the IESG or IAB position 373 currently occupied by the candidate. The mid-term vacancy can 374 not exist until, first, the candidate formally resigns from the 375 current position and, second, the body with the vacancy formally 376 decides for itself that it wants the nominating committee to fill 377 the mid-term vacancy. 379 The resignation should be effective as of when the term of the 380 new position begins. The resignation may remain confidential to 381 the IAB, IESG, and nominating committee until the confirmed 382 candidate is announced for the new position. 384 Filling a mid-term vacancy is a separate and independent action 385 from the customary action of filling open positions. In 386 particular, a nominating committee must complete its job with 387 respect to filling the open positions and then separately submit 388 a candidate to fill a mid-term vacancy. 390 It is consistent with these rules for the announcements of a 391 resignation, of the existence of a mid-term vacancy, and of the 392 confirmed candidates to all occur at the same time as long as the 393 actual sequence of events that occurred did so in the following 394 order. 396 * The nominating committee completes the advice and consent 397 process for the candidate already sitting on another body. 399 * The newly confirmed candidate resigns from their current 400 position. 402 * The body with the new mid-term vacancy requests that the 403 nominating committee fill the position. 405 * The Executive Director of the IETF informs the nominating 406 committee of the mid-term vacancy. 408 * The nominating committee acts on the request to fill the 409 mid-term vacancy 411 9. All announcements must be made using at least the mechanism used 412 by the IETF Secretariat for its announcements, including a notice 413 on the IETF web site. 415 As of the publication of this document the current mechanism is 416 an email message to both the "ietf" and the "ietf-announce" 417 mailing lists. 419 4. Nominating Committee Selection 421 The following set of rules apply to the creation of the nominating 422 committee and the selection of its members. 424 1. The process of selecting and organizing the members of the 425 nominating committee is expected to be completed within 3 426 months. 428 The selection and organization process must be completed at 429 least one month prior to the Third IETF. This ensures the 430 nominating committee is fully operational and available for 431 interviews and consultation during the Third IETF. 433 2. The term of a nominating committee is expected to be 15 months. 435 It is the intent of this rule that the end of a nominating 436 committee's term overlap by approximately three months the 437 beginning of the term of the next nominating committee. 439 The term of a nominating committee begins when its members are 440 officially announced. The term ends at the Third IETF (not 441 three meetings) after the next nominating committee's term 442 begins. 444 A term is expected to begin at least two months prior to the 445 Third IETF to ensure the nominating committee has at least one 446 month to get organized before preparing for the Third IETF. 448 A nominating committee is expected to complete any 449 work-in-progress before it is dissolved at the end of its term. 451 During the period of time that the terms of the nominating 452 committees overlap, all mid-term vacancies are to be relegated 453 to the prior year's nominating committee. The prior year's 454 nominating committee has no other responsibilities during the 455 overlap period. At all times other than the overlap period 456 there is exactly one official nominating committee and it is 457 responsible for all mid-term vacancies. 459 When the prior year's nominating committee is filling a mid-term 460 vacancy during the period of time that the terms overlap, the 461 nominating committees operate independently. However, some 462 coordination is needed between them. Since the prior year's 463 Chair is a non-voting advisor to the current nominating 464 committee the coordination is expected to be straightforward. 466 3. The nominating committee comprises at least a Chair, 10 voting 467 volunteers, 2 liaisons, and an advisor. 469 Any committee member may propose the addition of an advisor to 470 participate in some or all of the deliberations of the 471 committee. The addition must be approved by all members of the 472 committee according to its established voting mechanism. 473 Advisors participate as individuals. 475 Any committee member may propose the addition of a liaison from 476 other unrepresented organizations to participate in some or all 477 of the deliberations of the committee. The addition must be 478 approved by all members of the committee according to its 479 established voting mechanism. Liaisons participate as 480 representatives of their respective organizations. 482 The Chair is selected according to rules stated elsewhere in 483 this document. 485 The 10 voting volunteers are selected according to rules stated 486 elsewhere in this document. 488 The IESG and IAB liaisons are selected according to rules stated 489 elsewhere in this document. 491 The Chair of last year's nominating committee serves as an 492 advisor according to rules stated elsewhere in this document. 494 None of the Chair, liaisons, or advisors vote on the selection 495 of candidates. They do vote on all other issues before the 496 committee unless otherwise specified. 498 4. The Chair of the nominating committee is responsible for 499 ensuring the nominating committee completes its assigned duties 500 in a timely fashion and performs in the best interests of the 501 IETF community. 503 The Chair must be thoroughly familiar with the rules and 504 guidance indicated throughout this document. The Chair must 505 ensure the nominating committee completes its assigned duties in 506 a manner that is consistent with this document. 508 The Chair must attest by proclamation at a plenary session of 509 the First IETF that the results of the committee represent its 510 best effort and the best interests of the IETF community. 512 The Chair does not vote on the selection of candidates. 514 5. The Internet Society President appoints the Chair, who must meet 515 the same requirements for membership in the nominating committee 516 as a voting volunteer. 518 The nominating committee Chair must agree to invest the time 519 necessary to ensure that the nominating committee completes its 520 assigned duties and to perform in the best interests of the IETF 521 community in that role. 523 The appointment must be completed no later than the Second IETF 524 meeting to ensure it can be announced during a plenary session 525 at that meeting. The appointment must be completed as soon as 526 necessary to ensure the annual process can complete at the time 527 specified elsewhere in this document. 529 6. A Chair, in consultation with the Internet Society President, 530 may appoint a temporary substitute. 532 There are a variety of ordinary circumstances that may arise 533 from time to time that could result in a Chair being unavailable 534 to oversee the activities of the committee. The Chair, in 535 consultation with the Internet Society President, may appoint a 536 substitute from a pool comprised of the liaisons currently 537 serving on the committee and the prior year's Chair or designee. 539 Any such appointment must be temporary and does not absolve the 540 Chair of any or all responsibility for ensuring the nominating 541 committee completes its assigned duties in a timely fashion. 543 7. Liaisons are responsible for ensuring the nominating committee 544 in general and the Chair in particular execute their assigned 545 duties in the best interests of the IETF community. 547 Liaisons are expected to represent the views of their respective 548 organizations during the deliberations of the committee. They 549 should provide information as requested or when they believe it 550 would be helpful to the committee. 552 Liaisons from the IESG and IAB are expected to provide 553 information to the nominating committee regarding the operation, 554 responsibility, and composition of their respective bodies. 556 Liaisons are expected to convey questions from the committee to 557 their respective organizations and responses to those questions 558 to the committee, as requested by the committee. 560 Liaisons from the IESG, IAB, and Internet Society Board of 561 Trustees are expected to review the operation and executing 562 process of the nominating committee and to report any concerns 563 or issues to the Chair of the nominating committee immediately. 564 If they can not resolve the issue between themselves liaisons 565 must report the issue to their respective bodies. If their 566 respective body agrees that there is an issue the liaison must 567 report it according to the dispute resolution process stated 568 elsewhere in this document. 570 Liaisons from confirming bodies are expected to assist the 571 committee in preparing the testimony it is required to provide 572 with its candidates. 574 Liaisons may have other nominating committee responsibilities as 575 required by their respective organizations or requested by the 576 nominating committee, except that such responsibilities may not 577 conflict with any other provisions of this document. 579 Liaisons do not vote on the selection of candidates. 581 8. The sitting IAB and IESG members each appoint a liaison to the 582 nominating committee from their current membership who is not 583 sitting in an open position. 585 9. The Internet Society Board of Trustees may appoint a liaison to 586 the nominating committee. 588 10. An advisor is responsible for such duties as specified by the 589 invitation that resulted in the appointment. 591 Advisors do not vote on the selection of candidates. 593 11. The Chair of the prior year's nominating committee serves as an 594 advisor to the current committee. 596 The prior year's Chair is expected to review the actions and 597 activities of the current Chair and to report any concerns or 598 issues to the nominating committee Chair immediately. If they 599 can not resolve the issue between themselves the prior year's 600 Chair must report it according to the dispute resolution process 601 stated elsewhere in this document. 603 The prior year's Chair may select a designee from a pool 604 composed of the voting volunteers of the prior year's committee 605 and all prior Chairs if the Chair is unavailable. If the prior 606 year's Chair is unavailable or is unable or unwilling to make 607 such a designation in a timely fashion, the Chair of the current 608 year's committee may select a designee in consultation with the 609 Internet Society President. 611 Selecting a prior year's committee member as the designee 612 permits the experience of the prior year's deliberations to be 613 readily available to the current committee. Selecting an 614 earlier prior year Chair as the designee permits the experience 615 of being a Chair as well as that Chair's committee deliberations 616 to be readily available to the current committee. 618 12. Voting volunteers are responsible for completing the tasks of 619 the nominating committee in a timely fashion. 621 Each voting volunteer is expected to participate in all 622 activities of the nominating committee with a level of effort 623 approximately equal to all other voting volunteers. Specific 624 tasks to be completed are established and managed by the Chair 625 according to rules stated elsewhere in this document. 627 13. The Chair must establish and announce milestones for the 628 selection of the nominating committee members. 630 There is a defined time period during which the selection 631 process must be completed. The Chair must establish a set of 632 milestones which, if met in a timely fashion, will result in the 633 completion of the process on time. 635 14. The Chair obtains the list of IESG and IAB positions to be 636 reviewed and announces it along with a solicitation for names of 637 volunteers from the IETF community willing to serve on the 638 nominating committee. 640 The solicitation must permit the community at least 30 days 641 during which they may choose to volunteer to be selected for the 642 nominating committee. 644 The list of open positions is published with the solicitation to 645 facilitate community members choosing between volunteering for 646 an open position and volunteering for the nominating committee. 648 15. Members of the IETF community must have attended at least 3 of 649 the last 5 IETF meetings in order to volunteer. 651 The 5 meetings are the five most recent meetings that ended 652 prior to the date on which the solicitation for nominating 653 committee volunteers was submitted for distribution to the IETF 654 community. 656 The IETF Secretariat is responsible for confirming that 657 volunteers have met the attendance requirement. 659 Volunteers must provide their full name, email address, and 660 primary company or organization affiliation (if any) when 661 volunteering. 663 Volunteers are expected to be familiar with the IETF processes 664 and procedures, which are readily learned by active 665 participation in a working group and especially by serving as a 666 document editor or working group chair. 668 16. Members of the Internet Society Board of Trustees, sitting 669 members of the IAB, and sitting members of the IESG may not 670 volunteer to serve on the nominating committee. 672 17. The Chair announces both the list of the pool of volunteers from 673 which the 10 voting volunteers will be randomly selected and the 674 method with which the selection will be completed. 676 The announcement should be made at least 1 week prior to the 677 date on which the random selection will occur. 679 The pool of volunteers must be enumerated or otherwise indicated 680 according to the needs of the selection method to be used. 682 The announcement must specify the data that will be used as 683 input to the selection method. The method must depend on random 684 data whose value is not known or available until the date on 685 which the random selection will occur. 687 It must be possible to independently verify that the selection 688 method used is both fair and unbiased. A method is fair if each 689 eligible volunteer is equally likely to be selected. A method 690 is unbiased if no one can influence its outcome in favor of a 691 specific outcome. 693 It must be possible to repeat the selection method, either 694 through iteration or by restarting in such a way as to remain 695 fair and unbiased. This is necessary to replace selected 696 volunteers should they become unavailable after selection. 698 The selection method must produce an ordered list of volunteers. 700 One possible selection method is described in RFC2777 [1]. 702 18. The Chair randomly selects the 10 voting volunteers from the 703 pool of names of volunteers and announces the members of the 704 nominating committee. 706 No more than two volunteers with the same primary affiliation 707 may be selected for the nominating committee. The Chair reviews 708 the primary affiliation of each volunteer selected by the method 709 in turn. If the primary affiliation for a volunteer is the same 710 as two previously selected volunteers, that volunteer is removed 711 from consideration and the method is repeated to identify the 712 next eligible volunteer. 714 There must be at least two announcements of all members of the 715 nominating committee. 717 The first announcement should occur as soon after the random 718 selection as is reasonable for the Chair. The community must 719 have at least 1 week during which any member may challenge the 720 results of the random selection. 722 The challenge must be made in writing (email is acceptable) to 723 the Chair. The Chair has 48 hours to review the challenge and 724 offer a resolution to the member. If the resolution is not 725 accepted by the member, that member may report the challenge 726 according to the dispute resolution process stated elsewhere in 727 this document. 729 If a selected volunteer, upon reading the announcement with the 730 list of selected volunteers, finds that two or more other 731 volunteers have the same affiliation, then the volunteer should 732 notify the Chair who will determine the appropriate action. 734 During at least the 1 week challenge period the Chair must 735 contact each of the members and confirm their willingness and 736 availability to serve. The Chair should make every reasonable 737 effort to contact each member. 739 * If the Chair is unable to contact a liaison the problem is 740 referred to the respective organization to resolve. The 741 Chair should allow a reasonable amount of time for the 742 organization to resolve the problem and then may proceed 743 without the liaison. 745 * If the Chair is unable to contact an advisor the Chair may 746 elect to proceed without the advisor, except for the prior 747 year's Chair for whom the Chair must consult with the 748 Internet Society President as stated elsewhere in this 749 document. 751 * If the Chair is unable to contact a voting volunteer the 752 Chair must repeat the random selection process in order to 753 replace the unavailable volunteer. There should be at least 754 1 day between the announcement of the iteration and the 755 selection process. 757 After at least 1 week and confirming that 10 voting volunteers 758 are ready to serve, the Chair makes the second announcement of 759 the members of the nominating committee, which officially begins 760 the term of the nominating committee. 762 19. The Chair works with the members of the committee to organize 763 itself in preparation for completing its assigned duties. 765 The committee has approximately one month during which it can 766 self-organize. Its responsibilities during this time include 767 but are not limited to the following. 769 * Setting up a regular teleconference schedule. 771 * Setting up an internal web site. 773 * Setting up a mailing list for internal discussions. 775 * Setting up an email address for receiving community input. 777 * Establishing operational procedures. 779 * Establishing milestones in order to monitor the progress of 780 the selection process. 782 5. Nominating Committee Operation 784 The following rules apply to the operation of the nominating 785 committee. If necessary, a paragraph discussing the interpretation 786 of each rule is included. 788 The rules are organized approximately in the order in which they 789 would be invoked. 791 1. All rules and special circumstances not otherwise specified are 792 at the discretion of the committee. 794 Exceptional circumstances will occasionally arise during the 795 normal operation of the nominating committee. This rule is 796 intended to foster the continued forward progress of the 797 committee. 799 Any member of the committee may propose a rule for adoption by 800 the committee. The rule must be approved by all members of the 801 committee according to its established voting mechanism. 803 All members of the committee should consider whether the 804 exception is worthy of mention in the next revision of this 805 document and follow-up accordingly. 807 2. The process of selecting candidates to be confirmed by their 808 respective confirming body is expected to be completed within 3 809 months. 811 The selection process must be completed at least two month's 812 prior to the First IETF. This ensures the nominating committee 813 has sufficient time to complete the confirmation process. 815 3. The process of confirming the candidates is expected to be 816 completed within 1 month. 818 The confirmation process must be completed at least one month 819 prior to the First IETF. 821 4. The Chair must establish for the nominating committee a set of 822 milestones for the candidate selection and confirmation process. 824 There is a defined time period during which the candidate 825 selection and confirmation process must be completed. The Chair 826 must establish a set of milestones which, if met in a timely 827 fashion, will result in the completion of the process on time. 828 The Chair should allow time for iterating the activities of the 829 committee if one or more candidates is not confirmed. 831 The Chair should ensure that all committee members are aware of 832 the milestones. 834 5. The Chair must establish a voting mechanism. 836 The committee must be able to objectively determine when a 837 decision has been made during its deliberations. The criteria 838 for determining closure must be established and known to all 839 members of the nominating committee. 841 6. At least a quorum of committee members must participate in a 842 vote. 844 Only voting volunteers vote on a candidate selection. For a 845 candidate selection vote a quorum is comprised of at least 7 of 846 the voting volunteers. 848 At all other times a quorum is present if at least 75% of the 849 nominating committee members are participating. 851 7. Any member of the nominating committee may propose to the 852 committee that any other member except the Chair be recalled. 853 The process for recalling the Chair is defined elsewhere in this 854 document. 856 There are a variety of ordinary circumstances that may arise 857 that could result in one or more members of the committee being 858 unavailable to complete their assigned duties, for example 859 health concerns, family issues, or a change of priorities at 860 work. A committee member may choose to resign for unspecified 861 personal reasons. In addition, the committee may not function 862 well as a group because a member may be disruptive or otherwise 863 uncooperative. 865 Regardless of the circumstances, if individual committee members 866 can not work out their differences between themselves, the 867 entire committee may be called upon to discuss and review the 868 circumstances. If a resolution is not forthcoming a vote may be 869 conducted. A member may recalled if at least a quorum of all 870 committee members agree, including the vote of the member being 871 recalled. 873 If a liaison member is recalled the committee must notify the 874 affected organization and must allow a reasonable amount of time 875 for a replacement to be identified by the organization before 876 proceeding. 878 If an advisor member other than the prior year's Chair is 879 recalled, the committee may choose to proceed without the 880 advisor. In the case of the prior year's Chair, the Internet 881 Society President must be notified and the current Chair must be 882 allowed a reasonable amount of time to consult with the Internet 883 Society President to identify a replacement before proceeding. 885 If a voting volunteer member is recalled the committee may 886 choose to proceed with only 9 voting volunteers at its own 887 discretion. In all other cases the Chair must repeat the random 888 selection process including an announcement of the iteration 889 prior to the actual selection as stated elsewhere in this 890 document. 892 A change in the primary affiliation of a voting volunteer during 893 the term of the nominating committee is not a cause to request 894 the recall of that volunteer, even if the change would result in 895 more than two voting volunteers with the same affiliation. 897 8. Only the prior year's Chair may request the recall of the 898 current Chair. 900 It is the responsibility of the prior year's Chair to ensure the 901 current Chair completes the assigned tasks in a manner 902 consistent with this document and in the best interests of the 903 IETF community. 905 Any member of the committee who has an issue or concern 906 regarding the Chair should report it to the prior year's Chair 907 immediately. The prior year's Chair is expected to report it to 908 the Chair immediately. If they can not resolve the issue 909 between themselves the prior year's Chair must report it 910 according to the dispute resolution process stated elsewhere in 911 this document. 913 9. All members of the nominating committee may participate in all 914 deliberations. 916 The emphasis of this rule is that no member can be explicitly 917 excluded from any deliberation. However, a member may 918 individually choose not to participate in a deliberation. 920 10. The Chair announces the open positions to be reviewed and the 921 call for nominees. 923 The call for nominees must include a request for comments 924 regarding the past performance of incumbents, which will be 925 considered during the deliberations of the nominating committee. 927 The call must request that a nomination include a valid, working 928 email address, a telephone number, or both for the nominee. The 929 nomination must include the set of skills or expertise the 930 nominator believes the nominee has that would be desirable. 932 11. Any member of the IETF community may nominate any member of the 933 IETF community for any open position, whose eligibility to serve 934 will be confirmed by the nominating committee. 936 A self-nomination is permitted. 938 Nominating committee members are not eligible to be considered 939 for filling any open position by the nominating committee on 940 which they serve. They become ineligible as soon as the term of 941 the nominating committee on which they serve officially begins. 942 They remain ineligible for the duration of that nominating 943 committee's term. 945 Although each nominating committee's term overlaps with the 946 following nominating committee's term, nominating committee 947 members are eligible for nomination by the following committee 948 if not otherwise disqualified. 950 Members of the IETF community who were recalled from any IESG or 951 IAB position during the previous two years are not eligible to 952 be considered for filling any open position. 954 12. The nominating committee selects candidates based on its 955 understanding of the IETF community's consensus of the 956 qualifications required to fill the open positions. 958 The intent of this rule is to ensure that the nominating 959 committee consults with a broad base of the IETF community for 960 input to its deliberations. In particular, the nominating 961 committee must determine if the desired qualifications for the 962 open positions matches its understanding of the qualifications 963 desired by the IETF community. 965 The consultations are permitted to include names of nominees, if 966 all parties to the consultation agree to observe the same 967 confidentiality rules as the nominating committee itself. 969 A broad base of the community should include the existing 970 members of the IAB and IESG, especially sitting members who 971 share responsibilities with open positions, e.g., co-Area 972 Directors. 974 Only voting volunteer members vote to select candidates. 976 13. Nominees should be advised that they are being considered and 977 must consent to their nomination prior to being chosen as 978 candidates. 980 Although the nominating committee will make every reasonable 981 effort to contact and to remain in contact with nominees, any 982 nominee whose contact information changes during the process and 983 who wishes to still be considered should inform the nominating 984 committee of the changes. 986 A nominee's consent must be written (email is acceptable) and 987 must include a commitment to provide the resources necessary to 988 fill the open position and an assurance that the nominee will 989 perform the duties of the position for which they are being 990 considered in the best interests of the IETF community. 992 Consenting to a nomination must occur prior to a nominee being a 993 candidate and may occur as soon after the nomination as needed 994 by the nominating committee. 996 Consenting to a nomination must not imply the nominee will be a 997 candidate. 999 The nominating committee should help nominees provide 1000 justification to their employers. 1002 14. The nominating committee advises the confirming bodies of their 1003 candidates, specifying a single candidate for each open position 1004 and testifying as to how each candidate meets the qualifications 1005 of an open position. 1007 For each candidate, the testimony must include a brief statement 1008 of the qualifications for the position that is being filled, 1009 which may be exactly the qualifications that were requested. If 1010 the qualifications differ from the desired qualifications 1011 originally requested a brief statement explaining the difference 1012 must be included. 1014 The testimony may include either or both of a brief resume of 1015 the candidate and a brief summary of the deliberations of the 1016 nominating committee. 1018 15. Confirmed candidates must consent to their confirmation and 1019 rejected candidates and nominees must be notified before 1020 confirmed candidates are announced. 1022 It is not necessary to notify and get consent from all confirmed 1023 candidates together. 1025 A nominee may not know they were a candidate. This permits a 1026 candidate to be rejected by a confirming body without the 1027 nominee knowing about the rejection. 1029 Rejected nominees who consented to their nomination must be 1030 notified prior to announcing the confirmed candidates. Rejected 1031 candidates must be notified prior to announcing the confirmed 1032 candidates. 1034 It is not necessary to announce all confirmed candidates 1035 together. 1037 The nominating committee must ensure that all confirmed 1038 candidates are prepared to serve prior to announcing their 1039 confirmation. 1041 16. The nominating committee should archive the information it has 1042 collected or produced for a period of time not to exceed its 1043 term. 1045 The purpose of the archive is to assist the nominating committee 1046 should it be necessary for it to fill a mid-term vacancy. 1048 The existence of an archive, how it is implemented, and what 1049 information to archive is at the discretion of the committee. 1050 The decision must be approved by a quorum of the voting 1051 volunteer members. 1053 The implementation of the archive should make every reasonable 1054 effort to ensure that the confidentiality of the information it 1055 contains is maintained. 1057 6. Dispute Resolution Process 1059 The dispute resolution process described here is to be used as 1060 indicated elsewhere in this document. Its applicability in other 1061 circumstances is beyond the scope of this document. 1063 The nominating committee operates under a strict rule of 1064 confidentiality. For this reason when process issues arise it is 1065 best to make every reasonable effort to resolve them within the 1066 committee. However, when circumstances do not permit this or no 1067 resolution is forthcoming, the process described here is to be used. 1069 The following rules apply to the process. 1071 1. The results of this process are final and binding. There is no 1072 appeal. 1074 2. The process begins with the submission of a request as described 1075 below to the Internet Society President. 1077 3. As soon as the process begins, the nominating committee may 1078 continue those activities that are unrelated to the issue to be 1079 resolved except that it must not submit any candidates to a 1080 confirming body until the issue is resolved. 1082 4. All parties to the process are subject to the same 1083 confidentiality rules as each member of the nominating committee. 1085 5. The process should be completed within two weeks. 1087 The process is as follows. 1089 1. The party seeking resolution submits a written request (email is 1090 acceptable) to the Internet Society President detailing the issue 1091 to be resolved. 1093 2. The Internet Society President appoints an arbiter to investigate 1094 and resolve the issue. A self-appointment is permitted. 1096 3. The arbiter investigates the issue making every reasonable effort 1097 to understand both sides of the issue. Since the arbiter is 1098 subject to the same confidentiality obligations as all nominating 1099 committee members, all members are expect to cooperate fully with 1100 the arbiter and to provide all relevant information to the 1101 arbiter for review. 1103 4. After consultation with the two principal parties to the issue, 1104 the arbiter decides a resolution. Whatever actions are necessary 1105 to execute the resolution are immediately begun and completed as 1106 quickly as possible. 1108 5. The arbiter summarizes the issue, the resolution, and the 1109 rationale for the resolution for the Internet Society President. 1111 6. In consultation with the Internet Society President, the arbiter 1112 prepares a report of the dispute and its resolution. The report 1113 should include all information that in the judgement of the 1114 arbiter does not violate the confidentiality requirements of the 1115 nominating committee. 1117 7. The Chair includes the dispute report when reporting on the 1118 activities of the nominating committee to the IETF community. 1120 7. Member Recall 1122 The following rules apply to the recall process. If necessary, a 1123 paragraph discussing the interpretation of each rule is included. 1125 1. At any time, at least 20 members of the IETF community, who are 1126 qualified to be voting members of a nominating committee, may 1127 request by signed petition (email is acceptable) to the Internet 1128 Society President the recall of any sitting IAB or IESG member. 1130 All individual and collective qualifications of nominating 1131 committee eligibility are applicable, including that no more than 1132 two signatories may have the same primary affiliation. 1134 Each signature must include a full name, email address, and 1135 primary company or organization affiliation. 1137 The petition must include a statement of justification for the 1138 recall and all relevant and appropriate supporting documentation. 1140 The petition and its signatories must be announced to the IETF 1141 community. 1143 2. Internet Society President shall appoint a Recall Committee 1144 Chair. 1146 The Internet Society President must not evaluate the recall 1147 request. It is explicitly the responsibility of the IETF 1148 community to evaluate the behavior of its leaders. 1150 3. The recall committee is created according to the same rules as is 1151 the nominating committee with the qualifications that both the 1152 person being investigated and the parties requesting the recall 1153 must not be a member of the recall committee in any capacity. 1155 4. The recall committee operates according to the same rules as the 1156 nominating committee with the qualification that there is no 1157 confirmation process. 1159 5. The recall committee investigates the circumstances of the 1160 justification for the recall and votes on its findings. 1162 The investigation must include at least both an opportunity for 1163 the member being recalled to present a written statement and 1164 consultation with third parties. 1166 6. A 3/4 majority of the members who vote on the question is 1167 required for a recall. 1169 7. If a sitting member is recalled the open position is to be filled 1170 according to the mid-term vacancy rules. 1172 8. Changes From RFC2727 1174 This section describes the substantive changes from RFC2727, listed 1175 approximately in the order in which they appear in the document. 1177 1. A section with definitions for words and phrases used throughout 1178 the document was inserted. 1180 2. The role of term limits as a selection criterion was clarified. 1182 3. The NOMCOM must now be provided with a brief description of the 1183 desirable set of qualifications for the candidate to be 1184 nominated for each position. 1186 4. Because of the overlapping terms of successive nominating 1187 committees, the specific committee responsible for a mid-term 1188 vacancy was specified. 1190 5. The characterization of the advice and consent model was revised 1191 to require the nominating committee and the confirming body to 1192 consult during the approval process. 1194 6. A general rule was added to define that all announcements are 1195 made with the usual IETF Secretariat mechanism. 1197 7. Details regarding the expected timeline of the selection and 1198 operation of the committee were made even more explicit. An 1199 Appendix was added that captures all the details for the 1200 convenience of the reader. 1202 8. The term of the nominating committee was extended to 1203 approximately 15 months such that it explicitly overlaps by 1204 approximately 3 months the next year's nominating committee's 1205 term. 1207 9. The terms voting member and non-voting member were replaced by 1208 voting volunteers, liaisons, and advisors. All members vote at 1209 all times except that the only voting volunteers vote on a 1210 candidate selection. 1212 10. The responsibilities of the Chair, liaisons, advisors, and 1213 voting volunteers is now explicitly stated. 1215 11. Processes for recalling members of the committee were added. 1217 12. Liaisons and advisors are no longer required to meet the usual 1218 requirements for nominating committee membership. 1220 13. The Internet Society Board of Trustees may appoint a non-voting 1221 liaison. 1223 14. The eligibility qualifications for the nominating committee was 1224 changed to require attendance at 3 out of 5 of the last five 1225 meetings, to require volunteers to submit identifying contact 1226 information, and to request that volunteers be familiar with 1227 IETF processes and procedures. 1229 15. Some additional clarification was added to the method used to 1230 select volunteers. 1232 16. The process for selecting the 10 voting volunteers had several 1233 clarifications and additional requirements added, including a 1234 challenge process and the requirement to disallow more than two 1235 volunteers with the same primary affiliation. 1237 17. Nominations for open positions should include both contact 1238 information and a description of the skills or expertise the 1239 nominator believes the nominee possesses. 1241 18. Nominees are requested to keep the nominating committee informed 1242 of changes in their contact information. Editorially, the 1243 distinction between a nominee and candidate was emphasized. 1245 19. A description of a testimony to be provided with each candidate 1246 to a confirming body by the nominating committee is specified. 1248 20. The rules regarding the announcement of confirmed candidates 1249 were substantially rewritten to make it easier to understand. 1251 21. The nominating committee is permitted to keep an archive for the 1252 duration of its term of the information it collects and produces 1253 for its own internal use. 1255 22. A dispute resolution process for addressing process concerns was 1256 added. 1258 23. The process for recalling a sitting member of the IAB and IESG 1259 requires at least 20 eligible members of the IETF community to 1260 sign a petition requesting the recall. 1262 24. The section on Security Considerations was expanded. 1264 25. Appendix A, Oral Tradition, has been added. 1266 26. Appendix B, Nominating Committee Timeline, has been added as a 1267 convenience to the reader. 1269 9. Acknowledgements 1271 There have been a number of people involved with the development of 1272 this document over the years as it has progressed from RFC2027 1273 through RFC2282 and RFC2727 to its current version. 1275 A great deal of credit goes to the first three Nominating Committee 1276 Chairs: 1278 1993 - Jeff Case 1280 1994 - Fred Baker 1282 1995 - John Curran 1284 who had the pleasure of operating without the benefit of a documented 1285 process. It was their fine work and oral tradition that became the 1286 first version of this document. 1288 Of course we can not overlook the bug discovery burden that each of 1289 the Chairs since the first publication have had to endure: 1291 1996 - Guy Almes 1293 1997 - Geoff Huston 1295 1998 - Mike St. Johns 1297 1999 - Donald Eastlake 1299 2000 - Avri Doria 1301 2001 - Bernard Adoba 1303 2002 - Ted T'so 1305 2003 - Phil Roberts 1307 Of course the bulk of the early credit goes to the members of the 1308 POISSON Working Group, previously the POISED Working Group. The 1309 prose here would not be what it is were it not for the attentive and 1310 insightful review of its members. Specific acknowledgement must be 1311 extended to Scott Bradner and John Klensin, who consistently 1312 contributed to the improvement of the first three versions of this 1313 document. 1315 In January 2002 a new working group was formed, the Nominating 1316 Committee Working Group (nomcom), to revise the RFC2727 version. 1318 This working group was guided by the efforts of a design team whose 1319 members were as follows: 1321 Bernard Adoba 1323 Harald Alvestrand - Chair of the IETF 1325 Leslie Daigle - Chair of the IAB 1327 Avri Doria - Chair of the Working Group 1329 James Galvin - Editor of the Document 1331 Joel Halpern 1333 Thomas Narten 1335 Special acknowledgement must be extended to Brian Carpenter and Mike 1336 St. Johns, who consistently contributed to the RFC2727 revision. 1338 10. Security Considerations 1340 Any selection, confirmation, or recall process necessarily involves 1341 investigation into the qualifications and activities of prospective 1342 candidates. The investigation may reveal confidential or otherwise 1343 private information about candidates to those participating in the 1344 process. Each person who participates in any aspect of the process 1345 must maintain the confidentiality of any and all information not 1346 explicitly identified as suitable for public dissemination. 1348 When the nominating committee decides it is necessary to share 1349 confidential or otherwise private information with others, the 1350 dissemination must be minimal and must include a prior commitment 1351 from all persons consulted to observe the same confidentiality rules 1352 as the nominating committee itself. 1354 References 1356 [1] Eastlake, D., "Publicly Verifiable Nomcom Random Selection", RFC 1357 2777, February 2000. 1359 [2] Galvin, J., "IAB and IESG Selection, Confirmation, and Recall 1360 Process: Operation of the Nominating and Recall Committees", BCP 1361 10, RFC 2727, February 2000. 1363 [3] Galvin, J., "IAB and IESG Selection, Confirmation, and Recall 1364 Process: Operation of the Nominating and Recall Committees", BCP 1365 10, RFC 2282, February 1998. 1367 Author's Address 1369 James M. Galvin 1370 eList eXpress LLC 1371 607 Trixsam Road 1372 Sykesville, MD 21784 1373 US 1375 Phone: +1 410-549-4619 1376 Fax: +1 410-795-7978 1377 EMail: galvin+ietf@elistx.com 1378 URI: http://www.elistx.com/ 1380 Appendix A. Oral Tradition 1382 Over the years various nominating committees have learned through 1383 oral tradition passed on by liaisons that there are certain 1384 consistencies in the process and information considered during 1385 deliberations. Some items from that oral tradition are collected 1386 here to facilitate its consideration by future nominating committees. 1388 1. It has been found that experience as an IETF Working Group Chair 1389 or an IRTF Research Group Chair is helpful in giving a nominee 1390 experience of what the job of an Area Director involves. It is 1391 also helps a nominating committee judge the technical, people, 1392 and process management skills of the nominee. 1394 2. No person should ever be nominated to serve on both the IESG and 1395 the IAB concurrently; this does not apply to the IETF Chair who 1396 serves on both bodies by definition. 1398 3. The strength of the IAB is found in part in the balance of the 1399 demographics of its members (e.g., national distribution, years 1400 of experience, gender, etc.), the combined skill set of its 1401 members, and the combined sectors (e.g., industry, academia, 1402 etc.) represented by its members. 1404 4. There are no term limits explicitly because the issue of 1405 continuity versus turnover should be evaluated each year 1406 according to the expectations of the IETF community, as it is 1407 understood by each nominating committee. 1409 5. The number of nominating committee members with the same primary 1410 affiliation is limited in order to avoid the appearance of 1411 improper bias in choosing the leadership of the IETF. Rather 1412 than defining precise rules for how to define "affiliation," the 1413 IETF community depends on the honor and integrity of the 1414 participants to make the process work. 1416 Appendix B. Nominating Committee Timeline 1418 This appendix is included for the convenience of the reader and is 1419 not to be interpreted as the definitive timeline. It is intended to 1420 capture the detail described elsewhere in this document in one place. 1421 Although every effort has been made to ensure the description here is 1422 consistent with the description elsewhere, if there are any conflicts 1423 the definitive rule is the one in the main body of this document. 1425 The only absolute in the timeline rules for the annual process is 1426 that it must be completed by the First IETF of the year after the 1427 nominating committee begins its term. This is supported by the fact 1428 that the confirmed candidate terms begin during the week of the First 1429 IETF. 1431 The overall annual process is designed to be completed in 7 months. 1432 It is expected to start 8 months prior to the First IETF. The 7 1433 months is split between three major components of the process as 1434 follows. 1436 1. First is the selection and organization of the committee members. 1437 Three months are allotted for this process. 1439 2. Second is the selection of the candidates by the nominating 1440 committee. Three months are allotted for this process. 1442 3. Third is the confirmation of the candidates by their respective 1443 confirming bodies. One month is allotted for this process 1445 The following figure captures the details of the milestones within 1446 each component. For illustrative purposes the figure presumes the 1447 Friday before the First IETF is March 1. 1449 0. BEGIN 8 Months Prior to First IETF (approx. July 1); Internet 1450 Society President appoints the Chair. The appointment must be 1451 done no later than the Second IETF or 8 months prior to the First 1452 IETF, whichever comes first. The Chair must be announced and 1453 recognized during a plenary session of the Second IETF. 1455 1. The Chair establishes and announces milestones to ensure the 1456 timely selection of the nominating committee members. 1458 2. The Chair contacts the IESG, IAB, and Internet Society Board of 1459 Trustees and requests a liaison. The Chair contacts the prior 1460 year's Chair and requests an advisor. The Chair obtains the list 1461 of IESG and IAB open positions and descriptions from the IETF 1462 Executive Director. 1464 3. The Chair announces the solicitation for voting volunteer members 1465 that must remain open for at least 30 days. The announcement must 1466 be done no later than 7 months and 2 weeks prior to the First IETF 1467 (approx. July 15). 1469 4. After the solicitation closes the Chair announces the pool of 1470 volunteers and the date of the random selection, which must be at 1471 least 1 week in the future. The announcement must be done no 1472 later than 6 months and 2 weeks prior to the First IETF 1473 (approx. August 15). 1475 5. On the appointed day the random selection occurs and the Chair 1476 announces the members of the committee and the 1 week challenge 1477 period. The announcement must be done no later than 6 months and 1478 1 week prior to the First IETF (approx. August 22). 1480 6. During the challenge period the Chair contacts each of the 1481 committee members and confirms their availability to participate. 1483 7. After the challenge period closes the Chair announces the members of 1484 the committee and its term begins. The announcement must be done no 1485 later than 6 months prior to the First IETF (approx. September 1). 1487 8. The committee has one month during which it is to self-organize in 1488 preparation for completing its assigned duties. This must be done no 1489 later than 5 months prior to the First IETF (approx. October 1). 1491 9. END the Committee Member Selection Process; BEGIN the Selection of 1492 Candidates; Time is at least 5 months prior to the First IETF 1493 (approx. October 1). 1495 10. The Chair establishes and announces the milestones to ensure the 1496 timely selection of the candidates, including a call for 1497 nominations for the open positions. The announcement must be done 1498 no later than 5 months prior to the First IETF (approx. October 1499 1). 1501 11. Over the next 3 months the nominating committee collects input 1502 and deliberates. It should plan to conduct interviews and other 1503 consultations during the Third IETF. The committee must complete 1504 its candidate selection no later than 2 months prior to the First 1505 IETF (approx. January 1). 1507 12. END the Selection of Candidates; BEGIN the Confirmation of 1508 Candidates; Time is at least 2 months prior to the First IETF 1509 (approx. January 1); 1511 13. The committee presents its candidates to their respective confirming 1512 bodies. The presentation must be done no later than 2 months prior 1513 to the First IETF (approx. January 1). 1515 14. The confirming bodies have 1 month to deliberate and, in 1516 consultation with the nominating committee, accept or reject 1517 candidates. 1519 15. The Chair announces the confirmed candidates. The announcement 1520 must be done no later than 1 month prior to the First IETF 1521 (approx. February 1). 1523 Figure 1: The Timeline 1525 Intellectual Property Statement 1527 The IETF takes no position regarding the validity or scope of any 1528 intellectual property or other rights that might be claimed to 1529 pertain to the implementation or use of the technology described in 1530 this document or the extent to which any license under such rights 1531 might or might not be available; neither does it represent that it 1532 has made any effort to identify any such rights. Information on the 1533 IETF's procedures with respect to rights in standards-track and 1534 standards-related documentation can be found in BCP-11. Copies of 1535 claims of rights made available for publication and any assurances of 1536 licenses to be made available, or the result of an attempt made to 1537 obtain a general license or permission for the use of such 1538 proprietary rights by implementors or users of this specification can 1539 be obtained from the IETF Secretariat. 1541 The IETF invites any interested party to bring to its attention any 1542 copyrights, patents or patent applications, or other proprietary 1543 rights which may cover technology that may be required to practice 1544 this standard. Please address the information to the IETF Executive 1545 Director. 1547 Full Copyright Statement 1549 Copyright (C) The Internet Society (2003). All Rights Reserved. 1551 This document and translations of it may be copied and furnished to 1552 others, and derivative works that comment on or otherwise explain it 1553 or assist in its implementation may be prepared, copied, published 1554 and distributed, in whole or in part, without restriction of any 1555 kind, provided that the above copyright notice and this paragraph are 1556 included on all such copies and derivative works. However, this 1557 document itself may not be modified in any way, such as by removing 1558 the copyright notice or references to the Internet Society or other 1559 Internet organizations, except as needed for the purpose of 1560 developing Internet standards in which case the procedures for 1561 copyrights defined in the Internet Standards process must be 1562 followed, or as required to translate it into languages other than 1563 English. 1565 The limited permissions granted above are perpetual and will not be 1566 revoked by the Internet Society or its successors or assignees. 1568 This document and the information contained herein is provided on an 1569 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1570 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1571 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1572 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1573 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1575 Acknowledgement 1577 Funding for the RFC Editor function is currently provided by the 1578 Internet Society.