idnits 2.17.1 draft-ietf-iasa2-rfc4071bis-07.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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC4071], [RFC4333], [RFC7691]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == The 'Obsoletes: ' line in the draft header should list only the _numbers_ of the RFCs which will be obsoleted by this document (if approved); it should not include the word 'RFC' in the list. -- The abstract seems to indicate that this document obsoletes RFC4333, but the header doesn't have an 'Obsoletes:' line to match this. -- The abstract seems to indicate that this document obsoletes RFC4071, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 28, 2019) is 1884 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'ML-memo' is defined on line 1086, but no explicit reference was found in the text == Unused Reference: 'RFC2031' is defined on line 1095, but no explicit reference was found in the text == Unused Reference: 'RFC8318' is defined on line 1128, but no explicit reference was found in the text == Outdated reference: A later version (-08) exists of draft-ietf-iasa2-rfc2031bis-04 ** Downref: Normative reference to an Informational draft: draft-ietf-iasa2-rfc2031bis (ref. 'I-D.ietf-iasa2-rfc2031bis') == Outdated reference: A later version (-09) exists of draft-ietf-iasa2-rfc7437bis-05 -- Possible downref: Non-RFC (?) normative reference: ref. 'IETF-LLC-A' -- Obsolete informational reference (is this intentional?): RFC 2031 (Obsoleted by RFC 8712) -- Obsolete informational reference (is this intentional?): RFC 4071 (Obsoleted by RFC 8711) -- Obsolete informational reference (is this intentional?): RFC 4333 (Obsoleted by RFC 8711) -- Obsolete informational reference (is this intentional?): RFC 7691 (Obsoleted by RFC 8711) -- Obsolete informational reference (is this intentional?): RFC 8318 (Obsoleted by RFC 8713) Summary: 2 errors (**), 0 flaws (~~), 7 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IASA2 B. Haberman 3 Internet-Draft Johns Hopkins University 4 Obsoletes: RFC4071, RFC4333, RFC7691 (if J. Hall 5 approved) CDT 6 Intended status: Best Current Practice J. Livingood 7 Expires: September 1, 2019 Comcast 8 February 28, 2019 10 Structure of the IETF Administrative Support Activity, Version 2.0 11 draft-ietf-iasa2-rfc4071bis-07 13 Abstract 15 The IETF Administrative Support Activity (IASA) was originally 16 established in 2005. In the years since then, the needs of the IETF 17 evolved in ways that required changes to its administrative 18 structure. The purpose of this document is to document and describe 19 the IASA 2.0 structure. 21 Under IASA 2.0, the work of the IETF's administrative and fundraising 22 tasks is conducted by an administrative organization, the IETF 23 Administration Limited Liability Company ("IETF LLC"). Under this 24 structure, the IETF Administrative Oversight Committee (IAOC) was 25 eliminated, and its oversight and advising functions transferred to 26 the IETF LLC Board. 28 The IETF LLC provides the corporate legal home for the IETF, the 29 Internet Architecture Board (IAB), and the Internet Research Task 30 Force (IRTF). 32 This document describes the structure of the IETF Administrative 33 Support Activity, version 2 (IASA 2.0). It defines the roles and 34 responsibilities of the IETF LLC Board, the IETF Executive Director, 35 and ISOC in the fiscal and administrative support of the IETF 36 standards process. It also defines the membership and selection 37 rules for the IETF LLC Board. 39 This document obsoletes [RFC4071], [RFC4333], and [RFC7691]. 41 Status of This Memo 43 This Internet-Draft is submitted in full conformance with the 44 provisions of BCP 78 and BCP 79. 46 Internet-Drafts are working documents of the Internet Engineering 47 Task Force (IETF). Note that other groups may also distribute 48 working documents as Internet-Drafts. The list of current Internet- 49 Drafts is at https://datatracker.ietf.org/drafts/current/. 51 Internet-Drafts are draft documents valid for a maximum of six months 52 and may be updated, replaced, or obsoleted by other documents at any 53 time. It is inappropriate to use Internet-Drafts as reference 54 material or to cite them other than as "work in progress." 56 This Internet-Draft will expire on September 1, 2019. 58 Copyright Notice 60 Copyright (c) 2019 IETF Trust and the persons identified as the 61 document authors. All rights reserved. 63 This document is subject to BCP 78 and the IETF Trust's Legal 64 Provisions Relating to IETF Documents 65 (https://trustee.ietf.org/license-info) in effect on the date of 66 publication of this document. Please review these documents 67 carefully, as they describe your rights and restrictions with respect 68 to this document. Code Components extracted from this document must 69 include Simplified BSD License text as described in Section 4.e of 70 the Trust Legal Provisions and are provided without warranty as 71 described in the Simplified BSD License. 73 Table of Contents 75 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 76 2. Scope Limitation . . . . . . . . . . . . . . . . . . . . . . 4 77 3. LLC Agreement with the Internet Society . . . . . . . . . . . 4 78 4. Definitions and Principles . . . . . . . . . . . . . . . . . 5 79 4.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 80 4.2. Key Differences From the Old IASA Structure to IASA 2.0 . 6 81 4.3. General IETF LLC Responsibilities . . . . . . . . . . . . 6 82 4.4. IETF LLC Working Principles . . . . . . . . . . . . . . . 7 83 4.5. Principles of the IETF and ISOC Relationship . . . . . . 8 84 4.6. Relationship of the IETF LLC Board to the IETF Leadership 8 85 4.7. Review of IETF Executive Director and IETF LLC Board 86 Decisions . . . . . . . . . . . . . . . . . . . . . . . . 8 87 4.8. Termination and Change . . . . . . . . . . . . . . . . . 9 88 5. Structure of IASA2 . . . . . . . . . . . . . . . . . . . . . 9 89 5.1. IETF Executive Director and Staff Responsibilities . . . 9 90 5.2. IETF LLC Board Responsibilities . . . . . . . . . . . . . 11 91 5.3. Board Design Goals . . . . . . . . . . . . . . . . . . . 13 92 6. IETF LLC Board Membership, Selection and Accountability . . . 13 93 6.1. Board Composition . . . . . . . . . . . . . . . . . . . . 13 94 6.2. IETF LLC-Appointed Directors . . . . . . . . . . . . . . 14 95 6.3. Recruiting IETF LLC Board Directors . . . . . . . . . . . 14 96 6.4. IETF LLC Board Director Term Length . . . . . . . . . . . 14 97 6.5. IETF LLC Board Director Limit . . . . . . . . . . . . . . 15 98 6.6. Staggered Terms . . . . . . . . . . . . . . . . . . . . . 15 99 6.7. IETF LLC Board Director Removal . . . . . . . . . . . . . 15 100 6.8. Filling an IETF LLC Board Director Vacancy . . . . . . . 15 101 6.9. Quorum . . . . . . . . . . . . . . . . . . . . . . . . . 16 102 6.10. Board Voting . . . . . . . . . . . . . . . . . . . . . . 16 103 6.11. Interim Board . . . . . . . . . . . . . . . . . . . . . . 16 104 6.12. Board Positions . . . . . . . . . . . . . . . . . . . . . 17 105 7. IETF LLC Funding . . . . . . . . . . . . . . . . . . . . . . 17 106 7.1. Financial Statements . . . . . . . . . . . . . . . . . . 17 107 7.2. Bank and Investment Accounts . . . . . . . . . . . . . . 18 108 7.3. Financial Audits . . . . . . . . . . . . . . . . . . . . 18 109 7.4. ISOC Financial Support . . . . . . . . . . . . . . . . . 18 110 7.5. IETF Meeting Revenues . . . . . . . . . . . . . . . . . . 18 111 7.6. Sponsorships and Donations to the IETF LLC . . . . . . . 18 112 7.7. Focus of Funding Support . . . . . . . . . . . . . . . . 19 113 7.8. Charitable Fundraising Practices . . . . . . . . . . . . 19 114 7.9. Operating Reserve . . . . . . . . . . . . . . . . . . . . 19 115 7.10. Annual Budget Process . . . . . . . . . . . . . . . . . . 19 116 8. IETF LLC Policies . . . . . . . . . . . . . . . . . . . . . . 20 117 8.1. Conflict of Interest Policy . . . . . . . . . . . . . . . 20 118 8.2. Other Policies . . . . . . . . . . . . . . . . . . . . . 21 119 8.3. Compliance . . . . . . . . . . . . . . . . . . . . . . . 21 120 9. Three-Year Assessment . . . . . . . . . . . . . . . . . . . . 21 121 10. Security Considerations . . . . . . . . . . . . . . . . . . . 22 122 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 123 12. Pronouns . . . . . . . . . . . . . . . . . . . . . . . . . . 22 124 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22 125 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 126 14.1. Normative References . . . . . . . . . . . . . . . . . . 22 127 14.2. Informative References . . . . . . . . . . . . . . . . . 23 128 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 130 1. Introduction 132 The IETF Administrative Support Activity (IASA) was originally 133 established in 2005. In the years since then, the needs of the IETF 134 evolved in ways that required changes to its administrative 135 structure. The purpose of this document is to document and describe 136 the IASA 2.0 structure. 138 Under IASA 2.0, the work of the IETF's administrative and fundraising 139 tasks is conducted by an administrative organization, the IETF 140 Administration Limited Liability Company ("IETF LLC"). Under this 141 structure, the Internet Administrative Oversight Committee (IAOC) is 142 eliminated, and its oversight and advising functions transferred to 143 the IETF LLC Board. 145 The IETF LLC provides the corporate legal home for the IETF, the 146 Internet Architecture Board (IAB), and the Internet Research Task 147 Force (IRTF). 149 [I-D.haberman-iasa20dt-recs] discusses the challenges facing the 150 original IASA structure as well as several options for reorganizing 151 the IETF's administration under different legal structures. This 152 document outlines how the chosen option is structured and describes 153 how the organization fits together with existing and new IETF 154 community structures. 156 Under IASA 2.0, most of the responsibilities that [RFC4071] assigned 157 to the IETF Administrative Director (IAD) and the Internet Society 158 (ISOC) were transferred to the IETF LLC and IETF Administration LLC 159 Executive Director (IETF Executive Director). It is the job of the 160 IETF LLC to meet the administrative needs of the IETF and to ensure 161 that the IETF LLC meets the needs of the IETF community. 163 Eliminating the IAOC meant that changes were required in how trustees 164 could be appointed to the IETF Trust. The details of how this is 165 done are outside the scope of this document but are covered in 166 [I-D.ietf-iasa2-trust-update]. 168 This document obsoletes [RFC4071], which specified the original IASA, 169 [RFC4333], which specified the selection guidelines and process for 170 IAOC members and [RFC7691], which specified terms for IAOC members. 172 2. Scope Limitation 174 The document does not propose any changes related to the standards 175 process as currently conducted by the Internet Engineering Steering 176 Group (IESG) and Internet Architecture Board (IAB). In addition, no 177 changes are made to the appeals chain, the process for making and 178 confirming IETF and IAB appointments, the technical work of the 179 Internet Research Task Force (IRTF), or to ISOC's membership in or 180 support of other organizations. 182 3. LLC Agreement with the Internet Society 184 The LLC Agreement between the IETF LLC and ISOC is available at 185 [IETF-LLC-A]. This IASA2 structure, and thus this document, depends 186 on the LLC Agreement and will refer to it to help explain certain 187 aspects of the legal relationship between the IETF LLC and ISOC. 189 The LLC Agreement was developed between legal representatives of the 190 IETF and ISOC and includes all critical terms of the relationship, 191 while still enabling maximum unilateral flexibility for the IETF LLC 192 Board. The LLC Agreement includes only basic details about how the 193 Board manages itself or manages IETF LLC staff, so that the Board has 194 flexibility to make changes without amending the agreement. The 195 Board can independently develop policy or procedures documents that 196 fill gaps. 198 4. Definitions and Principles 200 4.1. Terminology 202 Although most of the terms, abbreviations, and acronyms used in this 203 document are reasonably well known, first-time readers may find some 204 terminology confusing. This section therefore attempts to provide a 205 quick summary. 207 IAB: Internet Architecture Board (see [RFC2026], [RFC2850]). 209 IAD: IETF Administrative Director, a role obsoleted by this document 210 and the ISOC/IETF LLC Agreement ([IETF-LLC-A]) and replaced by the 211 IETF LLC Executive Director. 213 IAOC: IETF Administrative Oversight Committee, a committee that 214 oversaw IETF administrative activity. The IAOC is obsoleted by this 215 document and replaced by the IETF LLC Board. The IETF Trust was 216 formerly populated by IAOC members. Its membership is now distinct 217 from that of the IETF LLC Board (See [I-D.ietf-iasa2-trust-update]).) 219 IASA: The IETF Administrative Support Activity, consists of the IETF 220 LLC board, employees, and contractors. Uses of the term 'IASA' as a 221 proper noun may imply a subset of these roles, or all of them. 223 IASA 2.0: Version 2.0 of the IETF Administrative Support Activity, 224 defined by this document. 226 IESG: Internet Engineering Steering Group (see [RFC2026], [RFC3710]). 228 IETF: Internet Engineering Task Force (see [RFC3233]). 230 IETF Administration LLC: The legal entity - a disregarded Limited 231 Liability Company (LLC) of The Internet Society - established to 232 provide a corporate legal framework for facilitating current and 233 future activities related to the IETF, IAB, and IRTF. It was 234 established by the ISOC/IETF LLC Agreement ([IETF-LLC-A]) and is 235 referred to as "IETF LLC." 237 IETF LLC Executive Director: the Executive Director for the IETF LLC, 238 responsible for day-to-day administrative and operational direction 239 (See Section 5.1). Also referred to as "IETF Executive Director". 241 IETF LLC Board: The Board of Directors of the IETF LLC. The IETF LLC 242 Board is formally a multi-member "manager" of the IETF LLC on behalf 243 of ISOC (See Section 5.2). 245 ISOC: Internet Society (see [I-D.ietf-iasa2-rfc2031bis] and [ISOC]). 247 4.2. Key Differences From the Old IASA Structure to IASA 2.0 249 o The IAOC and IAD roles defined in RFC 4071 are eliminated. 251 o The former ISOC and IAD responsibilities are assigned to a new 252 organization, IETF Administration LLC. 254 o The Board of Directors of the IETF LLC - formally a multi-member 255 "manager" of the IETF LLC on behalf of ISOC - assumes the 256 oversight responsibilities of the IAOC. 258 o The Board of the IETF LLC is more focused on strategy and 259 oversight than the IAOC was, with the IETF Executive Director and 260 their team in charge of day-to-day operations. 262 o The IAD role is replaced with the IETF Executive Director role. 264 o The role that was previously referred to as "IETF Executive 265 Director" in older documents such as [RFC2026] is now "Managing 266 Director, IETF Secretariat". 268 4.3. General IETF LLC Responsibilities 270 The IETF LLC is established to provide administrative support to the 271 IETF. It has no authority over the standards development activities 272 of the IETF. 274 The responsibilities of the IETF LLC are: 276 o Operations. The IETF LLC is responsible for supporting the 277 ongoing operations of the IETF, including meetings and non-meeting 278 activities. 280 o Finances. The IETF LLC is responsible for managing the IETF's 281 finances and budget. 283 o Fundraising. The IETF LLC is responsible for raising money on 284 behalf of the IETF. 286 o Compliance. The IETF LLC is responsible for establishing and 287 enforcing policies to ensure compliance with applicable laws, 288 regulations, and rules. 290 The manner by which these responsibilities under the IETF LLC are 291 organized is intended to address the problems described in Sections 292 3.1.1., 3.1.2, and 3.1.3 of [I-D.haberman-iasa20dt-recs]. 293 Specifically, this is intended to bring greater clarity around roles, 294 responsibilities, representation, decision-making, and authority. 296 In addition, by having the IETF LLC manage the IETF's finances and 297 conduct the IETF's fundraising, confusion about who is responsible 298 for representing the IETF to sponsors and who directs the uses of 299 sponsorship funds should have been eliminated. Finally, having the 300 IETF LLC reside in a defined, distinct legal entity, and taking 301 responsibility for operations, enables the organization to execute 302 its own contracts without the need for review and approval by ISOC. 304 4.4. IETF LLC Working Principles 306 The IETF LLC is expected to conduct its work according to the 307 following principles: 309 o Transparency. The IETF LLC is expected to keep the IETF community 310 informed about its work, subject to reasonable confidentiality 311 concerns, and to engage with the community to obtain consensus- 312 based community input on key issues and otherwise as needed. The 313 IETF community expects complete visibility into the financial and 314 legal structure of the IETF LLC. This includes information about 315 the IETF LLC annual budget and associated regular financial 316 reports, results of financial and any other independent audits, 317 tax filings, significant contracts or other significant long-term 318 financial commitments that bind the IETF LLC. As discussed in 319 [ietf101-slides], whatever doesn't have a specific justification 320 for being kept confidential is expected to be made public. The 321 Board is expected to develop and maintain a public list of 322 confidential items, describing the nature of the information and 323 the reason for confidentiality. The Board will also publish its 324 operating procedures. 326 o Responsiveness to the community. The IETF LLC is expected to act 327 consistently with the documented consensus of the IETF community, 328 to be responsive to the community's needs, and to adapt its 329 decisions in response to consensus-based community feedback. 331 o Diligence. The IETF LLC is expected to act responsibly so as to 332 minimize risks to IETF participants and to the future of the IETF 333 as a whole, such as financial risks. 335 o Unification: The IETF LLC is responsible for providing unified 336 legal, financial, and administrative support for operation of the 337 IETF, IAB, and IRTF, and financial support for the operation of 338 the RFC Editor. 340 o Transfer or Dissolution: Consistent with [IETF-LLC-A], the IETF 341 LLC subsidiary may be transferred from ISOC to another 342 organization, at the request of either party. Similarly, the IETF 343 LLC may be dissolved if necessary. Should either event occur, the 344 IETF community should be closely involved in any decisions and 345 plans. Any transfer, transition, or dissolution should be 346 conducted carefully and with minimal potential disruption to the 347 IETF. 349 The transparency and responsiveness principles are designed to 350 address the concern outlined in Section 3.3 of 351 [I-D.haberman-iasa20dt-recs] about the need for improved timeliness 352 of sharing of information and decisions and seeking community 353 comments. The issue of increased transparency was important 354 throughout the IASA 2.0 process, with little to no dissent. It was 355 recognized that there will naturally be confidentiality requirements 356 about some aspects of contracting, personnel matters, and other 357 narrow areas. 359 4.5. Principles of the IETF and ISOC Relationship 361 The principles of the relationship between the IETF and ISOC are 362 outlined in [I-D.ietf-iasa2-rfc2031bis]. In short, the IETF is 363 responsible for the development of the Internet Standards and ISOC 364 aids the IETF by providing it a legal entity within which the IETF 365 LLC exists, as well as with financial support. 367 4.6. Relationship of the IETF LLC Board to the IETF Leadership 369 The IETF LLC Board is directly accountable to the IETF community for 370 the performance of the IASA 2.0. However, the nature of the Board's 371 work involves treating the IESG and IAB as major internal customers 372 of the administrative support services. The Board and the IETF 373 Executive Director should not consider their work successful unless 374 the IESG and IAB are also satisfied with the administrative support 375 that the IETF is receiving. 377 4.7. Review of IETF Executive Director and IETF LLC Board Decisions 379 The IETF LLC Board is directly accountable to the IETF community for 380 the performance of the IASA 2.0, including hiring and managing the 381 IETF Executive Director. In extreme cases of dissatisfaction with 382 the IETF LLC, the IETF community can utilize the recall process as 383 noted in Section 6.7. 385 Anyone in the community of IETF participants may ask the Board for a 386 formal review of a decision or action by the IETF Executive Director 387 or Board if they believe this was not undertaken in accordance with 388 IETF BCPs or IETF LLC Board policies and procedures. 390 A formal request for review must be addressed to the IETF LLC Board 391 chair and must include a description of the decision or action to be 392 reviewed, an explanation of how, in the requestor's opinion, the 393 decision or action violates the BCPs or IASA 2.0 operational 394 guidelines, and a suggestion for how the situation could be 395 rectified. 397 The IETF LLC shall respond to such requests within a reasonable 398 period, typically within 90 days, and shall publicly publish 399 information about the request and the corresponding response and/or 400 result. 402 4.8. Termination and Change 404 Any major change to the IASA 2.0 arrangements shall require a similar 405 level of community consensus and deliberation and shall be reflected 406 by a subsequent Best Current Practice (BCP) document. 408 5. Structure of IASA2 410 5.1. IETF Executive Director and Staff Responsibilities 412 The IETF LLC is led by an IETF Executive Director chosen by the 413 Board. The IETF Executive Director is responsible for managing the 414 day-to-day operations of the IETF LLC, including hiring staff to 415 perform various operational functions. The IETF Executive Director 416 and any staff may be employees or independent contractors. 418 Allowing for the division of responsibilities among multiple staff 419 members and contractors is designed to address some of the concerns 420 raised in Section 3.2 (Lack of Resources) and Section 3.4 (Funding/ 421 Operating Model Mismatch and Rising Costs) of 422 [I-D.haberman-iasa20dt-recs]. 424 Based on the amount of work previously undertaken by the IAD and 425 others involved in the IETF administration, the design of the IETF 426 LLC anticipated that the IETF Executive Director may need to hire 427 multiple additional staff members. For example, resources to manage 428 fundraising, to manage the various contractors that are engaged to 429 fulfill the IETF's administrative needs, and to support outreach and 430 communications were envisioned. 432 The IETF has historically benefitted from the use of contractors for 433 accounting, finance, meeting planning, administrative assistance, 434 legal counsel, tools, and web site support, as well as other services 435 related to the standards process (RFC Editor and IANA). Prior to 436 making the transition from IASA to IASA 2.0, the IETF budget 437 reflected specific support from ISOC for communications and 438 fundraising as well as some general support for accounting, finance, 439 legal, and other services. The division of responsibilities between 440 staff and contractors is at the discretion of the IETF Executive 441 Director and their staff. 443 The IETF has a long history of community involvement in the execution 444 of certain administrative functions, in particular development of 445 IETF tools, the NOC's operation of the meeting network, and some 446 outreach and communications activities conducted by the Education and 447 Mentoring Directorate. The IETF LLC staff is expected to respect the 448 IETF community's wishes about community involvement in these and 449 other functions going forward as long as the staff feels that they 450 can meet the otherwise-stated needs of the community. Establishing 451 the framework to allow the IETF LLC to staff each administrative 452 function as appropriate may require the IETF community to document 453 its consensus expectations in areas where no documentation currently 454 exists. 456 In summary, the IETF Executive Director, with support from the team 457 that they alone direct and lead, is responsible for: 459 o Developing and refining an annual budget and other strategic 460 financial planning documents at the direction of the Board. 462 o Executing on the annual budget, including reporting to the Board 463 regularly with forecasts and actual performance to budget. 465 o Hiring and/or contracting the necessary resources to meet their 466 goals, within the defined limits of the IETF Executive Director's 467 authority and within the approved budget. This includes managing 468 and leading any such resources, including performing regular 469 performance reviews. 471 o Following the pre-approval guidelines set forth by the Board for 472 contracts or other decisions that have financial costs that exceed 473 a certain threshold of significance. Such thresholds are expected 474 to be set reasonably high so that the need for such approvals is 475 infrequent and only occurs when something is truly significant or 476 otherwise exceptional. It is expected that the IETF Executive 477 Director is sufficiently empowered to perform the job on a day-to- 478 day basis, being held accountable for meeting high level goals 479 rather than micromanaged. 481 o Regularly updating the Board on operations and other notable 482 issues as reasonable and appropriate. 484 o Ensuring that all staff and/or other resources comply with any 485 applicable policies established or approved by the Board, such as 486 ethics guidelines and/or a code of conduct. 488 5.2. IETF LLC Board Responsibilities 490 This section is intended to provide a summary of key IETF LLC Board 491 responsibilities, but the precise and legally binding 492 responsibilities are defined in the LLC Agreement [IETF-LLC-A] and 493 applicable law. To the extent to which there are unintentional 494 differences or other confusion between this document and these 495 authoritative sources, these sources will control over this document. 497 Board members have fiduciary obligations imposed by the LLC Agreement 498 and applicable law, including duties of loyalty, care and good faith. 499 The Board is responsible to set broad strategic direction for the 500 LLC, and adopt an annual budget, hire or terminate an IETF Executive 501 Director (or amend the terms of their engagement), adopt any employee 502 benefit plans, consult the relevant IETF communities on matters 503 related to the LLC as appropriate, approve any changes to the LLC 504 governance structure, incur any debt, and approve entering into 505 agreements that that meet a significant materiality threshold to be 506 determined by the Board. The IETF LLC Board is expected to delegate 507 management of day-to-day activities and related decision-making to 508 staff. 510 Per Section 5(d) of the LLC Agreement and as also described in 511 Section 4.4, the Board shall, as appropriate, act transparently and 512 provide the IETF community with an opportunity to review and discuss 513 any proposed changes to the IETF LLC structure prior to their 514 adoption. 516 The role of the Board is to ensure that the strategy and conduct of 517 the IETF LLC is consistent with the IETF's needs - both its concrete 518 needs and its needs for transparency and accountability. The Board 519 is not intended to directly define the IETF's needs; to the extent 520 that is required, the IETF community should document its needs in 521 consensus-based RFCs (e.g., as the community did in 522 [I-D.ietf-mtgvenue-iaoc-venue-selection-process]) and provide more 523 detailed input via consultations with the Board (such as takes place 524 on email discussion lists or at IETF meetings). 526 Key IETF LLC Board responsibilities include: 528 o Set broad strategic direction for the LLC. 530 o Hire or terminate an IETF Executive Director (or amending the 531 terms of their engagement). 533 o Delegate management of day-to-day activities and related decision- 534 making to staff. 536 o Adopt any employee benefit plans. 538 o Consult the relevant IETF communities on matters related to the 539 LLC, as appropriate. 541 o Approve any changes to the LLC governance structure. 543 o Adopt an annual budget and, as necessary, incur any debt. 545 o Prepare accurate and timely financial statements for ISOC, and in 546 accordance with generally accepted accounting principles. 548 o Provide assistance to help facilitate ISOC's tax compliance, 549 including but not limited to assistance related to preparing the 550 Form 990 and responding to any IRS questions and audits. 552 o Approve entering into agreements that that meet a significant 553 materiality threshold to be determined by the Board. 555 o Limit its activities to the purposes as set forth in Section 4 of 556 the LLC Agreement, in a manner consistent with ISOC's charitable 557 purposes. 559 o Establish an investment policy. 561 o Use best efforts to conduct all of its activities in strict 562 compliance with the LLC Agreement and all applicable laws, rules 563 and regulations. 565 o Ensure that IETF LLC is run in a manner that is transparent and 566 accountable to the IETF community; 568 o Develop policies, including those noted in Section 8), procedures, 569 and a compliance program. 571 o Obtain Commercial General Liability and other appropriate 572 insurance policies, with agreed-upon coverage limits. 574 o Recruit new Directors for consideration in all of the various 575 appointment processes. 577 5.3. Board Design Goals 579 A goal of this Board composition is to balance the need for the IETF 580 LLC to be accountable to the IETF community with the need for this 581 Board to have the expertise necessary to oversee a small non-profit 582 company. The Board is smaller than the previous IAOC and the other 583 leadership bodies of the IETF, in part to keep the Board focused on 584 its rather limited set of strategic responsibilities as noted in 585 Section 5.2. 587 This board structure, with limited strategic responsibilities noted 588 in Section 5.2 and limited size, together with the staff 589 responsibilities noted in Section 5.1, is designed to overcome the 590 challenges described in Section 3.1.4 of [I-D.haberman-iasa20dt-recs] 591 concerning oversight. This establishes a clear line of oversight 592 over staff performance: the IETF LLC Board oversees the IETF 593 Executive Director's performance and has actual legal authority to 594 remove a non-performing IETF Executive Director. The IETF Executive 595 Director is responsible for the day-to-day operation of the IETF LLC. 597 Finally, the Board would be expected to operate transparently, to 598 further address the concern raised in Section 3.3 of 599 [I-D.haberman-iasa20dt-recs]. The default transparency rule arrived 600 at during the IASA 2.0 design process is detailed above in 601 Section 4.4. The Board will need to establish how it will meet that 602 commitment. 604 6. IETF LLC Board Membership, Selection and Accountability 606 The section outlines the composition of the IETF LLC Board, selection 607 of IETF LLC Board Directors, and related details. 609 6.1. Board Composition 611 There is a minimum of 5 directors, expandable to 6 or 7. 613 o 1 IETF Chair or delegate selected by the IESG 615 o 1 Appointed by the ISOC Board of Trustees 617 o 3 Selected by the IETF NomCom, confirmed by the IESG 619 o Up to 2 Appointed by the IETF LLC board itself, on an as-needed 620 basis, confirmed by the IESG 622 For the first slot listed above, the presumption is that the IETF 623 Chair will serve on the board. At the IESG's discretion, another 624 area director may serve instead, or exceptionally the IESG may run a 625 selection process to appoint a director. The goal of having this 626 slot on the board is to maintain coordination and communication 627 between the board and the IESG. 629 6.2. IETF LLC-Appointed Directors 631 As noted above, a maximum of two Directors may be appointed by the 632 IETF LLC Board. They can obviously choose to appoint none, one, or 633 two. These appointments need not be on an exceptional basis, but 634 rather be routine, and may occur at any time of the year since it is 635 on an as-needed basis. 637 The appointment of a Board-appointed Director requires a two-thirds 638 majority vote of the Directors then in office, and the appointee 639 shall take office immediately upon appointment. The term of each 640 appointment is designated by the Board, with the maximum term being 641 three years, or until their earlier resignation, removal or death. 642 The Board may decide on a case-by-case basis how long each term shall 643 be, factoring in the restriction for consecutive terms in 644 Section 6.4. 646 6.3. Recruiting IETF LLC Board Directors 648 The Board itself is expected to take an active role in recruiting 649 potential new Directors, regardless of the process that may be used 650 to appoint them. In particular, the NomCom is primarily focused on 651 considering requirements expressed by the Board and others, reviewing 652 community feedback on candidates, conducting candidate interviews, 653 and ultimately appointing Directors. The Board and others can 654 recruit potential Directors and get them into the consideration 655 process of the NomCom or into open considerations processes of the 656 other appointing bodies if those bodies choose to use such processes. 658 6.4. IETF LLC Board Director Term Length 660 The term length for a Director is three years. The exceptions to 661 this guideline are: 663 o For the terms for some Directors during the first full formation 664 of the IETF LLC Board in order to establish staggered terms and 665 for any appointments to fill a vacancy. 667 o The Director slot occupied by the IETF Chair ex officio or a 668 delegate selected by the IESG will serve a two-year term. This 669 makes the term length for this slot the same as the term lengths 670 established in [I-D.ietf-iasa2-rfc7437bis], Section 3.4. 672 6.5. IETF LLC Board Director Limit 674 A director may serve no more than two consecutive terms. A director 675 cannot serve a third term until three years have passed since their 676 second consecutive term. An exception is if a Director role is 677 occupied by the IETF Chair ex officio, since that person's service is 678 governed instead by the term lengths established in 679 [I-D.ietf-iasa2-rfc7437bis], Section 3.4. 681 An exception to the two consecutive term rule is for an IETF LLC- 682 appointed Director. For such a Director, they may serve only one 683 term via this appointment method, after which any subsequent terms 684 would be occur via other appointment or selection processes (such as 685 via the NomCom process). 687 Lastly, partial terms of less than three years for the initial 688 appointments to the first full board, for which some Directors will 689 have terms of one or two years, do not count against the term limit. 691 The limit on consecutive terms supports the healthy regular 692 introduction of new ideas and energy into the Board and mitigates 693 potential long-term risk of ossification or conflict, without 694 adversely impacting the potential pool of director candidates over 695 time. 697 6.6. Staggered Terms 699 The Internet Society Board of Trustees, the IESG, the Nominating 700 Committee, and the Board are expected to coordinate with each other 701 to ensure that collectively their appointment or selection processes 702 provide for no more than three Directors' terms concluding in the 703 same year. 705 6.7. IETF LLC Board Director Removal 707 NomCom-appointed Directors may be removed with or without cause. A 708 vote in favor of removal must be no fewer than the number of 709 Directors less two. So for example, if there are seven directors, 710 then five votes are required. Directors may also be removed via the 711 IETF recall process defined in [I-D.ietf-iasa2-rfc7437bis], 712 Section 7. 714 6.8. Filling an IETF LLC Board Director Vacancy 716 It shall be the responsibility of each respective body that appointed 717 or selected a Director that vacates the Board to appoint a new 718 Director to fill the vacancy. For example, if a Director selected by 719 the NomCom departs the Board prior to the end of their term for 720 whatever reason, then it is the responsibility of the NomCom (using 721 its mid-term rules, as specified in [I-D.ietf-iasa2-rfc7437bis], 722 Section 3.5) as the original appointing body to designate a 723 replacement that will serve out the remainder of the term of the 724 departed Director. However, this obligation will not apply to 725 vacancies in Board-appointed positions. 727 6.9. Quorum 729 At all synchronous live meetings of the Board, two-thirds of the 730 Directors then in office shall constitute a quorum for the 731 transaction of business. Unless a greater affirmative vote is 732 expressly required for an action under applicable law, the LLC 733 Agreement, or an applicable Board policy, the affirmative vote of 734 two-thirds of the Directors then in office shall be an act of the 735 Board. 737 6.10. Board Voting 739 Board decisions may be made either by vote communicated in a 740 synchronous live (including telephonic and video) meeting, or via an 741 asynchronous written (including electronic) process. Absentee voting 742 and voting by proxy shall not be permitted. If a quorum is not 743 present at any meeting of the Board, the Directors present may 744 adjourn the meeting from time to time, without notice other than 745 announcement at the meeting, until a quorum is present. Voting 746 thresholds for Director removal are described in Section 6.7. 748 6.11. Interim Board 750 An initial interim Board was necessary in order to legally form and 751 bootstrap the IETF LLC. As a result, an Interim Board was formed on 752 a temporary basis until the first full board was constituted. 754 The interim Board was comprised of: 756 o The IETF chair, ex officio 758 o The IAOC chair, ex officio 760 o The IAB chair, ex officio 762 o One ISOC trustee, selected by the ISOC Board of Trustees 764 6.12. Board Positions 766 Following the formation of the first permanent Board, and annually 767 thereafter, the Directors shall elect a Director to serve as Board 768 Chair by majority vote. The IETF, IAB and IRTF chairs, and the chair 769 of ISOC's Board, will be ineligible for this Board Chair role. The 770 Board may also form committees of the Board and/or define other roles 771 for Board Directors as necessary. 773 7. IETF LLC Funding 775 The IETF LLC must function within a budget of costs balanced against 776 limited revenues. The IETF community expects the IETF LLC to work to 777 attain that goal, in order to maintain a viable support function that 778 provides the environment within which the work of the IETF, IAB, 779 IRTF, and RFC Editor can remain vibrant and productive. 781 The IETF LLC was generating income from a few key sources at the time 782 that this document was written, as enumerated below. Additional 783 sources of income may be developed in the future, within the general 784 bounds noted in Section 7.8, and some of these may decline in 785 relevance or go away. As a result this list is subject to change 786 over time and is merely an example of the primary sources of income 787 for the IETF LLC at the time of this writing: 789 1. ISOC support 791 2. IETF meeting revenues 793 3. Sponsorships (monetary and/or in-kind) 795 4. Donations (monetary and/or in-kind) 797 7.1. Financial Statements 799 As noted in Section 5.2, the IETF LLC must comply with relevant tax 800 laws, such as filing an annual IRS Form 990. Other official 801 financial statements may also be required. 803 In addition to these official financial statements and forms, the 804 IETF LLC is also expected to report on a regular basis to the IETF 805 community on the current and future annual budget, budget forecasts 806 vs. actuals over the course of a fiscal year, and on other 807 significant projects as needed. This regular reporting to the IETF 808 community is expected to be reported in the form of standard 809 financial statements that reflect the income, expenses, assets, and 810 liabilities of the IETF LLC. 812 7.2. Bank and Investment Accounts 814 The IETF LLC maintains its own bank account, separate and distinct 815 from ISOC. The IETF LLC may at its discretion create additional 816 accounts as needed. Similarly, the IETF LLC may as needed create 817 investment accounts in support of its financial goals and objectives. 819 7.3. Financial Audits 821 The IETF LLC is expected to retain and work with an independent 822 auditor. Reports from the auditor are expected to be shared with the 823 IETF community and other groups and organizations as needed or as 824 required by law. 826 7.4. ISOC Financial Support 828 ISOC currently provides significant financial support to the IETF 829 LLC. Exhibit B of the [IETF-LLC-A] summarizes the financial support 830 from ISOC for the foreseeable future. It is expected that this 831 support will be periodically reviewed and revised, via a cooperative 832 assessment process between ISOC and the IETF LLC. 834 7.5. IETF Meeting Revenues 836 Meeting revenues are another important source of funding that 837 supports the IETF, coming mainly from the fees paid by IETF meeting 838 participants. The IETF Executive Director sets those meeting fees, 839 in consultation with other IETF LLC staff and the IETF community, 840 with approval by the IETF LLC Board. Setting these fees and 841 projecting the number of participants at future meetings is a key 842 part of the annual budget process. 844 7.6. Sponsorships and Donations to the IETF LLC 846 Sponsorships and donations are an essential component of the 847 financial support for the IETF. Within the general bounds noted in 848 Section 7.8, the IETF LLC is responsible for fundraising activities 849 in order to establish, maintain, and grow a strong foundation of 850 donation revenues. This can and does include both direct financial 851 contributions as well as in-kind contributions, such as equipment, 852 software licenses, and services. 854 Sponsorships and donations to the IETF LLC do not (and must not) 855 convey to sponsors and donors any special oversight or direct 856 influence over the IETF's technical work or other activities of the 857 IETF or IETF LLC. This helps ensure that no undue influence may be 858 ascribed to those from whom funds are raised, and so helps to 859 maintain an open and consensus-based IETF standards process. 861 To the extent that the IETF LLC needs to undertake any significant 862 special projects for the IETF, the IETF LLC may need to fundraise 863 distinctly for those special projects. As a result, the IETF LLC may 864 conduct fundraising to support the IETF in general as well as one or 865 more special fundraising efforts (which may also be accounted for 866 distinctly and be held in a separate bank account or investment, as 867 needed). 869 7.7. Focus of Funding Support 871 The IETF LLC exists to support the IETF, IAB, and IRTF. Therefore, 872 the IETF LLC's funding and all revenues, in-kind contributions, and 873 other income that comprise that funding shall be used solely to 874 support activities related to the IETF, IAB, IRTF, and RFC Editor, 875 and for no other purposes. 877 7.8. Charitable Fundraising Practices 879 When the IETF LLC conducts fundraising, it substantiates charitable 880 contributions on behalf of ISOC - meaning that according to US tax 881 law, the IETF LLC must send a written acknowledgment of contributions 882 to donors. The IETF LLC evaluates and facilitates state, federal, 883 and other applicable law and regulatory compliance for ISOC and/or 884 the LLC with respect to such fundraising activities. In addition, 885 the IETF LLC ensures that all fundraising activities are conducted in 886 compliance with any policies developed by the IETF LLC, including but 887 not limited to those noted in Section 8. 889 7.9. Operating Reserve 891 An initial target operating reserve has been specified in Exhibit B 892 of the [IETF-LLC-A]. That says that the IETF LLC should maintain an 893 operating reserve equal to the IETF LLC's budgeted Net Loss for 2019 894 multiplied times three. The IETF LLC, in cooperation with ISOC, may 895 regularly review the financial target for this reserve fund, as noted 896 in the [IETF-LLC-A] or as otherwise necessary. 898 Should the IETF LLC generate an annual budget surplus, it may choose 899 to direct all or part of the surplus towards the growth of the 900 operating reserve. 902 7.10. Annual Budget Process 904 As noted in Section 4.3, the IETF LLC is responsible for managing the 905 IETF's finances and budget. A key part of this responsibility is 906 establishing, maintaining, and successfully meeting an annual budget. 907 This is essential to the continued operation and vibrancy of the 908 IETF's technical activities and establishes trust with ISOC, 909 sponsors, and donors that funds are being appropriately spent, and 910 that financial oversight is being conducted properly. This is also 911 essential to the IETF LLC meeting applicable legal and tax 912 requirements and is a core part of the Board's fiduciary 913 responsibilities. 915 As explained in Section 5.1, the IETF Executive Director is expected 916 to develop, execute, and report on the annual budget. Regular 917 reporting is expected to include forecast vs. budget statements, 918 including updated projections of income and expenses for the full 919 fiscal year. 921 The Board, as explained in Section 5.2, is expected to review and 922 approve the budget, as well as to provide ongoing oversight of the 923 budget and of any other significant financial matters. 925 The annual budget is expected to be developed in an open, 926 transparent, and collaborative manner, in accordance with 927 Section 4.4. The specific timeline for the development, review, and 928 approval of the IETF LLC annual budget is established by the Board 929 and may be revised as needed. 931 8. IETF LLC Policies 933 The Board is expected to maintain policies as necessary to achieve 934 the goals of the IETF LLC, meet transparency expectations of the 935 community, comply with applicable laws or regulations, or for other 936 reasons as appropriate. All policies are expected to be developed 937 with input from the IETF community. Some policies provided by ISOC 938 and past policies developed by the previous IAOC may provide a useful 939 starting point for the Board to consider. 941 8.1. Conflict of Interest Policy 943 The Board is expected to maintain a Conflict of Interest policy for 944 the IETF LLC. While the details are determined by the Board, at a 945 minimum such policy is expected to include the following: 947 o The IETF, ISOC Board, IAB, or IRTF chair cannot be chair of the 948 IETF LLC Board, though they may serve as a Director. 950 o A Director cannot be a paid consultant or employee of the IETF 951 Executive Director or their sub-contractors, nor a paid consultant 952 or employee of ISOC. 954 8.2. Other Policies 956 The Board is expected to maintain additional policies for the IETF 957 LLC as necessary, covering Directors, employees, and contractors, 958 concerning issues such as: 960 o Acceptance of gifts and other non-cash compensation; 962 o Travel and expense reimbursement; 964 o Anti-bribery; 966 o Code of conduct; 968 o Anti-harassment; 970 o Non-discrimination; 972 o Whistleblower; 974 o Document retention; 976 o Export controls; 978 o Anti-terrorism sanctions; 980 o Data protection and privacy; 982 o Social media 984 8.3. Compliance 986 The IETF LLC is expected to implement a compliance program to ensure 987 its compliance with all applicable laws, rules and regulations, 988 including without limitation laws governing bribery, anti-terrorism 989 sanctions, export controls, data protection/privacy, as well as other 990 applicable policies noted in Section 8. In addition, actions and 991 activities of the IETF LLC must be consistent with 501(c)(3) 992 purposes. 994 The IETF LLC is expected report to ISOC and the IETF community on the 995 implementation of its compliance plan on an annual basis. 997 9. Three-Year Assessment 999 The IETF LLC, with the involvement of the community, shall conduct 1000 and complete an assessment of the structure, processes, and operation 1001 of IASA 2.0 and the IETF LLC. This should be presented to the 1002 community after a period of roughly three years of operation. The 1003 assessment may potentially include recommendations for improvements 1004 or changes to the IASA2 and/or IETF LLC. 1006 10. Security Considerations 1008 This document describes the structure of the IETF's Administrative 1009 Support Activity (IASA), version 2 (IASA2). It introduces no 1010 security considerations for the Internet. 1012 11. IANA Considerations 1014 This document has no IANA considerations in the traditional sense. 1015 However, some of the information in this document may affect how the 1016 IETF standards process interfaces with the IANA, so the IANA may be 1017 interested in the contents. 1019 12. Pronouns 1021 This document has used "they" and "their" as a non-gender-specific 1022 pronoun to refer to a single individual. 1024 13. Acknowledgments 1026 Thanks to Jari Arkko, Richard Barnes, Brian E Carpenter, Alissa 1027 Cooper, John C Klensin, Bob Hinden, Jon Peterson, Sean Turner and the 1028 IASA2 Working Group for discussions of possible structures, and to 1029 the attorneys of Morgan Lewis and Brad Biddle for legal advice. 1031 14. References 1033 14.1. Normative References 1035 [I-D.ietf-iasa2-rfc2031bis] 1036 Camarillo, G. and J. Livingood, "The IETF-ISOC 1037 Relationship", draft-ietf-iasa2-rfc2031bis-04 (work in 1038 progress), February 2019. 1040 [I-D.ietf-iasa2-rfc7437bis] 1041 Kucherawy, M., Hinden, R., and J. Livingood, "IAB, IESG, 1042 IETF Trust and IETF LLC Selection, Confirmation, and 1043 Recall Process: Operation of the IETF Nominating and 1044 Recall Committees", draft-ietf-iasa2-rfc7437bis-05 (work 1045 in progress), January 2019. 1047 [IETF-LLC-A] 1048 The Internet Society, "Limited Liability Company Agreement 1049 of IETF Administration LLC", August 2018, 1050 . 1053 14.2. Informative References 1055 [I-D.haberman-iasa20dt-recs] 1056 Haberman, B., Arkko, J., Daigle, L., Livingood, J., Hall, 1057 J., and E. Rescorla, "IASA 2.0 Design Team 1058 Recommendations", draft-haberman-iasa20dt-recs-03 (work in 1059 progress), November 2018. 1061 [I-D.ietf-iasa2-trust-update] 1062 Arkko, J. and T. Hardie, "Update to the Process for 1063 Selection of Trustees for the IETF Trust", draft-ietf- 1064 iasa2-trust-update-03 (work in progress), February 2019. 1066 [I-D.ietf-mtgvenue-iaoc-venue-selection-process] 1067 Lear, E., "IETF Plenary Meeting Venue Selection Process", 1068 draft-ietf-mtgvenue-iaoc-venue-selection-process-16 (work 1069 in progress), June 2018. 1071 [ietf101-slides] 1072 Hall, J., "IASA 2.0 IETF-101 Slides", n.d., 1073 . 1076 [ietf102-slides] 1077 Hall, J., "IASA 2.0 IETF-102 Slides", n.d., 1078 . 1081 [ISOC] The Internet Society, "Amended and restated By-Laws of the 1082 Internet Society", July 2018, 1083 . 1086 [ML-memo] Morgan Lewis, "Options for New Organization to Conduct 1087 IETF Administrative Support Activities", February 2018, 1088 . 1091 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 1092 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 1093 . 1095 [RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031, 1096 DOI 10.17487/RFC2031, October 1996, 1097 . 1099 [RFC2850] Internet Architecture Board and B. Carpenter, Ed., 1100 "Charter of the Internet Architecture Board (IAB)", 1101 BCP 39, RFC 2850, DOI 10.17487/RFC2850, May 2000, 1102 . 1104 [RFC3233] Hoffman, P. and S. Bradner, "Defining the IETF", BCP 58, 1105 RFC 3233, DOI 10.17487/RFC3233, February 2002, 1106 . 1108 [RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, 1109 DOI 10.17487/RFC3710, February 2004, 1110 . 1112 [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the 1113 IETF Administrative Support Activity (IASA)", BCP 101, 1114 RFC 4071, DOI 10.17487/RFC4071, April 2005, 1115 . 1117 [RFC4333] Huston, G., Ed. and B. Wijnen, Ed., "The IETF 1118 Administrative Oversight Committee (IAOC) Member Selection 1119 Guidelines and Process", BCP 113, RFC 4333, 1120 DOI 10.17487/RFC4333, December 2005, 1121 . 1123 [RFC7691] Bradner, S., Ed., "Updating the Term Dates of IETF 1124 Administrative Oversight Committee (IAOC) Members", 1125 BCP 101, RFC 7691, DOI 10.17487/RFC7691, November 2015, 1126 . 1128 [RFC8318] Dawkins, S., "IAB, IESG, and IAOC Selection, Confirmation, 1129 and Recall Process: IAOC Advisor for the Nominating 1130 Committee", BCP 10, RFC 8318, DOI 10.17487/RFC8318, 1131 January 2018, . 1133 Authors' Addresses 1135 Brian Haberman 1136 Johns Hopkins University 1138 Email: brian@innovationslab.net 1139 Joseph Lorenzo Hall 1140 CDT 1142 Email: joe@cdt.org 1144 Jason Livingood 1145 Comcast 1147 Email: jason_livingood@comcast.com