idnits 2.17.1 draft-leiba-3777upd-eligibility-03.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 (September 14, 2012) is 4235 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) September 14, 2012 5 Intended status: BCP 6 Expires: March 18, 2013 8 Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF 9 Leadership 10 draft-leiba-3777upd-eligibility-03 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 March 18, 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 The "Operation of the Nominating and Recall Committees" document 70 [RFC3777] defines the nominating committee process. One of the key 71 points in the process and in the selection of the nominating 72 committee is that the IETF wants to avoid having its top leadership 73 be self-selecting: the leaders should not be the ones who choose the 74 leaders. The selection of the nominating committee, therefore, 75 excludes those individuals who are in top leadership positions 76 currently. 78 That said, it would be bad to eliminate people who have the 79 experience necessary to understand of the IETF process: those 80 individuals can bring a broader perspective to the nominating 81 committee and will help ensure that the people it selects for the 82 leadership positions are better prepared to fulfill the roles. 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 IETF Administrative Oversight Committee 87 (IAOC) was formed, and that body is not covered by RFC 3777. There 88 is also uncertainty about whether ex-officio members liaisons, and 89 such are included as "sitting members". This document clarifies 90 those situations, with the understanding that the intent of RFC 3777 91 was to exclude those currently in IETF leadership positions from 92 voting on the selection of the new leadership. 94 In order to allow the largest reasonable list of potential nominating 95 committee members, we do not want to exclude those at lower levels of 96 IETF leadership. In particular, this document does not exclude 97 participation from working group chairs, IRTF research group chairs, 98 members of directorates and special review teams, and members of 99 other advisory bodies. 101 2. Replacement of RFC 3777, Section 4, Paragraph 15 103 The following paragraph replaces RFC 3777, Section 4, paragraph 15 in 104 its entirety. 106 15. Members of the Internet Society Board of Trustees and sitting 107 members of the IAB, the IESG, and the IAOC, including members in ex- 108 officio positions, may not volunteer to serve as voting members of 109 the nominating committee. Liaisons to these bodies from other bodies 110 or organizations are not excluded by this rule. 112 3. Security Considerations 114 This is a procedural document, and is entirely unrelated to security. 116 4. IANA Considerations 118 No IANA actions are requested by this document, and the RFC Editor is 119 asked to remove this section before publication. 121 5. Normative References 123 [RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and 124 Recall Process: Operation of the Nominating and Recall 125 Committees", BCP 10, RFC 3777, June 2004. 127 Author's Address 129 Barry Leiba 130 Huawei Technologies 132 Phone: +1 646 827 0648 133 Email: barryleiba@computer.org 134 URI: http://internetmessagingtechnology.org/