<?xml version="1.0" encoding="US-ASCII"?> version='1.0' encoding='utf-8'?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [

<!ENTITY RFC2026 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2026.xml">
<!ENTITY RFC2028 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2028.xml">
<!ENTITY RFC2031 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2031.xml">
<!ENTITY RFC2850 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2850.xml">
<!ENTITY RFC3677 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3677.xml">
<!ENTITY RFC4033 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4033.xml">
<!ENTITY RFC4071 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4071.xml">
<!ENTITY RFC4371 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4371.xml">
<!ENTITY RFC5378 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5378.xml">
<!ENTITY RFC6756 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6756.xml">
<!ENTITY RFC7437 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7437.xml">
<!ENTITY RFC8200 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8200.xml">
<!ENTITY I-D.ietf-iasa2-rfc4071bis SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-iasa2-rfc4071bis.xml">
<!ENTITY I-D.ietf-iasa2-trust-rationale SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-iasa2-trust-rationale.xml">
<!ENTITY I-D.ietf-iasa2-trust-update SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-iasa2-trust-update.xml">


<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?> "rfc2629-xhtml.ent">

category="info" docName="draft-ietf-iasa2-rfc2031bis-08"
ipr="trust200902" obsoletes="2031">
  <!-- xml2rfc v2v3 conversion 2.34.0 -->
    <title abbrev="The IETF-ISOC Relationship">
	The IETF-ISOC Relationship
    <seriesInfo name="RFC" value="8712"/>
    <author fullname="Gonzalo Camarillo" initials="G." surname="Camarillo">
    <author fullname="Jason Livingood" initials="J." surname="Livingood">
    <date month="August" year="2019" /> month="January" year="2020"/>
    <workgroup>IETF Administrative Support Activity 2</workgroup>
This document summarises summarizes the Internet Engineering Task Force (IETF) -
Internet Society (ISOC) relationship, following a major revision to
the structure of the IETF Administrative Support Activity (IASA) in
2018. The IASA was revised under a new "IASA 2.0" structure by the
IASA2 Working Group, which changed the IETF's administrative, legal,
and financial structure. As a result, it also changed the relationship
between the IETF and ISOC, which made it necessary to revise RFC 2031.
    <section title="Introduction numbered="true" toc="default">
      <name>Introduction and History"> History</name>
The Internet Society provides a corporate home for the administrative
entity that supports the Internet Engineering Task Force (IETF), the
Internet Architecture Board (IAB), and the Internet Research Task
Force (IRTF), and supports the work of these groups through a variety
of programs.
The Internet Engineering Task Force (IETF) is the body that is
responsible for the development and maintenance of the Internet
Standards. The IETF is primarily a volunteer organization. Its driving
force is a group of dedicated dedicated, high-quality engineers from all over the
world. In a structure of working groups, these engineers exchange
ideas and experience, and through discussion and collaboration (both
electronically and face-to-face) face-to-face), they strive to achieve rough
consensus and implement the standards through running code.
The growth of the Internet over several decades has also led to the
growth of the IETF. More and more people, organizations, and companies
rely on Internet Standards. Non-technical Nontechnical issues, such as legal,
administrative, and financial issues had long been an undesirable but
unavoidable part of the IETF. To address these issues in 1995 issues, the IETF
established the Poised95 Working Group. Group in 1995. Its goal was to structure and
document the IETF processes in order to maximize the flexibility and
freedom of IETF engineers so that they could work in the way the IETF
had always been most successful and to honour honor the IETF credo: "Rough
consensus and running code".
The Poised95 Working Group concluded that the Internet Society (ISOC),
which was formed in 1992, was the best organization to handle all of
these legal, administrative, and financial tasks on behalf of of, and in
close cooperation with with, the IETF. This led to documenting things such
as the IETF standards process <xref target="RFC2026"/>, target="RFC2026" format="default"/>, the IETF
organizational structure <xref target="RFC2028"/>, target="RFC2028" format="default"/>, the IETF Nominating
Committee (NomCom) procedures <eref target="BCP10"/>, <xref target="RFC2027"/>, and the IETF-ISOC
relationship <xref target="RFC2031"/>. target="RFC2031" format="default"/>.
As time passed and operational experience accumulated, additional
structure was necessary. As a result, the Internet Administrative
Support Activity (IASA) was defined in 2005 and documented in <xref
target="RFC4071"/> target="RFC4071" format="default"/> and <xref target="RFC4371"/>. target="RFC4371" format="default"/>.
In 2018, the IASA was revised under a new "IASA 2.0" structure by the
IASA2 Working Group, which made significant revisions to the IETF's
administrative, legal, and financial structure. One critical outcome
was the formation, in close cooperation between the IETF and
ISOC, of the IETF Administration Limited Liability Company (IETF LLC)
as a subsidiary of ISOC.
As a result of the IASA 2.0 structure <xref
target="I-D.ietf-iasa2-rfc4071bis"/> target="RFC8711" format="default"/> and formation of the IETF LLC, the
relationship between the IETF and ISOC has changed. This document
summarizes the current state of the IETF-ISOC relationship at a high
level and replaces <xref target="RFC2031"/>. target="RFC2031" format="default"/>.
    <section title="Philosophical numbered="true" toc="default">
      <name>Philosophical Relationship with ISOC"> ISOC</name>
ISOC and the IETF have historically been philosophically
aligned. ISOC's connection with the IETF community has always played
an important role in its policy work, which has not changed. ISOC has always been and
	  continues to be an advocate
for multistakeholder processes, which includes the technical
community. Open standards are an explicit part of one of the focus
areas in ISOC's mission: Advancing advancing the development and application of
Internet infrastructure, technologies, and open standards <eref <xref target="ISOC-Mission"/>.
    <section title="Main numbered="true" toc="default">
      <name>Main Division of Responsibilities between IETF and ISOC"> ISOC</name>
The IETF remains responsible for the development and quality of the
Internet Standards. Apart from the roles described below, the IETF and
ISOC acknowledge that ISOC as an organization has no direct influence whatsoever on the
technical content of Internet Standards (though ISOC employees may independently continue to
make technical contributions as individuals).
    <section anchor="standards" title="ISOC's numbered="true" toc="default">
      <name>ISOC's Role in the IETF Standards Process"> Process</name>
ISOC plays a small role in the IETF standards process. In particular,
ISOC assists the standards process by appointing the IETF NomCom chair
and by confirming IAB candidates who are put forward by the IETF
NomCom, as described in <xref target="RFC7437"/>, target="RFC8713" format="default"/>, and by acting as the
last resort in the appeals process, as described in <xref
target="RFC2026"/>. target="RFC2026" format="default"/>.
ISOC maintains liaison relationships and memberships in other
Standards Development Organizations (SDOs) and related organizations,
which directly benefits the IETF. For example, ISOC is a Sector Member
of the ITU-T. As a result, ISOC delegates are afforded the same rights
as other ITU-T Sector Members <xref target="RFC6756"/>. target="RFC6756" format="default"/>.
ISOC also supports the IETF standards process more indirectly (e.g.,
by promoting it in relevant communities) through several
programs.  For example, ISOC's Policymakers Program Programme to the IETF
(usually referred to simply as ISOC's policy fellows program) IETF Policy Program) gives
policy experts an opportunity to interact directly with the IETF
technical community. ISOC also performs technical work using the
standards developed in the IETF as its basis. An example of that is
ISOC's Deploy360 program, which helps encourage work in encouraging and support supporting the deployment
of IETF standards like DNSSEC  <xref
target="RFC4033"/> and IPv6  <xref
target="RFC8200"/>. standards.
Otherwise, the involvement of ISOC's employees in the IETF standards
process (e.g., as document editors or in leadership positions) is as
individual contributors rather than on institutional grounds.
    <section title="The numbered="true" toc="default">
      <name>The IETF's Role in ISOC"> ISOC</name>
The IETF plays a role in the governance of ISOC. Per ISOC's by-laws, bylaws,
the IETF appoints a set of trustees to the ISOC Board. The process by
which the IETF makes those appointments is defined in <xref
target="RFC3677"/>. target="RFC3677" format="default"/>.
The charter of the IAB (Internet Architecture Board) <xref
target="RFC2850"/> target="RFC2850" format="default"/> states that "the IAB acts as a source of advice and
guidance to the Board of Trustees and Officers of the Internet Society
concerning technical, architectural, procedural, and (where
appropriate) policy matters pertaining to the Internet and its
enabling technologies". This connection between the IAB and ISOC
ensures that ISOC's proposals in the policy area are based on a sound
understanding of the relevant technologies and architectures. ISOC's
strong connection to the Internet technical community has always been
one of its main strengths.
    <section title="Legal numbered="true" toc="default">
      <name>Legal Relationship with ISOC"> ISOC</name>
The IETF LLC is a disregarded Limited Liability Company (LLC) of the Internet Society - that was
established to provide a corporate legal framework for facilitating current and
future activities related to the IETF, IAB, and IRTF.  It was established by the
ISOC / IETF LLC Agreement <xref target="OpAgreement"/> target="OpAgreement" format="default"/> on August 27, 2018, and
governs the relationship between the IETF LLC and ISOC.
The IETF Trust, documented in <xref target="RFC5378"/>, target="RFC5378" format="default"/>, and updated in
<xref target="I-D.ietf-iasa2-trust-rationale"/> target="RFC8714" format="default"/> and <xref
target="I-D.ietf-iasa2-trust-update"/>, target="RFC8715" format="default"/>, provides legal protection for
the RFC series Series of documents and other aspects of the IETF. This
includes things such as protection for trademarks, copyrights, and
intellectual property rights. As part of the IETF Trust arrangement,
IETF standards documents can be freely downloaded, copied, and
distributed without financial or other distribution restrictions,
though all rights to change these documents lie with the IETF.  The
IETF Trust also provides legal protection in case of disputes over
intellectual property rights and other rights. The creation of the
IETF LLC has changed the way that the IETF Trust's trustees are
selected but did not change the purpose or operation of the Trust. One
of the IETF Trust's trustees is appointed by the ISOC's Board of
    <section title="Financial numbered="true" toc="default">
      <name>Financial and Administrative Relationship with ISOC"> ISOC</name>
Under the terms of the Operating Agreement <xref
target="OpAgreement"/> target="OpAgreement" format="default"/> between ISOC and the IETF, ISOC has agreed to
provide significant funding support for the IETF.  In addition,
the IETF LLC is responsible for creating and
managing an annual operating budget for the IETF; for negotiating,
signing, and overseeing contracts; for fundraising; for maintaining
bank accounts; and for liability insurance. The IETF LLC is managed by
a Board of Directors, one of whom is appointed by the ISOC's Board of
Trustees. The intention is that ISOC and the IETF LLC operate at arm's
The IETF LLC establishes contracts with third parties to provide
different types of services to the IETF. Note that it is possible that
some of those services may be provided by ISOC or involve ISOC staff.
Under the new IASA 2.0 structure, the IETF LLC is solely responsible for
its administration, including the IETF Trust, IAB, IESG, IETF
working groups, and other IETF processes. A further exploration of
this can be found in Section 4 of <xref
target="I-D.ietf-iasa2-rfc4071bis"/>. target="RFC8711" sectionFormat="of" section="4" format="default"/>.
    <section title="IANA Considerations"> numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This document introduces has no new IANA considerations.</t> actions.</t>
    <section title="Security Considerations"> numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>This document introduces no new security considerations.</t>
    <section title="Privacy Considerations"> numbered="true" toc="default">
      <name>Privacy Considerations</name>
      <t>This document introduces no new privacy considerations.</t>

<section anchor="ack" title="Acknowledgements">

The authors would like to thank Erik Huizer for his contribution as
the author of <xref target="RFC2031"/>, which this document


<section anchor="changes" title="Changes from Previous Versions">
	<t>RFC Editor: Please remove this section upon publication.</t>
	<t>-00: Initial version published</t>
	<t>-01: Several key updates to prepare WGLC based on WG feedback</t>
	<t>-02: Fixed nits identified by Brian Carpenter on 12-21-2018, and text on the tax status from John Levine.</t>
	<t>-03: As we entered IESG review, added a short description

        <name>Normative References</name>
        <!-- draft-ietf-iasa2-rfc4071bis-11 [RFC8711] in cluster -->
        <reference anchor="RFC8711" target="https://www.rfc-editor.org/info/rfc8711">
            <title>Structure of what ISOC does (in relation to the IETF)
		that can be used IETF Administrative Support Activity, Version 2.0</title>
            <author initials="B." surname="Haberman">
            <author initials="J." surname="Hall">
            <author initials="J." surname="Livingood">
            <date month="January" year="2020"/>
	  <seriesInfo name='BCP' value='101'/>
          <seriesInfo name="RFC" value="8711"/>
          <seriesInfo name="DOI" value="10.17487/RFC8711"/>
        <name>Informative References</name>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2027.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2028.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2031.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2850.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3677.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4071.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4371.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5378.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6756.xml"/>
        <!-- draft-ietf-iasa2-rfc7437bis-09 - in external material by both cluster: RFC8713 -->
        <reference anchor="RFC8713" target="https://rfc-editor.org/info/rfc8713">
            <title>IAB, IESG, and IETF LLC Selection, Confirmation, and
                         Recall Process: Operation of the IETF Nominating and ISOC.</t>
	<t>-04: Clarification adding text
                         Recall Committees</title>

            <author initials="M." surname="Kucherawy" role="editor">

            <author initials="R." surname="Hinden" role="editor">

            <author initials="J." surname="Livingood" role="editor">

            <date month="January" year="2020"/>
          <seriesInfo name="BCP" value="10"/>
          <seriesInfo name="RFC" value="8713"/>
          <seriesInfo name="DOI" value="10.17487/RFC8713"/>


        <!-- draft-ietf-iasa2-trust-update-03 - in cluster: RFC8714 -->
	<reference anchor='RFC8714' target="https://www.rfc-editor.org/info/rfc8714">
	    <title>Update to Section 6 on legal issue.</t>
	<t>-05: Fix nits</t>
	<t>-06: Fix nits and other changes from IESG review</t>
	<t>-07: Fixed one missed nit from IESG review</t>
	<t>-08: Fixed two typographical errors</t>



  <references title="Normative References">

<references title="Informative References">


        &I-D.ietf-iasa2-trust-update; the Process for Selection of Trustees for the IETF Trust</title>

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

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

            <date month="January" year="2020"/>

	  <seriesInfo name='BCP' value='101'/>
          <seriesInfo name="RFC" value="8714"/>
          <seriesInfo name="DOI" value="10.17487/RFC8714"/>


        <!-- draft-ietf-iasa2-trust-rationale-03 - in cluster: RFC8715 -->
	<reference anchor="BCP10" target="https://www.rfc-editor.org/refs/ref-bcp10.txt"> anchor='RFC8715' target="https://www.rfc-editor.org/info/rfc8715">
	    <title>Discussion of the IASA 2.0 Changes as They Relate to the IETF Trust</title>

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

            <date month="January" year="2020"/>

          <seriesInfo name="RFC" value="8715"/>
          <seriesInfo name="DOI" value="10.17487/RFC8715"/>

        <!-- URL https://www.internetsociety.org/mission/ works -->
        <reference anchor="ISOC-Mission" target="https://www.internetsociety.org/mission/">
            <title>Internet Society Mission</title>
              <organization>Internet Society</organization>
        <!-- URL https://www.ietf.org/documents/180/IETF-LLC-Agreement.pdf works.
However, if one were to locate the LLC Agreement by navigating from www.ietf.org, then the URL is
        <reference anchor='OpAgreement' anchor="OpAgreement" target="https://www.ietf.org/documents/180/IETF-LLC-Agreement.pdf">
            <title abbrev='Operating Agreement'>Limited abbrev="Operating Agreement">Limited Liability Company
Agreement of IETF Administration LLC</title>
<author />
            <date month='August' year='2018' /> month="August" year="2018"/>
    <section anchor="ack" numbered="false" toc="default">
The authors would like to thank <contact fullname="Erik Huizer"/> for his contribution as
the author of <xref target="RFC2031" format="default"/>, which this document