<?xml version='1.0' encoding='utf-8'?>
<!-- xml2rfc v2v3 conversion 2.34.0 -->

<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<rfc 
xmlns:xi="http://www.w3.org/2001/XInclude" 
number="8717"
updates="2028, 2418, 3005, 3710, 3929, 4633, 6702" 
obsoletes="" 
docName="draft-ietf-iasa2-consolidated-upd-07" 
category="bcp" 
consensus="true"
submissionType="IETF" 
ipr="trust200902" 
sortRefs="true" 
symRefs="true" 
tocInclude="true" 
xml:lang="en" 
version="3">

  <front>
	 
    <title abbrev="IASA 2.0 Consolidated Updates">
	    IETF Administrative Support Activity 2.0:
Consolidated Updates to IETF Administrative Terminology</title>
    <seriesInfo name="RFC" value="8717"/>
    <seriesInfo name="BCP" value="101"/>
    <author fullname="John C Klensin" initials="J." surname="Klensin" role="editor">
      <organization/>
      <address>
        <postal>
          <street>1770 Massachusetts Ave, Ste 322</street>
          <city>Cambridge</city>
          <region>MA</region>
          <code>02140</code>
          <country>USA</country>
        </postal>
        <phone>+1 617 245 1457</phone>
        <email>john-ietf@jck.com</email>
      </address>
    </author>
    <date month="February" year="2020"/>
    <area>General</area>
    <workgroup>IASA2</workgroup>

<keyword>IASA</keyword>

    <abstract>
      <t>In 2018, the IETF began the transition to a new
		 administrative structure and updated its IETF
		 Administrative Support Activity (IASA) to a new "IASA 2.0"
		 structure.  
		 In addition to more substantive changes that are described in
		 other documents, the transition to the 2018 IETF
		 Administrative Support structure changes several position
		 titles and organizational relationships that are referenced
		 elsewhere.  Rather than reissue those referencing documents
		 individually,
		 this specification provides updates to them and deprecates
		 some now-obsolete documents to ensure that
		 there is no confusion due to these changes.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="Intro" numbered="true" toc="default">
      <name>Introduction</name>
      <t>In 2018, the IETF began the transition to a new
		 administrative structure, and updated its IETF
		 Administrative Support Activity (IASA) to a new "IASA 2.0"
		 structure <xref target="RFC8711" format="default"/>.   Key
		 IASA 2.0 changes have been 
		 specified in a series of documents, including
		 changes to the IETF Trust <xref target="RFC8714" format="default"/>,
		 the rationale for it <xref target="RFC8715" format="default"/>,
		 a new defining document for the IETF Administration LLC <xref target="LLC-Agreement" format="default"/> (informally called the "IETF
		 LLC" or just "the LLC" in places in this document and elsewhere),
		 and adjustments to the procedures for nominations and
		 selections for relevant positions
		 <xref target="RFC8713" format="default"/>.</t>
      <t>In addition to more substantive changes that are described in
	   those and other documents, the IASA 2.0 structure changes
	   several position titles and organizational relationships that
	   are referenced in other documents. Rather than reissue those
	   documents individually, this document provides a unified
	   update to them. </t>

      <t> This document updates RFCs 2028, 2418, 3005, 3710, 3929,
		 4633, and 6702 (citations in context below) 
		 to make those terminology and related changes.  In addition,
		 with the authorization of the IAB, it requests
		 that the Informational RFC 3716 be made
		 Historic (see <xref target="MakeHistoric" format="default"/>).
		 The sections that follow identify the details of the
		 relevant documents and the required changes. </t>

    </section>

	<section anchor="ExecDir-Managing" numbered="true" toc="default">
      <name>Where Appropriate, Replacement of the IETF Executive Director Position with the Managing Director, IETF Secretariat</name>
	  
      <t>Under the IASA 2.0 structure, most of the responsibilities
		  of the former position of IETF
		  Executive Director have been assigned to a new position (or at
		  least title) of Managing Director, IETF Secretariat.
		  An "Executive Director" title is now associated with
		  different, and largely new, responsibilities as an officer
		  of the IETF Administration
		  LLC.  These changes are covered in the description of the
		  new structural arrangements <xref target="RFC8711" format="default"/>.</t>
      <t> This document applies that change to the following:</t>
      <ul spacing="normal">
        <li>RFC 2028, "The Organizations Involved in the IETF
                                Standards Process", <xref target="RFC2028" sectionFormat="comma" section="3.3" format="default"/>.</li>
        <li>RFC 2418, "IETF Working Group Guidelines and Procedures",
                                <xref target="RFC2418" sectionFormat="comma" section="1" format="default"/>.</li>
        <li>RFC 3710, "An IESG Charter",
                                <xref target="RFC3710" sectionFormat="comma" section="2" format="default"/>.</li>
        <li>RFC 3929, "Alternative Decision Making Processes for
                 Consensus-Blocked Decisions in the IETF",
                             <xref target="RFC3929" format="default"/>, Sections <xref target="RFC3929" section="4.1.1" sectionFormat="bare"/>
                             and <xref target="RFC3929" section="4.3" sectionFormat="bare"/>
                                 (twice).</li>
        <li>RFC 4633, "Experiment in Long-Term Suspensions From
              Internet Engineering Task Force (IETF) Mailing
                          Lists", <xref target="RFC4633" sectionFormat="comma" section="1" format="default"/>.</li>
        <li>RFC 6702, "Promoting Compliance with Intellectual
                           Property Rights (IPR) Disclosure Rules",
                           <xref target="RFC6702" section="5" sectionFormat="comma"/>.</li>
      </ul>
      <t> Note that the current description of the Internet
			 Standards Process <xref target="RFC2026" format="default"/> does not
			 require an update by this document for this purpose
			 because the reference 
			 to the IETF Executive Director in RFC 2026 was replaced
			 by a document <xref target="RFC3979" format="default"/> that precedes the current
			 effort, and that document was, in turn,
			 obsoleted by <xref target="RFC8179" format="default">RFC 8179</xref>.</t>
    </section>
    <section numbered="true" toc="default">
      <name>Removal of the IETF Executive Director as an Option</name>
      <t> In a few cases, it is no longer appropriate for either the
		  Managing Director, IETF Secretariat (former IETF Executive
		  Director position) or the new IETF Executive Director (for
		  the LLC) to perform a particular historical function.
          The relevant documents are updated to remove
		  the IETF Executive Director from the list of people with
		  specific responsibilities or authority.  Those documents
		  will not be updated to use "Managing Director, IETF
		  Secretariat" but, instead, the mention of the position will
		  simply be dropped.</t>
      <t> This document applies that change to the following:
      </t>
      <ul spacing="normal">
        <li>RFC 3005, "IETF Discussion List Charter"
				<xref target="RFC3005" format="default"/>, section titled "Charter for
				the IETF Discussion List".  This document is modified
				to remove the authorization for the IETF Executive
				Director to restrict people from posting, etc.</li>
      </ul>
    </section>
    <section anchor="MakeHistoric" numbered="true" toc="default">
      <name>Deprecated Documents</name>

      <section numbered="true" toc="default">
        <name>Documents Whose Context Is Changed by This Specification</name>
        <t>Both of the documents that follow were obsoleted in 2017
			 by <xref target="RFC8179" format="default">RFC 8179</xref>, which changed
			 mentions of the IETF Executive Director to point to
		     the IETF Secretariat more generally.</t>
        <ul spacing="normal">
          <li>
            <xref target="RFC3979" format="default">RFC 3979</xref></li>
          <li>
            <xref target="RFC4879" format="default">RFC 4879</xref></li>
        </ul>
      </section>
      <section numbered="true" toc="default">
        <name>General Description of the IETF Administrative Model</name>
		
        <t><xref target="RFC3716" format="default">RFC 3716</xref> was a
		report of an IAB Advisory Committee that served as a
		starting point for the work that led to the original
		IASA structure.  That report was an IAB document
		rather than an IETF one.  The IAB approved a proposal
		to move RFC 3716 to Historic on March 6, 2019
                <xref target="IAB-3716-Historic" format="default"/>. </t>
      </section>
    </section>

    <section anchor="Security" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>The changes specified in this document are matters of
		 terminology and organizational structure derived from
		 documents it references.  It should have no effect on
		 Internet security.</t>
    </section>
  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <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.2418.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3005.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3710.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6702.xml"/>

        <reference anchor="RFC8711" target="https://www.rfc-editor.org/info/rfc8711">
          <front>
            <title>Structure of the IETF Administrative Support Activity, Version 2.0</title>
            <author initials="B." surname="Haberman">
              <organization/>
            </author>
            <author initials="J." surname="Hall">
              <organization/>
            </author>
            <author initials="J." surname="Livingood">
              <organization/>
            </author>
            <date year="2020" month="February"/>
          </front>
          <seriesInfo name="BCP" value="101"/>
          <seriesInfo name="RFC" value="8711"/>
          <seriesInfo name="DOI" value="10.17487/RFC8711"/>
        </reference>


        <reference anchor="RFC8714" target="https://www.rfc-editor.org/info/rfc8714">
          <front>
            <title>Update to the Process for Selection of Trustees for
			 the IETF Trust</title>
            <author initials="J." surname="Arkko">
              <organization/>
            </author>
            <author initials="T." surname="Hardie">
              <organization/>
            </author>
            <date month="February" year="2020"/>
          </front>
          <seriesInfo name="BCP" value="101"/>
          <seriesInfo name="RFC" value="8714"/>
          <seriesInfo name="DOI" value="10.17487/RFC8714"/>
        </reference>


        <reference anchor="RFC8715" target="https://www.rfc-editor.org/info/rfc8715">
          <front>
            <title>IETF Administrative Support Activity 2.0: Update to the
	    Process for Selection of Trustees for the IETF Trust</title>
            <author initials="J." surname="Arkko">
              <organization/>
            </author>
            <date month="February" year="2020"/>
          </front>
          <seriesInfo name="RFC" value="8715"/>
          <seriesInfo name="DOI" value="10.17487/RFC8715"/>
        </reference>

        <reference anchor="LLC-Agreement" target="https://www.ietf.org/documents/180/IETF-LLC-Agreement.pdf">
          <front>
            <title>Limited Liability Company Agreement of IETF Administration LLC</title>
            <author>
              <organization>IETF Administration LLC</organization>
            </author>
            <date year="2018" month="August" day="28"/>
          </front>
        </reference>

        <reference anchor="RFC8713" target="https://www.rfc-editor.org/info/rfc8713">
          <front>
            <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/>
            </author>
            <author initials="R." surname="Hinden" role="editor">
              <organization/>
            </author>
            <author initials="J." surname="Livingood" role="editor">
              <organization/>
            </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>
      </references>
      <references>

        <name>Informative References</name>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2026.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3716.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3929.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3979.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4633.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4879.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8179.xml"/>

        <reference anchor="IAB-3716-Historic" target="https://www.iab.org/documents/minutes/minutes-2019/iab-minutes-2019-03-06/">
          <front>
            <title>IAB Minutes 2019-03-06</title>
            <author>
              <organization>Internet Architecture Board</organization>
            </author>
            <date year="2019" month="March" day="6"/>
          </front>
       </reference>

      </references>
    </references>

    <section anchor="Acknowledgments" numbered="false" toc="default">
      <name>Acknowledgments</name>
      <t> <contact fullname="Brian Carpenter's"/> careful checking and identification of
		 documents that did, and did not, require consideration was
		 essential to the document in its current form.  He also made
		 several other significant contributions.  <contact fullname="Bob Hinden"/> also
		 gave the document a careful reading and made useful
		 suggestions.  In additional to the above, <contact fullname="Alissa Cooper"/>,
		 <contact fullname="Eliot Lear"/>, <contact fullname="Heather Flanagan"/> (the RFC Series Editor), and the
		 current membership to the IAB helped sort out the handing of
		 RFC 3716.</t>
    </section>
    <section numbered="false" toc="default">
      <name>Contributors</name>
      <t><contact fullname="Jason Livingood"/> did the hard work of identifying the
		  documents that required updating and supplied considerable
		  text used in this document.</t>
    </section>
  </back>
</rfc>
