idnits 2.17.1 draft-moonesamy-nomcom-eligibility-01.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 (July 30, 2013) is 3917 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 (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT S. Moonesamy 3 Updates: 3777 (if approved) 4 Intended Status: Best Current Practice 5 Expires: January 31, 2014 July 30, 2013 7 The Nominating Committee Process: Eligibility 8 draft-moonesamy-nomcom-eligibility-01 10 Abstract 12 RFC 3777 specifies the process by which members of the Internet 13 Architecture Board, Internet Engineering Steering Group and IETF 14 Administrative Oversight Committee are selected, confirmed, and 15 recalled. 17 This document updates RFC 3777 to allow all contributors to the IETF 18 Standards Process to be eligible to serve on NomCom and sign a Recall 19 petition. 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), its areas, and its working groups. Note that 28 other groups may also distribute working documents as 29 Internet-Drafts. 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 The list of current Internet-Drafts can be accessed at 37 http://www.ietf.org/1id-abstracts.html 39 The list of Internet-Draft Shadow Directories can be accessed at 40 http://www.ietf.org/shadow.html 42 Copyright and License Notice 44 Copyright (c) 2013 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2. Updated Text from RFC 3777 . . . . . . . . . . . . . . . . . . 3 61 3 Security Considerations . . . . . . . . . . . . . . . . . . . . 4 62 4 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 63 5 References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 5.1 Normative References . . . . . . . . . . . . . . . . . . . 4 65 5.2 Informative References . . . . . . . . . . . . . . . . . . 4 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 68 1 Introduction 70 RFC 3777 [RFC3777] specifies the process by which members of the 71 Internet Architecture Board (IAB), Internet Engineering Steering 72 Group (IESG) and IETF Administrative Oversight Committee (IOAC) are 73 selected, confirmed, and recalled. The Nominating Committee 74 Selection is the process by which volunteers who will serve on the 75 committee (NomCom) are recognized. 77 The IETF Trust considers any submission to the IETF intended by the 78 Contributor for publication as all or part of an Internet-Draft or 79 RFC and any statement made within the context of an IETF activity 80 [RFC5378]. Such statements include oral statements in IETF sessions 81 as well as written and electronic communications, made through a 82 Jabber room. It is to be noted that the IETF decisions are made on 83 its mailing lists. 85 One of the rules for eligibility to serve on NomCom and to sign a 86 Recall petition is that a person must have attended at least three of 87 the last five IETF meetings. There is an assumption that a person 88 cannot understand how the IETF works if he or she does not have the 89 financial means to attend three out of five meetings. A person 90 contributing to the IETF through electronic communications does not 91 have any say about IAB, IESG or IAOC even though the IETF consider 92 the person as as a contributor. People are encouraged to participate 93 and contribute through mailing lists but are completely 94 disenfranchised relative to other people who attend IETF meetings. 95 People from remote parts of the world who lack extensive travel 96 resources cannot participate to the maximum extent possible even if 97 they are willing to invest the energy to do so. 99 This document updates RFC 3777 [RFC3777] to to allow all contributors 100 to the IETF Standards Process to be eligible to serve on NomCom and 101 sign a Recall petition. 103 2. Updated Text from RFC 3777 105 RFC 3777 [RFC3777], Section 5, "Nominating Committee Operation", 106 Paragraph 1 of Rule 14 is replaced as follows: 108 Members of the IETF community must have satisfied either of the 109 following requirements in order to volunteer: 111 (a) attended at least 3 of last 5 IETF meetings 113 (b) attended at least 15 IETF meetings, including at least 114 2 of the last 5 IETF meetings. 116 (c) attended at least 2 of the last 5 IETF meetings and has been 117 listed as least twice as personnel during the last 5 IETF 118 meetings. 120 3 Security Considerations 122 The document makes changes to the IETF process. These changes 123 will not affect the security of the Internet. 125 The IETF community depends on the honor and integrity of the 126 participants to make the process work. This document 127 encourages contributors not to cause any perception they are 128 "gaming" the system. 130 4 IANA Considerations 132 This document does not require IANA to take any action. 134 5 References 136 5.1 Normative References 138 [RFC3777] Galvin, J., Ed., "IAB and IESG Selection, Confirmation, 139 and Recall Process: Operation of the Nominating and Recall 140 Committees", BCP 10, RFC 3777, June 2004. 142 5.2 Informative References 144 [RFC5378] Bradner, S., Ed., and J. Contreras, Ed., "Rights 145 Contributors Provide to the IETF Trust", BCP 78, RFC 5378, 146 November 2008. 148 Authors' Addresses 150 S. Moonesamy 151 76, Ylang Ylang Avenue 152 Quatres Bornes 153 Mauritius 155 Email: sm+ietf@elandsys.com