Diff: rfc8711xml2.original.xml

	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" ?>	<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="bcp" conse
	<!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.2.8 -->	nsus="true" docName="draft-ietf-iasa2-rfc4071bis-11" indexInclude="true" ipr="tr
		ust200902" number="8711" obsoletes="4071, 4333, 7691" prepTime="2020-02-26T16:42
	<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [	:42" scripts="Common,Latin" sortRefs="true" submissionType="IETF" symRefs="true"
	]>	tocDepth="3" tocInclude="true" xml:lang="en">
		<link href="https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc4071bis-11" r
	<?rfc toc="yes"?>	el="prev"/>
	<?rfc sortrefs="yes"?>	<link href="https://dx.doi.org/10.17487/rfc8711" rel="alternate"/>
	<?rfc symrefs="yes"?>	<link href="urn:issn:2070-1721" rel="alternate"/>

	<rfc ipr="trust200902" docName="draft-ietf-iasa2-rfc4071bis-11" category="bcp" o
	bsoletes="4071, 4333, 7691">

	<front>	<front>

	<title abbrev="IASA2">Structure of the IETF Administrative Support Activity,	<title abbrev="IASA 2.0">Structure of the IETF Administrative Support Activi
	Version 2.0</title>	ty, Version 2.0</title>
		<seriesInfo name="RFC" value="8711" stream="IETF"/>
		<seriesInfo name="BCP" value="101" stream="IETF"/>
	<author initials="B." surname="Haberman" fullname="Brian Haberman">	<author initials="B." surname="Haberman" fullname="Brian Haberman">

	<organization>Johns Hopkins University</organization>	<organization showOnFrontPage="true">Johns Hopkins University</organizatio n>
	<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 showOnFrontPage="true">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 showOnFrontPage="true">Comcast</organization>
	<address>	<address>
	<email>jason_livingood@comcast.com</email>	<email>jason_livingood@comcast.com</email>
	</address>	</address>
	</author>	</author>

		<date month="02" year="2020"/>
	<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>
		<abstract pn="section-abstract">
	<abstract>	<t pn="section-abstract-1">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 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 pn="section-abstract-2">This document obsoletes RFC 4071, RFC 4333, and
	<t>This document obsoletes RFC 4071, RFC 4333, and RFC 7691.</t>	RFC 7691.</t>

	</abstract>	</abstract>

		<boilerplate>
		<section anchor="status-of-memo" numbered="false" removeInRFC="false" toc=
		"exclude" pn="section-boilerplate.1">
		<name slugifiedName="name-status-of-this-memo">Status of This Memo</name
		>
		<t pn="section-boilerplate.1-1">
		This memo documents an Internet Best Current Practice.
		</t>
		<t pn="section-boilerplate.1-2">
		This document is a product of the Internet Engineering Task Force
		(IETF). It represents the consensus of the IETF community. It has
		received public review and has been approved for publication by
		the Internet Engineering Steering Group (IESG). Further information
		on BCPs is available in Section 2 of RFC 7841.
		</t>
		<t pn="section-boilerplate.1-3">
		Information about the current status of this document, any
		errata, and how to provide feedback on it may be obtained at
		<eref target="https://www.rfc-editor.org/info/rfc8711" brackets="non
		e"/>.
		</t>
		</section>
		<section anchor="copyright" numbered="false" removeInRFC="false" toc="excl
		ude" pn="section-boilerplate.2">
		<name slugifiedName="name-copyright-notice">Copyright Notice</name>
		<t pn="section-boilerplate.2-1">
		Copyright (c) 2020 IETF Trust and the persons identified as the
		document authors. All rights reserved.
		</t>
		<t pn="section-boilerplate.2-2">
		This document is subject to BCP 78 and the IETF Trust's Legal
		Provisions Relating to IETF Documents
		(<eref target="https://trustee.ietf.org/license-info" brackets="none
		"/>) in effect on the date of
		publication of this document. Please review these documents
		carefully, as they describe your rights and restrictions with
		respect to this document. Code Components extracted from this
		document must include Simplified BSD License text as described in
		Section 4.e of the Trust Legal Provisions and are provided without
		warranty as described in the Simplified BSD License.
		</t>
		</section>
		</boilerplate>
		<toc>
		<section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" p
		n="section-toc.1">
		<name slugifiedName="name-table-of-contents">Table of Contents</name>
		<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-to
		c.1-1">
		<li pn="section-toc.1-1.1">
		<t keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent
		="1" format="counter" sectionFormat="of" target="section-1"/>. <xref derivedCon
		tent="" format="title" sectionFormat="of" target="name-introduction">Introductio
		n</xref></t>
		</li>
		<li pn="section-toc.1-1.2">
		<t keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent
		="2" format="counter" sectionFormat="of" target="section-2"/>. <xref derivedCon
		tent="" format="title" sectionFormat="of" target="name-scope-limitation">Scope L
		imitation</xref></t>
		</li>
		<li pn="section-toc.1-1.3">
		<t keepWithNext="true" pn="section-toc.1-1.3.1"><xref derivedContent
		="3" format="counter" sectionFormat="of" target="section-3"/>. <xref derivedCon
		tent="" format="title" sectionFormat="of" target="name-llc-agreement-with-the-in
		te">LLC Agreement with the Internet Society</xref></t>
		</li>
		<li pn="section-toc.1-1.4">
		<t keepWithNext="true" pn="section-toc.1-1.4.1"><xref derivedContent
		="4" format="counter" sectionFormat="of" target="section-4"/>. <xref derivedCon
		tent="" format="title" sectionFormat="of" target="name-definitions-and-principle
		s">Definitions and Principles</xref></t>
		<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
		n-toc.1-1.4.2">
		<li pn="section-toc.1-1.4.2.1">
		<t keepWithNext="true" pn="section-toc.1-1.4.2.1.1"><xref derive
		dContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-terminology">
		Terminology</xref></t>
		</li>
		<li pn="section-toc.1-1.4.2.2">
		<t keepWithNext="true" pn="section-toc.1-1.4.2.2.1"><xref derive
		dContent="4.2" format="counter" sectionFormat="of" target="section-4.2"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-key-differenc
		es-from-the-ol">Key Differences from the Old IASA Structure to IASA 2.0</xref></
		t>
		</li>
		<li pn="section-toc.1-1.4.2.3">
		<t keepWithNext="true" pn="section-toc.1-1.4.2.3.1"><xref derive
		dContent="4.3" format="counter" sectionFormat="of" target="section-4.3"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-general-ietf-
		llc-responsibi">General IETF LLC Responsibilities</xref></t>
		</li>
		<li pn="section-toc.1-1.4.2.4">
		<t keepWithNext="true" pn="section-toc.1-1.4.2.4.1"><xref derive
		dContent="4.4" format="counter" sectionFormat="of" target="section-4.4"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-ietf-llc-work
		ing-principles">IETF LLC Working Principles</xref></t>
		</li>
		<li pn="section-toc.1-1.4.2.5">
		<t keepWithNext="true" pn="section-toc.1-1.4.2.5.1"><xref derive
		dContent="4.5" format="counter" sectionFormat="of" target="section-4.5"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-principles-of
		-the-ietf-and-">Principles of the IETF and ISOC Relationship</xref></t>
		</li>
		<li pn="section-toc.1-1.4.2.6">
		<t keepWithNext="true" pn="section-toc.1-1.4.2.6.1"><xref derive
		dContent="4.6" format="counter" sectionFormat="of" target="section-4.6"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-relationship-
		of-the-ietf-ll">Relationship of the IETF LLC Board to the IETF Leadership</xref>
		</t>
		</li>
		<li pn="section-toc.1-1.4.2.7">
		<t keepWithNext="true" pn="section-toc.1-1.4.2.7.1"><xref derive
		dContent="4.7" format="counter" sectionFormat="of" target="section-4.7"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-review-of-iet
		f-executive-di">Review of IETF Executive Director and IETF LLC Board Decisions</
		xref></t>
		</li>
		<li pn="section-toc.1-1.4.2.8">
		<t keepWithNext="true" pn="section-toc.1-1.4.2.8.1"><xref derive
		dContent="4.8" format="counter" sectionFormat="of" target="section-4.8"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-termination-a
		nd-change">Termination and Change</xref></t>
		</li>
		</ul>
		</li>
		<li pn="section-toc.1-1.5">
		<t keepWithNext="true" pn="section-toc.1-1.5.1"><xref derivedContent
		="5" format="counter" sectionFormat="of" target="section-5"/>. <xref derivedCon
		tent="" format="title" sectionFormat="of" target="name-structure-of-iasa-20">Str
		ucture of IASA 2.0</xref></t>
		<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
		n-toc.1-1.5.2">
		<li pn="section-toc.1-1.5.2.1">
		<t keepWithNext="true" pn="section-toc.1-1.5.2.1.1"><xref derive
		dContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-ietf-executiv
		e-director-and">IETF Executive Director and Staff Responsibilities</xref></t>
		</li>
		<li pn="section-toc.1-1.5.2.2">
		<t keepWithNext="true" pn="section-toc.1-1.5.2.2.1"><xref derive
		dContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-ietf-llc-boar
		d-responsibili">IETF LLC Board Responsibilities</xref></t>
		</li>
		<li pn="section-toc.1-1.5.2.3">
		<t keepWithNext="true" pn="section-toc.1-1.5.2.3.1"><xref derive
		dContent="5.3" format="counter" sectionFormat="of" target="section-5.3"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-board-design-
		goals">Board Design Goals</xref></t>
		</li>
		</ul>
		</li>
		<li pn="section-toc.1-1.6">
		<t keepWithNext="true" pn="section-toc.1-1.6.1"><xref derivedContent
		="6" format="counter" sectionFormat="of" target="section-6"/>. <xref derivedCon
		tent="" format="title" sectionFormat="of" target="name-ietf-llc-board-membership
		-s">IETF LLC Board Membership, Selection, and Accountability</xref></t>
		<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
		n-toc.1-1.6.2">
		<li pn="section-toc.1-1.6.2.1">
		<t keepWithNext="true" pn="section-toc.1-1.6.2.1.1"><xref derive
		dContent="6.1" format="counter" sectionFormat="of" target="section-6.1"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-board-composi
		tion">Board Composition</xref></t>
		</li>
		<li pn="section-toc.1-1.6.2.2">
		<t keepWithNext="true" pn="section-toc.1-1.6.2.2.1"><xref derive
		dContent="6.2" format="counter" sectionFormat="of" target="section-6.2"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-ietf-llc-appo
		inted-director">IETF LLC-Appointed Directors</xref></t>
		</li>
		<li pn="section-toc.1-1.6.2.3">
		<t keepWithNext="true" pn="section-toc.1-1.6.2.3.1"><xref derive
		dContent="6.3" format="counter" sectionFormat="of" target="section-6.3"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-recruiting-ie
		tf-llc-board-d">Recruiting IETF LLC Board Directors</xref></t>
		</li>
		<li pn="section-toc.1-1.6.2.4">
		<t keepWithNext="true" pn="section-toc.1-1.6.2.4.1"><xref derive
		dContent="6.4" format="counter" sectionFormat="of" target="section-6.4"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-ietf-llc-boar
		d-director-ter">IETF LLC Board Director Term Length</xref></t>
		</li>
		<li pn="section-toc.1-1.6.2.5">
		<t keepWithNext="true" pn="section-toc.1-1.6.2.5.1"><xref derive
		dContent="6.5" format="counter" sectionFormat="of" target="section-6.5"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-ietf-llc-boar
		d-director-lim">IETF LLC Board Director Limit</xref></t>
		</li>
		<li pn="section-toc.1-1.6.2.6">
		<t keepWithNext="true" pn="section-toc.1-1.6.2.6.1"><xref derive
		dContent="6.6" format="counter" sectionFormat="of" target="section-6.6"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-staggered-ter
		ms">Staggered Terms</xref></t>
		</li>
		<li pn="section-toc.1-1.6.2.7">
		<t keepWithNext="true" pn="section-toc.1-1.6.2.7.1"><xref derive
		dContent="6.7" format="counter" sectionFormat="of" target="section-6.7"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-ietf-llc-boar
		d-director-rem">IETF LLC Board Director Removal</xref></t>
		</li>
		<li pn="section-toc.1-1.6.2.8">
		<t keepWithNext="true" pn="section-toc.1-1.6.2.8.1"><xref derive
		dContent="6.8" format="counter" sectionFormat="of" target="section-6.8"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-filling-an-ie
		tf-llc-board-d">Filling an IETF LLC Board Director Vacancy</xref></t>
		</li>
		<li pn="section-toc.1-1.6.2.9">
		<t keepWithNext="true" pn="section-toc.1-1.6.2.9.1"><xref derive
		dContent="6.9" format="counter" sectionFormat="of" target="section-6.9"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-quorum">Quoru
		m</xref></t>
		</li>
		<li pn="section-toc.1-1.6.2.10">
		<t keepWithNext="true" pn="section-toc.1-1.6.2.10.1"><xref deriv
		edContent="6.10" format="counter" sectionFormat="of" target="section-6.10"/>. <x
		ref derivedContent="" format="title" sectionFormat="of" target="name-board-votin
		g">Board Voting</xref></t>
		</li>
		<li pn="section-toc.1-1.6.2.11">
		<t keepWithNext="true" pn="section-toc.1-1.6.2.11.1"><xref deriv
		edContent="6.11" format="counter" sectionFormat="of" target="section-6.11"/>. <x
		ref derivedContent="" format="title" sectionFormat="of" target="name-interim-boa
		rd">Interim Board</xref></t>
		</li>
		<li pn="section-toc.1-1.6.2.12">
		<t keepWithNext="true" pn="section-toc.1-1.6.2.12.1"><xref deriv
		edContent="6.12" format="counter" sectionFormat="of" target="section-6.12"/>. <x
		ref derivedContent="" format="title" sectionFormat="of" target="name-board-posit
		ions">Board Positions</xref></t>
		</li>
		</ul>
		</li>
		<li pn="section-toc.1-1.7">
		<t keepWithNext="true" pn="section-toc.1-1.7.1"><xref derivedContent
		="7" format="counter" sectionFormat="of" target="section-7"/>. <xref derivedCon
		tent="" format="title" sectionFormat="of" target="name-ietf-llc-funding">IETF LL
		C Funding</xref></t>
		<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
		n-toc.1-1.7.2">
		<li pn="section-toc.1-1.7.2.1">
		<t keepWithNext="true" pn="section-toc.1-1.7.2.1.1"><xref derive
		dContent="7.1" format="counter" sectionFormat="of" target="section-7.1"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-financial-sta
		tements">Financial Statements</xref></t>
		</li>
		<li pn="section-toc.1-1.7.2.2">
		<t keepWithNext="true" pn="section-toc.1-1.7.2.2.1"><xref derive
		dContent="7.2" format="counter" sectionFormat="of" target="section-7.2"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-bank-and-inve
		stment-account">Bank and Investment Accounts</xref></t>
		</li>
		<li pn="section-toc.1-1.7.2.3">
		<t keepWithNext="true" pn="section-toc.1-1.7.2.3.1"><xref derive
		dContent="7.3" format="counter" sectionFormat="of" target="section-7.3"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-financial-aud
		its">Financial Audits</xref></t>
		</li>
		<li pn="section-toc.1-1.7.2.4">
		<t keepWithNext="true" pn="section-toc.1-1.7.2.4.1"><xref derive
		dContent="7.4" format="counter" sectionFormat="of" target="section-7.4"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-isoc-financia
		l-support">ISOC Financial Support</xref></t>
		</li>
		<li pn="section-toc.1-1.7.2.5">
		<t keepWithNext="true" pn="section-toc.1-1.7.2.5.1"><xref derive
		dContent="7.5" format="counter" sectionFormat="of" target="section-7.5"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-ietf-meeting-
		revenues">IETF Meeting Revenues</xref></t>
		</li>
		<li pn="section-toc.1-1.7.2.6">
		<t keepWithNext="true" pn="section-toc.1-1.7.2.6.1"><xref derive
		dContent="7.6" format="counter" sectionFormat="of" target="section-7.6"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-sponsorships-
		and-donations-">Sponsorships and Donations to the IETF LLC</xref></t>
		</li>
		<li pn="section-toc.1-1.7.2.7">
		<t keepWithNext="true" pn="section-toc.1-1.7.2.7.1"><xref derive
		dContent="7.7" format="counter" sectionFormat="of" target="section-7.7"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-focus-of-fund
		ing-support">Focus of Funding Support</xref></t>
		</li>
		<li pn="section-toc.1-1.7.2.8">
		<t keepWithNext="true" pn="section-toc.1-1.7.2.8.1"><xref derive
		dContent="7.8" format="counter" sectionFormat="of" target="section-7.8"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-charitable-fu
		ndraising-prac">Charitable Fundraising Practices</xref></t>
		</li>
		<li pn="section-toc.1-1.7.2.9">
		<t keepWithNext="true" pn="section-toc.1-1.7.2.9.1"><xref derive
		dContent="7.9" format="counter" sectionFormat="of" target="section-7.9"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-operating-res
		erve">Operating Reserve</xref></t>
		</li>
		<li pn="section-toc.1-1.7.2.10">
		<t keepWithNext="true" pn="section-toc.1-1.7.2.10.1"><xref deriv
		edContent="7.10" format="counter" sectionFormat="of" target="section-7.10"/>. <x
		ref derivedContent="" format="title" sectionFormat="of" target="name-annual-budg
		et-process">Annual Budget Process</xref></t>
		</li>
		</ul>
		</li>
		<li pn="section-toc.1-1.8">
		<t keepWithNext="true" pn="section-toc.1-1.8.1"><xref derivedContent
		="8" format="counter" sectionFormat="of" target="section-8"/>. <xref derivedCon
		tent="" format="title" sectionFormat="of" target="name-ietf-llc-policies">IETF L
		LC Policies</xref></t>
		<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
		n-toc.1-1.8.2">
		<li pn="section-toc.1-1.8.2.1">
		<t keepWithNext="true" pn="section-toc.1-1.8.2.1.1"><xref derive
		dContent="8.1" format="counter" sectionFormat="of" target="section-8.1"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-conflict-of-i
		nterest-policy">Conflict of Interest Policy</xref></t>
		</li>
		<li pn="section-toc.1-1.8.2.2">
		<t keepWithNext="true" pn="section-toc.1-1.8.2.2.1"><xref derive
		dContent="8.2" format="counter" sectionFormat="of" target="section-8.2"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-other-policie
		s">Other Policies</xref></t>
		</li>
		<li pn="section-toc.1-1.8.2.3">
		<t keepWithNext="true" pn="section-toc.1-1.8.2.3.1"><xref derive
		dContent="8.3" format="counter" sectionFormat="of" target="section-8.3"/>. <xre
		f derivedContent="" format="title" sectionFormat="of" target="name-compliance">C
		ompliance</xref></t>
		</li>
		</ul>
		</li>
		<li pn="section-toc.1-1.9">
		<t keepWithNext="true" pn="section-toc.1-1.9.1"><xref derivedContent
		="9" format="counter" sectionFormat="of" target="section-9"/>. <xref derivedCon
		tent="" format="title" sectionFormat="of" target="name-three-year-assessment">Th
		ree-Year Assessment</xref></t>
		</li>
		<li pn="section-toc.1-1.10">
		<t keepWithNext="true" pn="section-toc.1-1.10.1"><xref derivedConten
		t="10" format="counter" sectionFormat="of" target="section-10"/>. <xref derivedC
		ontent="" format="title" sectionFormat="of" target="name-security-considerations
		">Security Considerations</xref></t>
		</li>
		<li pn="section-toc.1-1.11">
		<t keepWithNext="true" pn="section-toc.1-1.11.1"><xref derivedConten
		t="11" format="counter" sectionFormat="of" target="section-11"/>. <xref derivedC
		ontent="" format="title" sectionFormat="of" target="name-iana-considerations">IA
		NA Considerations</xref></t>
		</li>
		<li pn="section-toc.1-1.12">
		<t keepWithNext="true" pn="section-toc.1-1.12.1"><xref derivedConten
		t="12" format="counter" sectionFormat="of" target="section-12"/>. <xref derivedC
		ontent="" format="title" sectionFormat="of" target="name-references">References<
		/xref></t>
		<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
		n-toc.1-1.12.2">
		<li pn="section-toc.1-1.12.2.1">
		<t keepWithNext="true" pn="section-toc.1-1.12.2.1.1"><xref deriv
		edContent="12.1" format="counter" sectionFormat="of" target="section-12.1"/>. <
		xref derivedContent="" format="title" sectionFormat="of" target="name-normative-
		references">Normative References</xref></t>
		</li>
		<li pn="section-toc.1-1.12.2.2">
		<t keepWithNext="true" pn="section-toc.1-1.12.2.2.1"><xref deriv
		edContent="12.2" format="counter" sectionFormat="of" target="section-12.2"/>. <
		xref derivedContent="" format="title" sectionFormat="of" target="name-informativ
		e-references">Informative References</xref></t>
		</li>
		</ul>
		</li>
		<li pn="section-toc.1-1.13">
		<t keepWithNext="true" pn="section-toc.1-1.13.1"><xref derivedConten
		t="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derived
		Content="" format="title" sectionFormat="of" target="name-acknowledgments">Ackno
		wledgments</xref></t>
		</li>
		<li pn="section-toc.1-1.14">
		<t keepWithNext="true" pn="section-toc.1-1.14.1"><xref derivedConten
		t="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derived
		Content="" format="title" sectionFormat="of" target="name-authors-addresses">Aut
		hors' Addresses</xref></t>
		</li>
		</ul>
		</section>
		</toc>
	</front>	</front>


	<middle>	<middle>

		<section anchor="introduction" numbered="true" toc="include" removeInRFC="fa
	<section anchor="introduction" title="Introduction">	lse" pn="section-1">
		<name slugifiedName="name-introduction">Introduction</name>
	<t>The IETF Administrative Support Activity (IASA) was originally	<t pn="section-1-1">The IETF Administrative Support Activity (IASA) was or
		iginally
	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 pn="section-1-2">Under IASA 2.0, the work of the IETF's administrative
	<t>Under IASA 2.0, the work of the IETF’s administrative and fundraising	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 pn="section-1-3">The IETF LLC provides the corporate legal home for the
	<t>The IETF LLC provides the corporate legal home for the IETF, the Internet	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.</t>

		<t pn="section-1-4"><xref target="I-D.haberman-iasa20dt-recs" format="defa
	<t><xref target="I-D.haberman-iasa20dt-recs"/> discusses the challenges facing t	ult" sectionFormat="of" derivedContent="IASA2RECS"/> discusses the challenges fa
	he	cing the
	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 pn="section-1-5">Under IASA 2.0, most of the responsibilities that <xre
	<t>Under IASA 2.0, most of the responsibilities that <xref target="RFC4071"/> as	f target="RFC4071" format="default" sectionFormat="of" derivedContent="RFC4071"/
	signed to	> assigned 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 pn="section-1-6">Eliminating the IAOC meant that changes were required
	<t>Eliminating the IAOC meant that changes were required in how	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" sectionFormat="of" derivedContent="RFC87
		14"/>.</t>
	<t>This document obsoletes <xref target="RFC4071"/>, which specified the origina	<t pn="section-1-7">This document obsoletes <xref target="RFC4071" format=
	l IASA,	"default" sectionFormat="of" derivedContent="RFC4071"/>, which specified the ori
	<xref target="RFC4333"/>, which specified the selection guidelines and process f	ginal IASA,
	or IAOC	<xref target="RFC4333" format="default" sectionFormat="of" derivedContent="RFC43
	members and <xref target="RFC7691"/>, which specified terms for IAOC members.</t	33"/>, which specified the selection guidelines and process for IAOC
	>	members, and <xref target="RFC7691" format="default" sectionFormat="of" derivedC
		ontent="RFC7691"/>, which specified terms for IAOC members.</t>
	</section>	</section>
	<section anchor="scope-limitation" title="Scope Limitation">	<section anchor="scope-limitation" numbered="true" toc="include" removeInRFC
		="false" pn="section-2">
	<t>The document does not propose any changes related to the	<name slugifiedName="name-scope-limitation">Scope Limitation</name>
		<t pn="section-2-1">The document does not propose any changes related to t
		he
	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" sect
	t="RFC2850"/>). In addition, no changes are made to the appeals	ionFormat="of" derivedContent="RFC2026"/> and
	chain, the process for making and confirming IETF and IAB appointments (see BCP	BCP 39 <xref target="RFC2850" format="default" sectionFormat="of" derivedContent
	10 <xref target="I-D.ietf-iasa2-rfc7437bis"></xref>),	="RFC2850"/>). In addition, no changes are made 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" sectionFormat="of" derivedContent
	ISOC’s membership in or support of other organizations.</t>	="RFC8713"/>),
		the technical work of the Internet Research Task Force (IRTF) (see <xref target=
	</section>	"RFC2014" format="default" sectionFormat="of" derivedContent="RFC2014"/>), or to
	<section anchor="llc-agreement-with-the-internet-society" title="LLC Agreement w	ISOC's membership in or support of other organizations.</t>
	ith the Internet Society">	</section>
		<section anchor="llc-agreement-with-the-internet-society" numbered="true" to
	<t>The LLC Agreement between the IETF LLC and ISOC is available	c="include" removeInRFC="false" pn="section-3">
	at <xref target="IETF-LLC-A"/>. This IASA2 structure, and thus this document,	<name slugifiedName="name-llc-agreement-with-the-inte">LLC Agreement with
		the Internet Society</name>
		<t pn="section-3-1">The LLC Agreement between the IETF LLC and ISOC is ava
		ilable
		at <xref target="IETF-LLC-A" format="default" sectionFormat="of" derivedContent=
		"IETF-LLC-A"/>. This IASA 2.0 structure, and thus 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 pn="section-3-2">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="include" r
	<section anchor="definitions-and-principles" title="Definitions and Principles">	emoveInRFC="false" pn="section-4">
		<name slugifiedName="name-definitions-and-principles">Definitions and Prin
	<section anchor="terminology" title="Terminology">	ciples</name>
		<section anchor="terminology" numbered="true" toc="include" removeInRFC="f
	<t>Although most of the terms, abbreviations, and acronyms used in this	alse" pn="section-4.1">
		<name slugifiedName="name-terminology">Terminology</name>
		<t pn="section-4.1-1">Although most of the terms, abbreviations, and acr
		onyms 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 newline="false" spacing="normal" pn="section-4.1-2">
	<t>IAB: Internet Architecture Board (see <xref target="RFC2026"/>, <xref target=	<dt pn="section-4.1-2.1">IAB:</dt>
	"RFC2850"/>).</t>	<dd pn="section-4.1-2.2">Internet Architecture Board (see <xref target
		="RFC2026" format="default" sectionFormat="of" derivedContent="RFC2026"/> and <x
	<t>IAD: IETF Administrative Director, a role obsoleted by this document	ref target="RFC2850" format="default" sectionFormat="of" derivedContent="RFC2850
	and the ISOC/IETF LLC Agreement (<xref target="IETF-LLC-A"/>) and replaced by th	"/>).</dd>
	e	<dt pn="section-4.1-2.3">IAD:</dt>
	IETF LLC Executive Director.</t>	<dd pn="section-4.1-2.4">IETF Administrative Director, a role obsolete
		d by this document
	<t>IAOC: IETF Administrative Oversight Committee, a committee that oversaw	and the ISOC / IETF LLC Agreement (see <xref target="IETF-LLC-A" format="default
		" sectionFormat="of" derivedContent="IETF-LLC-A"/>) and replaced by the
		IETF LLC Executive Director.</dd>
		<dt pn="section-4.1-2.5">IAOC:</dt>
		<dd pn="section-4.1-2.6">IETF Administrative Oversight Committee, a co
		mmittee 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" sectionFormat="of" derivedCon
		tent="RFC8714"/>).</dd>
	<t>IASA: The IETF Administrative Support Activity, consists of the IETF	<dt pn="section-4.1-2.7">IASA:</dt>
	LLC board, employees, and contractors. Uses of the term ‘IASA’ as	<dd pn="section-4.1-2.8">The IETF Administrative Support Activity, con
	a proper noun may imply a subset of these roles, or all of them.</t>	sists of the IETF
		LLC Board, employees, and contractors. Uses of the term 'IASA' as
	<t>IASA 2.0: Version 2.0 of the IETF Administrative Support Activity,	a proper noun may imply a subset of these roles, or all of them.</dd>
	defined by this document.</t>	<dt pn="section-4.1-2.9">IASA 2.0:</dt>
		<dd pn="section-4.1-2.10">The IETF Administrative Support Activity,
	<t>IESG: Internet Engineering Steering Group (see <xref target="RFC2026"/>,	version 2.0 (defined by this document).</dd>
	<xref target="RFC3710"/>).</t>	<dt pn="section-4.1-2.11">IESG:</dt>
		<dd pn="section-4.1-2.12">Internet Engineering Steering Group (see <xr
	<t>IETF: Internet Engineering Task Force (see <xref target="RFC3233"/>).</t>	ef target="RFC2026" format="default" sectionFormat="of" derivedContent="RFC2026"
		/> and
	<t>IETF Administration LLC: The legal entity - a disregarded Limited Liability C	<xref target="RFC3710" format="default" sectionFormat="of" derivedContent="RFC37
	ompany	10"/>).</dd>
		<dt pn="section-4.1-2.13">IETF:</dt>
		<dd pn="section-4.1-2.14">Internet Engineering Task Force (see <xref t
		arget="RFC3233" format="default" sectionFormat="of" derivedContent="RFC3233"/>).
		</dd>
		<dt pn="section-4.1-2.15">IETF Administration LLC:</dt>
		<dd pn="section-4.1-2.16">The legal entity - a disregarded Limited Lia
		bility Company
	(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" sectionFormat="of" derivedContent="IETF-LLC-A"/>) and is ref
	to as “IETF LLC.”</t>	erred
		to as "IETF LLC".</dd>
	<t>IETF LLC Executive Director: the Executive Director for the IETF LLC, respons	<dt pn="section-4.1-2.17">IETF LLC Executive Director:</dt>
	ible	<dd pn="section-4.1-2.18">the Executive Director for the IETF LLC, res
	for day-to-day administrative and operational direction (See <xref target="staff	ponsible
	-responsibilities"/>).	for day-to-day administrative and operational direction (see <xref target="staff
	Also referred to as “IETF Executive Director”.</t>	-responsibilities" format="default" sectionFormat="of" derivedContent="Section 5
		.1"/>).
	<t>IETF LLC Board: The Board of Directors of the IETF LLC. The IETF LLC	Also referred to as "IETF Executive Director".</dd>
	Board is formally a multi-member “manager” of the IETF LLC on behalf	<dt pn="section-4.1-2.19">IETF LLC Board:</dt>
	of ISOC (See <xref target="board-responsibilities"/>).</t>	<dd pn="section-4.1-2.20">The Board of Directors of the IETF LLC. The
		IETF LLC
	<t>ISOC: Internet Society (see <xref target="I-D.ietf-iasa2-rfc2031bis"/> and <x	Board is formally a multi-member "manager" of the IETF LLC on behalf
	ref target="ISOC"/>).</t>	of ISOC (see <xref target="board-responsibilities" format="default" sectionForma
		t="of" derivedContent="Section 5.2"/>).</dd>
	</section>	<dt pn="section-4.1-2.21">ISOC:</dt>
	<section anchor="key-differences-from-the-old-iasa-structure-to-iasa-20" title="	<dd pn="section-4.1-2.22">Internet Society (see <xref target="RFC8712"
	Key Differences From the Old IASA Structure to IASA 2.0">	format="default" sectionFormat="of" derivedContent="RFC8712"/> and <xref target
		="ISOC" format="default" sectionFormat="of" derivedContent="ISOC"/>).</dd>
	<t><list style="symbols">	</dl>
	<t>The IAOC and IAD roles defined in RFC 4071 are eliminated.</t>	</section>
	<t>The former ISOC and IAD responsibilities are assigned to a new	<section anchor="key-differences-from-the-old-iasa-structure-to-iasa-20" n
	organization, IETF Administration LLC.</t>	umbered="true" toc="include" removeInRFC="false" pn="section-4.2">
	<t>The Board of Directors of the IETF LLC – formally a multi-member “manager”	<name slugifiedName="name-key-differences-from-the-ol">Key Differences f
	of the IETF LLC on behalf of ISOC – assumes the oversight responsibilities from	rom the Old IASA Structure to IASA 2.0</name>
	the IAOC.</t>	<ul spacing="normal" bare="false" empty="false" pn="section-4.2-1">
	<t>The Board of the IETF LLC is more focused on strategy and oversight than th	<li pn="section-4.2-1.1">The IAOC and IAD roles defined in RFC 4071 ar
	e IAOC was, with the IETF Executive Director and their team in charge of day-to-	e eliminated.</li>
	day operations.</t>	<li pn="section-4.2-1.2">The former ISOC and IAD responsibilities are
	<t>The IAD role is replaced with the IETF Executive Director role.</t>	assigned to a new
	<t>The role that was previously referred to as “IETF Executive	organization, IETF Administration LLC.</li>
	Director” in older documents such as <xref target="RFC2026"/> is now “Managing	<li pn="section-4.2-1.3">The Board of Directors of the IETF LLC -- for
	Director, IETF Secretariat”.</t>	mally a multi-member "manager" of the IETF LLC on behalf of ISOC -- assumes the
	</list></t>	oversight responsibilities from the IAOC.</li>
		<li pn="section-4.2-1.4">The Board of the IETF LLC is more focused on
	</section>	strategy and oversight than the IAOC was, with the IETF Executive Director and t
	<section anchor="llc-responsibilities" title="General IETF LLC Responsibilities"	heir team in charge of day-to-day operations.</li>
	>	<li pn="section-4.2-1.5">The IAD role is replaced with the IETF Execut
		ive Director role.</li>
	<t>The IETF LLC is established to provide administrative support to the IETF. It	<li pn="section-4.2-1.6">The role that was previously referred to as "
	has no authority over the standards development activities of the IETF.</t>	IETF Executive
		Director" in older documents such as <xref target="RFC2026" format="default" sec
	<t>The responsibilities of the IETF LLC are:</t>	tionFormat="of" derivedContent="RFC2026"/> is now "Managing
		Director, IETF Secretariat".</li>
	<t><list style="symbols">	</ul>
	<t>Operations. The IETF LLC is responsible for supporting the ongoing operatio	</section>
	ns of the IETF, including meetings and non-meeting activities.</t>	<section anchor="llc-responsibilities" numbered="true" toc="include" remov
	<t>Finances. The IETF LLC is responsible for managing the IETF’s finances and	eInRFC="false" pn="section-4.3">
	budget.</t>	<name slugifiedName="name-general-ietf-llc-responsibi">General IETF LLC
	<t>Fundraising. The IETF LLC is responsible for raising money on behalf of the	Responsibilities</name>
	IETF.</t>	<t pn="section-4.3-1">The IETF LLC is established to provide administrat
	<t>Compliance. The IETF LLC is responsible for establishing and enforcing poli	ive support to the IETF. It has no authority over the standards development acti
	cies to ensure compliance with applicable laws, regulations, and rules.</t>	vities of the IETF.</t>
	</list></t>	<t pn="section-4.3-2">The responsibilities of the IETF LLC are:</t>
		<ul spacing="normal" bare="false" empty="false" pn="section-4.3-3">
	<t>The manner by which these responsibilities under the IETF LLC are organized	<li pn="section-4.3-3.1">Operations. The IETF LLC is responsible for s
	is intended to address the problems described in Sections 3.1.1.,	upporting the ongoing operations of the IETF, including meetings and non-meeting
	3.1.2, and 3.1.3 of <xref target="I-D.haberman-iasa20dt-recs"/>.	activities.</li>
		<li pn="section-4.3-3.2">Finances. The IETF LLC is responsible for man
		aging the IETF's finances and budget.</li>
		<li pn="section-4.3-3.3">Fundraising. The IETF LLC is responsible for
		raising money on behalf of the IETF.</li>
		<li pn="section-4.3-3.4">Compliance. The IETF LLC is responsible for e
		stablishing and enforcing policies to ensure compliance with applicable laws, re
		gulations, and rules.</li>
		</ul>
		<t pn="section-4.3-4">The manner by which these responsibilities under t
		he IETF LLC are organized
		is intended to address the problems described in Sections
		<xref target="I-D.haberman-iasa20dt-recs" section="3.1.1" sectionFormat="bare" f
		ormat="default" derivedLink="https://tools.ietf.org/html/draft-haberman-iasa20dt
		-recs-03#section-3.1.1" derivedContent="IASA2RECS"/>,
		<xref target="I-D.haberman-iasa20dt-recs" section="3.1.2" sectionFormat="bare" f
		ormat="default" derivedLink="https://tools.ietf.org/html/draft-haberman-iasa20dt
		-recs-03#section-3.1.2" derivedContent="IASA2RECS"/>, and
		<xref target="I-D.haberman-iasa20dt-recs" section="3.1.3" sectionFormat="bare" f
		ormat="default" derivedLink="https://tools.ietf.org/html/draft-haberman-iasa20dt
		-recs-03#section-3.1.3" derivedContent="IASA2RECS"/>
		of <xref target="I-D.haberman-iasa20dt-recs" format="default" sectionFormat="of"
		derivedContent="IASA2RECS"/>.
	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 pn="section-4.3-5">In addition, by having the IETF LLC manage the IET
	<t>In addition, by having the IETF LLC manage the IETF’s finances and conduct th	F's finances and conduct the IETF's fundraising, confusion about who is responsi
	e IETF’s fundraising, confusion about who is responsible for representing the IE	ble for representing the IETF to sponsors and who directs the uses of sponsorshi
	TF to sponsors and who directs the uses of sponsorship funds should have been el	p funds should be eliminated. Finally, having the IETF LLC reside in a defined,
	iminated. Finally, having the IETF LLC reside in a defined, distinct legal entit	distinct legal entity, and taking responsibility for operations, enables the org
	y, and taking responsibility for operations, enables the organization to execute	anization to execute its own contracts without the need for review and approval
	its own contracts without the need for review and approval by ISOC.</t>	by ISOC.</t>
		</section>
	</section>	<section anchor="principles" numbered="true" toc="include" removeInRFC="fa
	<section anchor="principles" title="IETF LLC Working Principles">	lse" pn="section-4.4">
		<name slugifiedName="name-ietf-llc-working-principles">IETF LLC Working
	<t>The IETF LLC is expected to conduct its work according to the following princ	Principles</name>
	iples:</t>	<t pn="section-4.4-1">The IETF LLC is expected to conduct its work accor
		ding to the following principles:</t>
	<t><list style="symbols">	<ul spacing="normal" bare="false" empty="false" pn="section-4.4-2">
	<t>Transparency. The IETF LLC is expected to keep the IETF community informed	<li pn="section-4.4-2.1">Transparency. The IETF LLC is expected to kee
	about its work,	p 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 pn="section-4.4-2.2">Responsiveness to the community. The IETF LLC
	ly with the documented consensus of the IETF community, to be responsive to the	is expected to act consistently with the documented consensus of the IETF commu
	community’s needs, and to adapt its decisions in response to consensus-based com	nity, to be responsive to the community's needs, and to adapt its decisions in r
	munity feedback.</t>	esponse to consensus-based community feedback.</li>
	<t>Diligence. The IETF LLC is expected to act responsibly so as to minimize ri	<li pn="section-4.4-2.3">Diligence. The IETF LLC is expected to act re
	sks to IETF participants and to the future of the IETF as a whole, such as finan	sponsibly so as to minimize risks to IETF participants and to the future of the
	cial risks.</t>	IETF as a whole, such as financial risks.</li>
	<t>Unification: The IETF LLC provides the corporate legal home for the IETF, t	<li pn="section-4.4-2.4">Unification: The IETF LLC provides the corpor
	he Internet	ate legal home for the 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 pn="section-4.4-2.5">Transfer or Dissolution: Consistent with <xre
	ETF LLC subsidiary may be transferred from ISOC to	f target="IETF-LLC-A" format="default" sectionFormat="of" derivedContent="IETF-L
		LC-A"/>, 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 pn="section-4.4-3">The transparency and responsiveness principles are
	<t>The transparency and responsiveness principles are designed to address the co	designed to address 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" forma
	ut the need for improved timeliness of sharing of information and decisions and	t="default" derivedLink="https://tools.ietf.org/html/draft-haberman-iasa20dt-rec
	seeking community comments. The issue of increased transparency was important th	s-03#section-3.3" derivedContent="IASA2RECS"/> about the need for improved timel
	roughout the IASA 2.0 process, with little to no dissent. It was recognized tha	iness of sharing of information and decisions and seeking community comments. Th
	t there will naturally be confidentiality requirements about some aspects of con	e issue of increased transparency was important throughout the IASA 2.0 process,
	tracting, personnel matters, and other narrow areas.</t>	with little to no dissent. It was recognized that there will naturally be conf
		identiality requirements about some aspects of contracting, personnel matters, a
	</section>	nd other narrow areas.</t>
	<section anchor="principles-of-the-ietf-and-isoc-relationship" title="Principles	</section>
	of the IETF and ISOC Relationship">	<section anchor="principles-of-the-ietf-and-isoc-relationship" numbered="t
		rue" toc="include" removeInRFC="false" pn="section-4.5">
	<t>The principles of the relationship between the IETF and ISOC are outlined in	<name slugifiedName="name-principles-of-the-ietf-and-">Principles of the
	<xref target="I-D.ietf-iasa2-rfc2031bis"/>.	IETF and ISOC Relationship</name>
		<t pn="section-4.5-1">The principles of the relationship between the IET
		F and ISOC are outlined in <xref target="RFC8712" format="default" sectionFormat
		="of" derivedContent="RFC8712"/>.
	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="include" removeInRFC="false" pn="section-4.6">
	e="Relationship of the IETF LLC Board to the IETF Leadership">	<name slugifiedName="name-relationship-of-the-ietf-ll">Relationship of t
		he IETF LLC Board to the IETF Leadership</name>
	<t>The IETF LLC Board is directly accountable to the IETF community for the	<t pn="section-4.6-1">The IETF LLC Board is directly accountable to the
	performance of the IASA 2.0. However, the nature of the Board’s work	IETF community for the
		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="include" removeInRFC="false" pn="section-4.7">
	title="Review of IETF Executive Director and IETF LLC Board Decisions">	<name slugifiedName="name-review-of-ietf-executive-di">Review of IETF Ex
	<t>The IETF LLC Board is directly accountable to the IETF community for the perf	ecutive Director and IETF LLC Board Decisions</name>
	ormance of the IASA 2.0, including hiring and managing the IETF Executive Direct	<t pn="section-4.7-1">The IETF LLC Board is directly accountable to the
	or. In extreme cases of dissatisfaction with the IETF LLC, the IETF community ca	IETF community for the performance of the IASA 2.0, including hiring and managin
	n utilize the recall process as noted in <xref target="director-removal"/>.</t>	g 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
	<t>Anyone in the community of IETF participants may ask the Board for a formal r	="director-removal" format="default" sectionFormat="of" derivedContent="Section
	eview of a decision or action by the IETF Executive Director or Board if they be	6.7"/>.</t>
	lieve this was not undertaken in accordance with IETF BCPs or IETF	<t pn="section-4.7-2">Anyone in the community of IETF participants may a
		sk the Board for a formal review of a decision or action by the IETF Executive D
		irector 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 pn="section-4.7-3">A formal request for review must be addressed to t
	<t>A formal request for review must be addressed to the IETF LLC Board chair and	he IETF LLC Board chair and must include a description of the decision or action
	must include a description of the decision or action to be reviewed, an explana	to be reviewed, an explanation of how, in the requestor's opinion, the decision
	tion of how, in the requestor’s opinion, the decision or action violates the BCP	or action violates the BCPs or IASA 2.0 operational guidelines, and a suggestio
	s or IASA 2.0 operational guidelines, and a suggestion for how the situation cou	n for how the situation could be rectified.</t>
	ld be rectified.</t>	<t pn="section-4.7-4">The IETF LLC shall respond to such requests within
		a reasonable period, typically within 90 days, and shall publicly publish infor
	<t>The IETF LLC shall respond to such requests within a reasonable period, typic	mation about the request 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="include" rem
		oveInRFC="false" pn="section-4.8">
	</section>	<name slugifiedName="name-termination-and-change">Termination and Change
	<section anchor="termination-and-change" title="Termination and Change">	</name>
		<t pn="section-4.8-1">Any major change to the IASA 2.0 arrangements shal
	<t>Any major change to the IASA 2.0 arrangements shall require	l 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="include" removeInR
	<section anchor="structure-of-iasa2" title="Structure of IASA2">	FC="false" pn="section-5">
		<name slugifiedName="name-structure-of-iasa-20">Structure of IASA 2.0</nam
	<section anchor="staff-responsibilities" title="IETF Executive Director and Staf	e>
	f Responsibilities">	<section anchor="staff-responsibilities" numbered="true" toc="include" rem
		oveInRFC="false" pn="section-5.1">
	<t>The IETF LLC is led by an IETF Executive Director chosen by the Board. The IE	<name slugifiedName="name-ietf-executive-director-and">IETF Executive Di
	TF Executive Director is responsible for managing the day-to-day operations of t	rector and Staff Responsibilities</name>
	he IETF LLC, including hiring staff to perform various operational functions. Th	<t pn="section-5.1-1">The IETF LLC is led by an IETF Executive Director
	e IETF Executive Director and any staff may be employees or independent contract	chosen by the Board. The IETF Executive Director is responsible for managing the
	ors.</t>	day-to-day operations of the IETF LLC, including hiring staff to perform variou
		s operational functions. The IETF Executive Director and any staff may be employ
	<t>Allowing for the division of responsibilities among multiple staff members an	ees or independent contractors.</t>
	d contractors is designed to address some of the concerns raised in Section 3.2	<t pn="section-5.1-2">Allowing for the division of responsibilities amon
	(Lack of Resources) and Section 3.4 (Funding/Operating Model Mismatch and Rising	g multiple staff members and contractors is designed to address some of the conc
	Costs) of <xref target="I-D.haberman-iasa20dt-recs"/>.</t>	erns raised in
		Section <xref target="I-D.haberman-iasa20dt-recs" section="3.2" sectionFormat="b
	<t>Based on the amount of work previously undertaken by the IAD and others invol	are" format="default" derivedLink="https://tools.ietf.org/html/draft-haberman-ia
	ved in the IETF administration, the design of the IETF LLC anticipated that the	sa20dt-recs-03#section-3.2" derivedContent="IASA2RECS"/> (Lack of Resources) and
	IETF Executive Director may need to hire multiple additional staff members. For	Section <xref target="I-D.haberman-iasa20dt-recs" section="3.4" sectionFormat="b
	example, resources to manage fundraising, to manage the various contractors that	are" format="default" derivedLink="https://tools.ietf.org/html/draft-haberman-ia
	are engaged to fulfill the IETF’s administrative needs, and to support outreach	sa20dt-recs-03#section-3.4" derivedContent="IASA2RECS"/> (Funding/Operating Mode
	and communications were envisioned.</t>	l Mismatch and Rising Costs) of <xref target="I-D.haberman-iasa20dt-recs" format
		="default" sectionFormat="of" derivedContent="IASA2RECS"/>.</t>
	<t>The IETF has historically benefited from the use of contractors for accountin	<t pn="section-5.1-3">Based on the amount of work previously undertaken
	g, finance, meeting planning, administrative assistance, legal counsel, tools, a	by the IAD and others involved in the IETF administration, the design of the IET
	nd web site support, as well as other services related to the standards process	F LLC anticipated that the IETF Executive Director may need to hire multiple add
	(RFC Editor and IANA). Prior to making the transition from IASA to IASA 2.0, the	itional staff members. For example, resources to manage fundraising, to manage t
	IETF budget reflected specific support from ISOC for communications and fundrai	he various contractors that are engaged to fulfill the IETF's administrative nee
	sing as well as some general support for accounting, finance, legal, and other s	ds, and to support outreach and communications were envisioned.</t>
	ervices. The division of responsibilities between staff and contractors is at th	<t pn="section-5.1-4">The IETF has historically benefited from the use o
	e discretion of the IETF Executive Director and their staff.</t>	f contractors for
		accounting, finance, meeting planning, administrative assistance,
	<t>The IETF has a long history of community involvement in the execution of cert	legal counsel, tools, and web site support, as well as other services
	ain administrative functions, in particular development of IETF tools, the NOC’s	related to the standards process (e.g., RFC Editor and IANA). Prior to ma
	operation of the meeting network, and some outreach and communications activiti	king the transition from IASA to IASA 2.0, the IETF budget reflected specific su
	es conducted by the Education and Mentoring Directorate. The IETF LLC staff is e	pport from ISOC for communications and fundraising as well as some general suppo
	xpected to respect the IETF community’s wishes about community involvement in th	rt for accounting, finance, legal, and other services. The division of responsib
	ese and other functions going forward as long as the staff feels that they can m	ilities between staff and contractors is at the discretion of the IETF Executive
	eet the otherwise-stated needs of the community. Establishing the framework to a	Director and their staff.</t>
	llow the IETF LLC to staff each administrative function as appropriate may requi	<t pn="section-5.1-5">The IETF has a long history of community involveme
	re the IETF community to document its consensus expectations in areas where no d	nt in the execution of certain administrative functions, in particular developme
	ocumentation currently exists.</t>	nt of IETF tools, the operation of the meeting network by the Network Operations
		Center (NOC), and some outreach and communications activities conducted by the
	<t>In summary, the IETF Executive Director, with support from the team that they	Education and Mentoring Directorate. The IETF LLC staff is expected to respect t
	alone direct and lead, is responsible for:</t>	he IETF community's wishes about community involvement in these and other functi
		ons going forward as long as the staff feels that they can meet the otherwise-st
	<t><list style="symbols">	ated needs of the community. Establishing the framework to allow the IETF LLC to
	<t>Developing and refining an annual budget and other strategic financial plan	staff each administrative function as appropriate may require the IETF communit
	ning documents at the direction of the Board.</t>	y to document its consensus expectations in areas where no documentation current
	<t>Executing on the annual budget, including reporting to the Board regularly	ly exists.</t>
	with forecasts and actual performance to budget.</t>	<t pn="section-5.1-6">In summary, the IETF Executive Director, with supp
	<t>Hiring and/or contracting the necessary resources to meet their goals, with	ort from the team that they alone direct and lead, is responsible for:</t>
	in the defined limits of the IETF	<ul spacing="normal" bare="false" empty="false" pn="section-5.1-7">
	Executive Director’s authority and within the approved budget. This includes man	<li pn="section-5.1-7.1">Developing and refining an annual budget and
	aging and leading any such	other strategic financial planning documents at the direction of the Board.</li>
	resources, including performing regular performance reviews.</t>	<li pn="section-5.1-7.2">Executing on the annual budget, including rep
	<t>Following the pre-approval guidelines set forth by the Board for contracts	orting to the Board regularly with forecasts and actual performance to budget.</
	or other decisions that have financial costs that exceed a certain threshold of	li>
	significance. Such thresholds are expected to be set reasonably high so that the	<li pn="section-5.1-7.3">Hiring and/or contracting the necessary resou
	need for such approvals is infrequent and only occurs when something is truly s	rces to meet their goals, within the defined limits of the IETF
	ignificant or otherwise exceptional. It is expected that the IETF Executive Dire	Executive Director's authority and within the approved budget. This includes man
	ctor is sufficiently empowered to perform the job on a day-to-day basis, being h	aging and leading any such
	eld accountable for meeting high level goals rather than micromanaged.</t>	resources, including performing regular performance reviews.</li>
	<t>Regularly updating the Board on operations and other notable issues as reas	<li pn="section-5.1-7.4">Following the pre-approval guidelines set for
	onable and appropriate.</t>	th by the Board for contracts or other decisions that have financial costs that
	<t>Ensuring that all staff and/or other resources comply with any applicable p	exceed a certain threshold of significance. Such thresholds are expected to be s
	olicies established or approved by the Board, such as ethics guidelines and/or a	et reasonably high so that the need for such approvals is infrequent and only oc
	code of conduct.</t>	curs when something is truly significant or otherwise exceptional. It is expecte
	</list></t>	d 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 goals rathe
	</section>	r than being micromanaged.</li>
	<section anchor="board-responsibilities" title="IETF LLC Board Responsibilities"	<li pn="section-5.1-7.5">Regularly updating the Board on operations an
	>	d other notable issues as reasonable and appropriate.</li>
		<li pn="section-5.1-7.6">Ensuring that all staff and/or other resource
	<t>This section is intended to provide a summary of key IETF LLC Board responsib	s comply with any applicable policies established or approved by the Board, such
	ilities,	as ethics guidelines and/or a code of conduct.</li>
		</ul>
		</section>
		<section anchor="board-responsibilities" numbered="true" toc="include" rem
		oveInRFC="false" pn="section-5.2">
		<name slugifiedName="name-ietf-llc-board-responsibili">IETF LLC Board Re
		sponsibilities</name>
		<t pn="section-5.2-1">This section is intended to provide a summary of k
		ey IETF LLC Board responsibilities,
	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" sectionFormat="of" derivedContent="IE
	unintentional differences	TF-LLC-A"/> and applicable law.
	or other confusion between this document and these authoritative sources, these	If there are unintentional differences or other
	sources will	confusion, the LLC Agreement and applicable law are authoritative.</t>
	control over this document.</t>	<t pn="section-5.2-2">Board members have fiduciary obligations imposed b
		y the LLC Agreement and applicable law,
	<t>Board members have fiduciary obligations imposed by the LLC Agreement and app	including duties of loyalty, care, and good faith. The Board is responsible
	licable law,	for setting broad strategic direction for the LLC, adopting an annual budget, hi
	including duties of loyalty, care and good faith. The Board is responsible to se	ring or terminating an
	t broad strategic direction	IETF Executive Director (or amending the terms of their engagement), adopting an
	for the LLC, and adopt an annual budget, hire or terminate an	y employee benefit plans,
	IETF Executive Director (or amend the terms of their engagement), adopt any empl	consulting the relevant IETF communities on matters related to the LLC as approp
	oyee benefit plans,	riate, approving any
	consult the relevant IETF communities on matters related to the LLC as appropria	changes to the LLC governance structure, incurring any debt, and approving enter
	te, approve any	ing into agreements
	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 pn="section-5.2-3">Per Section 5(d) of the LLC Agreement and as also
	<t>Per Section 5(d) of the LLC Agreement and as also described in <xref target="	described in
	principles"/>, the Board shall,	<xref target="principles" format="default" sectionFormat="of" derivedCont
		ent="Section 4.4"/> of this document, the Board 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 pn="section-5.2-4">The role of the Board is to ensure that the strate
	<t>The role of the Board is to ensure that the strategy and conduct of the IETF	gy and conduct of the IETF LLC is consistent with the IETF's needs -- both its c
	LLC is consistent with the IETF’s needs – both its concrete needs and its needs	oncrete needs and its needs for transparency and accountability. The Board is n
	for transparency and accountability. The Board is not intended to directly defi	ot intended to directly define the IETF's needs; to the extent that is required,
	ne the IETF’s needs; to the extent that is required, the IETF community should d	the IETF community should document its needs in consensus-based RFCs (e.g., as
	ocument its needs in consensus-based RFCs (e.g., as the community did in <xref t	the community did in <xref target="RFC8718" format="default" sectionFormat="of"
	arget="I-D.ietf-mtgvenue-iaoc-venue-selection-process"/>) and provide more detai	derivedContent="RFC8718"/>) and provide more detailed input via consultations wi
	led input via consultations with the Board (such as takes place on email discuss	th the Board (such as takes place on email discussion lists or at IETF meetings)
	ion lists or at IETF meetings).</t>	.</t>
		<t pn="section-5.2-5">Key IETF LLC Board responsibilities include:</t>
	<t>Key IETF LLC Board responsibilities include:</t>	<ul spacing="normal" bare="false" empty="false" pn="section-5.2-6">
		<li pn="section-5.2-6.1">Setting broad strategic direction for the LLC
	<t><list style="symbols">	.</li>
	<t>Set broad strategic direction for the LLC.</t>	<li pn="section-5.2-6.2">Hiring or terminating an IETF Executive Direc
	<t>Hire or terminate an IETF Executive Director (or amending the terms of thei	tor (or amending the terms of their engagement).</li>
	r engagement).</t>	<li pn="section-5.2-6.3">Delegating management of day-to-day activitie
	<t>Delegate management of day-to-day activities and related decision-making to	s and related decision-making to staff.</li>
	staff.</t>	<li pn="section-5.2-6.4">Adopting any employee benefit plans.</li>
	<t>Adopt any employee benefit plans.</t>	<li pn="section-5.2-6.5">Consulting the relevant IETF communities on m
	<t>Consult the relevant IETF communities on matters related to the LLC, as app	atters related to the LLC, as appropriate.</li>
	ropriate.</t>	<li pn="section-5.2-6.6">Approving any changes to the LLC governance s
	<t>Approve any changes to the LLC governance structure.</t>	tructure.</li>
	<t>Adopt an annual budget and, as necessary, incur any debt.</t>	<li pn="section-5.2-6.7">Adopting an annual budget and, as necessary,
	<t>Prepare accurate and timely financial statements for ISOC, and in accordanc	incur any debt.</li>
	e with generally	<li pn="section-5.2-6.8">Preparing accurate and timely financial state
	accepted accounting principles.</t>	ments for ISOC, in accordance with generally
	<t>Provide assistance to help facilitate ISOC’s tax compliance, including but	accepted accounting principles.</li>
	not limited to assistance related to preparing the Form 990 and responding to an	<li pn="section-5.2-6.9">Providing assistance to help facilitate ISOC'
	y IRS questions and audits.</t>	s tax compliance, including but not limited to assistance related to preparing t
	<t>Approve entering into agreements that that meet a significant materiality t	he Form 990 and responding to any United States Internal Revenue Service (IRS) q
	hreshold to be	uestions and audits.</li>
	determined by the Board.</t>	<li pn="section-5.2-6.10">Approving entering into agreements that meet
	<t>Limit its activities to the purposes as set forth in Section 4 of the LLC A	a significant materiality threshold to be
	greement, in a manner	determined by the Board.</li>
	consistent with ISOC’s charitable purposes.</t>	<li pn="section-5.2-6.11">Limiting its activities to the purposes as s
	<t>Establish an investment policy.</t>	et forth in Section 4 of the LLC Agreement, in a manner
	<t>Use best efforts to conduct all of its activities in strict compliance with	consistent with ISOC's charitable purposes.</li>
	the LLC Agreement and all	<li pn="section-5.2-6.12">Establishing an investment policy.</li>
	applicable laws, rules and regulations.</t>	<li pn="section-5.2-6.13">Using best efforts to conduct all of its act
	<t>Ensure that IETF LLC is run in a manner that is transparent and accountable	ivities in strict compliance with the LLC Agreement and all
	to the IETF community;</t>	applicable laws, rules, and regulations.</li>
	<t>Develop policies, including those noted in <xref target="llc-policies"/>),	<li pn="section-5.2-6.14">Ensuring that IETF LLC is run in a manner th
	procedures, and a compliance program.</t>	at is transparent and accountable to the IETF community.</li>
	<t>Obtain Commercial General Liability and other appropriate insurance policie	<li pn="section-5.2-6.15">Developing policies, including those noted i
	s, with	n <xref target="llc-policies" format="default" sectionFormat="of" derivedContent
	agreed-upon coverage limits.</t>	="Section 8"/>, procedures, and a compliance program.</li>
	<t>Recruit new Directors for consideration in all of the various appointment p	<li pn="section-5.2-6.16">Obtaining Commercial General Liability and o
	rocesses.</t>	ther appropriate insurance policies, with
	</list></t>	agreed-upon coverage limits.</li>
		<li pn="section-5.2-6.17">Recruiting new Directors for consideration i
	</section>	n all of the various appointment processes.</li>
	<section anchor="board-design-goals" title="Board Design Goals">	</ul>
		</section>
	<t>A goal of this Board composition is to balance the need for the IETF LLC to b	<section anchor="board-design-goals" numbered="true" toc="include" removeI
	e accountable to the IETF community with the need for this Board to have the exp	nRFC="false" pn="section-5.3">
	ertise necessary to oversee a small non-profit company. The Board is smaller tha	<name slugifiedName="name-board-design-goals">Board Design Goals</name>
	n the previous IAOC and the other leadership bodies of the IETF, in part to keep	<t pn="section-5.3-1">A goal of this Board composition is to balance the
	the Board focused on its rather limited set of strategic responsibilities as no	need for the IETF LLC to be accountable to the IETF community with the need for
	ted in <xref target="board-responsibilities"/>.</t>	this Board to have the expertise necessary to oversee a small non-profit compan
		y. The Board is smaller than the previous IAOC and the other leadership bodies o
	<t>This board structure, with limited strategic responsibilities noted in <xref	f the IETF, in part to keep the Board focused on its rather limited set of strat
	target="board-responsibilities"/> and limited size, together with the staff resp	egic responsibilities as noted in <xref target="board-responsibilities" format="
	onsibilities noted in <xref target="staff-responsibilities"/>, is designed to ov	default" sectionFormat="of" derivedContent="Section 5.2"/>.</t>
	ercome the challenges described in Section 3.1.4 of <xref target="I-D.haberman-i	<t pn="section-5.3-2">This board structure, with limited strategic respo
	asa20dt-recs"/> concerning oversight. This establishes a clear line of oversight	nsibilities noted in <xref target="board-responsibilities" format="default" sect
	over staff performance: the IETF LLC Board oversees the IETF Executive Director	ionFormat="of" derivedContent="Section 5.2"/> and limited size, together with th
	’s performance and has actual legal authority to remove a non-performing IETF Ex	e staff responsibilities noted in <xref target="staff-responsibilities" format="
	ecutive Director. The IETF Executive Director is responsible for the day-to-day	default" sectionFormat="of" derivedContent="Section 5.1"/>, is designed to overc
	operation of the IETF LLC.</t>	ome the challenges described in
		<xref target="I-D.haberman-iasa20dt-recs" section="3.1.4" sectionFormat="of" for
	<t>Finally, the Board would be expected to operate transparently, to further add	mat="default" derivedLink="https://tools.ietf.org/html/draft-haberman-iasa20dt-r
	ress the concern raised in Section 3.3 of <xref target="I-D.haberman-iasa20dt-re	ecs-03#section-3.1.4" derivedContent="IASA2RECS"/>
	cs"/>. The default transparency rule arrived at during the IASA 2.0 design proce	concerning oversight. This establishes a clear line of oversight over staff perf
	ss is detailed above in <xref target="principles"/>. The Board will need to esta	ormance: the IETF LLC Board oversees the IETF Executive Director's performance a
	blish how it will meet that commitment.</t>	nd 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
	</section>	IETF LLC.</t>
	</section>	<t pn="section-5.3-3">Finally, the Board is expected to operate transpar
	<section anchor="board" title="IETF LLC Board Membership, Selection and Accounta	ently, to further address the concern raised in
	bility">	<xref target="I-D.haberman-iasa20dt-recs" section="3.3" sectionFormat="of" forma
		t="default" derivedLink="https://tools.ietf.org/html/draft-haberman-iasa20dt-rec
	<t>The section outlines the composition of the IETF LLC Board, selection of IETF	s-03#section-3.3" derivedContent="IASA2RECS"/>. The default transparency rule ar
	LLC Board Directors, and related details.</t>	rived at during the IASA 2.0 design process is detailed in <xref target="princip
		les" format="default" sectionFormat="of" derivedContent="Section 4.4"/>. The Boa
	<section anchor="board-composition" title="Board Composition">	rd will need to establish how it will meet that commitment.</t>
		</section>
	<t>There is a minimum of 5 directors, expandable to 6 or 7.</t>	</section>
		<section anchor="board" numbered="true" toc="include" removeInRFC="false" pn
	<t><list style="symbols">	="section-6">
	<t>1 IETF Chair or delegate selected by the IESG</t>	<name slugifiedName="name-ietf-llc-board-membership-s">IETF LLC Board Memb
	<t>1 Appointed by the ISOC Board of Trustees</t>	ership, Selection, and Accountability</name>
	<t>3 Selected by the IETF NomCom, confirmed by the IESG</t>	<t pn="section-6-1">The section outlines the composition of the IETF LLC B
	<t>Up to 2 Appointed by the IETF LLC board itself, on an as-needed basis, conf	oard, selection of IETF LLC Board Directors, and related details.</t>
	irmed by the IESG</t>	<section anchor="board-composition" numbered="true" toc="include" removeIn
	</list></t>	RFC="false" pn="section-6.1">
		<name slugifiedName="name-board-composition">Board Composition</name>
	<t>For the first slot listed above, the presumption is that the IETF	<t pn="section-6.1-1">There is a minimum of 5 directors, which is expand
	Chair will serve on the board. At the IESG’s discretion, another area	able to 6 or 7.
		The IETF LLC Board is comprised of the following:</t>
		<ul spacing="normal" bare="false" empty="false" pn="section-6.1-2">
		<li pn="section-6.1-2.1">1 IETF Chair or delegate selected by the IESG
		</li>
		<li pn="section-6.1-2.2">1 Appointed by the ISOC Board of Trustees</li
		>
		<li pn="section-6.1-2.3">3 Selected by the IETF Nominating Committee (
		NomCom), confirmed by the IESG</li>
		<li pn="section-6.1-2.4">Up to 2 Appointed by the IETF LLC Board itsel
		f, on an as-needed basis, confirmed by the IESG</li>
		</ul>
		<t pn="section-6.1-3">For the first slot listed above, the presumption i
		s 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="include" removeInRFC=
	<section anchor="llc-directors" title="IETF LLC-Appointed Directors">	"false" pn="section-6.2">
		<name slugifiedName="name-ietf-llc-appointed-director">IETF LLC-Appointe
	<t>As noted above, a maximum of two Directors may be appointed by the	d Directors</name>
		<t pn="section-6.2-1">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	two. 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 pn="section-6.2-2">The appointment of a Board-appointed Director requ
	<t>The appointment of a Board-appointed Director requires a two-thirds	ires 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" sectionFormat="of" derivedContent="Section 6.5"/>.</t>
	</section>	</section>
	<section anchor="director-recruitment" title="Recruiting IETF LLC Board Director	<section anchor="director-recruitment" numbered="true" toc="include" remov
	s">	eInRFC="false" pn="section-6.3">
		<name slugifiedName="name-recruiting-ietf-llc-board-d">Recruiting IETF L
	<t>The Board itself is expected to take an active role in recruiting potential n	LC Board Directors</name>
	ew Directors, regardless of the process that may be used to appoint them. In par	<t pn="section-6.3-1">The Board itself is expected to take an active rol
	ticular, the NomCom is primarily focused on considering requirements expressed b	e in recruiting potential new Directors, regardless of the process that may be u
	y the Board and others, reviewing community feedback on candidates, conducting c	sed to appoint them. In particular, the NomCom is primarily focused on consideri
	andidate interviews, and ultimately appointing Directors. The Board and others	ng requirements expressed by the Board and others, reviewing community feedback
	can recruit potential Directors and get them into the consideration process of t	on candidates, conducting candidate interviews, and ultimately appointing Direct
	he NomCom or into open considerations processes of the other appointing bodies i	ors. The Board and others can recruit potential Directors and get them into the
	f those bodies choose to use such processes.</t>	consideration process of the NomCom or into open consideration processes of the
		other appointing bodies if those bodies choose to use such processes.</t>
	</section>	</section>
	<section anchor="term-length" title="IETF LLC Board Director Term Length">	<section anchor="term-length" numbered="true" toc="include" removeInRFC="f
		alse" pn="section-6.4">
	<t>The term length for a Director is three years. The exceptions to this	<name slugifiedName="name-ietf-llc-board-director-ter">IETF LLC Board Di
		rector Term Length</name>
		<t pn="section-6.4-1">The term length for a Director is three years. The
		exceptions to this
	guideline are:</t>	guideline are:</t>

		<ul spacing="normal" bare="false" empty="false" pn="section-6.4-2">
	<t><list style="symbols">	<li pn="section-6.4-2.1">The terms for some Directors during the first
	<t>For the terms for some Directors during the first full formation of	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 pn="section-6.4-2.2">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" derivedLink="https://rfc-editor.org/rfc/rfc8713#section-
	3.4.</t>	3.4" derivedContent="RFC8713"/>.</li>
	</list></t>	</ul>
		</section>
	</section>	<section anchor="term-limit" numbered="true" toc="include" removeInRFC="fa
	<section anchor="term-limit" title="IETF LLC Board Director Limit">	lse" pn="section-6.5">
		<name slugifiedName="name-ietf-llc-board-director-lim">IETF LLC Board Di
	<t>A director may serve no more than two consecutive terms.	rector Limit</name>
		<t pn="section-6.5-1">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" derivedLink="https://rfc-editor.org/rfc/rfc8713#section-3.4"
		derivedContent="RFC8713"/>.</t>
	<t>The term limits specified above apply to an individual, even if that	<t pn="section-6.5-2">The term limits specified above apply to an indivi
		dual, 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 pn="section-6.5-3">Lastly, partial terms of less than three years for
	<t>Lastly, partial terms of less than three years for the initial appointments t	the initial appointments to the first full Board, for which some Directors will
	o the first full board, for which some Directors will have terms of one or two y	have terms of one or two years, do not count against the term limit.</t>
	ears, do not count against the term limit.</t>	<t pn="section-6.5-4">The limit on consecutive terms supports the health
		y regular introduction of new ideas and energy into the Board and mitigates pote
	<t>The limit on consecutive terms supports the healthy regular introduction of n	ntial long-term risk of ossification or conflict, without adversely impacting th
	ew ideas and energy into the Board and mitigates potential long-term risk of oss	e potential pool of 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="include" removeInRF
		C="false" pn="section-6.6">
	</section>	<name slugifiedName="name-staggered-terms">Staggered Terms</name>
	<section anchor="staggered-terms" title="Staggered Terms">	<t pn="section-6.6-1">The Internet Society Board of Trustees, the IESG,
		the Nominating Committee, and the
	<t>The Internet Society Board of Trustees, the IESG, the Nominating Committee, a	IETF LLC Board are expected to coordinate with each other to ensure that
	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="include" removeInR
	<section anchor="director-removal" title="IETF LLC Board Director Removal">	FC="false" pn="section-6.7">
		<name slugifiedName="name-ietf-llc-board-director-rem">IETF LLC Board Di
	<t>NomCom-appointed and IESG-appointed Directors may be removed with or without	rector Removal</name>
	cause. A vote in favor of	<t pn="section-6.7-1">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	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" derivedLink="https://rfc-editor.org/rfc/rfc8713#section-7" derivedContent="
	</section>	RFC8713"/>.</t>
	<section anchor="director-vacancy" title="Filling an IETF LLC Board Director Vac	</section>
	ancy">	<section anchor="director-vacancy" numbered="true" toc="include" removeInR
		FC="false" pn="section-6.8">
	<t>It shall be the responsibility of each respective body that appointed or sele	<name slugifiedName="name-filling-an-ietf-llc-board-d">Filling an IETF L
	cted a Director that vacates the Board	LC Board Director Vacancy</name>
		<t pn="section-6.8-1">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 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" derivedLink="https://rfc-editor.org/rfc/rfc8713#section-3.5" derivedContent="RFC8713"/>) 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="include" removeInRFC="false"
	<section anchor="quorum" title="Quorum">	pn="section-6.9">
		<name slugifiedName="name-quorum">Quorum</name>
	<t>At all meetings of the Board, two-thirds of the Directors then in office shal	<t pn="section-6.9-1">At all meetings of the Board, two-thirds of the Di
	l constitute	rectors then in office shall 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="include" removeInRFC="false"
	<section anchor="voting" title="Board Voting">	pn="section-6.10">
		<name slugifiedName="name-board-voting">Board Voting</name>
	<t>Board decisions may be made either by vote communicated in a meeting	<t pn="section-6.10-1">Board decisions may be made either by vote commun
		icated 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. 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" sectio
		nFormat="of" derivedContent="Section 6.7"/>.</t>
	</section>	</section>
	<section anchor="interim-board" title="Interim Board">	<section anchor="interim-board" numbered="true" toc="include" removeInRFC=
		"false" pn="section-6.11">
	<t>An initial interim Board was necessary in order to legally form and bootstrap	<name slugifiedName="name-interim-board">Interim Board</name>
	the IETF LLC. As a result, an Interim Board was formed on a temporary basis unt	<t pn="section-6.11-1">An initial interim Board was necessary in order t
	il the first full board was constituted.</t>	o legally form and bootstrap the IETF LLC. As a result, an Interim Board was for
		med on a temporary basis until the first full Board was constituted.</t>
	<t>The interim Board was comprised of:</t>	<t pn="section-6.11-2">The interim Board was comprised of:</t>
		<ul spacing="normal" bare="false" empty="false" pn="section-6.11-3">
	<t><list style="symbols">	<li pn="section-6.11-3.1">The IETF chair, ex officio</li>
	<t>The IETF chair, ex officio</t>	<li pn="section-6.11-3.2">The IAOC chair, ex officio</li>
	<t>The IAOC chair, ex officio</t>	<li pn="section-6.11-3.3">The IAB chair, ex officio</li>
	<t>The IAB chair, ex officio</t>	<li pn="section-6.11-3.4">One ISOC trustee, selected by the ISOC Board
	<t>One ISOC trustee, selected by the ISOC Board of Trustees</t>	of Trustees</li>
	</list></t>	</ul>
		</section>
	</section>	<section anchor="board-positions" numbered="true" toc="include" removeInRF
	<section anchor="board-positions" title="Board Positions">	C="false" pn="section-6.12">
		<name slugifiedName="name-board-positions">Board Positions</name>
	<t>Following the formation of the first permanent Board, and annually thereafter	<t pn="section-6.12-1">Following the formation of the first permanent Bo
	, the Directors shall	ard, and annually thereafter, the Directors shall
	elect a Director to serve as Board Chair by majority vote. The IETF, IAB and IRT	elect a Director to serve as Board Chair by majority vote. The IETF, IAB, and IR
	F chairs, and the	TF chairs, and the
	chair of ISOC’s Board, will be ineligible for this Board Chair role. The Board m	chair of ISOC's Board, will be ineligible for this Board Chair role. The Board m
	ay also form committees	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="include" removeInRFC
	<section anchor="ietf-llc-funding" title="IETF LLC Funding">	="false" pn="section-7">
		<name slugifiedName="name-ietf-llc-funding">IETF LLC Funding</name>
	<t>The IETF LLC must function within a budget of costs balanced against limited	<t pn="section-7-1">The IETF LLC must function within a budget of costs ba
	revenues. The IETF community expects	lanced 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	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 pn="section-7-2">The IETF LLC was generating income from a few key sour
	<t>The IETF LLC was generating income from a few key sources at the time that th	ces at the time that this document was written, as enumerated below. Additional
	is document was written, as enumerated below. Additional sources of income may b	sources of income may be developed in the future, within the general bounds note
	e developed in the future, within the general bounds noted in <xref target="fund	d in <xref target="fundraising-practices" format="default" sectionFormat="of" de
	raising-practices"/>, and some of these may decline in relevance or go away. As	rivedContent="Section 7.8"/>, and some of these may decline in relevance or go a
	a result this list is subject to change over time and is merely an example of th	way. As a result, this list is subject to change over time and is merely an exam
	e primary sources of income for the IETF LLC at the time of this writing:</t>	ple of the primary sources of income for the IETF LLC at the time of this writin
		g:</t>
	<t><list style="numbers">	<ol spacing="normal" type="1" start="1" pn="section-7-3">
	<t>ISOC support</t>	<li pn="section-7-3.1" derivedCounter="1.">ISOC support</li>
	<t>IETF meeting revenues</t>	<li pn="section-7-3.2" derivedCounter="2.">IETF meeting revenues</li>
	<t>Sponsorships (monetary and/or in-kind)</t>	<li pn="section-7-3.3" derivedCounter="3.">Sponsorships (monetary and/or
	<t>Donations (monetary and/or in-kind)</t>	in-kind)</li>
	</list></t>	<li pn="section-7-3.4" derivedCounter="4.">Donations (monetary and/or in
		-kind)</li>
	<section anchor="financial-statements" title="Financial Statements">	</ol>
		<section anchor="financial-statements" numbered="true" toc="include" remov
	<t>As noted in <xref target="board-responsibilities"/>, the IETF LLC must comply	eInRFC="false" pn="section-7.1">
	with relevant tax laws, such as filing an annual	<name slugifiedName="name-financial-statements">Financial Statements</na
		me>
		<t pn="section-7.1-1">As noted in <xref target="board-responsibilities"
		format="default" sectionFormat="of" derivedContent="Section 5.2"/>, 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 pn="section-7.1-2">In addition to these official financial statements
	<t>In addition to these official financial statements and forms, the IETF LLC is	and forms, the IETF 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="includ
	<section anchor="bank-and-investment-accounts" title="Bank and Investment Accoun	e" removeInRFC="false" pn="section-7.2">
	ts">	<name slugifiedName="name-bank-and-investment-account">Bank and Investme
		nt Accounts</name>
	<t>The IETF LLC maintains its own bank account, separate and distinct from ISOC.	<t pn="section-7.2-1">The IETF LLC maintains its own bank account, separ
	The IETF LLC	ate 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	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="include" removeInR
	<section anchor="financial-audits" title="Financial Audits">	FC="false" pn="section-7.3">
		<name slugifiedName="name-financial-audits">Financial Audits</name>
	<t>The IETF LLC is expected to retain and work with an independent auditor. Repo	<t pn="section-7.3-1">The IETF LLC is expected to retain and work with a
	rts from the auditor are expected to be shared with the IETF community and other	n independent auditor. Reports from the auditor are expected to be shared with t
	groups and organizations as needed or as required by law.</t>	he IETF community and other groups and organizations as needed or as required by
		law.</t>
	</section>	</section>
	<section anchor="isoc-financial-support" title="ISOC Financial Support">	<section anchor="isoc-financial-support" numbered="true" toc="include" rem
		oveInRFC="false" pn="section-7.4">
	<t>ISOC currently provides significant financial support to the IETF LLC. Exhibi	<name slugifiedName="name-isoc-financial-support">ISOC Financial Support
	t B of the <xref target="IETF-LLC-A"/>	</name>
		<t pn="section-7.4-1">ISOC currently provides significant financial supp
		ort to the IETF LLC. Exhibit B of the <xref target="IETF-LLC-A" format="default"
		sectionFormat="of" derivedContent="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="include" remo
	<section anchor="ietf-meeting-revenues" title="IETF Meeting Revenues">	veInRFC="false" pn="section-7.5">
		<name slugifiedName="name-ietf-meeting-revenues">IETF Meeting Revenues</
	<t>Meeting revenues are another important source of funding that supports the IE	name>
	TF, coming mainly from the fees paid	<t pn="section-7.5-1">Meeting revenues are another important source of f
		unding that supports the IETF, 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="include" removeInRFC="false" pn="section-7.6">
	and Donations to the IETF LLC">	<name slugifiedName="name-sponsorships-and-donations-">Sponsorships and
		Donations to the IETF LLC</name>
	<t>Sponsorships and donations are an essential component of the financial suppor	<t pn="section-7.6-1">Sponsorships and donations are an essential compon
	t for the IETF. Within the general	ent of the financial support for the IETF. Within the general
	bounds noted in <xref target="fundraising-practices"/>, the IETF LLC is responsi	bounds noted in <xref target="fundraising-practices" format="default" sectionFor
	ble for fundraising activities in order	mat="of" derivedContent="Section 7.8"/>, the IETF LLC is responsible for fundrai
		sing 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 pn="section-7.6-2">Sponsorships and donations to the IETF LLC do not
	<t>Sponsorships and donations to the IETF LLC do not (and must not) convey to sp	(and must not) convey 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 pn="section-7.6-3">To the extent that the IETF LLC needs to undertake
	<t>To the extent that the IETF LLC needs to undertake any significant special pr	any significant special 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="include" r
	<section anchor="focus-of-funding-support" title="Focus of Funding Support">	emoveInRFC="false" pn="section-7.7">
		<name slugifiedName="name-focus-of-funding-support">Focus of Funding Sup
	<t>The IETF LLC exists to support the IETF, IAB, and IRTF. Therefore, the IETF	port</name>
	LLC’s funding and all revenues,	<t pn="section-7.7-1">The IETF LLC exists to support the IETF, IAB, and
		IRTF. Therefore, the IETF 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="include" remo
	<section anchor="fundraising-practices" title="Charitable Fundraising Practices"	veInRFC="false" pn="section-7.8">
	>	<name slugifiedName="name-charitable-fundraising-prac">Charitable Fundra
		ising Practices</name>
	<t>When the IETF LLC conducts fundraising, it substantiates charitable	<t pn="section-7.8-1">When the IETF LLC conducts fundraising, it substan
	contributions on behalf of ISOC – meaning that according to US tax	tiates charitable
		contributions on behalf of ISOC -- meaning that according to United States 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" sectionFormat="of
		" derivedContent="Section 8"/>.</t>
	</section>	</section>
	<section anchor="operating-reserve" title="Operating Reserve">	<section anchor="operating-reserve" numbered="true" toc="include" removeIn
		RFC="false" pn="section-7.9">
	<t>An initial target operating reserve has been specified in Exhibit B of the <x	<name slugifiedName="name-operating-reserve">Operating Reserve</name>
	ref target="IETF-LLC-A"/>. That says that the IETF LLC	<t pn="section-7.9-1">An initial target operating reserve has been speci
	should maintain an operating reserve equal to the IETF LLC’s budgeted Net Loss f	fied in Exhibit B of the <xref target="IETF-LLC-A" format="default" sectionForma
	or 2019 multiplied times three. The IETF	t="of" derivedContent="IETF-LLC-A"/>. It says that the IETF LLC
	LLC, in cooperation with ISOC, may regularly review the financial target for thi	should maintain an operating reserve equal to the IETF LLC's budgeted Net Loss f
	s reserve fund, as noted in the <xref target="IETF-LLC-A"/> or as otherwise nece	or 2019 multiplied times three. The IETF
	ssary.</t>	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" secti
	<t>Should the IETF LLC generate an annual budget surplus, it may choose to direc	onFormat="of" derivedContent="IETF-LLC-A"/> or as otherwise necessary.</t>
	t all or part of the surplus towards	<t pn="section-7.9-2">Should the IETF LLC generate an annual budget surp
		lus, it may choose to direct 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="include" remo
	<section anchor="annual-budget-process" title="Annual Budget Process">	veInRFC="false" pn="section-7.10">
		<name slugifiedName="name-annual-budget-process">Annual Budget Process</
	<t>As noted in <xref target="llc-responsibilities"/>, the IETF LLC is responsibl	name>
	e for managing the IETF’s finances and budget.	<t pn="section-7.10-1">As noted in <xref target="llc-responsibilities" f
		ormat="default" sectionFormat="of" derivedContent="Section 4.3"/>, the IETF LLC
		is responsible 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 pn="section-7.10-2">As explained in <xref target="staff-responsibilit
	<t>As explained in <xref target="staff-responsibilities"/>, the IETF Executive D	ies" format="default" sectionFormat="of" derivedContent="Section 5.1"/>, the IET
	irector is expected to develop, execute, and report on the	F Executive Director is expected to develop, execute, and report on 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 pn="section-7.10-3">The Board, as explained in <xref target="board-re
	<t>The Board, as explained in <xref target="board-responsibilities"/>, is expect	sponsibilities" format="default" sectionFormat="of" derivedContent="Section 5.2"
	ed to review and approve the	/>, is expected 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 pn="section-7.10-4">The annual budget is expected to be developed in
	<t>The annual budget is expected to be developed in an open, transparent, and co	an open, transparent, and collaborative manner, in accordance with
	llaborative manner, in accordance with	<xref target="principles" format="default" sectionFormat="of" derivedContent="Se
	<xref target="principles"/>. The specific timeline for the development, review,	ction 4.4"/>. The specific timeline for the development, review, and approval of
	and approval of the IETF LLC annual budget is established by the Board and may b	the IETF LLC annual budget is established by the Board and may be revised as ne
	e revised as needed.</t>	eded.</t>
		</section>
	</section>	</section>
	</section>	<section anchor="llc-policies" numbered="true" toc="include" removeInRFC="fa
	<section anchor="llc-policies" title="IETF LLC Policies">	lse" pn="section-8">
		<name slugifiedName="name-ietf-llc-policies">IETF LLC Policies</name>
	<t>The Board is expected to maintain policies as necessary to achieve the	<t pn="section-8-1">The Board is expected to maintain policies as necessar
		y 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="include" remov
	<section anchor="conflict-of-interest" title="Conflict of Interest Policy">	eInRFC="false" pn="section-8.1">
		<name slugifiedName="name-conflict-of-interest-policy">Conflict of Inter
	<t>The Board is expected to maintain a Conflict of Interest policy for the IETF	est Policy</name>
	LLC. While the details are determined by the Board, at a minimum such policy is	<t pn="section-8.1-1">The Board is expected to maintain a Conflict of In
	expected to include the following:</t>	terest policy for the IETF LLC. While the details are determined by the Board, a
		t a minimum such policy is expected to include the following:</t>
	<t><list style="symbols">	<ul spacing="normal" bare="false" empty="false" pn="section-8.1-2">
	<t>The IETF, ISOC Board, IAB, or IRTF chair cannot be chair of the IETF LLC Bo	<li pn="section-8.1-2.1">The IETF, ISOC Board, IAB, or IRTF chair cann
	ard, though they may serve as a Director.</t>	ot be chair of the IETF LLC Board, though they may serve as a Director.</li>
	<t>A Director cannot be a paid consultant or employee of the IETF Executive Di	<li pn="section-8.1-2.2">A Director cannot be a paid consultant or emp
	rector or their sub-contractors, nor a paid consultant or employee of ISOC.</t>	loyee of the IETF Executive Director or their sub-contractors, nor a paid consul
	</list></t>	tant or employee of ISOC.</li>
		</ul>
	</section>	</section>
	<section anchor="other-policies" title="Other Policies">	<section anchor="other-policies" numbered="true" toc="include" removeInRFC
		="false" pn="section-8.2">
	<t>The Board is expected to maintain additional policies for the IETF LLC as nec	<name slugifiedName="name-other-policies">Other Policies</name>
	essary, covering Directors, employees, and contractors, concerning issues such a	<t pn="section-8.2-1">The Board is expected to maintain additional polic
	s:</t>	ies for the IETF LLC as necessary, covering Directors, employees, and contractor
		s, concerning issues such as:</t>
	<t><list style="symbols">	<ul spacing="normal" bare="false" empty="false" pn="section-8.2-2">
	<t>Acceptance of gifts and other non-cash compensation;</t>	<li pn="section-8.2-2.1">Acceptance of gifts and other non-cash compen
	<t>Travel and expense reimbursement;</t>	sation</li>
	<t>Anti-bribery;</t>	<li pn="section-8.2-2.2">Travel and expense reimbursement</li>
	<t>Code of conduct;</t>	<li pn="section-8.2-2.3">Anti-bribery</li>
	<t>Anti-harassment;</t>	<li pn="section-8.2-2.4">Code of conduct</li>
	<t>Non-discrimination;</t>	<li pn="section-8.2-2.5">Anti-harassment</li>
	<t>Whistleblower;</t>	<li pn="section-8.2-2.6">Non-discrimination</li>
	<t>Document retention;</t>	<li pn="section-8.2-2.7">Whistleblower</li>
	<t>Export controls;</t>	<li pn="section-8.2-2.8">Document retention</li>
	<t>Anti-terrorism sanctions;</t>	<li pn="section-8.2-2.9">Export controls</li>
	<t>Data protection and privacy;</t>	<li pn="section-8.2-2.10">Anti-terrorism sanctions</li>
	<t>Social media</t>	<li pn="section-8.2-2.11">Data protection and privacy</li>
	</list></t>	<li pn="section-8.2-2.12">Social media</li>
		</ul>
	</section>	</section>
	<section anchor="compliance" title="Compliance">	<section anchor="compliance" numbered="true" toc="include" removeInRFC="fa
		lse" pn="section-8.3">
	<t>The IETF LLC is expected to implement a compliance program to ensure its comp	<name slugifiedName="name-compliance">Compliance</name>
	liance with all applicable laws, rules and regulations, including without limita	<t pn="section-8.3-1">The IETF LLC is expected to implement a compliance
	tion laws governing bribery, anti-terrorism sanctions, export controls, data pro	program to ensure its compliance with all applicable laws, rules, and regulatio
	tection/privacy, as well as other applicable policies noted in <xref target="llc	ns, including without limitation laws governing bribery, anti-terrorism sanction
	-policies"/>. In addition, actions and activities of the IETF LLC must be consis	s, export controls, data protection/privacy, as well as other applicable policie
	tent with 501(c)(3) purposes.</t>	s noted in <xref target="llc-policies" format="default" sectionFormat="of" deriv
		edContent="Section 8"/>. In addition, actions and activities of the IETF LLC mus
	<t>The IETF LLC is expected report to ISOC and the IETF community on the impleme	t be consistent with 501(c)(3) purposes.</t>
	ntation of its compliance plan on an annual basis.</t>	<t pn="section-8.3-2">The IETF LLC is expected to report to ISOC and the
		IETF community on the implementation of its compliance plan on an annual basis.
	</section>	</t>
	</section>	</section>
	<section anchor="three-year-assessment" title="Three-Year Assessment">	</section>
		<section anchor="three-year-assessment" numbered="true" toc="include" remove
	<t>The IETF LLC, with the involvement of the community, shall conduct and comple	InRFC="false" pn="section-9">
	te an assessment of the structure, processes, and operation of IASA 2.0 and the	<name slugifiedName="name-three-year-assessment">Three-Year Assessment</na
	IETF LLC. This should be presented to the community after a period of roughly th	me>
	ree years of operation. The assessment may potentially include recommendations f	<t pn="section-9-1">The IETF LLC, with the involvement of the community, s
	or improvements or changes to the IASA2 and/or IETF LLC.</t>	hall 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 anchor="security-considerations" title="Security Considerations">	after a period of roughly three years of operation. The assessment may
		potentially include recommendations for improvements or changes to the
	<t>This document describes the structure of the IETF’s Administrative	IASA 2.0 and/or IETF LLC.</t>
	Support Activity (IASA), version 2 (IASA2). It introduces no security considera	</section>
	tions	<section anchor="security-considerations" numbered="true" toc="include" remo
		veInRFC="false" pn="section-10">
		<name slugifiedName="name-security-considerations">Security Considerations
		</name>
		<t pn="section-10-1">This document describes the structure of IASA 2.0. I
		t introduces no security considerations
	for the Internet.</t>	for the Internet.</t>

		</section>
	</section>	<section anchor="iana-considerations" numbered="true" toc="include" removeIn
	<section anchor="iana-considerations" title="IANA Considerations">	RFC="false" pn="section-11">
		<name slugifiedName="name-iana-considerations">IANA Considerations</name>
	<t>This document has no IANA considerations in the traditional sense.	<t pn="section-11-1">This document has no IANA considerations in the tradi
		tional 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 title='Normative References'>	<references pn="section-12">
		<name slugifiedName="name-references">References</name>
	<reference anchor="I-D.ietf-iasa2-rfc2031bis">	<references pn="section-12.1">
	<front>	<name slugifiedName="name-normative-references">Normative References</na
	<title>The IETF-ISOC Relationship</title>	me>
		<reference anchor="IETF-LLC-A" target="https://www.ietf.org/documents/18
	<author initials='G' surname='Camarillo' fullname='Gonzalo Camarillo'>	0/IETF-LLC-Agreement.pdf" quoteTitle="true" derivedAnchor="IETF-LLC-A">
	<organization />	<front>
	</author>	<title>Limited Liability Company Agreement of IETF Administration LL
		C</title>
	<author initials='J' surname='Livingood' fullname='Jason Livingood'>	<author>
	<organization />	</author>
	</author>	<date year="2018" month="August"/>
		</front>
	<date month='February' day='14' year='2019' />	</reference>
		<reference anchor="RFC8712" target="https://www.rfc-editor.org/info/rfc8
	<abstract><t>This document summarises the Internet Engineering Task Force (IETF)	712" quoteTitle="true" derivedAnchor="RFC8712">
	- Internet Society (ISOC) relationship, following a major revision to the struc	<front>
	ture of the IETF Administrative Support Activity (IASA) in 2018. The IASA was r	<title>The IETF-ISOC Relationship</title>
	evised under a new "IASA 2.0" structure by the IASA2 Working Group, which change	<author initials="G" surname="Camarillo" fullname="Gonzalo Camarillo
	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	<organization showOnFrontPage="true"/>
	o revise RFC 2031.</t></abstract>	</author>
		<author initials="J" surname="Livingood" fullname="Jason Livingood">
	</front>	<organization showOnFrontPage="true"/>
		</author>
	<seriesInfo name='Internet-Draft' value='draft-ietf-iasa2-rfc2031bis-04' />	<date month="February" year="2020"/>
	<format type='TXT'	</front>
	target='http://www.ietf.org/internet-drafts/draft-ietf-iasa2-rfc2031bis-	<seriesInfo name="RFC" value="8712"/>
	04.txt' />	<seriesInfo name="DOI" value="10.17487/RFC8712"/>
	</reference>	</reference>
		<reference anchor="RFC8713" target="https://www.rfc-editor.org/info/rfc8
	<reference anchor="I-D.ietf-iasa2-rfc7437bis">	713" quoteTitle="true" derivedAnchor="RFC8713">
	<front>	<front>
	<title>IAB, IESG, IETF Trust and IETF LLC Selection, Confirmation, and Recall Pr	<title>IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation,
	ocess: Operation of the IETF Nominating and Recall Committees</title>	and Recall Process: Operation of the IETF Nominating and Recall Committees</titl
		e>
	<author initials='M' surname='Kucherawy' fullname='Murray Kucherawy'>	<author initials="M." surname="Kucherawy" role="editor">
	<organization />	<organization showOnFrontPage="true"/>
	</author>	</author>
		<author initials="R." surname="Hinden" role="editor">
	<author initials='R' surname='Hinden' fullname='Robert Hinden'>	<organization showOnFrontPage="true"/>
	<organization />	</author>
	</author>	<author initials="J." surname="Livingood" role="editor">
		<organization showOnFrontPage="true"/>
	<author initials='J' surname='Livingood' fullname='Jason Livingood'>	</author>
	<organization />	<date month="February" year="2020"/>
	</author>	</front>
		<seriesInfo name="BCP" value="10"/>
	<date month='March' day='26' year='2019' />	<seriesInfo name="RFC" value="8713"/>
		<seriesInfo name="DOI" value="10.17487/RFC8713"/>
	<abstract><t>The process by which the members of the IAB and IESG, some Trustees	</reference>
	of the IETF Trust, and some Directors of the IETF LLC are selected, confirmed,	</references>
	and recalled is specified in this document. This document based on RFC3777 and	<references pn="section-12.2">
	RFC7437 and has been updated to reflect the changes introduced by IASA 2.0. Thi	<name slugifiedName="name-informative-references">Informative References
	s document obsoletes RFC7437 and RFC8318.</t></abstract>	</name>
		<reference anchor="I-D.haberman-iasa20dt-recs" quoteTitle="true" target=
	</front>	"https://tools.ietf.org/html/draft-haberman-iasa20dt-recs-03" derivedAnchor="IAS
		A2RECS">
	<seriesInfo name='Internet-Draft' value='draft-ietf-iasa2-rfc7437bis-06' />	<front>
	<format type='TXT'	<title>IASA 2.0 Design Team Recommendations</title>
	target='http://www.ietf.org/internet-drafts/draft-ietf-iasa2-rfc7437bis-	<author initials="B" surname="Haberman" fullname="Brian Haberman">
	06.txt' />	<organization showOnFrontPage="true"/>
	</reference>	</author>
		<author initials="J" surname="Arkko" fullname="Jari Arkko">
	<reference anchor="IETF-LLC-A" target="https://www.ietf.org/documents/180/IETF-L	<organization showOnFrontPage="true"/>
	LC-Agreement.pdf">	</author>
	<front>	<author initials="L" surname="Daigle" fullname="Leslie Daigle">
	<title>Limited Liability Company Agreement of IETF Administration LLC</title	<organization showOnFrontPage="true"/>
	>	</author>
	<author >	<author initials="J" surname="Livingood" fullname="Jason Livingood">
	<organization>The Internet Society</organization>	<organization showOnFrontPage="true"/>
	</author>	</author>
	<date year="2018" month="August"/>	<author initials="J" surname="Hall" fullname="Joseph Hall">
	</front>	<organization showOnFrontPage="true"/>
	</reference>	</author>
		<author initials="E" surname="Rescorla" fullname="Eric Rescorla">
	</references>	<organization showOnFrontPage="true"/>
		</author>
	<references title='Informative References'>	<date month="November" day="27" year="2018"/>
		<abstract>
	<reference anchor="RFC7691" target='https://www.rfc-editor.org/info/rfc7691'>	<t>The arrangements relating to administrative support for the IET
	<front>	F were created more than ten years ago. Since then, there has been considerable
	<title>Updating the Term Dates of IETF Administrative Oversight Committee (IAOC)	change in the tasks and in our own expectations. The IETF community has discus
	Members</title>	sed these changes and the problems they cause. The community has some sense of
	<author initials='S.' surname='Bradner' fullname='S. Bradner' role='editor'><org	the properties they expect from future arrangements, including those related to
	anization /></author>	structure, organization, personnel, and transparency. This document is a produc
	<date year='2015' month='November' />	t of a design team, focused on providing additional information to the community
	<abstract><t>BCP 101 defines the start and end dates for the terms of IETF Admin	about solution options, as well as supporting analysis of the implications of t
	istrative Oversight Committee (IAOC) members; these terms have proven to be impr	hose options. This document reflects the final snapshot of the design team discu
	actical. This memo updates BCP 101 to direct the IAOC to establish more practic	ssion and is published for historical posterity.</t>
	al start and end dates for terms of IAOC members.</t></abstract>	</abstract>
	</front>	</front>
	<seriesInfo name='BCP' value='101'/>	<seriesInfo name="Internet-Draft" value="draft-haberman-iasa20dt-recs-
	<seriesInfo name='RFC' value='7691'/>	03"/>
	<seriesInfo name='DOI' value='10.17487/RFC7691'/>	<format type="TXT" target="http://www.ietf.org/internet-drafts/draft-h
	</reference>	aberman-iasa20dt-recs-03.txt"/>
		<refcontent>Work in Progress</refcontent>
	<reference anchor="RFC2026" target='https://www.rfc-editor.org/info/rfc2026'>	</reference>
	<front>	<reference anchor="ISOC" target="https://www.internetsociety.org/about-i
	<title>The Internet Standards Process -- Revision 3</title>	nternet-society/governance-policies/by-laws/" quoteTitle="true" derivedAnchor="I
	<author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></	SOC">
	author>	<front>
	<date year='1996' month='October' />	<title>Amended and restated By-Laws of the Internet Society</title>
	<abstract><t>This memo documents the process used by the Internet community for	<author>
	the standardization of protocols and procedures. It defines the stages in the s	<organization showOnFrontPage="true">The Internet Society</organiz
	tandardization process, the requirements for moving a document between stages an	ation>
	d the types of documents used during this process. This document specifies an In	</author>
	ternet Best Current Practices for the Internet Community, and requests discussio	<date year="2019" month="October"/>
	n and suggestions for improvements.</t></abstract>	</front>
	</front>	</reference>
	<seriesInfo name='BCP' value='9'/>	<reference anchor="RFC2014" target="https://www.rfc-editor.org/info/rfc2
	<seriesInfo name='RFC' value='2026'/>	014" quoteTitle="true" derivedAnchor="RFC2014">
	<seriesInfo name='DOI' value='10.17487/RFC2026'/>	<front>
	</reference>	<title>IRTF Research Group Guidelines and Procedures</title>
		<author initials="A." surname="Weinrib" fullname="A. Weinrib">
	<reference anchor="RFC2014" target='https://www.rfc-editor.org/info/rfc2014'>	<organization showOnFrontPage="true"/>
	<front>	</author>
	<title>IRTF Research Group Guidelines and Procedures</title>	<author initials="J." surname="Postel" fullname="J. Postel">
	<author initials='A.' surname='Weinrib' fullname='A. Weinrib'><organization /></	<organization showOnFrontPage="true"/>
	author>	</author>
	<author initials='J.' surname='Postel' fullname='J. Postel'><organization /></au	<date year="1996" month="October"/>
	thor>	<abstract>
	<date year='1996' month='October' />	<t>This document describes the guidelines and procedures for forma
	<abstract><t>This document describes the guidelines and procedures for formation	tion and operation of IRTF Research Groups. It describes the relationship betwe
	and operation of IRTF Research Groups. It describes the relationship between I	en IRTF participants, Research Groups, the Internet Research Steering Group (IRS
	RTF participants, Research Groups, the Internet Research Steering Group (IRSG) a	G) and the Internet Architecture Board (IAB). This document specifies an Intern
	nd the Internet Architecture Board (IAB). This document specifies an Internet B	et Best Current Practices for the Internet Community, and requests discussion an
	est Current Practices for the Internet Community, and requests discussion and su	d suggestions for improvements.</t>
	ggestions for improvements.</t></abstract>	</abstract>
	</front>	</front>
	<seriesInfo name='BCP' value='8'/>	<seriesInfo name="BCP" value="8"/>
	<seriesInfo name='RFC' value='2014'/>	<seriesInfo name="RFC" value="2014"/>
	<seriesInfo name='DOI' value='10.17487/RFC2014'/>	<seriesInfo name="DOI" value="10.17487/RFC2014"/>
	</reference>	</reference>
		<reference anchor="RFC2026" target="https://www.rfc-editor.org/info/rfc2
	<reference anchor="RFC2850" target='https://www.rfc-editor.org/info/rfc2850'>	026" quoteTitle="true" derivedAnchor="RFC2026">
	<front>	<front>
	<title>Charter of the Internet Architecture Board (IAB)</title>	<title>The Internet Standards Process -- Revision 3</title>
	<author><organization>Internet Architecture Board</organization></author>	<author initials="S." surname="Bradner" fullname="S. Bradner">
	<author initials='B.' surname='Carpenter' fullname='B. Carpenter' role='editor'>	<organization showOnFrontPage="true"/>
	<organization /></author>	</author>
	<date year='2000' month='May' />	<date year="1996" month="October"/>
	<abstract><t>This memo documents the composition, selection, roles, and organiza	<abstract>
	tion of the Internet Architecture Board. It replaces RFC 1601. This document s	<t>This memo documents the process used by the Internet community
	pecifies an Internet Best Current Practices for the Internet Community, and requ	for the standardization of protocols and procedures. It defines the stages in t
	ests discussion and suggestions for improvements.</t></abstract>	he standardization process, the requirements for moving a document between stage
	</front>	s and the types of documents used during this process. This document specifies a
	<seriesInfo name='BCP' value='39'/>	n Internet Best Current Practices for the Internet Community, and requests discu
	<seriesInfo name='RFC' value='2850'/>	ssion and suggestions for improvements.</t>
	<seriesInfo name='DOI' value='10.17487/RFC2850'/>	</abstract>
	</reference>	</front>
		<seriesInfo name="BCP" value="9"/>
	<reference anchor="RFC4071" target='https://www.rfc-editor.org/info/rfc4071'>	<seriesInfo name="RFC" value="2026"/>
	<front>	<seriesInfo name="DOI" value="10.17487/RFC2026"/>
	<title>Structure of the IETF Administrative Support Activity (IASA)</title>	</reference>
	<author initials='R.' surname='Austein' fullname='R. Austein' role='editor'><org	<reference anchor="RFC2850" target="https://www.rfc-editor.org/info/rfc2
	anization /></author>	850" quoteTitle="true" derivedAnchor="RFC2850">
	<author initials='B.' surname='Wijnen' fullname='B. Wijnen' role='editor'><organ	<front>
	ization /></author>	<title>Charter of the Internet Architecture Board (IAB)</title>
	<date year='2005' month='April' />	<author>
	<abstract><t>This document describes the structure of the IETF Administrative Su	<organization showOnFrontPage="true">Internet Architecture Board</
	pport Activity (IASA) as an activity housed within the Internet Society (ISOC).	organization>
	It defines the roles and responsibilities of the IETF Administrative Oversight	</author>
	Committee (IAOC), the IETF Administrative Director (IAD), and ISOC in the fiscal	<author initials="B." surname="Carpenter" fullname="B. Carpenter" ro
	and administrative support of the IETF standards process. It also defines the	le="editor">
	membership and selection rules for the IAOC. This document specifies an Interne	<organization showOnFrontPage="true"/>
	t Best Current Practices for the Internet Community, and requests discussion and	</author>
	suggestions for improvements.</t></abstract>	<date year="2000" month="May"/>
	</front>	<abstract>
	<seriesInfo name='BCP' value='101'/>	<t>This memo documents the composition, selection, roles, and orga
	<seriesInfo name='RFC' value='4071'/>	nization of the Internet Architecture Board. It replaces RFC 1601. This docume
	<seriesInfo name='DOI' value='10.17487/RFC4071'/>	nt specifies an Internet Best Current Practices for the Internet Community, and
	</reference>	requests discussion and suggestions for improvements.</t>
		</abstract>
	<reference anchor="RFC3710" target='https://www.rfc-editor.org/info/rfc3710'>	</front>
	<front>	<seriesInfo name="BCP" value="39"/>
	<title>An IESG charter</title>	<seriesInfo name="RFC" value="2850"/>
	<author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'><organizatio	<seriesInfo name="DOI" value="10.17487/RFC2850"/>
	n /></author>	</reference>
	<date year='2004' month='February' />	<reference anchor="RFC3233" target="https://www.rfc-editor.org/info/rfc3
	<abstract><t>This memo provides a charter for the Internet Engineering Steering	233" quoteTitle="true" derivedAnchor="RFC3233">
	Group (IESG), a management function of the Internet Engineering Task Force (IETF	<front>
	). It is meant to document the charter of the IESG as it is presently understoo	<title>Defining the IETF</title>
	d. This memo provides information for the Internet community.</t></abstract>	<author initials="P." surname="Hoffman" fullname="P. Hoffman">
	</front>	<organization showOnFrontPage="true"/>
	<seriesInfo name='RFC' value='3710'/>	</author>
	<seriesInfo name='DOI' value='10.17487/RFC3710'/>	<author initials="S." surname="Bradner" fullname="S. Bradner">
	</reference>	<organization showOnFrontPage="true"/>
		</author>
	<reference anchor="RFC3233" target='https://www.rfc-editor.org/info/rfc3233'>	<date year="2002" month="February"/>
	<front>	<abstract>
	<title>Defining the IETF</title>	<t>This document gives a more concrete definition of "the IETF" as
	<author initials='P.' surname='Hoffman' fullname='P. Hoffman'><organization /></	it understood today. Many RFCs refer to "the IETF". Many important IETF docum
	author>	ents speak of the IETF as if it were an already-defined entity. However, no IETF
	<author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></	document correctly defines what the IETF is. This document specifies an Intern
	author>	et Best Current Practices for the Internet Community, and requests discussion an
	<date year='2002' month='February' />	d suggestions for improvements.</t>
	<abstract><t>This document gives a more concrete definition of "the IETF&qu	</abstract>
	ot; as it understood today. Many RFCs refer to "the IETF". Many impo	</front>
	rtant IETF documents speak of the IETF as if it were an already-defined entity.	<seriesInfo name="BCP" value="58"/>
	However, no IETF document correctly defines what the IETF is. This document spe	<seriesInfo name="RFC" value="3233"/>
	cifies an Internet Best Current Practices for the Internet Community, and reques	<seriesInfo name="DOI" value="10.17487/RFC3233"/>
	ts discussion and suggestions for improvements.</t></abstract>	</reference>
	</front>	<reference anchor="RFC3710" target="https://www.rfc-editor.org/info/rfc3
	<seriesInfo name='BCP' value='58'/>	710" quoteTitle="true" derivedAnchor="RFC3710">
	<seriesInfo name='RFC' value='3233'/>	<front>
	<seriesInfo name='DOI' value='10.17487/RFC3233'/>	<title>An IESG charter</title>
	</reference>	<author initials="H." surname="Alvestrand" fullname="H. Alvestrand">
		<organization showOnFrontPage="true"/>
	<reference anchor="RFC4333" target='https://www.rfc-editor.org/info/rfc4333'>	</author>
	<front>	<date year="2004" month="February"/>
	<title>The IETF Administrative Oversight Committee (IAOC) Member Selection Guide	<abstract>
	lines and Process</title>	<t>This memo provides a charter for the Internet Engineering Steer
	<author initials='G.' surname='Huston' fullname='G. Huston' role='editor'><organ	ing Group (IESG), a management function of the Internet Engineering Task Force (
	ization /></author>	IETF). It is meant to document the charter of the IESG as it is presently under
	<author initials='B.' surname='Wijnen' fullname='B. Wijnen' role='editor'><organ	stood. This memo provides information for the Internet community.</t>
	ization /></author>	</abstract>
	<date year='2005' month='December' />	</front>
	<abstract><t>This memo outlines the guidelines for selection of members of the I	<seriesInfo name="RFC" value="3710"/>
	ETF Administrative Oversight Committee, and describes the selection process used	<seriesInfo name="DOI" value="10.17487/RFC3710"/>
	by the IAB and the IESG. This document specifies an Internet Best Current Prac	</reference>
	tices for the Internet Community, and requests discussion and suggestions for im	<reference anchor="RFC4071" target="https://www.rfc-editor.org/info/rfc4
	provements.</t></abstract>	071" quoteTitle="true" derivedAnchor="RFC4071">
	</front>	<front>
	<seriesInfo name='BCP' value='113'/>	<title>Structure of the IETF Administrative Support Activity (IASA)<
	<seriesInfo name='RFC' value='4333'/>	/title>
	<seriesInfo name='DOI' value='10.17487/RFC4333'/>	<author initials="R." surname="Austein" fullname="R. Austein" role="
	</reference>	editor">
		<organization showOnFrontPage="true"/>
	<reference anchor="I-D.ietf-mtgvenue-iaoc-venue-selection-process">	</author>
	<front>	<author initials="B." surname="Wijnen" fullname="B. Wijnen" role="ed
	<title>IETF Plenary Meeting Venue Selection Process</title>	itor">
		<organization showOnFrontPage="true"/>
	<author initials='E' surname='Lear' fullname='Eliot Lear'>	</author>
	<organization />	<date year="2005" month="April"/>
	</author>	<abstract>
		<t>This document describes the structure of the IETF Administrativ
	<date month='June' day='14' year='2018' />	e Support Activity (IASA) as an activity housed within the Internet Society (ISO
		C). It defines the roles and responsibilities of the IETF Administrative Oversi
	<abstract><t>The IASA has responsibility for arranging IETF plenary meeting Venu	ght Committee (IAOC), the IETF Administrative Director (IAD), and ISOC in the fi
	e selection and operation. This memo specifies IETF community requirements for	scal and administrative support of the IETF standards process. It also defines
	meeting venues, including hotels and meeting room space. It directs the IASA to	the membership and selection rules for the IAOC. This document specifies an Int
	make available additional process documents that describe the current meeting s	ernet Best Current Practices for the Internet Community, and requests discussion
	election process.</t></abstract>	and suggestions for improvements.</t>
		</abstract>
	</front>	</front>
		<seriesInfo name="BCP" value="101"/>
	<seriesInfo name='Internet-Draft' value='draft-ietf-mtgvenue-iaoc-venue-selectio	<seriesInfo name="RFC" value="4071"/>
	n-process-16' />	<seriesInfo name="DOI" value="10.17487/RFC4071"/>
	<format type='TXT'	</reference>
	target='http://www.ietf.org/internet-drafts/draft-ietf-mtgvenue-iaoc-ven	<reference anchor="RFC4333" target="https://www.rfc-editor.org/info/rfc4
	ue-selection-process-16.txt' />	333" quoteTitle="true" derivedAnchor="RFC4333">
	</reference>	<front>
		<title>The IETF Administrative Oversight Committee (IAOC) Member Sel
	<reference anchor="I-D.haberman-iasa20dt-recs">	ection Guidelines and Process</title>
	<front>	<author initials="G." surname="Huston" fullname="G. Huston" role="ed
	<title>IASA 2.0 Design Team Recommendations</title>	itor">
		<organization showOnFrontPage="true"/>
	<author initials='B' surname='Haberman' fullname='Brian Haberman'>	</author>
	<organization />	<author initials="B." surname="Wijnen" fullname="B. Wijnen" role="ed
	</author>	itor">
		<organization showOnFrontPage="true"/>
	<author initials='J' surname='Arkko' fullname='Jari Arkko'>	</author>
	<organization />	<date year="2005" month="December"/>
	</author>	<abstract>
		<t>This memo outlines the guidelines for selection of members of t
	<author initials='L' surname='Daigle' fullname='Leslie Daigle'>	he IETF Administrative Oversight Committee, and describes the selection process
	<organization />	used by the IAB and the IESG. This document specifies an Internet Best Current
	</author>	Practices for the Internet Community, and requests discussion and suggestions fo
		r improvements.</t>
	<author initials='J' surname='Livingood' fullname='Jason Livingood'>	</abstract>
	<organization />	</front>
	</author>	<seriesInfo name="BCP" value="113"/>
		<seriesInfo name="RFC" value="4333"/>
	<author initials='J' surname='Hall' fullname='Joseph Hall'>	<seriesInfo name="DOI" value="10.17487/RFC4333"/>
	<organization />	</reference>
	</author>	<reference anchor="RFC7691" target="https://www.rfc-editor.org/info/rfc7
		691" quoteTitle="true" derivedAnchor="RFC7691">
	<author initials='E' surname='Rescorla' fullname='Eric Rescorla'>	<front>
	<organization />	<title>Updating the Term Dates of IETF Administrative Oversight Comm
	</author>	ittee (IAOC) Members</title>
		<author initials="S." surname="Bradner" fullname="S. Bradner" role="
	<date month='November' day='27' year='2018' />	editor">
		<organization showOnFrontPage="true"/>
	<abstract><t>The arrangements relating to administrative support for the IETF we	</author>
	re created more than ten years ago. Since then, there has been considerable cha	<date year="2015" month="November"/>
	nge in the tasks and in our own expectations. The IETF community has discussed	<abstract>
	these changes and the problems they cause. The community has some sense of the	<t>BCP 101 defines the start and end dates for the terms of IETF A
	properties they expect from future arrangements, including those related to stru	dministrative Oversight Committee (IAOC) members; these terms have proven to be
	cture, organization, personnel, and transparency. This document is a product of	impractical. This memo updates BCP 101 to direct the IAOC to establish more pra
	a design team, focused on providing additional information to the community abo	ctical start and end dates for terms of IAOC members.</t>
	ut solution options, as well as supporting analysis of the implications of those	</abstract>
	options. This document reflects the final snapshot of the design team discussio	</front>
	n and is published for historical posterity.</t></abstract>	<seriesInfo name="BCP" value="101"/>
		<seriesInfo name="RFC" value="7691"/>
	</front>	<seriesInfo name="DOI" value="10.17487/RFC7691"/>
		</reference>
	<seriesInfo name='Internet-Draft' value='draft-haberman-iasa20dt-recs-03' />	<reference anchor="RFC8714" target="https://www.rfc-editor.org/info/rfc8
	<format type='TXT'	714" quoteTitle="true" derivedAnchor="RFC8714">
	target='http://www.ietf.org/internet-drafts/draft-haberman-iasa20dt-recs	<front>
	-03.txt' />	<title>Update to the Process for Selection of Trustees for the IETF
	</reference>	Trust</title>
		<author initials="J." surname="Arkko">
	<reference anchor="I-D.ietf-iasa2-trust-update">	<organization showOnFrontPage="true"/>
	<front>	</author>
	<title>Update to the Process for Selection of Trustees for the IETF Trust</title	<author initials="T." surname="Hardie">
	>	<organization showOnFrontPage="true"/>
		</author>
	<author initials='J' surname='Arkko' fullname='Jari Arkko'>	<date month="February" year="2020"/>
	<organization />	</front>
	</author>	<seriesInfo name="BCP" value="101"/>
		<seriesInfo name="RFC" value="8714"/>
	<author initials='T' surname='Hardie' fullname='Ted Hardie'>	<seriesInfo name="DOI" value="10.17487/RFC8714"/>
	<organization />	</reference>
	</author>	<reference anchor="RFC8718" target="https://www.rfc-editor.org/info/rfc8
		718" quoteTitle="true" derivedAnchor="RFC8718">
	<date month='February' day='4' year='2019' />	<front>
		<title>IETF Plenary Meeting Venue Selection Process</title>
	<abstract><t>This memo updates the process for selection of trustees for the IET	<author initials="E." surname="Lear" role="editor">
	F Trust. Previously, the Internet Administrative Oversight Committee (IAOC) mem	<organization showOnFrontPage="true"/>
	bers also acted as trustees, but the IAOC has been eliminated as part of an upda	</author>
	te of the structure of the Internet Administrative Support Activity (IASA). Thi	<date month="February" year="2020"/>
	s memo specifies that the trustees shall be selected separately. This memo obso	</front>
	letes RFC 4371. The changes relate only to the selection of trustees. All othe	<seriesInfo name="BCP" value="226"/>
	r aspects of the IETF Trust remain as they are today.</t></abstract>	<seriesInfo name="RFC" value="8718"/>
		<seriesInfo name="DOI" value="10.17487/RFC8718"/>
	</front>	</reference>
		</references>
	<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-updat
	e-03.txt' />
	</reference>

	<reference anchor="ISOC" target="https://www.internetsociety.org/about-internet-
	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="2018" month="July"/>
	</front>
	</reference>

	</references>	</references>

		<section anchor="acknowledgments" numbered="false" toc="include" removeInRFC
		="false" pn="section-appendix.a">
		<name slugifiedName="name-acknowledgments">Acknowledgments</name>
		<t pn="section-appendix.a-1">Thanks to <contact fullname="Jari Arkko"/>, <
		contact fullname="Richard Barnes"/>, <contact fullname="Brian E. Carpenter"/>, <
		contact fullname="Alissa Cooper"/>, <contact fullname="John C. Klensin"/>, <cont
		act 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 pn="section-appendix.a-2">Coauthor Hall performed work on this document
		before employment at the Internet Society, and his affiliation listed in this d
		ocument is for identification purposes only.</t>
		</section>
		<section anchor="authors-addresses" numbered="false" removeInRFC="false" toc
		="include" pn="section-appendix.b">
		<name slugifiedName="name-authors-addresses">Authors' Addresses</name>
		<author initials="B." surname="Haberman" fullname="Brian Haberman">
		<organization showOnFrontPage="true">Johns Hopkins University</organizat
		ion>
		<address>
		<email>brian@innovationslab.net</email>
		</address>
		</author>
		<author initials="J." surname="Hall" fullname="Joseph Lorenzo Hall">
		<organization showOnFrontPage="true">Internet Society</organization>
		<address>
		<email>hall@isoc.org</email>
		</address>
		</author>
		<author initials="J." surname="Livingood" fullname="Jason Livingood">
		<organization showOnFrontPage="true">Comcast</organization>
		<address>
		<email>jason_livingood@comcast.com</email>
		</address>
		</author>
		</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. 80 change blocks.
	1448 lines changed or deleted	1620 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/