draft-ietf-iasa2-rfc2031bis-08.txt   rfc8712.txt 
IETF Administrative Support Activity 2 G. Camarillo Internet Engineering Task Force (IETF) G. Camarillo
Internet-Draft Ericsson Request for Comments: 8712 Ericsson
Obsoletes: 2031 (if approved) J. Livingood Obsoletes: 2031 J. Livingood
Intended status: Informational Comcast Category: Informational Comcast
Expires: February 27, 2020 August 26, 2019 ISSN: 2070-1721 February 2020
The IETF-ISOC Relationship The IETF-ISOC Relationship
draft-ietf-iasa2-rfc2031bis-08
Abstract Abstract
This document summarises the Internet Engineering Task Force (IETF) - This document summarizes the Internet Engineering Task Force (IETF) -
Internet Society (ISOC) relationship, following a major revision to Internet Society (ISOC) relationship, following a major revision to
the structure of the IETF Administrative Support Activity (IASA) in the structure of the IETF Administrative Support Activity (IASA) in
2018. The IASA was revised under a new "IASA 2.0" structure by the 2018. The IASA was revised under a new "IASA 2.0" structure by the
IASA2 Working Group, which changed the IETF's administrative, legal, IASA2 Working Group, which changed the IETF's administrative, legal,
and financial structure. As a result, it also changed the and financial structure. As a result, it also changed the
relationship between the IETF and ISOC, which made it necessary to relationship between the IETF and ISOC, which made it necessary to
revise RFC 2031. revise RFC 2031.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This document is not an Internet Standards Track specification; it is
provisions of BCP 78 and BCP 79. published for informational purposes.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." 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.
This Internet-Draft will expire on February 27, 2020. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8712.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction and History . . . . . . . . . . . . . . . . . . 2 1. Introduction and History
2. Philosophical Relationship with ISOC . . . . . . . . . . . . 3 2. Philosophical Relationship with ISOC
3. Main Division of Responsibilities between IETF and ISOC . . . 3 3. Main Division of Responsibilities between IETF and ISOC
4. ISOC's Role in the IETF Standards Process . . . . . . . . . . 4 4. ISOC's Role in the IETF Standards Process
5. The IETF's Role in ISOC . . . . . . . . . . . . . . . . . . . 4 5. The IETF's Role in ISOC
6. Legal Relationship with ISOC . . . . . . . . . . . . . . . . 5 6. Legal Relationship with ISOC
7. Financial and Administrative Relationship with ISOC . . . . . 5 7. Financial and Administrative Relationship with ISOC
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 8. IANA Considerations
9. Security Considerations . . . . . . . . . . . . . . . . . . . 6 9. Security Considerations
10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 6 10. Privacy Considerations
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 11. References
12. Changes from Previous Versions . . . . . . . . . . . . . . . 6 11.1. Normative References
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 11.2. Informative References
13.1. Normative References . . . . . . . . . . . . . . . . . . 7 Acknowledgements
13.2. Informative References . . . . . . . . . . . . . . . . . 7 Authors' Addresses
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction and History 1. Introduction and History
The Internet Society provides a corporate home for the administrative The Internet Society provides a corporate home for the administrative
entity that supports the Internet Engineering Task Force (IETF), the entity that supports the Internet Engineering Task Force (IETF), the
Internet Architecture Board (IAB), and the Internet Research Task Internet Architecture Board (IAB), and the Internet Research Task
Force (IRTF), and supports the work of these groups through a variety Force (IRTF), and supports the work of these groups through a variety
of programs. of programs.
The Internet Engineering Task Force (IETF) is the body that is The Internet Engineering Task Force (IETF) is the body that is
responsible for the development and maintenance of the Internet responsible for the development and maintenance of the Internet
Standards. The IETF is primarily a volunteer organization. Its Standards. The IETF is primarily a volunteer organization. Its
driving force is a group of dedicated high-quality engineers from all driving force is a group of dedicated, high-quality engineers from
over the world. In a structure of working groups, these engineers all over the world. In a structure of working groups, these
exchange ideas and experience, and through discussion and engineers exchange ideas and experience, and through discussion and
collaboration (both electronically and face-to-face) they strive to collaboration (both electronically and face-to-face), they strive to
achieve rough consensus and implement the standards through running achieve rough consensus and implement the standards through running
code. code.
The growth of the Internet over several decades also led to the The growth of the Internet over several decades has also led to the
growth of the IETF. More and more people, organizations, and growth of the IETF. More and more people, organizations, and
companies rely on Internet Standards. Non-technical issues, such as companies rely on Internet Standards. Nontechnical issues, such as
legal, administrative, and financial issues had long been an legal, administrative, and financial issues had long been an
undesirable but unavoidable part of the IETF. To address these undesirable but unavoidable part of the IETF. To address these
issues in 1995 the IETF established the Poised95 Working Group. Its issues, the IETF established the Poised95 Working Group in 1995. Its
goal was to structure and document the IETF processes in order to goal was to structure and document the IETF processes in order to
maximize the flexibility and freedom of IETF engineers so that they maximize the flexibility and freedom of IETF engineers so that they
could work in the way the IETF had always been most successful and to could work in the way the IETF had always been most successful and to
honour the IETF credo: "Rough consensus and running code". honor the IETF credo: "Rough consensus and running code".
The Poised95 Working Group concluded that the Internet Society The Poised95 Working Group concluded that the Internet Society
(ISOC), which was formed in 1992, was the best organization to handle (ISOC), which was formed in 1992, was the best organization to handle
all of these legal, administrative, and financial tasks on behalf of all of these legal, administrative, and financial tasks on behalf of,
and in close cooperation with the IETF. This led to documenting and in close cooperation with, the IETF. This led to documenting
things such as the IETF standards process [RFC2026], the IETF things such as the IETF standards process [RFC2026], the IETF
organizational structure [RFC2028], the IETF Nominating Committee organizational structure [RFC2028], the IETF Nominating Committee
(NomCom) procedures <BCP10>, and the IETF-ISOC relationship (NomCom) procedures [RFC2027], and the IETF-ISOC relationship
[RFC2031]. [RFC2031].
As time passed and operational experience accumulated, additional As time passed and operational experience accumulated, additional
structure was necessary. As a result, the Internet Administrative structure was necessary. As a result, the Internet Administrative
Support Activity (IASA) was defined in 2005 and documented in Support Activity (IASA) was defined in 2005 and documented in
[RFC4071] and [RFC4371]. [RFC4071] and [RFC4371].
In 2018, the IASA was revised under a new "IASA 2.0" structure by the 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 IASA2 Working Group, which made significant revisions to the IETF's
administrative, legal, and financial structure. One critical outcome administrative, legal, and financial structure. One critical outcome
was the formation, in close cooperation between the IETF and ISOC, of was the formation, in close cooperation between the IETF and ISOC, of
the IETF Administration Limited Liability Company (IETF LLC) as a the IETF Administration Limited Liability Company (IETF LLC) as a
subsidiary of ISOC. subsidiary of ISOC.
As a result of the IASA 2.0 structure [I-D.ietf-iasa2-rfc4071bis] and As a result of the IASA 2.0 structure [RFC8711] and formation of the
formation of the IETF LLC, the relationship between the IETF and ISOC IETF LLC, the relationship between the IETF and ISOC has changed.
has changed. This document summarises the current state of the IETF- This document summarizes the current state of the IETF-ISOC
ISOC relationship at a high level and replaces [RFC2031]. relationship at a high level and replaces [RFC2031].
2. Philosophical Relationship with ISOC 2. Philosophical Relationship with ISOC
ISOC and the IETF have historically been philosophically aligned. ISOC and the IETF have historically been philosophically aligned.
ISOC's connection with the IETF community has always played an ISOC's connection with the IETF community has always played an
important role in its policy work, which has not changed. ISOC has important role in its policy work, which has not changed. ISOC has
always been and continues to be an advocate for multistakeholder always been and continues to be an advocate for multistakeholder
processes, which includes the technical community. Open standards processes, which includes the technical community. Open standards
are an explicit part of one of the focus areas in ISOC's mission: are an explicit part of one of the focus areas in ISOC's mission:
Advancing the development and application of Internet infrastructure, advancing the development and application of Internet infrastructure,
technologies, and open standards <ISOC-Mission>. technologies, and open standards [ISOC-Mission].
3. Main Division of Responsibilities between IETF and ISOC 3. Main Division of Responsibilities between IETF and ISOC
The IETF remains responsible for the development and quality of the The IETF remains responsible for the development and quality of the
Internet Standards. Apart from the roles described below, the IETF Internet Standards. Apart from the roles described below, the IETF
and ISOC acknowledge that ISOC as an organization has no direct and ISOC acknowledge that ISOC as an organization has no direct
influence whatsoever on the technical content of Internet Standards influence whatsoever on the technical content of Internet Standards
(though ISOC employees may independently continue to make technical (though ISOC employees may independently continue to make technical
contributions as individuals). contributions as individuals).
4. ISOC's Role in the IETF Standards Process 4. ISOC's Role in the IETF Standards Process
ISOC plays a small role in the IETF standards process. In ISOC plays a small role in the IETF standards process. In
particular, ISOC assists the standards process by appointing the IETF particular, ISOC assists the standards process by appointing the IETF
NomCom chair and by confirming IAB candidates who are put forward by NomCom chair and by confirming IAB candidates who are put forward by
the IETF NomCom, as described in [RFC7437], and by acting as the last the IETF NomCom, as described in [RFC8713], and by acting as the last
resort in the appeals process, as described in [RFC2026]. resort in the appeals process, as described in [RFC2026].
ISOC maintains liaison relationships and memberships in other ISOC maintains liaison relationships and memberships in other
Standards Development Organizations (SDOs) and related organizations, Standards Development Organizations (SDOs) and related organizations,
which directly benefits the IETF. For example, ISOC is a Sector which directly benefits the IETF. For example, ISOC is a Sector
Member of the ITU-T. As a result, ISOC delegates are afforded the Member of the ITU-T. As a result, ISOC delegates are afforded the
same rights as other ITU-T Sector Members [RFC6756]. same rights as other ITU-T Sector Members [RFC6756].
ISOC also supports the IETF standards process more indirectly (e.g., ISOC also supports the IETF standards process indirectly (e.g., by
by promoting it in relevant communities) through several programs. promoting it in relevant communities) through several programs. For
For example, ISOC's Policymakers Program to the IETF (usually example, ISOC's Policymakers Programme to the IETF (usually referred
referred to simply as ISOC's policy fellows program) gives policy to simply as ISOC's IETF Policy Program) gives policy experts an
experts an opportunity to interact directly with the IETF technical opportunity to interact directly with the IETF technical community.
community. ISOC also performs technical work using the standards ISOC also performs technical work using the standards developed in
developed in the IETF as its basis. An example of that is ISOC's the IETF as its basis. An example of that is ISOC's work in
Deploy360 program, which helps encourage and support the deployment encouraging and supporting the deployment of IETF standards.
of IETF standards like DNSSEC [RFC4033] and IPv6 [RFC8200].
Otherwise, the involvement of ISOC's employees in the IETF standards Otherwise, the involvement of ISOC's employees in the IETF standards
process (e.g., as document editors or in leadership positions) is as process (e.g., as document editors or in leadership positions) is as
individual contributors rather than on institutional grounds. individual contributors rather than on institutional grounds.
5. The IETF's Role in ISOC 5. The IETF's Role in ISOC
The IETF plays a role in the governance of ISOC. Per ISOC's by-laws, The IETF plays a role in the governance of ISOC. Per ISOC's bylaws,
the IETF appoints a set of trustees to the ISOC Board. The process the IETF appoints a set of trustees to the ISOC Board. The process
by which the IETF makes those appointments is defined in [RFC3677]. by which the IETF makes those appointments is defined in [RFC3677].
The charter of the IAB (Internet Architecture Board) [RFC2850] states The charter of the IAB (Internet Architecture Board) [RFC2850] states
that "the IAB acts as a source of advice and guidance to the Board of that "the IAB acts as a source of advice and guidance to the Board of
Trustees and Officers of the Internet Society concerning technical, Trustees and Officers of the Internet Society concerning technical,
architectural, procedural, and (where appropriate) policy matters architectural, procedural, and (where appropriate) policy matters
pertaining to the Internet and its enabling technologies". This pertaining to the Internet and its enabling technologies". This
connection between the IAB and ISOC ensures that ISOC's proposals in connection between the IAB and ISOC ensures that ISOC's proposals in
the policy area are based on a sound understanding of the relevant the policy area are based on a sound understanding of the relevant
technologies and architectures. ISOC's strong connection to the technologies and architectures. ISOC's strong connection to the
Internet technical community has always been one of its main Internet technical community has always been one of its main
strengths. strengths.
6. Legal Relationship with ISOC 6. Legal Relationship with ISOC
The IETF LLC is a disregarded Limited Liability Company (LLC) of the The IETF LLC is a disregarded Limited Liability Company (LLC) of the
Internet Society - established to provide a corporate legal framework Internet Society that was established to provide a corporate legal
for facilitating current and future activities related to the IETF, framework for facilitating current and future activities related to
IAB, and IRTF. It was established by the ISOC/IETF LLC Agreement the IETF, IAB, and IRTF. It was established by the ISOC / IETF LLC
[OpAgreement] on August 27, 2018, and governs the relationship Agreement [OpAgreement] on August 27, 2018, and governs the
between the IETF LLC and ISOC. relationship between the IETF LLC and ISOC.
The IETF Trust, documented in [RFC5378], and updated in The IETF Trust, documented in [RFC5378], and updated in [RFC8714] and
[I-D.ietf-iasa2-trust-rationale] and [I-D.ietf-iasa2-trust-update], [RFC8715], provides legal protection for the RFC Series of documents
provides legal protection for the RFC series of documents and other and other aspects of the IETF. This includes things such as
aspects of the IETF. This includes things such as protection for protection for trademarks, copyrights, and intellectual property
trademarks, copyrights, and intellectual property rights. As part of rights. As part of the IETF Trust arrangement, IETF standards
the IETF Trust arrangement, IETF standards documents can be freely documents can be freely downloaded, copied, and distributed without
downloaded, copied, and distributed without financial or other financial or other distribution restrictions, though all rights to
distribution restrictions, though all rights to change these change these documents lie with the IETF. The IETF Trust also
documents lie with the IETF. The IETF Trust also provides legal provides legal protection in case of disputes over intellectual
protection in case of disputes over intellectual property rights and property rights and other rights. The creation of the IETF LLC has
other rights. The creation of the IETF LLC has changed the way that changed the way that the IETF Trust's trustees are selected but did
the IETF Trust's trustees are selected but did not change the purpose not change the purpose or operation of the Trust. One of the IETF
or operation of the Trust. One of the IETF Trust's trustees is Trust's trustees is appointed by the ISOC's Board of Trustees.
appointed by the ISOC's Board of Trustees.
7. Financial and Administrative Relationship with ISOC 7. Financial and Administrative Relationship with ISOC
Under the terms of the Operating Agreement [OpAgreement] between ISOC Under the terms of the Operating Agreement [OpAgreement] between ISOC
and the IETF, ISOC has agreed to provide significant funding support and the IETF, ISOC has agreed to provide significant funding support
for the IETF. In addition, the IETF LLC is responsible for creating for the IETF. In addition, the IETF LLC is responsible for creating
and managing an annual operating budget for the IETF; for and managing an annual operating budget for the IETF; for
negotiating, signing, and overseeing contracts; for fundraising; for negotiating, signing, and overseeing contracts; for fundraising; for
maintaining bank accounts; and for liability insurance. The IETF LLC maintaining bank accounts; and for liability insurance. The IETF LLC
is managed by a Board of Directors, one of whom is appointed by the is managed by a Board of Directors, one of whom is appointed by the
skipping to change at page 5, line 49 skipping to change at line 232
LLC operate at arm's length. LLC operate at arm's length.
The IETF LLC establishes contracts with third parties to provide The IETF LLC establishes contracts with third parties to provide
different types of services to the IETF. Note that it is possible 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 that some of those services may be provided by ISOC or involve ISOC
staff. staff.
Under the new IASA 2.0 structure, the IETF LLC is solely responsible Under the new IASA 2.0 structure, the IETF LLC is solely responsible
for its administration, including the IETF Trust, IAB, IESG, IETF for its administration, including the IETF Trust, IAB, IESG, IETF
working groups, and other IETF processes. A further exploration of working groups, and other IETF processes. A further exploration of
this can be found in Section 4 of [I-D.ietf-iasa2-rfc4071bis]. this can be found in Section 4 of [RFC8711].
8. IANA Considerations 8. IANA Considerations
This document introduces no new IANA considerations. This document has no IANA actions.
9. Security Considerations 9. Security Considerations
This document introduces no new security considerations. This document introduces no new security considerations.
10. Privacy Considerations 10. Privacy Considerations
This document introduces no new privacy considerations. This document introduces no new privacy considerations.
11. Acknowledgements 11. References
The authors would like to thank Erik Huizer for his contribution as
the author of [RFC2031], which this document replaces.
12. Changes from Previous Versions
RFC Editor: Please remove this section upon publication.
-00: Initial version published
-01: Several key updates to prepare WGLC based on WG feedback
-02: Fixed nits identified by Brian Carpenter on 12-21-2018, and text
on the tax status from John Levine.
-03: As we entered IESG review, added a short description of what
ISOC does (in relation to the IETF) that can be used in external
material by both the IETF and ISOC.
-04: Clarification adding text to Section 6 on legal issue.
-05: Fix nits
-06: Fix nits and other changes from IESG review
-07: Fixed one missed nit from IESG review
-08: Fixed two typographical errors
13. References 11.1. Normative References
13.1. Normative References
[I-D.ietf-iasa2-rfc4071bis] [RFC8711] Haberman, B., Hall, J., and J. Livingood, "Structure of
Haberman, B., Hall, J., and J. Livingood, "Structure of
the IETF Administrative Support Activity, Version 2.0", the IETF Administrative Support Activity, Version 2.0",
draft-ietf-iasa2-rfc4071bis-11 (work in progress), April BCP 101, RFC 8711, DOI 10.17487/RFC8711, February 2020,
2019. <https://www.rfc-editor.org/info/rfc8711>.
13.2. Informative References
[BCP10] "BCP10", <https://www.rfc-editor.org/refs/ref-bcp10.txt>.
[I-D.ietf-iasa2-trust-rationale]
Arkko, J., "Discussion of the IASA 2.0 Changes as They
Relate to the IETF Trust", draft-ietf-iasa2-trust-
rationale-03 (work in progress), October 2018.
[I-D.ietf-iasa2-trust-update] 11.2. Informative References
Arkko, J. and T. Hardie, "Update to the Process for
Selection of Trustees for the IETF Trust", draft-ietf-
iasa2-trust-update-03 (work in progress), February 2019.
[ISOC-Mission] [ISOC-Mission]
"ISOC Mission", Internet Society, "Internet Society Mission",
<https://www.internetsociety.org/mission/>. <https://www.internetsociety.org/mission/>.
[OpAgreement] [OpAgreement]
"Limited Liability Company Agreement of IETF "Limited Liability Company Agreement of IETF
Administration LLC", August 2018, Administration LLC", August 2018,
<https://www.ietf.org/documents/180/ <https://www.ietf.org/documents/180/IETF-LLC-
IETF-LLC-Agreement.pdf>. Agreement.pdf>.
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996,
<https://www.rfc-editor.org/info/rfc2026>. <https://www.rfc-editor.org/info/rfc2026>.
[RFC2027] Galvin, J., "IAB and IESG Selection, Confirmation, and
Recall Process: Operation of the Nominating and Recall
Committees", RFC 2027, DOI 10.17487/RFC2027, October 1996,
<https://www.rfc-editor.org/info/rfc2027>.
[RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in
the IETF Standards Process", BCP 11, RFC 2028, the IETF Standards Process", BCP 11, RFC 2028,
DOI 10.17487/RFC2028, October 1996, DOI 10.17487/RFC2028, October 1996,
<https://www.rfc-editor.org/info/rfc2028>. <https://www.rfc-editor.org/info/rfc2028>.
[RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031, [RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031,
DOI 10.17487/RFC2031, October 1996, DOI 10.17487/RFC2031, October 1996,
<https://www.rfc-editor.org/info/rfc2031>. <https://www.rfc-editor.org/info/rfc2031>.
[RFC2850] Internet Architecture Board and B. Carpenter, Ed., [RFC2850] Internet Architecture Board and B. Carpenter, Ed.,
"Charter of the Internet Architecture Board (IAB)", "Charter of the Internet Architecture Board (IAB)",
BCP 39, RFC 2850, DOI 10.17487/RFC2850, May 2000, BCP 39, RFC 2850, DOI 10.17487/RFC2850, May 2000,
<https://www.rfc-editor.org/info/rfc2850>. <https://www.rfc-editor.org/info/rfc2850>.
[RFC3677] Daigle, L., Ed. and Internet Architecture Board, "IETF [RFC3677] Daigle, L., Ed. and Internet Architecture Board, "IETF
ISOC Board of Trustee Appointment Procedures", BCP 77, ISOC Board of Trustee Appointment Procedures", BCP 77,
RFC 3677, DOI 10.17487/RFC3677, December 2003, RFC 3677, DOI 10.17487/RFC3677, December 2003,
<https://www.rfc-editor.org/info/rfc3677>. <https://www.rfc-editor.org/info/rfc3677>.
[RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "DNS Security Introduction and Requirements",
RFC 4033, DOI 10.17487/RFC4033, March 2005,
<https://www.rfc-editor.org/info/rfc4033>.
[RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the
IETF Administrative Support Activity (IASA)", BCP 101, IETF Administrative Support Activity (IASA)", BCP 101,
RFC 4071, DOI 10.17487/RFC4071, April 2005, RFC 4071, DOI 10.17487/RFC4071, April 2005,
<https://www.rfc-editor.org/info/rfc4071>. <https://www.rfc-editor.org/info/rfc4071>.
[RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for [RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for
IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371, IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371,
January 2006, <https://www.rfc-editor.org/info/rfc4371>. January 2006, <https://www.rfc-editor.org/info/rfc4371>.
[RFC5378] Bradner, S., Ed. and J. Contreras, Ed., "Rights [RFC5378] Bradner, S., Ed. and J. Contreras, Ed., "Rights
skipping to change at page 8, line 41 skipping to change at line 316
DOI 10.17487/RFC5378, November 2008, DOI 10.17487/RFC5378, November 2008,
<https://www.rfc-editor.org/info/rfc5378>. <https://www.rfc-editor.org/info/rfc5378>.
[RFC6756] Trowbridge, S., Ed., Lear, E., Ed., Fishman, G., Ed., and [RFC6756] Trowbridge, S., Ed., Lear, E., Ed., Fishman, G., Ed., and
S. Bradner, Ed., "Internet Engineering Task Force and S. Bradner, Ed., "Internet Engineering Task Force and
International Telecommunication Union - Telecommunication International Telecommunication Union - Telecommunication
Standardization Sector Collaboration Guidelines", Standardization Sector Collaboration Guidelines",
RFC 6756, DOI 10.17487/RFC6756, September 2012, RFC 6756, DOI 10.17487/RFC6756, September 2012,
<https://www.rfc-editor.org/info/rfc6756>. <https://www.rfc-editor.org/info/rfc6756>.
[RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, [RFC8713] Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood,
Confirmation, and Recall Process: Operation of the Ed., "IAB, IESG, IETF Trust, and IETF LLC Selection,
Nominating and Recall Committees", BCP 10, RFC 7437, Confirmation, and Recall Process: Operation of the IETF
DOI 10.17487/RFC7437, January 2015, Nominating and Recall Committees", BCP 10, RFC 8713,
<https://www.rfc-editor.org/info/rfc7437>. DOI 10.17487/RFC8713, February 2020,
<https://www.rfc-editor.org/info/rfc8713>.
[RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC8714] Arkko, J. and T. Hardie, "Update to the Process for
(IPv6) Specification", STD 86, RFC 8200, Selection of Trustees for the IETF Trust", BCP 101,
DOI 10.17487/RFC8200, July 2017, RFC 8714, DOI 10.17487/RFC8714, February 2020,
<https://www.rfc-editor.org/info/rfc8200>. <https://www.rfc-editor.org/info/rfc8714>.
[RFC8715] Arkko, J., "IETF Administrative Support Activity 2.0:
Update to the Process for Selection of Trustees for the
IETF Trust", RFC 8715, DOI 10.17487/RFC8715, February
2020, <https://www.rfc-editor.org/info/rfc8715>.
Acknowledgements
The authors would like to thank Erik Huizer for his contribution as
the author of [RFC2031], which this document replaces.
Authors' Addresses Authors' Addresses
Gonzalo Camarillo Gonzalo Camarillo
Ericsson Ericsson
Email: Gonzalo.Camarillo@ericsson.com Email: Gonzalo.Camarillo@ericsson.com
Jason Livingood Jason Livingood
Comcast Comcast
 End of changes. 35 change blocks. 
150 lines changed or deleted 114 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/