INTERNET-DRAFT S. Moonesamy Updates: 3777 (if approved) Intended Status: Best Current Practice Expires: January 31, 2014 July 30, 2013 The Nominating Committee Process: Eligibility draft-moonesamy-nomcom-eligibility-01 Abstract RFC 3777 specifies the process by which members of the Internet Architecture Board, Internet Engineering Steering Group and IETF Administrative Oversight Committee are selected, confirmed, and recalled. This document updates RFC 3777 to allow all contributors to the IETF Standards Process to be eligible to serve on NomCom and sign a Recall petition. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright and License Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. S. Moonesamy Expires January 31, 2014 [Page 1]
Internet-Draft NomCom Eligibility July 30, 2013 This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Updated Text from RFC 3777 . . . . . . . . . . . . . . . . . . 3 3 Security Considerations . . . . . . . . . . . . . . . . . . . . 4 4 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 5 References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5.1 Normative References . . . . . . . . . . . . . . . . . . . 4 5.2 Informative References . . . . . . . . . . . . . . . . . . 4 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 S. Moonesamy Expires January 31, 2014 [Page 2]
Internet-Draft NomCom Eligibility July 30, 2013 1 Introduction RFC 3777 [RFC3777] specifies the process by which members of the Internet Architecture Board (IAB), Internet Engineering Steering Group (IESG) and IETF Administrative Oversight Committee (IOAC) are selected, confirmed, and recalled. The Nominating Committee Selection is the process by which volunteers who will serve on the committee (NomCom) are recognized. The IETF Trust considers any submission to the IETF intended by the Contributor for publication as all or part of an Internet-Draft or RFC and any statement made within the context of an IETF activity [RFC5378]. Such statements include oral statements in IETF sessions as well as written and electronic communications, made through a Jabber room. It is to be noted that the IETF decisions are made on its mailing lists. One of the rules for eligibility to serve on NomCom and to sign a Recall petition is that a person must have attended at least three of the last five IETF meetings. There is an assumption that a person cannot understand how the IETF works if he or she does not have the financial means to attend three out of five meetings. A person contributing to the IETF through electronic communications does not have any say about IAB, IESG or IAOC even though the IETF consider the person as as a contributor. People are encouraged to participate and contribute through mailing lists but are completely disenfranchised relative to other people who attend IETF meetings. People from remote parts of the world who lack extensive travel resources cannot participate to the maximum extent possible even if they are willing to invest the energy to do so. This document updates RFC 3777 [RFC3777] to to allow all contributors to the IETF Standards Process to be eligible to serve on NomCom and sign a Recall petition. 2. Updated Text from RFC 3777 RFC 3777 [RFC3777], Section 5, "Nominating Committee Operation", Paragraph 1 of Rule 14 is replaced as follows: Members of the IETF community must have satisfied either of the following requirements in order to volunteer: (a) attended at least 3 of last 5 IETF meetings (b) attended at least 15 IETF meetings, including at least 2 of the last 5 IETF meetings. S. Moonesamy Expires January 31, 2014 [Page 3]
Internet-Draft NomCom Eligibility July 30, 2013 (c) attended at least 2 of the last 5 IETF meetings and has been listed as least twice as personnel during the last 5 IETF meetings. 3 Security Considerations The document makes changes to the IETF process. These changes will not affect the security of the Internet. The IETF community depends on the honor and integrity of the participants to make the process work. This document encourages contributors not to cause any perception they are "gaming" the system. 4 IANA Considerations This document does not require IANA to take any action. 5 References 5.1 Normative References [RFC3777] Galvin, J., Ed., "IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees", BCP 10, RFC 3777, June 2004. 5.2 Informative References [RFC5378] Bradner, S., Ed., and J. Contreras, Ed., "Rights Contributors Provide to the IETF Trust", BCP 78, RFC 5378, November 2008. Authors' Addresses S. Moonesamy 76, Ylang Ylang Avenue Quatres Bornes Mauritius Email: sm+ietf@elandsys.com S. Moonesamy Expires January 31, 2014 [Page 4]