| rfc8711xml2.original.xml | rfc8711.xml | |||
|---|---|---|---|---|
| <?xml version="1.0" encoding="UTF-8"?> | <?xml version='1.0' encoding='utf-8'?> | |||
| <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> | <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.2.8 --> | |||
| <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.2.8 --> | <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent"> | |||
| <rfc | ||||
| xmlns:xi="http://www.w3.org/2001/XInclude" | ||||
| number="8711" | ||||
| updates="" | ||||
| obsoletes="4071, 4333, 7691" | ||||
| category="bcp" | ||||
| consensus="true" | ||||
| submissionType="IETF" | ||||
| ipr="trust200902" | ||||
| docName="draft-ietf-iasa2-rfc4071bis-11" | ||||
| xml:lang="en" | ||||
| tocInclude="true" | ||||
| sortRefs="true" | ||||
| symRefs="true" | ||||
| version="3"> | ||||
| <!-- xml2rfc v2v3 conversion 2.34.0 --> | ||||
| <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ | <!-- [rfced] This document obsoletes RFCs that are part of BCP 101 and | |||
| ]> | 113. We have marked this document as BCP 101, but please review and let us | |||
| know if any updates are needed. (We wonder whether BCP 113 should have been | ||||
| part of BCP 101.) | ||||
| <?rfc toc="yes"?> | *AD: We would appreciate your input here as well. | |||
| <?rfc sortrefs="yes"?> | ||||
| <?rfc symrefs="yes"?> | ||||
| <rfc ipr="trust200902" docName="draft-ietf-iasa2-rfc4071bis-11" category="bcp" o | BCP 101 | |||
| bsoletes="4071, 4333, 7691"> | RFC 4071: Structure of the IETF Administrative Support Activity (IASA) | |||
| RFC 4371: BCP 101 Update for IPR Trust | ||||
| RFC 7691: Updating the Term Dates of IETF Administrative Oversight Committee | ||||
| (IAOC) Members | ||||
| BCP 113 | ||||
| RFC 4333: The IETF Administrative Oversight Committee (IAOC) Member Selection | ||||
| Guidelines and Process | ||||
| --> | ||||
| <front> | <front> | |||
| <title abbrev="IASA2">Structure of the IETF Administrative Support Activity, Version 2.0</title> | ||||
| <title abbrev="IASA 2.0">Structure of the IETF Administrative Support Activi | ||||
| ty, Version 2.0</title> | ||||
| <seriesInfo name="RFC" value="8711"/> | ||||
| <seriesInfo name="BCP" value="101"/> | ||||
| <author initials="B." surname="Haberman" fullname="Brian Haberman"> | <author initials="B." surname="Haberman" fullname="Brian Haberman"> | |||
| <organization>Johns Hopkins University</organization> | <organization>Johns Hopkins University</organization> | |||
| <address> | <address> | |||
| <email>brian@innovationslab.net</email> | <email>brian@innovationslab.net</email> | |||
| </address> | </address> | |||
| </author> | </author> | |||
| <author initials="J." surname="Hall" fullname="Joseph Lorenzo Hall"> | <author initials="J." surname="Hall" fullname="Joseph Lorenzo Hall"> | |||
| <organization>CDT</organization> | <organization>Internet Society</organization> | |||
| <address> | <address> | |||
| <email>joe@cdt.org</email> | <email>hall@isoc.org</email> | |||
| </address> | </address> | |||
| </author> | </author> | |||
| <author initials="J." surname="Livingood" fullname="Jason Livingood"> | <author initials="J." surname="Livingood" fullname="Jason Livingood"> | |||
| <organization>Comcast</organization> | <organization>Comcast</organization> | |||
| <address> | <address> | |||
| <email>jason_livingood@comcast.com</email> | <email>jason_livingood@comcast.com</email> | |||
| </address> | </address> | |||
| </author> | </author> | |||
| <date year="2020" month="January"/> | ||||
| <date year="2019" month="April" day="12"/> | ||||
| <area>General</area> | <area>General</area> | |||
| <workgroup>IASA2</workgroup> | <workgroup>IASA2</workgroup> | |||
| <keyword>Internet-Draft</keyword> | <keyword>IASA</keyword> | |||
| <!-- [rfced] The following terms are used interchangeably. Do you want to | ||||
| make any of these more consistent? If so, please let us know the preferred | ||||
| form. | ||||
| <abstract> | We have updated one instance of "Board" to "IETF LLC Board" for clarity - | |||
| please review. | ||||
| <t>The IETF Administrative Support Activity (IASA) was originally | IETF Administration LLC Board | |||
| IETF LLC Board | ||||
| Board of Directors of the IETF LLC | ||||
| Board | ||||
| IETF LLC Agreement | ||||
| LLC Agreement | ||||
| ISOC/IETF LLC Agreement | ||||
| Please note that we updated the document to use the following consistently: | ||||
| IASA 2.0 (instead of IASA2 - except where it refers to the WG) | ||||
| IETF Administrative Support Activity, version 2.0 | ||||
| --> | ||||
| <abstract> | ||||
| <t>The IETF Administrative Support Activity (IASA) was originally | ||||
| established in 2005. In the years since then, the needs of the IETF | established in 2005. In the years since then, the needs of the IETF | |||
| evolved in ways that required changes to its administrative | evolved in ways that required changes to its administrative | |||
| structure. The purpose of this document is to document and describe | structure. The purpose of this RFC is to document and describe | |||
| the IETF Administrative Support Activity, version 2 (IASA 2.0). It | the IETF Administrative Support Activity, version 2.0 (IASA 2.0). It | |||
| defines the roles and responsibilities of the IETF Administration LLC | defines the roles and responsibilities of the IETF Administration LLC | |||
| Board, the IETF Executive Director, and the Internet Society in the | Board (IETF LLC Board), the IETF Executive Director, and the Internet Society in the | |||
| fiscal and administrative support of the IETF standards process. It | fiscal and administrative support of the IETF standards process. It | |||
| also defines the membership and selection rules for the IETF | also defines the membership and selection rules for the IETF | |||
| Administration LLC Board.</t> | LLC Board.</t> | |||
| <t>This document obsoletes RFC 4071, RFC 4333, and RFC 7691.</t> | ||||
| <t>This document obsoletes RFC 4071, RFC 4333, and RFC 7691.</t> | ||||
| </abstract> | </abstract> | |||
| </front> | </front> | |||
| <middle> | <middle> | |||
| <section anchor="introduction" numbered="true" toc="default"> | ||||
| <section anchor="introduction" title="Introduction"> | <name>Introduction</name> | |||
| <t>The IETF Administrative Support Activity (IASA) was originally | ||||
| <t>The IETF Administrative Support Activity (IASA) was originally | ||||
| established in 2005. In the years since then, the needs of the | established in 2005. In the years since then, the needs of the | |||
| IETF evolved in ways that required changes to its administrative | IETF evolved in ways that required changes to its administrative | |||
| structure. The purpose of this document is to document and describe | structure. The purpose of this document is to document and describe | |||
| the IASA 2.0 structure.</t> | the IASA 2.0 structure.</t> | |||
| <t>Under IASA 2.0, the work of the IETF's administrative and fundraising | ||||
| <t>Under IASA 2.0, the work of the IETF’s administrative and fundraising | ||||
| tasks is conducted by an administrative organization, the IETF Administration | tasks is conducted by an administrative organization, the IETF Administration | |||
| Limited Liability Company (“IETF LLC”). Under this structure, the IETF | LLC (IETF LLC). Under this structure, the IETF | |||
| Administrative Oversight Committee (IAOC) is eliminated, and its oversight | Administrative Oversight Committee (IAOC) is eliminated, and its oversight | |||
| and advising functions transferred to the IETF LLC Board.</t> | and advising functions transferred to the IETF LLC Board.</t> | |||
| <t>The IETF LLC provides the corporate legal home for the IETF, the Intern | ||||
| <t>The IETF LLC provides the corporate legal home for the IETF, the Internet | et | |||
| Architecture Board (IAB), and the Internet Research Task Force (IRTF), and | Architecture Board (IAB), and the Internet Research Task Force (IRTF), and | |||
| financial support for the operation of the RFC Editor.</t> | financial support for the operation of the RFC Editor.</t> | |||
| <t><xref target="I-D.haberman-iasa20dt-recs" format="default"/> discusses | ||||
| <t><xref target="I-D.haberman-iasa20dt-recs"/> discusses the challenges facing t | the challenges facing the | |||
| he | ||||
| original IASA structure as well as several options for reorganizing the | original IASA structure as well as several options for reorganizing the | |||
| IETF’s administration under different legal structures. This document | IETF's administration under different legal structures. This document | |||
| outlines how the chosen option is structured and describes how | outlines how the chosen option is structured and describes how | |||
| the organization fits together with existing and new IETF | the organization fits together with existing and new IETF | |||
| community structures.</t> | community structures.</t> | |||
| <t>Under IASA 2.0, most of the responsibilities that <xref target="RFC4071 | ||||
| <t>Under IASA 2.0, most of the responsibilities that <xref target="RFC4071"/> as | " format="default"/> assigned to | |||
| signed to | ||||
| the IETF Administrative Director (IAD) and the Internet Society (ISOC) were | the IETF Administrative Director (IAD) and the Internet Society (ISOC) were | |||
| transferred to the IETF LLC and IETF Administration LLC Executive Director | transferred to the IETF LLC and IETF Administration LLC Executive Director | |||
| (IETF Executive Director). It is the job of the IETF LLC to meet the | (IETF Executive Director). It is the job of the IETF LLC to meet the | |||
| administrative needs of the IETF and to ensure that the IETF LLC meets the | administrative needs of the IETF and to ensure that the IETF LLC meets the | |||
| needs of the IETF community.</t> | needs of the IETF community.</t> | |||
| <t>Eliminating the IAOC meant that changes were required in how | ||||
| <t>Eliminating the IAOC meant that changes were required in how | ||||
| trustees could be appointed to the IETF Trust. The details of how this | trustees could be appointed to the IETF Trust. The details of how this | |||
| is done are outside the scope of this document but are covered in | is done are outside the scope of this document but are covered in | |||
| <xref target="I-D.ietf-iasa2-trust-update"/>.</t> | <xref target="RFC8714" format="default"/>.</t> | |||
| <t>This document obsoletes <xref target="RFC4071" format="default"/>, whic | ||||
| <t>This document obsoletes <xref target="RFC4071"/>, which specified the origina | h specified the original IASA, | |||
| l IASA, | <xref target="RFC4333" format="default"/>, which specified the selection guideli | |||
| <xref target="RFC4333"/>, which specified the selection guidelines and process f | nes and process for IAOC | |||
| or IAOC | members, and <xref target="RFC7691" format="default"/>, which specified terms fo | |||
| members and <xref target="RFC7691"/>, which specified terms for IAOC members.</t | r IAOC members.</t> | |||
| > | </section> | |||
| <section anchor="scope-limitation" numbered="true" toc="default"> | ||||
| </section> | <name>Scope Limitation</name> | |||
| <section anchor="scope-limitation" title="Scope Limitation"> | <t>The document does not propose any changes related to the | |||
| <t>The document does not propose any changes related to the | ||||
| standards process as currently conducted | standards process as currently conducted | |||
| by the Internet Engineering Steering Group (IESG) and Internet | by the Internet Engineering Steering Group (IESG) and Internet | |||
| Architecture Board (IAB) (see BCP 9 <xref target="RFC2026"/>, BCP 39 <xref targe | Architecture Board (IAB) (see BCP 9 <xref target="RFC2026" format="default"/> an | |||
| t="RFC2850"/>). In addition, no changes are made to the appeals | d | |||
| chain, the process for making and confirming IETF and IAB appointments (see BCP | BCP 39 <xref target="RFC2850" format="default"/>). In addition, no changes are m | |||
| 10 <xref target="I-D.ietf-iasa2-rfc7437bis"></xref>), | ade to the appeals | |||
| the technical work of the Internet Research Task Force (IRTF) (see BCP 8 <xref t | chain, the process for making and confirming IETF and IAB appointments (see | |||
| arget="RFC2014"/>), or to | BCP 10 <xref target="RFC8713" format="default"/>), | |||
| ISOC’s membership in or support of other organizations.</t> | the technical work of the Internet Research Task Force (IRTF) (see <xref | |||
| target="RFC2014" format="default"/>), or to ISOC's membership in or support of o | ||||
| </section> | ther organizations.</t> | |||
| <section anchor="llc-agreement-with-the-internet-society" title="LLC Agreement w | </section> | |||
| ith the Internet Society"> | <section anchor="llc-agreement-with-the-internet-society" numbered="true" to | |||
| c="default"> | ||||
| <t>The LLC Agreement between the IETF LLC and ISOC is available | <name>LLC Agreement with the Internet Society</name> | |||
| at <xref target="IETF-LLC-A"/>. This IASA2 structure, and thus this document, | <t>The LLC Agreement between the IETF LLC and ISOC is available | |||
| at <xref target="IETF-LLC-A" format="default"/>. This IASA 2.0 structure, and th | ||||
| us this document, | ||||
| depends on the LLC Agreement and will refer to it to help | depends on the LLC Agreement and will refer to it to help | |||
| explain certain aspects of the legal | explain certain aspects of the legal | |||
| relationship between the IETF LLC and ISOC.</t> | relationship between the IETF LLC and ISOC.</t> | |||
| <t>The LLC Agreement was developed | ||||
| <t>The LLC Agreement was developed | ||||
| between legal representatives of the IETF and ISOC and includes all | between legal representatives of the IETF and ISOC and includes all | |||
| critical terms of the relationship, while still enabling maximum | critical terms of the relationship, while still enabling maximum | |||
| unilateral flexibility for the IETF LLC Board. The LLC Agreement includes only basic | unilateral flexibility for the IETF LLC Board. The LLC Agreement includes only basic | |||
| details about how the Board manages itself or manages IETF LLC staff, | details about how the Board manages itself or manages IETF LLC staff, | |||
| so that the Board has flexibility to make changes without amending | so that the Board has flexibility to make changes without amending | |||
| the agreement. The Board can independently develop policy or procedures | the agreement. The Board can independently develop policy or procedures | |||
| documents that fill gaps.</t> | documents that fill gaps.</t> | |||
| </section> | ||||
| </section> | <section anchor="definitions-and-principles" numbered="true" toc="default"> | |||
| <section anchor="definitions-and-principles" title="Definitions and Principles"> | <name>Definitions and Principles</name> | |||
| <section anchor="terminology" numbered="true" toc="default"> | ||||
| <section anchor="terminology" title="Terminology"> | <name>Terminology</name> | |||
| <t>Although most of the terms, abbreviations, and acronyms used in this | ||||
| <t>Although most of the terms, abbreviations, and acronyms used in this | ||||
| document are reasonably well known, first-time readers may find some | document are reasonably well known, first-time readers may find some | |||
| terminology confusing. This section therefore attempts to provide a | terminology confusing. This section therefore attempts to provide a | |||
| quick summary.</t> | quick summary.</t> | |||
| <dl> | ||||
| <dt>IAB:</dt> <dd>Internet Architecture Board (see <xref | ||||
| target="RFC2026" format="default"/> and <xref target="RFC2850" format="de | ||||
| fault"/>).</dd> | ||||
| <t>IAB: Internet Architecture Board (see <xref target="RFC2026"/>, <xref target= | <dt>IAD:</dt> <dd>IETF Administrative Director, a role obsoleted by this | |||
| "RFC2850"/>).</t> | document | |||
| and the ISOC / IETF LLC Agreement (see <xref target="IETF-LLC-A" format="default | ||||
| <t>IAD: IETF Administrative Director, a role obsoleted by this document | "/>) and replaced by the | |||
| and the ISOC/IETF LLC Agreement (<xref target="IETF-LLC-A"/>) and replaced by th | IETF LLC Executive Director.</dd> | |||
| e | <dt>IAOC:</dt> <dd>IETF Administrative Oversight Committee, a committee | |||
| IETF LLC Executive Director.</t> | that oversaw | |||
| <t>IAOC: IETF Administrative Oversight Committee, a committee that oversaw | ||||
| IETF administrative activity. The IAOC is obsoleted by this document and | IETF administrative activity. The IAOC is obsoleted by this document and | |||
| replaced by the IETF LLC Board. The IETF Trust was formerly populated by | replaced by the IETF LLC Board. The IETF Trust was formerly populated by | |||
| IAOC members. Its membership is now distinct from that of the IETF LLC | IAOC members. Its membership is now distinct from that of the IETF LLC | |||
| Board (See <xref target="I-D.ietf-iasa2-trust-update"/>).)</t> | Board (see <xref target="RFC8714" format="default"/>).</dd> | |||
| <dt>IASA:</dt> <dd>The IETF Administrative Support Activity, consists of | ||||
| <t>IASA: The IETF Administrative Support Activity, consists of the IETF | the IETF | |||
| LLC board, employees, and contractors. Uses of the term ‘IASA’ as | LLC Board, employees, and contractors. Uses of the term 'IASA' as | |||
| a proper noun may imply a subset of these roles, or all of them.</t> | a proper noun may imply a subset of these roles, or all of them.</dd> | |||
| <dt>IASA 2.0:</dt> <dd>The IETF Administrative Support Activity, | ||||
| <t>IASA 2.0: Version 2.0 of the IETF Administrative Support Activity, | version 2.0 (defined by this document).</dd> | |||
| defined by this document.</t> | <dt>IESG:</dt> <dd>Internet Engineering Steering Group (see <xref | |||
| target="RFC2026" format="default"/> and | ||||
| <t>IESG: Internet Engineering Steering Group (see <xref target="RFC2026"/>, | <xref target="RFC3710" format="default"/>).</dd> | |||
| <xref target="RFC3710"/>).</t> | <dt>IETF:</dt> <dd>Internet Engineering Task Force (see <xref target="RF | |||
| C3233" format="default"/>).</dd> | ||||
| <t>IETF: Internet Engineering Task Force (see <xref target="RFC3233"/>).</t> | <dt>IETF Administration LLC:</dt> <dd>The legal entity - a disregarded L | |||
| imited Liability Company | ||||
| <t>IETF Administration LLC: The legal entity - a disregarded Limited Liability C | ||||
| ompany | ||||
| (LLC) of The Internet Society - established to provide a corporate legal framewo rk | (LLC) of The Internet Society - established to provide a corporate legal framewo rk | |||
| for facilitating current and future activities related to the IETF, IAB, and IRT F. | for facilitating current and future activities related to the IETF, IAB, and IRT F. | |||
| It was established by the ISOC/IETF LLC Agreement (<xref target="IETF-LLC-A"/>) | It was established by the ISOC / IETF LLC Agreement (see <xref target="IETF-LLC- | |||
| and is referred | A" format="default"/>) and is referred | |||
| to as “IETF LLC.”</t> | to as "IETF LLC".</dd> | |||
| <dt>IETF LLC Executive Director:</dt> <dd>the Executive Director for the | ||||
| <t>IETF LLC Executive Director: the Executive Director for the IETF LLC, respons | IETF LLC, responsible | |||
| ible | for day-to-day administrative and operational direction (see <xref target="staff | |||
| for day-to-day administrative and operational direction (See <xref target="staff | -responsibilities" format="default"/>). | |||
| -responsibilities"/>). | Also referred to as "IETF Executive Director".</dd> | |||
| Also referred to as “IETF Executive Director”.</t> | <dt>IETF LLC Board:</dt> <dd>The Board of Directors of the IETF LLC. The | |||
| IETF LLC | ||||
| <t>IETF LLC Board: The Board of Directors of the IETF LLC. The IETF LLC | Board is formally a multi-member "manager" of the IETF LLC on behalf | |||
| Board is formally a multi-member “manager” of the IETF LLC on behalf | of ISOC (see <xref target="board-responsibilities" format="default"/>).</dd> | |||
| of ISOC (See <xref target="board-responsibilities"/>).</t> | <dt>ISOC:</dt> <dd>Internet Society (see <xref target="RFC8712" format=" | |||
| default"/> and <xref target="ISOC" format="default"/>).</dd> | ||||
| <t>ISOC: Internet Society (see <xref target="I-D.ietf-iasa2-rfc2031bis"/> and <x | </dl> | |||
| ref target="ISOC"/>).</t> | </section> | |||
| <section anchor="key-differences-from-the-old-iasa-structure-to-iasa-20" n | ||||
| </section> | umbered="true" toc="default"> | |||
| <section anchor="key-differences-from-the-old-iasa-structure-to-iasa-20" title=" | <name>Key Differences from the Old IASA Structure to IASA 2.0</name> | |||
| Key Differences From the Old IASA Structure to IASA 2.0"> | <ul spacing="normal"> | |||
| <li>The IAOC and IAD roles defined in RFC 4071 are eliminated.</li> | ||||
| <t><list style="symbols"> | <li>The former ISOC and IAD responsibilities are assigned to a new | |||
| <t>The IAOC and IAD roles defined in RFC 4071 are eliminated.</t> | organization, IETF Administration LLC.</li> | |||
| <t>The former ISOC and IAD responsibilities are assigned to a new | <li>The Board of Directors of the IETF LLC -- formally a multi-member | |||
| organization, IETF Administration LLC.</t> | "manager" of the IETF LLC on behalf of ISOC -- assumes the oversight responsibil | |||
| <t>The Board of Directors of the IETF LLC – formally a multi-member “manager” | ities from the IAOC.</li> | |||
| of the IETF LLC on behalf of ISOC – assumes the oversight responsibilities from | <li>The Board of the IETF LLC is more focused on strategy and oversigh | |||
| the IAOC.</t> | t than the IAOC was, with the IETF Executive Director and their team in charge o | |||
| <t>The Board of the IETF LLC is more focused on strategy and oversight than th | f day-to-day operations.</li> | |||
| e IAOC was, with the IETF Executive Director and their team in charge of day-to- | <li>The IAD role is replaced with the IETF Executive Director role.</l | |||
| day operations.</t> | i> | |||
| <t>The IAD role is replaced with the IETF Executive Director role.</t> | <li>The role that was previously referred to as "IETF Executive | |||
| <t>The role that was previously referred to as “IETF Executive | Director" in older documents such as <xref target="RFC2026" format="default"/> i | |||
| Director” in older documents such as <xref target="RFC2026"/> is now “Managing | s now "Managing | |||
| Director, IETF Secretariat”.</t> | Director, IETF Secretariat".</li> | |||
| </list></t> | </ul> | |||
| </section> | ||||
| </section> | <section anchor="llc-responsibilities" numbered="true" toc="default"> | |||
| <section anchor="llc-responsibilities" title="General IETF LLC Responsibilities" | <name>General IETF LLC Responsibilities</name> | |||
| > | <t>The IETF LLC is established to provide administrative support to the | |||
| IETF. It has no authority over the standards development activities of the IETF. | ||||
| <t>The IETF LLC is established to provide administrative support to the IETF. It | </t> | |||
| has no authority over the standards development activities of the IETF.</t> | <t>The responsibilities of the IETF LLC are:</t> | |||
| <ul spacing="normal"> | ||||
| <t>The responsibilities of the IETF LLC are:</t> | <li>Operations. The IETF LLC is responsible for supporting the ongoing | |||
| operations of the IETF, including meetings and non-meeting activities.</li> | ||||
| <t><list style="symbols"> | <li>Finances. The IETF LLC is responsible for managing the IETF's fina | |||
| <t>Operations. The IETF LLC is responsible for supporting the ongoing operatio | nces and budget.</li> | |||
| ns of the IETF, including meetings and non-meeting activities.</t> | <li>Fundraising. The IETF LLC is responsible for raising money on beha | |||
| <t>Finances. The IETF LLC is responsible for managing the IETF’s finances and | lf of the IETF.</li> | |||
| budget.</t> | <li>Compliance. The IETF LLC is responsible for establishing and enfor | |||
| <t>Fundraising. The IETF LLC is responsible for raising money on behalf of the | cing policies to ensure compliance with applicable laws, regulations, and rules. | |||
| IETF.</t> | </li> | |||
| <t>Compliance. The IETF LLC is responsible for establishing and enforcing poli | </ul> | |||
| cies to ensure compliance with applicable laws, regulations, and rules.</t> | <t>The manner by which these responsibilities under the IETF LLC are org | |||
| </list></t> | anized | |||
| is intended to address the problems described in Sections | ||||
| <t>The manner by which these responsibilities under the IETF LLC are organized | <xref target="I-D.haberman-iasa20dt-recs" section="3.1.1" sectionFormat="bare"/> | |||
| is intended to address the problems described in Sections 3.1.1., | , | |||
| 3.1.2, and 3.1.3 of <xref target="I-D.haberman-iasa20dt-recs"/>. | <xref target="I-D.haberman-iasa20dt-recs" section="3.1.2" sectionFormat="bare"/> | |||
| , and | ||||
| <xref target="I-D.haberman-iasa20dt-recs" section="3.1.3" sectionFormat="bare"/> | ||||
| of <xref target="I-D.haberman-iasa20dt-recs" format="default"/>. | ||||
| Specifically, this is | Specifically, this is | |||
| intended to bring greater clarity around roles, responsibilities, | intended to bring greater clarity around roles, responsibilities, | |||
| representation, decision-making, and authority.</t> | representation, decision-making, and authority.</t> | |||
| <t>In addition, by having the IETF LLC manage the IETF's finances and co | ||||
| <t>In addition, by having the IETF LLC manage the IETF’s finances and conduct th | nduct the IETF's fundraising, confusion about who is responsible for representin | |||
| e IETF’s fundraising, confusion about who is responsible for representing the IE | g the IETF to sponsors and who directs the uses of sponsorship funds should be e | |||
| TF to sponsors and who directs the uses of sponsorship funds should have been el | liminated. Finally, having the IETF LLC reside in a defined, distinct legal enti | |||
| iminated. Finally, having the IETF LLC reside in a defined, distinct legal entit | ty, and taking responsibility for operations, enables the organization to execut | |||
| y, and taking responsibility for operations, enables the organization to execute | e its own contracts without the need for review and approval by ISOC.</t> | |||
| its own contracts without the need for review and approval by ISOC.</t> | </section> | |||
| <section anchor="principles" numbered="true" toc="default"> | ||||
| </section> | <name>IETF LLC Working Principles</name> | |||
| <section anchor="principles" title="IETF LLC Working Principles"> | <t>The IETF LLC is expected to conduct its work according to the followi | |||
| ng principles:</t> | ||||
| <t>The IETF LLC is expected to conduct its work according to the following princ | <ul spacing="normal"> | |||
| iples:</t> | <li>Transparency. The IETF LLC is expected to keep the IETF community | |||
| informed about its work, | ||||
| <t><list style="symbols"> | ||||
| <t>Transparency. The IETF LLC is expected to keep the IETF community informed | ||||
| about its work, | ||||
| subject to reasonable confidentiality concerns, and to engage with the community to obtain | subject to reasonable confidentiality concerns, and to engage with the community to obtain | |||
| consensus-based community input on key issues and otherwise as needed. The IETF community expects | consensus-based community input on key issues and otherwise as needed. The IETF community expects | |||
| complete visibility into the financial and legal structure of the IETF LLC. This includes information | complete visibility into the financial and legal structure of the IETF LLC. This includes information | |||
| about the IETF LLC annual budget and associated regular financial reports, resul ts of financial and any | about the IETF LLC annual budget and associated regular financial reports, resul ts of financial and any | |||
| other independent audits, tax filings, significant contracts or other significan | other independent audits, tax filings, significant contracts, or other significa | |||
| t long-term financial | nt long-term financial | |||
| commitments that bind the IETF LLC. Whatever doesn’t have a specific | commitments that bind the IETF LLC. Whatever doesn't have a specific | |||
| justification for being kept confidential is expected to be made public. The Boa rd is expected to develop | justification for being kept confidential is expected to be made public. The Boa rd is expected to develop | |||
| and maintain a public list of confidential items, describing the nature of the i nformation and the reason | and maintain a public list of confidential items, describing the nature of the i nformation and the reason | |||
| for confidentiality. The Board will also publish its operating procedures.</t> | for confidentiality. The Board will also publish its operating procedures.</li> | |||
| <t>Responsiveness to the community. The IETF LLC is expected to act consistent | <li>Responsiveness to the community. The IETF LLC is expected to act c | |||
| ly with the documented consensus of the IETF community, to be responsive to the | onsistently with the documented consensus of the IETF community, to be responsiv | |||
| community’s needs, and to adapt its decisions in response to consensus-based com | e to the community's needs, and to adapt its decisions in response to consensus- | |||
| munity feedback.</t> | based community feedback.</li> | |||
| <t>Diligence. The IETF LLC is expected to act responsibly so as to minimize ri | <li>Diligence. The IETF LLC is expected to act responsibly so as to mi | |||
| sks to IETF participants and to the future of the IETF as a whole, such as finan | nimize risks to IETF participants and to the future of the IETF as a whole, such | |||
| cial risks.</t> | as financial risks.</li> | |||
| <t>Unification: The IETF LLC provides the corporate legal home for the IETF, t | <li>Unification: The IETF LLC provides the corporate legal home for th | |||
| he Internet | e IETF, the Internet | |||
| Architecture Board (IAB), and the Internet Research Task Force (IRTF), and | Architecture Board (IAB), and the Internet Research Task Force (IRTF), and | |||
| financial support for the operation of the RFC Editor.</t> | financial support for the operation of the RFC Editor.</li> | |||
| <t>Transfer or Dissolution: Consistent with <xref target="IETF-LLC-A"/>, the I | <li>Transfer or Dissolution: Consistent with <xref target="IETF-LLC-A" | |||
| ETF LLC subsidiary may be transferred from ISOC to | format="default"/>, the IETF LLC subsidiary may be transferred from ISOC to | |||
| another organization, at the request of either party. Similarly, the IETF LLC ma y be dissolved if necessary. Should | another organization, at the request of either party. Similarly, the IETF LLC ma y be dissolved if necessary. Should | |||
| either event occur, the IETF community should be closely involved in any decisio ns and plans. Any transfer, | either event occur, the IETF community should be closely involved in any decisio ns and plans. Any transfer, | |||
| transition, or dissolution should be conducted carefully and with minimal potent | transition, or dissolution should be conducted carefully and with minimal potent | |||
| ial disruption to the IETF.</t> | ial disruption to the IETF.</li> | |||
| </list></t> | </ul> | |||
| <t>The transparency and responsiveness principles are designed to addres | ||||
| <t>The transparency and responsiveness principles are designed to address the co | s the concern outlined in | |||
| ncern outlined in Section 3.3 of <xref target="I-D.haberman-iasa20dt-recs"/> abo | <xref target="I-D.haberman-iasa20dt-recs" section="3.3" sectionFormat="of"/> abo | |||
| ut the need for improved timeliness of sharing of information and decisions and | ut the need for improved timeliness of sharing of information and decisions and | |||
| seeking community comments. The issue of increased transparency was important th | seeking community comments. The issue of increased transparency was important th | |||
| roughout the IASA 2.0 process, with little to no dissent. It was recognized tha | roughout the IASA 2.0 process, with little to no dissent. It was recognized tha | |||
| t there will naturally be confidentiality requirements about some aspects of con | t there will naturally be confidentiality requirements about some aspects of con | |||
| tracting, personnel matters, and other narrow areas.</t> | tracting, personnel matters, and other narrow areas.</t> | |||
| </section> | ||||
| </section> | <section anchor="principles-of-the-ietf-and-isoc-relationship" numbered="t | |||
| <section anchor="principles-of-the-ietf-and-isoc-relationship" title="Principles | rue" toc="default"> | |||
| of the IETF and ISOC Relationship"> | <name>Principles of the IETF and ISOC Relationship</name> | |||
| <t>The principles of the relationship between the IETF and ISOC are outl | ||||
| <t>The principles of the relationship between the IETF and ISOC are outlined in | ined in <xref target="RFC8712" format="default"/>. | |||
| <xref target="I-D.ietf-iasa2-rfc2031bis"/>. | ||||
| In short, the IETF is responsible for the development of the Internet Standards and ISOC aids the IETF by | In short, the IETF is responsible for the development of the Internet Standards and ISOC aids the IETF by | |||
| providing it a legal entity within which the IETF LLC exists, as well as with fi nancial support.</t> | providing it a legal entity within which the IETF LLC exists, as well as with fi nancial support.</t> | |||
| </section> | ||||
| </section> | <section anchor="relationship-of-the-ietf-llc-board-to-the-ietf-leadership | |||
| <section anchor="relationship-of-the-ietf-llc-board-to-the-ietf-leadership" titl | " numbered="true" toc="default"> | |||
| e="Relationship of the IETF LLC Board to the IETF Leadership"> | <name>Relationship of the IETF LLC Board to the IETF Leadership</name> | |||
| <t>The IETF LLC Board is directly accountable to the IETF community for | ||||
| <t>The IETF LLC Board is directly accountable to the IETF community for the | the | |||
| performance of the IASA 2.0. However, the nature of the Board’s work | performance of the IASA 2.0. However, the nature of the Board's work | |||
| involves treating the IESG, IRTF, and IAB as major internal customers of the | involves treating the IESG, IRTF, and IAB as major internal customers of the | |||
| administrative support services. The Board and the IETF Executive Director shou ld not | administrative support services. The Board and the IETF Executive Director shou ld not | |||
| consider their work successful unless the IESG, IRTF, and IAB are also | consider their work successful unless the IESG, IRTF, and IAB are also | |||
| satisfied with the administrative support that the IETF is receiving.</t> | satisfied with the administrative support that the IETF is receiving.</t> | |||
| </section> | ||||
| </section> | <section anchor="review-of-ietf-executive-director-and-ietf-llc-board-deci | |||
| <section anchor="review-of-ietf-executive-director-and-ietf-llc-board-decisions" | sions" numbered="true" toc="default"> | |||
| title="Review of IETF Executive Director and IETF LLC Board Decisions"> | <name>Review of IETF Executive Director and IETF LLC Board Decisions</na | |||
| <t>The IETF LLC Board is directly accountable to the IETF community for the perf | me> | |||
| ormance of the IASA 2.0, including hiring and managing the IETF Executive Direct | <t>The IETF LLC Board is directly accountable to the IETF community for | |||
| or. In extreme cases of dissatisfaction with the IETF LLC, the IETF community ca | the performance of the IASA 2.0, including hiring and managing the IETF Executiv | |||
| n utilize the recall process as noted in <xref target="director-removal"/>.</t> | e Director. In extreme cases of dissatisfaction with the IETF LLC, the IETF comm | |||
| unity can utilize the recall process as noted in <xref target="director-removal" | ||||
| <t>Anyone in the community of IETF participants may ask the Board for a formal r | format="default"/>.</t> | |||
| eview of a decision or action by the IETF Executive Director or Board if they be | <t>Anyone in the community of IETF participants may ask the Board for a | |||
| lieve this was not undertaken in accordance with IETF BCPs or IETF | formal review of a decision or action by the IETF Executive Director or Board if | |||
| they believe this was not undertaken in accordance with IETF BCPs or IETF | ||||
| LLC Board policies and procedures.</t> | LLC Board policies and procedures.</t> | |||
| <t>A formal request for review must be addressed to the IETF LLC Board c | ||||
| <t>A formal request for review must be addressed to the IETF LLC Board chair and | hair and must include a description of the decision or action to be reviewed, an | |||
| must include a description of the decision or action to be reviewed, an explana | explanation of how, in the requestor's opinion, the decision or action violates | |||
| tion of how, in the requestor’s opinion, the decision or action violates the BCP | the BCPs or IASA 2.0 operational guidelines, and a suggestion for how the situa | |||
| s or IASA 2.0 operational guidelines, and a suggestion for how the situation cou | tion could be rectified.</t> | |||
| ld be rectified.</t> | <t>The IETF LLC shall respond to such requests within a reasonable perio | |||
| d, typically within 90 days, and shall publicly publish information about the re | ||||
| <t>The IETF LLC shall respond to such requests within a reasonable period, typic | quest and the corresponding response and/or result.</t> | |||
| ally within 90 days, and shall publicly publish information about the request an | </section> | |||
| d the corresponding response and/or result.</t> | <section anchor="termination-and-change" numbered="true" toc="default"> | |||
| <name>Termination and Change</name> | ||||
| </section> | <t>Any major change to the IASA 2.0 arrangements shall require | |||
| <section anchor="termination-and-change" title="Termination and Change"> | ||||
| <t>Any major change to the IASA 2.0 arrangements shall require | ||||
| community consensus and deliberation and shall be reflected by a | community consensus and deliberation and shall be reflected by a | |||
| subsequent Best Current Practice (BCP) document.</t> | subsequent Best Current Practice (BCP) document.</t> | |||
| </section> | ||||
| </section> | </section> | |||
| </section> | <section anchor="structure-of-iasa2" numbered="true" toc="default"> | |||
| <section anchor="structure-of-iasa2" title="Structure of IASA2"> | <name>Structure of IASA 2.0</name> | |||
| <section anchor="staff-responsibilities" numbered="true" toc="default"> | ||||
| <section anchor="staff-responsibilities" title="IETF Executive Director and Staf | <name>IETF Executive Director and Staff Responsibilities</name> | |||
| f Responsibilities"> | <t>The IETF LLC is led by an IETF Executive Director chosen by the Board | |||
| . The IETF Executive Director is responsible for managing the day-to-day operati | ||||
| <t>The IETF LLC is led by an IETF Executive Director chosen by the Board. The IE | ons of the IETF LLC, including hiring staff to perform various operational funct | |||
| TF Executive Director is responsible for managing the day-to-day operations of t | ions. The IETF Executive Director and any staff may be employees or independent | |||
| he IETF LLC, including hiring staff to perform various operational functions. Th | contractors.</t> | |||
| e IETF Executive Director and any staff may be employees or independent contract | <t>Allowing for the division of responsibilities among multiple staff me | |||
| ors.</t> | mbers and contractors is designed to address some of the concerns raised in | |||
| Section <xref target="I-D.haberman-iasa20dt-recs" section="3.2" sectionFormat="b | ||||
| <t>Allowing for the division of responsibilities among multiple staff members an | are"/> (Lack of Resources) and | |||
| d contractors is designed to address some of the concerns raised in Section 3.2 | Section <xref target="I-D.haberman-iasa20dt-recs" section="3.4" sectionFormat="b | |||
| (Lack of Resources) and Section 3.4 (Funding/Operating Model Mismatch and Rising | are"/> (Funding/Operating Model Mismatch and Rising Costs) of <xref target="I-D. | |||
| Costs) of <xref target="I-D.haberman-iasa20dt-recs"/>.</t> | haberman-iasa20dt-recs" format="default"/>.</t> | |||
| <t>Based on the amount of work previously undertaken by the IAD and othe | ||||
| <t>Based on the amount of work previously undertaken by the IAD and others invol | rs involved in the IETF administration, the design of the IETF LLC anticipated t | |||
| ved in the IETF administration, the design of the IETF LLC anticipated that the | hat the IETF Executive Director may need to hire multiple additional staff membe | |||
| IETF Executive Director may need to hire multiple additional staff members. For | rs. For example, resources to manage fundraising, to manage the various contract | |||
| example, resources to manage fundraising, to manage the various contractors that | ors that are engaged to fulfill the IETF's administrative needs, and to support | |||
| are engaged to fulfill the IETF’s administrative needs, and to support outreach | outreach and communications were envisioned.</t> | |||
| and communications were envisioned.</t> | <t>The IETF has historically benefited from the use of contractors for | |||
| accounting, finance, meeting planning, administrative assistance, | ||||
| <t>The IETF has historically benefited from the use of contractors for accountin | legal counsel, tools, and web site support, as well as other services | |||
| g, finance, meeting planning, administrative assistance, legal counsel, tools, a | related to the standards process (e.g., RFC Editor and IANA). Prior to ma | |||
| nd web site support, as well as other services related to the standards process | king the transition from IASA to IASA 2.0, the IETF budget reflected specific su | |||
| (RFC Editor and IANA). Prior to making the transition from IASA to IASA 2.0, the | pport from ISOC for communications and fundraising as well as some general suppo | |||
| IETF budget reflected specific support from ISOC for communications and fundrai | rt for accounting, finance, legal, and other services. The division of responsib | |||
| sing as well as some general support for accounting, finance, legal, and other s | ilities between staff and contractors is at the discretion of the IETF Executive | |||
| ervices. The division of responsibilities between staff and contractors is at th | Director and their staff.</t> | |||
| e discretion of the IETF Executive Director and their staff.</t> | <t>The IETF has a long history of community involvement in the execution | |||
| of certain administrative functions, in particular development of IETF tools, t | ||||
| <t>The IETF has a long history of community involvement in the execution of cert | he operation of the meeting network by the Network Operations Center (NOC), and | |||
| ain administrative functions, in particular development of IETF tools, the NOC’s | some outreach and communications activities conducted by the Education and Mento | |||
| operation of the meeting network, and some outreach and communications activiti | ring Directorate. The IETF LLC staff is expected to respect the IETF community's | |||
| es conducted by the Education and Mentoring Directorate. The IETF LLC staff is e | wishes about community involvement in these and other functions going forward a | |||
| xpected to respect the IETF community’s wishes about community involvement in th | s long as the staff feels that they can meet the otherwise-stated needs of the c | |||
| ese and other functions going forward as long as the staff feels that they can m | ommunity. Establishing the framework to allow the IETF LLC to staff each adminis | |||
| eet the otherwise-stated needs of the community. Establishing the framework to a | trative function as appropriate may require the IETF community to document its c | |||
| llow the IETF LLC to staff each administrative function as appropriate may requi | onsensus expectations in areas where no documentation currently exists.</t> | |||
| re the IETF community to document its consensus expectations in areas where no d | <t>In summary, the IETF Executive Director, with support from the team t | |||
| ocumentation currently exists.</t> | hat they alone direct and lead, is responsible for:</t> | |||
| <ul spacing="normal"> | ||||
| <t>In summary, the IETF Executive Director, with support from the team that they | <li>Developing and refining an annual budget and other strategic finan | |||
| alone direct and lead, is responsible for:</t> | cial planning documents at the direction of the Board.</li> | |||
| <li>Executing on the annual budget, including reporting to the Board r | ||||
| <t><list style="symbols"> | egularly with forecasts and actual performance to budget.</li> | |||
| <t>Developing and refining an annual budget and other strategic financial plan | <li>Hiring and/or contracting the necessary resources to meet their go | |||
| ning documents at the direction of the Board.</t> | als, within the defined limits of the IETF | |||
| <t>Executing on the annual budget, including reporting to the Board regularly | Executive Director's authority and within the approved budget. This includes man | |||
| with forecasts and actual performance to budget.</t> | aging and leading any such | |||
| <t>Hiring and/or contracting the necessary resources to meet their goals, with | resources, including performing regular performance reviews.</li> | |||
| in the defined limits of the IETF | <li>Following the pre-approval guidelines set forth by the Board for c | |||
| Executive Director’s authority and within the approved budget. This includes man | ontracts or other decisions that have financial costs that exceed a certain thre | |||
| aging and leading any such | shold of significance. Such thresholds are expected to be set reasonably high so | |||
| resources, including performing regular performance reviews.</t> | that the need for such approvals is infrequent and only occurs when something i | |||
| <t>Following the pre-approval guidelines set forth by the Board for contracts | s truly significant or otherwise exceptional. It is expected that the IETF Execu | |||
| or other decisions that have financial costs that exceed a certain threshold of | tive Director is sufficiently empowered to perform the job on a day-to-day basis | |||
| significance. Such thresholds are expected to be set reasonably high so that the | , being held accountable for meeting high-level goals rather than being microman | |||
| need for such approvals is infrequent and only occurs when something is truly s | aged.</li> | |||
| ignificant or otherwise exceptional. It is expected that the IETF Executive Dire | <li>Regularly updating the Board on operations and other notable issue | |||
| ctor is sufficiently empowered to perform the job on a day-to-day basis, being h | s as reasonable and appropriate.</li> | |||
| eld accountable for meeting high level goals rather than micromanaged.</t> | <li>Ensuring that all staff and/or other resources comply with any app | |||
| <t>Regularly updating the Board on operations and other notable issues as reas | licable policies established or approved by the Board, such as ethics guidelines | |||
| onable and appropriate.</t> | and/or a code of conduct.</li> | |||
| <t>Ensuring that all staff and/or other resources comply with any applicable p | </ul> | |||
| olicies established or approved by the Board, such as ethics guidelines and/or a | </section> | |||
| code of conduct.</t> | <section anchor="board-responsibilities" numbered="true" toc="default"> | |||
| </list></t> | <name>IETF LLC Board Responsibilities</name> | |||
| <t>This section is intended to provide a summary of key IETF LLC Board r | ||||
| </section> | esponsibilities, | |||
| <section anchor="board-responsibilities" title="IETF LLC Board Responsibilities" | ||||
| > | ||||
| <t>This section is intended to provide a summary of key IETF LLC Board responsib | ||||
| ilities, | ||||
| but the precise and legally binding responsibilities are defined in the LLC Agre ement | but the precise and legally binding responsibilities are defined in the LLC Agre ement | |||
| <xref target="IETF-LLC-A"/> and applicable law. To the extent to which there are | <xref target="IETF-LLC-A" format="default"/> and applicable law. | |||
| unintentional differences | If there are unintentional differences or other | |||
| or other confusion between this document and these authoritative sources, these | confusion, the LLC Agreement and applicable law are authoritative.</t> | |||
| sources will | <t>Board members have fiduciary obligations imposed by the LLC Agreement | |||
| control over this document.</t> | and applicable law, | |||
| including duties of loyalty, care, and good faith. The Board is responsible | ||||
| <t>Board members have fiduciary obligations imposed by the LLC Agreement and app | for setting broad strategic direction for the LLC, adopting an annual budget, hi | |||
| licable law, | ring or terminating an | |||
| including duties of loyalty, care and good faith. The Board is responsible to se | IETF Executive Director (or amending the terms of their engagement), adopting an | |||
| t broad strategic direction | y employee benefit plans, | |||
| for the LLC, and adopt an annual budget, hire or terminate an | consulting the relevant IETF communities on matters related to the LLC as approp | |||
| IETF Executive Director (or amend the terms of their engagement), adopt any empl | riate, approving any | |||
| oyee benefit plans, | changes to the LLC governance structure, incurring any debt, and approving enter | |||
| consult the relevant IETF communities on matters related to the LLC as appropria | ing into agreements | |||
| te, approve any | ||||
| changes to the LLC governance structure, incur any debt, and approve entering in | ||||
| to agreements | ||||
| that meet a significant materiality threshold to be determined by the Board. The IETF LLC | that meet a significant materiality threshold to be determined by the Board. The IETF LLC | |||
| Board is expected to delegate management of day-to-day activities and related de cision-making to staff.</t> | Board is expected to delegate management of day-to-day activities and related de cision-making to staff.</t> | |||
| <t>Per Section 5(d) of the LLC Agreement and as also described in | ||||
| <t>Per Section 5(d) of the LLC Agreement and as also described in <xref target=" | <xref target="principles" format="default"/> of this document, the Board | |||
| principles"/>, the Board shall, | shall, | |||
| as appropriate, act transparently and provide the IETF community with an opportu nity to review | as appropriate, act transparently and provide the IETF community with an opportu nity to review | |||
| and discuss any proposed changes to the IETF LLC structure prior to their adopti on.</t> | and discuss any proposed changes to the IETF LLC structure prior to their adopti on.</t> | |||
| <t>The role of the Board is to ensure that the strategy and conduct of t | ||||
| <t>The role of the Board is to ensure that the strategy and conduct of the IETF | he IETF LLC is consistent with the IETF's needs -- both its concrete needs and i | |||
| LLC is consistent with the IETF’s needs – both its concrete needs and its needs | ts needs for transparency and accountability. The Board is not intended to dire | |||
| for transparency and accountability. The Board is not intended to directly defi | ctly define the IETF's needs; to the extent that is required, the IETF community | |||
| ne the IETF’s needs; to the extent that is required, the IETF community should d | should document its needs in consensus-based RFCs (e.g., as the community did i | |||
| ocument its needs in consensus-based RFCs (e.g., as the community did in <xref t | n <xref target="RFC8718" format="default"/>) and provide more detailed input via | |||
| arget="I-D.ietf-mtgvenue-iaoc-venue-selection-process"/>) and provide more detai | consultations with the Board (such as takes place on email discussion lists or | |||
| led input via consultations with the Board (such as takes place on email discuss | at IETF meetings).</t> | |||
| ion lists or at IETF meetings).</t> | <t>Key IETF LLC Board responsibilities include:</t> | |||
| <ul spacing="normal"> | ||||
| <t>Key IETF LLC Board responsibilities include:</t> | <li>Setting broad strategic direction for the LLC.</li> | |||
| <li>Hiring or terminating an IETF Executive Director (or amending the | ||||
| <t><list style="symbols"> | terms of their engagement).</li> | |||
| <t>Set broad strategic direction for the LLC.</t> | <li>Delegating management of day-to-day activities and related decisio | |||
| <t>Hire or terminate an IETF Executive Director (or amending the terms of thei | n-making to staff.</li> | |||
| r engagement).</t> | <li>Adopting any employee benefit plans.</li> | |||
| <t>Delegate management of day-to-day activities and related decision-making to | <li>Consulting the relevant IETF communities on matters related to the | |||
| staff.</t> | LLC, as appropriate.</li> | |||
| <t>Adopt any employee benefit plans.</t> | <li>Approving any changes to the LLC governance structure.</li> | |||
| <t>Consult the relevant IETF communities on matters related to the LLC, as app | <li>Adopting an annual budget and, as necessary, incur any debt.</li> | |||
| ropriate.</t> | <li>Preparing accurate and timely financial statements for ISOC, in ac | |||
| <t>Approve any changes to the LLC governance structure.</t> | cordance with generally | |||
| <t>Adopt an annual budget and, as necessary, incur any debt.</t> | accepted accounting principles.</li> | |||
| <t>Prepare accurate and timely financial statements for ISOC, and in accordanc | <li>Providing assistance to help facilitate ISOC's tax compliance, inc | |||
| e with generally | luding but not limited to assistance related to preparing the Form 990 and respo | |||
| accepted accounting principles.</t> | nding to any United States Internal Revenue Service (IRS) questions and audits.< | |||
| <t>Provide assistance to help facilitate ISOC’s tax compliance, including but | /li> | |||
| not limited to assistance related to preparing the Form 990 and responding to an | <li>Approving entering into agreements that meet a significant materia | |||
| y IRS questions and audits.</t> | lity threshold to be | |||
| <t>Approve entering into agreements that that meet a significant materiality t | determined by the Board.</li> | |||
| hreshold to be | <li>Limiting its activities to the purposes as set forth in Section 4 | |||
| determined by the Board.</t> | of the LLC Agreement, in a manner | |||
| <t>Limit its activities to the purposes as set forth in Section 4 of the LLC A | consistent with ISOC's charitable purposes.</li> | |||
| greement, in a manner | <li>Establishing an investment policy.</li> | |||
| consistent with ISOC’s charitable purposes.</t> | <li>Using best efforts to conduct all of its activities in strict comp | |||
| <t>Establish an investment policy.</t> | liance with the LLC Agreement and all | |||
| <t>Use best efforts to conduct all of its activities in strict compliance with | applicable laws, rules, and regulations.</li> | |||
| the LLC Agreement and all | <li>Ensuring that IETF LLC is run in a manner that is transparent and | |||
| applicable laws, rules and regulations.</t> | accountable to the IETF community.</li> | |||
| <t>Ensure that IETF LLC is run in a manner that is transparent and accountable | <li>Developing policies, including those noted in <xref target="llc-po | |||
| to the IETF community;</t> | licies" format="default"/>, procedures, and a compliance program.</li> | |||
| <t>Develop policies, including those noted in <xref target="llc-policies"/>), | <li>Obtaining Commercial General Liability and other appropriate insur | |||
| procedures, and a compliance program.</t> | ance policies, with | |||
| <t>Obtain Commercial General Liability and other appropriate insurance policie | agreed-upon coverage limits.</li> | |||
| s, with | <li>Recruiting new Directors for consideration in all of the various a | |||
| agreed-upon coverage limits.</t> | ppointment processes.</li> | |||
| <t>Recruit new Directors for consideration in all of the various appointment p | </ul> | |||
| rocesses.</t> | </section> | |||
| </list></t> | <section anchor="board-design-goals" numbered="true" toc="default"> | |||
| <name>Board Design Goals</name> | ||||
| </section> | <t>A goal of this Board composition is to balance the need for the IETF | |||
| <section anchor="board-design-goals" title="Board Design Goals"> | LLC to be accountable to the IETF community with the need for this Board to have | |||
| the expertise necessary to oversee a small non-profit company. The Board is sma | ||||
| <t>A goal of this Board composition is to balance the need for the IETF LLC to b | ller than the previous IAOC and the other leadership bodies of the IETF, in part | |||
| e accountable to the IETF community with the need for this Board to have the exp | to keep the Board focused on its rather limited set of strategic responsibiliti | |||
| ertise necessary to oversee a small non-profit company. The Board is smaller tha | es as noted in <xref target="board-responsibilities" format="default"/>.</t> | |||
| n the previous IAOC and the other leadership bodies of the IETF, in part to keep | <t>This board structure, with limited strategic responsibilities noted i | |||
| the Board focused on its rather limited set of strategic responsibilities as no | n <xref target="board-responsibilities" format="default"/> and limited size, tog | |||
| ted in <xref target="board-responsibilities"/>.</t> | ether with the staff responsibilities noted in <xref target="staff-responsibilit | |||
| ies" format="default"/>, is designed to overcome the challenges described in | ||||
| <t>This board structure, with limited strategic responsibilities noted in <xref | <xref target="I-D.haberman-iasa20dt-recs" section="3.1.4" sectionFormat="of"/> | |||
| target="board-responsibilities"/> and limited size, together with the staff resp | concerning oversight. This establishes a clear line of oversight over staff perf | |||
| onsibilities noted in <xref target="staff-responsibilities"/>, is designed to ov | ormance: the IETF LLC Board oversees the IETF Executive Director's performance a | |||
| ercome the challenges described in Section 3.1.4 of <xref target="I-D.haberman-i | nd has actual legal authority to remove a non-performing IETF Executive Director | |||
| asa20dt-recs"/> concerning oversight. This establishes a clear line of oversight | . The IETF Executive Director is responsible for the day-to-day operation of the | |||
| over staff performance: the IETF LLC Board oversees the IETF Executive Director | IETF LLC.</t> | |||
| ’s performance and has actual legal authority to remove a non-performing IETF Ex | <t>Finally, the Board is expected to operate transparently, to further a | |||
| ecutive Director. The IETF Executive Director is responsible for the day-to-day | ddress the concern raised in | |||
| operation of the IETF LLC.</t> | <xref target="I-D.haberman-iasa20dt-recs" section="3.3" sectionFormat="of"/>. Th | |||
| e default transparency rule arrived at during the IASA 2.0 design process is det | ||||
| <t>Finally, the Board would be expected to operate transparently, to further add | ailed in <xref target="principles" format="default"/>. The Board will need to es | |||
| ress the concern raised in Section 3.3 of <xref target="I-D.haberman-iasa20dt-re | tablish how it will meet that commitment.</t> | |||
| cs"/>. The default transparency rule arrived at during the IASA 2.0 design proce | </section> | |||
| ss is detailed above in <xref target="principles"/>. The Board will need to esta | </section> | |||
| blish how it will meet that commitment.</t> | <section anchor="board" numbered="true" toc="default"> | |||
| <name>IETF LLC Board Membership, Selection, and Accountability</name> | ||||
| </section> | <t>The section outlines the composition of the IETF LLC Board, selection o | |||
| </section> | f IETF LLC Board Directors, and related details.</t> | |||
| <section anchor="board" title="IETF LLC Board Membership, Selection and Accounta | <section anchor="board-composition" numbered="true" toc="default"> | |||
| bility"> | <name>Board Composition</name> | |||
| <t>There is a minimum of 5 directors, which is expandable to 6 or 7. | ||||
| <t>The section outlines the composition of the IETF LLC Board, selection of IETF | The IETF LLC Board is comprised of the following:</t> | |||
| LLC Board Directors, and related details.</t> | <ul spacing="normal"> | |||
| <li>1 IETF Chair or delegate selected by the IESG</li> | ||||
| <section anchor="board-composition" title="Board Composition"> | <li>1 Appointed by the ISOC Board of Trustees</li> | |||
| <li>3 Selected by the IETF Nominating Committee (NomCom), confirmed by | ||||
| <t>There is a minimum of 5 directors, expandable to 6 or 7.</t> | the IESG</li> | |||
| <li>Up to 2 Appointed by the IETF LLC Board itself, on an as-needed ba | ||||
| <t><list style="symbols"> | sis, confirmed by the IESG</li> | |||
| <t>1 IETF Chair or delegate selected by the IESG</t> | </ul> | |||
| <t>1 Appointed by the ISOC Board of Trustees</t> | <t>For the first slot listed above, the presumption is that the IETF | |||
| <t>3 Selected by the IETF NomCom, confirmed by the IESG</t> | Chair will serve on the board. At the IESG's discretion, another area | |||
| <t>Up to 2 Appointed by the IETF LLC board itself, on an as-needed basis, conf | ||||
| irmed by the IESG</t> | ||||
| </list></t> | ||||
| <t>For the first slot listed above, the presumption is that the IETF | ||||
| Chair will serve on the board. At the IESG’s discretion, another area | ||||
| director may serve instead, or exceptionally the IESG may run a | director may serve instead, or exceptionally the IESG may run a | |||
| selection process to appoint a director. The goal of having this slot | selection process to appoint a director. The goal of having this slot | |||
| on the board is to maintain coordination and communication between the | on the board is to maintain coordination and communication between the | |||
| board and the IESG.</t> | board and the IESG.</t> | |||
| </section> | ||||
| </section> | <section anchor="llc-directors" numbered="true" toc="default"> | |||
| <section anchor="llc-directors" title="IETF LLC-Appointed Directors"> | <name>IETF LLC-Appointed Directors</name> | |||
| <t>As noted above, a maximum of two Directors may be appointed by the | ||||
| <t>As noted above, a maximum of two Directors may be appointed by the | ||||
| IETF LLC Board. They can obviously choose to appoint none, one, or | IETF LLC Board. They can obviously choose to appoint none, one, or | |||
| two. These appointments need not be on an exceptional basis, but | t | |||
| wo. These appointments need not be on an exceptional basis; they | ||||
| can be routine, and may occur at any time of the year since it is | can be routine, and may occur at any time of the year since it is | |||
| on an as-needed basis.</t> | on an as-needed basis.</t> | |||
| <t>The appointment of a Board-appointed Director requires a two-thirds | ||||
| <t>The appointment of a Board-appointed Director requires a two-thirds | ||||
| majority vote of the Directors then in office, and the appointee shall | majority vote of the Directors then in office, and the appointee shall | |||
| take office immediately upon appointment and IESG confirmation. The term of each appointment | take office immediately upon appointment and IESG confirmation. The term of each appointment | |||
| is designated by the Board, with the maximum term being three years, | is designated by the Board, with the maximum term being three years, | |||
| or until their earlier resignation, removal or death. The Board may | or until their earlier resignation, removal, or death. The Board may | |||
| decide on a case-by-case basis how long each term shall be, factoring | decide on a case-by-case basis how long each term shall be, factoring | |||
| in the restriction for consecutive terms in <xref target="term-limit"/>.</t> | in the restriction for consecutive terms in <xref target="term-limit" format="de | |||
| fault"/>.</t> | ||||
| </section> | </section> | |||
| <section anchor="director-recruitment" title="Recruiting IETF LLC Board Director | <section anchor="director-recruitment" numbered="true" toc="default"> | |||
| s"> | <name>Recruiting IETF LLC Board Directors</name> | |||
| <t>The Board itself is expected to take an active role in recruiting pot | ||||
| <t>The Board itself is expected to take an active role in recruiting potential n | ential new Directors, regardless of the process that may be used to appoint them | |||
| ew Directors, regardless of the process that may be used to appoint them. In par | . In particular, the NomCom is primarily focused on considering requirements exp | |||
| ticular, the NomCom is primarily focused on considering requirements expressed b | ressed by the Board and others, reviewing community feedback on candidates, cond | |||
| y the Board and others, reviewing community feedback on candidates, conducting c | ucting candidate interviews, and ultimately appointing Directors. The Board and | |||
| andidate interviews, and ultimately appointing Directors. The Board and others | others can recruit potential Directors and get them into the consideration proc | |||
| can recruit potential Directors and get them into the consideration process of t | ess of the NomCom or into open consideration processes of the other appointing b | |||
| he NomCom or into open considerations processes of the other appointing bodies i | odies if those bodies choose to use such processes.</t> | |||
| f those bodies choose to use such processes.</t> | </section> | |||
| <section anchor="term-length" numbered="true" toc="default"> | ||||
| </section> | <name>IETF LLC Board Director Term Length</name> | |||
| <section anchor="term-length" title="IETF LLC Board Director Term Length"> | <t>The term length for a Director is three years. The exceptions to this | |||
| <t>The term length for a Director is three years. The exceptions to this | ||||
| guideline are:</t> | guideline are:</t> | |||
| <ul spacing="normal"> | ||||
| <t><list style="symbols"> | <li>The terms for some Directors during the first full formation of | |||
| <t>For the terms for some Directors during the first full formation of | ||||
| the IETF LLC Board in order to establish staggered terms and for any | the IETF LLC Board in order to establish staggered terms and for any | |||
| appointments to fill a vacancy.</t> | appointments to fill a vacancy.</li> | |||
| <t>The Director slot occupied by the IETF Chair ex officio or a | <li>The Director slot occupied by the IETF Chair ex officio or a | |||
| delegate selected by the IESG will serve a two-year term. This | delegate selected by the IESG will serve a two-year term. This | |||
| applies regardless of whether the appointed individual is on the | applies regardless of whether the appointed individual is on the | |||
| IESG, rotates off the IESG during the two-year term, or is not on | IESG, rotates off the IESG during the two-year term, or is not on | |||
| the IESG. This makes the term length for this slot the same as the | the IESG. This makes the term length for this slot the same as the | |||
| term lengths established in <xref target="I-D.ietf-iasa2-rfc7437bis"></xref>, Se | term lengths established in <xref target="RFC8713" section="3.4" sectionFormat=" | |||
| ction | comma" format="default"/>.</li> | |||
| 3.4.</t> | </ul> | |||
| </list></t> | </section> | |||
| <section anchor="term-limit" numbered="true" toc="default"> | ||||
| </section> | <name>IETF LLC Board Director Limit</name> | |||
| <section anchor="term-limit" title="IETF LLC Board Director Limit"> | <t>A director may serve no more than two consecutive terms. | |||
| <t>A director may serve no more than two consecutive terms. | ||||
| A director cannot serve a third term until three years have | A director cannot serve a third term until three years have | |||
| passed since their second consecutive term. An | passed since their second consecutive term. An | |||
| exception is if a Director role is occupied by the IETF Chair ex | exception is if a Director role is occupied by the IETF Chair ex | |||
| officio, since that person’s service is governed instead by the term | officio, since that person's service is governed instead by the term | |||
| lengths established in <xref target="I-D.ietf-iasa2-rfc7437bis"/>, Section 3.4.< | lengths established in <xref target="RFC8713" section="3.4" sectionFormat="comma | |||
| /t> | " format="default"/>.</t> | |||
| <t>The term limits specified above apply to an individual, even if that | ||||
| <t>The term limits specified above apply to an individual, even if that | ||||
| individual is appointed in different ways over time. For example, an | individual is appointed in different ways over time. For example, an | |||
| individual appointed to two terms by the ISOC Board of Trustees | individual appointed to two terms by the ISOC Board of Trustees | |||
| may not immediately be appointed to a third term by the IETF | may not immediately be appointed to a third term by the IETF | |||
| NomCom. A Director appointed by the IETF LLC itself may only | NomCom. A Director appointed by the IETF LLC itself may only | |||
| serve for one term by that appointment method, and any subsequent | serve for one term by that appointment method, and any subsequent | |||
| terms would have to be via other methods; in any case, the term | terms would have to be via other methods; in any case, the term | |||
| limits above apply to that individual.</t> | limits above apply to that individual.</t> | |||
| <t>Lastly, partial terms of less than three years for the initial appoin | ||||
| <t>Lastly, partial terms of less than three years for the initial appointments t | tments to the first full Board, for which some Directors will have terms of one | |||
| o the first full board, for which some Directors will have terms of one or two y | or two years, do not count against the term limit.</t> | |||
| ears, do not count against the term limit.</t> | <t>The limit on consecutive terms supports the healthy regular introduct | |||
| ion of new ideas and energy into the Board and mitigates potential long-term ris | ||||
| <t>The limit on consecutive terms supports the healthy regular introduction of n | k of ossification or conflict, without adversely impacting the potential pool of | |||
| ew ideas and energy into the Board and mitigates potential long-term risk of oss | director candidates over time.</t> | |||
| ification or conflict, without adversely impacting the potential pool of directo | </section> | |||
| r candidates over time.</t> | <section anchor="staggered-terms" numbered="true" toc="default"> | |||
| <name>Staggered Terms</name> | ||||
| </section> | <t>The Internet Society Board of Trustees, the IESG, the Nominating Comm | |||
| <section anchor="staggered-terms" title="Staggered Terms"> | ittee, and the | |||
| IETF LLC Board are expected to coordinate with each other to ensure that | ||||
| <t>The Internet Society Board of Trustees, the IESG, the Nominating Committee, a | ||||
| nd the | ||||
| Board are expected to coordinate with each other to ensure that | ||||
| collectively their appointment or selection processes provide for no | collectively their appointment or selection processes provide for no | |||
| more than three Directors’ terms concluding in the same year.</t> | more than three Directors' terms concluding in the same year.</t> | |||
| </section> | ||||
| </section> | <section anchor="director-removal" numbered="true" toc="default"> | |||
| <section anchor="director-removal" title="IETF LLC Board Director Removal"> | <name>IETF LLC Board Director Removal</name> | |||
| <t>NomCom-appointed and IESG-appointed Directors may be removed with or | ||||
| <t>NomCom-appointed and IESG-appointed Directors may be removed with or without | without cause. A vote in favor of | |||
| cause. A vote in favor of | ||||
| removal must be no fewer than the number of Directors less two. So | removal must be no fewer than the number of Directors less two. So | |||
| for example, if there are seven directors, then five votes are | for example, if there are seven directors, then five votes are | |||
| required. Directors may also be removed via the IETF recall process | required. Directors may also be removed via the IETF recall process | |||
| defined in <xref target="I-D.ietf-iasa2-rfc7437bis"/>, Section 7.</t> | defined in <xref target="RFC8713" section="7" sectionFormat="comma" format="defa | |||
| ult"/>.</t> | ||||
| </section> | </section> | |||
| <section anchor="director-vacancy" title="Filling an IETF LLC Board Director Vac | <section anchor="director-vacancy" numbered="true" toc="default"> | |||
| ancy"> | <name>Filling an IETF LLC Board Director Vacancy</name> | |||
| <t>It shall be the responsibility of each respective body that appointed | ||||
| <t>It shall be the responsibility of each respective body that appointed or sele | or selected a Director that vacates the Board | |||
| cted a Director that vacates the Board | ||||
| to appoint a new Director to fill the vacancy. For example, if a Director selec ted by the NomCom departs the Board | to appoint a new Director to fill the vacancy. For example, if a Director selec ted by the NomCom departs the Board | |||
| prior to the end of their term for whatever reason, then it is the responsibilit y of the NomCom (using its mid-term | prior to the end of their term for whatever reason, then it is the responsibilit y of the NomCom (using its mid-term | |||
| rules, as specified in <xref target="I-D.ietf-iasa2-rfc7437bis"/>, Section 3.5) as the original appointing body to designate a | rules, as specified in <xref target="RFC8713" section="3.5" sectionFormat="comma " format="default"/>) as the original appointing body to designate a | |||
| replacement that will serve out the remainder of the term of the departed Direct or. However, this obligation will | replacement that will serve out the remainder of the term of the departed Direct or. However, this obligation will | |||
| not apply to vacancies in Board-appointed positions.</t> | not apply to vacancies in Board-appointed positions.</t> | |||
| </section> | ||||
| </section> | <section anchor="quorum" numbered="true" toc="default"> | |||
| <section anchor="quorum" title="Quorum"> | <name>Quorum</name> | |||
| <t>At all meetings of the Board, two-thirds of the Directors then in off | ||||
| <t>At all meetings of the Board, two-thirds of the Directors then in office shal | ice shall constitute | |||
| l constitute | ||||
| a quorum for the transaction of business. Unless a greater affirmative vote is e xpressly required for | a quorum for the transaction of business. Unless a greater affirmative vote is e xpressly required for | |||
| an action under applicable law, the LLC Agreement, or an applicable Board policy , the affirmative vote of | an action under applicable law, the LLC Agreement, or an applicable Board policy , the affirmative vote of | |||
| two-thirds of the Directors then in office shall be an act of the Board.</t> | two-thirds of the Directors then in office shall be an act of the Board.</t> | |||
| </section> | ||||
| </section> | <section anchor="voting" numbered="true" toc="default"> | |||
| <section anchor="voting" title="Board Voting"> | <name>Board Voting</name> | |||
| <t>Board decisions may be made either by vote communicated in a meeting | ||||
| <t>Board decisions may be made either by vote communicated in a meeting | ||||
| of the Board (including telephonic and video), or via an asynchronous | of the Board (including telephonic and video), or via an asynchronous | |||
| written (including electronic) process. Absentee voting and voting by | written (including electronic) process. Absentee voting and voting by | |||
| proxy shall not be permitted. If a quorum is not present at any | proxy shall not be permitted. | |||
| <!-- [rfced] What is meant by "other than announcement at the meeting"? | ||||
| Original: | ||||
| If a quorum is not present at any | ||||
| meeting of the Board, the Directors present may adjourn the meeting | ||||
| without notice, other than announcement at the meeting, until a | ||||
| quorum is present. | ||||
| --> | ||||
| If a quorum is not present at any | ||||
| meeting of the Board, the Directors present may adjourn the meeting | meeting of the Board, the Directors present may adjourn the meeting | |||
| without notice, other than announcement at the | without notice, other than announcement at the | |||
| meeting, until a quorum is present. Voting thresholds for Director | meeting, until a quorum is present. Voting thresholds for Director | |||
| removal are described in <xref target="director-removal"/>.</t> | removal are described in <xref target="director-removal" format="default"/>.</t> | |||
| </section> | ||||
| </section> | <section anchor="interim-board" numbered="true" toc="default"> | |||
| <section anchor="interim-board" title="Interim Board"> | <name>Interim Board</name> | |||
| <t>An initial interim Board was necessary in order to legally form and b | ||||
| <t>An initial interim Board was necessary in order to legally form and bootstrap | ootstrap the IETF LLC. As a result, an Interim Board was formed on a temporary b | |||
| the IETF LLC. As a result, an Interim Board was formed on a temporary basis unt | asis until the first full Board was constituted.</t> | |||
| il the first full board was constituted.</t> | <t>The interim Board was comprised of:</t> | |||
| <ul spacing="normal"> | ||||
| <t>The interim Board was comprised of:</t> | <li>The IETF chair, ex officio</li> | |||
| <li>The IAOC chair, ex officio</li> | ||||
| <t><list style="symbols"> | <li>The IAB chair, ex officio</li> | |||
| <t>The IETF chair, ex officio</t> | <li>One ISOC trustee, selected by the ISOC Board of Trustees</li> | |||
| <t>The IAOC chair, ex officio</t> | </ul> | |||
| <t>The IAB chair, ex officio</t> | </section> | |||
| <t>One ISOC trustee, selected by the ISOC Board of Trustees</t> | <section anchor="board-positions" numbered="true" toc="default"> | |||
| </list></t> | <name>Board Positions</name> | |||
| <t>Following the formation of the first permanent Board, and annually th | ||||
| </section> | ereafter, the Directors shall | |||
| <section anchor="board-positions" title="Board Positions"> | elect a Director to serve as Board Chair by majority vote. The IETF, IAB, and IR | |||
| TF chairs, and the | ||||
| <t>Following the formation of the first permanent Board, and annually thereafter | chair of ISOC's Board, will be ineligible for this Board Chair role. The Board m | |||
| , the Directors shall | ay also form committees | |||
| elect a Director to serve as Board Chair by majority vote. The IETF, IAB and IRT | ||||
| F chairs, and the | ||||
| chair of ISOC’s Board, will be ineligible for this Board Chair role. The Board m | ||||
| ay also form committees | ||||
| of the Board and/or define other roles for Board Directors as necessary.</t> | of the Board and/or define other roles for Board Directors as necessary.</t> | |||
| </section> | ||||
| </section> | </section> | |||
| </section> | <section anchor="ietf-llc-funding" numbered="true" toc="default"> | |||
| <section anchor="ietf-llc-funding" title="IETF LLC Funding"> | <name>IETF LLC Funding</name> | |||
| <t>The IETF LLC must function within a budget of costs balanced against li | ||||
| <t>The IETF LLC must function within a budget of costs balanced against limited | mited revenues. The IETF community expects | |||
| revenues. The IETF community expects | ||||
| the IETF LLC to work to attain that goal, in order to maintain a viable support function that provides the | the IETF LLC to work to attain that goal, in order to maintain a viable support function that provides the | |||
| environment within which the work of the IETF, IAB, IRTF, and RFC Editor can rem ain vibrant and productive.</t> | environment within which the work of the IETF, IAB, IRTF, and RFC Editor can rem ain vibrant and productive.</t> | |||
| <t>The IETF LLC was generating income from a few key sources at the time t | ||||
| <t>The IETF LLC was generating income from a few key sources at the time that th | hat this document was written, as enumerated below. Additional sources of income | |||
| is document was written, as enumerated below. Additional sources of income may b | may be developed in the future, within the general bounds noted in <xref target | |||
| e developed in the future, within the general bounds noted in <xref target="fund | ="fundraising-practices" format="default"/>, and some of these may decline in re | |||
| raising-practices"/>, and some of these may decline in relevance or go away. As | levance or go away. As a result, this list is subject to change over time and is | |||
| a result this list is subject to change over time and is merely an example of th | merely an example of the primary sources of income for the IETF LLC at the time | |||
| e primary sources of income for the IETF LLC at the time of this writing:</t> | of this writing:</t> | |||
| <ol spacing="normal" type="1"> | ||||
| <t><list style="numbers"> | <li>ISOC support</li> | |||
| <t>ISOC support</t> | <li>IETF meeting revenues</li> | |||
| <t>IETF meeting revenues</t> | <li>Sponsorships (monetary and/or in-kind)</li> | |||
| <t>Sponsorships (monetary and/or in-kind)</t> | <li>Donations (monetary and/or in-kind)</li> | |||
| <t>Donations (monetary and/or in-kind)</t> | </ol> | |||
| </list></t> | <section anchor="financial-statements" numbered="true" toc="default"> | |||
| <name>Financial Statements</name> | ||||
| <section anchor="financial-statements" title="Financial Statements"> | <t>As noted in <xref target="board-responsibilities" format="default"/>, | |||
| the IETF LLC must comply with relevant tax laws, such as filing an annual | ||||
| <t>As noted in <xref target="board-responsibilities"/>, the IETF LLC must comply | ||||
| with relevant tax laws, such as filing an annual | ||||
| IRS Form 990. Other official financial statements may also be required.</t> | IRS Form 990. Other official financial statements may also be required.</t> | |||
| <t>In addition to these official financial statements and forms, the IET | ||||
| <t>In addition to these official financial statements and forms, the IETF LLC is | F LLC is also expected to report on a regular basis | |||
| also expected to report on a regular basis | ||||
| to the IETF community on the current and future annual budget, budget forecasts vs. actuals over the course of a fiscal | to the IETF community on the current and future annual budget, budget forecasts vs. actuals over the course of a fiscal | |||
| year, and on other significant projects as needed. This regular reporting to the IETF community is expected to be | year, and on other significant projects as needed. This regular reporting to the IETF community is expected to be | |||
| reported in the form of standard financial statements that reflect the income, e xpenses, assets, and liabilities of the | reported in the form of standard financial statements that reflect the income, e xpenses, assets, and liabilities of the | |||
| IETF LLC.</t> | IETF LLC.</t> | |||
| </section> | ||||
| </section> | <section anchor="bank-and-investment-accounts" numbered="true" toc="defaul | |||
| <section anchor="bank-and-investment-accounts" title="Bank and Investment Accoun | t"> | |||
| ts"> | <name>Bank and Investment Accounts</name> | |||
| <t>The IETF LLC maintains its own bank account, separate and distinct fr | ||||
| <t>The IETF LLC maintains its own bank account, separate and distinct from ISOC. | om ISOC. The IETF LLC | |||
| The IETF LLC | ||||
| may at its discretion create additional accounts as needed. Similarly, the IETF LLC may as needed create investment | may at its discretion create additional accounts as needed. Similarly, the IETF LLC may as needed create investment | |||
| accounts in support of its financial goals and objectives.</t> | accounts in support of its financial goals and objectives.</t> | |||
| </section> | ||||
| </section> | <section anchor="financial-audits" numbered="true" toc="default"> | |||
| <section anchor="financial-audits" title="Financial Audits"> | <name>Financial Audits</name> | |||
| <t>The IETF LLC is expected to retain and work with an independent audit | ||||
| <t>The IETF LLC is expected to retain and work with an independent auditor. Repo | or. Reports from the auditor are expected to be shared with the IETF community a | |||
| rts from the auditor are expected to be shared with the IETF community and other | nd other groups and organizations as needed or as required by law.</t> | |||
| groups and organizations as needed or as required by law.</t> | </section> | |||
| <section anchor="isoc-financial-support" numbered="true" toc="default"> | ||||
| </section> | <name>ISOC Financial Support</name> | |||
| <section anchor="isoc-financial-support" title="ISOC Financial Support"> | <t>ISOC currently provides significant financial support to the IETF LLC | |||
| . Exhibit B of the <xref target="IETF-LLC-A" format="default"/> | ||||
| <t>ISOC currently provides significant financial support to the IETF LLC. Exhibi | ||||
| t B of the <xref target="IETF-LLC-A"/> | ||||
| summarizes the financial support from ISOC for the foreseeable future. It is exp ected that this support | summarizes the financial support from ISOC for the foreseeable future. It is exp ected that this support | |||
| will be periodically reviewed and revised, via a cooperative assessment process between ISOC and | will be periodically reviewed and revised, via a cooperative assessment process between ISOC and | |||
| the IETF LLC.</t> | the IETF LLC.</t> | |||
| </section> | ||||
| </section> | <section anchor="ietf-meeting-revenues" numbered="true" toc="default"> | |||
| <section anchor="ietf-meeting-revenues" title="IETF Meeting Revenues"> | <name>IETF Meeting Revenues</name> | |||
| <t>Meeting revenues are another important source of funding that support | ||||
| <t>Meeting revenues are another important source of funding that supports the IE | s the IETF, coming mainly from the fees paid | |||
| TF, coming mainly from the fees paid | ||||
| by IETF meeting participants. The IETF Executive Director sets those meeting fee s, in consultation with other IETF | by IETF meeting participants. The IETF Executive Director sets those meeting fee s, in consultation with other IETF | |||
| LLC staff and the IETF community, with approval by the IETF LLC Board. Setting t hese fees and projecting the number | LLC staff and the IETF community, with approval by the IETF LLC Board. Setting t hese fees and projecting the number | |||
| of participants at future meetings is a key part of the annual budget process.</ t> | of participants at future meetings is a key part of the annual budget process.</ t> | |||
| </section> | ||||
| </section> | <section anchor="sponsorships-and-donations-to-the-ietf-llc" numbered="tru | |||
| <section anchor="sponsorships-and-donations-to-the-ietf-llc" title="Sponsorships | e" toc="default"> | |||
| and Donations to the IETF LLC"> | <name>Sponsorships and Donations to the IETF LLC</name> | |||
| <t>Sponsorships and donations are an essential component of the financia | ||||
| <t>Sponsorships and donations are an essential component of the financial suppor | l support for the IETF. Within the general | |||
| t for the IETF. Within the general | bounds noted in <xref target="fundraising-practices" format="default"/>, the IET | |||
| bounds noted in <xref target="fundraising-practices"/>, the IETF LLC is responsi | F LLC is responsible for fundraising activities in order | |||
| ble for fundraising activities in order | ||||
| to establish, maintain, and grow a strong foundation of donation revenues. This can and does include both | to establish, maintain, and grow a strong foundation of donation revenues. This can and does include both | |||
| direct financial contributions as well as in-kind contributions, such as equipme nt, software licenses, and services.</t> | direct financial contributions as well as in-kind contributions, such as equipme nt, software licenses, and services.</t> | |||
| <t>Sponsorships and donations to the IETF LLC do not (and must not) conv | ||||
| <t>Sponsorships and donations to the IETF LLC do not (and must not) convey to sp | ey to sponsors and donors any special oversight | |||
| onsors and donors any special oversight | or direct influence over the IETF's technical work or other activities of the IE | |||
| or direct influence over the IETF’s technical work or other activities of the IE | TF or IETF LLC. This helps | |||
| TF or IETF LLC. This helps | ||||
| ensure that no undue influence may be ascribed to those from whom funds are rais ed, and so helps to maintain | ensure that no undue influence may be ascribed to those from whom funds are rais ed, and so helps to maintain | |||
| an open and consensus-based IETF standards process.</t> | an open and consensus-based IETF standards process.</t> | |||
| <t>To the extent that the IETF LLC needs to undertake any significant sp | ||||
| <t>To the extent that the IETF LLC needs to undertake any significant special pr | ecial projects for the IETF, the IETF LLC | |||
| ojects for the IETF, the IETF LLC | ||||
| may need to fundraise distinctly for those special projects. As a result, the IE TF LLC may conduct fundraising to support | may need to fundraise distinctly for those special projects. As a result, the IE TF LLC may conduct fundraising to support | |||
| the IETF in general as well as one or more special fundraising efforts (which ma y also be accounted for distinctly and be held in a separate bank account or inv estment, as needed).</t> | the IETF in general as well as one or more special fundraising efforts (which ma y also be accounted for distinctly and be held in a separate bank account or inv estment, as needed).</t> | |||
| </section> | ||||
| </section> | <section anchor="focus-of-funding-support" numbered="true" toc="default"> | |||
| <section anchor="focus-of-funding-support" title="Focus of Funding Support"> | <name>Focus of Funding Support</name> | |||
| <t>The IETF LLC exists to support the IETF, IAB, and IRTF. Therefore, t | ||||
| <t>The IETF LLC exists to support the IETF, IAB, and IRTF. Therefore, the IETF | he IETF LLC's funding and all revenues, | |||
| LLC’s funding and all revenues, | ||||
| in-kind contributions, and other income that comprise that funding shall be used solely to support activities | in-kind contributions, and other income that comprise that funding shall be used solely to support activities | |||
| related to the IETF, IAB, IRTF, and RFC Editor, and for no other purposes.</t> | related to the IETF, IAB, IRTF, and RFC Editor, and for no other purposes.</t> | |||
| </section> | ||||
| </section> | <section anchor="fundraising-practices" numbered="true" toc="default"> | |||
| <section anchor="fundraising-practices" title="Charitable Fundraising Practices" | <name>Charitable Fundraising Practices</name> | |||
| > | <t>When the IETF LLC conducts fundraising, it substantiates charitable | |||
| contributions on behalf of ISOC -- meaning that according to United States tax | ||||
| <t>When the IETF LLC conducts fundraising, it substantiates charitable | ||||
| contributions on behalf of ISOC – meaning that according to US tax | ||||
| law, the IETF LLC must send a written acknowledgment of contributions | law, the IETF LLC must send a written acknowledgment of contributions | |||
| to donors. The IETF LLC evaluates and facilitates state, federal, and | to donors. The IETF LLC evaluates and facilitates state, federal, and | |||
| other applicable law and regulatory compliance for ISOC and/or the LLC | other applicable law and regulatory compliance for ISOC and/or the LLC | |||
| with respect to such fundraising activities. In addition, the IETF LLC | with respect to such fundraising activities. In addition, the IETF LLC | |||
| ensures that all fundraising activities are conducted in compliance | ensures that all fundraising activities are conducted in compliance | |||
| with any policies developed by the IETF LLC, including but not limited | with any policies developed by the IETF LLC, including but not limited | |||
| to those noted in <xref target="llc-policies"/>.</t> | to those noted in <xref target="llc-policies" format="default"/>.</t> | |||
| </section> | ||||
| </section> | <section anchor="operating-reserve" numbered="true" toc="default"> | |||
| <section anchor="operating-reserve" title="Operating Reserve"> | <name>Operating Reserve</name> | |||
| <t>An initial target operating reserve has been specified in Exhibit B o | ||||
| <t>An initial target operating reserve has been specified in Exhibit B of the <x | f the <xref target="IETF-LLC-A" format="default"/>. It says that the IETF LLC | |||
| ref target="IETF-LLC-A"/>. That says that the IETF LLC | should maintain an operating reserve equal to the IETF LLC's budgeted Net Loss f | |||
| should maintain an operating reserve equal to the IETF LLC’s budgeted Net Loss f | or 2019 multiplied times three. The IETF | |||
| or 2019 multiplied times three. The IETF | LLC, in cooperation with ISOC, may regularly review the financial target for thi | |||
| LLC, in cooperation with ISOC, may regularly review the financial target for thi | s reserve fund, as noted in the <xref target="IETF-LLC-A" format="default"/> or | |||
| s reserve fund, as noted in the <xref target="IETF-LLC-A"/> or as otherwise nece | as otherwise necessary.</t> | |||
| ssary.</t> | <t>Should the IETF LLC generate an annual budget surplus, it may choose | |||
| to direct all or part of the surplus towards | ||||
| <t>Should the IETF LLC generate an annual budget surplus, it may choose to direc | ||||
| t all or part of the surplus towards | ||||
| the growth of the operating reserve.</t> | the growth of the operating reserve.</t> | |||
| </section> | ||||
| </section> | <section anchor="annual-budget-process" numbered="true" toc="default"> | |||
| <section anchor="annual-budget-process" title="Annual Budget Process"> | <name>Annual Budget Process</name> | |||
| <t>As noted in <xref target="llc-responsibilities" format="default"/>, t | ||||
| <t>As noted in <xref target="llc-responsibilities"/>, the IETF LLC is responsibl | he IETF LLC is responsible for managing the IETF's finances and budget. | |||
| e for managing the IETF’s finances and budget. | ||||
| A key part of this responsibility is establishing, maintaining, and successfully meeting an annual budget. This | A key part of this responsibility is establishing, maintaining, and successfully meeting an annual budget. This | |||
| is essential to the continued operation and vibrancy of the IETF’s technical act ivities and establishes trust | is essential to the continued operation and vibrancy of the IETF's technical act ivities and establishes trust | |||
| with ISOC, sponsors, and donors that funds are being appropriately spent, and th at financial oversight is being conducted | with ISOC, sponsors, and donors that funds are being appropriately spent, and th at financial oversight is being conducted | |||
| properly. This is also essential to the IETF LLC meeting applicable legal and ta x requirements and is a core part of | properly. This is also essential to the IETF LLC meeting applicable legal and ta x requirements and is a core part of | |||
| the Board’s fiduciary responsibilities.</t> | the Board's fiduciary responsibilities.</t> | |||
| <t>As explained in <xref target="staff-responsibilities" format="default | ||||
| <t>As explained in <xref target="staff-responsibilities"/>, the IETF Executive D | "/>, the IETF Executive Director is expected to develop, execute, and report on | |||
| irector is expected to develop, execute, and report on the | the | |||
| annual budget. Regular reporting is expected to include forecast vs. budget stat ements, including updated projections of income and expenses for the full fiscal year.</t> | annual budget. Regular reporting is expected to include forecast vs. budget stat ements, including updated projections of income and expenses for the full fiscal year.</t> | |||
| <t>The Board, as explained in <xref target="board-responsibilities" form | ||||
| <t>The Board, as explained in <xref target="board-responsibilities"/>, is expect | at="default"/>, is expected to review and approve the | |||
| ed to review and approve the | ||||
| budget, as well as to provide ongoing oversight of the budget and of any other s ignificant financial matters.</t> | budget, as well as to provide ongoing oversight of the budget and of any other s ignificant financial matters.</t> | |||
| <t>The annual budget is expected to be developed in an open, transparent | ||||
| <t>The annual budget is expected to be developed in an open, transparent, and co | , and collaborative manner, in accordance with | |||
| llaborative manner, in accordance with | <xref target="principles" format="default"/>. The specific timeline for the deve | |||
| <xref target="principles"/>. The specific timeline for the development, review, | lopment, review, and approval of the IETF LLC annual budget is established by th | |||
| and approval of the IETF LLC annual budget is established by the Board and may b | e Board and may be revised as needed.</t> | |||
| e revised as needed.</t> | </section> | |||
| </section> | ||||
| </section> | <section anchor="llc-policies" numbered="true" toc="default"> | |||
| </section> | <name>IETF LLC Policies</name> | |||
| <section anchor="llc-policies" title="IETF LLC Policies"> | <t>The Board is expected to maintain policies as necessary to achieve the | |||
| <t>The Board is expected to maintain policies as necessary to achieve the | ||||
| goals of the IETF LLC, meet transparency expectations of the | goals of the IETF LLC, meet transparency expectations of the | |||
| community, comply with applicable laws or regulations, or for other | community, comply with applicable laws or regulations, or for other | |||
| reasons as appropriate. All policies are expected to be developed with | reasons as appropriate. All policies are expected to be developed with | |||
| input from the IETF community. Some policies provided by ISOC and | input from the IETF community. Some policies provided by ISOC and | |||
| past policies developed by the previous IAOC may | past policies developed by the previous IAOC may | |||
| provide a useful starting point for the Board to consider.</t> | provide a useful starting point for the Board to consider.</t> | |||
| <section anchor="conflict-of-interest" numbered="true" toc="default"> | ||||
| <section anchor="conflict-of-interest" title="Conflict of Interest Policy"> | <name>Conflict of Interest Policy</name> | |||
| <t>The Board is expected to maintain a Conflict of Interest policy for t | ||||
| <t>The Board is expected to maintain a Conflict of Interest policy for the IETF | he IETF LLC. While the details are determined by the Board, at a minimum such po | |||
| LLC. While the details are determined by the Board, at a minimum such policy is | licy is expected to include the following:</t> | |||
| expected to include the following:</t> | <ul spacing="normal"> | |||
| <li>The IETF, ISOC Board, IAB, or IRTF chair cannot be chair of the IE | ||||
| <t><list style="symbols"> | TF LLC Board, though they may serve as a Director.</li> | |||
| <t>The IETF, ISOC Board, IAB, or IRTF chair cannot be chair of the IETF LLC Bo | <li>A Director cannot be a paid consultant or employee of the IETF Exe | |||
| ard, though they may serve as a Director.</t> | cutive Director or their sub-contractors, nor a paid consultant or employee of I | |||
| <t>A Director cannot be a paid consultant or employee of the IETF Executive Di | SOC.</li> | |||
| rector or their sub-contractors, nor a paid consultant or employee of ISOC.</t> | </ul> | |||
| </list></t> | </section> | |||
| <section anchor="other-policies" numbered="true" toc="default"> | ||||
| </section> | <name>Other Policies</name> | |||
| <section anchor="other-policies" title="Other Policies"> | <t>The Board is expected to maintain additional policies for the IETF LL | |||
| C as necessary, covering Directors, employees, and contractors, concerning issue | ||||
| <t>The Board is expected to maintain additional policies for the IETF LLC as nec | s such as:</t> | |||
| essary, covering Directors, employees, and contractors, concerning issues such a | <ul spacing="normal"> | |||
| s:</t> | <li>Acceptance of gifts and other non-cash compensation</li> | |||
| <li>Travel and expense reimbursement</li> | ||||
| <t><list style="symbols"> | <li>Anti-bribery</li> | |||
| <t>Acceptance of gifts and other non-cash compensation;</t> | <li>Code of conduct</li> | |||
| <t>Travel and expense reimbursement;</t> | <li>Anti-harassment</li> | |||
| <t>Anti-bribery;</t> | <li>Non-discrimination</li> | |||
| <t>Code of conduct;</t> | <li>Whistleblower</li> | |||
| <t>Anti-harassment;</t> | <li>Document retention</li> | |||
| <t>Non-discrimination;</t> | <li>Export controls</li> | |||
| <t>Whistleblower;</t> | <li>Anti-terrorism sanctions</li> | |||
| <t>Document retention;</t> | <li>Data protection and privacy</li> | |||
| <t>Export controls;</t> | <li>Social media</li> | |||
| <t>Anti-terrorism sanctions;</t> | </ul> | |||
| <t>Data protection and privacy;</t> | </section> | |||
| <t>Social media</t> | <section anchor="compliance" numbered="true" toc="default"> | |||
| </list></t> | <name>Compliance</name> | |||
| <t>The IETF LLC is expected to implement a compliance program to ensure | ||||
| </section> | its compliance with all applicable laws, rules, and regulations, including witho | |||
| <section anchor="compliance" title="Compliance"> | ut limitation laws governing bribery, anti-terrorism sanctions, export controls, | |||
| data protection/privacy, as well as other applicable policies noted in <xref ta | ||||
| <t>The IETF LLC is expected to implement a compliance program to ensure its comp | rget="llc-policies" format="default"/>. In addition, actions and activities of t | |||
| liance with all applicable laws, rules and regulations, including without limita | he IETF LLC must be consistent with 501(c)(3) purposes.</t> | |||
| tion laws governing bribery, anti-terrorism sanctions, export controls, data pro | <t>The IETF LLC is expected to report to ISOC and the IETF community on | |||
| tection/privacy, as well as other applicable policies noted in <xref target="llc | the implementation of its compliance plan on an annual basis.</t> | |||
| -policies"/>. In addition, actions and activities of the IETF LLC must be consis | </section> | |||
| tent with 501(c)(3) purposes.</t> | </section> | |||
| <section anchor="three-year-assessment" numbered="true" toc="default"> | ||||
| <t>The IETF LLC is expected report to ISOC and the IETF community on the impleme | <name>Three-Year Assessment</name> | |||
| ntation of its compliance plan on an annual basis.</t> | <t>The IETF LLC, with the involvement of the community, shall conduct | |||
| and complete an assessment of the structure, processes, and operation of | ||||
| </section> | IASA 2.0 and the IETF LLC. This should be presented to the community | |||
| </section> | after a period of roughly three years of operation. The assessment may | |||
| <section anchor="three-year-assessment" title="Three-Year Assessment"> | potentially include recommendations for improvements or changes to the | |||
| IASA 2.0 and/or IETF LLC.</t> | ||||
| <t>The IETF LLC, with the involvement of the community, shall conduct and comple | </section> | |||
| te an assessment of the structure, processes, and operation of IASA 2.0 and the | <section anchor="security-considerations" numbered="true" toc="default"> | |||
| IETF LLC. This should be presented to the community after a period of roughly th | <name>Security Considerations</name> | |||
| ree years of operation. The assessment may potentially include recommendations f | <t>This document describes the structure of IASA 2.0. It introduces no se | |||
| or improvements or changes to the IASA2 and/or IETF LLC.</t> | curity considerations | |||
| </section> | ||||
| <section anchor="security-considerations" title="Security Considerations"> | ||||
| <t>This document describes the structure of the IETF’s Administrative | ||||
| Support Activity (IASA), version 2 (IASA2). It introduces no security considera | ||||
| tions | ||||
| for the Internet.</t> | for the Internet.</t> | |||
| </section> | ||||
| </section> | <section anchor="iana-considerations" numbered="true" toc="default"> | |||
| <section anchor="iana-considerations" title="IANA Considerations"> | <name>IANA Considerations</name> | |||
| <t>This document has no IANA considerations in the traditional sense. | ||||
| <t>This document has no IANA considerations in the traditional sense. | ||||
| However, some of the information in this document may affect how the | However, some of the information in this document may affect how the | |||
| IETF standards process interfaces with the IANA, so the IANA may be | IETF standards process interfaces with the IANA, so the IANA may be | |||
| interested in the contents.</t> | interested in the contents.</t> | |||
| </section> | ||||
| </section> | ||||
| <section anchor="pronouns" title="Pronouns"> | ||||
| <t>This document has used “they” and “their” as a non-gender-specific pronoun to | ||||
| refer to a single individual.</t> | ||||
| </section> | ||||
| <section anchor="acknowledgments" title="Acknowledgments"> | ||||
| <t>Thanks to Jari Arkko, Richard Barnes, Brian E Carpenter, Alissa | ||||
| Cooper, John C Klensin, Bob Hinden, Jon Peterson, Sean Turner and the | ||||
| IASA2 Working Group for discussions of possible structures, and to the | ||||
| attorneys of Morgan Lewis and Brad Biddle for legal advice.</t> | ||||
| </section> | ||||
| </middle> | </middle> | |||
| <back> | <back> | |||
| <displayreference target="I-D.haberman-iasa20dt-recs" to="IASA2RECS"/> | ||||
| <references> | ||||
| <name>References</name> | ||||
| <references> | ||||
| <name>Normative References</name> | ||||
| <!-- draft-ietf-iasa2-rfc2031bis [RFC8712] --> | ||||
| <reference anchor="RFC8712" target="https://www.rfc-editor.org/info/rfc8 | ||||
| 712"> | ||||
| <front> | ||||
| <title>The IETF-ISOC Relationship</title> | ||||
| <author initials="G" surname="Camarillo" fullname="Gonzalo Camarillo | ||||
| "> | ||||
| <organization/> | ||||
| </author> | ||||
| <author initials="J" surname="Livingood" fullname="Jason Livingood"> | ||||
| <organization/> | ||||
| </author> | ||||
| <date month="January" year="2020"/> | ||||
| </front> | ||||
| <seriesInfo name="RFC" value="8712"/> | ||||
| <seriesInfo name="DOI" value="10.17487/RFC8712"/> | ||||
| </reference> | ||||
| <!-- draft-ietf-iasa2-rfc7437bis [RFC8713] --> | ||||
| <reference anchor="RFC8713" target="https://rfc-editor.org/info/rfc8713" | ||||
| > | ||||
| <front> | ||||
| <title>IAB, IESG, and IETF LLC Selection, Confirmation, and | ||||
| Recall Process: Operation of the IETF Nominating and | ||||
| Recall Committees</title> | ||||
| <author initials="M." surname="Kucherawy" role="editor"> | ||||
| <organization/> | ||||
| </author> | ||||
| <author initials="R." surname="Hinden" role="editor"> | ||||
| <organization/> | ||||
| </author> | ||||
| <author initials="J." surname="Livingood" role="editor"> | ||||
| <organization/> | ||||
| </author> | ||||
| <date month="January" year="2020"/> | ||||
| </front> | ||||
| <seriesInfo name="BCP" value="10"/> | ||||
| <seriesInfo name="RFC" value="8713"/> | ||||
| <seriesInfo name="DOI" value="10.17487/RFC8713"/> | ||||
| </reference> | ||||
| <reference anchor="IETF-LLC-A" target="https://www.ietf.org/documents/18 | ||||
| 0/IETF-LLC-Agreement.pdf"> | ||||
| <front> | ||||
| <title>Limited Liability Company Agreement of IETF Administration LL | ||||
| C</title> | ||||
| <author> | ||||
| </author> | ||||
| <date year="2018" month="August"/> | ||||
| </front> | ||||
| </reference> | ||||
| </references> | ||||
| <references> | ||||
| <name>Informative References</name> | ||||
| <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer | ||||
| ence.RFC.7691.xml"/> | ||||
| <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer | ||||
| ence.RFC.2026.xml"/> | ||||
| <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer | ||||
| ence.RFC.2014.xml"/> | ||||
| <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer | ||||
| ence.RFC.2850.xml"/> | ||||
| <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer | ||||
| ence.RFC.4071.xml"/> | ||||
| <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer | ||||
| ence.RFC.3710.xml"/> | ||||
| <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer | ||||
| ence.RFC.3233.xml"/> | ||||
| <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer | ||||
| ence.RFC.4333.xml"/> | ||||
| <references title='Normative References'> | <!-- draft-ietf-mtgvenue-iaoc-venue-selection-process-16 RFC 8718 --> | |||
| <reference anchor="RFC8718" target="https://rfc-editor.org/info/rfc8718" | ||||
| <reference anchor="I-D.ietf-iasa2-rfc2031bis"> | > | |||
| <front> | <front> | |||
| <title>The IETF-ISOC Relationship</title> | <title>IETF Plenary Meeting Venue Selection Process</title> | |||
| <author initials="E." surname="Lear" role="editor"> | ||||
| <author initials='G' surname='Camarillo' fullname='Gonzalo Camarillo'> | <organization/> | |||
| <organization /> | </author> | |||
| </author> | <date month="January" year="2020"/> | |||
| </front> | ||||
| <author initials='J' surname='Livingood' fullname='Jason Livingood'> | <seriesInfo name="BCP" value="226"/> | |||
| <organization /> | <seriesInfo name="RFC" value="8718"/> | |||
| </author> | <seriesInfo name="DOI" value="10.17487/RFC8718"/> | |||
| </reference> | ||||
| <date month='February' day='14' year='2019' /> | ||||
| <abstract><t>This document summarises the Internet Engineering Task Force (IETF) | ||||
| - Internet Society (ISOC) relationship, following a major revision to the struc | ||||
| ture of the IETF Administrative Support Activity (IASA) in 2018. The IASA was r | ||||
| evised under a new "IASA 2.0" structure by the IASA2 Working Group, which change | ||||
| d the IETF's administrative, legal, and financial structure. As a result, it al | ||||
| so changed the relationship between the IETF and ISOC, which made it necessary t | ||||
| o revise RFC 2031.</t></abstract> | ||||
| </front> | ||||
| <seriesInfo name='Internet-Draft' value='draft-ietf-iasa2-rfc2031bis-04' /> | ||||
| <format type='TXT' | ||||
| target='http://www.ietf.org/internet-drafts/draft-ietf-iasa2-rfc2031bis- | ||||
| 04.txt' /> | ||||
| </reference> | ||||
| <reference anchor="I-D.ietf-iasa2-rfc7437bis"> | ||||
| <front> | ||||
| <title>IAB, IESG, IETF Trust and IETF LLC Selection, Confirmation, and Recall Pr | ||||
| ocess: Operation of the IETF Nominating and Recall Committees</title> | ||||
| <author initials='M' surname='Kucherawy' fullname='Murray Kucherawy'> | ||||
| <organization /> | ||||
| </author> | ||||
| <author initials='R' surname='Hinden' fullname='Robert Hinden'> | ||||
| <organization /> | ||||
| </author> | ||||
| <author initials='J' surname='Livingood' fullname='Jason Livingood'> | ||||
| <organization /> | ||||
| </author> | ||||
| <date month='March' day='26' year='2019' /> | ||||
| <abstract><t>The process by which the members of the IAB and IESG, some Trustees | ||||
| of the IETF Trust, and some Directors of the IETF LLC are selected, confirmed, | ||||
| and recalled is specified in this document. This document based on RFC3777 and | ||||
| RFC7437 and has been updated to reflect the changes introduced by IASA 2.0. Thi | ||||
| s document obsoletes RFC7437 and RFC8318.</t></abstract> | ||||
| </front> | ||||
| <seriesInfo name='Internet-Draft' value='draft-ietf-iasa2-rfc7437bis-06' /> | ||||
| <format type='TXT' | ||||
| target='http://www.ietf.org/internet-drafts/draft-ietf-iasa2-rfc7437bis- | ||||
| 06.txt' /> | ||||
| </reference> | ||||
| <reference anchor="IETF-LLC-A" target="https://www.ietf.org/documents/180/IETF-L | ||||
| LC-Agreement.pdf"> | ||||
| <front> | ||||
| <title>Limited Liability Company Agreement of IETF Administration LLC</title | ||||
| > | ||||
| <author > | ||||
| <organization>The Internet Society</organization> | ||||
| </author> | ||||
| <date year="2018" month="August"/> | ||||
| </front> | ||||
| </reference> | ||||
| </references> | ||||
| <references title='Informative References'> | ||||
| <reference anchor="RFC7691" target='https://www.rfc-editor.org/info/rfc7691'> | ||||
| <front> | ||||
| <title>Updating the Term Dates of IETF Administrative Oversight Committee (IAOC) | ||||
| Members</title> | ||||
| <author initials='S.' surname='Bradner' fullname='S. Bradner' role='editor'><org | ||||
| anization /></author> | ||||
| <date year='2015' month='November' /> | ||||
| <abstract><t>BCP 101 defines the start and end dates for the terms of IETF Admin | ||||
| istrative Oversight Committee (IAOC) members; these terms have proven to be impr | ||||
| actical. This memo updates BCP 101 to direct the IAOC to establish more practic | ||||
| al start and end dates for terms of IAOC members.</t></abstract> | ||||
| </front> | ||||
| <seriesInfo name='BCP' value='101'/> | ||||
| <seriesInfo name='RFC' value='7691'/> | ||||
| <seriesInfo name='DOI' value='10.17487/RFC7691'/> | ||||
| </reference> | ||||
| <reference anchor="RFC2026" target='https://www.rfc-editor.org/info/rfc2026'> | ||||
| <front> | ||||
| <title>The Internet Standards Process -- Revision 3</title> | ||||
| <author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></ | ||||
| author> | ||||
| <date year='1996' month='October' /> | ||||
| <abstract><t>This memo documents the process used by the Internet community for | ||||
| the standardization of protocols and procedures. It defines the stages in the s | ||||
| tandardization process, the requirements for moving a document between stages an | ||||
| d the types of documents used during this process. This document specifies an In | ||||
| ternet Best Current Practices for the Internet Community, and requests discussio | ||||
| n and suggestions for improvements.</t></abstract> | ||||
| </front> | ||||
| <seriesInfo name='BCP' value='9'/> | ||||
| <seriesInfo name='RFC' value='2026'/> | ||||
| <seriesInfo name='DOI' value='10.17487/RFC2026'/> | ||||
| </reference> | ||||
| <reference anchor="RFC2014" target='https://www.rfc-editor.org/info/rfc2014'> | ||||
| <front> | ||||
| <title>IRTF Research Group Guidelines and Procedures</title> | ||||
| <author initials='A.' surname='Weinrib' fullname='A. Weinrib'><organization /></ | ||||
| author> | ||||
| <author initials='J.' surname='Postel' fullname='J. Postel'><organization /></au | ||||
| thor> | ||||
| <date year='1996' month='October' /> | ||||
| <abstract><t>This document describes the guidelines and procedures for formation | ||||
| and operation of IRTF Research Groups. It describes the relationship between I | ||||
| RTF participants, Research Groups, the Internet Research Steering Group (IRSG) a | ||||
| nd the Internet Architecture Board (IAB). This document specifies an Internet B | ||||
| est Current Practices for the Internet Community, and requests discussion and su | ||||
| ggestions for improvements.</t></abstract> | ||||
| </front> | ||||
| <seriesInfo name='BCP' value='8'/> | ||||
| <seriesInfo name='RFC' value='2014'/> | ||||
| <seriesInfo name='DOI' value='10.17487/RFC2014'/> | ||||
| </reference> | ||||
| <reference anchor="RFC2850" target='https://www.rfc-editor.org/info/rfc2850'> | ||||
| <front> | ||||
| <title>Charter of the Internet Architecture Board (IAB)</title> | ||||
| <author><organization>Internet Architecture Board</organization></author> | ||||
| <author initials='B.' surname='Carpenter' fullname='B. Carpenter' role='editor'> | ||||
| <organization /></author> | ||||
| <date year='2000' month='May' /> | ||||
| <abstract><t>This memo documents the composition, selection, roles, and organiza | ||||
| tion of the Internet Architecture Board. It replaces RFC 1601. This document s | ||||
| pecifies an Internet Best Current Practices for the Internet Community, and requ | ||||
| ests discussion and suggestions for improvements.</t></abstract> | ||||
| </front> | ||||
| <seriesInfo name='BCP' value='39'/> | ||||
| <seriesInfo name='RFC' value='2850'/> | ||||
| <seriesInfo name='DOI' value='10.17487/RFC2850'/> | ||||
| </reference> | ||||
| <reference anchor="RFC4071" target='https://www.rfc-editor.org/info/rfc4071'> | ||||
| <front> | ||||
| <title>Structure of the IETF Administrative Support Activity (IASA)</title> | ||||
| <author initials='R.' surname='Austein' fullname='R. Austein' role='editor'><org | ||||
| anization /></author> | ||||
| <author initials='B.' surname='Wijnen' fullname='B. Wijnen' role='editor'><organ | ||||
| ization /></author> | ||||
| <date year='2005' month='April' /> | ||||
| <abstract><t>This document describes the structure of the IETF Administrative Su | ||||
| pport Activity (IASA) as an activity housed within the Internet Society (ISOC). | ||||
| It defines the roles and responsibilities of the IETF Administrative Oversight | ||||
| Committee (IAOC), the IETF Administrative Director (IAD), and ISOC in the fiscal | ||||
| and administrative support of the IETF standards process. It also defines the | ||||
| membership and selection rules for the IAOC. This document specifies an Interne | ||||
| t Best Current Practices for the Internet Community, and requests discussion and | ||||
| suggestions for improvements.</t></abstract> | ||||
| </front> | ||||
| <seriesInfo name='BCP' value='101'/> | ||||
| <seriesInfo name='RFC' value='4071'/> | ||||
| <seriesInfo name='DOI' value='10.17487/RFC4071'/> | ||||
| </reference> | ||||
| <reference anchor="RFC3710" target='https://www.rfc-editor.org/info/rfc3710'> | ||||
| <front> | ||||
| <title>An IESG charter</title> | ||||
| <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'><organizatio | ||||
| n /></author> | ||||
| <date year='2004' month='February' /> | ||||
| <abstract><t>This memo provides a charter for the Internet Engineering Steering | ||||
| Group (IESG), a management function of the Internet Engineering Task Force (IETF | ||||
| ). It is meant to document the charter of the IESG as it is presently understoo | ||||
| d. This memo provides information for the Internet community.</t></abstract> | ||||
| </front> | ||||
| <seriesInfo name='RFC' value='3710'/> | ||||
| <seriesInfo name='DOI' value='10.17487/RFC3710'/> | ||||
| </reference> | ||||
| <reference anchor="RFC3233" target='https://www.rfc-editor.org/info/rfc3233'> | ||||
| <front> | ||||
| <title>Defining the IETF</title> | ||||
| <author initials='P.' surname='Hoffman' fullname='P. Hoffman'><organization /></ | ||||
| author> | ||||
| <author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></ | ||||
| author> | ||||
| <date year='2002' month='February' /> | ||||
| <abstract><t>This document gives a more concrete definition of "the IETF&qu | ||||
| ot; as it understood today. Many RFCs refer to "the IETF". Many impo | ||||
| rtant IETF documents speak of the IETF as if it were an already-defined entity. | ||||
| However, no IETF document correctly defines what the IETF is. This document spe | ||||
| cifies an Internet Best Current Practices for the Internet Community, and reques | ||||
| ts discussion and suggestions for improvements.</t></abstract> | ||||
| </front> | ||||
| <seriesInfo name='BCP' value='58'/> | ||||
| <seriesInfo name='RFC' value='3233'/> | ||||
| <seriesInfo name='DOI' value='10.17487/RFC3233'/> | ||||
| </reference> | ||||
| <reference anchor="RFC4333" target='https://www.rfc-editor.org/info/rfc4333'> | ||||
| <front> | ||||
| <title>The IETF Administrative Oversight Committee (IAOC) Member Selection Guide | ||||
| lines and Process</title> | ||||
| <author initials='G.' surname='Huston' fullname='G. Huston' role='editor'><organ | ||||
| ization /></author> | ||||
| <author initials='B.' surname='Wijnen' fullname='B. Wijnen' role='editor'><organ | ||||
| ization /></author> | ||||
| <date year='2005' month='December' /> | ||||
| <abstract><t>This memo outlines the guidelines for selection of members of the I | ||||
| ETF Administrative Oversight Committee, and describes the selection process used | ||||
| by the IAB and the IESG. This document specifies an Internet Best Current Prac | ||||
| tices for the Internet Community, and requests discussion and suggestions for im | ||||
| provements.</t></abstract> | ||||
| </front> | ||||
| <seriesInfo name='BCP' value='113'/> | ||||
| <seriesInfo name='RFC' value='4333'/> | ||||
| <seriesInfo name='DOI' value='10.17487/RFC4333'/> | ||||
| </reference> | ||||
| <reference anchor="I-D.ietf-mtgvenue-iaoc-venue-selection-process"> | ||||
| <front> | ||||
| <title>IETF Plenary Meeting Venue Selection Process</title> | ||||
| <author initials='E' surname='Lear' fullname='Eliot Lear'> | ||||
| <organization /> | ||||
| </author> | ||||
| <date month='June' day='14' year='2018' /> | ||||
| <abstract><t>The IASA has responsibility for arranging IETF plenary meeting Venu | ||||
| e selection and operation. This memo specifies IETF community requirements for | ||||
| meeting venues, including hotels and meeting room space. It directs the IASA to | ||||
| make available additional process documents that describe the current meeting s | ||||
| election process.</t></abstract> | ||||
| </front> | ||||
| <seriesInfo name='Internet-Draft' value='draft-ietf-mtgvenue-iaoc-venue-selectio | ||||
| n-process-16' /> | ||||
| <format type='TXT' | ||||
| target='http://www.ietf.org/internet-drafts/draft-ietf-mtgvenue-iaoc-ven | ||||
| ue-selection-process-16.txt' /> | ||||
| </reference> | ||||
| <reference anchor="I-D.haberman-iasa20dt-recs"> | ||||
| <front> | ||||
| <title>IASA 2.0 Design Team Recommendations</title> | ||||
| <author initials='B' surname='Haberman' fullname='Brian Haberman'> | ||||
| <organization /> | ||||
| </author> | ||||
| <author initials='J' surname='Arkko' fullname='Jari Arkko'> | ||||
| <organization /> | ||||
| </author> | ||||
| <author initials='L' surname='Daigle' fullname='Leslie Daigle'> | ||||
| <organization /> | ||||
| </author> | ||||
| <author initials='J' surname='Livingood' fullname='Jason Livingood'> | ||||
| <organization /> | ||||
| </author> | ||||
| <author initials='J' surname='Hall' fullname='Joseph Hall'> | ||||
| <organization /> | ||||
| </author> | ||||
| <author initials='E' surname='Rescorla' fullname='Eric Rescorla'> | ||||
| <organization /> | ||||
| </author> | ||||
| <date month='November' day='27' year='2018' /> | ||||
| <abstract><t>The arrangements relating to administrative support for the IETF we | ||||
| re created more than ten years ago. Since then, there has been considerable cha | ||||
| nge in the tasks and in our own expectations. The IETF community has discussed | ||||
| these changes and the problems they cause. The community has some sense of the | ||||
| properties they expect from future arrangements, including those related to stru | ||||
| cture, organization, personnel, and transparency. This document is a product of | ||||
| a design team, focused on providing additional information to the community abo | ||||
| ut solution options, as well as supporting analysis of the implications of those | ||||
| options. This document reflects the final snapshot of the design team discussio | ||||
| n and is published for historical posterity.</t></abstract> | ||||
| </front> | ||||
| <seriesInfo name='Internet-Draft' value='draft-haberman-iasa20dt-recs-03' /> | ||||
| <format type='TXT' | ||||
| target='http://www.ietf.org/internet-drafts/draft-haberman-iasa20dt-recs | ||||
| -03.txt' /> | ||||
| </reference> | ||||
| <reference anchor="I-D.ietf-iasa2-trust-update"> | ||||
| <front> | ||||
| <title>Update to the Process for Selection of Trustees for the IETF Trust</title | ||||
| > | ||||
| <author initials='J' surname='Arkko' fullname='Jari Arkko'> | ||||
| <organization /> | ||||
| </author> | ||||
| <author initials='T' surname='Hardie' fullname='Ted Hardie'> | ||||
| <organization /> | ||||
| </author> | ||||
| <date month='February' day='4' year='2019' /> | ||||
| <abstract><t>This memo updates the process for selection of trustees for the IET | ||||
| F Trust. Previously, the Internet Administrative Oversight Committee (IAOC) mem | ||||
| bers also acted as trustees, but the IAOC has been eliminated as part of an upda | ||||
| te of the structure of the Internet Administrative Support Activity (IASA). Thi | ||||
| s memo specifies that the trustees shall be selected separately. This memo obso | ||||
| letes RFC 4371. The changes relate only to the selection of trustees. All othe | ||||
| r aspects of the IETF Trust remain as they are today.</t></abstract> | ||||
| </front> | <!-- draft-haberman-iasa20dt-recs-03 expired 05/31/19 --> | |||
| <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/refe | ||||
| rence.I-D.draft-haberman-iasa20dt-recs-03.xml"/> | ||||
| <seriesInfo name='Internet-Draft' value='draft-ietf-iasa2-trust-update-03' /> | <!-- draft-ietf-iasa2-trust-update-03 RFC 8714 --> | |||
| <format type='TXT' | <reference anchor="RFC8714" target="https://rfc-editor.org/info/rfc8714" | |||
| target='http://www.ietf.org/internet-drafts/draft-ietf-iasa2-trust-updat | > | |||
| e-03.txt' /> | <front> | |||
| </reference> | <title>Update to the Process for Selection of Trustees for the | |||
| IETF Trust</title> | ||||
| <author initials="J." surname="Arkko"> | ||||
| <organization/> | ||||
| </author> | ||||
| <author initials="T." surname="Hardie"> | ||||
| <organization/> | ||||
| </author> | ||||
| <date month="January" year="2020"/> | ||||
| </front> | ||||
| <seriesInfo name="BCP" value="101"/> | ||||
| <seriesInfo name="RFC" value="8714"/> | ||||
| <seriesInfo name="DOI" value="10.17487/RFC8714"/> | ||||
| </reference> | ||||
| <reference anchor="ISOC" target="https://www.internetsociety.org/about-internet- | <!-- [rfced] https://www.internetsociety.org/about-internet-society/governance-p | |||
| society/governance-policies/by-laws/"> | olicies/by-laws/ | |||
| <front> | shows a date of October 2019. We have udpated the reference accordingly. | |||
| <title>Amended and restated By-Laws of the Internet Society</title> | Please let us know if this is incorrect. | |||
| <author > | ||||
| <organization>The Internet Society</organization> | ||||
| </author> | ||||
| <date year="2018" month="July"/> | ||||
| </front> | ||||
| </reference> | ||||
| Original: | ||||
| [ISOC] The Internet Society, "Amended and restated By-Laws of the | ||||
| Internet Society", July 2018, | ||||
| <https://www.internetsociety.org/about-internet-society/ | ||||
| governance-policies/by-laws/>. | ||||
| --> | ||||
| <reference anchor="ISOC" target="https://www.internetsociety.org/about-i | ||||
| nternet-society/governance-policies/by-laws/"> | ||||
| <front> | ||||
| <title>Amended and restated By-Laws of the Internet Society</title> | ||||
| <author> | ||||
| <organization>The Internet Society</organization> | ||||
| </author> | ||||
| <date year="2019" month="October"/> | ||||
| </front> | ||||
| </reference> | ||||
| </references> | ||||
| </references> | </references> | |||
| <section anchor="acknowledgments" numbered="false" toc="default"> | ||||
| <name>Acknowledgments</name> | ||||
| <t>Thanks to <contact fullname="Jari Arkko"/>, <contact | ||||
| fullname="Richard Barnes"/>, <contact fullname="Brian E. Carpenter"/>, <co | ||||
| ntact | ||||
| fullname="Alissa Cooper"/>, <contact fullname="John C. Klensin"/>, <contac | ||||
| t fullname="Bob Hinden"/>, | ||||
| <contact fullname="Jon Peterson"/>, <contact fullname="Sean Turner"/>, and the | ||||
| IASA2 Working Group for discussions of possible structures, and to the | ||||
| attorneys of <contact fullname="Morgan Lewis"/> and <contact fullname="Brad Bidd | ||||
| le"/> for legal advice.</t> | ||||
| <t>Coauthor Hall performed work on this document before employment at the | ||||
| Internet Society, and his affiliation listed in this document is for identificat | ||||
| ion purposes only.</t> | ||||
| </section> | ||||
| </back> | </back> | |||
| <!-- ##markdown-source: | ||||
| H4sIAPpysFwAA9V9WZPj1pXmO34FovSgKgeZtUmWlX7prEWy7JKlqSzZMdHR | ||||
| 0QGClyRUIEADYLJohSL6b8zfm18y5zvLXQAwqzSefphot4pJAnc99yzfWe5y | ||||
| ucyyoRpqd53fDt2xHI6dy9tNPuxc/t3rd9/kN+t91VT90BVDdefy2+Ph0HZD | ||||
| flPSn9VwXuR/c11ftU3+7OpJVqxWnbu7zr+7ub15lq3bsin21PK6KzbDsnLD | ||||
| ZlkVffFs2W3KL5589XRV9cunT7OyGNy27c7X+ao8ZO2qb2s3uP46xzOL/Ivn | ||||
| z58v8q9+//XTLKsO3XVO4+yHZ0+efP3kWVZ0rrjOv3WN64o6e+/Op7Zb0wCa | ||||
| wXWNG5av0HV22tqYsn4omvV/FnXb0MDOrs8O1XX+70NbLvKeJta5TU+fznt8 | ||||
| +I8sK47Dru2uszxf0v/nedXQuF5c5X8qVq7bFw1/KbN80VVFk/7Qdtuiqf5J | ||||
| S9c21/mf213T539qD++plfynhtaTlm4486NuX1Q1rQAa+beqado7fquvi9UV | ||||
| TSQdwJ8xgLqOOv9z27vDLn/Tdq75Zxt+TUfw8tW7uLOfW/dv5Xq4oocm7b+h | ||||
| 7W22bbuOOyl62uj0l1EH7b4s+iHpBC/9Z20v/Vspj1zRv1nWtLRWICys8HfL | ||||
| V1cpkTx78hxEMv/jV188/0p/xO9ErMs3b14ub665dyXqN9W+Gtya/i1WVU2L | ||||
| jSEeiuac32w75/auGUDuE1LHPN+85JYCCeh8r/N3OB1KYvltW9LAZBfXRMrX | ||||
| +bMnT/+wfPIHGUfRbd1wne+G4dBfP358Op14Hlj0x3RCjhhC//jpH548DlOw | ||||
| oV0d1hsi+mYTL9Pbb17iMOjHZ0+e/d5/fPqFffzDl0/0Iw6Rfnz+1VP79vmz | ||||
| 58/tgefy0a/wftjeueboaKnbcikfe1e7EsuyPHRt6Xq/Jzuld9mXJ+th2bly | ||||
| bsf41C6PB16iDL/f/vAy2asbmvKa9ooOaN45OqjYuBfn5Zvi1HueNLfq/7c7 | ||||
| 9NXlHdJXe3mTN6tYtUfiYsZZ9KfH25aOcVM0pVse2rqiL/vHq/OypkE/zrLl | ||||
| cpkXK9BUOWTZu0/kqvlDcKtH+amgiXfVtmroPJ8zrMmqrvodrUtFHPfJky+v | ||||
| aJa8MGdXdH3eVzQO/N0s+NvGuXUf8/PM3bX1nbx/Ks49/VAMtNr/OFYdfVvu | ||||
| imbr6Ns2r4Y+L5JhEu9UCXHF63s4dgdiO9J81edGzXnFDfg/sZ9r15ddtXLZ | ||||
| pwuWOxMsshoQMI9oukO2dpuqwSCpqY5kRW8UcyB+WfExp024KMX0aL9oi269 | ||||
| CI+8/uDKIw/lFS1FObTdgtudozqsHn2fbaq+LGp+LF2qvNfpxINg0UOd9rme | ||||
| oasc0ynqnhYrmtPe7elM9bvqwC37o5d3R0yWmEHYzunEcp7YFYgt3hMvVnHk | ||||
| VbLyJ5au6Ad/gbFcCdXuq/W6dln2GWbftesjj+G/h4Z/AxFn3Pe/QMV5TMb/ | ||||
| Ih0rWeZRi1n2EzGxzv8mUyCt5H1MC59PRoXGN8eGVKWK5r/Ns6Ho3/cYQtk2 | ||||
| WHya1+pMj41fjAXw4iLFZ5cF4cMH/AKRzgM6XzJ6Xgc/q6jZbLTrP/Ap3e4G | ||||
| NEc9DM5h4394+QhDdzX12oCPC4lhN1r/Ribn5k4mTJNnCqM174qm37gOW0nr | ||||
| 7/sOxJ1HZIhv6TzdVWs9PmVL20nDc3nttnQ6d+3eJYdmkZ7p7KYrd7Q2ovty | ||||
| B5jCi0cz5/+t64lEy13+jnYn/6btSkz37btv9GHiCBAFFXVrHMB6bg9O90Lp | ||||
| AOft9boiRkMn7pdfLgvTX3/N18Rojn1vM9zRUXJM4puixOKBGdkhE9Lzm5fT | ||||
| +Tu5usa/vbuDnkxjkZXG2DqnFGTtzNAnDfrIdLGuNrQxOAyytr6XHiIhOjsZ | ||||
| ycqaOdquPemg6Yw12nUek9c6OVn8Bh+vmLLzDWhnaElS72gcp2rY5e4DDQ+j | ||||
| xuuNOwlHJL1yf2xA4NHgpqdy3/aeO09EB7OTX35R7YnWv+iJZBuhx4sizOQG | ||||
| qOfVo8vC4yE0H2KMtJDU2D3EjhYuiK8ZcZVnDy8IMhabzM2o9Z/bVSKV0Bh1 | ||||
| vHc0QmawI/4yUSFkYm3umh7kxWuVtIampK9s+rLfHtqT18oelPJy8A16u2gG | ||||
| adX4OK+U5+7E85lCoE86B/54rIk3EqHTgYN6li7kOzwnCsvaDWSS8HiEKqs+ | ||||
| Y5pt6GXYvcehJzbC7/YlHdipSFgdB360BBvjwejRvaDp/vrrPZI4orBFftpV | ||||
| xFf6gyurTeWEdJIjvcgzeYEk9qUXgq6wPdJM5ARiv1Tj4BPPy5yplsG/cruQ | ||||
| /bPtEkuKXtT3rqAZ3PIisWgpgnbgZ7puqfemHdA7S1iIG9vUztVF2KtsohyB | ||||
| X5XHDsymPgchmJEQTE7V64aWyLkORHQ76Idvu/Z4oIP2+vZbOYj2+EVmnz/s | ||||
| SXS9ePlj/rUsBwwrLAe+em7fkVn166+PWOku1sS7WeY2rZ8USGNfgISEAokk | ||||
| Hel3eUYPVCqe463YF++NgdEMN1W3x5/+lNHAjKrZTAyDfPok//eLJvF/kDRi | ||||
| LkXz3DUVVNREAfm4NAsd/cFW4+kXNPNFDmlGPBAsjIREpKrSsaTfIr23ZU4d | ||||
| M3EhGrCIYHwzJ5+17JiW0odXbjg518xwSRoOGFxxRwec9EuwMXDwYFLTQRQJ | ||||
| xThQrNsInz726UmnFVy7AxmkxC6kw3QoeOtUkVjt3MZ1omrivztXH/LMfTjU | ||||
| tOF56boB/xY4ToPnhCw8Mz4BWBYs371TM4VntHR0QtYk0Ws6hHQutAERzJ07 | ||||
| kFSjp5iJT/k3LxirZE1ZH6E6ATEiATwwuciZ9+IxjJPZAy0vCV6au2ugyxPF | ||||
| 7osP1f64z4iz41RDx9jUJJ9V1Yy1r1iNy6eT8uNpGzr2q6Kvysz4NlvgXqGQ | ||||
| w0vaUoGTR+qBqzc5nyn5xndGrGWzWWR9G2SVvLujBYyHCTFYvHdB7hBtoscC | ||||
| wARNk89U4cEZHr20VJJeXjVCMMKwdGNyxgTOGBef+zXUkczjPjKiDdZyWxzk | ||||
| fLyCKViJgoYd+pE4WlkdyPSjXz/L3zkwibZut3REbmqMcLtL1BnePKJrBmMr | ||||
| 2Toh86Ls2uZMO3vsRZCyCAwGDotZ4HW0rWfRGt837YkYF7EmkmlDtecn1hAc | ||||
| +4I2toKBCgU7G8K4mJcdodXzFkPXU6kEluCIGmgZyVTYH1inM/U9LzIS8eV7 | ||||
| YiL7fdFBQyAGGMDcfI53g08l/Dph1Gjh1fW92hqtDKMIXi6znZXwgsyrcnRq | ||||
| Hnu6CkT7MOU0jxSQIB5QWnOiV19Q3XicP7ycH+iMiYUxl97eYhpis6o4qX08 | ||||
| Ni7VJheSZTFO07s8YYw/G41//vAGFYvZEYBK1xHtHNrDUeQ7vZ0ligPpoqng | ||||
| gI5wgolDimBJp6Fr9zqnkZqa6Z7f8p7fq3U9unqENb29uQ7D/CjiVMII6IeU | ||||
| W2boeSVgEVFs3Z5J6VyYyGZgr8WsfuoDm8VZyD9H959DjckK1oBITDTtseGD | ||||
| U1FLZM0Tqa96ZzPtFc9iKUv8WL/eX8lUYLhcx/6W3+SoUdhsutlonfSk609T | ||||
| qcbnTXRSIMt63mgsF5qKtQzfDIDo8OaMpSMbKFKNRgs+vaSFI3Lp6LtuzZjG | ||||
| JWwje0gtPMI6zQHC1FAMR8WcaIIibDqSAqxFZZBmsLtr1nppYqqmKoYjRrcs | ||||
| ezVRdBWBIMYmNAR1i8T7d3J+4uHYsfstPKfqRR+BaZJRh9SkR3euHmTZfUzo | ||||
| mrubsSvH0nsRDGYoWvh5XZyXQ7ukf+ZwLQ990DquuVXsrR5jls7LsQnOJHED | ||||
| ZNTPJ57OdJQPoCOlLOo6EtBEAfZkP+YrV4FFeGAYK8lel5qP6f5YD9VSmFb+ | ||||
| QDSM7sGEQdGsVm5X1JsMPiWoWDpJ5h/zk2RV+noGJejnuFxwigGVYNMN70tL | ||||
| pB38xZ1pogLSkJWRfyPMlKRIvRb0I7h5aUGNrWTZ74JoEMvjlWLrxjZIWzDk | ||||
| mBWFgO1d2dvC/YNuyY2MsZWCIakApxSAbrJ8hGNeYAa+q4/var5c/is7mNsO | ||||
| woHTk0ai2FuALycz29haYxWnI036IfLaQw3aEBOGLkb98jzd9ixHxndDkrAJ | ||||
| 6AgxiUVkM82fBYOeKjq3rthj60il7baMZ0RH1Z/L/ioQgOy7cBJVAD7aH97w | ||||
| TfDrLL/B0Q7QQdtjT5tw/0kmEvBnmY3JmgFHryn3RzJUiz4WPqY6PPge2wkF | ||||
| PY/UOm7+1pUdWQ8dqcEP5IRorEDYirfjffzls7oup4d1hDlX/UXhMe8Kivg/ | ||||
| 43GwPppWnZcQWthzQXE8FqJWhOhkQaRE1HQlw7rX+8WmZAev6+/yH8Ke5+P5 | ||||
| xGx9E4x5g+faZtvicyCbuJeFmm5sDjqHt8R+adpmqV9Ec2By+YbRcvcJQ9nr | ||||
| DscelI2+zb2sjuutG6TV4Eb5eMPmb9m3DbHO5PhHS/w71ijqCv19vE1PF4bt | ||||
| OHjwGag3F3EEoJa+ZTloxYH+LBnEgBMZ0nZ7rGMzjv2AuvG0METPUBYEt1M1 | ||||
| ckwOR3XrpBRhTNetgYMCO2UHPM7net0BpFLAigaz7z1Ez8Lg1qm75vnVU/q/ | ||||
| RYZ/n8kA8fE5lvB+t8ZVdisoYwkmvRC1FJhsNJAVq46k9QBWyMu64KNSkDKK | ||||
| hRBteTzbRRbDHxAna+oGWvNSADe1hu3kQQjHgB4t5q64i6lNcG0WGhcpUCHK | ||||
| 5PdAiQszionEBMc47dpZgrShJ/3TSvBjrSK2eFlUKdmjo1of9hAMK/ROfHPH | ||||
| +DhNyBFtuyYW3HwAeenn5kvDADsDfGVawCKYabFGriCagJnJbgj2EzjGQjAj | ||||
| E6axhwcngoWBEz/hqfEGVoBizB+sS3VXuZPs5QHclwZEe8eIGfN6P5W/k+KO | ||||
| sQUshbj8wf8xx9s/ALETGrSdxbDYBChKMg+Y0ylT37R13Z74gPtGmd2+g3vn | ||||
| UEAbO08ZR9zJe+cOM26SXKJ/4CRjqrExLPKMbMefXcmCxaM2TnBkgFBVwetP | ||||
| f5ekWSrrYLazBRl7oR66oh/bFeOVGUxh8Kd+uSqgn8TjOdAwaL/eE7+sSDNS | ||||
| 8me491T17HDEFoG+3k3nI3MGJA6+52i34QBWYqGTrwvq/ahoe+RsnFPgmX8p | ||||
| dOgDpuD4lmUbwarNEaTCIkPIp0c4D5tpwm27aAR0IkkKCp8hLZLPWTo+NjUF | ||||
| 745QQGIwxFHovaH4AIwPEnGRQ/NllkcPBPrGIeH3459rkrhLxhJCd5ngPhF6 | ||||
| uKoMnfLL8Xf6Hq5e9sA0nw9y+gtz6pR59vORjjG6Eecqdb9yIN/37jAkJDQm | ||||
| 05U6OA5HknBljIGOHjQAlMGzPRGVAOH6Yk7ikWGPtK/BAblUOWMMiXhVtOnx | ||||
| 5houJ+QvpuiI/uMRMl7P4TY8iH4njEaYE59dQ2hZ5JtieEcaY9/bUQ8OzHuP | ||||
| M+2q4UkCCPvzZiotnyo9ZfMu0oUueOcHMhnE53LWwuku1sVBuITJPJwHa8Ip | ||||
| O7twtjfU1Koo3/P0XxHFbt2swjOeaJBh57xn5R5QOinBe9It8q5CJAusTTRB | ||||
| zHAgFehQgIB10Hzij5OjTe0UkHS1W3j1PzqWaJZH+lPjSfk6Hev//4EhKkI2 | ||||
| 7EqjPSFGVR8t2NbIS4grBYQWKc8D0Fitq6I7M/5IVBVHHrDpyuYunHtFM/Xd | ||||
| 0TQGPWv/IJbPZ9dV/Bh2lE7DLe02MU5R5BK1ibtb89A5aGtDNAsXKDD+/Fb0 | ||||
| k0wbI64BH3lZHrvFnDhUdYYaLOu2dzVkRggGAyMOdM+O77qAqXNDP9iEFxp1 | ||||
| odoe4KuwrHEHPvCqJAG+OTKQ0Kg5zNRNu3loB2VeQCSPB1NlRvbZEOkBSbii | ||||
| MpegNrBeTiQbAJJIFVdhnmt0TayIk9L9CSp3HsShV6OqPY4JOqv2EjIgquSu | ||||
| YN2bPo55brrEvXOsXIVNwicIKOEcrCRIMyU4NXqKlwMwAY2BzoREfnTwaHmh | ||||
| bTF26jZX9INY+1AzN2ta3j52yOUKo9Jc2y3bNd7l1zlh/yxMGBNaTXUljTER | ||||
| 4Sorxc6tyH1rIptVejq5JHcaVxORD8QJlA3L6WmKrmtP2M6iF3U00j5n/bFv | ||||
| I0erkM1h8sb9TuPg2pVwFk8k9wKJwJ+Z8LshOnMztgmLrwiSmARle+AiDKRa | ||||
| 96FNOIOEJ4NgKlKRUmQfe4uYTjNlAxfhYC+sb4hmY0KY8FVZ6ngpJ1iIsPIk | ||||
| 2kp8mn7dR4/CW8LGFjgA6f7HZmBdO24ikqKyUhlRBx8bWPY2BKVmItU/tSeo | ||||
| aIsZFYc7/Vz0/EzZG8IiXRQq9fr22wU7DxYhUgQ+2Z9xoHk/aElK0vKIfj04 | ||||
| Oo7tMlHUu+6uYhwm0paKWK2cAf2UUZKsYGuhUoCh6sRGIoGN80psMz82tTGw | ||||
| 2XEDESatLOtpVD3HHHll6RKWlgSdMaWWjlNMbPvZMrTMjgsQ6WiXXxlX+39G | ||||
| Avk9JBDjZbuqM6hoAnTNuYsRf+Q+DOBUJJvU9AcX5AUsRB6kqC37bWZGisgF | ||||
| ar2Goib8BWBMHIRFG2w8ZK0DIGGyh7XN0W0kWhFAJyHxUcu2+InCB2UAGpIn | ||||
| c16qQpF6s+jp1cILGXaGypRiT/TMntL/dLN4qcHi68pBa4Z5eJK5CBQ2FO9d | ||||
| wxoDm/IBfeO2X7z8kU2y4ACWdj1650PqzFq4CTMQ9SjCJ/bwjiM+UQT5pahm | ||||
| YPSVECa/oeYsrwTsoUOsI84sjtkK6FMCrnMOQ2q8crlrTwvbJx1n230OC4jO | ||||
| mEWPz7R8V7VwYcoJ9mtjgjn27oWoQ4XY6MRut9SPWZkWvEPK11HG5cM32S+I | ||||
| 03814sE9wp1VFvHasS2gE+hNZhQxCEJDqlpkd5wPAi7aU18/gQNERycNi0GK | ||||
| mAUzCmNtx6tLtrHGFolsdEgR6MX+zse89YAKiJ8yO9KgnaBAveQIIz47yrMl | ||||
| 5shThi0u6RD4Xl0guhCspGSxumVmpChndbUykyJMk1d4UzufSZBx7AFNigT5 | ||||
| C8zspbqxf2T9BgYM7fWjOE4AIZ8xCKM5lYa0XWCzt/DwzrlZLrh+p2Bc7ZMf | ||||
| LvWj0eXKIDRC5d09vOJjPoZZN9lYk5jh4Twn9gYJ68/vSItuj31yTHyuw/1j | ||||
| NGhJ2lQ7yseg5G2KNsXRKIgMU0DS623VnZ7rzYxTdt/CBwIf6YGj+7jDKEI4 | ||||
| apxF4Yx9wpqyLpCBjuxeGZspz/KHb4qSw1GJKNoj2cq9hC+EZ77IH8KNQxN4 | ||||
| /IPHZ75vibbz76ueDifQACQtiffmZUuc4NGneByyF4X6W1m92EOQ4z3WWSJn | ||||
| ZSQlTOrcvArafZ+YnUH/TjzWxlCxVlOHXCNScYiMlIuUgL1new0RphWCjG2r | ||||
| zGvB+Gi0a1cAIUgAFABZGbqUhZYgR3ZkJN6J8DXGYUQbbzsPkj3/DCDzWEi7 | ||||
| 4+DFyOcxlz7g0SkfHnyENqt7qIys1DPG0f6uEWpNpQFcpiTKaTjK1VdkPW84 | ||||
| 9sc734+SyRWPnFUM0dl4ruq2WZifkkGCRvxCo+iVHgiLPCyGClrpXY0Fa2ud | ||||
| 2MmtINC8eppYKQrrqoY9jgaahr0/DPCPash/vXl0BdtRQq81ZHwwUKES2coA | ||||
| DqRGFNURKXyKdQcJ4KFgD0d5CEhQ1GRPxtlpcU4Rjv1WneoxtjW74ryIsZUc | ||||
| TI93H2NSZu0Knc9wJT1ESJbqXKwtfTxOgtsck1rBCLxS3FmoKrhB+PhrzDL3 | ||||
| It4r7dZHfqcE5Tk/K2KiGrO7YWRWq9OPSQxt/5XD7SdQoREwGd/iFCosHve+ | ||||
| ExZFEiTJhWjxNf0ZVIfvaTgtyzVbMyLeER4s2zFChbF5LnKGJoj1CSETBrDc | ||||
| t6S9iyglJAhKGALR2Int1F62qejtRNFwNs7VveerYub4FCfvqlpqknmSphQB | ||||
| /K9jRz6D1D4KEIIPIjZl6mBx3L8s/fzeM64Nf+UBYSmOmbsqdXMWWpyCClw/ | ||||
| aHuy4LqpoDVowPmJwa4mvKV6ts+lEShFnN4aav2RPGi2jBJGwewHsUVhibmm | ||||
| hhrJ6rUrSAWfKlrsGH0l9G5mb8dB7/zHjHtOWYUESBHPCqCPce4oUMhzAQs0 | ||||
| jFEVRtR1isA2VQ2Ie4yVOnH9RY5esdTUR2heHQS0o6ZFr0H2AxqLTX+YZiE+ | ||||
| 5U/e2n8s/ioDFBWWVWh8JLOVeIlXbduiVhxUOY/F6MGzPw5fnu4nhLQPOjJA | ||||
| W1sSP7rz8TQjz6pXkW1/5fNZTLLMjzheQ10IWU7xrcZrIwarxgN5NzqDJ51b | ||||
| er9+lM+GgGl6nRY+VvdVbE0cqgGrZlJlT2ignxKKo/ziPpTQsArPuocdzWfX | ||||
| 1hy9F/yycIjdHhmf1N8Fsx95SXsWtz6ZYldtd3mcguLhd/Fs6TxZjpEB2qlh | ||||
| xtSPTBj2iPDhbpjBD8yTkNPZHeF1i9zGNnV2xmNWB1EQLQs0DPRjaicyN46b | ||||
| DTAP4Rz7Q3tyGsJnBg4a4KRSjhMJZhNyd4gQxK+8c/U6wc3Y4FLpxWtTgyEI | ||||
| bZPVwFvHoY/7qiSGw6rpWt2ydvg42N+oReMsm9hci8D4Vrq1gIU+Rgt8AIkw | ||||
| ZOERCM6StqH21nVQOx572gonlIMZlB3gPERBXB40isMFoXz4oxZRcXB0YofL | ||||
| fpTH+ZjBspLsINVxIbzZMP9sjCbN2NsXopA1QdVydEaRYCEkXmUFekbsx6i/ | ||||
| SRBWnq0UOqGDXFYqy1kBhOZeJcBJGh8cxRzj/TTwPUv9nLZ7Ucwcca1WNTL2 | ||||
| jtIsvEehk1RfEq0NO+40KD1ETGd+d0PAVvCzjJJkTElRdqogtfFA+dFIhN1P | ||||
| GXOotrZgzzQPQ1Pa1O5WVkVbzG7blmhna8J+j3xaTzrT1MR0QWgvAj9eHy1A | ||||
| tG7PRc2JLwzB02uo0JRvCqLiUWRHLMKh5BBzW3VtsY6EchC4mWEODJFIlYf2 | ||||
| MExk+0JsWTys+BhGoSlMM+zoIagfuXiqfoQcRZKKYpViAeBy1/7OHi4xU1Ec | ||||
| wguJcCIj2pxq7g6sM1G9eJUac+2NLTe24RNFbmFHWuKBoiok9nyoFRQnoNLW | ||||
| HDt1Xa+GRRTPBjt4kOQZjozyuYc98nuJL7FWUCTcf49ASfVnBgkmMmntZKFH | ||||
| TGek0GcX4nlwdFldbXShR+HkkVkhKp2s1yj20uvIRO8/0hkwzOfLh+tHprnM | ||||
| 0HOfa52cKAT1l1+iED4NeJCxM+RJmzzZIJgk3vc8qEPfWNyM8q0MnYQKFEGv | ||||
| kCuyz7FNWpuDN1AT3ZMSNImBEGLYDmbQC/kyxdI6WDw3ZyRGiqsWoxkXXUiS | ||||
| BixOcSbZIIQipX4hix9CmsOK2J5ZGDCgrfaDVW6Rv/hsj6MZvGSvJOYqZR7w | ||||
| usQixTvShM9PBvNHWzbj35gtMyEpAXFfYEhiKsmIq2YS8vT2m5d9/tBdba8W | ||||
| ZjeGltbV2GX+SRXRLAfLqInzOyR1mckVYZN3VZEr4zG0y3bD8llV/AN67HNO | ||||
| wAAT4mJ6Rmo4LrUkKnYwd3glLOYeiUB/+bh4Np2ejbHbe9l5xM3Nfpky7Y/y | ||||
| bA9aXWTbEnX238BmfpfffEQeaIj/vywRFiORIJ1HUuEThUIy6KlBvJAYWzUU | ||||
| xxKEX/6RTFeW6rAbZI80wOccx0wA/xCBwgU+bn9QgT3jGVWMj97P6CcyKtw6 | ||||
| wviiUBXtX9VGj6D66gg+d1KSG//3f/2vnkNkQyJEbD5CiQQDqTXJk5OHfJvR | ||||
| Fhx4xkZm38A0+frrJ1GwlQVsY52+e3ubsz/P2wkSrJts2EXhq+z3twvg7KIE | ||||
| Rr+cxyolywKNK6VokbJeyjiZARz5Vb6YFZ4LCd/XLJFsLAa0jAeywyoxkKwf | ||||
| MYLMYsm5vsEdrRcfSClqILGXPY5ST+bzBkPq43h5TWEeTajiVLeK42PTzJcL | ||||
| oh9q8zQp5hgK//n0mGC5qYhMsnSOTbIYJlUifSCVZZeiO/4Y4VfeuotJdoAz | ||||
| Mo6bQD6ZPchVVELsgPnJo7WgH7ddsRea+EEC8pH67zo+s5bAFrKdg5kbw4oV | ||||
| 1kEa9GPEMmdMyOvl8cDed1QE2zqFjtTALrsjESJKaoX0SoVXOM5HEEUspk9S | ||||
| 9y6jqF6N+TScxr9ZmA37w75lS9+MUnGSLdn8/xXhFPjkyy9pfEQLq6cyIxUn | ||||
| qqgLrRUY8JQxILtynxCw4+kvasZ3DMZV3DlVSQ6uG2DNBqAOeRPI13RsJSPj | ||||
| lJPeaPYQMKXkoo8MKn7MMA41ktn3GHJwPVTNSJtWS1i161F6n/ckJFkkhon5 | ||||
| 9FKcQsVVjJVq5YEg86fGeBL+cymL2UpcrUT3DpaNhmpqb5e7+YQ+BDywpqp/ | ||||
| oihhUg0uYP/3NX8p23wx9mpjQ0s4Ulg3DAX35nLgON/ti08IvlW3OCPPluCr | ||||
| EGsAh+B3KmnHsU8NGwEhGZhRA5llhKFepzSvSJhQZBR8OYsEx1Aslpj9XoJg | ||||
| i8MzQMVs9+xZkxH6DsDuxUC1d5c7vxhgOhN5Mcn4yTKfuhao/WShRLHdKm24 | ||||
| 1OxbiPO6E6Y5E2A9F7fwKRmNWmduU7AiGZtJEFgI56kA+ZHkWR+9ruKjfTRU | ||||
| wFzBTJJqPxQrLPzE6J2kt1iUgKcnDrmqBvlVvQjFkIc0Ii46NCKe7315lgUt | ||||
| gNWUA33cJJae8W+N2TEI0Rd/VMPKs+3ZSNxFVLbOXJ9RVKZJoMVI3eeaULFg | ||||
| eRl1ZHIl6lzG2HFqeyHx+8c9OvwyX4c+iHTgkVdJ8XvYOV+xVHwqA3vJQXrI | ||||
| GTBDRQYf18m5/VZeuPEFCaNaHqEgwDutYIiHn+syj8rt/LXd06wWVhxu2slP | ||||
| Bwzz2UxXtorClKU81oJBejggl5KhZyD9hfa/0SPJ1Z/yvmY1vB+MHK2eneuP | ||||
| e1/WM3EqZLJcTHvw9DvzuK1E670ZfG+f95HjHnutGk3nimwdx8FIO6TdDOxf | ||||
| 5CgX7+Oow/DFr0pKX5EF+rKjBX1eloxrycTsyjQPnxILaU1Tz+KhqwLi89rK | ||||
| lhNCg+c8cbnHgfrZahRdffttmqy6DHsZtC+pSeDpFCqSyTXdisKKsPEhO7XR | ||||
| yxo5VoxoZFQuhWcvnvJ2ZWFQ5a5tJWvMlos4vwMd4T9dRh3xe71LCxUyG4LZ | ||||
| tnJKc9EmedfQccjQHUITWzhktRofxsv+LvBJWGtcd0x5B2pEa4loGEt9NkvS | ||||
| CqPFyigHFfNMl8VkhQ1bAmugOS1p17t1n3FsJvjcHS21jSAs7LCTIOIWPjJf | ||||
| SjCstBMgMgOYow/lFSnyayjo7MDC4KMxSlQ60a4eSKYeIUvOA20tsiC8k3nF | ||||
| pYiOvzJWrxkZbXAr4pKDbaoltxdwesCOrw2VKbq6EgcXN8xHUoO+hfkVcBFE | ||||
| wof2LAMEs5b95rD05eq8xL+yJSyIOFKDp8AjsdDUBUABiTTJfICyWImGQDGE | ||||
| pyqEYEgsDPFxyXoh66Ec+8/mi1dLZkQJHacolJ0fx1KqFHsRccwxCs47CXIr | ||||
| eSBSKgXplb7PkBCW2E9cxoHarTW7SjinMiNGEuSQHjU+3I7bgPpfiPcPsUIa | ||||
| EcSiAeMjfWBPxheAnaDum6kmPrYorYlmo1Hoifc8RDYuFN1OU7osNZTbpocr | ||||
| 1FkTycGl4fGwfS0JKOzWlzOBYMW9kLzOKw4p0tivyUCYFenKRssadpE9VhIW | ||||
| sQ+p46mRamusS66rJkkyrBw26Qt9MFrtHW9a28DVBuMsA3BH/TvwSsQgMpA7 | ||||
| MoAv0COHh+dvyMBAFudnQtL8l1IknxX5RvMlYiU6Osiykp7VKnpETNK7kX0h | ||||
| GJPtobwvx42F1Y0UVJH/yIDMQ2h8u8nyOcODC8GupSZq0ELpw3YroQPcIUcU | ||||
| cgge7uVIZAdUc87Uzu8KxFucfWmhkHsEVQQi4lCNVB5RONwHYbdVyxA59XCv | ||||
| uhYrKML/WcpgpGKeyRBrKecWH+PTTkzQmOtjCRDIuD5K+rzoDXxHDZKfunbg | ||||
| ZIp2swkDiBY76Z71G3WhtI1fcNIZxGzcs5tgmKERr7eIZVxwGqMOJHo2DUug | ||||
| vbunrPDCjCFq4vnVF/fTtICZRs3MoIHrzKhyTSu+EoFCTu2U1V/l8ZtEE1gO | ||||
| v10Q1TIlE2H+PAhukx0KZnj+YgkEfDpwrklXyBTO/PnhWIhNfNysNta9tJcp | ||||
| 7S18j8TfJVeUwW6NeUU7Av7zyrM+a+1hLNmFHZrL5dQtApARBdFfxexDYsNC | ||||
| XW+xKEHWZ0HFI7JdcB62cLiCVIyEnmM6j24E4Is4JKyB1LVR/HnRxI2kldpp | ||||
| x4Un3G8lcQw8PImRAjWu+p5QQ7Q1mfB92t0o+PeiyaSin9XQpj5nQmlcyKZx | ||||
| UdvQTiPlDUFZrd50ITFxll+TyfxOoRKP4JJwB4p0kXf7P1oSO9SmRUQJsnmj | ||||
| LRME2y8r7fabomd0g5WFuI6zJmAWTXI6DHLhesNhXzwbHvF+rYKKt7RIfCox | ||||
| mIvK9KxfLBg6oT0WTTNft7yLjCLkxbYA4UcMDBNVsuXPpsukqp/Gogrn27mi | ||||
| HnZnH11YRffVYAzQw0j6FSJ0gJ5vo0ozQeug3hBgA7erVzZCCRaUm+AZ9X0o | ||||
| nKL1RmrSUxehXPSaobeaq7xGkZ2h1UPb1pKyGViaalTRCWL2euvl5jueOWdN | ||||
| yTc8Lp8uNa4fOTlACy87vAJply/EhYXFhNEYkHFcozdz1WPDmrxQcBqckJVt | ||||
| zTb3nROTvOpSY6zLJ0a5673vHCTWtFkkFphqPakRG1VKAGCnbhc1HFjUgdju | ||||
| l09v1ZpJTAHJas2UXUR2ohlmM6ajt68FHNXk5bbz9FAWpA+C9bARSaPcFHfg | ||||
| JZvMLCrLECVJuHGn2CvQHLlgZVLoUs4yDG/abI618mxWEl81xq1nHh5hW2yu | ||||
| bnCKMBIOtcsspuJqNB+OtokmBVblmWSaJJxF4XqfKJu+kr35hhiGBn1f2qa/ | ||||
| iQoYb5NqhbRN3w0huVFtxrj0mFnLmoyAiZOqnnJuicX0SmEk6vkp9OUzX3lk | ||||
| WQIdxTaeV1zFHSaqa57KwVSbGOuiap2s4cgekk7jaKEcEXA+gELqQzFL1qJP | ||||
| Etmq2135i1+mixN1+ZDLtbOTaF8JZ8kz9rFyrEHQGn6L/vHlIwuu8ReZpFaU | ||||
| JDcYeEErY0XH9z7sJ4YOfSYuYLe1HAsvOXxiNNYuOp5pqQUue25xlBqSCXHk | ||||
| Zarsm/qpx2iRQclQSEG//+PYdsc90eY/+AMUXPF6+wKYcQjXIkKWPoYlKV1D | ||||
| 8g3VgJp4WZFLL15qs3uh8GJuhS3kW+V+knoLhS+bWGwUTNKjr6gGcIDa556I | ||||
| PZYpuOGvfBpHkg7TEAM24+IHo2x5ddBMRkADzn7zcqwMe0lzOvLICfC3lonr | ||||
| l8/u+MOvFlQb0gCUW3MVMy06tFKAL4C2Wk7INjJLQvEeRq5+OsGHXUvvsIiA | ||||
| 8GrllhQwTMYlz02569qmPfbZqYOUbeIGmAN0aOBRuBbwZoV6No6XyrIt9OPq | ||||
| jAIqH866IgqxHhBUMnBJx+/AYZRSKrt+hwtKKpqaWdj9iDaT5bdXWBSsf26P | ||||
| ncgjWw+TbdQ8I5+qA+wkWol0Oz3D4guwLhdqocUD1J6ubOeirIoNV7ySIXlZ | ||||
| qeWR4ijQ2bIUn30mOlG111375bNK/l6ay+qm8ZpvlTx6isOrEkDDwtc584Hr | ||||
| zrbtAM92VLuRS/Dd9FyRAAFlXIrhu0kHWtaR0VLchdF26EygUo/FTtRvfjWw | ||||
| BUuPnY4fnq+OnZjt5tqXd+aoB5ipiwgjSap/3/Pri/kff2jUZtMruRZTjOWC | ||||
| 38uf2h+NsXrHnWe1v8INFacFxQhUtEQHdshyMQMhaDHDEDknGijxws1gBXcC | ||||
| pcs5ynjEifhvDWGwMBAx71dascG8AsHHvZBqNo0U9Ze16oNTIJP6HlpX/PM+ | ||||
| YPTC2Yh5k2CKXOFV2jEX2U4Rd9HSmBb9dSDIYIiZlWaNaKit5q20dpHoGBiP | ||||
| CT91DGs6/qg4A2uuPrHRl+LQUEXOUUGcqgbqrL3BZ5EcneNo2rgQwkyp0MQ6 | ||||
| RzaHZWAOmqhFbAZuu0VyVqOik8SMsa4+hdEGLMhMXCQwQ+Y58WN/OVVSjmp8 | ||||
| j6de5BDqGUXJ24JeYxDU/aor1L1zUNv0zo3rnODUSpDlIOYMx59wumUBu4Cz | ||||
| biybRJ2s7BlTl2ucm4K2VNqwAkeLvOc4CMRH0GEiBhUVDtA2pUQbOrWafXa7 | ||||
| lNlWUqQxyT201O9Vy+WGo1ibKGF8edCaIqwhhiRlu/YE/ZGEZoCa3SkcfVsy | ||||
| drClfT4V54Slymy5hijnqPlCuFpGxRvREsyK+2Y69j40pooHH0zFSU3TNZjE | ||||
| ksVLbpFpWGOaHzHYp1dypbURWfbsKk8isz2tZ89huYVCzX3+ENXHBwxDT2vV | ||||
| LN+TivuIH33VNuqauPycWFMW1nvrw3ojP/G94VXjmo041nFOm4+HRqCuRGCG | ||||
| ipxmwwm3zRBba+G3V/kPzHFEXKD0yVzscWpwmkGaVOVW26d3H2lK/Qr7fjSj | ||||
| ShNI0iR1KUYhxYMEPBL5m81HCWoEwNx9L2lek/K/kBh8RxxOwqr6UOe/JJqT | ||||
| ahV0vuUq6QzAhdZHaGZKAhP3+Jl5YlJkmSOpZPyTjOVxOelJOd9MXokOeSvm | ||||
| lNWmmF9ovXKZ60koiIhjwxE0runFcOzdoBKw1mjVKHjRxx9oEE/RvBfpGQKN | ||||
| NdqoH0sd5ey9rxS+4pflaegfZARa0Ht6sZRcp5e0xshyoUVzQ+2Iko2nuMCK | ||||
| tp8s/n1VT/1j1lYUQp35xhAPHW5NxCDCeks6LFMDszjc5XeFW+vT837Dsev3 | ||||
| FzHHNRiVxKawFLPMpknBapjMb6Xkdcj1119mE513RefGl4QEggvByVvcIKWz | ||||
| iW+FjNYJPYQ8H+haSOcUZR68NWJxymX5+pyouIEX5vGpmRbfHeVlXeWvP+yI | ||||
| HZLyaNQ5yjLNJPu1+qfqCTP1fJMCKnqQiGE5yXc+yv3g8ynYlYe088z0Qalh | ||||
| poVurKybxsDdQbFfiI0JUFbiJKVgDSlvcfC1jz3y1/Ik6lQEkn6vcuqtyans | ||||
| +5HkklKNGpkVSraK7OSy6EdL9KFpJSC9aEtly+GiOL8wooy6NlBbD0VFY1ud | ||||
| U6EZVw+8P5y0l1uH4YK3lzdOAvOTnCvFZ3kOocBfKCozpeGFv5jD3zGQnHVF | ||||
| IW7dYFh/r3NShY+PrtV3EEQXSnpaCnswWeLBIw5UhNLH0d1Kl2kykIcMBANJ | ||||
| tAp0HnSHEcVn2eTZtX9Wtjl3XFZXyiTQZjdRydfL5ay56HH+96mCmP0GDXEs | ||||
| usdxwkktoiS1RLT/LI49WHh5IaJoy2V5EY/echkZasvbk7YGiWFSSSiKrFFI | ||||
| nZOESQ1OTGpKNENXrY6euVmpJNXW0geijH/iegdB1Pp2M5ywCzWtiApTrrRs | ||||
| xZLu3b5x0qm63B760pL01yOM4s6dJzeLUDPy8Syob1FH8eeIE9P5Vs2mPjrW | ||||
| 0U2f0RzO8a3Dlk8/f4GRr7MZLnJAllgPSywk8jQt4Miji7q1qEaDgnjWOP3M | ||||
| Vk47+o/cgMLXmhbCMcX00B5iGzHjJF9nwZtpuiiPb1KqC/bbNE81WXlJQB3a | ||||
| UE5OFjaSTbbIXrObqUifaCoW4W1nwHkNp7bCs1iFcbsjSGqirFjSVny0oopt | ||||
| QWjQYtmRjsuciaOXPXbWddyUpYc9FGM61vhVE1IAOpoM42tOaoewGe/1uljd | ||||
| k2AuU6wWQZvQK/G+QVAcKE4RjKA6JOqSVEWKpzwy8g3YkbBHucY2XUe98ccQ | ||||
| WynWKWyEKzDMnv6gH6ndaeH5jN7JX9aqR8E5yg+3t4rTwkYcnbDs8rWTc2jF | ||||
| wgdk0UmT4USZgLSKL0OKYHS/lq8VCuBunptn2d9343utldZGFyRVA4dMQKWo | ||||
| 2OkW0hKzlKfO3tK3d0UTCrbEN/T8dAuzNfPui9TM7R0n4Bk2X5S48rh2661F | ||||
| DSd9Z1yOq/FRi4F+SDM48rB5JX2Oay9G04IUAsQYSvG7zMcURr6VOJsR9eai | ||||
| lEBLzjW7X50wmdrmWmtNK+POC8fRpfWJLiCc1ko81vUl+Vp08a0IrFfZEDNf | ||||
| +sbXuwno0Uhhuie9N/Nc/GL6pNBjqAqKqze6O5fA+QNuOxyiq106eYjTm/gW | ||||
| rMSj+RHln088FFpEOE2ZfKalBwLe2Mz0TNIdA0tFM4eDiSpHI/krDflN24sI | ||||
| ePbk6ddW5hPDBOyksZ4R5WW6nMEIMAVXcrmltpwVTNKyFakCp2vlMWcbMGhg | ||||
| kWQAzphFYrCFclMxeKw3eyRrpfimm6a1EwUe6mPPbIDlkY+mtZJyNYeex7qw | ||||
| vkMPnVgws5CCegcFX4N3xxsh5HMjfb+Qvn/UQIYRWDZ7DeQnaKefelkhohpT | ||||
| 9T5uTG/E6pPrBIMuW9k1dqHQPu2wv2hxtLyqWWXcnGn1IWCa3jm66KJedWYC | ||||
| tS7PsbaWqHejSgxxCiO7gvIsokRTMhexlumlm/AWSUyIkphrVkKbwbwoRaxn | ||||
| B7UUuadO4tWNOWVy43Z9thJ2hv+NZx+EgS1dxJQlAxJdFx9Gt4MIrswXRTu/ | ||||
| g5n3u/CWW+mmMRFBf7/ppTx7iJy5nJvqxzmfRTlz7dbC7tKzrDlDOhl4G5HG | ||||
| 2wl2OGrUDB7DMxnOtHPrIcGYrcs97MH41eLZquIwtShMGNASDi8XGJTDt/Io | ||||
| HUOcGOl6XcayJ9DX6J5AiRbKDK2N1Nio4Jm/7jRk38o5iAtTbljkTXHaQKVa | ||||
| LMRmkzK9KRqbuFzUJlnEyat29XxdF6tWUR+paLCYq9qRzeWL+uK/duPP3O0u | ||||
| lgcSF6Qq6sR0m16mN7oVd5Ji4kPlGMGKgdTE2fij6RCS9+aFf5Kgk66dl77h | ||||
| koY+zdEvyp3eBuEyAVYn5dwlPzZO201qrOotKhEwlNT9S2tU5JxVFl3d2spV | ||||
| 6kwsmQRp9eN6MfkN4ur8DKZoa6APruUgZYXCzdMJbnWV3+K0+eaUstd2SSZr | ||||
| ogec58s6W1qWAFleoSAgWSG43oX2u9PUJwTFGSn52gmWX6OGhMbLsuqOqAUU | ||||
| D+H9RpCfRdMu282y0l8/adeL+YYlBmniy8MViVXtlOQ5k1gDS2bLs/DlZyFn | ||||
| WFJ7pOULnFLgXw1bSMIvFlE0hBpkUO59xIClN6xc7gMGpmgjZAKuycJP5yiX | ||||
| gqtW+9A3LmYTXZLgWy4EbTVYVIxoXxrpI1WzW7vnh6y1ZVSCe0G6U/fxpsP1 | ||||
| rOIajM46H43fdtoj94wn4qnnNqmWxDVPkgS0RbhVwdhrNKuoaoOWD1XEjvf1 | ||||
| hmsh2Q0/22ozpHVHG6RA7phRkLxjXvBHvdYPBU8jUUjcotqv4BIE++WHbkhV | ||||
| Wa6Ab3VSduZlWvozPESmciHAP3/3V+qXfVmV3TvCX/8dtcxrt6pRxlXq2FjE | ||||
| AAq+Nf7B1x9YYdBqlX3oh85H13ZVT6eg0Hrc0k4xFGAwQ1QrgHjaXVHKwBGW | ||||
| DmmI1A3lA966xbG3Pz5yFW8F371Els2UzImC0KWO3ehm7bqeuV17rpBQrMpY | ||||
| qBtbqKIdM3uX1B22YWWDQDrzK8RO0Xg9F/k6Xa/HulYzVwfMlZK9bBynVn5R | ||||
| RgWu5uFXj4Os3KRK4JdPnj4sHz18/igGgy5ujyqZuIDgNiphM+9D9xvpoffR | ||||
| jqEum5UrUBVDE7s/I15KVvDyfyJJ7sY7vNKRRbnPcV35cY33RQi0lZJVkrov | ||||
| FxNz+Kb3p5nNGcrb+LwFRfHiaiXhBp9mPRI9Um3XXzOpAZABqot8pxuO3lVX | ||||
| IF+KAKZfS2Exy+JBUop1LfpdNGqIBp94wrdlioDCFYm4pHGtqk10EaQYOG03 | ||||
| KWKJ234MgYr9hwj5PnJA3MsklVbLAvmgJAvb7NOFHNmXN0nV/EzRWuKzTL5n | ||||
| XMF6e/NokbNaTov9TL559kjuf7TsHz4lSPOTkaVJvr5CraXNSKzbzV9vPjKF | ||||
| HeMh8uQob1gBEhp3CKwCW7/KfPx5fEVOfMtUNS4tzPD4ZgPYQ2/MyuZ9EBL4 | ||||
| uSmkwLB54Gl0Cyk2Ln+o2p2ZRhXgHDAkvqkT8/+Rw5TnJ82I8wNoGw+YpB+w | ||||
| CvBAFA5IuS1iCLqlNy0O0pjYXxuJyEOhvGbLKfNR0tpntLcx5sr9F43cGfzn | ||||
| oqvym+79+3aRv62ACK/zF0XHN4y9IJ25yV/nL4vuwLX6FqQ+4xa87CWjYYv8 | ||||
| z+2uyV/mf6lpI+D+e9Gu8j8h4qHBb03+I/Q9Tpa4ddTUu2OHynCWAyUEb3fH | ||||
| f4vwBXNRaBlOPnwHpIRxeKFRdLjwBs2QAdhSu2d++HsOfcjfuFMlbPkF0Uv+ | ||||
| olqvFTxSzGENR99V9n8AlczKZ6GlAAA= | ||||
| </rfc> | </rfc> | |||
| End of changes. 91 change blocks. | ||||
| 1433 lines changed or deleted | 886 lines changed or added | |||
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||