draft-ietf-iasa-bcp-01.txt | | draft-ietf-iasa-bcp-00.txt |
---|
| | |
| | |
Network Working Group R. Austein, Ed. | | Network Working Group R. Austein, Ed. |
Internet-Draft ISC | | Internet-Draft ISC |
Expires: May 31, 2005 B. Wijnen, Ed. | | Expires: May 16, 2005 B. Wijnen, Ed. |
Lucent Technologies | | Lucent Technologies |
November 30, 2004 | | November 15, 2004 |
| | |
| | |
Structure of the IETF Administrative Support Activity (IASA) | | Structure of the IETF Administrative Support Activity (IASA) |
| | draft-ietf-iasa-bcp-00 |
draft-ietf-iasa-bcp-01 | | |
| | |
Status of this Memo | | Status of this Memo |
| | |
This document is an Internet-Draft and is subject to all provisions | | This document is an Internet-Draft and is subject to all provisions |
of section 3 of RFC 3667. By submitting this Internet-Draft, each | | of section 3 of RFC 3667. By submitting this Internet-Draft, each |
author represents that any applicable patent or other IPR claims of | | author represents that any applicable patent or other IPR claims of |
which he or she is aware have been or will be disclosed, and any of | | which he or she is aware have been or will be disclosed, and any of |
which he or she become aware will be disclosed, in accordance with | | which he or she become aware will be disclosed, in accordance with |
RFC 3668. | | RFC 3668. |
| | |
Internet-Drafts are working documents of the Internet Engineering | | Internet-Drafts are working documents of the Internet Engineering |
Task Force (IETF), its areas, and its working groups. Note that | | Task Force (IETF), its areas, and its working groups. Note that |
other groups may also distribute working documents as | | other groups may also distribute working documents as |
Internet-Drafts. | | Internet-Drafts. |
| | |
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." |
| | |
The list of current Internet-Drafts can be accessed at | | The list of current Internet-Drafts can be accessed at |
http://www.ietf.org/ietf/1id-abstracts.txt. | | http://www.ietf.org/ietf/1id-abstracts.txt. |
| | |
The list of Internet-Draft Shadow Directories can be accessed at | | The list of Internet-Draft Shadow Directories can be accessed at |
http://www.ietf.org/shadow.html. | | http://www.ietf.org/shadow.html. |
| | |
This Internet-Draft will expire on May 31, 2005. | | This Internet-Draft will expire on May 16, 2005. |
| | |
Copyright Notice | | Copyright Notice |
| | |
Copyright (C) The Internet Society (2004). | | Copyright (C) The Internet Society (2004). |
| | |
Abstract | | Abstract |
| | |
This document describes the structure of the IETF Administrative | | This document describes the structure of the IETF Administrative |
Support Activity (IASA) as an IETF-controlled activity housed within | | Support Activity (IASA) as an IETF-controlled activity housed within |
the Internet Society (ISOC) legal umbrella. It defines the roles and | | the Internet Society (ISOC) legal umbrella. It defines the roles and |
responsibilities of the IETF Administrative Oversight Committee | | responsibilities of the IETF Administrative Oversight Committee |
(IAOC), the IETF Administrative Director (IAD), and ISOC in the | | (IAOC), the IETF Administrative Director (IAD) and ISOC in the |
fiscal and administrative support of the IETF standards process. It | | fiscal and administrative support of the IETF standards process. It also |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 1] | | Austein & Wijnen Expires May 16, 2005 [Page 1] |
| | |
Internet-Draft Structure of IASA November 2004 | | Internet-Draft Structure of IASA November 2004 |
| | |
| | |
also defines the membership and selection rules for the IAOC. | | defines how the IAOC will be comprised and selected. |
| | |
Table of Contents | | Table of Contents |
| | |
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 | | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 |
1.1 Editors' Notes . . . . . . . . . . . . . . . . . . . . . . 4 | | 1.1 Editors' Notes . . . . . . . . . . . . . . . . . . . . . . 4 |
1.2 Open issues . . . . . . . . . . . . . . . . . . . . . . . 4 | | |
2. Definitions and Principles . . . . . . . . . . . . . . . . . . 5 | | 2. |
2.1 Alphabet Soup . . . . . . . . . . . . . . . . . . . . . . 5 | | Alphabet Soup . . . . . . . . . . . . . . . . . . . . . . |
2.2 Principles of the IASA, IETF and ISOC relationship . . . . 6 | | |
2.3 Community Consensus and Grant of Authority . . . . . . . . 7 | | . . 4 |
3. Structure of the IASA . . . . . . . . . . . . . . . . . . . . 7 | | 3. Structure of the IASA . . . . . . . . . . . . . . . . . . . . 4 |
3.1 IAD Responsibilities . . . . . . . . . . . . . . . . . . . 8 | | 3.1 IAD Responsibilities . . . . . . . . . . . . . . . . . . . 5 |
3.2 IAD Committees . . . . . . . . . . . . . . . . . . . . . . 9 | | 3.2 IAD Committees . . . . . . . . . . . . . . . . . . . . . . 6 |
3.3 IAOC Responsibilities . . . . . . . . . . . . . . . . . . 9 | | 3.3 IAOC Responsibilities . . . . . . . . . . . . . . . . . . 7 |
3.4 Relationship of the IAOC to Existing IETF Leadership . . . 10 | | 3.4 Relationship of the IAOC to Existing IETF Leadership . . . 7 |
3.5 IAOC Decision Making . . . . . . . . . . . . . . . . . . . 10 | | 3.5 IAOC Decision Making . . . . . . . . . . . . . . . . . . . 8 |
4. IAOC Membership, Selection and Accountability . . . . . . . . 11 | | 4. IAOC Membership, Selection and Accountability . . . . . . . . 8 |
4.1 Initial IAOC Selection . . . . . . . . . . . . . . . . . . 13 | | 4.1 Initial IAOC Selection . . . . . . . . . . . . . . . . . . 10 |
5. IASA Funding . . . . . . . . . . . . . . . . . . . . . . . . . 13 | | 5. IASA Funding . . . . . . . . . . . . . . . . . . . . . . . . . 10 |
5.1 Divisional Accounting . . . . . . . . . . . . . . . . . . 14 | | 5.1 |
5.2 IETF meeting revenues . . . . . . . . . . . . . . . . . . | | IETF meeting revenues . . . . . . . . . . . . . . . . . . 10 |
14 | | 5.2 |
5.3 Designated donations, monetary and in-kind . . . . . . . . | | Designated donations, monetary and in-kind . . . . . . . . 10 |
14 | | 5.3 |
5.4 Other ISOC support . . . . . . . . . . . . . . . . . . . . | | Other ISOC support . . . . . . . . . . . . . . . . . . . . 11 |
15 | | 5.4 |
5.5 Operating Reserve . . . . . . . . . . . . . . . . . . . . 15 | | Operating Reserve . . . . . . . . . . . . . . . . . . . . 11 |
6. IASA Budget Process . . . . . . . . . . . . . . . . . . . . . 15 | | 6. IASA Budget Process . . . . . . . . . . . . . . . . . . . . . 12 |
7. ISOC Responsibilities for IASA . . . . . . . . . . . . . . . . 16 | | 7. ISOC Responsibilities for IASA . . . . . . . . . . . . . . . . 12 |
8. Security Considerations . . . . . . . . . . . . . . . . . . . 17 | | 8. Security Considerations . . . . . . . . . . . . . . . . . . . 13 |
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 | | 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 |
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 | | 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 |
11. References . . . . . . . . . . . . . . . . . . . . . . . . . | | 11. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 14 |
18 | | 12. |
11.1 Normative References . . . . . . . . . . . . . . . . . . . . 18 | | References . . . . . . . . . . . . . . . . . . . . |
11.2 Informative References . . . . . . | | . . . . . 15 |
. . . . . . . . . . . . . 18 | | 12.1 Normative References . . . . . . . . . . . . . |
Authors' Addresses . . . . . . . | | . . . . . . . 15 |
. . . . . . . . . . . . . . . 19 | | 12.2 Informative References . . . . . . . . . . . . . . . |
A. Change Log . . . . | | . . . . 16 |
. . . . . . . . . . . . . . . . . . . . . . 19 | | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 16 |
Intellectual Property and Copyright Statements . . . . . . . . 22 | | Intellectual Property and Copyright Statements . . . . . . . . 17 |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 2] | | Austein & Wijnen Expires May 16, 2005 [Page 2] |
| | |
Internet-Draft Structure of IASA November 2004 | | Internet-Draft Structure of IASA November 2004 |
| | |
| | |
1. Introduction | | 1. Introduction |
| | |
This document describes the structure of the IETF Administrative | | This document describes the structure of the IETF Administrative |
Support Activity (IASA) as an IETF-controlled activity housed within | | Support Activity (IASA) as an IETF-controlled activity housed within |
the Internet Society (ISOC) legal umbrella. It defines the roles and | | the Internet Society (ISOC) legal umbrella. It defines the roles and |
responsibilities of the IETF Administrative Oversight Committee | | responsibilities of the IETF Administrative Oversight Committee |
(IAOC), the IETF Administrative Director (IAD), and ISOC in the | | (IAOC), the IETF Administrative Director (IAD) and ISOC in the |
fiscal and administrative support of the IETF standards process. It | | fiscal and administrative support of the IETF standards process. It |
also defines the membership and selection rules for the IAOC. | | also defines how the IAOC is comprised and selected. |
| | |
The IETF undertakes its technical activities as an ongoing, open, | | The IETF undertakes its technical activities as an ongoing, open, |
consensus-based process. This document defines an administrative | | consensus-based process. This document defines an administrative |
support structure intended to be responsive to the administrative | | support structure intended to be responsive to the administrative |
needs of the IETF technical community, and describes how that support | | needs of the IETF technical community, and describes how that support |
structure fits under ISOC's organizational umbrella. This document | | structure fits under ISOC's organizational umbrella. This document |
does not affect the ISOC-IETF working relationship as it relates to | | does not affect the ISOC-IETF working relationship as it relates to |
standards development or the communication of technical advice | | standards development or the communication of technical advice |
relevant to the policy and educational goals of ISOC. | | relevant to the policy and educational goals of ISOC. |
| | |
The IETF Administrative Support Activity (IASA) provides the | | The IETF Administrative Support Activity (IASA) provides the |
administrative structure required to support the IETF standards | | administrative structure required to support the IETF standards |
process and to support the IETF's technical activities. As of the | | process and to support the IETF's technical activities. At the |
time | | time |
at which this document was written, this included the work of | | of writing of this document, this includes the work of |
IETF working groups, the IESG, the IAB, and the | | IETF working groups, the IESG, the IAB, and the IRTF; it will include any |
IRTF. Should the | | successors to these which have been described by the Internet |
IETF standards process at some future date come to include other | | standards process as part of the |
technical activities, the | | technical activities of the IETF. |
IASA shall provide administrative support | | This |
for those activities as well. Such support includes, as appropriate, | | includes, as appropriate, |
undertaking or contracting for the work described in | | undertaking or contracting for the work described in [RFC3716], including |
[RFC3716],including IETF document and data management, IETF meetings, | | IETF document and data management, IETF meetings, |
and any operational agreements or contracts with the RFC Editor and | | and any operational agreements or contracts with the RFC Editor and |
IANA. The IASA is also ultimately responsible for the financial | | IANA. The IASA is also ultimately responsible for the financial |
activities associated with IETF administrative support such as | | activities associated with IETF administrative support such as |
collecting IETF meeting fees, paying invoices, managing budgets and | | collecting IETF meeting fees, paying invoices, managing budgets and |
financial accounts, and so forth. | | financial accounts, etc. |
| | |
The IASA is responsible for ensuring that the IETF's administrative | | The IASA is responsible for ensuring that the IETF's administrative |
needs are met, and met well. The IETF does not expect the IASA to | | needs are met and met well; it is not expected that the IASA will |
undertake the bulk of this work directly; rather, the IETF expects | | undertake the bulk of this work directly, but rather that |
the IASA to contract this work from others, and manage these | | IASA will contract this work from others, and manage the |
contractual relationships to achieve efficiency, transparency and | | contractual relationships in line with key operating principles such as efficiency, transparency and |
cost effectiveness. | | cost effectiveness. |
| | |
The IASA is distinct from IETF-related technical functions, such as | | The IASA is distinct from other IETF-related technical functions, such as |
the RFC Editor, the Internet Assigned Numbers Authority (IANA), and | | the RFC Editor, the Internet Assigned Numbers Authority (IANA), and |
the IETF standards process itself. The IASA has no influence on the | | the IETF standards process itself. The IASA has no influence on the |
technical decisions of the IETF or on the technical contents of IETF | | technical decisions of the IETF or on the technical contents of IETF |
work. Note, however, that this in no way prevents people who form | | work. This in no way prevents people who form |
part of the IASA from participating as individuals in IETF technical | | part of the IASA participating as individuals in IETF activities. |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 3] | | Austein & Wijnen Expires May 16, 2005 [Page 3] |
| | |
Internet-Draft Structure of IASA November 2004 | | Internet-Draft Structure of IASA November 2004 |
| | |
| | |
activities. | | |
| | |
1.1 Editors' Notes | | 1.1 Editors' Notes |
| | |
This document is still a work in progress, and, due to time pressure | | This document is still a work in progress, and, due to time pressure, |
and lack of a clear consensus on some issues, the editors have not | | the editors have not |
yet been able to incorporate all of the outstanding change requests. | | yet been able to incorporate all of the outstanding change requests. Among other, more substantive issues, |
| | the entire document probably ought to be recast in the present tense. |
Work will continue after this version has shipped. | | Work will continue after this version has shipped. |
| | |
In some cases the best way to handle a particular suggestion (in the | | In some cases the best way to handle a particular suggestion (in the |
editors' opinion, at any rate) has been to incorporate new text with | | editors' opinion, at any rate) has been to incorporate new text with |
an "Editors' note" which attempts to explain the change. | | an "Editors' note" which attempts to explain the change. |
| | |
The editors request that substantive comments and requested changes | | The editors request that substantive comments and requested changes |
be sent, one per message, with a clear and meaningful subject line on | | be sent, one per message, with a clear and meaningful subject line on |
each message, as this will make it easier for the editors to keep | | each message, as this will make it easier for the editors to keep |
track of change requests. | | track of change requests. |
| | |
| | 2. Alphabet Soup |
| | |
| | Although most of the terms, abbreviations, and acronyms used in this |
| | document are reasonably well-known, first-time readers may find this |
| | alphabet soup confusing. This section therefore attempts to provide |
| | a quick summary. |
| | |
| | IAB Internet Architecture Board (see [RFC2026]). |
| | |
| | IAD Internet Administrative Director, defined by this document. |
| | |
| | IAOC Internet Administrative Oversight Committee, defined by this |
| | document. |
| | |
| | IESG Internet Engineering Steering Group (see [RFC2026]). |
| | |
| | ISOC Internet Society (see [????]). |
| | |
| | |
| | 3. Structure |
| | |
1.2 Open issues | | |
| | |
Summary of | | of the IASA |
| | |
open issues for which we need to find specific IETF | | The IASA will be structured to ensure accountability |
consensus so that editors can put in correct and agreed-upon text. | | and transparency |
| | |
Do we need "pre-nuptial" agreement text as part of the BCP? | | of the IETF administrative and fiscal activities to |
Currently, the doc does not have text for it. Seems IETF | | the IETF |
| | community. The IASA will |
consensus on choosing Scenario O means that we (the IETF) trust | | |
ISOC. | | |
| | |
Do we need separate bank accounts? Consensus seems to be | | be directed and overseen by the IETF |
| | Administrative Oversight Committee (IAOC). The IAOC will consist of |
emerging | | volunteers, all chosen directly or indirectly by the |
not to ask for that. So this doc does not claim so now. Instead | | |
we specify "Divisional Accounting" (Section 5.1). | | |
| | |
Do we need to add text to protect IETF | | IETF community, |
from an IAD or an IAOC | | as well as appropriate ex officio appointments from ISOC |
going amok? Seems that IAD can be suspended/fired and | | and IETF |
IAOC can be | | leadership. The IAOC will be accountable |
recalled, and so maybe that is sufficient. | | |
| | |
Are designated donations specified appropriately? In particular, | | |
does requiring that not be "unduly restricted" address previously | | |
stated concerns? That is what current text says. | | |
| | |
Do we need to be more specific as to how reserves are built for | | to the IETF community for |
emergency situations, or can we leave that at ISOC's discretion? | | |
| | |
We have added a set of principles (Section 2.2). The remainder of | | |
the document still contains a fair amount of detail (based on the | | the effectiveness, efficiency and transparency of the IASA. |
| | |
| | The IASA will initially consist |
principles) but potentially some of those details can be removed. | | of a single full-time ISOC employee, |
It is not clear whether the IETF wants to keep the details or | | |
remove them. | | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 4] | | Austein & Wijnen Expires May 16, 2005 [Page 4] |
| | |
Internet-Draft Structure of IASA November 2004 | | Internet-Draft Structure of IASA November 2004 |
| | |
| | |
There has been a suggestion that we may need some more wording on | | |
startup phase. Not clear exactly what might be needed. Send text | | |
if you feel additions are needed. | | |
| | |
Not clear yet if we have too much about the IAD task. Should that | | the IETF Administrative Director (IAD), who will |
task be | | be an officer |
specified elsewhere, initially by the Transition Team, | | entitled |
later by IAOC or some committee? | | |
| | |
Would we want the IAOC to sign off on the yearly (or more | | to act on behalf of the IASA at the direction |
frequent) reports in some formal sense within a reasonable amount | | |
of time? This might protect the | | of the IAOC. |
IAD | | The IAD is likely to draw on financial, legal and administrative |
from some form of open-ended | | support furnished by ISOC support staff or consultants. Allocation of costs |
lingering responsibility for previous years. It might also | | for ISOC support staff |
protect against having somebody, five years from now, state "this | | |
is wrong and | | and consultants will be based on an |
by | | actual expenses or on some other allocation model determined by |
the way this was already wrong N years ago" | | consultation between the |
| | |
How should we deal with conflict between IAD, IAOC and | | IAOC and ISOC. |
| | |
ISOC? This | | Although |
is complicated by the fact that ISOC | | the IAD will be an ISOC employee, he or she will work under |
officially employs the IAD | | the direction of the IAOC. The IAD will be selected and hired by |
while a small committee | | a committee of the IAOC. The members of this committee will be |
hires and fires and evaluates the IAD. | | appointed by the IAOC, and will consist minimally of |
| | |
Related to above: What happens if/when there is a disagreement | | |
between the ISOC | | the ISOC |
BoT and IAOC regarding business decisions, | | President and |
spending, hiring, etc? | | |
| | |
Do we need wording about the | | the IETF Chair. This same committee will be |
ownership of IETF tools and | | responsible for periodically reviewing the performance of the IAD and |
data? We | | determining any changes to his or her employment |
have some text (in Section 2.2) about IPR, but does that fully | | |
cover tools and | | and compensation. |
| | |
| | In principle, IETF administrative functions will be outsourced via |
| | well-defined contracts or equivalent instruments. The IAD will be |
data? | | responsible for negotiating |
| | |
| | |
2. Definitions and | | and maintaining those contracts, as well |
| | as providing any coordination that is necessary to make sure the IETF |
| | administrative support functions are properly covered. The IAOC is |
Principles | | accountable for |
| | |
This section describes terminology and underlying principles used in | | |
the rest of this document. | | the structure |
| | |
2.1 Alphabet Soup | | |
| | |
Although most of the terms, abbreviations, and | | of the IASA and thus decides which |
acronyms used in this | | functions |
document are reasonably well-known, first-time readers may find this | | are |
alphabet soup confusing. This section therefore attempts to | | to be outsourced. If any functions are done in-house, |
| | then they will be clearly specified and documented with well-defined |
| | deliverables, service level agreements, and transparent accounting |
| | for the cost of such functions. |
| | |
| | 3.1 IAD Responsibilities |
| | |
provide | | The |
a quick summary. | | |
| | |
IAB Internet Architecture Board (see [RFC2026], [RFC2850]). | | |
| | |
IAD Internet Administrative Director, defined by this document. | | IAD will be responsible for working with the |
| | |
IAOC Internet Administrative Oversight Committee, defined by this | | IAOC |
document. | | |
| | |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 5] | | |
| | |
Internet-Draft Structure of IASA November 2004 | | |
| | |
| | |
IESG Internet Engineering Steering Group (see [RFC2026], [RFC3710]). | | |
| | |
ISOC Internet Society (see [RFC2031] and | | and others to |
[ISOC]). | | understand the administrative requirements |
| | |
| | |
2.2 Principles of the IASA, IETF and | | of the IETF and for |
ISOC relationship | | managing the IASA to meet those needs. |
| | |
This section attempts to describe principles underlying the | | This will include determining the |
mechanisms described in this document. | | |
| | |
1. The IETF intends to establish a structure (the IASA) in order to | | structure of the |
get IETF administrative functions managed appropriately, | | |
according to good administrative, fiscal, and management | | |
principles. The IASA | | IASA effort, establishing an operating budget, |
includes the | | negotiating contracts with service providers, managing the business |
| | relationship with those providers and establishing mechanisms to |
| | track their performance. The IAD may also manage other contractors |
| | or ISOC employees (such as support staff) as necessary, when such |
| | contractors or employees are engaged in IASA-related work. |
| | |
IAD | | The IAD will be responsible for running IASA in an open and |
and | | transparent manner and for producing regular (monthly, quarterly and |
the IAOC, and shall be | | annual) financial and operational updates for |
housed within ISOC. | | |
| | |
2. The IAD, IAOC and ISOC shall not have any authority over the IETF | | IAOC and IETF community |
| | review. |
standards development activities. | | |
| | |
3. The IAD and IAOC, with advice from the | | The IAD will be responsible for administering the IETF finances, |
ISOC President/CEO and | | managing a separate financial account |
staff, will develop an annual budget for the IASA. The budget | | for the IASA, |
must clearly identify all expected direct and indirect | | and establishing |
expenditures related to the IASA. ISOC, through its normal | | |
procedures, will evaluate and adopt the IASA | | and administering the IASA budget. While it is understood that ISOC |
budget as part of | | will need |
ISOC's own budget process and commit to ensuring funds to | | to put some financial controls in place to protect ISOC's |
| | |
| | |
| | |
| | Austein & Wijnen Expires May 16, 2005 [Page 5] |
| | |
| | Internet-Draft Structure of IASA November 2004 |
| | |
| | |
support | | fiscal stability, |
the | | the IAD (with IAOC approval, as appropriate) should |
| | have signing authority consistent with carrying out IASA work |
| | effectively, efficiently and independently. If there are any |
approved budget. | | problems regarding |
| | |
4. Responsibility for the evaluation, review and negotiation of | | the level of financial approval granted to |
contracts and other IETF administrative and support agreements | | |
and other expenditures of funds under the IASA shall rest with | | |
the IAD, operating in accordance with policies and procedures set | | the IAD, |
by the IAOC and consistent with ISOC operating policies. | | the IAOC and ISOC commit to working out |
| | |
5. There shall be a | | a policy that is |
detailed public accounting to separately | | mutually agreeable, and |
identify all funds available to | | to doing so within a reasonable timeframe. |
| | |
| | Service contracts will be negotiated by the IAD (with input from any |
and all expenditures relating to | | other appropriate bodies) and reviewed, as appropriate, by |
the | | the IAOC. |
IETF and to the IASA, including any donations, of funds or | | It is expected that the IAOC will establish guidelines for what level of review is expected based on contract type, size, cost, or |
| | duration. The contracts will be executed |
in-kind, received by | | by ISOC, on behalf of the |
ISOC | | IASA, after whatever review ISOC requires in order to ensure that the |
| | contracts meet ISOC's legal and financial requirements. |
| | |
for IETF-related activities. In-kind | | Although |
donations shall only be accepted at the direction of the IAD and | | the approval of the ISOC President/CEO |
IAOC. | | |
| | |
6. The right to use any intellectual property rights created by any | | |
IASA-related or | | or ISOC Board of |
IETF activity may not be withheld or limited in | | Trustees may be required for some contracts, their review should be limited |
any way by ISOC from the IETF. | | |
| | |
7. The IASA should establish a target for a reserve fund to cover | | to protecting ISOC's liabilities |
normal operating expenses and | | and financial stability. |
meeting expenses in accordance with | | The IAD |
prudent planning, and | | and IAOC are responsible for making all business decisions |
ISOC should work with the IASA to build up | | regarding the IASA. In particular, |
and maintain the reserve. | | the ISOC Board |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 6] | | |
| | |
Internet-Draft Structure of | | of Trustees will |
IASA November 2004 | | not have direct influence over |
| | |
| | |
The remainder of this document contains details based on the above | | the choice |
principles. | | |
| | |
2.3 Community Consensus and Grant of Authority | | of IASA contractors or |
| | |
The IETF | | IETF |
is a consensus-based group, and authority to act on behalf | | meeting sponsors. This restriction is meant to enforce |
of the | | the |
community requires a high degree of consensus and the | | separation between fund raising and the actual operation |
continued consent of the | | of the |
| | standards process. |
| | |
| | The IAD will prepare an annual budget, which will be reviewed and |
| | approved by the IAOC. The IAD will be responsible for presenting |
community. After a careful process of | | this budget |
deliberation, a broad-based community consensus emerged to house the | | to the ISOC Board |
IETF Administrative Support Activity (IASA) within the Internet | | |
Society. This document reflects that consensus. | | |
| | |
Termination and change: Any change to this agreement shall require a | | |
similar level of community consensus and deliberation and shall be | | of Trustees, as part |
reflected by a subsequent Best Current Practice (BCP) document. | | |
| | |
3. Structure of | | of ISOC's annual |
the IASA | | financial planning process. |
| | |
The IASA structure is | | The IAOC is responsible for ensuring the |
designed to ensure accountability and | | suitability |
transparency of the IETF administrative | | of the budget for meeting the IETF community's administrative needs, but the IAOC does not bear fiduciary |
| | responsibility for ISOC. Therefore, the ISOC Board also needs to |
and | | review and understand the budget and planned activity in enough |
| | detail to properly carry out their fiduciary responsibility. Each |
fiscal activities to the | | year, the complete IASA budget will published to the |
IETF community. | | IETF community. |
| | |
| | Unless explicitly delegated with the consent of the IAOC, the IAD |
The IETF Administrative Oversight Committee (IAOC) | | will also fill |
directs and oversees the IASA. The IAOC consists of volunteers, all | | the role of |
chosen directly or indirectly by the IETF community, as | | the IETF Executive Director, as described |
well as | | in various |
appropriate ex officio appointments from ISOC and IETF | | IETF process BCPs. |
| | |
leadership. | | 3.2 IAD Committees |
The IAOC shall be accountable to | | The IAD may constitute special-purpose, chartered committees to bring |
the IETF | | in expertise (on topics such as finance, IETF process, or tools), to |
| | engage volunteers in IASA activities, or to gain additional |
community for the | | perspectives. These committees may consist |
effectiveness, efficiency and transparency of the IASA. | | of subsets |
| | |
The IASA consists initially of a single full-time ISOC employee, the | | of the IAOC, |
| | IAB or IESG, selected |
IETF | | IETF participants, or external experts, |
Administrative Director (IAD), an officer entitled to act on | | depending on |
behalf of the | | the need. These committees are advisory in nature -- |
| | |
| | |
| | |
| | Austein & Wijnen Expires May 16, 2005 [Page 6] |
| | |
IASA at the direction of the IAOC. The IAD is likely | | Internet-Draft Structure of IASA November 2004 the IAD is responsible |
to draw on financial, legal and administrative support furnished by | | |
ISOC support staff or consultants. Costs for ISOC support staff and | | for the outcome, including presenting and |
| | supporting any decisions |
consultants are allocated based on actual expenses or on some other | | or work items to |
allocation model determined by consultation between the IAOC and | | the IAOC and |
ISOC. | | |
| | |
Although the | | the IETF |
| | community, as appropriate. |
| | |
| | 3.3 IAOC Responsibilities |
| | |
IAD is | | The role of the IAOC is to provide appropriate direction to the IAD, |
| | review the IAD's regular reports, and oversee the IASA functions to |
an ISOC employee, he or she works under the | | ensure that the administrative needs |
direction of the | | of the IETF community are being |
IAOC. The IAD is | | properly met. The IAOC is not expected to be regularly engaged in |
| | the day-to-day administrative work of IASA, but rather to provide |
selected and | | appropriate direction, oversight and approval. |
| | |
hired by a committee | | Therefore, |
of the | | the IAOC's responsibilities are: |
| | |
IAOC. The members of this committee are appointed by the | | o Select the IAD |
IAOC, and consist at minimum of the ISOC President and | | and provide high-level review and direction for his |
the IETF | | or her work. It |
Chair. This same committee is | | is expected that this task will be handled by a |
| | sub-committee, as described above. |
| | |
responsible for setting the IAD's | | o Review the IAD's plans and contracts to ensure that they will meet |
initial compensation, reviewing the performance of the | | the administrative needs of the IETF. |
| | |
IAD | | o Track whether the IASA functions are meeting |
periodically, and determining any changes to the IAD's employment and | | the |
compensation. | | |
| | |
In principle, IETF administrative functions should be outsourced. | | IETF community's administrative needs, and work with the |
The IAD is responsible for negotiating and maintaining such | | IAD to determine a plan for corrective action if they |
contracts, as well as providing any coordination necessary to make | | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 7] | | |
| | |
Internet-Draft Structure of IASA November 2004 | | |
| | |
| | |
sure the IETF administrative support functions are | | are not. |
| | |
covered properly. | | o Review |
The IAOC is accountable for the structure of the IASA and thus | | the IAD's budget proposals |
decides which functions are to be outsourced. All outsourcing must | | to ensure that |
be via well-defined contracts or equivalent instruments. If any | | |
functions are performed in-house, they must be clearly specified and | | they will meet |
documented with well-defined deliverables, service level agreements, | | |
and transparent accounting for the cost of such functions. | | the IETF's needs, |
| | |
3.1 IAD Responsibilities | | |
| | |
The IAD is responsible for working with the IAOC and others to | | and review |
understand the | | the IAD's regular financial reports. |
| | |
administrative requirements of the IETF, and | | o Ensure that the IASA is run in a transparent and accountable |
for | | manner. While |
managing the IASA to meet those needs. This includes determining the | | the work may be delegated to the IAD and others, |
structure of the IASA effort, establishing an operating budget, | | the IAOC |
negotiating contracts with service providers, managing the business | | |
relationship with those providers, and establishing mechanisms to | | |
track their performance. The IAD may also manage other contractors | | |
or ISOC employees (such as support staff) as necessary, when such | | |
contractors or employees are engaged in IASA-related work. | | |
| | |
The IAD is responsible for running IASA in an open and | | is responsible for ensuring that IASA finances and |
transparent | | operational status are appropriately tracked |
manner, and for producing regular monthly, | | and that monthly, |
quarterly, and annual | | quarterly and annual |
financial and operational | | financial and operational reports are |
updates for IAOC and IETF community review. | | published to the IETF community. |
| | |
The IAD is responsible for administering the IETF finances, managing | | The IAOC's role is to direct and review, not perform, the work of |
a separate financial account for the | | the |
IASA, and establishing and | | IAD and IASA. It is expected |
administering the IASA budget. While ISOC will | | the IAOC will have periodic |
need to put some | | teleconferences and face-to-face meetings, as needed |
financial controls in place to protect ISOC's fiscal stability, the | | to |
IAD (with IAOC approval, as appropriate) should have signing | | |
authority consistent with carrying out IASA work effectively, | | |
efficiently and | | efficiently and effectively carry out their duties. |
| | |
independently. If there are any problems regarding | | 3.4 Relationship |
the level of financial approval granted to the IAD, the IAOC and ISOC | | of the IAOC to Existing IETF Leadership |
shall work out a policy that is mutually agreeable, and shall do so | | |
within a reasonable timeframe. | | |
| | |
The | | The IAOC will be directly accountable to the IETF Community. |
IAD negotiates service contracts, with input, as appropriate, | | However, |
from other bodies, and with review, as appropriate, by the IAOC. The | | the nature |
IAOC should establish guidelines for what level of review is expected | | |
based on contract type, size, cost, or duration. Contracts are | | |
executed by ISOC, on behalf of the IASA, after whatever review ISOC | | of the IAOC's work will involve treating |
requires to ensure that the contracts meet ISOC's legal and financial | | the IESG and IAB as internal customers. |
requirements. | | |
| | |
The IAD and IAOC are responsible for making all business decisions | | The IAOC and |
regarding the IASA. In particular, the ISOC Board of Trustees shall | | the IAD should |
not | | not |
have direct influence over the choice of IASA contractors or IETF | | consider their work successful unless the IESG |
meeting sponsors. This restriction is meant to enforce the | | |
separation between fund raising and | | and IAB are satisfied |
the actual operation of the | | with the administrative support that they are receiving. |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 8] | | Austein & Wijnen Expires May 16, 2005 [Page 7] |
| | |
Internet-Draft Structure of IASA November 2004 | | Internet-Draft Structure of IASA November 2004 |
| | |
| | |
| | 3.5 IAOC Decision Making |
| | |
| | |
standards process. | | |
| | |
The IAD prepares an annual budget, which is subject to | | The IAOC attempts to reach all decisions unanimously. If unanimity |
review and | | cannot be achieved, |
approval by the IAOC. The IAD is responsible for presenting this | | the IAOC chair may conduct informal polls |
budget to | | to |
the ISOC Board of | | determine the consensus of the group. In cases where it is |
Trustees, as part of | | necessary, some decisions may be made by voting. For the purpose of |
| | judging consensus or voting, only the "voting members" (as defined in |
ISOC's annual | | Section 4) shall be counted. If voting |
financial planning process. The IAOC is responsible for ensuring the | | is used and the votes are |
| | equally split, then |
budget's suitability for meeting the | | the IAOC chair decides. |
| | |
IETF community's administrative | | Decisions of IAOC members or |
needs, but the IAOC does not bear fiduciary responsibility for ISOC. | | the entire IAOC are subject |
The ISOC Board therefore needs to | | to appeal |
review and understand the budget | | using the procedures described |
and planned activity in | | in RFC 2026 [RFC2026]. Appeals of |
enough detail to carry out their fiduciary | | IAOC decisions will go |
responsibility properly. The IASA publishes its complete budget to | | to |
the | | the IESG and continue up the chain as |
IETF community each year. | | necessary (to |
| | |
The IAOC, in consultation with the IAB and the | | the IAB and the ISOC Board). The IAOC will play no |
IESG, designates the | | role in appeals of WG Chair, IESG |
person or | | or IAB decisions. |
| | |
| | 4. IAOC Membership, Selection and Accountability |
| | |
people who | | The IAOC will consist of eight voting members who will be selected as |
| | follows: |
| | |
carry out the tasks which other IETF | | o 2 members chosen by the IETF Nominations Committee (NomCom) |
| | |
process | | o 1 member chosen |
documents say are carried out by the | | by the IESG |
| | |
IETF Executive Director. | | o 1 member chosen by |
| | |
Editors' note: The preceding paragraph has generated some | | |
comments, given that the | | the IAB |
| | |
role of the IETF Executive director is | | o 1 member chosen by the ISOC Board |
mentioned in a number of | | of Trustees |
| | |
documents, some of which are fairly old | | o |
and dusty. The | | The IETF Chair (ex officio) |
| | |
| | o The IAB Chair |
| | |
| | o The ISOC President/CEO (ex officio) |
| | |
| | There will also be a non-voting, ex officio liaison: |
| | |
editors actively solicit feedback on whether this | | o |
paragraph is ok as it stands. | | |
| | |
| | |
3.2 IAD Committees | | |
| | |
The IAD may constitute special-purpose, chartered committees to bring | | The |
in expertise (on topics such as finance, IETF | | IETF Administrative Director |
| | |
process, or tools), to | | Editors' note: There has been some question about whether |
engage volunteers in IASA activities, or to gain additional | | |
perspectives. Such committees may consist of subsets of the IAOC, | | the |
IAB | | IAB |
or IESG, selected IETF participants, or external experts, | | Chair should be a liaison or a voting member of |
depending on the need. These committees are advisory in nature -- | | the IAOC. There are multiple trade-offs here, and this should be discussed by |
the | | the |
| | community. Discussion up till November 15th seems to indicate to |
IAD is responsible for the | | go for voting member, as currently described in the text above. |
| | |
outcome, including presenting and | | The members of |
supporting any decisions or work items to the IAOC and the IETF | | the IAOC will serve two year terms. |
community, as appropriate. | | |
| | |
3.3 IAOC | | IAOC terms will |
Responsibilities | | normally end at |
| | |
The IAOC's role is to provide appropriate direction to the IAD, to | | |
review the IAD's regular reports, and to oversee the IASA functions | | |
to ensure that the administrative needs of the IETF community are | | the first IETF meeting |
being properly met. The IAOC's mission is not to be be engaged in | | |
the day-to-day administrative work of IASA, but rather to provide | | of a year, similar to IAB |
appropriate direction, oversight and | | and |
approval. | | IESG terms. |
| | |
Therefore, the IAOC's responsibilities are: | | |
| | |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 9] | | Austein & Wijnen Expires May 16, 2005 [Page 8] |
| | |
Internet-Draft Structure of IASA November 2004 | | Internet-Draft Structure of IASA November 2004 |
| | |
| | |
| | The members of |
| | |
| | |
o To select the | | the IAOC will choose their own chair each year using a |
| | consensus mechanism of their choosing. Any appointed voting member |
IAD and provide high-level review and direction for | | of the IAOC may serve |
his or her work. This task should be handled by a sub-committee, | | |
as described in Section 3. | | as |
| | |
o To review the IAD's plans and contracts to ensure that they will | | the IAOC Chair; liaisons, |
meet the administrative needs of the IETF. | | the IETF Chair, the IAB Chair, or |
| | |
o To track whether the | | the ISOC President/CEO may not serve as IAOC Chair. |
IASA functions are meeting the IETF | | The role of the IAOC Chair is |
community's administrative needs, and to work with the | | to manage the IAOC. The IAOC Chair has |
IAD to | | no formal duties |
determine a plan for corrective action if they are not. | | for representing |
| | |
o To review the | | the IAOC, except as directed by |
| | IAOC consensus. |
| | |
IAD's budget proposals to ensure that they will meet | | The two NomCom selected members will be selected using |
the | | the procedures |
IETF's needs, and review the IAD's regular financial reports. | | described in RFC 3777 [RFC3777]. For the initial IAOC selection, |
| | |
o To ensure that the | | the |
IASA is run in a transparent and accountable | | IESG will provide |
manner. While the | | the list of desired qualifications for these |
day-to-day work should be delegated to the | | positions. In later years, this list will be provided by the IAOC. |
IAD | | The IESG will serve as |
and others, the IAOC | | the confirming body for IAOC appointments by |
| | the NomCom. |
| | |
is responsible for ensuring that IASA | | While there |
finances and operational status are tracked appropriately, and | | are no hard rules regarding how |
that monthly, quarterly, and annual financial and operational | | |
reports are published to the IETF community. | | the IAB |
| | |
The IAOC's role is to direct and review, not perform, the | | and the IESG |
work of the | | should select members of the IAOC, it is not expected that they will |
| | typically choose current IAB or IESG members, if only |
IAD and IASA. The IAOC holds periodic teleconferences and | | |
face-to-face meetings as needed to | | to avoid |
carry out the | | overloading the existing leadership. They should choose people with |
IAOC's duties | | some knowledge of contracts |
efficiently and | | and financial procedures who are familiar |
effectively. | | with the administrative support needs |
| | |
3.4 Relationship of the IAOC to Existing IETF | | of the IAB, the IESG, or the IETF standards process. It is suggested that a fairly open process |
| | be followed for these selections, perhaps with an open call for |
Leadership | | nominations or a period of public comment on the candidates. |
| | |
The | | The IAB |
IAOC is directly accountable to the IETF community for the | | and IESG are encouraged to look at the procedure for IAB selection |
performance of | | of |
the IASA. However, the nature of | | ISOC Trustees for an example of how this might work. After we gain |
| | some experience with IAOC selection, these selection mechanisms |
| | should be more formally documented. |
| | |
the IAOC's work | | Although the IAB, |
involves treating the IESG and IAB as internal customers. The IAOC | | IESG and ISOC BoT will choose some members of |
and the | | the |
IAD should not consider their work successful unless the | | IAOC, those members will not directly represent the bodies that chose |
IESG | | them. All members of |
and IAB are satisfied with the administrative support that they are | | the IAOC are accountable directly |
receiving. | | |
| | |
3.5 IAOC Decision Making | | |
| | |
The IAOC attempts to | | to the IETF |
reach all decisions unanimously. If unanimity | | community. To receive direct feedback from the community, |
cannot be achieved, the IAOC | | the IAOC |
| | will hold an open meeting at least once per year at an IETF meeting. |
chair may conduct informal polls to | | This may take |
determine the consensus of | | the form of an open IAOC plenary or a working meeting |
| | held during an IETF meeting slot. The form and contents of this |
| | meeting are left to the discretion of the IAOC Chair. The IAOC |
| | should also consider open mailing lists or other means to establish |
the group. In | | open communication with the community. In the event that an IAOC member abrogates his duties or acts against |
| | the bests interests of the IETF community, IAOC members are subject |
cases where it is | | to recall. Any appointed IESG member, including those appointed |
necessary, some decisions may be made by voting. For the purpose of | | by the IAB, IESG or ISOC Board of Trustees, may be recalled using |
judging consensus or voting, only the | | the |
"voting members" (as defined in | | recall procedure defined in RFC 3777 [RFC3777]. |
Section 4) shall be counted. If voting results in a tie, then IAOC | | IAOC members are not |
| | subject |
chair decides how to proceed with the decision process. | | to recall by the body that appointed them. |
| | |
Editors' note: The above text was changed from the previous | | |
version. Are the voting rules in the preceding paragraph | | |
sufficient? Do we need to define rules for determining a quorum? | | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 10] | | Austein & Wijnen Expires May 16, 2005 [Page 9] |
| | |
Internet-Draft Structure of IASA November 2004 | | Internet-Draft Structure of IASA November 2004 |
| | |
| | |
| | 4.1 Initial IAOC Selection |
| | |
| | |
The editors would prefer to specify the minimum necessary | | The initial |
mechanism here, but no less. The text above seems to be | | |
acceptable to most. | | |
| | |
Decisions of IAOC members or the entire IAOC are subject to appeal | | IAOC selection will start after this document is approved |
using the procedures described in RFC 2026 [RFC2026]. Appeals of | | |
IAOC decisions go first to the IESG, then continue up the chain as | | as a BCP by |
necessary to the IAB and the ISOC Board of Trustees. | | the IESG and accepted by the ISOC Board of Trustees. |
| | |
The IAOC plays no role in appeals of WG Chair, IESG, or IAB | | The IESG, IAB |
decisions. | | |
| | |
4. IAOC Membership, Selection and Accountability | | and ISOC should make their selections within 45-days |
| | |
The IAOC will consist of | | of BCP |
| | approval, and the NomCom should make their selections as quickly as |
| | possible while complying with the documented NomCom procedures. The |
eight voting members who will be selected as | | IAOC will become active as soon as a majority (three or more) of the |
| | appointed |
follows: | | |
| | |
o 2 members | | members are selected. |
| | |
chosen by the IETF Nominations Committee (NomCom) | | Initially, |
| | |
o 1 member chosen by the IESG | | the IESG and ISOC Board will make one-year appointments, |
| | |
o 1 member chosen by the IAB | | the IAB will make a two-year appointment, and |
| | |
o 1 member chosen by the | | the NomCom will make |
ISOC Board of Trustees | | one one-year appointment and one two-year appointment to establish |
| | |
o The IETF Chair (ex officio) | | |
| | |
o The IAB Chair (ex officio) | | |
| | |
o The ISOC President/CEO (ex officio) | | |
| | |
The IETF Administrative Director also serves, ex officio, as a | | a |
| | pattern where approximately half |
non-voting member of the IAOC. | | of the |
| | |
The IAOC | | IAOC is selected each year. |
| | |
| | 5. IASA Funding |
| | |
| | Editors' note: Changes were made to this section to be more |
may also | | specific about funding sources and where they go. Some text has also been added or changed regarding the reserve funds. |
| | |
choose to invite liaisons from | | The IASA will manage money from three sources: |
| | |
| | 1. IETF meeting revenues. |
| | |
| | 2. Designated ISOC donations, monetary and in-kind. |
| | |
| | 3. Other ISOC support. |
| | |
other groups, but is | | Note that the goal is |
not required to | | to achieve and maintain a viable IETF support |
do so; the IAOC | | function based on meeting fees and specified donations, and the IAOC |
decides whether or not to have a | | and ISOC are expected to work together |
liaison to | | to attain that goal. For |
any particular group. Any such liaisons are non-voting. | | example, dropping |
Responsibility for selecting the | | the meeting fees to $0 and expecting ISOC to pick |
individual filling a particular | | up |
liaison role with the body from which the | | the slack is not desirable; neither is raising the meeting fees to |
| | prohibitive levels to fund all non-meeting-related activities. |
| | |
| | 5.1 IETF meeting revenues |
| | |
| | Meeting revenues are an important support mechanism for IETF |
IAOC has requested the | | functions. The IAD, in consultation with the IAOC, sets |
liaison. | | |
| | |
Editors' note: There has been some question about whether the | | the meeting |
IAB | | fees as part |
Chair should be a voting or non-voting member of the IAOC. There | | of the budgeting process. All meeting revenues |
are multiple trade-offs here, and this should be discussed by the | | |
community. Discussion up till November 15th seems to indicate to | | |
go for voting member, as currently described in the | | go into the IASA account. |
| | |
| | 5.2 Designated donations, monetary and in-kind |
| | |
| | Donations are an essential component of funding. The IASA undertakes |
text above. | | no direct fund-raising activities. This establishes a practice |
| | |
Earlier versions of | | of |
this document used the term "liaison" to refer | | separating IETF administrative and standards activities from |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 11] | | Austein & Wijnen Expires May 16, 2005 [Page 10] |
| | |
Internet-Draft Structure of IASA November 2004 | | Internet-Draft Structure of IASA November 2004 |
| | |
| | |
| | fund-raising activities, and it helps ensure that no undue influence |
| | may be ascribed to those from whom funds are raised. |
| | |
| | ISOC will create and maintain appropriate structures and programs to |
| | coordinate donations intended |
| | |
| | |
to non-voting IAOC members, but this usage has since been dropped. | | to support |
However, the term begs the question of whether the | | the work of the IETF, and |
| | these will include mechanisms for both in-kind and direct |
IAOC might wish | | contributions |
to have -other- liaisons (ex officio or not), such as liaisons to | | to |
the RFC editor or the | | the work supported by IASA. Since ISOC will be the |
IANA. The text above has been modified to | | sole entity through whom donations may be made to the work |
permit this. Feedback requested. | | |
| | |
Appointed members of the | | of the |
| | IETF, ISOC will ensure that those programs are not unduly |
IAOC serve two year terms. IAOC terms | | restrictive. For |
normally end at the first IETF meeting of a year, just as as IAB and | | the benefit of individuals, smaller organizations and countries with developing economies, it will maintain programs |
| | that allow for designated donations to |
IESG terms do. | | |
| | |
The members of the IAOC choose their own chair each year using | | the IETF either using an |
| | overhead model or other unrestricted donation program. |
| | |
| | ISOC will create appropriate administrative structures to coordinate |
a | | such donations with |
consensus mechanism of their choosing. Any appointed voting member | | |
of the | | the IASA. In particular, it is important that |
IAOC may serve as the IAOC Chair; the IETF Administrative | | in-kind contributions be "useful". In-kind resources are owned by the ISOC on behalf of the IETF |
Director, the IETF Chair, the IAB Chair, the ISOC President/CEO, and | | and shall be reported and accounted |
| | for in a manner that identifies them |
non-voting liaisons are not eligible to serve as | | as such. Designated monetary |
IAOC Chair. The | | donations will be deposited in |
IAOC Chair's role is to manage the | | the IASA account. |
| | |
| | 5.3 Other ISOC support |
| | |
IAOC. The IAOC Chair has no | | Other ISOC support shall be based on |
formal duty to represent the IAOC, except as | | the budget process as specified |
directed by IAOC | | in Section 6. ISOC will deposit |
consensus. | | |
| | |
The two NomCom-selected IAOC members are chosen using the | | the yearly amount (as agreed to in |
procedures | | approved budget) |
described in RFC 3777 [RFC3777]. For the initial IAOC selection, the | | in equal portions. At a minimum such deposits |
IESG will | | will |
| | be made quarterly. |
| | |
provide the | | If ISOC directly funds any other IETF expenses, such as the IETF |
list of desired qualifications for these | | share of ISOC's liability insurance premium, |
positions; in later years, the IAOC will provide this qualification | | this |
list. The IESG will | | will be documented |
| | together with the other IASA accounts. |
| | |
| | 5.4 Operating Reserve |
| | |
serve as the | | In normal operating circumstances, the IASA would look to have an |
confirming body for | | operating reserve for its activities sufficient to cover 6-months of |
IAOC | | non-meeting operational expenses, plus twice |
appointments by the | | the recent average for |
NomCom. | | meeting contract guarantees. Rather than having |
| | |
While there are no hard rules regarding how the | | the IASA attempt to |
IAB and the IESG | | accrue that reserve in its separate account, the IASA looks to ISOC |
should select members of the IAOC, such appointees need not be | | |
current IAB or IESG members (and probably should not be, if only to | | to build |
avoid overloading the existing leadership). The IAB and | | and provide that operational reserve (through whatever |
IESG should | | mechanisms ISOC deems appropriate -- line |
choose people with some knowledge of contracts and financial | | of credit, financial |
| | reserves, meeting cancellation insurance, etc). Such reserves do not |
| | appear instantaneously; |
procedures, who are familiar with the administrative support needs of | | the goal is to reach this level of reserves |
| | by 3 years after |
the IAB, the | | the creation of the IASA. Such funds shall be held |
IESG, or the IETF | | in reserve for use by IASA for use in the event of IETF meeting |
standards process. The IAB and IESG | | cancellation |
should follow a fairly open process for these selections, perhaps | | |
with an open call for nominations or | | or other unexpected fiscal emergencies. These funds |
| | shall be dedicated to IETF support functions. |
| | |
| | |
| | |
| | |
| | Austein & Wijnen Expires May 16, 2005 [Page 11] |
| | |
a period of | | Internet-Draft Structure of IASA November 2004 |
| | |
| | |
| | 6. IASA Budget Process |
| | |
public comment on | | While |
the candidates. The procedure for IAB selection of ISOC Board of | | the IASA sets |
Trustees [RFC3677] might be a good model for how this could work. | | a budget for |
After the | | the IETF's administrative needs, its |
IETF gains some experience with | | budget process clearly needs to be closely coordinated with ISOC's. |
IAOC selection, these | | The specific timeline will |
selection mechanisms should be | | be established each year. A general |
| | annual timeline for budgeting will be: |
| | |
| | July 1: The IAD presents a budget proposal for the following fiscal |
more formally documented. | | year, with 3 year projections, to |
| | |
Although the | | the IAOC. |
| | |
IAB, the | | August 1: The IAOC approves the budget proposal for IETF purposes, |
IESG and the ISOC Board of Trustees choose some | | after any appropriate revisions. As the ISOC President is part |
members of the IAOC, those members do not directly represent the | | of the IAOC, the IAOC should have a preliminary indication |
bodies that chose them. All members of the | | of how the |
| | budget will fit with ISOC's own budgetary expectations. The |
IAOC are accountable | | budget proposal is passed |
directly to the | | to the ISOC Board of Trustees for review |
| | in accordance with their fiduciary duty. |
| | |
| | September 1: The ISOC Board of Trustees approves the budget proposal |
IETF community. To receive direct feedback from the | | provisionally. During the next 2 months, |
community, the IAOC holds an open meeting at least once per year at | | the budget |
an IETF meeting. This may | | may be |
| | revised to be integrated in ISOC's overall budgeting process. |
| | |
| | November 1: Final budget to the ISOC Board for approval. |
| | |
| | The dates described above are subject to change, and will most likely |
take the form of an open IAOC plenary or a | | be modified based on the dates of the Second and Third |
working meeting held during an IETF meeting slot. The form and | | IETF meetings. The IAD will provide monthly accountings of expenses, and will update |
| | forecasts |
contents of this meeting are left to the | | of expenditures quarterly. This may necessitate the |
discretion of the IAOC | | adjustment of the |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 12] | | |
| | |
Internet-Draft Structure of IASA November 2004 | | IASA budget. |
| | |
| | |
Chair. The IAOC should also consider open mailing lists or other | | The revised budget will need |
means to | | to be |
establish open communication with the | | approved by the IAOC, the ISOC President/CEO and, if necessary, the |
| | ISOC Board of Trustees. |
| | |
| | 7. ISOC Responsibilities for IASA |
| | |
community. | | Within ISOC, support for the IASA should be structured |
| | |
IAOC members are subject to recall in the | | to meet the |
| | following goals: |
| | |
event that an IAOC member | | Transparency: The IETF community should have complete visibility into |
abrogates his or her duties or acts against the best interests of the | | the financial and legal structure of the ISOC standards activity. |
| | In particular, the |
IETF | | IETF community should have access to a detailed |
community. Any appointed IAOC member, including those appointed | | budget for |
by the | | the entire standards activity, quarterly financial |
| | reports and audited annual financials. In addition, key contract |
IAB, IESG or ISOC Board of | | material and MOUs should be publicly available. Most of these |
Trustees, may be recalled using the | | goals |
recall procedure defined in RFC 3777 [RFC3777]. IAOC members are | | are already met |
not, however, subject to recall by the bodies that appointed them. | | by ISOC today. |
| | |
4.1 Initial IAOC Selection | | |
| | |
The initial IAOC selection will | | The IAOC will be responsible |
start after this document is approved | | for providing |
as a BCP by the IESG and accepted by the | | the IETF community with regular overviews of the |
| | state of affairs. |
| | |
| | |
| | |
| | |
| | |
| | Austein & Wijnen Expires May 16, 2005 [Page 12] |
| | |
ISOC Board of | | Internet-Draft Structure of IASA November 2004 |
| | |
| | |
Trustees. The | | Unification: As part |
IESG, IAB, and ISOC Board of Trustees should make their selections | | of this arrangement, ISOC's sponsorship |
within 45-days of | | of the |
BCP approval, and the NomCom should make their | | RFC Editor, IAB and IESG |
selections as quickly as possible while complying with the documented | | |
NomCom procedures. The IAOC will become active as soon as a majority | | will be managed as part |
(three or more) of the appointed members have been selected. | | of the IASA under |
| | |
Initially, the | | the IAOC. |
| | |
IESG and | | Independence: The IASA should be financially and legally distinct |
the ISOC | | from other ISOC activities. IETF meeting fees should be deposited |
Board of Trustees will make one-year | | in |
appointments, the IAB will make a two-year appointment, and | | a separate IETF-specific financial account and used to fund the |
the | | IASA under the direction |
NomCom will make one one-year appointment and | | and oversight of the IAOC. Any fees or |
| | payments collected from IETF meeting sponsors should also be |
one two-year | | deposited into this account. |
appointment. This will | | This account will be administered by |
establish a pattern in which approximately | | the IAD and used to fund |
half of the IAOC is selected each year. | | the |
| | |
5. IASA | | IASA in accordance with a budget and |
| | policies that are developed as described above. |
| | |
Funding | | Support: ISOC may, from time to time, choose |
| | |
Editors' note: Changes were made to | | to transfer other funds |
this section to | | into this account to fund IETF administrative projects or to cover |
be more | | IETF meeting revenue shortfalls. There may also be cases |
specific about funding sources and where | | where |
they go. Some text has | | ISOC chooses to loan money to |
also been added or changed regarding the | | the IASA to help with temporary cash |
| | flow issues. These cases should be carefully documented and |
reserve funds. | | tracked on both sides. ISOC will work |
| | |
Disclaimer: The IAOC is authorized to vary the | | to provide the operational |
procedures for | | reserve for IASA functioning described above. |
| | |
legal, | | Removability: While there is no current plan |
accounting or practical reasons as long as it reports the variance to | | to transfer |
the IETF community and triggers an update of this BCP. | | the legal and financial home of the |
| | |
The IASA manages money from three sources: | | IASA |
| | |
1. IETF meeting revenues. | | |
| | |
2. Designated donations to ISOC (both monetary and in-kind). | | to another corporation, |
| | |
3. Other ISOC support. | | |
| | |
Note that the | | the IASA |
goal is to | | should be structured to enable a clean transition in the event |
achieve and maintain a viable IETF support | | that the |
function based on meeting fees and designated donations. The IETF | | IETF |
community | | community decides, through BCP publication, that |
| | such a transition is required. In that case, the IAOC will give |
| | ISOC a minimum of six-months notice before the transition formally |
expects the IAOC and ISOC to work together to attain that | | occurs. During that period, the IAOC and ISOC will work together to create a smooth transition that does not result in any |
| | significant service outages or missed IETF meetings. All |
| | contracts |
goal, and recognizes that doing so will require striking some sort of | | that are executed by ISOC as part |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 13] | | |
| | |
Internet-Draft Structure of IASA | | of the IASA should |
November 2004 | | either include a clause allowing termination or transfer by |
| | |
| | |
balance. For example, dropping the meeting fees to $0 and expecting | | |
ISOC | | ISOC |
to | | with six months notice, or should be transferable to another |
pick up the | | corporation in the event that the IASA is transitioned away from |
slack would not be viable in the long term, and | | ISOC in the future. Any accrued funds, and IETF-specific |
| | intellectual property rights concerning administrative data or |
| | tools |
neither would be raising the meeting fees to prohibitive levels in | | would also be expected to be transitioned |
order to fund all non-meeting-related activities. | | to |
| | |
5.1 Divisional Accounting | | |
| | |
Editors' note: Added following paragraph on Divisional accounting | | |
(thanks Glenn Ricart) and then removed the | | the new entity, |
| | as well. |
| | |
text about "deposit in | | Within |
IASA account" from subsections below. To the best of the editors' | | the constraints outlined above, all other details of how |
ability to | | to |
determine the will of the community, there does not | | structure this activity within ISOC (whether |
appear to be enough support to prescribe separate bank accounts, | | |
and Divisional Accounting as described below should suffice to | | as |
achieve transparency. If you do not agree, please speak up ASAP. | | |
| | |
For bookkeeping purposes, funds managed by IASA should be kept in a | | a cost center, |
separate set of accounts which can be rolled-up periodically to the | | |
equivalent of a | | a |
balance sheet and a profit and loss statement for | | department, or a formal subsidiary) shall be determined |
IASA alone after taking into account the effect of common items paid | | |
for or received by ISOC as a whole. | | by ISOC |
| | |
5.2 IETF meeting revenues | | |
| | |
Meeting revenues are an important source of funds for IETF functions. | | |
The IAD, in consultation with the | | in consultation with the IAOC. |
| | |
IAOC, sets the meeting fees as part | | 8. Security Considerations |
of the budgeting process. All meeting revenues will be credited to | | |
the appropriate IASA account. | | |
| | |
5.3 Designated donations, monetary and in-kind | | |
| | |
Donations are an essential component of funding. The IASA undertakes | | |
no direct fund-raising activities. This establishes a practice of | | |
separating IETF administrative and standards activities from | | |
fund-raising activities, and helps ensure that no undue influence may | | |
be ascribed to those from whom funds are raised. | | |
| | |
ISOC will create and maintain appropriate structures and programs to | | |
coordinate donations intended to support the work of the IETF, and | | |
these will include mechanisms for both in-kind and direct | | |
contributions to the work supported by IASA. Since ISOC will be the | | |
sole entity through whom donations may be made to the work of the | | |
IETF, ISOC will ensure that those programs are not unduly | | |
restrictive. For the benefit of individuals, smaller organizations | | |
and countries with developing economies, it will maintain programs | | |
that allow for designated donations to the IETF. | | |
| | |
Editors' note: Some have suggested we need explicit IETF consensus | | |
on the above. So if you do not agree, please speak up ASAP. | | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 14] | | |
| | |
Internet-Draft Structure of IASA November 2004 | | |
| | |
| | |
Editors' note: Removed "either using an overhead model or other | | |
unrestricted donation program." because it is too detailed and | | |
prescriptive. Send objections ASAP if you do not agree. | | |
| | |
ISOC will create appropriate administrative structures to coordinate | | |
such donations with the IASA. In particular, it is important that | | |
in-kind contributions be "useful". In-kind resources are owned by | | |
the ISOC on behalf of the IETF and shall be reported and accounted | | |
for in a manner that identifies them as such. Designated monetary | | |
donations will be credited to the appropriate IASA account. | | |
| | |
5.4 Other ISOC support | | |
| | |
Other ISOC support shall be based on the budget process as specified | | |
in Section 6. ISOC will credit the appropriate IASA accounts at | | |
least quarterly. | | |
| | |
If ISOC pays any other IETF expenses directly, without transferring | | |
funds to the IASA, this will be documented as a footnote to the IASA | | |
accounts. | | |
| | |
5.5 Operating Reserve | | |
| | |
In normal operating circumstances, the IASA should have an operating | | |
reserve for its activities sufficient to cover 6-months of | | |
non-meeting operational expenses, plus twice the recent average for | | |
meeting contract guarantees. Rather than having the IASA attempt to | | |
build that reserve in its separate accounts, the IASA looks to ISOC | | |
to build and provide that operational reserve, through whatever | | |
mechanisms ISOC deems appropriate: line of credit, financial | | |
reserves, meeting cancellation insurance, and so forth. Such | | |
reserves do not appear instantaneously; the goal is to reach this | | |
level of reserves within 3 years after the creation of the IASA. | | |
Such funds shall be held in reserve for use by IASA for use in the | | |
event of IETF meeting cancellation or other unexpected fiscal | | |
emergencies. These reserves shall only be spent on IETF support | | |
functions. | | |
| | |
6. IASA Budget Process | | |
| | |
While the IASA sets a budget for the IETF's administrative needs, its | | |
budget process clearly needs to be closely coordinated with ISOC's. | | |
The specific timeline will be established each year. A general | | |
annual timeline for budgeting will be: | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 15] | | |
| | |
Internet-Draft Structure of IASA November 2004 | | |
| | |
| | |
July 1: The IAD presents a budget proposal for the following fiscal | | |
year, with 3 year projections, to the IAOC. | | |
| | |
August 1: The IAOC approves the budget proposal for IETF purposes, | | |
after any appropriate revisions. As the ISOC President is part of | | |
the IAOC, the IAOC should have a preliminary indication of how the | | |
budget will fit with ISOC's own budgetary expectations. The | | |
budget proposal is passed to the ISOC Board of Trustees for review | | |
in accordance with their fiduciary duty. | | |
| | |
September 1: The ISOC Board of Trustees approves the budget proposal | | |
provisionally. During the next 2 months, the budget may be | | |
revised to be integrated in ISOC's overall budgeting process. | | |
| | |
November 1: Final budget to the ISOC Board for approval. | | |
| | |
The dates described above are subject to change, and will most likely | | |
be modified each year based on the dates of the second and third IETF | | |
meetings of that year. | | |
| | |
The IAD shall provide monthly accountings of expenses, and shall | | |
update expenditures forecasts every quarter. This may require | | |
adjustment of the IASA budget: if so, the revised budget will need to | | |
be approved by the IAOC, the ISOC President/CEO and, if necessary, | | |
the ISOC Board of Trustees. | | |
| | |
7. ISOC Responsibilities for IASA | | |
| | |
Within ISOC, support for the IASA should meet the following goals: | | |
| | |
Transparency: The IETF community should have complete visibility into | | |
the financial and legal structure of the ISOC standards activity. | | |
In particular, a detailed budget for the entire standards | | |
activity, quarterly financial reports, and audited annual | | |
financials should all be available to the IETF community. In | | |
addition, key contract material and MOUs should also be publicly | | |
available. The IAOC is responsible for providing regular | | |
overviews of the state of the IASA to the IETF community. | | |
| | |
Unification: As part of this arrangement, ISOC's sponsorship of the | | |
RFC Editor, IAB and IESG shall be managed as part of the IASA | | |
under the IAOC. | | |
| | |
Independence: The IASA should be financially and legally distinct | | |
from other ISOC activities. IETF meeting fees shall be deposited | | |
in a separate IETF-specific financial account and used to fund the | | |
IASA under the direction and oversight of the IAOC. Any fees or | | |
payments collected from IETF meeting sponsors should also be | | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 16] | | |
| | |
Internet-Draft Structure of IASA November 2004 | | |
| | |
| | |
deposited into this account. The IAD administers this account and | | |
uses it to fund the IASA in accordance with a budget and policies | | |
developed as described above. | | |
| | |
Support: ISOC may, from time to time, choose to transfer other funds | | |
into the IASA account to fund IETF administrative projects or to | | |
cover IETF meeting revenue shortfalls. There may also be cases | | |
where ISOC chooses to loan money to the IASA to help with | | |
temporary cash flow issues. These cases should be documented | | |
carefully and tracked on both sides. ISOC will work to provide | | |
the operational reserve for IASA functioning described above. | | |
| | |
Removability: While there is no current plan to transfer the legal | | |
and financial home of the IASA to another corporation, the IASA | | |
should be structured to enable a clean transition in the event | | |
that the IETF community decides, through BCP publication, that | | |
such a transition is required. In such a case case, the IAOC will | | |
give ISOC a minimum of six months notice before the transition | | |
formally occurs. During that period, the IAOC and ISOC will work | | |
together to create a smooth transition that does not result in any | | |
significant service outages or missed IETF meetings. All | | |
contracts executed by ISOC on behalf of IASA should either include | | |
a clause allowing termination or transfer by ISOC with six months | | |
notice, or should be transferable to another corporation in the | | |
event that the IASA transitions away from ISOC. Any accrued funds | | |
or IETF-specific intellectual property rights concerning | | |
administrative data and tools should also transition to the new | | |
entity. | | |
| | |
Within the constraints outlined above, all other details of how to | | |
structure this activity within ISOC (whether as a cost center, a | | |
department, or a formal subsidiary) shall be determined by ISOC in | | |
consultation with the IAOC. | | |
| | |
8. Security Considerations | | |
| | |
This document describes the structure of the IETF's administrative | | |
support activity. It introduces no security considerations for the | | |
Internet. | | |
| | |
9. IANA Considerations | | |
| | |
This document has no IANA considerations in the traditional sense. | | |
However, some of the information in this document may affect how the | | |
IETF standards process interfaces with IANA, so IANA may be | | |
interested in the contents. | | |
| | |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 17] | | |
| | |
Internet-Draft Structure of IASA November 2004 | | |
| | |
| | |
10. Acknowledgements | | |
| | |
The editors would like to thank the following people for their | | |
feedback on the original "Scenario O" e-mail message or intermediate | | |
versions of this document: Bernard Aboba, Harald Alvestrand, Scott | | |
Bradner, Brian Carpenter, Dave Crocker, Tony Hain, Joel Halpern, Sam | | |
Hartman, John Klensin, Valdis Kletnieks, Eliot Lear, Carl Malamud, | | |
and Glenn Ricart. | | |
| | |
Particular thanks are due to Leslie Daigle and Margaret Wasserman, | | |
who wrote the original "Scenario O" message and edited the earliest | | |
versions of this document. | | |
| | |
This document was written using the xml2rfc tool described in RFC | | |
2629 [RFC2629]. | | |
| | |
No doubt the above list is incomplete. We apologize to anyone whom | | |
we left out. | | |
| | |
11. References | | |
| | |
11.1 Normative References | | |
| | |
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision | | |
3", BCP 9, RFC 2026, October 1996. | | |
| | |
[RFC3716] Advisory, IAB., "The IETF in the Large: Administration and | | |
Execution", RFC 3716, March 2004. | | |
| | |
[RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and | | |
Recall Process: Operation of the Nominating and Recall | | |
Committees", BCP 10, RFC 3777, June 2004. | | |
| | |
11.2 Informative References | | |
| | |
[ISOC] Internet Society, "Internet Society By-Laws", February | | |
2001, | | |
<http://www.isoc.org/isoc/general/trustees/bylaws.shtml>. | | |
| | |
[RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031, October | | |
1996. | | |
| | |
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, | | |
June 1999. | | |
| | |
[RFC2850] Internet Architecture Board and B. Carpenter, "Charter of | | |
the Internet Architecture Board (IAB)", BCP 39, RFC 2850, | | |
May 2000. | | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 18] | | |
| | |
Internet-Draft Structure of IASA November 2004 | | |
| | |
| | |
[RFC3668] Bradner, S., "Intellectual Property Rights in IETF | | |
Technology", BCP 79, RFC 3668, February 2004. | | |
| | |
[RFC3677] Daigle, L. and Internet Architecture Board, "IETF ISOC | | |
Board of Trustee Appointment Procedures", BCP 77, RFC | | |
3677, December 2003. | | |
| | |
[RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, February | | |
2004. | | |
| | |
| | |
Authors' Addresses | | |
| | |
Rob Austein (editor) | | |
Internet Systems Consortium | | |
950 Charter Street | | |
Redwood City, CA 94063 | | |
USA | | |
| | |
EMail: sra@isc.org | | |
| | |
| | |
Bert Wijnen (editor) | | |
Lucent Technologies | | |
Schagen 33 | | |
3461 GL Linschoten | | |
NL | | |
| | |
EMail: bwijnen@lucent.com | | |
| | |
Appendix A. Change Log | | |
| | |
Note to RFC Editor: Please remove this entire appendix prior to | | |
publication. | | |
| | |
This document was produced as part of the | | This document describes the structure of the IETF's administrative |
overall IETF Administrative | | support activity. It introduces no security considerations for |
Restructuring (AdminRest) effort. Information about the effort and | | |
related documents can be found at: | | |
| | |
http://www.alvestrand.no/ietf/adminrest | | |
| | |
We are using an issue tracker to track the editorial and substantive | | the |
feedback on this document. It can be found at: | | |
| | |
https://rt.psg.com (user: ietf, password: ietf, queue: iasa-bcp). | | |
| | |
Changes in draft-ietf-iasa-bcp-01.txt: | | |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 19] | | Austein & Wijnen Expires May 16, 2005 [Page 13] |
| | |
Internet-Draft Structure of IASA November 2004 | | Internet-Draft Structure of IASA November 2004 |
| | |
| | |
| | Internet. |
| | |
| | 9. IANA Considerations |
| | |
| | This document has no IANA considerations in the traditional sense. |
| | However, some |
| | |
| | |
o Added a list of | | of the information in this document may affect how the |
| | IETF standards process interfaces with IANA, so IANA may be |
| | interested in the contents. |
| | |
| | 10. Acknowledgements |
| | |
open issues (Section 1.2). | | The editors would like to thank the following people |
| | |
o Added that small committee determines initial compensation for | | for their |
| | feedback on the original "Scenario O" e-mail message or intermediate |
| | versions |
IAD. | | |
| | |
o Added a set of | | of this document: Bernard Aboba, Harald Alvestrand, Brian |
| | Carpenter, Dave Crocker, Tony Hain, Joel Halpern, John Klensin, and |
| | Eliot Lear. |
| | |
Principles (Section 2.2) on which any details are | | Particular thanks are due to Leslie Daigle and Margaret Wasserman, |
| | who wrote the original "Scenario O" message |
(should be) based. | | |
| | |
o Added "Community Consensus and | | and edited the earliest |
Grant of | | versions of this document. |
| | |
| | This document was written using the xml2rfc tool described in RFC |
| | 2629 [RFC2629]. |
| | |
Authority" (Section 2.3). | | No |
| | |
o Added more acknowledgments (no doubt still incomplete). | | doubt |
| | |
o Clarified Section 5 and subsections. Added Editors' note. | | |
| | |
o Clarified what happens if IAOC voting results in a tie. | | |
| | |
o Changed the selection of person(s) to | | the above list is incomplete. We apologize to anyone whom |
| | we left out. |
| | |
| | 11. Change Log |
| | |
act as IETF Executive | | This document was produced as part |
Director. | | |
| | |
o Added a disclaimer in Section 5, stating that IAOC can deal with | | |
changes because of | | of the overall IETF Administrative |
legal, accounting or practical reasons. | | Restructuring (AdminRest) effort. Information about the effort |
| | |
o Removed "insurance" example in Section 5.4. | | |
| | |
o Added a reference to ISOC bylaws. | | |
| | |
o Stop using term "liaison" to mean "non-voting IAOC member"; | | |
instead, spell out which members are voting and | | and |
| | related documents can be found at: |
| | |
| | http://www.alvestrand.no/ietf/adminrest |
| | |
which are not. | | We are using an issue tracker |
Add text allowing IAOC to request non-voting liaisons from other | | to track the |
bodies. | | |
| | |
o Various editorial | | editorial and substantive |
| | feedback on this document. It can be found at: |
| | |
cleanups. | | https://rt.psg.com (user: ietf, password: ietf, queue: iasa-bcp). |
| | |
Changes in draft-ietf-iasa-bcp-00.txt: | | Changes in draft-ietf-iasa-bcp-00.txt: |
| | |
o Modified the text of Section 5. | | o Modified the text of the section on Funding. |
| | |
o Added text on Reserve funds. | | o Added text on Reserve funds. |
| | |
o Made IAB chair a voting member of IAOC; added tie-breaker rule | | o Made IAB chair a voting member of IAOC; added tie-breaker rule |
that if voting results in equal split, then IAOC chair decides. | | that if voting results in equal split, then IAOC chair decides. |
| | |
| | |
| | |
| | Austein & Wijnen Expires May 16, 2005 [Page 14] |
| | |
| | Internet-Draft Structure of IASA November 2004 |
| | |
o Changed 2nd para in "Structure of IASA" sect to replace the fuzzy | | o Changed 2nd para in "Structure of IASA" sect to replace the fuzzy |
term "executive-level" and to be clear about cost aspects. | | term "executive-level" and to be clear about cost aspects. |
| | |
o Made it explicit that IESG only conforms the IAOC appoints made by | | o Made it explicit that IESG only conforms the IAOC appoints made by |
the NomCom. | | the NomCom. |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 20] | | |
| | |
Internet-Draft Structure of IASA November 2004 | | |
| | |
| | |
o Editorial changes at various places in the document. | | o Editorial changes at various places in the document. |
| | |
Changes in draft-wasserman-iasa-bcp-01.txt: | | Changes in draft-wasserman-iasa-bcp-01.txt: |
| | |
o Adjusted the description of the IAD role and reporting structure | | o Adjusted the description of the IAD role and reporting structure |
to make it clear that the IAD is expected to serve as | | to make it clear that the IAD is expected to serve as |
executive-level management for IASA, with only high-level | | executive-level management for IASA, with only high-level |
direction (not day-to-day management) from the IAOC. | | direction (not day-to-day management) from the IAOC. |
| | |
o Removed some troublesome wording regarding termination of the IAD | | o Removed some troublesome wording regarding termination of the IAD |
by the ISOC President/CEO. | | by the ISOC President/CEO. |
| | |
o Moved the initial IAOC selection into a separate section and added | | o Moved the initial IAOC selection into a separate section and added |
some text describing how and when the initial IAOC will be seated. | | some text describing how and when the initial IAOC will be seated. |
| | |
o Added the concept of IAD committees, largely taken from Leslie | | o Added the concept of IAD committees, largely taken from Leslie |
Daigle's original AdminRest proposal. | | Daigle's original AdminRest proposal. |
| | |
o Performed some general text editing and clean-up. | | o Performed some general text editing and clean-up. |
| | |
Origination of draft-wasserman-iasa-bcp-00.txt: | | Origination of draft-wasserman-iasa-bcp-00.txt: |
| | |
draft-wasserman-iasa-bcp-00.txt was derived from an e-mail message | | draft-wasserman-iasa-bcp-00.txt was derived from an e-mail message |
written by Leslie Daigle and Margaret Wasserman and posted to the | | written by Leslie Daigle and Margaret Wasserman and posted to the |
IETF by Leslie Daigle. The original message can be found at: | | IETF by Leslie Daigle. The original message can be found at: |
| | |
http://www1.ietf.org/mail-archive/web/ietf/current/msg31326.html | | http://www1.ietf.org/mail-archive/web/ietf/current/msg31326.html |
| | |
This document was derived from the "Draft BCP" portion of that | | This document was derived from the "Draft BCP" portion of that |
message and has been updated based on comments received. | | message and has been updated based on comments received. |
| | |
| | 12. References |
| | |
| | 12.1 Normative References |
| | |
| | [RFC2026] Bradner, S., "The Internet Standards Process -- Revision |
| | 3", BCP 9, RFC 2026, October 1996. |
| | |
| | [RFC3716] Advisory, IAB., "The IETF in the Large: Administration and |
| | Execution", RFC 3716, March 2004. |
| | |
| | [RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and |
| | |
| | |
| | |
| | Austein & Wijnen Expires May 16, 2005 [Page 15] |
| | |
| | Internet-Draft Structure of IASA November 2004 |
| | |
| | |
| | Recall Process: Operation of the Nominating and Recall |
| | Committees", BCP 10, RFC 3777, June 2004. |
| | |
| | 12.2 Informative References |
| | |
| | [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, |
| | June 1999. |
| | |
| | [RFC3667] Bradner, S., "IETF Rights in Contributions", BCP 78, RFC |
| | 3667, February 2004. |
| | |
| | [RFC3668] Bradner, S., "Intellectual Property Rights in IETF |
| | Technology", BCP 79, RFC 3668, February 2004. |
| | |
| | |
| | Authors' Addresses |
| | |
| | Rob Austein (editor) |
| | Internet Systems Consortium |
| | 950 Charter Street |
| | Redwood City, CA 94063 |
| | USA |
| | |
| | EMail: sra@isc.org |
| | |
| | |
| | Bert Wijnen (editor) |
| | Lucent Technologies |
| | Schagen 33 |
| | 3461 GL Linschoten |
| | NL |
| | |
| | EMail: bwijnen@lucent.com |
| | |
$Revision: 1.1 $ | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 21] | | Austein & Wijnen Expires May 16, 2005 [Page 16] |
| | |
Internet-Draft Structure of IASA November 2004 | | Internet-Draft Structure of IASA November 2004 |
| | |
| | |
Intellectual Property Statement | | Intellectual Property Statement |
| | |
The IETF takes no position regarding the validity or scope of any | | The IETF takes no position regarding the validity or scope of any |
Intellectual Property Rights or other rights that might be claimed to | | Intellectual Property Rights or other rights that might be claimed to |
pertain to the implementation or use of the technology described in | | pertain to the implementation or use of the technology described in |
this document or the extent to which any license under such rights | | this document or the extent to which any license under such rights |
might or might not be available; nor does it represent that it has | | might or might not be available; nor does it represent that it has |
made any independent effort to identify any such rights. Information | | made any independent effort to identify any such rights. Information |
on the procedures with respect to rights in RFC documents can be | | on the procedures with respect to rights in RFC documents can be |
found in BCP 78 and BCP 79. | | found in BCP 78 and BCP 79. |
| | |
Copies of IPR disclosures made to the IETF Secretariat and any | | Copies of IPR disclosures made to the IETF Secretariat and any |
assurances of licenses to be made available, or the result of an | | assurances of licenses to be made available, or the result of an |
attempt made to obtain a general license or permission for the use of | | attempt made to obtain a general license or permission for the use of |
such proprietary rights by implementers or users of this | | such proprietary rights by implementers or users of this |
specification can be obtained from the IETF on-line IPR repository at | | specification can be obtained from the IETF on-line IPR repository at |
http://www.ietf.org/ipr. | | http://www.ietf.org/ipr. |
| | |
The IETF invites any interested party to bring to its attention any | | The IETF invites any interested party to bring to its attention any |
copyrights, patents or patent applications, or other proprietary | | copyrights, patents or patent applications, or other proprietary |
rights that may cover technology that may be required to implement | | rights that may cover technology that may be required to implement |
this standard. Please address the information to the IETF at | | this standard. Please address the information to the IETF at |
ietf-ipr@ietf.org. | | ietf-ipr@ietf.org. |
| | |
| | |
Disclaimer of Validity | | Disclaimer of Validity |
| | |
This document and the information contained herein are provided on an | | This document and the information contained herein are provided on an |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS | | "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET | | OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET |
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, | | ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, |
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE | | INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE |
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED | | INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | | WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| | |
| | |
Copyright Statement | | Copyright Statement |
| | |
Copyright (C) The Internet Society (2004). This document is subject | | Copyright (C) The Internet Society (2004). This document is subject |
to the rights, licenses and restrictions contained in BCP 78, and | | to the rights, licenses and restrictions contained in BCP 78, and |
except as set forth therein, the authors retain all their rights. | | except as set forth therein, the authors retain all their rights. |
| | |
| | |
Acknowledgment | | Acknowledgment |
| | |
Funding for the RFC Editor function is currently provided by the | | Funding for the RFC Editor function is currently provided by the |
Internet Society. | | Internet Society. |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires May 31, 2005 [Page 22] | | Austein & Wijnen Expires May 16, 2005 [Page 17] |
| | |
| |
|