Network Working Group S. Dawkins, Ed. Internet-Draft Huawei (USA) Updates: 3777 (if approved) February 20, 2009 Intended status: BCP Expires: August 24, 2009 Nominating Committee Process: Earlier Announcement of Open Positions and Solicitation of Volunteers draft-dawkins-nomcom-dont-wait-00 Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on August 24, 2009. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Dawkins Expires August 24, 2009 [Page 1]
Internet-Draft NomCom Issues February 2009 Abstract This document updates RFC 3777, Section 4, Bullet 13 to allow announcement of open positions and solicitation of volunteers to be issued before a Nominating and Recall Committee Chair has been named by the Internet Society President. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Background of this document . . . . . . . . . . . . . . . . . . 3 3. Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Updated text from RFC 3777 . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 7.2. Informative References . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 Dawkins Expires August 24, 2009 [Page 2]
Internet-Draft NomCom Issues February 2009 1. Introduction The Internet Engineering Steering Group (IESG), the Internet Architecture Board (IAB), and at-large IETF representatives to the IETF Administrative Oversight Committee (IAOC) are selected by a "Nominating and Recall Committee" (universally abbreviated as "NomCom"). [RFC3777] defines how the NomCom is selected, and the processes it follows as it selects candidates for these positions. This document describes an issue with [RFC3777] that has arisen in practice, and proposes a normative update to resolve the issue. 2. Background of this document [RFC3777] is the latest in a series of revisions to the NomCom process. [RFC3777] has been updated once since 2004, but this update ([RFC5078] did not change normative text (it replaced a sample timeline). [RFC5078] identified a serial delay in the process described in [RFC3777], in section 4, "Nominating Committee Selection", bullet 13, which states: The Chair obtains the list of IESG and IAB positions to be reviewed and announces it along with a solicitation for names of volunteers from the IETF community willing to serve on the nominating committee. The solicitation must permit the community at least 30 days during which they may choose to volunteer to be selected for the nominating committee. The list of open positions is published with the solicitation to facilitate community members choosing between volunteering for an open position and volunteering for the nominating committee. The result is that the Chair is the only person who can announce the list of open positions and solicitation for names of volunteers, a process that requires 30 days for public solicitation. Since this is the first step in organizing the NomCom committee, delays in selecting a NomCom Chair translate directly into delays in issuing the solicitation and organizing the NomCom. This proved problematic in practice in 2008-2009, when Joel Halpern was named NomCom Chair less than 30 days prior to the Second IETF meeting. If the 30-day solicitation had already taken place, Joel Dawkins Expires August 24, 2009 [Page 3]
Internet-Draft NomCom Issues February 2009 could have organized the NomCom at the Second IETF meeting, face to face, but since the required 30-day solicitation didn't start until Joel was named, Joel was forced to organize the NomCom by e-mail and conference call. It is desirable to allow the solicitation and announcement to take place in a timely manner so that when a NomCom Chair IS named, the NomCom Chair can immediately announce the source of selection randomness and quickly select voting volunteer members of the NomCom. 3. Discussion This document proposes that the Past NomCom Chair, not the current NomCom Chair, will issue the announcement of open positions and the solicitation for names of volunteers on behalf of the NomCom Chair who will be named by the ISOC President. This allows the search for NomCom Chair and volunteers to proceed in parallel. The Past NomCom Chair is already a trusted part of the NomCom process, and will be serving on the upcoming NomCom as advisor to the current Chair, so no additional trust or confidentiality issues apply. This process change covers only the announcement of open positions and the solicitation for names of volunteers. The announcement of the pool of volunteers and the source of randomness used to select voting volunteers is still the responsibility of the current Chair. The goal of this process change is not to allow a NomCom to proceed without a current Chair, it is only to ensure that a current Chair can begin organizing the NomCom without an avoidable delay, and can use face-to-face time at the Second IETF meeting effectively for this purpose. 4. Updated text from RFC 3777 For [RFC3777], in section 4, "Nominating Committee Selection", bullet 13, which states: The Chair obtains the list of IESG and IAB positions to be reviewed and announces it along with a solicitation for names of volunteers from the IETF community willing to serve on the nominating committee. this text is replaced with the following text: Dawkins Expires August 24, 2009 [Page 4]
Internet-Draft NomCom Issues February 2009 The Past NomCom Chair obtains the list of IESG and IAB positions to be reviewed and announces it along with a solicitation for names of volunteers from the IETF community willing to serve on the nominating committee. 5. Security Considerations This specification describes issues with the current IETF Nominating Committee process ([RFC3777]) and proposes an update to avoid a serial delay. No security considerations apply. 6. IANA Considerations No IANA actions are requested in this specification. 7. References 7.1. Normative References [RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees", BCP 10, RFC 3777, June 2004. 7.2. Informative References [RFC5078] Dawkins, S., "IAB and IESG Selection, Confirmation, and Recall Process: Revision of the Nominating and Recall Committees Timeline", RFC 5078, October 2007. Author's Address Spencer Dawkins (editor) Huawei Technologies (USA) Phone: +1 214 755 3870 Email: spencer@wonderhamster.org Dawkins Expires August 24, 2009 [Page 5]
