<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> version='1.0' encoding='utf-8'?>
<!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.2.8 -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [

<?rfc toc="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?> "rfc2629-xhtml.ent">
<rfc ipr="trust200902" docName="draft-ietf-iasa2-rfc4071bis-11" category="bcp"
obsoletes="4071, 4333, 7691"> 7691"
  <!-- xml2rfc v2v3 conversion 2.34.0 -->


    <title abbrev="IASA2">Structure abbrev="IASA 2.0">Structure of the IETF Administrative Support Activity, Version 2.0</title>
    <seriesInfo name="RFC" value="8711"/>
    <seriesInfo name="BCP" value="101"/>
    <author initials="B." surname="Haberman" fullname="Brian Haberman">
      <organization>Johns Hopkins University</organization>
    <author initials="J." surname="Hall" fullname="Joseph Lorenzo Hall">
      <organization>Internet Society</organization>
    <author initials="J." surname="Livingood" fullname="Jason Livingood">
    <date year="2019" month="April" day="12"/> year="2020" month="February"/>

      <t>The IETF Administrative Support Activity (IASA) was originally
established in 2005. In the years since then, the needs of the IETF
evolved in ways that required changes to its administrative
structure. The purpose of this document RFC is to document and describe
the IETF Administrative Support Activity, version 2 2.0 (IASA 2.0). It
defines the roles and responsibilities of the IETF Administration LLC
Board (IETF LLC Board), the IETF Executive Director, and the Internet Society in the
fiscal and administrative support of the IETF standards process.  It
also defines the membership and selection rules for the IETF
LLC Board.</t>
      <t>This document obsoletes RFC 4071, RFC 4333, and RFC 7691.</t>
    <section anchor="introduction" title="Introduction"> numbered="true" toc="default">
      <t>The IETF Administrative Support Activity (IASA) was originally
established in 2005.  In the years since then, the needs of the
IETF evolved in ways that required changes to its administrative
structure.  The purpose of this document is to document and describe
the IASA 2.0 structure.</t>
      <t>Under IASA 2.0, the work of the IETF’s IETF's administrative and fundraising
tasks is conducted by an administrative organization, the IETF Administration
Limited Liability Company (“IETF LLC”).
LLC (IETF LLC). Under this structure, the IETF
Administrative Oversight Committee (IAOC) is eliminated, and its oversight
and advising functions transferred to the IETF LLC Board.</t>
      <t>The IETF LLC provides the corporate legal home for the IETF, the Internet
Architecture Board (IAB), and the Internet Research Task Force (IRTF), and
financial support for the operation of the RFC Editor.</t>
      <t><xref target="I-D.haberman-iasa20dt-recs"/> target="I-D.haberman-iasa20dt-recs" format="default"/> discusses the challenges facing the
original IASA structure as well as several options for reorganizing the
IETF's administration under different legal structures. This document
outlines how the chosen option is structured and describes how
the organization fits together with existing and new IETF
community structures.</t>
      <t>Under IASA 2.0, most of the responsibilities that <xref target="RFC4071"/> target="RFC4071" format="default"/> assigned to
the IETF Administrative Director (IAD) and the Internet Society (ISOC) were
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
administrative needs of the IETF and to ensure that the IETF LLC meets the
needs of the IETF community.</t>
      <t>Eliminating the IAOC meant that changes were required in how
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
<xref target="I-D.ietf-iasa2-trust-update"/>.</t> target="RFC8714" format="default"/>.</t>
      <t>This document obsoletes <xref target="RFC4071"/>, target="RFC4071" format="default"/>, which specified the original IASA,
<xref target="RFC4333"/>, target="RFC4333" format="default"/>, which specified the selection guidelines and process for IAOC
members, and <xref target="RFC7691"/>, target="RFC7691" format="default"/>, which specified terms for IAOC members.</t>
    <section anchor="scope-limitation" title="Scope Limitation"> numbered="true" toc="default">
      <name>Scope Limitation</name>
      <t>The document does not propose any changes related to the
standards process as currently conducted
by the Internet Engineering Steering Group (IESG) and Internet
Architecture Board (IAB) (see BCP 9 <xref target="RFC2026"/>, target="RFC2026" format="default"/> and
BCP 39 <xref target="RFC2850"/>). target="RFC2850" format="default"/>). In addition, no changes are made to the appeals
chain, the process for making and confirming IETF and IAB appointments (see
BCP 10 <xref target="I-D.ietf-iasa2-rfc7437bis"></xref>), target="RFC8713" format="default"/>),
the technical work of the Internet Research Task Force (IRTF) (see BCP 8 <xref target="RFC2014"/>),
target="RFC2014" format="default"/>), or to
ISOC’s ISOC's membership in or support of other organizations.</t>
    <section anchor="llc-agreement-with-the-internet-society" title="LLC numbered="true" toc="default">
      <name>LLC Agreement with the Internet Society"> Society</name>
      <t>The LLC Agreement between the IETF LLC and ISOC is available
at <xref target="IETF-LLC-A"/>. target="IETF-LLC-A" format="default"/>. This IASA2 IASA 2.0 structure, and thus this document,
depends on the LLC Agreement and will refer to it to help
explain certain aspects of the legal
relationship between the IETF LLC and ISOC.</t>
      <t>The LLC Agreement was developed
between legal representatives of the IETF and ISOC and includes all
critical terms of the relationship, while still enabling maximum
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,
so that the Board has flexibility to make changes without amending
the agreement. The Board can independently develop policy or procedures
documents that fill gaps.</t>
    <section anchor="definitions-and-principles" title="Definitions numbered="true" toc="default">
      <name>Definitions and Principles"> Principles</name>
      <section anchor="terminology" title="Terminology"> numbered="true" toc="default">
        <t>Although most of the terms, abbreviations, and acronyms used in this
document are reasonably well known, first-time readers may find some
terminology confusing.  This section therefore attempts to provide a
quick summary.</t>

<t>IAB: Internet
        <dt>IAB:</dt> <dd>Internet Architecture Board (see <xref target="RFC2026"/>,
	target="RFC2026" format="default"/> and <xref target="RFC2850"/>).</t>

<t>IAD: IETF target="RFC2850" format="default"/>).</dd>

        <dt>IAD:</dt> <dd>IETF Administrative Director, a role obsoleted by this document
and the ISOC/IETF ISOC / IETF LLC Agreement (<xref target="IETF-LLC-A"/>) (see <xref target="IETF-LLC-A" format="default"/>) and replaced by the
IETF LLC Executive Director.</t>

<t>IAOC: IETF Director.</dd>
        <dt>IAOC:</dt> <dd>IETF Administrative Oversight Committee, a committee that oversaw
IETF administrative activity. The IAOC is obsoleted by this document and
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
Board (See (see <xref target="I-D.ietf-iasa2-trust-update"/>).)</t>

<t>IASA: The target="RFC8714" format="default"/>).</dd>
        <dt>IASA:</dt> <dd>The IETF Administrative Support Activity, consists of the IETF
LLC board, Board, employees, and contractors. Uses of the term ‘IASA’ 'IASA' as
a proper noun may imply a subset of these roles, or all of them.</t>

<t>IASA 2.0: Version 2.0 of the them.</dd>
        <dt>IASA 2.0:</dt> <dd>The IETF Administrative Support Activity,
	version 2.0 (defined by this document.</t>

<t>IESG: Internet document).</dd>
        <dt>IESG:</dt> <dd>Internet Engineering Steering Group (see <xref target="RFC2026"/>,
	target="RFC2026" format="default"/> and
<xref target="RFC3710"/>).</t>

<t>IETF: Internet target="RFC3710" format="default"/>).</dd>
        <dt>IETF:</dt> <dd>Internet Engineering Task Force (see <xref target="RFC3233"/>).</t>

<t>IETF target="RFC3233" format="default"/>).</dd>
        <dt>IETF Administration LLC: The LLC:</dt> <dd>The legal entity - a disregarded Limited Liability Company
(LLC) of The Internet Society - established to provide a corporate legal framework
for facilitating current and future activities related to the IETF, IAB, and IRTF.
It was established by the ISOC/IETF ISOC / IETF LLC Agreement (<xref target="IETF-LLC-A"/>) (see <xref target="IETF-LLC-A" format="default"/>) and is referred
to as “IETF LLC.”</t>

<t>IETF "IETF LLC".</dd>
        <dt>IETF LLC Executive Director: the Director:</dt> <dd>the Executive Director for the IETF LLC, responsible
for day-to-day administrative and operational direction (See (see <xref target="staff-responsibilities"/>). target="staff-responsibilities" format="default"/>).
Also referred to as “IETF "IETF Executive Director”.</t>

<t>IETF Director".</dd>
        <dt>IETF LLC Board: The Board:</dt> <dd>The Board of Directors of the IETF LLC. The IETF LLC
Board is formally a multi-member “manager” "manager" of the IETF LLC on behalf
of ISOC (See (see <xref target="board-responsibilities"/>).</t>

<t>ISOC: Internet target="board-responsibilities" format="default"/>).</dd>
        <dt>ISOC:</dt> <dd>Internet Society (see <xref target="I-D.ietf-iasa2-rfc2031bis"/> target="RFC8712" format="default"/> and <xref target="ISOC"/>).</t> target="ISOC" format="default"/>).</dd>
      <section anchor="key-differences-from-the-old-iasa-structure-to-iasa-20" title="Key numbered="true" toc="default">
        <name>Key Differences From from the Old IASA Structure to IASA 2.0">

<t><list style="symbols">
  <t>The 2.0</name>
        <ul spacing="normal">
          <li>The IAOC and IAD roles defined in RFC 4071 are eliminated.</t>
  <t>The eliminated.</li>
          <li>The former ISOC and IAD responsibilities are assigned to a new
organization, IETF Administration LLC.</t>
  <t>The LLC.</li>
          <li>The Board of Directors of the IETF LLC  -- formally a multi-member “manager” "manager" of the IETF LLC on behalf of ISOC  -- assumes the oversight responsibilities from the IAOC.</t>
  <t>The IAOC.</li>
          <li>The Board of the IETF LLC is more focused on strategy and oversight than the IAOC was, with the IETF Executive Director and their team in charge of day-to-day operations.</t>
  <t>The operations.</li>
          <li>The IAD role is replaced with the IETF Executive Director role.</t>
  <t>The role.</li>
          <li>The role that was previously referred to as “IETF "IETF Executive
Director" in older documents such as <xref target="RFC2026"/> target="RFC2026" format="default"/> is now “Managing "Managing
Director, IETF Secretariat”.</t>
</list></t> Secretariat".</li>
      <section anchor="llc-responsibilities" title="General numbered="true" toc="default">
        <name>General IETF LLC Responsibilities"> 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>
        <t>The responsibilities of the IETF LLC are:</t>

<t><list style="symbols">
        <ul spacing="normal">
          <li>Operations. The IETF LLC is responsible for supporting the ongoing operations of the IETF, including meetings and non-meeting activities.</t>
  <t>Finances. activities.</li>
          <li>Finances. The IETF LLC is responsible for managing the IETF’s IETF's finances and budget.</t>
  <t>Fundraising. budget.</li>
          <li>Fundraising. The IETF LLC is responsible for raising money on behalf of the IETF.</t>
  <t>Compliance. IETF.</li>
          <li>Compliance. The IETF LLC is responsible for establishing and enforcing policies to ensure compliance with applicable laws, regulations, and rules.</t>
</list></t> rules.</li>
        <t>The manner by which these responsibilities under the IETF LLC are organized
is intended to address the problems described in Sections 3.1.1.,
<xref target="I-D.haberman-iasa20dt-recs" section="3.1.1" sectionFormat="bare"/>,
<xref target="I-D.haberman-iasa20dt-recs" section="3.1.2" sectionFormat="bare"/>, and 3.1.3
<xref target="I-D.haberman-iasa20dt-recs" section="3.1.3" sectionFormat="bare"/>
of <xref target="I-D.haberman-iasa20dt-recs"/>. target="I-D.haberman-iasa20dt-recs" format="default"/>.
Specifically, this is
intended to bring greater clarity around roles, responsibilities,
representation, decision-making, and authority.</t>
        <t>In addition, by having the IETF LLC manage the IETF’s IETF's finances and conduct the IETF’s IETF's fundraising, confusion about who is responsible for representing the IETF to sponsors and who directs the uses of sponsorship funds should have been be eliminated. Finally, having the IETF LLC reside in a defined, distinct legal entity, and taking responsibility for operations, enables the organization to execute its own contracts without the need for review and approval by ISOC.</t>
      <section anchor="principles" title="IETF numbered="true" toc="default">
        <name>IETF LLC Working Principles"> Principles</name>
        <t>The IETF LLC is expected to conduct its work according to the following principles:</t>

<t><list style="symbols">
        <ul spacing="normal">
          <li>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
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
about the IETF LLC annual budget and associated regular financial reports, results of financial and any
other independent audits, tax filings, significant contracts contracts, or other significant long-term financial
commitments that bind the IETF LLC. Whatever doesn’t doesn't have a specific
justification for being kept confidential is expected to be made public. The Board is expected to develop
and maintain a public list of confidential items, describing the nature of the information and the reason
for confidentiality. The Board will also publish its operating procedures.</t>
  <t>Responsiveness procedures.</li>
          <li>Responsiveness to the community. The IETF LLC is expected to act consistently with the documented consensus of the IETF community, to be responsive to the community’s community's needs, and to adapt its decisions in response to consensus-based community feedback.</t>
  <t>Diligence. feedback.</li>
          <li>Diligence. The IETF LLC is expected to act responsibly so as to minimize risks to IETF participants and to the future of the IETF as a whole, such as financial risks.</t>
  <t>Unification: risks.</li>
          <li>Unification: The IETF LLC provides the corporate legal home for the IETF, the Internet
Architecture Board (IAB), and the Internet Research Task Force (IRTF), and
financial support for the operation of the RFC Editor.</t>
  <t>Transfer Editor.</li>
          <li>Transfer or Dissolution: Consistent with <xref target="IETF-LLC-A"/>, target="IETF-LLC-A" format="default"/>, the IETF LLC subsidiary may be transferred from ISOC to
another organization, at the request of either party. Similarly, the IETF LLC may be dissolved if necessary. Should
either event occur, the IETF community should be closely involved in any decisions and plans. Any transfer,
transition, or dissolution should be conducted carefully and with minimal potential disruption to the IETF.</t>
</list></t> IETF.</li>
        <t>The transparency and responsiveness principles are designed to address the concern outlined in Section 3.3 of
<xref target="I-D.haberman-iasa20dt-recs"/> target="I-D.haberman-iasa20dt-recs" section="3.3" sectionFormat="of"/> about the need for improved timeliness of sharing of information and decisions and seeking community comments. The issue of increased transparency was important throughout the IASA 2.0 process, with little to no dissent.  It was recognized that there will naturally be confidentiality requirements about some aspects of contracting, personnel matters, and other narrow areas.</t>
      <section anchor="principles-of-the-ietf-and-isoc-relationship" title="Principles numbered="true" toc="default">
        <name>Principles of the IETF and ISOC Relationship"> Relationship</name>
        <t>The principles of the relationship between the IETF and ISOC are outlined in <xref target="I-D.ietf-iasa2-rfc2031bis"/>. target="RFC8712" format="default"/>.
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 financial support.</t>
      <section anchor="relationship-of-the-ietf-llc-board-to-the-ietf-leadership" title="Relationship numbered="true" toc="default">
        <name>Relationship of the IETF LLC Board to the IETF Leadership"> Leadership</name>
        <t>The IETF LLC Board is directly accountable to the IETF community for the
performance of the IASA 2.0.  However, the nature of the Board’s Board's work
involves treating the IESG, IRTF, and IAB as major internal customers of the
administrative support services.  The Board and the IETF Executive Director should not
consider their work successful unless the IESG, IRTF, and IAB are also
satisfied with the administrative support that the IETF is receiving.</t>
      <section anchor="review-of-ietf-executive-director-and-ietf-llc-board-decisions" title="Review numbered="true" toc="default">
        <name>Review of IETF Executive Director and IETF LLC Board Decisions"> Decisions</name>
        <t>The IETF LLC Board is directly accountable to the IETF community for the performance of the IASA 2.0, including hiring and managing the IETF Executive Director. In extreme cases of dissatisfaction with the IETF LLC, the IETF community can utilize the recall process as noted in <xref target="director-removal"/>.</t> target="director-removal" format="default"/>.</t>
        <t>Anyone in the community of IETF participants may ask the Board for a 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>
        <t>A formal request for review must be addressed to the IETF LLC Board chair and must include a description of the decision or action to be reviewed, an explanation of how, in the requestor’s requestor's opinion, the decision or action violates the BCPs or IASA 2.0 operational guidelines, and a suggestion for how the situation could be rectified.</t>
        <t>The IETF LLC shall respond to such requests within a reasonable period, typically within 90 days, and shall publicly publish information about the request and the corresponding response and/or result.</t>
      <section anchor="termination-and-change" title="Termination numbered="true" toc="default">
        <name>Termination and Change"> Change</name>
        <t>Any major change to the IASA 2.0 arrangements shall require
community consensus and deliberation and shall be reflected by a
subsequent Best Current Practice (BCP) document.</t>
    <section anchor="structure-of-iasa2" title="Structure numbered="true" toc="default">
      <name>Structure of IASA2"> IASA 2.0</name>
      <section anchor="staff-responsibilities" title="IETF numbered="true" toc="default">
        <name>IETF Executive Director and Staff Responsibilities"> Responsibilities</name>
        <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 operations of the IETF LLC, including hiring staff to perform various operational functions. The IETF Executive Director and any staff may be employees or independent contractors.</t>
        <t>Allowing for the division of responsibilities among multiple staff members and contractors is designed to address some of the concerns raised in
Section 3.2 <xref target="I-D.haberman-iasa20dt-recs" section="3.2" sectionFormat="bare"/> (Lack of Resources) and
Section 3.4 <xref target="I-D.haberman-iasa20dt-recs" section="3.4" sectionFormat="bare"/> (Funding/Operating Model Mismatch and Rising Costs) of <xref target="I-D.haberman-iasa20dt-recs"/>.</t> target="I-D.haberman-iasa20dt-recs" format="default"/>.</t>
        <t>Based on the amount of work previously undertaken by the IAD and others involved in the IETF administration, the design of the IETF LLC anticipated that the IETF Executive Director may need to hire multiple additional staff members. For example, resources to manage fundraising, to manage the various contractors that are engaged to fulfill the IETF’s IETF's administrative needs, and to support outreach and communications were envisioned.</t>
        <t>The IETF has historically benefited from the use of contractors for
	accounting, finance, meeting planning, administrative assistance,
	legal counsel, tools, and web site support, as well as other services
	related to the standards process (RFC (e.g., RFC Editor and IANA). Prior to making the transition from IASA to IASA 2.0, the IETF budget reflected specific support from ISOC for communications and fundraising as well as some general support for accounting, finance, legal, and other services. The division of responsibilities between staff and contractors is at the 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, the NOC’s operation of the meeting network, network by the Network Operations Center (NOC), and some outreach and communications activities conducted by the Education and Mentoring Directorate. The IETF LLC staff is expected to respect the IETF community’s community's wishes about community involvement in these and other functions going forward as long as the staff feels that they can meet the otherwise-stated needs of the community. Establishing the framework to allow the IETF LLC to staff each administrative function as appropriate may require the IETF community to document its consensus expectations in areas where no documentation currently exists.</t>
        <t>In summary, the IETF Executive Director, with support from the team that they alone direct and lead, is responsible for:</t>

<t><list style="symbols">
        <ul spacing="normal">
          <li>Developing and refining an annual budget and other strategic financial planning documents at the direction of the Board.</t>
  <t>Executing Board.</li>
          <li>Executing on the annual budget, including reporting to the Board regularly with forecasts and actual performance to budget.</t>
  <t>Hiring budget.</li>
          <li>Hiring and/or contracting the necessary resources to meet their goals, within the defined limits of the IETF
Executive Director’s Director's authority and within the approved budget. This includes managing and leading any such
resources, including performing regular performance reviews.</t>
  <t>Following reviews.</li>
          <li>Following the pre-approval guidelines set forth by the Board for contracts or other decisions that have financial costs that exceed a certain threshold of significance. Such thresholds are expected to be set reasonably high so that the need for such approvals is infrequent and only occurs when something is truly significant or otherwise exceptional. It is expected that the IETF Executive Director is sufficiently empowered to perform the job on a day-to-day basis, being held accountable for meeting high level high-level goals rather than micromanaged.</t>
  <t>Regularly being micromanaged.</li>
          <li>Regularly updating the Board on operations and other notable issues as reasonable and appropriate.</t>
  <t>Ensuring appropriate.</li>
          <li>Ensuring that all staff and/or other resources comply with any applicable policies established or approved by the Board, such as ethics guidelines and/or a code of conduct.</t>
</list></t> conduct.</li>
      <section anchor="board-responsibilities" title="IETF numbered="true" toc="default">
        <name>IETF LLC Board Responsibilities"> Responsibilities</name>
        <t>This section is intended to provide a summary of key IETF LLC Board responsibilities,
but the precise and legally binding responsibilities are defined in the LLC Agreement
<xref target="IETF-LLC-A"/> target="IETF-LLC-A" format="default"/> and applicable law. To the extent to which
   If there are unintentional differences or other confusion between this document
   confusion, the LLC Agreement and these authoritative sources, these sources will
control over this document.</t> applicable law are authoritative.</t>
        <t>Board members have fiduciary obligations imposed by the LLC Agreement and applicable law,
including duties of loyalty, care care, and good faith. The Board is responsible to set
for setting broad strategic direction for the LLC, and adopt adopting an annual budget, hire hiring or terminate terminating an
IETF Executive Director (or amend amending the terms of their engagement), adopt adopting any employee benefit plans,
consulting the relevant IETF communities on matters related to the LLC as appropriate, approve approving any
changes to the LLC governance structure, incur incurring any debt, and approve approving entering into agreements
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 decision-making to staff.</t>
        <t>Per Section 5(d) of the LLC Agreement and as also described in
	<xref target="principles"/>, target="principles" format="default"/> of this document, the Board shall,
as appropriate, act transparently and provide the IETF community with an opportunity to review
and discuss any proposed changes to the IETF LLC structure prior to their adoption.</t>
        <t>The role of the Board is to ensure that the strategy and conduct of the IETF LLC is consistent with the IETF’s IETF's needs  -- both its concrete needs and its needs for transparency and accountability.  The Board is not intended to directly define the IETF’s IETF's needs; to the extent that is required, the IETF community should document its needs in consensus-based RFCs (e.g., as the community did in <xref target="I-D.ietf-mtgvenue-iaoc-venue-selection-process"/>) target="RFC8718" format="default"/>) and provide more detailed input via consultations with the Board (such as takes place on email discussion lists or at IETF meetings).</t>
        <t>Key IETF LLC Board responsibilities include:</t>

<t><list style="symbols">
        <ul spacing="normal">
          <li>Setting broad strategic direction for the LLC.</t>
  <t>Hire LLC.</li>
          <li>Hiring or terminate terminating an IETF Executive Director (or amending the terms of their engagement).</t>
  <t>Delegate engagement).</li>
          <li>Delegating management of day-to-day activities and related decision-making to staff.</t>
  <t>Adopt staff.</li>
          <li>Adopting any employee benefit plans.</t>
  <t>Consult plans.</li>
          <li>Consulting the relevant IETF communities on matters related to the LLC, as appropriate.</t>
  <t>Approve appropriate.</li>
          <li>Approving any changes to the LLC governance structure.</t>
  <t>Adopt structure.</li>
          <li>Adopting an annual budget and, as necessary, incur any debt.</t>
  <t>Prepare debt.</li>
          <li>Preparing accurate and timely financial statements for ISOC, and in accordance with generally
accepted accounting principles.</t>
  <t>Provide principles.</li>
          <li>Providing assistance to help facilitate ISOC’s ISOC's tax compliance, including but not limited to assistance related to preparing the Form 990 and responding to any IRS United States Internal Revenue Service (IRS) questions and audits.</t>
  <t>Approve audits.</li>
          <li>Approving entering into agreements that that meet a significant materiality threshold to be
determined by the Board.</t>
  <t>Limit Board.</li>
          <li>Limiting its activities to the purposes as set forth in Section 4 of the LLC Agreement, in a manner
consistent with ISOC’s ISOC's charitable purposes.</t>
  <t>Establish purposes.</li>
          <li>Establishing an investment policy.</t>
  <t>Use policy.</li>
          <li>Using best efforts to conduct all of its activities in strict compliance with the LLC Agreement and all
applicable laws, rules rules, and regulations.</t>
  <t>Ensure regulations.</li>
          <li>Ensuring that IETF LLC is run in a manner that is transparent and accountable to the IETF community;</t>
  <t>Develop community.</li>
          <li>Developing policies, including those noted in <xref target="llc-policies"/>), target="llc-policies" format="default"/>, procedures, and a compliance program.</t>
  <t>Obtain program.</li>
          <li>Obtaining Commercial General Liability and other appropriate insurance policies, with
agreed-upon coverage limits.</t>
  <t>Recruit limits.</li>
          <li>Recruiting new Directors for consideration in all of the various appointment processes.</t>
</list></t> processes.</li>
      <section anchor="board-design-goals" title="Board numbered="true" toc="default">
        <name>Board Design Goals"> Goals</name>
        <t>A goal of this Board composition is to balance the need for the IETF 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 smaller than the previous IAOC and the other leadership bodies of the IETF, in part to keep the Board focused on its rather limited set of strategic responsibilities as noted in <xref target="board-responsibilities"/>.</t> target="board-responsibilities" format="default"/>.</t>
        <t>This board structure, with limited strategic responsibilities noted in <xref target="board-responsibilities"/> target="board-responsibilities" format="default"/> and limited size, together with the staff responsibilities noted in <xref target="staff-responsibilities"/>, target="staff-responsibilities" format="default"/>, is designed to overcome the challenges described in Section 3.1.4 of
<xref target="I-D.haberman-iasa20dt-recs"/> target="I-D.haberman-iasa20dt-recs" section="3.1.4" sectionFormat="of"/>
concerning oversight. This establishes a clear line of oversight over staff performance: the IETF LLC Board oversees the IETF Executive Director’s Director's performance and has actual legal authority to remove a non-performing IETF Executive Director. The IETF Executive Director is responsible for the day-to-day operation of the IETF LLC.</t>
        <t>Finally, the Board would be is expected to operate transparently, to further address the concern raised in Section 3.3 of
<xref target="I-D.haberman-iasa20dt-recs"/>. target="I-D.haberman-iasa20dt-recs" section="3.3" sectionFormat="of"/>. The default transparency rule arrived at during the IASA 2.0 design process is detailed above in <xref target="principles"/>. target="principles" format="default"/>. The Board will need to establish how it will meet that commitment.</t>
    <section anchor="board" title="IETF numbered="true" toc="default">
      <name>IETF LLC Board Membership, Selection Selection, and Accountability"> Accountability</name>
      <t>The section outlines the composition of the IETF LLC Board, selection of IETF LLC Board Directors, and related details.</t>
      <section anchor="board-composition" title="Board Composition"> numbered="true" toc="default">
        <name>Board Composition</name>
        <t>There is a minimum of 5 directors, which is expandable to 6 or 7.</t>

<t><list style="symbols">
  <t>1 7.
	The IETF LLC Board is comprised of the following:</t>
        <ul spacing="normal">
          <li>1 IETF Chair or delegate selected by the IESG</t>
  <t>1 IESG</li>
          <li>1 Appointed by the ISOC Board of Trustees</t>
  <t>3 Trustees</li>
          <li>3 Selected by the IETF NomCom, Nominating Committee (NomCom), confirmed by the IESG</t>
  <t>Up IESG</li>
          <li>Up to 2 Appointed by the IETF LLC board Board itself, on an as-needed basis, confirmed by the IESG</t>
</list></t> IESG</li>
        <t>For the first slot listed above, the presumption is that the IETF
Chair will serve on the board. At the IESG’s IESG's discretion, another area
director may serve instead, or exceptionally the IESG may run a
selection process to appoint a director. The goal of having this slot
on the board is to maintain coordination and communication between the
board and the IESG.</t>
      <section anchor="llc-directors" title="IETF numbered="true" toc="default">
        <name>IETF LLC-Appointed Directors"> Directors</name>
        <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
two. These appointments need not be on an exceptional basis, but basis; they
can be routine, and may occur at any time of the year since it is
on an as-needed basis.</t>
        <t>The appointment of a Board-appointed Director requires a two-thirds
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
is designated by the Board, with the maximum term being three years,
or until their earlier resignation, removal removal, or death.  The Board may
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> target="term-limit" format="default"/>.</t>
      <section anchor="director-recruitment" title="Recruiting numbered="true" toc="default">
        <name>Recruiting IETF LLC Board Directors"> Directors</name>
        <t>The Board itself is expected to take an active role in recruiting potential new Directors, regardless of the process that may be used to appoint them. In particular, the NomCom is primarily focused on considering requirements expressed by the Board and others, reviewing community feedback on candidates, conducting candidate interviews, and ultimately appointing Directors. The  Board and others can recruit potential Directors and get them into the consideration process of the NomCom or into open considerations consideration processes of the other appointing bodies if those bodies choose to use such processes.</t>
      <section anchor="term-length" title="IETF numbered="true" toc="default">
        <name>IETF LLC Board Director Term Length"> Length</name>
        <t>The term length for a Director is three years. The exceptions to this
guideline are:</t>

<t><list style="symbols">
  <t>For the
        <ul spacing="normal">
          <li>The terms for some Directors during the first full formation of
the IETF LLC Board in order to establish staggered terms and for any
appointments to fill a vacancy.</t>
  <t>The vacancy.</li>
          <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
applies regardless of whether the appointed individual is on the
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
term lengths established in <xref target="I-D.ietf-iasa2-rfc7437bis"></xref>, Section
</list></t> target="RFC8713" section="3.4" sectionFormat="comma" format="default"/>.</li>
      <section anchor="term-limit" title="IETF numbered="true" toc="default">
        <name>IETF LLC Board Director Limit"> Limit</name>
        <t>A director may serve no more than two consecutive terms.
A director cannot serve a third term until three years have
passed since their second consecutive term. An
exception is if a Director role is occupied by the IETF Chair ex
officio, since that person’s person's service is governed instead by the term
lengths established in <xref target="I-D.ietf-iasa2-rfc7437bis"/>, Section 3.4.</t> target="RFC8713" section="3.4" sectionFormat="comma" format="default"/>.</t>
        <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 appointed to two terms by the ISOC Board of Trustees
may not immediately be appointed to a third term by the IETF
NomCom. A Director appointed by the IETF LLC itself may only
serve for one term by that appointment method, and any subsequent
terms would have to be via other methods; in any case, the term
limits above apply to that individual.</t>
        <t>Lastly, partial terms of less than three years for the initial appointments to the first full board, Board, for which some Directors will have terms of one or two years, do not count against the term limit.</t>
        <t>The limit on consecutive terms supports the healthy regular introduction of new ideas and energy into the Board and mitigates potential long-term risk of ossification or conflict, without adversely impacting the potential pool of director candidates over time.</t>
      <section anchor="staggered-terms" title="Staggered Terms"> numbered="true" toc="default">
        <name>Staggered Terms</name>
        <t>The Internet Society Board of Trustees, the IESG, the Nominating Committee, and the
IETF LLC Board are expected to coordinate with each other to ensure that
collectively their appointment or selection processes provide for no
more than three Directors’ Directors' terms concluding in the same year.</t>
      <section anchor="director-removal" title="IETF numbered="true" toc="default">
        <name>IETF LLC Board Director Removal"> Removal</name>
        <t>NomCom-appointed and IESG-appointed Directors may be removed with or without cause. A vote in favor of
removal must be no fewer than the number of Directors less two.  So
for example, if there are seven directors, then five votes are
required. Directors may also be removed via the IETF recall process
defined in <xref target="I-D.ietf-iasa2-rfc7437bis"/>, Section 7.</t> target="RFC8713" section="7" sectionFormat="comma" format="default"/>.</t>
      <section anchor="director-vacancy" title="Filling numbered="true" toc="default">
        <name>Filling an IETF LLC Board Director Vacancy"> Vacancy</name>
        <t>It shall be the responsibility of each respective body that appointed or selected a Director that vacates the Board
to appoint a new Director to fill the vacancy.  For example, if a Director selected by the NomCom departs the Board
prior to the end of their term for whatever reason, then it is the responsibility of the NomCom (using its mid-term
rules, as specified in <xref target="I-D.ietf-iasa2-rfc7437bis"/>, Section 3.5) 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 Director.  However, this obligation will
not apply to vacancies in Board-appointed positions.</t>
      <section anchor="quorum" title="Quorum"> numbered="true" toc="default">
        <t>At all meetings of the Board, two-thirds of the Directors then in office shall constitute
a quorum for the transaction of business. Unless a greater affirmative vote is expressly required for
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>
      <section anchor="voting" title="Board Voting"> numbered="true" toc="default">
        <name>Board Voting</name>
        <t>Board decisions may be made either by vote communicated in a meeting
of the Board (including telephonic and video), or via an asynchronous
written (including electronic) process. Absentee voting and voting by
proxy shall not be permitted. 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. Voting thresholds for Director
removal are described in <xref target="director-removal"/>.</t> target="director-removal" format="default"/>.</t>
      <section anchor="interim-board" title="Interim Board"> numbered="true" toc="default">
        <name>Interim Board</name>
        <t>An initial interim Board was necessary in order to legally form and bootstrap the IETF LLC. As a result, an Interim Board was formed on a temporary basis until the first full board Board was constituted.</t>
        <t>The interim Board was comprised of:</t>

<t><list style="symbols">
        <ul spacing="normal">
          <li>The IETF chair, ex officio</t>
  <t>The officio</li>
          <li>The IAOC chair, ex officio</t>
  <t>The officio</li>
          <li>The IAB chair, ex officio</t>
  <t>One officio</li>
          <li>One ISOC trustee, selected by the ISOC Board of Trustees</t>
</list></t> Trustees</li>
      <section anchor="board-positions" title="Board Positions"> numbered="true" toc="default">
        <name>Board Positions</name>
        <t>Following the formation of the first permanent Board, and annually thereafter, the Directors shall
elect a Director to serve as Board Chair by majority vote. The IETF, IAB IAB, and IRTF chairs, and the
chair of ISOC’s ISOC's Board, will be ineligible for this Board Chair role. The Board may also form committees
of the Board and/or define other roles for Board Directors as necessary.</t>
    <section anchor="ietf-llc-funding" title="IETF numbered="true" toc="default">
      <name>IETF LLC Funding"> Funding</name>
      <t>The IETF LLC must function within a budget of costs balanced against limited 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
environment within which the work of the IETF, IAB, IRTF, and RFC Editor can remain vibrant and productive.</t>
      <t>The IETF LLC was generating income from a few key sources at the time that this document was written, as enumerated below. Additional sources of income may be developed in the future, within the general bounds noted in <xref target="fundraising-practices"/>, target="fundraising-practices" format="default"/>, and some of these may decline in relevance or go away. As a result result, this list is subject to change over time and is merely an example of the primary sources of income for the IETF LLC at the time of this writing:</t>

<t><list style="numbers">
  <t>ISOC support</t>
      <ol spacing="normal" type="1">
        <li>ISOC support</li>
        <li>IETF meeting revenues</t>
  <t>Sponsorships revenues</li>
        <li>Sponsorships (monetary and/or in-kind)</t>
  <t>Donations in-kind)</li>
        <li>Donations (monetary and/or in-kind)</t>
</list></t> in-kind)</li>
      <section anchor="financial-statements" title="Financial Statements"> numbered="true" toc="default">
        <name>Financial Statements</name>
        <t>As noted in <xref target="board-responsibilities"/>, target="board-responsibilities" format="default"/>, 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>
        <t>In addition to these official financial statements and forms, the IETF LLC is 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
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, expenses, assets, and liabilities of the
      <section anchor="bank-and-investment-accounts" title="Bank numbered="true" toc="default">
        <name>Bank and Investment Accounts"> Accounts</name>
        <t>The IETF LLC maintains its own bank account, separate and distinct from ISOC. The IETF LLC
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>
      <section anchor="financial-audits" title="Financial Audits"> numbered="true" toc="default">
        <name>Financial Audits</name>
        <t>The IETF LLC is expected to retain and work with an independent auditor. Reports from the auditor are expected to be shared with the IETF community and other groups and organizations as needed or as required by law.</t>
      <section anchor="isoc-financial-support" title="ISOC numbered="true" toc="default">
        <name>ISOC Financial Support"> Support</name>
        <t>ISOC currently provides significant financial support to the IETF LLC. Exhibit B of the <xref target="IETF-LLC-A"/> target="IETF-LLC-A" format="default"/>
summarizes the financial support from ISOC for the foreseeable future. It is expected that this support
will be periodically reviewed and revised, via a cooperative assessment process between ISOC and
the IETF LLC.</t>
      <section anchor="ietf-meeting-revenues" title="IETF numbered="true" toc="default">
        <name>IETF Meeting Revenues"> Revenues</name>
        <t>Meeting revenues are another important source of funding that supports the IETF, coming mainly from the fees paid
by IETF meeting participants. The IETF Executive Director sets those meeting fees, in consultation with other IETF
LLC staff and the IETF community, with approval by the IETF LLC Board. Setting these fees and projecting the number
of participants at future meetings is a key part of the annual budget process.</t>
      <section anchor="sponsorships-and-donations-to-the-ietf-llc" title="Sponsorships numbered="true" toc="default">
        <name>Sponsorships and Donations to the IETF LLC"> LLC</name>
        <t>Sponsorships and donations are an essential component of the financial support for the IETF. Within the general
bounds noted in <xref target="fundraising-practices"/>, target="fundraising-practices" format="default"/>, the IETF LLC is responsible for fundraising activities in order
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 equipment, software licenses, and services.</t>
        <t>Sponsorships and donations to the IETF LLC do not (and must not) convey to sponsors and donors any special oversight
or direct influence over the IETF’s IETF's technical work or other activities of the IETF or IETF LLC. This helps
ensure that no undue influence may be ascribed to those from whom funds are raised, and so helps to maintain
an open and consensus-based IETF standards process.</t>
        <t>To the extent that the IETF LLC needs to undertake any significant special projects for the IETF, the IETF LLC
may need to fundraise distinctly for those special projects. As a result, the IETF LLC may conduct fundraising to support
the IETF in general as well as one or more special fundraising efforts (which may also be accounted for distinctly and be held in a separate bank account or investment, as needed).</t>
      <section anchor="focus-of-funding-support" title="Focus numbered="true" toc="default">
        <name>Focus of Funding Support"> Support</name>
        <t>The IETF LLC exists to support the IETF, IAB, and IRTF.  Therefore, the IETF LLC’s LLC's funding and all revenues,
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>
      <section anchor="fundraising-practices" title="Charitable numbered="true" toc="default">
        <name>Charitable Fundraising Practices"> Practices</name>
        <t>When the IETF LLC conducts fundraising, it substantiates charitable
contributions on behalf of ISOC  -- meaning that according to US United States tax
law, the IETF LLC must send a written acknowledgment of contributions
to donors. The IETF LLC evaluates and facilitates state, federal, and
other applicable law and regulatory compliance for ISOC and/or the LLC
with respect to such fundraising activities. In addition, the IETF LLC
ensures that all fundraising activities are conducted in compliance
with any policies developed by the IETF LLC, including but not limited
to those noted in <xref target="llc-policies"/>.</t> target="llc-policies" format="default"/>.</t>
      <section anchor="operating-reserve" title="Operating Reserve"> numbered="true" toc="default">
        <name>Operating Reserve</name>
        <t>An initial target operating reserve has been specified in Exhibit B of the <xref target="IETF-LLC-A"/>.  That target="IETF-LLC-A" format="default"/>.  It says that the IETF LLC
should maintain an operating reserve equal to the IETF LLC’s LLC's budgeted Net Loss for 2019 multiplied times three. The IETF
LLC, in cooperation with ISOC, may regularly review the financial target for this reserve fund, as noted in the <xref target="IETF-LLC-A"/> target="IETF-LLC-A" format="default"/> or as otherwise necessary.</t>
        <t>Should the IETF LLC generate an annual budget surplus, it may choose to direct all or part of the surplus towards
the growth of the operating reserve.</t>
      <section anchor="annual-budget-process" title="Annual numbered="true" toc="default">
        <name>Annual Budget Process"> Process</name>
        <t>As noted in <xref target="llc-responsibilities"/>, target="llc-responsibilities" format="default"/>, the IETF LLC is responsible for managing the IETF’s IETF's finances and budget.
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 IETF's technical activities and establishes trust
with ISOC, sponsors, and donors that funds are being appropriately spent, and that financial oversight is being conducted
properly. This is also essential to the IETF LLC meeting applicable legal and tax requirements and is a core part of
the Board’s Board's fiduciary responsibilities.</t>
        <t>As explained in <xref target="staff-responsibilities"/>, target="staff-responsibilities" format="default"/>, the IETF Executive Director is expected to develop, execute, and report on the
annual budget. Regular reporting is expected to include forecast vs. budget statements, including updated projections of income and expenses for the full fiscal year.</t>
        <t>The Board, as explained in <xref target="board-responsibilities"/>, target="board-responsibilities" format="default"/>, is expected to review and approve the
budget, as well as to provide ongoing oversight of the budget and of any other significant financial matters.</t>
        <t>The annual budget is expected to be developed in an open, transparent, and collaborative manner, in accordance with
<xref target="principles"/>. target="principles" format="default"/>. The specific timeline for the development, review, and approval of the IETF LLC annual budget is established by the Board and may be revised as needed.</t>
    <section anchor="llc-policies" title="IETF numbered="true" toc="default">
      <name>IETF LLC Policies"> Policies</name>
      <t>The Board is expected to maintain policies as necessary to achieve the
goals of the IETF LLC, meet transparency expectations of the
community, comply with applicable laws or regulations, or for other
reasons as appropriate. All policies are expected to be developed with
input from the IETF community. Some policies provided by ISOC and
past policies developed by the previous IAOC may
provide a useful starting point for the Board to consider.</t>
      <section anchor="conflict-of-interest" title="Conflict numbered="true" toc="default">
        <name>Conflict of Interest Policy"> Policy</name>
        <t>The Board is expected to maintain a Conflict of Interest policy for the IETF LLC. While the details are determined by the Board, at a minimum such policy is expected to include the following:</t>

<t><list style="symbols">
        <ul spacing="normal">
          <li>The IETF, ISOC Board, IAB, or IRTF chair cannot be chair of the IETF LLC Board, though they may serve as a Director.</t>
  <t>A Director.</li>
          <li>A Director cannot be a paid consultant or employee of the IETF Executive Director or their sub-contractors, nor a paid consultant or employee of ISOC.</t>
</list></t> ISOC.</li>
      <section anchor="other-policies" title="Other Policies"> numbered="true" toc="default">
        <name>Other Policies</name>
        <t>The Board is expected to maintain additional policies for the IETF LLC as necessary, covering Directors, employees, and contractors, concerning issues such as:</t>

<t><list style="symbols">
        <ul spacing="normal">
          <li>Acceptance of gifts and other non-cash compensation;</t>
  <t>Travel compensation</li>
          <li>Travel and expense reimbursement;</t>
  <t>Code of conduct;</t>
  <t>Document retention;</t>
  <t>Export controls;</t>
  <t>Anti-terrorism sanctions;</t>
  <t>Data reimbursement</li>
          <li>Code of conduct</li>
          <li>Document retention</li>
          <li>Export controls</li>
          <li>Anti-terrorism sanctions</li>
          <li>Data protection and privacy;</t>
  <t>Social media</t>
</list></t> privacy</li>
          <li>Social media</li>
      <section anchor="compliance" title="Compliance"> numbered="true" toc="default">
        <t>The IETF LLC is expected to implement a compliance program to ensure its compliance with all applicable laws, rules rules, and regulations, including without limitation laws governing bribery, anti-terrorism sanctions, export controls, data protection/privacy, as well as other applicable policies noted in <xref target="llc-policies"/>. target="llc-policies" format="default"/>. In addition, actions and activities of the IETF LLC must be consistent with 501(c)(3) purposes.</t>
        <t>The IETF LLC is expected to report to ISOC and the IETF community on the implementation of its compliance plan on an annual basis.</t>
    <section anchor="three-year-assessment" title="Three-Year Assessment"> numbered="true" toc="default">
      <name>Three-Year Assessment</name>
      <t>The IETF LLC, with the involvement of the community, shall conduct
      and complete an assessment of the structure, processes, and operation of
      IASA 2.0 and the IETF LLC. This should be presented to the community
      after a period of roughly three years of operation. The assessment may
      potentially include recommendations for improvements or changes to the IASA2
      IASA 2.0 and/or IETF LLC.</t>
    <section anchor="security-considerations" title="Security Considerations"> numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>This document describes the structure of the IETF’s Administrative
Support Activity (IASA), version 2 (IASA2). IASA 2.0.  It introduces no security considerations
for the Internet.</t>
    <section anchor="iana-considerations" title="IANA Considerations"> numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This document has no IANA considerations in the traditional sense.
However, some of the information in this document may affect how the
IETF standards process interfaces with the IANA, so the IANA may be
interested in the contents.</t>
<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 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>


    <references title='Normative References'>
    <displayreference target="I-D.haberman-iasa20dt-recs" to="IASA2RECS"/>
        <name>Normative References</name>
        <!-- draft-ietf-iasa2-rfc2031bis [RFC8712] -->
        <reference anchor="I-D.ietf-iasa2-rfc2031bis"> anchor="RFC8712" target="https://www.rfc-editor.org/info/rfc8712">
            <title>The IETF-ISOC Relationship</title>
            <author initials='G' surname='Camarillo' fullname='Gonzalo Camarillo'>
    <organization /> initials="G" surname="Camarillo" fullname="Gonzalo Camarillo">
           <author initials='J' surname='Livingood' fullname='Jason Livingood'>
    <organization /> initials="J" surname="Livingood" fullname="Jason Livingood">
           <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 structure of the IETF Administrative Support Activity (IASA) in 2018.  The IASA was revised under a new "IASA 2.0" structure by the IASA2 Working Group, which changed the IETF's administrative, legal, and financial structure.  As a result, it also changed the relationship between the IETF and ISOC, which made it necessary to revise RFC 2031.</t></abstract> month="February" year="2020"/>
          <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' /> name="RFC" value="8712"/>
          <seriesInfo name="DOI" value="10.17487/RFC8712"/>
        <!-- draft-ietf-iasa2-rfc7437bis [RFC8713] -->
        <reference anchor="I-D.ietf-iasa2-rfc7437bis"> anchor="RFC8713" target="https://rfc-editor.org/info/rfc8713">
            <title>IAB, IESG, IETF Trust Trust, and IETF LLC Selection,
	    Confirmation, and Recall Process: Operation of the IETF Nominating
	    and Recall Committees</title>
            <author initials='M' surname='Kucherawy' fullname='Murray Kucherawy'>
    <organization /> initials="M." surname="Kucherawy" role="editor">
            <author initials='R' surname='Hinden' fullname='Robert Hinden'>
    <organization /> initials="R." surname="Hinden" role="editor">
            <author initials='J' surname='Livingood' fullname='Jason Livingood'>
    <organization /> initials="J." surname="Livingood" role="editor">
            <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.  This document obsoletes RFC7437 and RFC8318.</t></abstract> month="February" year="2020"/>
          <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' /> name="BCP" value="10"/>
          <seriesInfo name="RFC" value="8713"/>
          <seriesInfo name="DOI" value="10.17487/RFC8713"/>
        <reference anchor="IETF-LLC-A" target="https://www.ietf.org/documents/180/IETF-LLC-Agreement.pdf">
            <title>Limited Liability Company Agreement of IETF Administration LLC</title>
    <author >
      <organization>The Internet Society</organization>
            <date year="2018" month="August"/>

    <references title='Informative References'>
        <name>Informative References</name>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7691.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2026.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2014.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2850.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4071.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3710.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3233.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4333.xml"/>

        <!-- draft-ietf-mtgvenue-iaoc-venue-selection-process-16 RFC 8718 -->
        <reference  anchor="RFC7691" target='https://www.rfc-editor.org/info/rfc7691'> anchor="RFC8718" target="https://rfc-editor.org/info/rfc8718">
<title>Updating the Term Dates of IETF Administrative Oversight Committee (IAOC) Members</title>
            <title>IETF Plenary Meeting Venue Selection Process</title>
            <author initials='S.' surname='Bradner' fullname='S. Bradner' role='editor'><organization /></author> initials="E." surname="Lear" role="editor">
            <date year='2015' month='November' />
<abstract><t>BCP 101 defines the start and end dates for the terms of IETF Administrative Oversight Committee (IAOC) members; these terms have proven to be impractical.  This memo updates BCP 101 to direct the IAOC to establish more practical start and end dates for terms of IAOC members.</t></abstract> month="February" year="2020"/>
          <seriesInfo name='BCP' value='101'/> name="BCP" value="226"/>
          <seriesInfo name='RFC' value='7691'/> name="RFC" value="8718"/>
          <seriesInfo name='DOI' value='10.17487/RFC7691'/> name="DOI" value="10.17487/RFC8718"/>

        <!-- draft-haberman-iasa20dt-recs-03 expired 05/31/19 -->
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.draft-haberman-iasa20dt-recs-03.xml"/>

        <!-- draft-ietf-iasa2-trust-update-03 RFC 8714 -->
        <reference  anchor="RFC2026" target='https://www.rfc-editor.org/info/rfc2026'> anchor="RFC8714" target="https://rfc-editor.org/info/rfc8714">
<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 standardization process,
            <title>Update to the requirements Process for moving a document between stages and the types Selection of documents used during this process. This document specifies an Internet Best Current Practices Trustees for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
	    IETF Trust</title>
            <author initials="J." surname="Arkko">
            <author initials="T." surname="Hardie">
            <date month="February" year="2020"/>
          <seriesInfo name='BCP' value='9'/> name="BCP" value="101"/>
          <seriesInfo name='RFC' value='2026'/> name="RFC" value="8714"/>
          <seriesInfo name='DOI' value='10.17487/RFC2026'/> name="DOI" value="10.17487/RFC8714"/>

        <reference  anchor="RFC2014" target='https://www.rfc-editor.org/info/rfc2014'> anchor="ISOC" target="https://www.internetsociety.org/about-internet-society/governance-policies/by-laws/">
<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 /></author>
<date year='1996' month='October' />
<abstract><t>This document describes the guidelines and procedures for formation
            <title>Amended and operation restated By-Laws of IRTF Research Groups.  It describes the relationship between IRTF participants, Research Groups, the Internet Research Steering Group (IRSG) and the Internet Architecture Board (IAB).  This document specifies an Internet Best Current Practices for the Society</title>
              <organization>The Internet Community, and requests discussion and suggestions for improvements.</t></abstract> Society</organization>
            <date year="2019" month="October"/>
<seriesInfo name='BCP' value='8'/>
<seriesInfo name='RFC' value='2014'/>
<seriesInfo name='DOI' value='10.17487/RFC2014'/>

<reference  anchor="RFC2850" target='https://www.rfc-editor.org/info/rfc2850'>
<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,
    <section anchor="acknowledgments" numbered="false" toc="default">
      <t>Thanks to <contact fullname="Jari Arkko"/>, <contact
      fullname="Richard Barnes"/>, <contact fullname="Brian E. Carpenter"/>, <contact
      fullname="Alissa Cooper"/>, <contact fullname="John C. Klensin"/>, <contact fullname="Bob Hinden"/>,
<contact fullname="Jon Peterson"/>, <contact fullname="Sean Turner"/>, and organization of the Internet Architecture Board.  It replaces RFC 1601.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions
IASA2 Working Group for improvements.</t></abstract>
<seriesInfo name='BCP' value='39'/>
<seriesInfo name='RFC' value='2850'/>
<seriesInfo name='DOI' value='10.17487/RFC2850'/>

<reference  anchor="RFC4071" target='https://www.rfc-editor.org/info/rfc4071'>
<title>Structure of the IETF Administrative Support Activity (IASA)</title>
<author initials='R.' surname='Austein' fullname='R. Austein' role='editor'><organization /></author>
<author initials='B.' surname='Wijnen' fullname='B. Wijnen' role='editor'><organization /></author>
<date year='2005' month='April' />
<abstract><t>This document describes the structure of the IETF Administrative Support Activity (IASA) as an activity housed within the Internet Society (ISOC).  It defines the roles and responsibilities discussions of the IETF Administrative Oversight Committee (IAOC), the IETF Administrative Director (IAD), possible structures, and ISOC in to the fiscal and administrative support
attorneys of the IETF standards process.  It also defines the membership and selection rules <contact fullname="Morgan Lewis"/> and <contact fullname="Brad Biddle"/> for the IAOC.  This legal advice.</t>
      <t>Coauthor Hall performed work on this document specifies an Internet Best Current Practices for before employment at the Internet Community, and requests discussion Society, and suggestions for improvements.</t></abstract>
<seriesInfo name='BCP' value='101'/>
<seriesInfo name='RFC' value='4071'/>
<seriesInfo name='DOI' value='10.17487/RFC4071'/>

<reference  anchor="RFC3710" target='https://www.rfc-editor.org/info/rfc3710'>
<title>An IESG charter</title>
<author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'><organization /></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 his affiliation listed in this document the charter of the IESG as it is presently understood.  This memo provides information for the Internet community.</t></abstract>
<seriesInfo name='RFC' value='3710'/>
<seriesInfo name='DOI' value='10.17487/RFC3710'/>

<reference  anchor="RFC3233" target='https://www.rfc-editor.org/info/rfc3233'>
<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 &quot;the IETF&quot; as it understood today.  Many RFCs refer to &quot;the IETF&quot;.  Many important 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 specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
<seriesInfo name='BCP' value='58'/>
<seriesInfo name='RFC' value='3233'/>
<seriesInfo name='DOI' value='10.17487/RFC3233'/>

<reference  anchor="RFC4333" target='https://www.rfc-editor.org/info/rfc4333'>
<title>The IETF Administrative Oversight Committee (IAOC) Member Selection Guidelines and Process</title>
<author initials='G.' surname='Huston' fullname='G. Huston' role='editor'><organization /></author>
<author initials='B.' surname='Wijnen' fullname='B. Wijnen' role='editor'><organization /></author>
<date year='2005' month='December' />
<abstract><t>This memo outlines the guidelines for selection of members of the IETF Administrative Oversight Committee, and describes the selection process used by the IAB and the IESG.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
<seriesInfo name='BCP' value='113'/>
<seriesInfo name='RFC' value='4333'/>
<seriesInfo name='DOI' value='10.17487/RFC4333'/>

<reference anchor="I-D.ietf-mtgvenue-iaoc-venue-selection-process">
<title>IETF Plenary Meeting Venue Selection Process</title>

<author initials='E' surname='Lear' fullname='Eliot Lear'>
    <organization />

<date month='June' day='14' year='2018' />

<abstract><t>The IASA has responsibility for arranging IETF plenary meeting Venue 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 selection process.</t></abstract>


<seriesInfo name='Internet-Draft' value='draft-ietf-mtgvenue-iaoc-venue-selection-process-16' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-mtgvenue-iaoc-venue-selection-process-16.txt' />

<reference anchor="I-D.haberman-iasa20dt-recs">
<title>IASA 2.0 Design Team Recommendations</title>

<author initials='B' surname='Haberman' fullname='Brian Haberman'>
    <organization />

<author initials='J' surname='Arkko' fullname='Jari Arkko'>
    <organization />

<author initials='L' surname='Daigle' fullname='Leslie Daigle'>
    <organization />

<author initials='J' surname='Livingood' fullname='Jason Livingood'>
    <organization />

<author initials='J' surname='Hall' fullname='Joseph Hall'>
    <organization />

<author initials='E' surname='Rescorla' fullname='Eric Rescorla'>
    <organization />

<date month='November' day='27' year='2018' />

<abstract><t>The arrangements relating to administrative support for the IETF were created more than ten years ago.  Since then, there has been considerable change 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 structure, organization, personnel, and transparency.  This document is a product of a design team, focused on providing additional information to the community about solution options, as well as supporting analysis of the implications of those options. This document reflects the final snapshot of the design team discussion and is published for historical posterity.</t></abstract>


<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 anchor="I-D.ietf-iasa2-trust-update">
<title>Update to the Process for Selection of Trustees for the IETF Trust</title>

<author initials='J' surname='Arkko' fullname='Jari Arkko'>
    <organization />

<author initials='T' surname='Hardie' fullname='Ted Hardie'>
    <organization />

<date month='February' day='4' year='2019' />

<abstract><t>This memo updates the process for selection of trustees for the IETF Trust.  Previously, the Internet Administrative Oversight Committee (IAOC) members also acted as trustees, but the IAOC has been eliminated as part of an update of the structure of the Internet Administrative Support Activity (IASA).  This memo specifies that the trustees shall be selected separately.  This memo obsoletes RFC 4371.  The changes relate only to the selection of trustees.  All other aspects of the IETF Trust remain as they are today.</t></abstract>


<seriesInfo name='Internet-Draft' value='draft-ietf-iasa2-trust-update-03' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-iasa2-trust-update-03.txt' />

<reference anchor="ISOC" target="https://www.internetsociety.org/about-internet-society/governance-policies/by-laws/">
    <title>Amended and restated By-Laws of the Internet Society</title>
    <author >
      <organization>The Internet Society</organization>
    <date year="2018" month="July"/>

    </references> identification purposes only.</t>

<!-- ##markdown-source: