idnits 2.17.1 draft-ietf-iasa2-rfc4071bis-00.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 (December 05, 2018) is 1969 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 1109, but no explicit reference was found in the text == Outdated reference: A later version (-08) exists of draft-ietf-iasa2-rfc2031bis-00 == Outdated reference: A later version (-03) exists of draft-ietf-iasa2-trust-update-02 -- 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 7437 (Obsoleted by RFC 8713) -- 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: 1 error (**), 0 flaws (~~), 5 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: June 8, 2019 Comcast 8 December 05, 2018 10 Structure of the IETF Administrative Support Activity, Version 2.0 11 draft-ietf-iasa2-rfc4071bis-00 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 Internet Administrative Oversight Committee (IAOC) was 25 eliminated, and its oversight and advising functions transferred to 26 the IETF LLC Board. 28 This document describes the structure of the IETF Administrative 29 Support Activity, version 2 (IASA 2.0). It defines the roles and 30 responsibilities of the IETF LLC Board, the IETF Executive Director, 31 and ISOC in the fiscal and administrative support of the IETF 32 standards process. It also defines the membership and selection 33 rules for the IETF LLC Board. 35 This document obsoletes [RFC4071], [RFC4333], and [RFC7691]. 37 Status of This Memo 39 This Internet-Draft is submitted in full conformance with the 40 provisions of BCP 78 and BCP 79. 42 Internet-Drafts are working documents of the Internet Engineering 43 Task Force (IETF). Note that other groups may also distribute 44 working documents as Internet-Drafts. The list of current Internet- 45 Drafts is at https://datatracker.ietf.org/drafts/current/. 47 Internet-Drafts are draft documents valid for a maximum of six months 48 and may be updated, replaced, or obsoleted by other documents at any 49 time. It is inappropriate to use Internet-Drafts as reference 50 material or to cite them other than as "work in progress." 52 This Internet-Draft will expire on June 8, 2019. 54 Copyright Notice 56 Copyright (c) 2018 IETF Trust and the persons identified as the 57 document authors. All rights reserved. 59 This document is subject to BCP 78 and the IETF Trust's Legal 60 Provisions Relating to IETF Documents 61 (https://trustee.ietf.org/license-info) in effect on the date of 62 publication of this document. Please review these documents 63 carefully, as they describe your rights and restrictions with respect 64 to this document. Code Components extracted from this document must 65 include Simplified BSD License text as described in Section 4.e of 66 the Trust Legal Provisions and are provided without warranty as 67 described in the Simplified BSD License. 69 Table of Contents 71 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 72 2. Scope Limitation . . . . . . . . . . . . . . . . . . . . . . 4 73 2.1. LLC Agreement with the Internet Society . . . . . . . . . 4 74 3. Definitions and Principles . . . . . . . . . . . . . . . . . 5 75 3.1. Alphabet Soup . . . . . . . . . . . . . . . . . . . . . . 5 76 3.2. Key Differences From the Old IASA Structure to IASA 2.0 . 6 77 3.3. General IETF LLC Responsibilities . . . . . . . . . . . . 6 78 3.4. IETF LLC Working Principles . . . . . . . . . . . . . . . 7 79 3.5. Principles of the IETF and ISOC Relationship . . . . . . 8 80 3.6. Relationship of the IETF LLC Board to the IETF Leadership 8 81 3.7. IETF LLC Board Decision Making . . . . . . . . . . . . . 9 82 3.8. Review and Appeal of IETF Executive Director and IETF LLC 83 Board Decisions . . . . . . . . . . . . . . . . . . . . . 9 84 3.9. Community Consensus and Grant of Authority . . . . . . . 10 85 3.10. Termination and Change . . . . . . . . . . . . . . . . . 10 86 4. Structure of the IASA2 . . . . . . . . . . . . . . . . . . . 11 87 4.1. IETF Executive Director and Staff Responsibilities . . . 11 88 4.2. IETF LLC Board Responsibilities . . . . . . . . . . . . . 12 89 4.3. Board Design Goals . . . . . . . . . . . . . . . . . . . 14 90 5. IETF LLC Board Membership, Selection and Accountability . . . 14 91 5.1. Board Composition . . . . . . . . . . . . . . . . . . . . 14 92 5.2. IETF LLC-Appointed Directors . . . . . . . . . . . . . . 15 93 5.3. Recruiting IETF LLC Board Directors . . . . . . . . . . . 15 94 5.4. IETF LLC Board Director Term Length . . . . . . . . . . . 15 95 5.5. IETF LLC Board Director Limit . . . . . . . . . . . . . . 16 96 5.6. Staggered Terms . . . . . . . . . . . . . . . . . . . . . 16 97 5.7. IETF LLC Board Director Removal . . . . . . . . . . . . . 16 98 5.8. Filling an IETF LLC Board Director Vacancy . . . . . . . 17 99 5.9. Quorum . . . . . . . . . . . . . . . . . . . . . . . . . 17 100 5.10. Board Voting . . . . . . . . . . . . . . . . . . . . . . 17 101 5.11. Interim Board . . . . . . . . . . . . . . . . . . . . . . 17 102 5.12. Board Positions . . . . . . . . . . . . . . . . . . . . . 18 103 6. IETF LLC Funding . . . . . . . . . . . . . . . . . . . . . . 18 104 6.1. Financial Statements . . . . . . . . . . . . . . . . . . 18 105 6.2. Bank and Investment Accounts . . . . . . . . . . . . . . 19 106 6.3. Financial Audits . . . . . . . . . . . . . . . . . . . . 19 107 6.4. ISOC Financial Support . . . . . . . . . . . . . . . . . 19 108 6.5. IETF Meeting Revenues . . . . . . . . . . . . . . . . . . 19 109 6.6. Donations to the IETF LLC . . . . . . . . . . . . . . . . 19 110 6.7. Funding Supports the IETF . . . . . . . . . . . . . . . . 20 111 6.8. Charitable Fundraising Practices . . . . . . . . . . . . 20 112 6.9. Operating Reserve . . . . . . . . . . . . . . . . . . . . 20 113 6.10. Annual Budget Process . . . . . . . . . . . . . . . . . . 20 114 7. IETF LLC Policies . . . . . . . . . . . . . . . . . . . . . . 21 115 7.1. Conflict of Interest Policy . . . . . . . . . . . . . . . 21 116 7.2. Other Policies . . . . . . . . . . . . . . . . . . . . . 21 117 7.3. Compliance . . . . . . . . . . . . . . . . . . . . . . . 22 118 8. Three-Year Assessment . . . . . . . . . . . . . . . . . . . . 22 119 9. Security Considerations . . . . . . . . . . . . . . . . . . . 23 120 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 121 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 122 12. Informative References . . . . . . . . . . . . . . . . . . . 23 123 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 125 1. Introduction 127 The IETF Administrative Support Activity (IASA) was originally 128 established in 2005. In the years since then, the needs of the IETF 129 evolved in ways that required changes to its administrative 130 structure. The purpose of this document is to document and describe 131 the IASA 2.0 structure. 133 Under IASA 2.0, the work of the IETF's administrative and fundraising 134 tasks is conducted by an administrative organization, the IETF 135 Administration Limited Liability Company ("IETF LLC"). Under this 136 structure, the Internet Administrative Oversight Committee (IAOC) was 137 eliminated, and its oversight and advising functions transferred to 138 the IETF LLC Board. 140 [I-D.haberman-iasa20dt-recs] discusses the challenges facing the 141 original IASA structure as well as several options for reorganizing 142 the IETF's administration under different legal structures. This 143 document outlines how the chosen option is structured and describes 144 how the organization fits together with existing and new IETF 145 community structures. 147 The point of the IASA2 WG and process has been to solicit community 148 input about how to address the challenges identified in 149 [I-D.haberman-iasa20dt-recs], and included much debate on the IASA2 150 mailing list and the IASA2 working group meetings at IETF 101 151 [ietf101-slides] and IETF 102 [ietf102-slides]. 153 Under IASA 2.0, most of the responsibilities that [RFC4071] assigned 154 to the IETF Administrative Director (IAD) and the Internet Society 155 (ISOC) were transferred to the IETF LLC and IETF Administration LLC 156 Executive Director (IETF Executive Director). It is the job of the 157 IETF LLC to meet the administrative needs of the IETF and to ensure 158 that the IETF LLC meets the needs of the IETF community. 160 Eliminating the IAOC meant that changes were required in how trustees 161 could be appointed to the IETF Trust. The details of how this is 162 done are outside the scope of this document but are covered in 163 [I-D.ietf-iasa2-trust-update]. 165 This document obsoletes [RFC4071], which specified the original IASA, 166 [RFC4333], which specified the selection guidelines and process for 167 IAOC members and [RFC7691], which specified terms for IAOC members. 169 2. Scope Limitation 171 The document does not propose any changes to anything related to the 172 oversight or steering of the standards process as currently conducted 173 by the Internet Engineering Steering Group (IESG) and Internet 174 Architecture Board (IAB), the appeals chain, the process for making 175 and confirming IETF and IAB appointments, the IETF Nominating 176 Committee (NomCom), the Internet Research Task Force (IRTF), or 177 ISOC's memberships in or support of other organizations. 179 2.1. LLC Agreement with the Internet Society 181 The LLC Agreement between the IETF LLC and ISOC [IETF-LLC-A] is also 182 out of scope for this document, however this document depends on the 183 LLC Agreement and will refer to it for certain aspects of the legal 184 relationship between the IETF LLC and ISOC. The LLC Agreement was 185 developed between legal representatives of the IETF and ISOC and 186 includes all critical terms of the relationship, while still enabling 187 maximum unilateral flexibility for the IETF LLC Board. The LLC 188 Agreement includes only basic details about how the IETF LLC Board 189 manages itself or manages IETF LLC staff, so that the IETF LLC Board 190 has flexibility to make changes without amending the agreement. The 191 IETF LLC Board can independently develop policy or procedures 192 documents that fill gaps. 194 3. Definitions and Principles 196 3.1. Alphabet Soup 198 Although most of the terms, abbreviations, and acronyms used in this 199 document are reasonably well known, first-time readers may find this 200 alphabet soup confusing. This section therefore attempts to provide 201 a quick summary. 203 IAB: Internet Architecture Board (see [RFC2026], [RFC2850]). 205 IAD: IETF Administrative Director, a role obsoleted by this document 206 and the ISOC/IETF LLC Agreement ([IETF-LLC-A]) and replaced by the 207 IETF LLC Executive Director. 209 IAOC: IETF Administrative Oversight Committee, a committee that 210 oversaw IETF administrative activity, obsoleted by this document and 211 replaced by the IETF LLC Board. (The IETF Trust function of the 212 former IAOC was not included in the new responsibilities of the IETF 213 LLC Board (See [I-D.ietf-iasa2-trust-update]).) 215 IASA: The original IETF Administrative Support Activity, defined by 216 [RFC4071] and obsoleted by this document and the ISOC/IETF LLC 217 Agreement ([IETF-LLC-A]). 219 IASA 2.0: Version 2.0 of the IETF Administrative Support Activity, 220 defined by this document. 222 IESG: Internet Engineering Steering Group (see [RFC2026], [RFC3710]). 224 IETF: Internet Engineering Task Force (see [RFC3233]). 226 IETF Administration LLC: The legal entity - a disregarded Limited 227 Liability Company (LLC) of The Internet Society - established to 228 house IASA2, specified by the ISOC/IETF LLC Agreement ([IETF-LLC-A]). 229 Also referred to as "IETF LLC" or just the "LLC". 231 IETF LLC Executive Director: the executive director for the IETF 232 Administration Limited Liability Company, responsible for day-to-day 233 administrative and operational direction (See Section 4.1). Also 234 referred to as "IETF Executive Director". (Note that the title of 235 "IETF Executive Director" in older documents such as [RFC2026] is now 236 "Managing Director, IETF Secretariat".) 237 IETF LLC Board: The Board of Directors of the IETF LLC - formally a 238 multi-member "manager" of the IETF LLC on behalf of ISOC (See 239 Section 4.2). 241 ISOC: Internet Society (see [RFC2031] and [ISOC]). 243 3.2. Key Differences From the Old IASA Structure to IASA 2.0 245 o The IAOC and IAD roles defined in RFC 4071 were eliminated. 247 o The former ISOC and IAD responsibilities were assigned to a new 248 organization, IETF Administration LLC. 250 o The Board of Directors of the IETF LLC - formally a multi-member 251 "manager" of the IETF LLC on behalf of ISOC - assumed the 252 oversight responsibilities of the IAOC. 254 o The Board of the IETF LLC is more focused on strategy and 255 oversight than the IAOC was, with the IETF Executive Director and 256 their team in charge of day-to-day operations. 258 o The IAD role was replaced with the IETF Executive Director role. 260 o The role that was previously referred to as "IETF Executive 261 Director" in older documents such as [RFC2026] was replaced with 262 "Managing Director, IETF Secretariat". 264 3.3. General IETF LLC Responsibilities 266 The IETF LLC was established to provide administrative support to the 267 IETF. It has no authority over the standards development activities 268 of the IETF. 270 The responsibilities of the IETF LLC are: 272 o Operations. The IETF LLC is responsible for supporting the 273 ongoing operations of the IETF, including meetings and non-meeting 274 activities. 276 o Finances. The IETF LLC is responsible for managing the IETF's 277 finances and budget. 279 o Fundraising. The IETF LLC is responsible for raising money on 280 behalf of the IETF. 282 o Compliance. The IETF LLC is responsible for establishing and 283 enforcing policies to ensure compliance with applicable laws, 284 regulations, and rules. 286 The manner by which these responsibilities under the IETF LLC are 287 organized is intended to address the problems described in Sections 288 3.1.1., 3.1.2, and 3.1.3 of [I-D.haberman-iasa20dt-recs]. 289 Specifically, this is intended to bring greater clarity around roles, 290 responsibilities, representation, decision-making, and authority. 292 In addition, by having the IETF LLC manage the IETF's finances and 293 conduct the IETF's fundraising, confusion about who is responsible 294 for representing the IETF to sponsors and who directs the uses of 295 sponsorship funds should have been eliminated. Finally, having the 296 IETF LLC reside in a defined, distinct legal entity, and taking 297 responsibility for operations, enables the organization to execute 298 its own contracts without the need for review and approval by ISOC. 300 3.4. IETF LLC Working Principles 302 The IETF LLC is expected to conduct its work according to the 303 following principles, subject to any reasonable confidentiality 304 obligations: 306 o Transparency. The IETF LLC is expected to keep the IETF community 307 informed about its work and to engage with the community to obtain 308 consensus-based community input on key issues and otherwise as 309 needed. The IETF community expects complete visibility into the 310 financial and legal structure of the IETF LLC. This includes 311 information about the IETF LLC annual budget and associated 312 regular financial reports, results of financial and any other 313 independent audits, tax filings, significant contracts or other 314 significant long-term financial commitments that bind the IETF 315 LLC. As discussed in [ietf101-slides], whatever doesn't have a 316 specific justification for being kept confidential is expected to 317 be made public. The IETF LLC Board is expected to develop and 318 maintain a public list of confidential items, describing the 319 nature of the information and the reason for confidentiality. 321 o Responsiveness to the community. The IETF LLC is expected to act 322 consistently with the documented consensus of the IETF community, 323 to be responsive to the community's needs, and to adapt its 324 decisions in response to consensus-based community feedback. 326 o Diligence. The IETF LLC is expected to act responsibly so as to 327 minimize risks to IETF participants and to the future of the IETF 328 as a whole, such as financial risks. 330 o Unification: The IETF LLC is reponsible for providing unified 331 legal, financial, and administrative support for operation of the 332 IETF, IAB, IESG, IRTF, and RFC Editor. 334 o Transfer or Dissolution: Consistent with [IETF-LLC-A], the IETF 335 LLC subsidiary may be transferred from ISOC to another 336 organization, at the request of either party. Similarly, the IETF 337 LLC may be dissolved if necessary. Should either event occur, the 338 IETF community should be closely involved in any decisions and 339 plans, and any tranfer, transition, or dissolution conducted 340 carefully and with minimal potential disruption to the IETF. 342 The transparency and responsiveness principles are designed to 343 address the concern outlined in Section 3.3 of 344 [I-D.haberman-iasa20dt-recs] about the need for improved timeliness 345 of sharing of information and decisions and seeking community 346 comments. The issue of increased transparency was important 347 throughout the IASA 2.0 process, with little to no dissent. It was 348 recognized that there will naturally be a confidentiality requirement 349 about some aspects of hotel contracting, personnel matters, and other 350 narrow areas. 352 3.5. Principles of the IETF and ISOC Relationship 354 ISOC and the IETF have historically been philosophically aligned. 355 The principles of the relationship between the IETF and ISOC are 356 outlined in [I-D.ietf-iasa2-rfc2031bis]. ISOC's connection with the 357 IETF community has always played an important role in its policy 358 work. ISOC has always been an advocate for multistakeholder 359 processes, which includes the technical community. Open standards 360 are an explicit part of one of the focus areas in ISOC's mission: 361 Advancing the development and application of Internet infrastructure, 362 technologies, and open standards. 364 On a practical level, the IETF LLC is a distinct entity (a 365 disregarded entity) of ISOC. The IETF remains responsible for the 366 development and quality of the Internet Standards. ISOC aids the 367 IETF by providing it a legal entity within which the IETF LLC exists, 368 as well as with financial support. ISOC has no influence whatsoever 369 on the technical content of Internet Standards. 371 3.6. Relationship of the IETF LLC Board to the IETF Leadership 373 The IETF LLC Board is directly accountable to the IETF community for 374 the performance of the IASA 2.0. However, the nature of the IETF LLC 375 Board's work involves treating the IESG and IAB as major internal 376 customers of the administrative support services. The IETF LLC Board 377 and the IETF Executive Director should not consider their work 378 successful unless the IESG and IAB are also satisfied with the 379 administrative support that the IETF is receiving. 381 3.7. IETF LLC Board Decision Making 383 The IETF LLC Board attempts to reach consensus on all decisions. If 384 the IETF LLC Board cannot achieve a consensus decision, then the IETF 385 LLC Board may decide by voting. 387 The IETF LLC Board decides the details about its decision-making 388 rules, including its rules for quorum (see Section 5.9), conflict of 389 interest (see Section 7.1), and breaking of ties. These rules are 390 expected to be public. 392 All IETF LLC Board decisions are expected to be recorded in IETF LLC 393 Board minutes, and IETF LLC Board minutes are expected to be 394 published in a timely fashion. 396 3.8. Review and Appeal of IETF Executive Director and IETF LLC Board 397 Decisions 399 The IETF LLC Board is directly accountable to the IETF community for 400 the performance of the IASA 2.0. In order to achieve this, the IETF 401 LLC Board and IETF Executive Director are expected to ensure that 402 guidelines are developed for regular operational decision making. 403 Where appropriate, these guidelines should be developed with public 404 input. In all cases, they must be made public. 406 If a member of the IETF community questions whether a decision or 407 action of the IETF Executive Director or the IETF LLC Board has been 408 undertaken in accordance with IETF BCPs or IASA 2.0 operational 409 guidelines, or questions whether the IETF LLC has created and 410 maintained appropriate guidelines, he or she may ask the IETF LLC 411 Board for a formal review of the decision or action. 413 The request for review should be addressed to the IETF LLC Board 414 chair and should include a description of the decision or action to 415 be reviewed, an explanation of how, in the requestor's opinion, the 416 decision or action violates the BCPs or operational guidelines, and a 417 suggestion for how the situation could be rectified. All requests 418 for review shall be posted publicly, and the IETF LLC Board is 419 expected to respond publicly to these requests within a reasonable 420 period, typically within 90 days. It is up to the IETF LLC Board to 421 determine what type of review and response is required, based on the 422 nature of the review request. Based on the results of the review, 423 the IETF LLC Board may choose to overturn their own decision, to 424 change their operational guidelines to prevent further 425 misunderstandings, to take other action as appropriate, or just to 426 publish the review result and take no other action. 428 If a member of the community is not satisfied with the IETF LLC 429 Board's response to his or her review request, he or she may escalate 430 the issue by appealing the decision or action to the IAB, using the 431 appeals procedures outlined in [RFC2026]. If he or she is not 432 satisfied with the IAB response, he or she can escalate the issue to 433 the ISOC Board of Trustees, as described in [RFC2026]. 435 The reviewing body (the IAB or ISOC Board of Trustees) shall review 436 the decision of the IETF Executive Director or IETF LLC Board to 437 determine whether it was made in accordance with existing BCPs and 438 operational guidelines. As a result of this review, the reviewing 439 body may recommend to the community that the BCPs governing IETF LLC 440 Board actions should be changed. The reviewing body may also advise 441 the IETF LLC Board to modify existing operational guidelines to avoid 442 similar issues in the future and/or it may advise the IETF LLC Board 443 to re-consider their decision or action. It may also recommend that 444 no action be taken, based on the review. 446 In exceptional cases, when no other recourse seems reasonable, the 447 reviewing body may overturn or reverse a non-binding decision or 448 action of the IETF LLC Board. This should be done only after careful 449 consideration and consultation with the IETF LLC Board regarding the 450 ramifications of this action. In no circumstances may the IAB or 451 ISOC Board of Trustees overturn a decision of the IETF LLC Board that 452 involves a binding contract or overturn a personnel-related action 453 (such as hiring, firing, promotion, demotion, performance reviews, 454 salary adjustments, etc.). 456 3.9. Community Consensus and Grant of Authority 458 The IETF is a consensus-based group, and authority to act on behalf 459 of the community requires a high degree of consensus and the 460 continued consent of the community. After a careful process of 461 deliberation, a broad-based community consensus emerged to house the 462 administration of the IETF within the IETF LLC as a disregarded 463 entity of the Internet Society. This document reflects that 464 consensus. 466 3.10. Termination and Change 468 Any major change to the IASA 2.0 arrangements shall require a similar 469 level of community consensus and deliberation and shall be reflected 470 by a subsequent Best Current Practice (BCP) document. 472 4. Structure of the IASA2 474 4.1. IETF Executive Director and Staff Responsibilities 476 The IETF LLC is led by an IETF Executive Director chosen by the 477 Board. The IETF Executive Director is responsible for managing the 478 day-to-day operations of the IETF LLC, including hiring staff to 479 perform various operational functions. The IETF Executive Director 480 and any staff may be employees or independent contractors. 482 Allowing for the division of responsibilities among multiple staff 483 members and contractors is designed to address some of the concerns 484 raised in Section 3.2 (Lack of Resources) and Section 3.4 (Funding/ 485 Operating Model Mismatch and Rising Costs) of 486 [I-D.haberman-iasa20dt-recs]. 488 Based on the amount of work previously undertaken by the IAD and 489 others involved in the IETF administration, the design of the IETF 490 LLC anticipated that the IETF Executive Director may need to hire 491 multiple additional staff members. For example, resources to manage 492 fundraising, to manage the various contractors that are engaged to 493 fulfill the IETF's administrative needs, and to support outreach and 494 communications were envisioned. 496 The IETF has historically benefitted from the use of contractors for 497 accounting, finance, meeting planning, administrative assistance, 498 legal counsel, tools, and web site support, as well as other services 499 related to the standards process (RFC Editor and IANA). Prior to 500 making the transition from IASA to IASA 2.0, the IETF budget 501 reflected specific support from ISOC for communications and 502 fundraising as well as some general support for accounting, finance, 503 legal, and other services. The division of responsibilities between 504 staff and contractors is at the discretion of the IETF Executive 505 Director and his or her staff. 507 The IETF has a long history of community involvement in the execution 508 of certain administrative functions, in particular development of 509 IETF tools, the NOC's operation of the meeting network, and some 510 outreach and communications activities conducted by the Education and 511 Mentoring Directorate. The IETF LLC staff is expected to respect the 512 IETF community's wishes about community involvement in these and 513 other functions going forward as long as the staff feels that they 514 can meet the otherwise-stated needs of the community. Establishing 515 the framework to allow the IETF LLC to staff each administrative 516 function as appropriate may require the IETF community to document 517 its consensus expectations in areas where no documentation currently 518 exists. 520 In summary, the IETF Executive Director, with support from the team 521 that they alone direct and lead, is responsible for: 523 o Developing and refining an annual budget and other strategic 524 financial planning documents at the direction of the IETF LLC 525 Board. 527 o Executing on the annual budget, including reporting to the IETF 528 LLC Board regularly with forecasts and actual performance to 529 budget. 531 o Hiring and/or contracting the necessary resources to meet their 532 goals, within the defined limits of their authority and within the 533 approved budget. This includes managing and leading any such 534 resources, including performing regular performance reviews. 536 o Following the pre-approval guidelines set forth by the IETF LLC 537 Board for contracts or other decisions that have financial costs 538 that exceed a certain threshold of significance. Such thresholds 539 are expected to be set reasonably high so that the need for such 540 approvals is infrequent and only occurs when something is truly 541 significant or otherwise exceptional. It is expected that the 542 IETF Executive Director is sufficiently empowered to perform their 543 job on a day-to-day basis, being held accountable for meeting high 544 level goals rather than micromanaged. 546 o Regularly updating the IETF LLC Board on operations and other 547 notable issues as reasonable and appropriate. 549 o Ensuring that all staff and/or other resources comply with any 550 applicable policies established or approved by the IETF LLC Board, 551 such as ethics guidelines and/or a code of conduct. 553 4.2. IETF LLC Board Responsibilities 555 The IETF LLC Board is responsible for conducting oversight of the 556 IETF LLC's execution of its responsibilities, as described in 557 Section 3.3. They have duties of loyalty, care, and good faith. 558 This includes the responsibility to: 560 o provide strategic direction for the IETF LLC to the IETF Executive 561 Director; 563 o hire, supervise, and manage the employment of the role of the IETF 564 Executive Director of the IETF LLC, including tasks such as 565 hiring, termination, performance review, amendment of employment 566 terms, the award of compensation and other requisite employment 567 benefits or decisions; 569 o adopting any employee benefit plans; 571 o exercising a fiduciary duty to ensure that IETF LLC has the 572 financial and business stability that it needs to be able to meet 573 the needs of the IETF, including adopting an annual budget, and as 574 necessary incurring any debt or making other financial 575 arrangements; 577 o approving or entering into agreements that meet a significant 578 materiality threshold; 580 o exercising a legal duty to ensure that the IETF LLC complies with 581 any applicable tax and other laws; 583 o ensuring that IETF LLC is run in a manner that is transparent and 584 accountable to the IETF community; 586 o recruiting new Directors, for consideration in all of the various 587 appointment processes. 589 The IETF LLC Board is an oversight body, with responsibilities 590 limited to those listed above. It does not directly conduct any of 591 the IETF's administrative work, which is the day-to-day job of the 592 IETF Executive Director and their team. Per Section 5(d) of the LLC 593 Agreement [IETF-LLC-A], the Board must provide the IETF community 594 with an opportunity to review and discuss any proposed changes to the 595 IETF LLC structure prior to their adoption. 597 The role of the IETF LLC Board is to ensure that the strategy and 598 conduct of the IETF LLC is consistent with the IETF's needs - both 599 its concrete needs and its needs for transparency and accountability. 600 The Board is not intended to directly define the IETF's needs; to the 601 extent that is required, the IETF community should document its needs 602 in consensus-based RFCs (e.g., as the community did in 603 [I-D.ietf-mtgvenue-iaoc-venue-selection-process]) and provide more 604 detailed input via consultations with the IETF LLC Board (such as 605 takes place on email discussion lists or at IETF meetings). 607 As part of the responsibilities outlined above the Board is expected 608 to work to ensure that IETF LLC: 610 o Acts consistently with ISOC's 501(c)(3) status; 612 o Provides accurate financial statements to ISOC on a timely basis; 614 o Prepares its financial reports in accordance with generally 615 accepted accounting principles; 617 o Provides assistance to help facilitate ISOC's tax compliance, 618 including but not limited to assistance related to preparing the 619 Form 990 and responding to any IRS questions and audits; 621 o Obtains appropriate insurance, including commercial general 622 liability insurance with appropriate limits; 624 o Implements risk management and compliance processes in a manner 625 consistent with industry norms. 627 The description below outlines the composition of the IETF LLC Board, 628 selection of IETF LLC Board Directors, and related details. 630 4.3. Board Design Goals 632 A goal of this Board composition is to balance the need for the IETF 633 LLC to be accountable to the IETF community with the need for this 634 Board to have the expertise necessary to oversee a small non-profit 635 corporation. The Board is smaller than the previous IAOC and the 636 other leadership bodies of the IETF, in part to keep the Board 637 focused on its rather limited set of strategic responsibilities as 638 noted in Section 4.2. 640 This board structure, with limited strategic responsibilities noted 641 in Section 4.2 and limited size, together with the staff 642 responsibilities noted in Section 4.1, is designed to overcome the 643 challenges described in Section 3.1.4 of [I-D.haberman-iasa20dt-recs] 644 concerning oversight. This establishes a clear line of oversight 645 over staff performance: the IETF LLC Board oversees the IETF 646 Executive Director's performance and has actual legal authority to 647 remove a non-performing IETF Executive Director. The IETF Executive 648 Director is responsible for the day-to-day operation of the IETF LLC. 650 Finally, the IETF LLC Board would be expected to operate 651 transparently, to further address the concern raised in Section 3.3 652 of [I-D.haberman-iasa20dt-recs]. The default transparency rule 653 arrived at during the IASA 2.0 design process is detailed above in 654 Section 3.4. The Board will need to establish how it will meet that 655 commitment. 657 5. IETF LLC Board Membership, Selection and Accountability 659 5.1. Board Composition 661 There is a minimum of 5 directors, expandable to 6 or 7. 663 o 1 IETF Chair or delegate selected by the IESG 664 o 1 Appointed by the ISOC Board of Trustees 666 o 3 Selected by the IETF NomCom, confirmed by the IESG 668 o Up to 2 Appointed by the IETF LLC board itself, on an as-needed 669 basis, confirmed by the IESG 671 For the first slot listed above, the presumption is that the IETF 672 Chair will serve on the board. At the IESG's discretion, another 673 area director may serve instead, or exceptionally the IESG may run a 674 selection process to appoint a director. The goal of having this 675 slot on the board is to maintain coordination and communication 676 between the board and the IESG. 678 5.2. IETF LLC-Appointed Directors 680 As noted above, a maximum of two Directors may be appointed by the 681 IETF LLC Board. They can obviously choose to appoint none, one, or 682 two. These appointments need not be on an exceptional basis, but 683 rather be routine, and may occur at any time of the year since it is 684 on an as-needed basis. 686 The appointment of an IETF LLC Board-appointed Director requires a 687 2/3rd-majority vote of the Directors then in office, and the 688 appointee shall take office immediately upon appointment. The term 689 of each appointment is designated by the Board, with the maximum term 690 being three years, or until their earlier resignation, removal or 691 death. The Board may decide on a case-by-case basis how long each 692 term shall be, factoring in the restriction for consecutive terms in 693 Section 5.4. 695 5.3. Recruiting IETF LLC Board Directors 697 The IETF LLC Board itself is expected to take an active role in 698 recruiting potential new Directors, regardless of the process that 699 may be used to appoint them. In particular, the NomCom is primarily 700 focused on considering requirements expressed by the Board and 701 others, reviewing community feedback on candidates, conducting 702 candidate interviews, and ultimately appointing Directors. The IETF 703 LLC Board and others can recruit potential Directors and get them 704 into the consideration process of the NomCom or other appointing 705 bodies. 707 5.4. IETF LLC Board Director Term Length 709 The term length for a Director is three years. The exceptions to 710 this guideline are: 712 o For the terms for some Directors during the first full formation 713 of the IETF LLC Board in order to establish staggered terms and 714 for any appointments to fill a vacancy. 716 o The Director slot occupied by the IETF Chair ex officio or a 717 delegate selected by the IESG will serve a two-year term. This 718 makes the term length for this slot the same as the term lengths 719 established in [RFC7437] (BCP10), Section 3.4. 721 5.5. IETF LLC Board Director Limit 723 A director may serve no more than two consecutive terms, with at 724 least one full term prior to the start of any additional terms. An 725 exception is if a Director role is occupied by the IETF Chair ex 726 officio, since that person's service is governed instead by the term 727 lengths established in [RFC7437] (BCP10), Section 3.4. 729 An exception to the two consecutive term rule is for an IETF LLC- 730 appointed Director. For such a Director, they may serve only one 731 term via this appointment method, after which any subsequent terms 732 would be occur via other appointment or selection processes (such as 733 via the NomCom process). 735 Lastly, partial terms of less than three years for the initial 736 appointments to the first full board, for which some Directors will 737 have terms of one or two years, do not count against the term limit. 739 The limit on consecutive terms supports the healthy regular 740 introduction of new ideas and energy into the Board and mitigates 741 potential long-term risk of ossification or conflict, without 742 adversely impacting the potential pool of director candidates over 743 time. 745 5.6. Staggered Terms 747 ISOC, the IESG, the Nominating Committee, and the Board are expected 748 to coordinate with each other to ensure that collectively their 749 appointment or selection processes provide for no more than three 750 Directors' terms concluding in the same year. 752 5.7. IETF LLC Board Director Removal 754 Directors may be removed with or without cause. A vote in favor of 755 removal must be no fewer than the number of Directors less two. So 756 for example, if there are seven directors, then five votes are 757 required. Directors may also be removed via the IETF recall process 758 defined in [RFC7437] (BCP10), Section 7. 760 5.8. Filling an IETF LLC Board Director Vacancy 762 It shall be the responsibility of each respective body that appointed 763 or selected a Director that vacates the Board to appoint a new 764 Director to fill the vacancy. For example, if a Director selected by 765 the NomCom departs the Board prior to the end of their term for 766 whatever reason, then it is the responsibility of the NomCom (using 767 its mid-term rules, as specified in [RFC8318], Section 3.5) as the 768 original appointing body to designate a replacement that will serve 769 out the remainder of the term of the departed Director. However, 770 this obligation will not apply to vacancies in Board-appointed 771 positions. 773 5.9. Quorum 775 At all meetings of the Board, at least 2/3 of the Directors then in 776 office constitute a quorum for the transaction of business. If a 777 quorum is not be present at any meeting of the Board, the Directors 778 present thereat may adjourn the meeting without notice other than 779 announcement at the meeting, until a quorum is present. 781 5.10. Board Voting 783 The Board can hold votes during synchronous live meetings of the 784 Board (including telephonic and video) or via asynchronous written 785 (including electronic) means. A given vote shall be either conducted 786 entirely during a synchronous live meeting or entirely via 787 asynchronous written means, not a mix of the two. Decisions on 788 regular IETF LLC matters require a 2/3 majority vote in favor, with 789 the exception of removal of a Director as specified in Section 5.7. 790 Absentee voting and voting by proxy are not permitted. 792 5.11. Interim Board 794 An initial interim Board was necessary in order to legally form and 795 bootstrap the IETF LLC. As a result, an Interim Board was formed on 796 a temporary basis until the first full board was constituted. The 797 Interim Board was expected to conclude no later than the end of the 798 104th meeting of the IETF, in March 2019. 800 The interim Board was comprised of: 802 o The IETF chair, ex officio 804 o The IAOC chair, ex officio 806 o The IAB chair, ex officio 807 o One ISOC trustee, selected by the ISOC Board of Trustees 809 5.12. Board Positions 811 Following the formation of the first full IETF LLC Board, and at each 812 subsequent annual meeting of the IETF LLC Board, the Directors are 813 expected to elect by a majority vote of the IETF LLC Board a Director 814 to serve as Board Chair. The Board may also form committees of the 815 Board and/or define other roles for IETF LLC Board Directors as 816 necessary. 818 6. IETF LLC Funding 820 The IETF LLC must function within a budget of costs balanced against 821 limited revenues. The IETF community expects the IETF LLC to work to 822 attain that goal, in order to maintain a viable IETF support function 823 that provides the environment within which the IETF's technical work 824 can remain vibrant and productive. 826 The IETF LLC generates income from a few key sources at the time that 827 this document was written, as enumerated below. Additional sources 828 of income may be developed in the future, within the general bounds 829 noted in Section 6.8, and some of these may decline in relevance or 830 go away. As a result this list is subject to change over time and is 831 merely an example of the primary sources of income for the IETF LLC 832 at the time of this writing: 834 1. ISOC support 836 2. IETF meeting revenues 838 3. Donations to the IETF LLC (monetary and/or in-kind) 840 6.1. Financial Statements 842 As noted in Section 4.2, the IETF LLC must comply with relevant tax 843 laws, such as filing an annual IRS Form 990. Other official 844 financial statements may also be required. 846 In addition to these official financial statements and forms, the 847 IETF LLC is also expected to report on a regular basis to the IETF 848 community on the current and future annual budget, budget forecasts 849 vs. actuals over the course of a fiscal year, and on other 850 significant projects as needed. This regular reporting to the IETF 851 community is expected to be reported in the form of standard 852 financial statements that reflect the income, expenses, assets, and 853 liabilities of the IETF LLC. 855 6.2. Bank and Investment Accounts 857 The IETF LLC maintains its own bank account, separate and distinct 858 from ISOC. The IETF LLC may at its discretion create additional 859 accounts as needed. Similarly, the IETF LLC may as needed create 860 investment accounts in support of its financial goals and objectives. 862 6.3. Financial Audits 864 The IETF LLC is expected to retain and work with an independent 865 auditor. Reports from the auditor are expected to be shared with the 866 IETF community and other groups and organizations as needed or as 867 required by law. 869 6.4. ISOC Financial Support 871 ISOC currently provides significant financial support to the IETF 872 LLC. Exhibit B of the [IETF-LLC-A] summarizes the one-time and on- 873 going financial support from ISOC for the forseeable future. It is 874 envisioned that this support will be periodically reviewed and 875 revised, via a cooperative assessment process between ISOC and the 876 IETF LLC. 878 6.5. IETF Meeting Revenues 880 Meeting revenues are another important source of funding that 881 supports the IETF, comining mainly from the fees paid by IETF meeting 882 participants. The IETF Executive Director sets those meeting fees, 883 in consultation with the IETF LLC and the IETF community, with formal 884 approval by the IETF LLC. Setting these fees and projecting the 885 number of participants at future meetings is a key part of the annual 886 budget process. 888 6.6. Donations to the IETF LLC 890 Donations are an essential component of the financial support for the 891 IETF. Within the general bounds noted in Section 6.8, the IETF LLC 892 is responsible for fundraising activities in order to establish, 893 maintain, and grow a strong foundation of donation revenues. This 894 can and does include both direct financial contributions as well as 895 in-kind contributions, such as equipment, software licenses, and 896 services. 898 Donations to the IETF LLC shall not convey to donors any special 899 oversight or direct influence over the IETF's technical work or other 900 activities of the IETF or IETF LLC. This helps ensure that no undue 901 influence may be ascribed to those from whom funds are raised, and so 902 helps to maintain an open and consensus-based IETF standards process. 904 To the extent that the IETF LLC needs to undertake any significant 905 special projects for the IETF, the IETF LLC may need to fundraise 906 distinctly for those special projects. As a result, the IETF LLC may 907 conduct fundraising to support the IETF in general as well as one or 908 more special fundraising efforts (which may also be accounted for 909 distinctly and be held in a separate bank account or investment, as 910 needed). 912 6.7. Funding Supports the IETF 914 The IETF LLC exists to support the IETF. Therefore, the IETF LLC's 915 funding and all revenues, in-kind contributions, and other income 916 that comprise that funding shall be used solely to support IETF- 917 related activities and for no other purposes. 919 6.8. Charitable Fundraising Practices 921 When the IETF LLC conducts fundraising, it substantiates charitable 922 contributions on behalf of ISOC. The IETF LLC evaluates and 923 facilitates state, federal, and other applicable law and regulatory 924 compliance for ISOC and/or the LLC with respect to such fundraising 925 activities. In addition, the IETF LLC ensures that all fundraising 926 activities are conducted in compliance with any policies developed by 927 the IETF LLC, including but not limited to those noted in Section 7. 929 6.9. Operating Reserve 931 An initial target operating reserve has been specified in Exhibit B 932 of the [IETF-LLC-A]. That says that the IETF LLC should maintain an 933 operating reserve equal to the IETF LLC's budgeted Net Loss for 2019 934 multiplied times three. The IETF LLC, in cooperation with ISOC, may 935 regularly review the financial target for this reserve fund, as noted 936 in the [IETF-LLC-A] or as otherwise necessary. 938 Should the IETF LLC generate an annual budget surplus, it may choose 939 to direct all or part of the surplus towards the growth of the 940 operating reserve. 942 6.10. Annual Budget Process 944 As noted in Section 3.3, the IETF LLC is responsible for managing the 945 IETF's finances and budget. A key part of this responsibility is 946 establishing, maintaining, and successfully meeting an annual budget. 947 This is essential to the continued operation and vibrancy of the 948 IETF's technical activities and establishes trust with ISOC and 949 donors that funds are being appropriately spent, and that financial 950 oversight is being conducted properly. This is also essential to the 951 IETF LLC meeting applicable legal and tax requirements and is a core 952 part of the IETF LLC Board's fiduciary responsibilities. 954 As explained in Section 4.1, the IETF Executive Director is expected 955 to develop, execute, and report on the annual budget. Regular 956 reporting is expected to include monthly and quarterly forecast vs. 957 budget statements, including updated projections of income and 958 expenses for the full fiscal year. 960 The IETF LLC Board, as explained in Section 4.2, is expected to 961 review and approve the budget, as well as to provide ongoing 962 oversight of the budget and of any other significant financial 963 matters. 965 The annual budget is expected to be developed in an open, 966 transparent, and collaborative manner, in accordance with 967 Section 3.4. The specific timeline for the development, review, and 968 approval of the IETF LLC annual budget is established by the IETF LLC 969 Board and may be revised as needed. 971 7. IETF LLC Policies 973 The Board is expected to maintain policies as necessary to achieve 974 the goals of the IETF LLC, meet transparency expectations of the 975 community, comply with applicable laws or regulations, or for other 976 reasons as appropriate. All policies are expected to be developed 977 with input from the IETF community. Some policies provided by ISOC 978 may provide a useful starting point for the Board to consider. 980 7.1. Conflict of Interest Policy 982 The Board is expected to maintain a Conflict of Interest policy for 983 the IETF LLC. While the details are determined by the Board, at a 984 minimum such policy is expected to include the following: 986 o The IETF, ISOC Board, IAB, or IRTF chair cannot be chair of this 987 IETF LLC Board, though they may serve as a Director. 989 o A Director cannot be a paid consultant or employee of the IETF 990 Executive Director or their sub-contractors, nor a paid consultant 991 or employee of ISOC. 993 7.2. Other Policies 995 The Board is expected to maintain additional policies for the IETF 996 LLC as necessary, covering Directors, employees, and contractors, 997 concerning issues such as: 999 o Acceptance of gifts and other non-cash compensation; 1001 o Travel and expense reimbursement; 1003 o Anti-bribery; 1005 o Code of conduct; 1007 o Anti-harassment; 1009 o Non-discrimination; 1011 o Whistleblower; 1013 o Document retention; 1015 o Export controls; 1017 o Anti-terrorism sanctions; 1019 o Data protection and privacy; 1021 o Social media 1023 7.3. Compliance 1025 The IETF LLC is expected to implement a compliance program to ensure 1026 its compliance with all applicable laws, rules and regulations, 1027 including without limitation laws governing bribery, anti-terrorism 1028 sanctions, export controls, data protection/privacy, as well as other 1029 applicable policies noted in Section 7. In addition, actions and 1030 activities of the IETF LLC must be consistent with 501(c)(3) 1031 purposes. 1033 The IETF LLC is expected report to ISOC on the implementation of its 1034 compliance plan on an annual basis. 1036 8. Three-Year Assessment 1038 The IETF LLC, with the involvement of the community, shall conduct 1039 and complete an assessment of the structure, processes, and operation 1040 of IASA 2.0 and the IETF LLC. This should be presented to the 1041 community after a period of roughly three years of operation. The 1042 assessment may potentially include recommendations for improvements 1043 or changes to the IASA2 and/or IETF LLC. 1045 9. Security Considerations 1047 This document describes the structure of the IETF's Administrative 1048 Aupport Activity (IASA), version 2 (IASA2). It introduces no 1049 security considerations for the Internet. 1051 10. IANA Considerations 1053 This document has no IANA considerations in the traditional sense. 1054 However, some of the information in this document may affect how the 1055 IETF standards process interfaces with the IANA, so the IANA may be 1056 interested in the contents. 1058 11. Acknowledgments 1060 Thanks to Jari Arkko, Richard Barnes, Brian E Carpenter, Alissa 1061 Cooper, John C Klensin, Bob Hinden, Jon Peterson, Sean Turner and the 1062 IASA2 Working Group for discussions of possible structures, and to 1063 the attorneys of Morgan Lewis and Brad Biddle for legal advice. 1065 12. Informative References 1067 [I-D.haberman-iasa20dt-recs] 1068 Haberman, B., Arkko, J., Daigle, L., Livingood, J., Hall, 1069 J., and E. Rescorla, "IASA 2.0 Design Team 1070 Recommendations", draft-haberman-iasa20dt-recs-03 (work in 1071 progress), November 2018. 1073 [I-D.ietf-iasa2-rfc2031bis] 1074 Camarillo, G. and J. Livingood, "The Updated IETF-ISOC 1075 Relationship", draft-ietf-iasa2-rfc2031bis-00 (work in 1076 progress), November 2018. 1078 [I-D.ietf-iasa2-trust-update] 1079 Arkko, J. and T. Hardie, "Update to the Process for 1080 Selection of Trustees for the IETF Trust", draft-ietf- 1081 iasa2-trust-update-02 (work in progress), October 2018. 1083 [I-D.ietf-mtgvenue-iaoc-venue-selection-process] 1084 Lear, E., "IETF Plenary Meeting Venue Selection Process", 1085 draft-ietf-mtgvenue-iaoc-venue-selection-process-16 (work 1086 in progress), June 2018. 1088 [IETF-LLC-A] 1089 The Internet Society, "Limited Liability Company Agreement 1090 of IETF Administration LLC", August 2018, 1091 . 1094 [ietf101-slides] 1095 Hall, J., "IASA 2.0 IETF-101 Slides", n.d., 1096 . 1099 [ietf102-slides] 1100 Hall, J., "IASA 2.0 IETF-102 Slides", n.d., 1101 . 1104 [ISOC] The Internet Society, "Amended and restated By-Laws of the 1105 Internet Society", July 2018, 1106 . 1109 [ML-memo] Morgan Lewis, "Options for New Organization to Conduct 1110 IETF Administrative Support Activities", February 2018, 1111 . 1114 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 1115 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 1116 . 1118 [RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031, 1119 DOI 10.17487/RFC2031, October 1996, 1120 . 1122 [RFC2850] Internet Architecture Board and B. Carpenter, Ed., 1123 "Charter of the Internet Architecture Board (IAB)", 1124 BCP 39, RFC 2850, DOI 10.17487/RFC2850, May 2000, 1125 . 1127 [RFC3233] Hoffman, P. and S. Bradner, "Defining the IETF", BCP 58, 1128 RFC 3233, DOI 10.17487/RFC3233, February 2002, 1129 . 1131 [RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, 1132 DOI 10.17487/RFC3710, February 2004, 1133 . 1135 [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the 1136 IETF Administrative Support Activity (IASA)", BCP 101, 1137 RFC 4071, DOI 10.17487/RFC4071, April 2005, 1138 . 1140 [RFC4333] Huston, G., Ed. and B. Wijnen, Ed., "The IETF 1141 Administrative Oversight Committee (IAOC) Member Selection 1142 Guidelines and Process", BCP 113, RFC 4333, 1143 DOI 10.17487/RFC4333, December 2005, 1144 . 1146 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 1147 Confirmation, and Recall Process: Operation of the 1148 Nominating and Recall Committees", BCP 10, RFC 7437, 1149 DOI 10.17487/RFC7437, January 2015, 1150 . 1152 [RFC7691] Bradner, S., Ed., "Updating the Term Dates of IETF 1153 Administrative Oversight Committee (IAOC) Members", 1154 BCP 101, RFC 7691, DOI 10.17487/RFC7691, November 2015, 1155 . 1157 [RFC8318] Dawkins, S., "IAB, IESG, and IAOC Selection, Confirmation, 1158 and Recall Process: IAOC Advisor for the Nominating 1159 Committee", BCP 10, RFC 8318, DOI 10.17487/RFC8318, 1160 January 2018, . 1162 Authors' Addresses 1164 Brian Haberman 1165 Johns Hopkins University 1167 Email: brian@innovationslab.net 1169 Joseph Lorenzo Hall 1170 CDT 1172 Email: joe@cdt.org 1174 Jason Livingood 1175 Comcast 1177 Email: jason_livingood@comcast.com