rfc8717xml2.original.xml   rfc8717.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version='1.0' encoding='utf-8'?>
<!-- updated by Jean Mahoney, converted to v3, /10/31/19 -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <!-- xml2rfc v2v3 conversion 2.34.0 -->
<!-- Getting references from the online citation library.
There has to be one entity for each item to be referenced. -->
<!ENTITY rfc2026 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.
RFC.2026.xml">
<!ENTITY rfc2028 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.
RFC.2028.xml">
<!ENTITY rfc2418 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.
RFC.2418.xml">
<!ENTITY rfc3005 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.
RFC.3005.xml">
<!ENTITY rfc3710 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.
RFC.3710.xml">
<!ENTITY rfc3716 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.
RFC.3716.xml">
<!ENTITY rfc3929 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.
RFC.3929.xml">
<!ENTITY rfc3979 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.
RFC.3979.xml">
<!ENTITY rfc4633 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.
RFC.4633.xml">
<!-- <!ENTITY rfc4844 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/refer
ence.RFC.4844.xml"> -->
<!ENTITY rfc4879 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.
RFC.4879.xml">
<!-- <!ENTITY rfc5377 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/refer
ence.RFC.5377.xml"> -->
<!ENTITY rfc6702 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.
RFC.6702.xml">
<!-- <!ENTITY rfc7500 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/refer
ence.RFC.7500.xml"> -->
<!ENTITY rfc8179 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.
RFC.8179.xml">
<!-- Fudge for XMLmind which doesn't have this built in -->
<!ENTITY nbsp "&#160;">
]>
<!-- Extra statement used by XSLT processors to control the output style. -->
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- Processing Instructions- PIs (for a complete list and description,
see file http://xml.resource.org/authoring/README.html.
You may find that some sphisticated editors are not able to edit PIs when p
alced here.
An alternative position is just inside the rfc elelment as noted below. -->
<!-- Some of the more generally applicable PIs that most I-Ds might want to use
-->
<!-- Try to enforce the ID-nits conventions and DTD validity -->
<?rfc strict="yes" ?>
<!-- Items used when reviewing the document -->
<!-- Controls display of <cref> elements -->
<?rfc comments="yes" ?>
<!-- When no, put comments at end in comments section,
otherwise, put inline -->
<?rfc inline="yes" ?>
<!-- When yes, insert editing marks: editing marks consist of a
string such as <29> printed in the blank line at the
beginning of each paragraph of text. -->
<?rfc editing="no" ?>
<!-- Create Table of Contents (ToC) and set some options for it.
Note the ToC may be omitted for very short documents,but idnits insists on
a ToC
if the document has more than 15 pages. -->
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<!-- If "yes" eliminates blank lines before main section entries. -->
<?rfc tocdepth="3"?>
<!-- Sets the number of levels of sections/subsections... in ToC.
Can be overridden by 'toc="include"/"exclude"' on the section
element-->
<!-- Choose the options for the references.
Some like symbolic tags in the references (and citations) and others prefer
numbers. The RFC Editor always uses symbolic tags.
The tags used are the anchor attributes of the references. -->
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<!-- If "yes", causes the references to be sorted in order of tags.
This doesn't have any effect unless symrefs is "yes"
also. -->
<!-- These two save paper: Just setting compact to "yes" makes savings by not st
arting each
main section on a new page but does not omit the blank lines between list i
tems.
If subcompact is also "yes" the blank lines between list items are also omi
tted. -->
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<!-- end of list of popular I-D processing instructions -->
<!-- This is -07c, the posting version -->
<rfc docName="draft-ietf-iasa2-consolidated-upd-07"
ipr="trust200902" category="bcp"
updates="2028, 2418, 3005, 3710, 3929, 4633, 6702" >
<!-- JcK 20181203: removed 3979, 4879, 8179 from Obsoletes
list
JcK 20190117: removed 4844, 5377
JcK 20190311, removed 3929, 4633 and moved to updates -->
<!-- ***** FRONT MATTER ***** --> <!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> <front>
<title abbrev="IASA2 Consolidated Updates"> <title abbrev="IASA 2.0 Consolidated Updates">
Consolidated IASA 2.0 Updates of IETF Administrative Terminology</tit IETF Administrative Support Activity 2.0:
le> Consolidated Updates to IETF Administrative Terminology</title>
<!-- Before -05 was "Consolidated IASA2-Related Document Updates" <seriesInfo name="RFC" value="8717"/>
Change per email from Brian Carpenter, 20180117 --> <seriesInfo name="BCP" value="101"/>
<author fullname="John C Klensin" initials="J." surname="Klensin" role="edit
<!-- add 'role="editor"' below for the editors if appropriate --> or">
<author fullname="John C Klensin" initials="J.C." surname="Klensin" <organization/>
role="editor">
<organization/>
<address> <address>
<postal> <postal>
<street>1770 Massachusetts Ave, Ste 322</street> <street>1770 Massachusetts Ave, Ste 322</street>
<city>Cambridge</city> <region>MA</region> <city>Cambridge</city>
<region>MA</region>
<code>02140</code> <code>02140</code>
<country>USA</country> <country>USA</country>
</postal> </postal>
<phone>+1 617 245 1457</phone> <phone>+1 617 245 1457</phone>
<email>john-ietf@jck.com</email> <email>john-ietf@jck.com</email>
</address> </address>
</author> </author>
<date month="January" year="2020"/>
<area>General</area>
<workgroup>IASA2</workgroup>
<date month="March" day="11" year="2019" /> <keyword>IASA</keyword>
<!-- Meta-data Declarations --> <!-- [rfced] The abstract does not explicitly mention the RFCs
<area>General</area> that this document updates nor does it explicitly call out the RFC that
this document moves to Historic.
<!-- WG name at the upper left corner of the doc, Original:
IETF fine for individual submissions. You can also Rather than reissue those referencing documents
omit this element in which case it defaults to "Network Working Group" individually, this specification provides updates to them and
- deprecates some now-obsolete documents to ensure that there is no
a hangover from the ancient history of the IETF! --> confusion due to these changes.</t>
<workgroup>IASA2</workgroup>
<!-- You can add <keyword/> elements here. They will be incorporated int Perhaps:
o HTML output Rather than reissue those referencing documents
files in a meta tag but they have no effect on text or nroff output. -- individually, this specification provides updates to RFCs 2028,
> 2418, 3005, 3710, 3929, 4633, and 6702 to make those terminology
<!-- <keyword>Text</keyword> (as many of those elements as needed --> and related changes. In addition, it requests that RFC 3716
be made Historic.
-->
<!-- [JcK 2020-01-20] It is my personal opinion that for a
document of this type, adding that list to the abstract makes
the latter less comprehensible rather than more so, especially
because those two sentences are basically incomprehensible
unless someone happens to have the numbers memorized. Those
sentences also violate the general principle that abstracts
should not contain references, whether the citation anchors are
explicit on not.
There is an additional consideration: If either the RFC Editor
or the IESG insist on such listings, especially in abstracts,
then any document proposed for BCP or Standards Track status
that says, whether explicitly or not, that any previous
document that happens to be inconsistent with it is now
partially obsolete and in need to alignment to the present
document becomes unpublishable. -->
<abstract> <abstract>
<t>In 2018, the IETF began the transition to a new <t>In 2018, the IETF began the transition to a new
administrative structure and updated its IETF administrative structure and updated its IETF
Administrative Support Activity (IASA) to a new "IASA 2.0" Administrative Support Activity (IASA) to a new "IASA 2.0"
structure. structure.
In addition to more substantive changes that are described in In addition to more substantive changes that are described in
other documents, the transition to the 2018 IETF other documents, the transition to the 2018 IETF
Administrative Support structure changes several position Administrative Support structure changes several position
titles and organizational relationships that are referenced titles and organizational relationships that are referenced
elsewhere. Rather than reissue those referencing documents elsewhere. Rather than reissue those referencing documents
individually, individually,
this specification provides updates to them and deprecates this specification provides updates to them and deprecates
some now-obsolete documents to ensure that some now-obsolete documents to ensure that
there is no confusion due to these changes.</t> there is no confusion due to these changes.</t>
</abstract> </abstract>
<!-- Note here if needed
<note title=""><t> .... </t></note> -->
</front> </front>
<middle> <middle>
<section title="Introduction" anchor="Intro"> <section anchor="Intro" numbered="true" toc="default">
<name>Introduction</name>
<t>In 2018, the IETF began the transition to a new <t>In 2018, the IETF began the transition to a new
administrative structure, and updated its IETF administrative structure, and updated its IETF
Administrative Support Activity (IASA) to a new "IASA 2.0" Administrative Support Activity (IASA) to a new "IASA 2.0"
structure <xref target="RFC-Struct"/>. Key IASA 2.0 changes ha structure <xref target="RFC8711" format="default"/>. Key
ve been IASA 2.0 changes have been
<!-- The IETF initiated a major revision of its administrative
support arrangements and procedures in 2018
<xref target="RFC-Struct"/>. Those changes have been -->
specified in a series of documents, including specified in a series of documents, including
<!-- notably a description of --> changes to the IETF Trust <xref target="RFC8714" format="default
changes to the IETF Trust <xref target="RFC-trust-update"/>, "/>,
the rationale for it <xref target="RFC-trust-rationale"/>, the rationale for it <xref target="RFC8715" format="default"/>,
a new defining document for the IETF Administration LLC a new defining document for the IETF Administration LLC <xref ta
<xref target="LLC-Agreement"/> (informally called the "IETF rget="LLC-Agreement" format="default"/> (informally called the "IETF
LLC" or just "the LLC" in places in this document and elsewhere) LLC" or just "the LLC" in places in this document and elsewhere)
,
and adjustments to the procedures for nominations and and adjustments to the procedures for nominations and
selections for relevant positions selections for relevant positions
<xref target="RFC-7437bis"/>.</t> <xref target="RFC8713" format="default"/>.</t>
<t>In addition to more substantive changes that are described in <t>In addition to more substantive changes that are described in
those and other documents, the IASA 2.0 structure changes those and other documents, the IASA 2.0 structure changes
several position titles and organizational relationships that several position titles and organizational relationships that
are referenced in other documents. Rather than reissue those are referenced in other documents. Rather than reissue those
documents individually, this document provides a unified documents individually, this document provides a unified
update to them. </t> update to them. </t>
<!-- Among the substantive changes in those documents are changes
in names of organizations, position titles, and associated <t> This document updates RFCs 2028, 2418, 3005, 3710, 3929,
relationships. 4633, and 6702 (citations in context below)
Rather than reissue those documents individually,
address other topics but mention those names, titles, and
relationships, this specification provides updates to them
to ensure that there is no confusion due to changes in
terminology. -->
<t> This document updates RFCs 2028, 2418, 3005, 3710, 3929,
4633, and <!-- 5377 removed -->
6702 (citations in context below)
to make those terminology and related changes. In addition, to make those terminology and related changes. In addition,
with the authorization of the IAB, it requests with the authorization of the IAB, it requests
that the Informational RFC 3716 be made that the Informational RFC 3716 be made
Historic (see <xref target="MakeHistoric"/>). Historic (see <xref target="MakeHistoric" format="default"/>).
The sections that follow identify the details of the The sections that follow identify the details of the
relevant documents and the required changes. </t> relevant documents and the required changes. </t>
<!-- <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in
<xref target="RFC2119">RFC 2119</xref>.</t> -->
</section> </section>
<!-- <section title="Remove Text About the Connection Between the IAOC and IET <section anchor="ExecDir-Managing" numbered="true" toc="default">
F Trust"> <name>Where Appropriate, Replacement of the IETF Executive Director Positi
<t> Some documents that discuss the IETF Trust or its on with the Managing Director, IETF Secretariat</name>
relationship to the community describe it, or the Trustees,
in relation to the IAOC. That connection must be eliminated to
reflect the new IASA 2.0 structure.
<t> This document applies that change to the following:
<list style="symbols">
<t> <xref target="RFC5377">RFC 5377</xref>, Advice to
the Trustees of the IETF Trust on Rights to Be Gr
anted in IETF Documents.
These changes require dropping "made up of the
members of the IAOC [RFC4371]" after "board of
trustees" in the first paragraph of Section 1 an
d
"which is made up of the members of the IAOC, as
described in [RFC4071] and [RFC4371]"
in the first paragraph of Section 3.
<vspace blankLines="0"/> <cref> RFC Editor pleas
e
note that the bracketed strings above are
quoted
text, not references. </cref></t>
</list></t>
</section> -->
<!-- <section title="Replacement of IAOC with IETF Administration LLC"
anchor="LLCRepl">
<t>All mentions of the IETF Administrative Oversight
Committee (IAOC) that are not removed by the prior
section, shall be updated and replaced by the IETF
Administration LLC (IETF-LLC). This is necessary because
the IAOC is phased out under the IASA 2.0 structure. </t>
<t> This document applies that change to the following:
<list style="symbols">
<t><xref target="RFC4844">RFC 4844</xref>, the RFC
Series and RFC Editor Sections 3.3, 3.4, and 4.</
t>
<t><xref target="RFC7500">RFC 7500</xref> Principles for
Operation of Internet Assigned Numbers Authority
(IANA) Registries, Section 3.4. This means that t
he
IETF LLC, the body responsible for IETF
administrative and financial matters, maintains a
n
SLA with the current registry operator, the Inter
net
Corporation for Assigned Names and Numbers (ICANN
).
It also means that both the Internet Architecture
Board (IAB) and the IETF LLC are accountable to t
he
larger Internet community for the IANA registries
.</t>
</list></t>
</section> -->
<section title="Where Appropriate, Replacement of the IETF Executive Dire <t>Under the IASA 2.0 structure, most of the responsibilities
ctor position with the Managing Director, IETF Secretariat"
anchor="ExecDir-Managing">
<t>Under the IASA 2.0 structure, most of the responsibilities
of the former position of IETF of the former position of IETF
Executive Director been assigned to a new position (or at Executive Director have been assigned to a new position (or at
least title) of Managing Director of the IETF Secretariat. least title) of Managing Director, IETF Secretariat.
An "Executive Director" title is now associated with An "Executive Director" title is now associated with
different, and largely new, responsibilities as an Officer different, and largely new, responsibilities as an officer
of the IETF Administration of the IETF Administration
LLC. These changes are described in the description of the LLC. These changes are covered in the description of the
new structural arrangements <xref target="RFC-Struct"/>.</t> new structural arrangements <xref target="RFC8711" format="defa
<t> This document applies that change to the following: ult"/>.</t>
<!-- RFC Editor: the inconsistency in the positioning of <t> This document applies that change to the following:</t>
section numbers in citations below is deliberate, to call <ul spacing="normal">
your attention to an issue about this type of reference that <li>RFC 2028, "The Organizations Involved in the IETF
I've been commenting/ inquiring/ complaining about since Standards Process", <xref target="RFC2028" secti
1999. Fix it however you like. --> onFormat="comma" section="3.3" format="default"/>.</li>
<list style="symbols"> <li>RFC 2418, "IETF Working Group Guidelines and Procedures",
<t>RFC 2028, The Organizations Involved in the IETF <xref target="RFC2418" sectionFormat="comma" sec
Standards Process <xref target="RFC2028"/>, tion="1" format="default"/>.</li>
Section 3.3.</t> <li>RFC 3710, "An IESG Charter",
<xref target="RFC3710" sectionFormat="comma" sec
<t>RFC 2418, IETF Working Group Guidelines and Procedure tion="2" format="default"/>.</li>
s <li>RFC 3929, "Alternative Decision Making Processes for
<xref target="RFC2418"/>, Section 1.</t> Consensus-Blocked Decisions in the IETF",
<xref target="RFC3929" format="default"/>, Sections
<t>RFC 3710, An IESG Charter, Section 2 <xref target="RFC3929" section="4.1.1" sectionFormat="bare"/>
<xref target="RFC3710"/>.</t> and <xref target="RFC3929" section="4.3" sectionFor
mat="bare"/>
<t>RFC 3929, Alternative Decision Making Processes for (twice).</li>
Consensus-Blocked Decisions in the IETF <li>RFC 4633, "Experiment in Long-Term Suspensions From
<xref target="RFC3929"/>, Sections 4.1.1 and 4.3
(twice).</t>
<t>RFC 4633, Experiment in Long-Term Suspensions From
Internet Engineering Task Force (IETF) Mailing Internet Engineering Task Force (IETF) Mailing
Lists <xref target="RFC4633"/>, Section 1.</t> Lists", <xref target="RFC4633" sectionFormat="comma" s
ection="1" format="default"/>.</li>
<t>RFC 6702, Promoting Compliance with Intellectual <li>RFC 6702, "Promoting Compliance with Intellectual
Property Rights (IPR) Disclosure Rules, Property Rights (IPR) Disclosure Rules",
Section 5 <xref target="RFC6702"/>.</t> <xref target="RFC6702" section="5" sectionFormat="com
ma"/>.</li>
</list></t> </ul>
<t> Note that the current description of the Internet <t> Note that the current description of the Internet
Standards Process <xref target="RFC2026"/> does not Standards Process <xref target="RFC2026" format="default
"/> does not
require an update by this document for this purpose require an update by this document for this purpose
because the reference because the reference
to the IETF Executive Director in RFC 2026 was replaced to the IETF Executive Director in RFC 2026 was replaced
by a document that precedes the current by a document <xref target="RFC3979" format="default"/>
effort <xref target="RFC3979"/> and that was, in turn, that precedes the current
obsoleted by <xref target="RFC8179">RFC 8179</xref>.</t> effort, and that document was, in turn,
</section> obsoleted by <xref target="RFC8179" format="default">RFC
8179</xref>.</t>
<section title="Remove the IETF Executive Director as an Option"> </section>
<t> In a few cases, it is no longer appropriate for either the <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 Managing Director, IETF Secretariat (former IETF Executive
Director position) or the new IETF Executive Director (for Director position) or the new IETF Executive Director (for
the LLC) to perform a particular historical function. the LLC) to perform a particular historical function.
The relevant documents are updated to remove The relevant documents are updated to remove
the IETF Executive Director from the list of people with the IETF Executive Director from the list of people with
specific responsibilities or authority. Those documents specific responsibilities or authority. Those documents
will not be updated to use "Managing Director, IETF will not be updated to use "Managing Director, IETF
Secretariat" but, instead, the mention of the position will Secretariat" but, instead, the mention of the position will
simply be dropped.</t> simply be dropped.</t>
<t> This document applies that change to the following: <t> This document applies that change to the following:
<list style="symbols"> </t>
<t>RFC 3005, IETF Discussion List Charter <ul spacing="normal">
<xref target="RFC3005"/>, section titled "Charter <li>RFC 3005, "IETF Discussion List Charter"
for <xref target="RFC3005" format="default"/>, sectio
n titled "Charter for
the IETF Discussion List". This document is modi fied the IETF Discussion List". This document is modi fied
to remove the authorization for the IETF Executiv e to remove the authorization for the IETF Executiv e
Director to restrict people from posting, etc.</t Director to restrict people from posting, etc.</l
> i>
<!-- Jason: As a result, only the IETF Chair, </ul>
or a sergeant-at-arms appointed by the Chair, </section>
are <section anchor="MakeHistoric" numbered="true" toc="default">
empowered to do so. --> <name>Deprecated Documents</name>
</list></t>
</section>
<section title="Deprecated Documents" anchor="MakeHistoric">
<t><cref> Note to the WG, IESG, and RFC Editor: I hope this
section correctly reflects the conclusions of discussions in
and with the WG. If it does not, the issues should
certainly be identified and fixed. However, details of
some of the actions are the responsibility of the RFC Editor
and RFC 3716 is an IAB document containing the report of an
IAB Advisory Committee. If that text, especially the
phrasing of various actions, is not quite right, I hope
those involved can sort the language out with the RFC Editor
rather than requiring that the WG iterate on the
draft. --JcK, editor. RFC Editor: should this paragraph reach
you, please remove it.</cref></t>
<section title="Documents Whose Context is Changed by This Specificati <section numbered="true" toc="default">
on "> <name>Documents Whose Context Is Changed by This Specification</name>
<t>Both of the documents that follow were obsoleted in 2017 <t>Both of the documents that follow were obsoleted in 2017
by <xref target="RFC8179">RFC 8179</xref>, which changed by <xref target="RFC8179" format="default">RFC 8179</xre
f>, which changed
mentions of the IETF Executive Director to point to mentions of the IETF Executive Director to point to
the IETF Secretariat more generally.</t> the IETF Secretariat more generally.</t>
<t><list style="symbols"> <ul spacing="normal">
<t><xref target="RFC3979">RFC 3979</xref>.</t> <li>
<t><xref target="RFC4879">RFC 4879</xref>.</t> <xref target="RFC3979" format="default">RFC 3979</xref></li>
</list></t> <li>
</section> <xref target="RFC4879" format="default">RFC 4879</xref></li>
</ul>
<section title="General Description of the IETF Adminstrative Model"> </section>
<t><xref target="RFC3716">RFC 3716</xref> is a <section numbered="true" toc="default">
report of an IAB Advisory Committee that served a <name>General Description of the IETF Administrative Model</name>
s a
starting point for the work that led to the origi
nal
IASA structure. That report is an IAB document
rather than an IETF one. The IAB approved a prop
osal
to move RFC 3716 to Historic on March 6, 2019. </
t>
</section>
</section>
<section anchor="Acknowledgments" title="Acknowledgments">
<t> Brian Carpenter's careful checking and identification of
documents that did, and did not, require consideration was
essential to the draft in its current form. He also made
several other significant contributions. Bob Hinden also
gave the document a careful reading and made useful
suggestions. In additional to the above, Alissa Cooper,
Eliot Lear, Heather Flanagan (the RFC Series Editor), and the
current membership to the IAB helped sort out the handing of
RFC 3716.</t>
</section>
<section title="Contributors">
<t>Jason Livingood did the hard work of identifying the
documents that required updating and supplied considerable
text used in this document.</t>
</section>
<section anchor="IANA" title="IANA Considerations"> <t><xref target="RFC3716" format="default">RFC 3716</xref> was a
<t><cref> RFC Editor: Please remove this section before report of an IAB Advisory Committee that served as a
publication.</cref></t> starting point for the work that led to the original
<t>This memo includes no requests to or actions for IANA.</t> 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>
<section anchor="Security" title="Security Considerations"> <section anchor="Security" numbered="true" toc="default">
<name>Security Considerations</name>
<t>The changes specified in this document are matters of <t>The changes specified in this document are matters of
terminology and organizational structure derived from terminology and organizational structure derived from
documents it references. It should have no effect on documents it references. It should have no effect on
Internet security.</t> Internet security.</t>
</section> </section>
</middle> </middle>
<!-- *****BACK MATTER ***** -->
<back> <back>
<references>
<name>References</name>
<references>
<name>Normative References</name>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.2028.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.2418.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.3005.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.3710.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.6702.xml"/>
<!-- draft-ietf-iasa2-rfc4071bis - RFC 8711 -->
<reference anchor="RFC8711" target="https://www.rfc-editor.org/info/rfc8
711">
<front>
<title>Structure of the IETF Administrative Support Activity, Versio
n 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="January"/>
</front>
<seriesInfo name="BCP" value="101"/>
<seriesInfo name="RFC" value="8711"/>
<seriesInfo name="DOI" value="10.17487/RFC8711"/>
</reference>
<references title="Normative References"> <!-- draft-ietf-iasa2-trust-update - RFC 8714 -->
<reference anchor="RFC8714" target="https://rfc-editor.org/info/rfc8714"
<!-- &rfc2119; --> >
&rfc2028; <front>
&rfc2418; <title>Update to the Process for Selection of Trustees for
&rfc3005;
<!-- &rfc4844; -->
<!-- &rfc5377; -->
&rfc3710;
&rfc6702;
<!-- &rfc7500; -->
<reference anchor="RFC-Struct"
target="https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc4
071bis/">
<front>
<title>Structure of the IETF Administrative Support Activity, Version
2.0</title>
<author initials="B." surname="Haberman">
<organization></organization>
<address/>
</author>
<author initials="J." surname="Hall">
<organization></organization>
<address/>
</author>
<author initials="J." surname="Livingood">
<organization></organization>
<address/>
</author>
<date year="2018" month="December" day="5" />
</front>
</reference>
<!--
<reference anchor="RFC-StructS3"
target="https://tools.ietf.org/html/draft-ietf-iasa2-struct-06
#section-3">
<front>
<title>Structure of the IETF Administrative Support Activity, Version
2.0</title>
<author initials="B." surname="Haberman">
<organization></organization>
<address/>
</author>
<author initials="J." surname="Hall">
<organization></organization>
<address/>
</author>
<author initials="J." surname="Livingood">
<organization></organization>
<address/>
</author>
<date year="2018" month="December" day="5" />
</front>
</reference> -->
<reference anchor="RFC-trust-update"
target="https://datatracker.ietf.org/doc/draft-ietf-iasa2-trust-u
pdate/">
<front>
<title>Update to the Process for Selection of Trustees for
the IETF Trust</title> the IETF Trust</title>
<author initials="J." surname="Arkko"> <author initials="J." surname="Arkko">
<organization></organization> <organization/>
<address/> </author>
</author> <author initials="T." surname="Hardie">
<author initials="T." surname="Hardie"> <organization/>
<organization></organization> </author>
<address/> <date month="January" year="2020"/>
</author> </front>
<date year="2018" /> <seriesInfo name="BCP" value="101"/>
</front> <seriesInfo name="RFC" value="8714"/>
</reference> <seriesInfo name="DOI" value="10.17487/RFC8714"/>
</reference>
<reference anchor="RFC-trust-rationale" <!-- draft-ietf-iasa2-trust-rationale - RFC 8715 -->
target="https://datatracker.ietf.org/doc/draft-ietf-iasa2-trust-rational <reference anchor="RFC8715" target="https://rfc-editor.org/info/rfc8715"
e/"> >
<front> <front>
<title>Discussion of the IASA 2.0 Changes as They Relate to <title>Discussion of the IASA 2.0 Changes as They Relate to
the IETF Trust</title> the IETF Trust</title>
<author initials="J." surname="Arkko"> <author initials="J." surname="Arkko">
<organization></organization> <organization/>
<address/> </author>
</author> <date month="January" year="2020"/>
<date year="2018" /> </front>
</front> <seriesInfo name="RFC" value="8715"/>
</reference> <seriesInfo name="DOI" value="10.17487/RFC8715"/>
</reference>
<reference anchor="LLC-Agreement" <reference anchor="LLC-Agreement" target="https://www.ietf.org/documents
target="https://www.ietf.org/documents/180/IETF-LLC-Agreement.pdf"> /180/IETF-LLC-Agreement.pdf">
<front> <front>
<title>Limited Liability Company Agreement of IETF Administration LLC< <title>Limited Liability Company Agreement of IETF Administration LL
/title> C</title>
<author > <author>
<organization>IETF Administration LLC</organization> <organization>IETF Administration LLC</organization>
<address/> </author>
</author> <date year="2018" month="August" day="28"/>
<date year="2018" month="August" day="28"/> </front>
</front> </reference>
</reference>
<reference anchor="RFC-7437bis" <!-- draft-ietf-iasa2-rfc7437bis - RFC 8713 -->
target="https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc7 <reference anchor="RFC8713" target="https://rfc-editor.org/info/rfc8713"
437bis/"> >
<front> <front>
<title>IAB, IESG, and IETF LLC Selection, Confirmation, and <title>IAB, IESG, and IETF LLC Selection, Confirmation, and
Recall Process: Operation of the IETF Nominating and Recall Process: Operation of the IETF Nominating and
Recall Committees</title> Recall Committees</title>
<author initials="M." surname="Kucherawy" role="editor"> <author initials="M." surname="Kucherawy" role="editor">
<organization></organization> <organization/>
<address/> </author> </author>
<author initials="R." surname="Hinden" role="editor"> <author initials="R." surname="Hinden" role="editor">
<organization></organization> <organization/>
<address/> </author> </author>
<author initials="J." surname="Livingood" role="editor"> <author initials="J." surname="Livingood" role="editor">
<organization></organization> <organization/>
<address/> </author>
</author> <date month="January" year="2020"/>
<date year="2018" /> </front>
</front> <seriesInfo name="BCP" value="10"/>
</reference> <seriesInfo name="RFC" value="8713"/>
<seriesInfo name="DOI" value="10.17487/RFC8713"/>
</references> </reference>
</references>
<references title="Informative References"> <references>
&rfc2026;
&rfc3716;
&rfc3929;
&rfc3979;
&rfc4633;
&rfc4879;
&rfc8179;
</references>
<!-- Sections below here become Appendices. -->
<section title="Change Log" anchor="ChangeLog">
<t>RFC Editor: Please remove this appendix before
publication.</t>
<section title="Changes from version -00 (2018-11-15) to -01">
<t><list style="symbols">
<t> Removed RFCs 3979 and 4879 from the "obsoletes" list
because they had already been obsoleted (by 8179)
. It
also removes RFC 8179 from the "updates" list bec
ause
8179 uses "IETF Secretariat" terminology rather t
han
"IETF Executive Director".
<vspace blankLines="1"/> <cref> Note in Draft: That
suggests an idea which might considerably mitigat
e the
name confusion issue: Instead of singling out the
Managing Director of the Secretariat as a named
individual, perhaps we should be referring to the
Secretariat itself, leaving the contact point or
address up to them as an internal administrative
matter. Just a thought. --JcK</cref></t>
<t> Added text to explain why RFC 2026 is not on the hit
list.</t>
<t> Added an acknowledgment to Brian Carpenter. If he
catches another batch of errors and supplies text
, he
gets promoted to Contributor.</t>
<t> Adjusted reference [RFC-Struct] to point to 4071bis.
</t>
<t> Minor editorial corrections and changes. </t>
</list></t>
</section>
<section title="Changes from version -01 (dated 2018-12-06 but
posted 2012-12-07) to -02">
<t> I accidentally omitted RFC 4844 from the document
header "updates" list in Version 01 and noticed t
hat
in response to an unrelated question almost
immediately after posting. The correction seeme
d
important enough to justify almost immediate
re-posting. Changes are only that header, the
document file name, and the date. --JcK </t>
</section>
<section title="Changes from version -02 (2018-12-07) to -03">
<t><list style="symbols">
<t> Removed discussion and pointers to RFC 7500 - IAB
will publish separately. </t>
<t> Added text to describe (very superficially) RFC 3716
.
That document was obsoleted in the previous vers
ion
but not described.</t>
<t> Removed rant about titles and responsibilities from
<xref target="ExecDir-Managing"/> and a subsequen
t
editorial note I hope it is no longer needed --Jc
K.
In additional, several blocks of text that were
commented out in earlier versions of the XML have
been
removed entirely.</t>
</list></t>
</section>
<section title="Changes from version -03 (2018-12-12) to -04">
<t><list style="symbols">
<t> Removed RFC 4844 from the update list and discussion
because the consensus in the WG seemed to be that
it
(and the RFC Editor) should be handled separately
. </t>
<t> Removed RFC 5377 from the update list and discussion
because it involves the Trust. </t>
<t> Editor's note in draft:
<list style="empty">
<t> The above changes and the earlier removal
of RFC 7500
so the IAB could publish it own d
ocument completely
eliminate the earlier Sections 2
and 3. That may call
for a revision of the Introductio
n and/or Abstract, but I
have not done a review for this i
teration of
whether such changes are needed.<
/t>
<t> As documents and references are
shuffled in and out of this one,
it occurred to me
that having a non-normative appen
dix somewhere that
would identify all of the documen
ts containing changes
to reflect the IASA 1.x to 2.0 tr
ansition would be of
great help to any future historia
n trying to
understand what we did and probab
ly helpful to the
IETF if some of these changes don
't work out and/or
require further tuning. After a
brief discussion,
Jason and I concluded that append
ix did not belong in
this iteration of this document.<
/t>
</list></t>
</list></t>
</section>
<section title="Changes from version -04 (2019-01-17) to -05">
<t><list style="symbols">
<t> Changed title from "Consolidated IASA2-Related
Document Updates" to "Consolidated IASA 2.0 Upda
tes of IETF
Administrative Terminology" per suggestions from
Brian
Carpenter and Bob Hinden and 2019-01-31 WG decis
ion.</t>
<t> Removed CREF from <xref target="Intro"/> (should ha
ve
been done in -04). The only remaining CREFs are
the one in
this section (above) that should probably be
preserved through IETF Last Call and notes to th
e RFC Editor. </t>
<t> Updated acknowledgments.</t>
</list></t>
</section>
<section title="Changes from version -05 (2019-01-31) to -06">
<t><list style="symbols">
<t> Changes to text about documents that are updated an
d
made historic, per advice from RFC Editor, WG
Chairs, and IAB. This includes a statement abou
t IAB
action of 2019-03-06 that requests that the RFC
Editor move RFC 3716 to Historic but does not ob
solete that
Informational report. When minimal changes were
attempted, <xref target="MakeHistoric"/> became
very
hard to read and hence was restructured and some
what
rewritten (and then further modified to work aro
und
an xml2rfc glitch). Special attention should be
paid
to the note at the beginning of that section.</t
>
<t> Updated the Acknowledgments section.</t>
</list></t>
</section>
<section title="Changes from version -06 (2019-03-06) to -07"> <name>Informative References</name>
<t><list style="symbols"> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
<t> Moved RFCs 3929 and 4633 from "obsoleted" to ence.RFC.2026.xml"/>
"updated" and stripped text requested that they <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
be ence.RFC.3716.xml"/>
made Historic at the direction of the IETF Chair <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
, WG ence.RFC.3929.xml"/>
Co-chair, and an author. </t> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
<t> Added a section number for a document listed in ence.RFC.3979.xml"/>
Section 2 that was missing.</t> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
<t> Added some notes to the RFC Editor and others.</t> ence.RFC.4633.xml"/>
<t> Updated the acknowledgments.</t> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
</list></t> ence.RFC.4879.xml"/>
</section> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.8179.xml"/>
<!-- <section title="Changes from version -07 (2019-03-11) to <reference anchor="IAB-3716-Historic" target="https://www.iab.org/docume
-08"> nts/minutes/minutes-2019/iab-minutes-2019-03-06/">
<t><list style="symbols"> <front>
<t> ... </t> <title>IAB Minutes 2019-03-06</title>
</list></t> <author>
</section> --> <organization>Internet Architecture Board</organization>
</author>
<date year="2019" month="March" day="6"/>
</front>
</reference>
</section> </references>
</references>
<section anchor="Acknowledgments" numbered="false" toc="default">
<name>Acknowledgments</name>
<t> <contact fullname="Brian Carpenter's"/> careful checking and identific
ation 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="Ali
ssa Cooper"/>,
<contact fullname="Eliot Lear"/>, <contact fullname="Heather Fla
nagan"/> (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> </back>
</rfc> </rfc>
 End of changes. 44 change blocks. 
658 lines changed or deleted 313 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/