idnits 2.17.1 draft-iab-rzerc-02.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 -- The document date (February 10, 2017) is 2631 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group C. Morgan 3 Internet-Draft AMS 4 Intended status: Informational February 10, 2017 5 Expires: August 14, 2017 7 IETF ICANN Root Zone Evolution Review Committee Appointment Procedures 8 draft-iab-rzerc-02 10 Abstract 12 This memo outlines the process by which the IETF makes an appointment 13 to the ICANN Root Zone Evolution Review Committee (RZERC). 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on August 14, 2017. 32 Copyright Notice 34 Copyright (c) 2017 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. Desirable Qualifications for an IETF-Nominated RZERC Member . 2 51 3. IETF-Nominated RZERC Member Selection Process . . . . . . . . 3 52 3.1. Term Length . . . . . . . . . . . . . . . . . . . . . . . 3 53 3.2. Nominations and Eligibility . . . . . . . . . . . . . . . 3 54 3.3. Selection . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3.4. Timeframe . . . . . . . . . . . . . . . . . . . . . . . . 4 56 3.5. Mid-term Vacancies . . . . . . . . . . . . . . . . . . . 4 57 3.5.1. Interim Appointment Process . . . . . . . . . . . . . 4 58 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 59 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 60 6. Normative References . . . . . . . . . . . . . . . . . . . . 5 61 Appendix A. IAB Members at the time of this writing . . . . . . 5 62 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 64 1. Introduction 66 The ICANN Root Zone Evolution Review Committee (RZERC) reviews 67 proposed architectural changes to the content of the DNS root zone, 68 the systems including both hardware and software components used in 69 executing changes to the DNS root zone, and the mechanisms used for 70 distribution of the DNS root zone, and makes recommendations to the 71 ICANN Board. As stipulated in [RZERC-Charter] the IETF is called 72 upon to name its delegate to the committee. 74 The IAB will select one person for a one-year term. This appointment 75 can be renewable for up to three additional one-year terms. This 76 memo outlines the process by which the IETF makes that selection. 78 In brief, this document describes the timeframe and procedures for 79 the IAB to solicit public input and make a selection for the open 80 position. 82 2. Desirable Qualifications for an IETF-Nominated RZERC Member 84 Candidates for the RZERC should have a demonstrable involvement in 85 the IETF with a particular focus on active participation in IETF 86 Working Groups. 88 The candidate is expected to possess clearly demonstrated technical 89 competence in Internet technology relating to the DNS root zone, and 90 be able to articulate those technology issues such that the ICANN 91 Board can be provided with sound technical perspectives. The 92 candidate is also expected to be able to understand the respective 93 roles and responsibilities of the IETF and ICANN and be able to 94 articulate these roles within both organizational communities. 96 The candidate will be a representative or a delegate of the IETF. It 97 is expected that the candidate would be able to call on experts in 98 the IETF community as required, to ensure that the ICANN Board 99 receives the highest quality technical advice available. 101 3. IETF-Nominated RZERC Member Selection Process 103 3.1. Term Length 105 The IETF appointment to the RZERC will serve a one-year term. This 106 appointment can be renewable for up to three additional one-year 107 terms. 109 In cases when the incumbent is willing to serve for an additional 110 term and has not yet exceeded the term limits described above, the 111 IAB may ask the IETF community for feedback on the incumbent to find 112 out whether it is necessary to run a full selection process. If the 113 IAB determines that it is not necessary to run a full selection 114 process, the incumbent may be re-appointed by the IAB for another 115 year. 117 3.2. Nominations and Eligibility 119 Except in cases when the IAB has decided to re-appoint the incumbent, 120 each year, the IAB will make a public call for nominations on the 121 ietf-announce@ietf.org mailing list. The public call will specify 122 the manner by which nominations will be accepted and the means by 123 which the list of nominees will be published. The call for 124 nominations will also include the expected workload for the position, 125 as provided by the current IETF-appointed RZERC member. 127 Self-nominations are permitted. Along with the name and contact 128 information for each candidate, details about the candidate's 129 background and qualifications for the position should be attached to 130 the nomination. All IETF participants are eligible for nomination. 131 While IETF NomCom members, IAB members, IAOC members, and IESG 132 members are eligible, the IAB will balance time constraints and 133 potential conflicts of interest from those members in its 134 consideration of nominees. 136 IAB members who accept a nomination will recuse themselves from 137 selection discussions. 139 3.3. Selection 141 The IAB will publish the list of nominated persons, review the 142 material, and make a selection. 144 The IAB will consider potential conflicts with a position on the 145 ICANN RZERC and any other ICANN committees supported by nominated 146 candidates. 148 3.4. Timeframe 150 The IAB expects to seat new RZERC members in time for ICANN's annual 151 general meeting in Q4 of each year. Basic timeframe requirements for 152 the IETF process are as follows: 154 o 4-6 weeks for solicitation of nominations or review of incumbent 156 o 4-6 weeks for review of nominees, deliberation and selection 158 In Q2 of each year, the IAB will announce the specific dates for the 159 RZERC selection process for that year (taking into account the 160 particular dates of IETF and ICANN meetings, etc), following the 161 guidelines above. 163 3.5. Mid-term Vacancies 165 This document describes the process for the general, annual 166 appointment of RZERC members to fill the seats of members whose terms 167 are ending. However, if an IETF-appointed member of the RZERC is 168 unable to serve his or her full term, the IAB may, at its discretion, 169 immediately select a replacement to serve the remainder of the term 170 using the interim process defined in Section 3.5.1. If the IAB does 171 not invoke the interim process, the next annual selection process 172 will fill the vacancy. 174 3.5.1. Interim Appointment Process 176 If the IAB elects to fill the mid-term vacancy before the next annual 177 selection, a separate timeline will be announced and the rest of the 178 process described in this document will be followed. 180 4. IANA Considerations 182 This document has no actions for IANA. 184 5. Security Considerations 186 This document does not describe any technical protocols and has no 187 implications for network security. 189 6. Normative References 191 [RZERC-Charter] 192 ICANN, "Root Zone Evolution Review Committee (RZERC) 193 Charter", August 2016, 194 . 197 Appendix A. IAB Members at the time of this writing 199 Jari Arkko 201 Ralph Droms 203 Ted Hardie 205 Joe Hildebrand 207 Russ Housley 209 Lee Howard 211 Erik Nordmark 213 Robert Sparks 215 Andrew Sullivan 217 Dave Thaler 219 Martin Thomson 221 Brian Trammell 223 Suzanne Woolf 225 Author's Address 227 Cindy Morgan 228 AMS 230 Email: cmorgan@amsl.com