idnits 2.17.1 draft-leiba-3777upd-eligibility-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 : ---------------------------------------------------------------------------- -- 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 (July 30, 2012) is 4288 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) 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 B. Leiba 3 Internet-Draft Huawei Technologies 4 Updates: 3777 (if approved) July 30, 2012 5 Intended status: BCP 6 Expires: January 31, 2013 8 Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF 9 Leadership 10 draft-leiba-3777upd-eligibility-00 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 January 31, 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. Replacement of RFC 3777, Section 4, Paragraph 15 . . . . . . . 3 59 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 61 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 63 5. Normative References . . . . . . . . . . . . . . . . . . . . . 4 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 4 67 1. Introduction 69 RFC 3777 [RFC3777] defines the nominating committee process. One of 70 the key points in the process and in the selection of the NomCom is 71 that the IETF wants to avoid having its top leadership be self- 72 selecting: the leaders should not be the ones who choose the leaders. 73 The selection of the NomCom, therefore, excludes those individuals 74 who are in top leadership positions currently. 76 That said, it would be bad to eliminate too many people who are in 77 good positions to understand well the IETF process -- those 78 individuals will give important perspective to the NomCom and will 79 help ensure that the people it selects for the leadership roles will 80 be qualified to do those jobs. There's an advantage, then, to 81 excluding only those necessary to achieve the "not self-selecting" 82 goal, and no others. 84 RFC 3777 specifies that "sitting members" of the IAB and IESG "may 85 not volunteer to serve on the nominating committee". Since that 86 document was written the IAOC was formed, and that body is not 87 covered by RFC 3777. There is also uncertainty about whether ex- 88 officio members liaisons, and such are included as "sitting members". 89 This document clarifies those situations, with the understanding that 90 the intent of RFC 3777 was to exclude those currently in IETF 91 leadership positions, or who would otherwise have a conflict of 92 interest, from voting on the selection of the new leadership. 94 This document also excludes individuals who are directly paid for 95 their work with the IETF, and who, therefore, have a direct personal 96 financial incentive in the selection of the leadership boards. In 97 practice, those people are unlikely to volunteer for the NomCom 98 anyway, so this addition makes little practical change. 100 In order to allow the largest reasonable list of potential NomCom 101 members, we do not want to exclude those at lower levels of IETF 102 leadership. In particular, this document does *not* exclude 103 participation from working group chairs, IRTF research group chairs, 104 members of directorates and special review teams, and members of 105 other advisory bodies such as the RSOC. 107 2. Replacement of RFC 3777, Section 4, Paragraph 15 109 The following two paragraphs replace RFC 3777, Section 4, paragraph 110 15 in its entirety. 112 15.1 Members of the Internet Society Board of Trustees and sitting 113 members of the IAB, the IESG, and the IAOC, including members in ex- 114 officio positions, and not including liaisons, may not volunteer to 115 serve as voting members of the nominating committee. 117 15.2 People serving in the Secretariat and the RFC Editor may not 118 volunteer to serve as voting members of the nominating committee. 120 3. Security Considerations 122 This is a procedural document, and is entirely unrelated to security. 124 4. IANA Considerations 126 No IANA actions are requested by this document, and the RFC Editor is 127 asked to remove this section before publication. 129 5. Normative References 131 [RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and 132 Recall Process: Operation of the Nominating and Recall 133 Committees", BCP 10, RFC 3777, June 2004. 135 Author's Address 137 Barry Leiba 138 Huawei Technologies 140 Phone: +1 646 827 0648 141 Email: barryleiba@computer.org 142 URI: http://internetmessagingtechnology.org/