draft-ietf-iasa2-rfc4071bis-00.txt   draft-ietf-iasa2-rfc4071bis-01.txt 
IASA2 B. Haberman IASA2 B. Haberman
Internet-Draft Johns Hopkins University Internet-Draft Johns Hopkins University
Obsoletes: RFC4071, RFC4333, RFC7691 (if J. Hall Obsoletes: RFC4071, RFC4333, RFC7691 (if J. Hall
approved) CDT approved) CDT
Intended status: Best Current Practice J. Livingood Intended status: Best Current Practice J. Livingood
Expires: June 8, 2019 Comcast Expires: June 15, 2019 Comcast
December 05, 2018 December 12, 2018
Structure of the IETF Administrative Support Activity, Version 2.0 Structure of the IETF Administrative Support Activity, Version 2.0
draft-ietf-iasa2-rfc4071bis-00 draft-ietf-iasa2-rfc4071bis-01
Abstract Abstract
The IETF Administrative Support Activity (IASA) was originally The IETF Administrative Support Activity (IASA) was originally
established in 2005. In the years since then, the needs of the IETF established in 2005. In the years since then, the needs of the IETF
evolved in ways that required changes to its administrative evolved in ways that required changes to its administrative
structure. The purpose of this document is to document and describe structure. The purpose of this document is to document and describe
the IASA 2.0 structure. the IASA 2.0 structure.
Under IASA 2.0, the work of the IETF's administrative and fundraising Under IASA 2.0, the work of the IETF's administrative and fundraising
skipping to change at page 2, line 7 skipping to change at page 2, line 7
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 8, 2019. This Internet-Draft will expire on June 15, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
skipping to change at page 2, line 37 skipping to change at page 2, line 37
2. Scope Limitation . . . . . . . . . . . . . . . . . . . . . . 4 2. Scope Limitation . . . . . . . . . . . . . . . . . . . . . . 4
2.1. LLC Agreement with the Internet Society . . . . . . . . . 4 2.1. LLC Agreement with the Internet Society . . . . . . . . . 4
3. Definitions and Principles . . . . . . . . . . . . . . . . . 5 3. Definitions and Principles . . . . . . . . . . . . . . . . . 5
3.1. Alphabet Soup . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Alphabet Soup . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Key Differences From the Old IASA Structure to IASA 2.0 . 6 3.2. Key Differences From the Old IASA Structure to IASA 2.0 . 6
3.3. General IETF LLC Responsibilities . . . . . . . . . . . . 6 3.3. General IETF LLC Responsibilities . . . . . . . . . . . . 6
3.4. IETF LLC Working Principles . . . . . . . . . . . . . . . 7 3.4. IETF LLC Working Principles . . . . . . . . . . . . . . . 7
3.5. Principles of the IETF and ISOC Relationship . . . . . . 8 3.5. Principles of the IETF and ISOC Relationship . . . . . . 8
3.6. Relationship of the IETF LLC Board to the IETF Leadership 8 3.6. Relationship of the IETF LLC Board to the IETF Leadership 8
3.7. IETF LLC Board Decision Making . . . . . . . . . . . . . 9 3.7. IETF LLC Board Decision Making . . . . . . . . . . . . . 9
3.8. Review and Appeal of IETF Executive Director and IETF LLC 3.8. Review of IETF Executive Director and IETF LLC Board
Board Decisions . . . . . . . . . . . . . . . . . . . . . 9 Decisions . . . . . . . . . . . . . . . . . . . . . . . . 9
3.9. Community Consensus and Grant of Authority . . . . . . . 10 3.9. Community Consensus and Grant of Authority . . . . . . . 9
3.10. Termination and Change . . . . . . . . . . . . . . . . . 10 3.10. Termination and Change . . . . . . . . . . . . . . . . . 10
4. Structure of the IASA2 . . . . . . . . . . . . . . . . . . . 11 4. Structure of the IASA2 . . . . . . . . . . . . . . . . . . . 10
4.1. IETF Executive Director and Staff Responsibilities . . . 11 4.1. IETF Executive Director and Staff Responsibilities . . . 10
4.2. IETF LLC Board Responsibilities . . . . . . . . . . . . . 12 4.2. IETF LLC Board Responsibilities . . . . . . . . . . . . . 11
4.3. Board Design Goals . . . . . . . . . . . . . . . . . . . 14 4.3. Board Design Goals . . . . . . . . . . . . . . . . . . . 13
5. IETF LLC Board Membership, Selection and Accountability . . . 14 5. IETF LLC Board Membership, Selection and Accountability . . . 14
5.1. Board Composition . . . . . . . . . . . . . . . . . . . . 14 5.1. Board Composition . . . . . . . . . . . . . . . . . . . . 14
5.2. IETF LLC-Appointed Directors . . . . . . . . . . . . . . 15 5.2. IETF LLC-Appointed Directors . . . . . . . . . . . . . . 14
5.3. Recruiting IETF LLC Board Directors . . . . . . . . . . . 15 5.3. Recruiting IETF LLC Board Directors . . . . . . . . . . . 14
5.4. IETF LLC Board Director Term Length . . . . . . . . . . . 15 5.4. IETF LLC Board Director Term Length . . . . . . . . . . . 15
5.5. IETF LLC Board Director Limit . . . . . . . . . . . . . . 16 5.5. IETF LLC Board Director Limit . . . . . . . . . . . . . . 15
5.6. Staggered Terms . . . . . . . . . . . . . . . . . . . . . 16 5.6. Staggered Terms . . . . . . . . . . . . . . . . . . . . . 16
5.7. IETF LLC Board Director Removal . . . . . . . . . . . . . 16 5.7. IETF LLC Board Director Removal . . . . . . . . . . . . . 16
5.8. Filling an IETF LLC Board Director Vacancy . . . . . . . 17 5.8. Filling an IETF LLC Board Director Vacancy . . . . . . . 16
5.9. Quorum . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.9. Quorum . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.10. Board Voting . . . . . . . . . . . . . . . . . . . . . . 17 5.10. Board Voting . . . . . . . . . . . . . . . . . . . . . . 16
5.11. Interim Board . . . . . . . . . . . . . . . . . . . . . . 17 5.11. Interim Board . . . . . . . . . . . . . . . . . . . . . . 17
5.12. Board Positions . . . . . . . . . . . . . . . . . . . . . 18 5.12. Board Positions . . . . . . . . . . . . . . . . . . . . . 17
6. IETF LLC Funding . . . . . . . . . . . . . . . . . . . . . . 18 6. IETF LLC Funding . . . . . . . . . . . . . . . . . . . . . . 17
6.1. Financial Statements . . . . . . . . . . . . . . . . . . 18 6.1. Financial Statements . . . . . . . . . . . . . . . . . . 18
6.2. Bank and Investment Accounts . . . . . . . . . . . . . . 19 6.2. Bank and Investment Accounts . . . . . . . . . . . . . . 18
6.3. Financial Audits . . . . . . . . . . . . . . . . . . . . 19 6.3. Financial Audits . . . . . . . . . . . . . . . . . . . . 18
6.4. ISOC Financial Support . . . . . . . . . . . . . . . . . 19 6.4. ISOC Financial Support . . . . . . . . . . . . . . . . . 18
6.5. IETF Meeting Revenues . . . . . . . . . . . . . . . . . . 19 6.5. IETF Meeting Revenues . . . . . . . . . . . . . . . . . . 18
6.6. Donations to the IETF LLC . . . . . . . . . . . . . . . . 19 6.6. Donations to the IETF LLC . . . . . . . . . . . . . . . . 19
6.7. Funding Supports the IETF . . . . . . . . . . . . . . . . 20 6.7. Funding Supports the IETF . . . . . . . . . . . . . . . . 19
6.8. Charitable Fundraising Practices . . . . . . . . . . . . 20 6.8. Charitable Fundraising Practices . . . . . . . . . . . . 19
6.9. Operating Reserve . . . . . . . . . . . . . . . . . . . . 20 6.9. Operating Reserve . . . . . . . . . . . . . . . . . . . . 19
6.10. Annual Budget Process . . . . . . . . . . . . . . . . . . 20 6.10. Annual Budget Process . . . . . . . . . . . . . . . . . . 20
7. IETF LLC Policies . . . . . . . . . . . . . . . . . . . . . . 21 7. IETF LLC Policies . . . . . . . . . . . . . . . . . . . . . . 20
7.1. Conflict of Interest Policy . . . . . . . . . . . . . . . 21 7.1. Conflict of Interest Policy . . . . . . . . . . . . . . . 21
7.2. Other Policies . . . . . . . . . . . . . . . . . . . . . 21 7.2. Other Policies . . . . . . . . . . . . . . . . . . . . . 21
7.3. Compliance . . . . . . . . . . . . . . . . . . . . . . . 22 7.3. Compliance . . . . . . . . . . . . . . . . . . . . . . . 21
8. Three-Year Assessment . . . . . . . . . . . . . . . . . . . . 22 8. Three-Year Assessment . . . . . . . . . . . . . . . . . . . . 22
9. Security Considerations . . . . . . . . . . . . . . . . . . . 23 9. Security Considerations . . . . . . . . . . . . . . . . . . . 22
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22
12. Informative References . . . . . . . . . . . . . . . . . . . 23 12. Informative References . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
The IETF Administrative Support Activity (IASA) was originally The IETF Administrative Support Activity (IASA) was originally
established in 2005. In the years since then, the needs of the IETF established in 2005. In the years since then, the needs of the IETF
evolved in ways that required changes to its administrative evolved in ways that required changes to its administrative
structure. The purpose of this document is to document and describe structure. The purpose of this document is to document and describe
the IASA 2.0 structure. the IASA 2.0 structure.
Under IASA 2.0, the work of the IETF's administrative and fundraising Under IASA 2.0, the work of the IETF's administrative and fundraising
skipping to change at page 9, line 20 skipping to change at page 9, line 20
The IETF LLC Board decides the details about its decision-making The IETF LLC Board decides the details about its decision-making
rules, including its rules for quorum (see Section 5.9), conflict of rules, including its rules for quorum (see Section 5.9), conflict of
interest (see Section 7.1), and breaking of ties. These rules are interest (see Section 7.1), and breaking of ties. These rules are
expected to be public. expected to be public.
All IETF LLC Board decisions are expected to be recorded in IETF LLC All IETF LLC Board decisions are expected to be recorded in IETF LLC
Board minutes, and IETF LLC Board minutes are expected to be Board minutes, and IETF LLC Board minutes are expected to be
published in a timely fashion. published in a timely fashion.
3.8. Review and Appeal of IETF Executive Director and IETF LLC Board 3.8. Review of IETF Executive Director and IETF LLC Board Decisions
Decisions
The IETF LLC Board is directly accountable to the IETF community for The IETF LLC Board is directly accountable to the IETF community for
the performance of the IASA 2.0. In order to achieve this, the IETF the performance of the IASA 2.0, including hiring and managing the
LLC Board and IETF Executive Director are expected to ensure that IETF Executive Director. In extreme cases of dissatisfaction with
guidelines are developed for regular operational decision making. the IETF LLC, the IETF community can utilize the recall process as
Where appropriate, these guidelines should be developed with public noted in Section 5.7.
input. In all cases, they must be made public.
If a member of the IETF community questions whether a decision or Anyone in the community of IETF participants may ask the IETF LLC
action of the IETF Executive Director or the IETF LLC Board has been Board for a formal review of a decision or action by the IETF
Executive Director or IETF LLC Board if they believe this was not
undertaken in accordance with IETF BCPs or IASA 2.0 operational undertaken in accordance with IETF BCPs or IASA 2.0 operational
guidelines, or questions whether the IETF LLC has created and guidelines.
maintained appropriate guidelines, he or she may ask the IETF LLC
Board for a formal review of the decision or action.
The request for review should be addressed to the IETF LLC Board
chair and should include a description of the decision or action to
be reviewed, an explanation of how, in the requestor's opinion, the
decision or action violates the BCPs or operational guidelines, and a
suggestion for how the situation could be rectified. All requests
for review shall be posted publicly, and the IETF LLC Board is
expected to respond publicly to these requests within a reasonable
period, typically within 90 days. It is up to the IETF LLC Board to
determine what type of review and response is required, based on the
nature of the review request. Based on the results of the review,
the IETF LLC Board may choose to overturn their own decision, to
change their operational guidelines to prevent further
misunderstandings, to take other action as appropriate, or just to
publish the review result and take no other action.
If a member of the community is not satisfied with the IETF LLC
Board's response to his or her review request, he or she may escalate
the issue by appealing the decision or action to the IAB, using the
appeals procedures outlined in [RFC2026]. If he or she is not
satisfied with the IAB response, he or she can escalate the issue to
the ISOC Board of Trustees, as described in [RFC2026].
The reviewing body (the IAB or ISOC Board of Trustees) shall review A formal request for review must be addressed to the IETF LLC Board
the decision of the IETF Executive Director or IETF LLC Board to chair and must include a description of the decision or action to be
determine whether it was made in accordance with existing BCPs and reviewed, an explanation of how, in the requestor's opinion, the
operational guidelines. As a result of this review, the reviewing decision or action violates the BCPs or IASA 2.0 operational
body may recommend to the community that the BCPs governing IETF LLC guidelines, and a suggestion for how the situation could be
Board actions should be changed. The reviewing body may also advise rectified.
the IETF LLC Board to modify existing operational guidelines to avoid
similar issues in the future and/or it may advise the IETF LLC Board
to re-consider their decision or action. It may also recommend that
no action be taken, based on the review.
In exceptional cases, when no other recourse seems reasonable, the The IETF LLC shall respond to such requests within a reasonable
reviewing body may overturn or reverse a non-binding decision or period, typically within 90 days, and shall publicly publish
action of the IETF LLC Board. This should be done only after careful information about the request and the corresponding response and/or
consideration and consultation with the IETF LLC Board regarding the result.
ramifications of this action. In no circumstances may the IAB or
ISOC Board of Trustees overturn a decision of the IETF LLC Board that
involves a binding contract or overturn a personnel-related action
(such as hiring, firing, promotion, demotion, performance reviews,
salary adjustments, etc.).
3.9. Community Consensus and Grant of Authority 3.9. Community Consensus and Grant of Authority
The IETF is a consensus-based group, and authority to act on behalf The IETF is a consensus-based group, and authority to act on behalf
of the community requires a high degree of consensus and the of the community requires a high degree of consensus and the
continued consent of the community. After a careful process of continued consent of the community. After a careful process of
deliberation, a broad-based community consensus emerged to house the deliberation, a broad-based community consensus emerged to house the
administration of the IETF within the IETF LLC as a disregarded administration of the IETF within the IETF LLC as a disregarded
entity of the Internet Society. This document reflects that entity of the Internet Society. This document reflects that
consensus. consensus.
skipping to change at page 11, line 38 skipping to change at page 10, line 46
The IETF has historically benefitted from the use of contractors for The IETF has historically benefitted from the use of contractors for
accounting, finance, meeting planning, administrative assistance, accounting, finance, meeting planning, administrative assistance,
legal counsel, tools, and web site support, as well as other services legal counsel, tools, and web site support, as well as other services
related to the standards process (RFC Editor and IANA). Prior to related to the standards process (RFC Editor and IANA). Prior to
making the transition from IASA to IASA 2.0, the IETF budget making the transition from IASA to IASA 2.0, the IETF budget
reflected specific support from ISOC for communications and reflected specific support from ISOC for communications and
fundraising as well as some general support for accounting, finance, fundraising as well as some general support for accounting, finance,
legal, and other services. The division of responsibilities between legal, and other services. The division of responsibilities between
staff and contractors is at the discretion of the IETF Executive staff and contractors is at the discretion of the IETF Executive
Director and his or her staff. Director and their staff.
The IETF has a long history of community involvement in the execution The IETF has a long history of community involvement in the execution
of certain administrative functions, in particular development of of certain administrative functions, in particular development of
IETF tools, the NOC's operation of the meeting network, and some IETF tools, the NOC's operation of the meeting network, and some
outreach and communications activities conducted by the Education and outreach and communications activities conducted by the Education and
Mentoring Directorate. The IETF LLC staff is expected to respect the Mentoring Directorate. The IETF LLC staff is expected to respect the
IETF community's wishes about community involvement in these and IETF community's wishes about community involvement in these and
other functions going forward as long as the staff feels that they other functions going forward as long as the staff feels that they
can meet the otherwise-stated needs of the community. Establishing can meet the otherwise-stated needs of the community. Establishing
the framework to allow the IETF LLC to staff each administrative the framework to allow the IETF LLC to staff each administrative
 End of changes. 21 change blocks. 
87 lines changed or deleted 53 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/