IETF Appointment Procedures for the ICANN Root Zone Evolution Review Committee
RFC 8128
Document | Type |
RFC - Informational
(March 2017; No errata)
Was draft-iab-rzerc (iab)
|
|
---|---|---|---|
Author | Cindy Morgan | ||
Last updated | 2017-03-10 | ||
Replaces | draft-morgan-iab-rzerc | ||
Stream | IAB | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | IAB state | Published RFC | |
Consensus Boilerplate | Yes | ||
RFC Editor Note | (None) |
Internet Architecture Board (IAB) C. Morgan Request for Comments: 8128 AMS Category: Informational March 2017 ISSN: 2070-1721 IETF Appointment Procedures for the ICANN Root Zone Evolution Review Committee Abstract This memo outlines the process by which the IETF makes an appointment to the ICANN Root Zone Evolution Review Committee (RZERC). 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 Architecture Board (IAB) and represents information that the IAB has deemed valuable to provide for permanent record. It represents the consensus of the Internet Architecture Board (IAB). Documents approved for publication by the IAB are not a candidate for any level of Internet Standard; see Section 2 of RFC 7841. 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/rfc8128. Copyright Notice Copyright (c) 2017 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. Morgan Informational [Page 1] RFC 8128 RZERC March 2017 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Desirable Qualifications for an IETF-Nominated RZERC Member . 2 3. IETF-Nominated RZERC Member Selection Process . . . . . . . . 3 3.1. Term Length . . . . . . . . . . . . . . . . . . . . . . . 3 3.2. Nominations and Eligibility . . . . . . . . . . . . . . . 3 3.3. Selection . . . . . . . . . . . . . . . . . . . . . . . . 4 3.4. Timeframe . . . . . . . . . . . . . . . . . . . . . . . . 4 3.5. Mid-term Vacancies . . . . . . . . . . . . . . . . . . . 4 3.5.1. Interim Appointment Process . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 6. Normative References . . . . . . . . . . . . . . . . . . . . 5 IAB Members at the Time of Approval . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction The ICANN Root Zone Evolution Review Committee (RZERC) reviews proposed architectural changes to the content of the DNS root zone, the systems including both hardware and software components used in executing changes to the DNS root zone, and the mechanisms used for distribution of the DNS root zone, and makes recommendations to the ICANN Board. As stipulated in [RZERC-Charter], the IETF is called upon to name its delegate to the committee. The IAB will select one person for a one-year term. This appointment can be renewed for up to three additional one-year terms. This memo outlines the process by which the IETF makes that selection. In brief, this document describes the timeframe and procedures for the IAB to solicit public input and make a selection for the open position. 2. Desirable Qualifications for an IETF-Nominated RZERC Member Candidates for the RZERC should have a demonstrable involvement in the IETF with a particular focus on active participation in IETF Working Groups. The candidate is expected to possess clearly demonstrated technical competence in Internet technology relating to the DNS root zone and be able to articulate those technology issues such that the ICANN Board can be provided with sound technical perspectives. The candidate is also expected to be able to understand the respective roles and responsibilities of the IETF and ICANN and be able to articulate these roles within both organizational communities. Morgan Informational [Page 2] RFC 8128 RZERC March 2017 The candidate will be a representative or a delegate of the IETF. It is expected that the candidate would be able to call on experts in the IETF community as required, to ensure that the ICANN Board receives the highest-quality technical advice available. 3. IETF-Nominated RZERC Member Selection Process 3.1. Term Length The IETF appointment to the RZERC will serve a one-year term. This appointment can be renewed for up to three additional one-year terms.Show full document text