idnits 2.17.1 draft-dawkins-nomcom-dont-wait-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC3777, updated by this document, for RFC5378 checks: 2002-06-24) -- 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 20, 2009) is 5537 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 3777 (Obsoleted by RFC 7437) -- Obsolete informational reference (is this intentional?): RFC 5078 (Obsoleted by RFC 7437) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. Dawkins, Ed. 3 Internet-Draft Huawei (USA) 4 Updates: 3777 (if approved) February 20, 2009 5 Intended status: BCP 6 Expires: August 24, 2009 8 Nominating Committee Process: Earlier Announcement of Open Positions and 9 Solicitation of Volunteers 10 draft-dawkins-nomcom-dont-wait-00 12 Status of this Memo 14 This Internet-Draft is submitted to IETF in full conformance with the 15 provisions of BCP 78 and BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on August 24, 2009. 35 Copyright Notice 37 Copyright (c) 2009 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. 47 Abstract 49 This document updates RFC 3777, Section 4, Bullet 13 to allow 50 announcement of open positions and solicitation of volunteers to be 51 issued before a Nominating and Recall Committee Chair has been named 52 by the Internet Society President. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Background of this document . . . . . . . . . . . . . . . . . . 3 58 3. Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 4. Updated text from RFC 3777 . . . . . . . . . . . . . . . . . . 4 60 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 61 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 62 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 64 7.2. Informative References . . . . . . . . . . . . . . . . . . 5 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 67 1. Introduction 69 The Internet Engineering Steering Group (IESG), the Internet 70 Architecture Board (IAB), and at-large IETF representatives to the 71 IETF Administrative Oversight Committee (IAOC) are selected by a 72 "Nominating and Recall Committee" (universally abbreviated as 73 "NomCom"). [RFC3777] defines how the NomCom is selected, and the 74 processes it follows as it selects candidates for these positions. 76 This document describes an issue with [RFC3777] that has arisen in 77 practice, and proposes a normative update to resolve the issue. 79 2. Background of this document 81 [RFC3777] is the latest in a series of revisions to the NomCom 82 process. [RFC3777] has been updated once since 2004, but this update 83 ([RFC5078] did not change normative text (it replaced a sample 84 timeline). 86 [RFC5078] identified a serial delay in the process described in 87 [RFC3777], in section 4, "Nominating Committee Selection", bullet 13, 88 which states: 90 The Chair obtains the list of IESG and IAB positions to be 91 reviewed and announces it along with a solicitation for names of 92 volunteers from the IETF community willing to serve on the 93 nominating committee. 95 The solicitation must permit the community at least 30 days during 96 which they may choose to volunteer to be selected for the 97 nominating committee. 99 The list of open positions is published with the solicitation to 100 facilitate community members choosing between volunteering for an 101 open position and volunteering for the nominating committee. 103 The result is that the Chair is the only person who can announce the 104 list of open positions and solicitation for names of volunteers, a 105 process that requires 30 days for public solicitation. 107 Since this is the first step in organizing the NomCom committee, 108 delays in selecting a NomCom Chair translate directly into delays in 109 issuing the solicitation and organizing the NomCom. 111 This proved problematic in practice in 2008-2009, when Joel Halpern 112 was named NomCom Chair less than 30 days prior to the Second IETF 113 meeting. If the 30-day solicitation had already taken place, Joel 114 could have organized the NomCom at the Second IETF meeting, face to 115 face, but since the required 30-day solicitation didn't start until 116 Joel was named, Joel was forced to organize the NomCom by e-mail and 117 conference call. 119 It is desirable to allow the solicitation and announcement to take 120 place in a timely manner so that when a NomCom Chair IS named, the 121 NomCom Chair can immediately announce the source of selection 122 randomness and quickly select voting volunteer members of the NomCom. 124 3. Discussion 126 This document proposes that the Past NomCom Chair, not the current 127 NomCom Chair, will issue the announcement of open positions and the 128 solicitation for names of volunteers on behalf of the NomCom Chair 129 who will be named by the ISOC President. This allows the search for 130 NomCom Chair and volunteers to proceed in parallel. 132 The Past NomCom Chair is already a trusted part of the NomCom 133 process, and will be serving on the upcoming NomCom as advisor to the 134 current Chair, so no additional trust or confidentiality issues 135 apply. 137 This process change covers only the announcement of open positions 138 and the solicitation for names of volunteers. The announcement of 139 the pool of volunteers and the source of randomness used to select 140 voting volunteers is still the responsibility of the current Chair. 141 The goal of this process change is not to allow a NomCom to proceed 142 without a current Chair, it is only to ensure that a current Chair 143 can begin organizing the NomCom without an avoidable delay, and can 144 use face-to-face time at the Second IETF meeting effectively for this 145 purpose. 147 4. Updated text from RFC 3777 149 For [RFC3777], in section 4, "Nominating Committee Selection", bullet 150 13, which states: 152 The Chair obtains the list of IESG and IAB positions to be 153 reviewed and announces it along with a solicitation for names of 154 volunteers from the IETF community willing to serve on the 155 nominating committee. 157 this text is replaced with the following text: 159 The Past NomCom Chair obtains the list of IESG and IAB positions 160 to be reviewed and announces it along with a solicitation for 161 names of volunteers from the IETF community willing to serve on 162 the nominating committee. 164 5. Security Considerations 166 This specification describes issues with the current IETF Nominating 167 Committee process ([RFC3777]) and proposes an update to avoid a 168 serial delay. No security considerations apply. 170 6. IANA Considerations 172 No IANA actions are requested in this specification. 174 7. References 176 7.1. Normative References 178 [RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and 179 Recall Process: Operation of the Nominating and Recall 180 Committees", BCP 10, RFC 3777, June 2004. 182 7.2. Informative References 184 [RFC5078] Dawkins, S., "IAB and IESG Selection, Confirmation, and 185 Recall Process: Revision of the Nominating and Recall 186 Committees Timeline", RFC 5078, October 2007. 188 Author's Address 190 Spencer Dawkins (editor) 191 Huawei Technologies (USA) 193 Phone: +1 214 755 3870 194 Email: spencer@wonderhamster.org