<?xmlversion="1.0" encoding="US-ASCII"?> <!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" ?>version='1.0' encoding='utf-8'?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="info" consensus="true" docName="draft-ietf-iasa2-rfc2031bis-08" indexInclude="true" ipr="trust200902"obsoletes="2031">number="8712" obsoletes="2031" prepTime="2020-02-26T16:54:45" 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-rfc2031bis-08" rel="prev"/> <link href="https://dx.doi.org/10.17487/rfc8712" rel="alternate"/> <link href="urn:issn:2070-1721" rel="alternate"/> <front> <title abbrev="The IETF-ISOCRelationship"> TheRelationship">The IETF-ISOCRelationship </title>Relationship</title> <seriesInfo name="RFC" value="8712" stream="IETF"/> <author fullname="Gonzalo Camarillo" initials="G." surname="Camarillo"><organization>Ericsson</organization><organization showOnFrontPage="true">Ericsson</organization> <address> <email>Gonzalo.Camarillo@ericsson.com</email> </address> </author> <author fullname="Jason Livingood" initials="J." surname="Livingood"><organization>Comcast</organization><organization showOnFrontPage="true">Comcast</organization> <address> <email>jason_livingood@comcast.com</email> </address> </author> <datemonth="August" year="2019" />month="02" year="2020"/> <area>General</area> <workgroup>IETF Administrative Support Activity 2</workgroup><abstract> <t><keyword>IASA</keyword> <abstract pn="section-abstract"> <t pn="section-abstract-1"> This documentsummarisessummarizes the Internet Engineering Task Force (IETF) - Internet Society (ISOC) relationship, following a major revision to the structure of the IETF Administrative Support Activity (IASA) in 2018. The IASA was revised under a new "IASA 2.0" structure by the IASA2 Working Group, which changed the IETF's administrative, legal, and financial structure. As a result, it also changed the relationship between the IETF and ISOC, which made it necessary to revise RFC 2031. </t> </abstract> <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 document is not an Internet Standards Track specification; it is published for informational purposes. </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). Not all documents approved by the IESG are candidates for any level of Internet Standard; see 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/rfc8712" brackets="none"/>. </t> </section> <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" 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" pn="section-toc.1"> <name slugifiedName="name-table-of-contents">Table of Contents</name> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.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 derivedContent="" format="title" sectionFormat="of" target="name-introduction-and-history">Introduction and History</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 derivedContent="" format="title" sectionFormat="of" target="name-philosophical-relationship-">Philosophical Relationship with ISOC</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 derivedContent="" format="title" sectionFormat="of" target="name-main-division-of-responsibi">Main Division of Responsibilities between IETF and ISOC</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 derivedContent="" format="title" sectionFormat="of" target="name-isocs-role-in-the-ietf-stan">ISOC's Role in the IETF Standards Process</xref></t> </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 derivedContent="" format="title" sectionFormat="of" target="name-the-ietfs-role-in-isoc">The IETF's Role in ISOC</xref></t> </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 derivedContent="" format="title" sectionFormat="of" target="name-legal-relationship-with-iso">Legal Relationship with ISOC</xref></t> </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 derivedContent="" format="title" sectionFormat="of" target="name-financial-and-administrativ">Financial and Administrative Relationship with ISOC</xref></t> </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 derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t> </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 derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t> </li> <li pn="section-toc.1-1.10"> <t keepWithNext="true" pn="section-toc.1-1.10.1"><xref derivedContent="10" format="counter" sectionFormat="of" target="section-10"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-privacy-considerations">Privacy Considerations</xref></t> </li> <li pn="section-toc.1-1.11"> <t keepWithNext="true" pn="section-toc.1-1.11.1"><xref derivedContent="11" format="counter" sectionFormat="of" target="section-11"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.11.2"> <li pn="section-toc.1-1.11.2.1"> <t keepWithNext="true" pn="section-toc.1-1.11.2.1.1"><xref derivedContent="11.1" format="counter" sectionFormat="of" target="section-11.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t> </li> <li pn="section-toc.1-1.11.2.2"> <t keepWithNext="true" pn="section-toc.1-1.11.2.2.1"><xref derivedContent="11.2" format="counter" sectionFormat="of" target="section-11.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t> </li> </ul> </li> <li pn="section-toc.1-1.12"> <t keepWithNext="true" pn="section-toc.1-1.12.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t> </li> <li pn="section-toc.1-1.13"> <t keepWithNext="true" pn="section-toc.1-1.13.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t> </li> </ul> </section> </toc> </front> <middle> <sectiontitle="Introduction and History"> <t>numbered="true" toc="include" removeInRFC="false" pn="section-1"> <name slugifiedName="name-introduction-and-history">Introduction and History</name> <t pn="section-1-1"> 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. </t><t><t pn="section-1-2"> 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 ofdedicateddedicated, 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 andface-to-face)face-to-face), they strive to achieve rough consensus and implement the standards through running code. </t><t><t pn="section-1-3"> 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-technicalNontechnical issues, such as legal, administrative, and financial issues had long been an undesirable but unavoidable part of the IETF. To address theseissues in 1995issues, the IETF established the Poised95 WorkingGroup.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 tohonourhonor the IETF credo: "Rough consensus and running code". </t><t><t pn="section-1-4"> 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 behalfofof, and in close cooperationwithwith, the IETF. This led to documenting things such as the IETF standards process <xreftarget="RFC2026"/>,target="RFC2026" format="default" sectionFormat="of" derivedContent="RFC2026"/>, the IETF organizational structure <xreftarget="RFC2028"/>,target="RFC2028" format="default" sectionFormat="of" derivedContent="RFC2028"/>, the IETF Nominating Committee (NomCom) procedures<eref target="BCP10"/>,<xref target="RFC2027" format="default" sectionFormat="of" derivedContent="RFC2027"/>, and the IETF-ISOC relationship <xreftarget="RFC2031"/>.target="RFC2031" format="default" sectionFormat="of" derivedContent="RFC2031"/>. </t><t><t pn="section-1-5"> 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 <xreftarget="RFC4071"/>target="RFC4071" format="default" sectionFormat="of" derivedContent="RFC4071"/> and <xreftarget="RFC4371"/>.target="RFC4371" format="default" sectionFormat="of" derivedContent="RFC4371"/>. </t><t><t pn="section-1-6"> 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. </t><t><t pn="section-1-7"> As a result of the IASA 2.0 structure <xreftarget="I-D.ietf-iasa2-rfc4071bis"/>target="RFC8711" format="default" sectionFormat="of" derivedContent="RFC8711"/> and formation of the IETF LLC, the relationship between the IETF and ISOC has changed. This documentsummarisessummarizes the current state of the IETF-ISOC relationship at a high level and replaces <xreftarget="RFC2031"/>.target="RFC2031" format="default" sectionFormat="of" derivedContent="RFC2031"/>. </t> </section> <sectiontitle="Philosophicalnumbered="true" toc="include" removeInRFC="false" pn="section-2"> <name slugifiedName="name-philosophical-relationship-">Philosophical Relationship withISOC"> <t>ISOC</name> <t pn="section-2-1"> 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:Advancingadvancing the development and application of Internet infrastructure, technologies, and open standards<eref target="ISOC-Mission"/>.<xref target="ISOC-Mission" format="default" sectionFormat="of" derivedContent="ISOC-Mission"/>. </t> </section> <sectiontitle="Mainnumbered="true" toc="include" removeInRFC="false" pn="section-3"> <name slugifiedName="name-main-division-of-responsibi">Main Division of Responsibilities between IETF andISOC"> <t>ISOC</name> <t pn="section-3-1"> 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). </t> </section> <section anchor="standards"title="ISOC'snumbered="true" toc="include" removeInRFC="false" pn="section-4"> <name slugifiedName="name-isocs-role-in-the-ietf-stan">ISOC's Role in the IETF StandardsProcess"> <t>Process</name> <t pn="section-4-1"> 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 <xreftarget="RFC7437"/>,target="RFC8713" format="default" sectionFormat="of" derivedContent="RFC8713"/>, and by acting as the last resort in the appeals process, as described in <xreftarget="RFC2026"/>.target="RFC2026" format="default" sectionFormat="of" derivedContent="RFC2026"/>. </t><t><t pn="section-4-2"> 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 <xreftarget="RFC6756"/>.target="RFC6756" format="default" sectionFormat="of" derivedContent="RFC6756"/>. </t><t><t pn="section-4-3"> ISOC also supports the IETF standards processmoreindirectly (e.g., by promoting it in relevant communities) through several programs. For example, ISOC's PolicymakersProgramProgramme to the IETF (usually referred to simply as ISOC'spolicy 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'sDeploy360 program, which helps encouragework in encouraging andsupportsupporting the deployment of IETFstandards like DNSSEC <xref target="RFC4033"/> and IPv6 <xref target="RFC8200"/>.standards. </t><t><t pn="section-4-4"> 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. </t> </section> <sectiontitle="Thenumbered="true" toc="include" removeInRFC="false" pn="section-5"> <name slugifiedName="name-the-ietfs-role-in-isoc">The IETF's Role inISOC"> <t>ISOC</name> <t pn="section-5-1"> The IETF plays a role in the governance of ISOC. Per ISOC'sby-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 <xreftarget="RFC3677"/>.target="RFC3677" format="default" sectionFormat="of" derivedContent="RFC3677"/>. </t><t><t pn="section-5-2"> The charter of the IAB (Internet Architecture Board) <xreftarget="RFC2850"/>target="RFC2850" format="default" sectionFormat="of" derivedContent="RFC2850"/> 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. </t> </section> <sectiontitle="Legalnumbered="true" toc="include" removeInRFC="false" pn="section-6"> <name slugifiedName="name-legal-relationship-with-iso">Legal Relationship withISOC"> <t>ISOC</name> <t pn="section-6-1"> 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 theISOC/IETFISOC / IETF LLC Agreement <xreftarget="OpAgreement"/>target="OpAgreement" format="default" sectionFormat="of" derivedContent="OpAgreement"/> on August 27, 2018, and governs the relationship between the IETF LLC and ISOC. </t><t><t pn="section-6-2"> The IETF Trust, documented in <xreftarget="RFC5378"/>,target="RFC5378" format="default" sectionFormat="of" derivedContent="RFC5378"/>, and updated in <xreftarget="I-D.ietf-iasa2-trust-rationale"/>target="RFC8714" format="default" sectionFormat="of" derivedContent="RFC8714"/> and <xreftarget="I-D.ietf-iasa2-trust-update"/>,target="RFC8715" format="default" sectionFormat="of" derivedContent="RFC8715"/>, provides legal protection for the RFCseriesSeries 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 Trustees. </t> </section> <sectiontitle="Financialnumbered="true" toc="include" removeInRFC="false" pn="section-7"> <name slugifiedName="name-financial-and-administrativ">Financial and Administrative Relationship withISOC"> <t>ISOC</name> <t pn="section-7-1"> Under the terms of the Operating Agreement <xreftarget="OpAgreement"/>target="OpAgreement" format="default" sectionFormat="of" derivedContent="OpAgreement"/> 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 length. </t><t><t pn="section-7-2"> 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. </t><t><t pn="section-7-3"> 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 inSection 4 of<xreftarget="I-D.ietf-iasa2-rfc4071bis"/>.target="RFC8711" sectionFormat="of" section="4" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8711#section-4" derivedContent="RFC8711"/>. </t> </section> <sectiontitle="IANA Considerations"> <t>Thisnumbered="true" toc="include" removeInRFC="false" pn="section-8"> <name slugifiedName="name-iana-considerations">IANA Considerations</name> <t pn="section-8-1">This documentintroduceshas nonewIANAconsiderations.</t>actions.</t> </section> <sectiontitle="Security Considerations"> <t>Thisnumbered="true" toc="include" removeInRFC="false" pn="section-9"> <name slugifiedName="name-security-considerations">Security Considerations</name> <t pn="section-9-1">This document introduces no new security considerations.</t> </section> <sectiontitle="Privacy Considerations"> <t>Thisnumbered="true" toc="include" removeInRFC="false" pn="section-10"> <name slugifiedName="name-privacy-considerations">Privacy Considerations</name> <t pn="section-10-1">This document introduces no new privacy considerations.</t> </section><section anchor="ack" title="Acknowledgements"> <t> The authors would like to thank Erik Huizer for his contribution as the author of <xref target="RFC2031"/>, which this document replaces. </t> </section> <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</middle> <back> <references pn="section-11"> <name slugifiedName="name-references">References</name> <references pn="section-11.1"> <name slugifiedName="name-normative-references">Normative References</name> <reference anchor="RFC8711" target="https://www.rfc-editor.org/info/rfc8711" quoteTitle="true" derivedAnchor="RFC8711"> <front> <title>Structure ofwhat ISOC does (in relation totheIETF) that can beIETF Administrative Support Activity, Version 2.0</title> <author initials="B." surname="Haberman"> <organization showOnFrontPage="true"/> </author> <author initials="J." surname="Hall"> <organization showOnFrontPage="true"/> </author> <author initials="J." surname="Livingood"> <organization showOnFrontPage="true"/> </author> <date month="February" year="2020"/> </front> <seriesInfo name="BCP" value="101"/> <seriesInfo name="RFC" value="8711"/> <seriesInfo name="DOI" value="10.17487/RFC8711"/> </reference> </references> <references pn="section-11.2"> <name slugifiedName="name-informative-references">Informative References</name> <reference anchor="ISOC-Mission" target="https://www.internetsociety.org/mission/" quoteTitle="true" derivedAnchor="ISOC-Mission"> <front> <title>Internet Society Mission</title> <author> <organization showOnFrontPage="true">Internet Society</organization> </author> </front> </reference> <reference anchor="OpAgreement" target="https://www.ietf.org/documents/180/IETF-LLC-Agreement.pdf" quoteTitle="true" derivedAnchor="OpAgreement"> <front> <title abbrev="Operating Agreement">Limited Liability Company Agreement of IETF Administration LLC</title> <author> <organization showOnFrontPage="true"/> </author> <date month="August" year="2018"/> </front> </reference> <reference anchor="RFC2026" target="https://www.rfc-editor.org/info/rfc2026" quoteTitle="true" derivedAnchor="RFC2026"> <front> <title>The Internet Standards Process -- Revision 3</title> <author initials="S." surname="Bradner" fullname="S. Bradner"> <organization showOnFrontPage="true"/> </author> <date year="1996" month="October"/> <abstract> <t>This memo documents the process used by the Internet community for the standardization of protocols and procedures. It defines the stages inexternal materialthe standardization process, the requirements for moving a document between stages and the types of documents used during this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="2026"/> <seriesInfo name="DOI" value="10.17487/RFC2026"/> </reference> <reference anchor="RFC2027" target="https://www.rfc-editor.org/info/rfc2027" quoteTitle="true" derivedAnchor="RFC2027"> <front> <title>IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees</title> <author initials="J." surname="Galvin" fullname="J. Galvin"> <organization showOnFrontPage="true"/> </author> <date year="1996" month="October"/> <abstract> <t>The process bybothwhich the members of the IAB and IESG are selected, confirmed, and recalled has been exercised four times since its formal creation. The evolution of the process has relied principally on oral tradition as a means by which the lessons learned could be passed on to successive committees. This document is a self-consistent, organized compilation of the process as it is known today. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="RFC" value="2027"/> <seriesInfo name="DOI" value="10.17487/RFC2027"/> </reference> <reference anchor="RFC2028" target="https://www.rfc-editor.org/info/rfc2028" quoteTitle="true" derivedAnchor="RFC2028"> <front> <title>The Organizations Involved in the IETF Standards Process</title> <author initials="R." surname="Hovey" fullname="R. Hovey"> <organization showOnFrontPage="true"/> </author> <author initials="S." surname="Bradner" fullname="S. Bradner"> <organization showOnFrontPage="true"/> </author> <date year="1996" month="October"/> <abstract> <t>This document describes the individuals and organizations involved in the IETF. This includes descriptions of the IESG, the IETF Working Groups and the relationship between the IETF and the Internet Society. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="11"/> <seriesInfo name="RFC" value="2028"/> <seriesInfo name="DOI" value="10.17487/RFC2028"/> </reference> <reference anchor="RFC2031" target="https://www.rfc-editor.org/info/rfc2031" quoteTitle="true" derivedAnchor="RFC2031"> <front> <title>IETF-ISOC relationship</title> <author initials="E." surname="Huizer" fullname="E. Huizer"> <organization showOnFrontPage="true"/> </author> <date year="1996" month="October"/> <abstract> <t>This memo summarises the issues on IETF - ISOC relationships as the have been discussed by the Poised Working Group. The purpose of the document is to gauge consensus on these issues. And to allow further discussions where necessary. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.</t> </abstract> </front> <seriesInfo name="RFC" value="2031"/> <seriesInfo name="DOI" value="10.17487/RFC2031"/> </reference> <reference anchor="RFC2850" target="https://www.rfc-editor.org/info/rfc2850" quoteTitle="true" derivedAnchor="RFC2850"> <front> <title>Charter of the Internet Architecture Board (IAB)</title> <author> <organization showOnFrontPage="true">Internet Architecture Board</organization> </author> <author initials="B." surname="Carpenter" fullname="B. Carpenter" role="editor"> <organization showOnFrontPage="true"/> </author> <date year="2000" month="May"/> <abstract> <t>This memo documents the composition, selection, roles, and organization of the Internet Architecture Board. It replaces RFC 1601. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="39"/> <seriesInfo name="RFC" value="2850"/> <seriesInfo name="DOI" value="10.17487/RFC2850"/> </reference> <reference anchor="RFC3677" target="https://www.rfc-editor.org/info/rfc3677" quoteTitle="true" derivedAnchor="RFC3677"> <front> <title>IETF ISOC Board of Trustee Appointment Procedures</title> <author initials="L." surname="Daigle" fullname="L. Daigle" role="editor"> <organization showOnFrontPage="true"/> </author> <author> <organization showOnFrontPage="true">Internet Architecture Board</organization> </author> <date year="2003" month="December"/> <abstract> <t>This memo outlines the process by which the IETF makes a selection of an Internet Society (ISOC) Board of Trustees appointment.</t> </abstract> </front> <seriesInfo name="BCP" value="77"/> <seriesInfo name="RFC" value="3677"/> <seriesInfo name="DOI" value="10.17487/RFC3677"/> </reference> <reference anchor="RFC4071" target="https://www.rfc-editor.org/info/rfc4071" quoteTitle="true" derivedAnchor="RFC4071"> <front> <title>Structure of the IETF Administrative Support Activity (IASA)</title> <author initials="R." surname="Austein" fullname="R. Austein" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="B." surname="Wijnen" fullname="B. Wijnen" role="editor"> <organization showOnFrontPage="true"/> </author> <date year="2005" month="April"/> <abstract> <t>This document describes the structure of the IETF Administrative Support Activity (IASA) as an activity housed within the Internet Society (ISOC). It defines the roles and responsibilities of the IETF Administrative Oversight Committee (IAOC), the IETF Administrative Director (IAD), and ISOC in the fiscal and administrative support of the IETF standards process. It also defines the membership and selection rules for the IAOC. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="101"/> <seriesInfo name="RFC" value="4071"/> <seriesInfo name="DOI" value="10.17487/RFC4071"/> </reference> <reference anchor="RFC4371" target="https://www.rfc-editor.org/info/rfc4371" quoteTitle="true" derivedAnchor="RFC4371"> <front> <title>BCP 101 Update for IPR Trust</title> <author initials="B." surname="Carpenter" fullname="B. Carpenter" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="L." surname="Lynch" fullname="L. Lynch" role="editor"> <organization showOnFrontPage="true"/> </author> <date year="2006" month="January"/> <abstract> <t>This document updates BCP 101 to take account of the new IETF Intellectual Property Trust. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="101"/> <seriesInfo name="RFC" value="4371"/> <seriesInfo name="DOI" value="10.17487/RFC4371"/> </reference> <reference anchor="RFC5378" target="https://www.rfc-editor.org/info/rfc5378" quoteTitle="true" derivedAnchor="RFC5378"> <front> <title>Rights Contributors Provide to the IETF Trust</title> <author initials="S." surname="Bradner" fullname="S. Bradner" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="J." surname="Contreras" fullname="J. Contreras" role="editor"> <organization showOnFrontPage="true"/> </author> <date year="2008" month="November"/> <abstract> <t>The IETF policies about rights in Contributions to the IETF are designed to ensure that such Contributions can be made available to the IETF andISOC.</t> <t>-04: Clarification adding textInternet communities while permitting the authors to retain as many rights as possible. This memo details the IETF policies on rights in Contributions to the IETF. It also describes the objectives that the policies are designed to meet. This memo obsoletes RFCs 3978 and 4748 and, with BCP 79 and RFC 5377, replaces Section610 of RFC 2026. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="78"/> <seriesInfo name="RFC" value="5378"/> <seriesInfo name="DOI" value="10.17487/RFC5378"/> </reference> <reference anchor="RFC6756" target="https://www.rfc-editor.org/info/rfc6756" quoteTitle="true" derivedAnchor="RFC6756"> <front> <title>Internet Engineering Task Force and International Telecommunication Union - Telecommunication Standardization Sector Collaboration Guidelines</title> <author initials="S." surname="Trowbridge" fullname="S. Trowbridge" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="E." surname="Lear" fullname="E. Lear" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="G." surname="Fishman" fullname="G. Fishman" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="S." surname="Bradner" fullname="S. Bradner" role="editor"> <organization showOnFrontPage="true"/> </author> <date year="2012" month="September"/> <abstract> <t>This document provides guidance to aid in the understanding of collaboration onlegal issue.</t> <t>-05: Fix nits</t> <t>-06: Fix nitsstandards development between the Telecommunication Standardization Sector of the International Telecommunication Union (ITU-T) andotherthe Internet Engineering Task Force (IETF) of the Internet Society (ISOC). It is an update of and obsoletes RFC 3356. The updates reflect changesfrom IESG review</t> <t>-07: Fixed one missed nit from IESG review</t> <t>-08: Fixed two typographical errors</t> </section> </middle> <back> <references title="Normative References"> &I-D.ietf-iasa2-rfc4071bis; </references> <references title="Informative References"> &RFC2026; &RFC2028; &RFC2031; &RFC2850; &RFC3677; &RFC4033; &RFC4071; &RFC4371; &RFC5378; &RFC6756; &RFC7437; &RFC8200; &I-D.ietf-iasa2-trust-rationale; &I-D.ietf-iasa2-trust-update;in the IETF and ITU-T since RFC 3356 was written. The bulk of this document is common text with ITU-T A Series Supplement 3 (07/2012).</t> <t>Note: This was approved by TSAG on 4 July 2012 as Supplement 3 to the ITU-T A-Series of Recommendations. </t> <t>This document is not an Internet Standards Track specification; it is published for informational purposes.</t> </abstract> </front> <seriesInfo name="RFC" value="6756"/> <seriesInfo name="DOI" value="10.17487/RFC6756"/> </reference> <referenceanchor="BCP10" target="https://www.rfc-editor.org/refs/ref-bcp10.txt">anchor="RFC8713" target="https://www.rfc-editor.org/info/rfc8713" quoteTitle="true" derivedAnchor="RFC8713"> <front><title>BCP10</title> <author/> <date/><title>IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees</title> <author initials="M." surname="Kucherawy" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="R." surname="Hinden" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="J." surname="Livingood" role="editor"> <organization showOnFrontPage="true"/> </author> <date month="February" year="2020"/> </front> <seriesInfo name="BCP" value="10"/> <seriesInfo name="RFC" value="8713"/> <seriesInfo name="DOI" value="10.17487/RFC8713"/> </reference> <referenceanchor="ISOC-Mission" target="https://www.internetsociety.org/mission/">anchor="RFC8714" target="https://www.rfc-editor.org/info/rfc8714" quoteTitle="true" derivedAnchor="RFC8714"> <front><title>ISOC Mission</title> <author/> <date/><title>Update to the Process for Selection of Trustees for the IETF Trust</title> <author initials="J" surname="Arkko" fullname="Jari Arkko"> <organization showOnFrontPage="true"/> </author> <author initials="T" surname="Hardie" fullname="Ted Hardie"> <organization showOnFrontPage="true"/> </author> <date month="February" year="2020"/> </front> <seriesInfo name="BCP" value="101"/> <seriesInfo name="RFC" value="8714"/> <seriesInfo name="DOI" value="10.17487/RFC8714"/> </reference> <referenceanchor='OpAgreement' target="https://www.ietf.org/documents/180/IETF-LLC-Agreement.pdf">anchor="RFC8715" target="https://www.rfc-editor.org/info/rfc8715" quoteTitle="true" derivedAnchor="RFC8715"> <front><title abbrev='Operating Agreement'>Limited Liability Company Agreement<title>IETF Administrative Support Activity 2.0: Update to the Process for Selection of Trustees for the IETFAdministration LLC</title>Trust</title> <author/>initials="J" surname="Arkko" fullname="Jari Arkko"> <organization showOnFrontPage="true"/> </author> <datemonth='August' year='2018' />month="February" year="2020"/> </front> <seriesInfo name="RFC" value="8715"/> <seriesInfo name="DOI" value="10.17487/RFC8715"/> </reference> </references> </references> <section anchor="ack" numbered="false" toc="include" removeInRFC="false" pn="section-appendix.a"> <name slugifiedName="name-acknowledgements">Acknowledgements</name> <t pn="section-appendix.a-1"> The authors would like to thank <contact fullname="Erik Huizer"/> for his contribution as the author of <xref target="RFC2031" format="default" sectionFormat="of" derivedContent="RFC2031"/>, which this document replaces. </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 fullname="Gonzalo Camarillo" initials="G." surname="Camarillo"> <organization showOnFrontPage="true">Ericsson</organization> <address> <email>Gonzalo.Camarillo@ericsson.com</email> </address> </author> <author fullname="Jason Livingood" initials="J." surname="Livingood"> <organization showOnFrontPage="true">Comcast</organization> <address> <email>jason_livingood@comcast.com</email> </address> </author> </section> </back> </rfc>