Requirements for IETF Nominations Committee Tools
RFC 6730
Document | Type |
RFC - Informational
(September 2012; No errata)
Was draft-krishnan-nomcom-tools (individual in gen area)
|
|
---|---|---|---|
Authors | Suresh Krishnan , Joel Halpern | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6730 (Informational) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Russ Housley | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) S. Krishnan Request for Comments: 6730 J. Halpern Category: Informational Ericsson ISSN: 2070-1721 September 2012 Requirements for IETF Nominations Committee Tools Abstract This document defines the requirements for a set of tools for use by the IETF Nominations Committee. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6730. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. 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. Krishnan & Halpern Informational [Page 1] RFC 6730 NomCom Tools September 2012 Table of Contents 1. Introduction ....................................................2 1.1. Conventions Used in This Document ..........................2 2. Meta Requirement ................................................2 3. Authentication ..................................................3 4. Security and Access Control .....................................3 5. Nominations .....................................................4 6. Accepting and Declining Nominations .............................5 7. Questionnaires ..................................................6 8. Feedback Collection .............................................7 9. Security Considerations .........................................8 10. Acknowledgements ...............................................8 12. Normative References ...........................................8 Appendix A. Example for Key Generation .............................9 1. Introduction The IETF Nominations Committee (NomCom) is a body that selects candidates for open IESG, IAB, and IAOC positions following the process outlined in [RFC3777]. There is a need for a set of tools to aid the NomCom in efficient operation. This document presents a set of requirements for such a tool. 1.1. Conventions Used in This Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 2. Meta Requirement There is an existing tool for supporting NomCom work. The set of requirements specified in this document are mainly enhancement requirements or behavioral changes to the existing tool. Unless otherwise stated, all of the current functions of the existing NomCom tool need to be supported in the new tool as well. o META-001: The tool MUST provide all the functionality that is provided by the current NomCom tool, except in cases where a requirement specified in this document overrides a current behavior. The current NomCom tool can be found at the following URLs: https://www.ietf.org/group/nomcom/2012/private/ displays the NomCom private parts of the tool (Private NomCom tool) and https://www.ietf.org/group/nomcom/2012/ displays the community member accessible parts of the tool (Public NomCom tool). Krishnan & Halpern Informational [Page 2] RFC 6730 NomCom Tools September 2012 3. Authentication All access to NomCom tools needs to be authenticated. Users of the tools have different privileges based on their role. The tool needs to support at least three levels of access: community member, NomCom member, and NomCom chair. The levels of access are set up by the staff of the IETF Secretariat. It is to be noted that the Secretariat staff do not have any access to the tool. They areShow full document text