idnits 2.17.1 draft-leiba-3777upd-eligibility-06.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 (December 12, 2012) is 4151 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) December 12, 2012 5 Intended status: BCP 6 Expires: June 15, 2013 8 Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF 9 Leadership 10 draft-leiba-3777upd-eligibility-06 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 the time 16 that document was written the IAOC was formed, and that body is not 17 covered by RFC 3777. There is also uncertainty in RFC 3777 about 18 whether ex-officio members and liaisons are included as "sitting 19 members". This document updates RFC 3777 to clarify the rules as 20 they apply to members of the IAB, the IESG, and the IAOC. 22 Status of this Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on June 15, 2013. 39 Copyright Notice 41 Copyright (c) 2012 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 1. Introduction 56 The "Operation of the Nominating and Recall Committees" document 57 [RFC3777] defines the nominating committee process. It is important 58 to include on the nominating committee people who have the experience 59 necessary to understand the IETF process: those individuals can bring 60 a broader perspective to the nominating committee and will help 61 ensure that the people it selects are better prepared to fulfill the 62 roles. That said, one of the key points in the process and in the 63 selection of the nominating committee is that the IETF wants to avoid 64 having the IAB and the IESG be self-selecting. The selection of the 65 nominating committee, therefore, excludes individuals who currently 66 serve on bodies to which the nominating committee selects seats. 68 RFC 3777 specifies that "sitting members" of the IAB and IESG "may 69 not volunteer to serve on the nominating committee". Since the time 70 that document was written the IETF Administrative Oversight Committee 71 (IAOC) was formed, some IAOC members are selected by the nominating 72 committee (see [RFC4071], Section 4), and that body is not covered by 73 RFC 3777. There is also uncertainty in RFC 3777 about whether ex- 74 officio members, liaisons, and such are included as "sitting 75 members". This document updates RFC 3777 to clarify the rules as 76 they apply to members of the IAB, the IESG, and the IAOC, with the 77 understanding of the intent of RFC 3777 as outlined above. 79 RFC 3777 does not exclude participation by working group chairs, IRTF 80 research group chairs, members of directorates and special review 81 teams, and members of other advisory bodies. This document makes no 82 changes in that regard. 84 2. Replacement of RFC 3777, Section 4, Rule 15 86 The following paragraph replaces RFC 3777, Section 4, rule 15 in its 87 entirety. 89 15. Any person who serves on any of the Internet Society Board of 90 Trustees, the IAB, the IESG, or the IAOC, including those who serve 91 on these bodies in ex-officio positions, may not volunteer to serve 92 as voting members of the nominating committee. Liaisons to these 93 bodies from other bodies or organizations are not excluded by this 94 rule. 96 3. Security Considerations 98 This is a procedural document, and is entirely unrelated to security. 100 4. IANA Considerations 102 No IANA actions are requested by this document, and the RFC Editor is 103 asked to remove this section before publication. 105 5. References 107 5.1. Normative References 109 [RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and 110 Recall Process: Operation of the Nominating and Recall 111 Committees", BCP 10, RFC 3777, June 2004. 113 5.2. Informative References 115 [RFC4071] Austein, R. and B. Wijnen, "Structure of the IETF 116 Administrative Support Activity (IASA)", BCP 101, 117 RFC 4071, April 2005. 119 Author's Address 121 Barry Leiba 122 Huawei Technologies 124 Phone: +1 646 827 0648 125 Email: barryleiba@computer.org 126 URI: http://internetmessagingtechnology.org/