idnits 2.17.1 draft-leiba-3777upd-eligibility-05.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 (October 28, 2012) is 4196 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 4071 (Obsoleted by RFC 8711) 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) October 28, 2012 5 Intended status: BCP 6 Expires: May 1, 2013 8 Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF 9 Leadership 10 draft-leiba-3777upd-eligibility-05 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 updates RFC 3777 and 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 May 1, 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, Rule 15 . . . . . . . . . 3 59 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 61 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 63 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 5.1. Normative References . . . . . . . . . . . . . . . . . . . . 4 65 5.2. Informative References . . . . . . . . . . . . . . . . . . . 4 67 Author's Address . . . . . . . . . . . . . . . . . . . . . . 4 69 1. Introduction 71 The "Operation of the Nominating and Recall Committees" document 72 [RFC3777] defines the nominating committee process. One of the key 73 points in the process and in the selection of the nominating 74 committee is that the IETF wants to avoid having its top leadership 75 be self-selecting: the leaders should not be the ones who choose the 76 leaders. The selection of the nominating committee, therefore, 77 excludes those individuals who are in top leadership positions 78 currently. 80 That said, it would be bad to eliminate people who have the 81 experience necessary to understand of the IETF process: those 82 individuals can bring a broader perspective to the nominating 83 committee and will help ensure that the people it selects for the 84 leadership positions are better prepared to fulfill the roles. 86 RFC 3777 specifies that "sitting members" of the IAB and IESG "may 87 not volunteer to serve on the nominating committee". Since that 88 document was written the IETF Administrative Oversight Committee 89 (IAOC) was formed, some IAOC members are selected by the nominating 90 committee (see [RFC4071], Section 4), and that body is not covered by 91 RFC 3777. There is also uncertainty about whether ex-officio members 92 liaisons, and such are included as "sitting members". This document 93 updates RFC 3777 and clarifies those situations, with the 94 understanding that the intent of RFC 3777 was to exclude those 95 currently in IETF leadership positions from voting on the selection 96 of the new leadership. 98 In order to allow the largest reasonable list of potential nominating 99 committee members, we do not want to exclude those at lower levels of 100 IETF leadership. In particular, this document does not exclude 101 participation from working group chairs, IRTF research group chairs, 102 members of directorates and special review teams, and members of 103 other advisory bodies. 105 2. Replacement of RFC 3777, Section 4, Rule 15 107 The following paragraph replaces RFC 3777, Section 4, rule 15 in its 108 entirety. 110 15. Any person who serves on any of the Internet Society Board of 111 Trustees, the IAB, the IESG, or the IAOC, including those who serve 112 on these bodies in ex-officio positions, may not volunteer to serve 113 as voting members of the nominating committee. Liaisons to these 114 bodies from other bodies or organizations are not excluded by this 115 rule. 117 3. Security Considerations 119 This is a procedural document, and is entirely unrelated to security. 121 4. IANA Considerations 123 No IANA actions are requested by this document, and the RFC Editor is 124 asked to remove this section before publication. 126 5. References 128 5.1. Normative References 130 [RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and 131 Recall Process: Operation of the Nominating and Recall 132 Committees", BCP 10, RFC 3777, June 2004. 134 5.2. Informative References 136 [RFC4071] Austein, R. and B. Wijnen, "Structure of the IETF 137 Administrative Support Activity (IASA)", BCP 101, 138 RFC 4071, April 2005. 140 Author's Address 142 Barry Leiba 143 Huawei Technologies 145 Phone: +1 646 827 0648 146 Email: barryleiba@computer.org 147 URI: http://internetmessagingtechnology.org/