idnits 2.17.1 draft-iab-ccg-appoint-process-03.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 == Line 183 has weird spacing: '...tion to the I...' -- The document date (4 January 2017) is 2667 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Architecture Board R. Housley 3 Internet-Draft Vigil Security 4 Intended status: Informational 4 January 2017 5 Expires: 4 July 2017 7 Appointment Procedures for the IETF Representatives to the 8 Community Coordination Group (CCG) 10 draft-iab-ccg-appoint-process-03 12 Abstract 14 This document outlines the procedures by which the IETF makes 15 appointments to the Community Coordination Group (CCG), which 16 provides advice and guidance to the IETF Trust in matters related to 17 the IANA Trademarks and the IANA domain names. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 Copyright Notice 36 Copyright (c) 2017 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 1. Introduction 51 The IANA IPR Community Agreement [1] was one of the many documents 52 that was part of the IANA Stewardship Transition. It calls for the 53 creation of the Community Coordination Group (CCG) to provide 54 guidance and advice to the IETF Trust regarding the stewardship of 55 the IANA Intellectual Property, which is the IANA trademarks and the 56 IANA domain names. 58 The CCG is comprised of nine individuals, called the CCG 59 Representatives. The three operational communities (the Names 60 Community, the Numbers Community, and the Protocol Parameters 61 Community) each appoint three CCG Representatives. Each operational 62 community has the right to change any of its CCG Representatives upon 63 written notice to the other operational communities and the IETF 64 Trust. An operational community may remove or replace its CCG 65 Representatives at any time and in its sole discretion. The means 66 and procedures by which an operational community chooses to select, 67 appoint, and remove its own CCG Representatives are determined solely 68 by that operational community. 70 Each Operational Community appoints one of its CCG Representatives as 71 a co-chair of the CCG, and that co-chair is empowered to speak on 72 behalf of its operational community regarding the IANA Intellectual 73 property. An Operational Community has the right to change its CCG 74 co-chair upon written notice to the other operational communities and 75 the IETF Trust. An operational community may remove or replace its 76 CCG co-chair at any time and in its sole discretion. 78 This document outlines the procedures for the IETF to select, 79 appoint, and remove the three CCG Representatives for the Protocol 80 Parameter Community. In addition, this document outlines the 81 procedures for the selection of the co-chair among those CCG 82 Representatives. 84 2. Desirable Qualifications for CCG Representatives 86 Candidates for the CCG Representative position for the Protocol 87 Parameters Community should have a demonstrable involvement in the 88 IETF and a solid understanding of the various ways that the IETF 89 makes use of protocol parameter registries. Candidates should be 90 familiar with the ways that the IETF community depends upon the IANA 91 trademarks and the IANA domain names. 93 Candidates are expected to be able to call on others in the IETF 94 community, as required, to ensure that the IETF Trust receives the 95 highest quality advice available. 97 Candidates are expected to possess clearly demonstrated technical 98 competence relating to the management of IANA protocol parameter 99 registries. Candidates are also expected to be able to understand 100 the ways that IANA registries are used by the Names Community and the 101 Numbers Community. 103 3. CCG Representative Selection Procedures 105 The three CCG Representatives for the Protocol Parameters Community 106 serve at the pleasure of the IAB. 108 3.1. Duration of Appointment 110 Each of the CCG Representatives is expected to serve for at least a 111 year, and appointments ought to be staggered to avoid simultaneous 112 replacement of all of the CCG Representatives at the same time. Each 113 year the IAB will seek input from the IETF community to determine 114 whether a personnel change is appropriate. 116 3.2. Nominations and Eligibility 118 When the IAB decides to appoint a new person as a CCG Representative, 119 the IAB will make a public call for nominations on the 120 ietf-announce@ietf.org mailing list. The public call will specify 121 the manner by which nominations will be accepted and the means by 122 which the list of nominees will be published for IETF community 123 feedback. Self-nominations are permitted. 125 Each nomination must include the name and contact information for 126 each candidate. The details about the candidate's background and 127 qualifications for the position should be provided with the 128 nomination. Trustees of the IETF Trust are not eligible for 129 nomination. All other IETF participants, including working group 130 chairs, IETF NomCom members, IAB members, and IESG members are 131 eligible for nomination. 133 IAB members who accept a nomination shall recuse themselves from 134 selection discussions. 136 3.3. Selection 138 The IAB will publish the list of people that have accepted their 139 nomination or nominated themselves. Feedback from the IETF community 140 will be considered by the IAB in making a selection. The IAB will 141 keep any feedback that is received confidential. 143 The IAB will consider potential conflicts with a CCG Representative 144 position and any other positions held by the nominated candidates. 146 After considering the IETF community feedback, potential conflicts, 147 and any other appropriate information that is available, the IAB 148 shall vote to select the best qualified CCG Representative. 150 4. CCG Representative Removal Procedures 152 If there are concerns with the performance of an IAB-appointed CCG 153 Representative, the IETF community can request that the IAB consider 154 removal. Such a request must be sent by email to iab-chair@iab.org. 156 The request must include a statement of justification for the removal 157 of the CCG Representative, including all relevant and appropriate 158 supporting documentation. 160 The IAB shall respond to the request within six weeks. If an IAB 161 member is serving in any of the CCG Representative positions, 162 regardless of the operational community that the IAB member 163 represents, that IAB member shall be recused from any investigation, 164 discussion, and vote to determine what action to take. 166 If the CCG Representative is removed, then the open position is to be 167 filled according to Section 3 of this document. 169 5. CCG Representative Co-Chair Selection Procedures 171 Whenever there is a change to the list of people that are serving as 172 CCG Representatives for the Protocol Parameters Community, the 173 sitting CCG Representatives shall use a procedure of their own 174 choosing to select the co-chair. The co-chair selection shall be 175 confirmed by the IAB, and then the IAB shall announce the co-chair 176 selection to the IETF community, the IETF Trust, and the CCG 177 Representatives from the other operational communities. 179 At any time, for any reason, the list of people that are serving as 180 CCG Representatives for the Protocol Parameters Community, may 181 revisit the selection of co-chair. If a different selection is made, 182 the new selection shall be confirmed by the IAB, and then the IAB 183 shall announce the co-chair selection to the IETF community, the 184 IETF Trust, and the CCG Representatives from the other operational 185 communities. 187 As part of the confirmation process, the IAB shall consider potential 188 conflicts of interest of the candidate for co-chair. 190 6. Initial Appointments 192 Since three CCG Representatives needed to be in place at midnight on 193 30 September 2016 when the IANA Stewardship Transition took place, 194 the IAB quickly appointed three individuals that were heavily 195 involved in the transition. The three individuals agreed to serve 196 until the appointment procedures could be adopted and employed. 198 Using the procedures in this document, the IAB will appoint three CCG 199 Representatives before the second IETF meeting in 2017. 201 To encourage the staggered replacement, at least one of those 202 appointed will be replaced before the second IETF meeting in 2018, 203 that is, one year after the first set of CCG Representatives are 204 appointed by the process in this document. 206 7. Reporting by the CCG Representatives to the IAB 208 CCG Representatives shall deliver reports to the IAB within a 209 reasonable time frame, providing whenever possible the opportunity to 210 obtain advice regarding open IANA Intellectual Property issues. 211 While no specific time periods for reporting are mandated, CCG 212 Representatives are expected to keep the IAB informed of CCG 213 activities. 215 Reports from the CCG Representatives will be made publicly available, 216 except for comments about individuals. These reports will typically 217 be part of the minutes of the IAB meeting where they are discussed. 219 8. IANA Considerations 221 This document has no actions for IANA. 223 9. Security Considerations 225 This document does not describe any technical protocols and has no 226 implications for network security. 228 10. Informative References 230 [1] IANA IPR Community Agreement, 21 September 2016, 231 . 234 11. Acknowledgements 236 Many thanks to Ted Hardie, Alissa Cooper, Brian Carpenter, Andrew 237 Sullivan, Dave Crocker, John Klensin, Dave Thaler, and Martin Thomson 238 for the valuable review and comments. 240 12. IAB Members at the time of this writing 242 {{{ RFC Editor: Please insert the list of IAB members at the time 243 this document is approved for publication. }}} 245 Author's Address 247 Russ Housley 248 918 Spring Knoll Drive 249 Herndon, VA 20170 250 USA 252 Email: housley@vigilsec.com