idnits 2.17.1 draft-leiba-3777upd-eligibility-02.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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC3777, but the abstract doesn't seem to directly say this. It does mention RFC3777 though, so this could be OK. 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 (August 18, 2012) is 4262 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) -- Looks like a reference, but probably isn't: '1' on line 219 ** Obsolete normative reference: RFC 3777 (Obsoleted by RFC 7437) -- Obsolete informational reference (is this intentional?): RFC 4333 (Obsoleted by RFC 8711) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group B. Leiba 3 Internet-Draft Huawei Technologies 4 Updates: 3777 (if approved) S. Moonesamy 5 Intended status: BCP August 18, 2012 6 Expires: February 19, 2013 8 Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF 9 Leadership 10 draft-leiba-3777upd-eligibility-02 12 Abstract 14 RFC 3777 specifies that "sitting members" of the IAB and IESG "may 15 not volunteer to serve on the nominating commitee". Since that 16 document was written the IAOC was formed, and that body is not 17 covered by RFC 3777. There is also uncertainty about whether ex- 18 officio members and liaisons are included as "sitting members". This 19 document clarifies those situations. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on February 19, 2013. 38 Copyright Notice 40 Copyright (c) 2012 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Addition of the IAOC to the Text of RFC 3777 . . . . . . . . 4 59 3. Security Considerations . . . . . . . . . . . . . . . . . . . 6 61 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 63 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 64 5.1. Normative References . . . . . . . . . . . . . . . . . . . . 6 65 5.2. Informative References . . . . . . . . . . . . . . . . . . . 6 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 7 69 1. Introduction 71 The "Operation of the Nominating and Recall Committees" document 72 [RFC3777] defines the nominating committee (NomCom) process. One of 73 the key points in the process and in the selection of the NomCom is 74 that the IETF wants to avoid having its top leadership be self- 75 selecting: the leaders should not be the ones who choose the leaders. 76 The selection of the NomCom, therefore, excludes those individuals 77 who are in top leadership positions currently. 79 That said, it would be bad to eliminate people who have the 80 experience necessary to understand of the IETF process: those 81 individuals can bring a broader perspective to the NomCom and will 82 help ensure that the people it selects for the leadership positions 83 are better prepared to fulfill the roles. 85 RFC 3777 specifies that "sitting members" of the IAB and IESG "may 86 not volunteer to serve on the nominating committee". Since that 87 document was written the IETF Administrative Oversight Committee 88 (IAOC) was formed, and that body is not covered by RFC 3777. There 89 is also uncertainty about whether ex-officio members liaisons, and 90 such are included as "sitting members". This document clarifies 91 those situations, with the understanding that the intent of RFC 3777 92 was to exclude those currently in IETF leadership positions, or who 93 would otherwise have a conflict of interest, from voting on the 94 selection of the new leadership. 96 This document also excludes certain individuals who are directly paid 97 for their work with the IETF, and who, therefore, have a direct 98 personal financial incentive in the selection of the leadership 99 boards. We limit this exclusion to a few people who are paid for 100 long-term full-time work. In practice, they are unlikely to 101 volunteer for the NomCom anyway, so this addition makes little 102 practical change. 104 In order to allow the largest reasonable list of potential NomCom 105 members, we do not want to exclude those at lower levels of IETF 106 leadership. In particular, this document does *not* exclude 107 participation from working group chairs, IRTF research group chairs, 108 members of directorates and special review teams, and members of 109 other advisory bodies. 110 [[anchor1: Some had suggested eliminating the RFC Series Oversight 111 Committee (RSOC) members, for example; we do not think that is a good 112 idea.]] 114 2. Addition of the IAOC to the Text of RFC 3777 116 RFC 3777 specifies processes involving the IAB and the IESG in a 117 number of places. For some of those situations, the "IAOC Member 118 Selection Guidelines and Process" document [RFC4333] covers what's 119 needed for the IAOC. This document makes the following updates to 120 add the IAOC to certain of the processes that are not covered there. 122 Note that the change below to Section 4, bullet 15 also puts 123 additional restrictions on who may volunteer as a voting member of 124 the NomCom. 126 Section 2 ("Definitions") is updated as follows: 128 o Paragraphs 5 and 6 are replaced by this: 130 nominee: A person who is being or has been considered for one or 131 more open positions of the IESG, the IAB, or the IAOC. 133 sitting member: A person who is currently serving a term of 134 membership in, and having a standing to participate in the 135 decisions of, the IESG, the IAB, the IAOC, or the ISOC Board of 136 Trustees. Liaisons from other bodies are not sitting members 137 by this definition. (For example, an IESG liaison to the IAB 138 is not a sitting member of the IAB, though that person may be a 139 sitting member of the IESG.) 141 Section 3 ("General") is updated as follows: 143 o Bullet 7, sub-bullet 1 is replaced by this: 145 The IETF Executive Director informs the nominating committee of 146 the IESG, IAB, and IAOC positions to be reviewed. 148 The IESG, the IAB, and the IAOC are responsible for providing 149 summary of the expertise desired of the candidates selected for 150 their respective open positions to the Executive Director. The 151 summaries are provided to the nominating committee for its 152 consideration. 154 o In bullet 7, sub-bullet 3, the following is inserted between 155 paragraphs 3 and 4: 157 The sitting IESG members review the IAOC candidate. 159 Section 4 ("Nominating Committee Selection") is updated as follows: 161 o Bullet 3, paragraph 1 is replaced by this: 163 The nominating committee comprises a Chair, ten voting 164 volunteers, the immediate past nominating committee Chair (or 165 alternate; see below) as an advisor, plus liaisons and possible 166 additional advisor(s) as described herein. 168 o Bullet 3, paragraph 6 is replaced by this: 170 The IESG, IAB, and IAOC liaisons are selected according to 171 rules stated elsewhere in this document. 173 o Bullet 7, paragraph 3 is replaced by this: 175 Liaisons from the IESG, the IAB, and the IAOC are expected to 176 provide information to the nominating committee regarding the 177 operation, responsibility, and composition of their respective 178 bodies. 180 o Bullet 7, paragraph 5 is replaced by this: 182 Liaisons from the IESG, the IAB, the IAOC, and the Internet 183 Society Board of Trustees (if one was appointed) are expected 184 to review the operation and executing process of the nominating 185 committee and to report any concerns or issues to the Chair of 186 the nominating committee immediately. If they can not resolve 187 the issue between themselves, liaisons must report it according 188 to the dispute resolution process stated elsewhere in this 189 document. 191 o Bullet 8, only paragraph is replaced by this: 193 For each of the IAB, the IESG, and the IAOC, the sitting 194 members appoint a liaison from their current membership, 195 someone who is not sitting in an open position, to serve on the 196 nominating committee. 198 o Bullet 13, paragraph 1 is replaced by this: 200 The Chair obtains the list of IESG, IAB, and IAOC positions to 201 be reviewed and announces it along with a solicitation for 202 names of volunteers from the IETF community willing to serve on 203 the nominating committee. 205 o Bullet 15 is replaced by these two bullets: 207 15.1. Members of the Internet Society Board of Trustees and 208 sitting members of the IAB, the IESG, and the IAOC, including 209 members in ex-officio positions, may not volunteer to serve 210 as voting members of the nominating committee. 212 15.2. People serving in the IETF Secretariat and the RFC Editor 213 may not volunteer to serve as voting members of the 214 nominating committee. 216 o In bullet 16, to correct an erratum, the last paragraph is 217 replaced by this: 219 One possible selection method is described in RFC 3797 [1]. 221 Section 5 ("Nominating Committee Operation") is updated as follows: 223 o In bullet 11, the last paragraph is replaced by this: 225 Members of the IETF community who were recalled from any 226 nominating-committee-appointed leadership position during the 227 previous two years are not eligible to be considered for 228 filling any open position. 230 3. Security Considerations 232 This is a procedural document, and is entirely unrelated to security. 234 4. IANA Considerations 236 No IANA actions are requested by this document, and the RFC Editor is 237 asked to remove this section before publication. 239 5. References 241 5.1. Normative References 243 [RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and 244 Recall Process: Operation of the Nominating and Recall 245 Committees", BCP 10, RFC 3777, June 2004. 247 5.2. Informative References 249 [RFC4333] Huston, G. and B. Wijnen, "The IETF Administrative 250 Oversight Committee (IAOC) Member Selection Guidelines and 251 Process", BCP 113, RFC 4333, December 2005. 253 Authors' Addresses 255 Barry Leiba 256 Huawei Technologies 258 Phone: +1 646 827 0648 259 Email: barryleiba@computer.org 260 URI: http://internetmessagingtechnology.org/ 262 S. Moonesamy 263 76, Ylang Ylang Avenue 264 Quatres Bornes 265 Mauritius 267 Email: sm+ietf@elandsys.com