Presentation is loading. Please wait.

Presentation is loading. Please wait.

NomCom WG IETF58 Minneapolis. Agenda Agenda Review Review of changes made in draft-ietf-nomcom-2727bis-08.txt Review of proposals for closing open issues.

Similar presentations


Presentation on theme: "NomCom WG IETF58 Minneapolis. Agenda Agenda Review Review of changes made in draft-ietf-nomcom-2727bis-08.txt Review of proposals for closing open issues."— Presentation transcript:

1 NomCom WG IETF58 Minneapolis

2 Agenda Agenda Review Review of changes made in draft-ietf-nomcom-2727bis-08.txt Review of proposals for closing open issues Discussion of issue of when 2727bis becomes normative

3 Open Issues 1. Release of Qualification Statements 2. NomCom cause Mid-term Vacancies 3. Liaison initiation of problem resolution process 10. NomCom Member recall 17. Must or Should for Completion of NomCom Process 24. Term changeover timing for IAB

4 1. Release of Qualification Statements Old Text: The Chair obtains the list of IESG and IAB positions to be reviewed and a description of the desirable qualifications for those positions. This information is announced, along with a solicitation for names of volunteers from the IETF community willing to serve on the nominating committee.

5 1. Release of Qualification Statements New Text: The Chair obtains the list of IESG and IAB positions to be reviewed and a description of the desirable qualifications for those positions. This information is announced on ietf-announce@ietf.org, along with a solicitation for names of volunteers from the IETF community willing to serve on the nominating committee. The description of desirable qualifications is used as input but the NomCom is charged with determining the qualifications for all positions and is charged, as documented elsewhere in this document, for documenting its choice criteria when announcing the confirmed candidates.

6 1. Release of Qualification Statements Open question  Should it be during announcement as opposed to during solicitation

7 2. NomCom caused Mid-term Vacancies Insert into section 3 "Nomcom-caused Mid-term Vacancies: From time to time the Nomcom may propose moving a serving Area Director or IAB member from one position to another. (E.g. moving a Transport AD to cover O&M). If the serving member is at the end of their normal term there is no change in procedures. Otherwise, this is treated as a mid-term vacancy and mid-term procedures are used with the following exceptions:

8 2. NomCom caused Mid-term Vacancies Insert into section 3 (Cont’d) a) If the vacancy, during the annual NomCom selection process, will occur on the IAB due to a move from the IAB to the IESG, the NomCom may, upon confirmation of nominee/IAB member, submit for confirmation as part of the normal slate of candidates another nominee to complete the term of the departing IAB member. If the Nomcom declines to nominate a replacement as part of the annual process, the IAB may, at anytime after the confirmation of the departing member, ask the NomCom to fill the slot using mid-term procedures.

9 2. NomCom caused Mid-term Vacancies Insert into section 3 (cont’d) b) If the vacancy will occur on the IESG, either as a move to another IESG slot or as a move to the IAB, or on the IAB, when filling a midterm vacancy outside of the annual process, the NomCom must use mid-term procedure rules. Most importantly, they must advertise the vacancy, and must consider all new candidates as equitably as any previously considered. The NomCom is explicitly barred from proceeding without an explicit request from the IETF Executive Director. The term of the nominee shall be for the remainder of the term of the vacated position."

10 3. Liaison initiation of Problem Resolution Process Old Text Liaisons from the IESG, IAB, and Internet Society Board of Trustees (if one was appointed) are expected to review the operation and executing process of the nominating committee and to report any concerns or issues to the Chair of the nominating committee immediately. If they can not resolve the issue between themselves, liaisons must report the issue to their respective bodies. If their respective body agrees that there is an issue the liaison must report it according to the dispute resolution process stated elsewhere in this document.

11 3. Liaison initiation of Problem Resolution Process New Text Liaisons from the IESG, IAB, and Internet Society Board of Trustees (if one was appointed) are expected to review the operation and executing process of the nominating committee and to report any concerns or issues to the Chair of the nominating committee immediately. If the Chair in consultation with a sub- group composed of the liaisons cannot resolve the issue, then the Chair must report it according to the dispute resolution process stated elsewhere in this document.

12 10. NomCom Member recall Old Text Regardless of the circumstances, if individual committee members can not work out their differences between themselves, the entire committee may be called upon to discuss and review the circumstances. If a resolution is not forthcoming a vote may be conducted. A member may recalled if at least a quorum of all committee members agree, including the vote of the member being recalled.

13 10. NomCom Member recall New Text Regardless of the circumstances, if individual committee members can not work out their differences between themselves, the entire committee may be called upon to discuss and review the circumstances. If a resolution is not forthcoming a vote may be conducted. A member may recalled if 2/3 of all committee members agree to the recall

14 17. Must or Should for Completion Timing Old Text The confirmation process must be completed at least one month prior to the First IETF. question of changing the must to should Proposal: Leave text as is.

15 24. Term changeover timing for IAB OLD: All confirmed candidate terms begin during the First IETF meeting corresponding to the beginning of the term for which they were confirmed. Normally, the confirmed candidate's term begins when the currently sitting member's term ends on the last day of the meeting. A term may begin or end no sooner than the first day of the meeting and no later than the last day of the meeting as determined by the mutual agreement of the currently sitting member and the confirmed candidate. The confirmed candidate's term may overlap the sitting member's term during the meeting as determined by their mutual agreement.

16 24. Term changeover timing for IAB New: All confirmed candidate terms begin during the First IETF meeting corresponding to the beginning of the term for which they were confirmed. Normally, the confirmed IESG candidate's term begins when the currently sitting member's term ends on the last day of the meeting. An IESG term may begin or end no sooner than the first day of the meeting and no later than the last day of the meeting as determined by the mutual agreement of the currently sitting member and the confirmed candidate. The confirmed IESG candidate's term may overlap the sitting member's term during the meeting as determined by their mutual agreement. For IAB candidates, the term begins on the first day of the meeting overlapping the period of the meeting with any sitting member of the IAB whose term expires with the end of the meeting.

17 When does 2727bis become normative Proposal  Becomes normative once IESG approves it and ISOC accepts it.  Current NomCom is free to use either the current BCP or the 2727bis for any current process where it does not conflict with the old BCP, but should use the new process for any new vacancies announced after the document becomes normative.


Download ppt "NomCom WG IETF58 Minneapolis. Agenda Agenda Review Review of changes made in draft-ietf-nomcom-2727bis-08.txt Review of proposals for closing open issues."

Similar presentations


Ads by Google