draft-ietf-iasa-bcp-03.txt | | draft-ietf-iasa-bcp-02.txt |
---|
| | |
| | |
Network Working Group R. Austein, Ed. | | Network Working Group R. Austein, Ed. |
Internet-Draft ISC | | Internet-Draft ISC |
Expires: June 23, 2005 B. Wijnen, Ed. | | Expires: June 7, 2005 B. Wijnen, Ed. |
Lucent Technologies | | Lucent Technologies |
December 23, 2004 | | December 7, 2004 |
| | |
| | |
Structure of the IETF Administrative Support Activity (IASA) | | Structure of the IETF Administrative Support Activity (IASA) |
| | draft-ietf-iasa-bcp-02 |
draft-ietf-iasa-bcp-03 | | |
| | |
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 June 23, 2005. | | This Internet-Draft will expire on June 7, 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 |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 1] | | Austein & Wijnen Expires June 7, 2005 [Page 1] |
| | |
Internet-Draft Structure of IASA December 2004 | | Internet-Draft Structure of IASA December 2004 |
| | |
| | |
also defines the membership and selection rules for the IAOC. | | also defines the membership and selection rules for the IAOC. |
| | |
Table of Contents | | Table of Contents |
| | |
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 | | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 |
1.1 Editors' Notes . . . . . . . . . . . . . . . . . . . . . . 4 | | 1.1 Editors' Notes . . . . . . . . . . . . . . . . . . . . . . 4 |
1.2 | | 1.2 Closed Issues . . . . . . . . . . . . . . . . . . . . . . 4 |
Open Issues . . . . . . . . . . . . . . . . . . . . . . . 4 | | 1.3 Open Issues . . . . . . . . . . . . . . . . . . . . . . . 5 |
2. Definitions and Principles . . . . . . . . . . . . . . . . . . 5 | | 2. Definitions and Principles . . . . . . . . . . . . . . . . . . 6 |
2.1 Alphabet Soup . . . . . . . . . . . . . . . . . . . . . . 5 | | 2.1 Alphabet Soup . . . . . . . . . . . . . . . . . . . . . . 6 |
2.2 Principles of the IASA, IETF and ISOC relationship . . . . 5 | | 2.2 Principles of the IASA, IETF and ISOC relationship . . . . 7 |
2.3 Community Consensus and Grant of Authority . . . . . . . . 7 | | 2.3 Community Consensus and Grant of Authority . . . . . . . . 8 |
2.4 Termination and Change . . . . . . . . . . . . . . . . . . 7 | | 2.4 Termination and Change . . . . . . . . . . . . . . . . . . 8 |
2.5 Effective Date for Commencement of IASA . . . . . . . . . 7 | | 2.5 Effective Date for Commencement of IASA . . . . . . . . . 8 |
3. Structure of the IASA . . . . . . . . . . . . . . . . . . . . 7 | | 3. Structure of the IASA . . . . . . . . . . . . . . . . . . . . 8 |
3.1 IAD Responsibilities . . . . . . . . . . . . . . . . . . . 8 | | 3.1 IAD Responsibilities . . . . . . . . . . . . . . . . . . . 9 |
3.2 IAOC Responsibilities . . . . . . . . . . . . . . . . . . 9 | | 3.2 IAOC Responsibilities . . . . . . . . . . . . . . . . . . 11 |
3.3 Relationship of the IAOC to Existing IETF Leadership . . . 10 | | 3.3 Relationship of the IAOC to Existing IETF Leadership . . . 11 |
3.4 IAOC Decision Making . . . . . . . . . . . . . . . . . . . 10 | | 3.4 IAOC Decision Making . . . . . . . . . . . . . . . . . . . 12 |
4. IAOC Membership, Selection and Accountability . . . . . . . . 11 | | 4. IAOC Membership, Selection and Accountability . . . . . . . . 12 |
4.1 Initial IAOC Selection . . . . . . . . . . . . . . . . . . 13 | | 4.1 Initial IAOC Selection . . . . . . . . . . . . . . . . . . 14 |
5. IASA Funding . . . . . . . . . . . . . . . . . . . . . . . . . 13 | | 5. IASA Funding . . . . . . . . . . . . . . . . . . . . . . . . . 14 |
5.1 Divisional Accounting . . . . . . . . . . . . . . . . . . 14 | | 5.1 Divisional Accounting . . . . . . . . . . . . . . . . . . 15 |
5.2 IETF Meeting Revenues . . . . . . . . . . . . . . . . . . 14 | | 5.2 IETF Meeting Revenues . . . . . . . . . . . . . . . . . . 15 |
5.3 Designated Donations, Monetary and In-Kind . . . . . . . . 14 | | 5.3 Designated Donations, Monetary and In-Kind . . . . . . . . 15 |
5.4 Other ISOC Support . . . . . . . . . . . . . . . . . . . . 15 | | 5.4 Other ISOC Support . . . . . . . . . . . . . . . . . . . . 16 |
5.5 IASA Expenses . . . . . . . . . . . . . . . . . . . . . . 15 | | 5.5 IASA Expenses . . . . . . . . . . . . . . . . . . . . . . 16 |
5.6 Operating Reserve . . . . . . . . . . . . . . . . . . . . 15 | | 5.6 Operating Reserve . . . . . . . . . . . . . . . . . . . . 16 |
6. IASA Budget Process . . . . . . . . . . . . . . . . . . . . . 15 | | 6. IASA Budget Process . . . . . . . . . . . . . . . . . . . . . 16 |
7. ISOC Responsibilities for IASA . . . . . . . . . . . . . . . . 16 | | 7. ISOC Responsibilities for IASA . . . . . . . . . . . . . . . . 17 |
8. Security Considerations . . . . . . . . . . . . . . . . . . . 17 | | 8. Security Considerations . . . . . . . . . . . . . . . . . . . 18 |
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 | | 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 |
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 | | 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 |
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 | | 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 |
11.1 Normative References . . . . . . . . . . . . . . . . . . . . 18 | | 11.1 Normative References . . . . . . . . . . . . . . . . . . . . 19 |
11.2 Informative References . . . . . . . . . . . . . . . . . . . 18 | | 11.2 Informative References . . . . . . . . . . . . . . . . . . . 19 |
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 19 | | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 20 |
A. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 19 | | A. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 20 |
A.1 Changes in draft-ietf-iasa-bcp-03.txt . . . . . . . . . . 20 | | A.1 Changes in draft-ietf-iasa-bcp-02.txt . . . . . . . . . . 20 |
A.2 Changes in draft-ietf-iasa-bcp-02.txt . . . . . . . . . . 21 | | A.2 Changes in draft-ietf-iasa-bcp-01.txt . . . . . . . . . . 21 |
A.3 Changes in draft-ietf-iasa-bcp-01.txt . . . . . . . . . . 21 | | A.3 Changes in draft-ietf-iasa-bcp-00.txt . . . . . . . . . . 22 |
A.4 Changes in draft-ietf-iasa-bcp-00.txt . . . . . . . . . . 22 | | A.4 Changes in draft-wasserman-iasa-bcp-01.txt . . . . . . . . 22 |
A.5 Changes in draft-wasserman-iasa-bcp-01.txt . . . . . . . . 23 | | A.5 |
A.6 Origin of draft-wasserman-iasa-bcp-00.txt . . . . . . . . 23 | | Origin of draft-wasserman-iasa-bcp-00.txt . . . . . . . . 23 |
Intellectual Property and Copyright Statements . . . . . . . . 24 | | Intellectual Property and Copyright Statements . . . . . . . . 24 |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 2] | | Austein & Wijnen Expires June 7, 2005 [Page 2] |
| | |
Internet-Draft Structure of IASA December 2004 | | Internet-Draft Structure of IASA December 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 the membership and selection rules for the IAOC. |
| | |
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. As of the |
time at which this document was written, this included the work of | | time at which this document was written, this included the work of |
IETF working groups, the IESG, the IAB, and the IRTF. Should the | | IETF working groups, the IESG, the IAB, and the IRTF. Should the |
IETF standards process at some future date come to include other | | IETF standards process at some future date come to include other |
technical activities, the IASA shall provide administrative support | | technical activities, the IASA shall provide administrative support |
for those activities as well. Such support includes, as appropriate, | | for those activities as well. Such support includes, as appropriate, |
undertaking or contracting for the work described in | | undertaking or contracting for the work described in |
[RFC3716],including IETF document and data management, IETF meetings, | | [RFC3716],including 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, and so forth. |
| | |
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. The IETF does not expect the IASA to |
undertake the bulk of this work directly; rather, the IETF expects | | undertake the bulk of this work directly; rather, the IETF expects |
the IASA to contract this work from others, and manage these | | the IASA to contract this work from others, and manage these |
contractual relationships to achieve efficiency, transparency and | | contractual relationships to achieve efficiency, transparency and |
cost effectiveness. | | cost effectiveness. |
| | |
The IASA is distinct from IETF-related technical functions, such as | | The IASA is distinct from 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. Note, however, that this in no way prevents people who form |
part of the IASA from participating as individuals in IETF technical | | part of the IASA from participating as individuals in IETF technical |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 3] | | Austein & Wijnen Expires June 7, 2005 [Page 3] |
| | |
Internet-Draft Structure of IASA December 2004 | | Internet-Draft Structure of IASA December 2004 |
| | |
| | |
activities. | | activities. |
| | |
1.1 Editors' Notes | | 1.1 Editors' Notes |
| | |
Note to RFC Editor: Please remove this section prior to | | Note to RFC Editor: Please remove this section prior to |
publication. | | publication. |
| | |
This document is still a work in progress, primarily due to time | | This document is still a work in progress, primarily due to time |
pressure and lack of a clear consensus on some issues. | | pressure and lack of a clear consensus on some issues. |
| | |
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. |
| | |
1.2 Open Issues | | 1.2 Closed Issues |
| | |
Note to RFC Editor: Please remove this section prior to | | Note to RFC Editor: Please remove this section prior to |
publication. | | publication. |
| | |
| | Summary |
| | |
Discussion of open issues has progressed quickly enough in recent | | of issues |
weeks that a summary of the current state of each open issue in this | | that |
document would be obsolete by the time anybody but the editors | | the editors believe have been resolved and |
had a | | been agreed to. Please do check |
chance to see it. A kind volunteer is now keeping reasonably | | to make sure that |
up-to-date status of each known open issue is available in an online | | |
tracking system: | | |
| | |
URL: https://rt.psg.com | | |
| | |
Username: ietf | | |
| | |
Password: ietf | | |
| | |
Queue: iasa-bcp | | |
| | |
The "status" of each tracked issue is stored in a "custom field" | | |
named "Discussion". That status is also mapped onto the | | the editors are |
system's | | correct |
priority field, so you can see it in the list of | | in their assessment of these issues. |
| | |
tickets and so you | | o Do we need "pre-nuptial" agreement text |
can sort on it. The mapping is as follows: | | as part |
| | |
1. No dicussion | | |
| | |
2. No consensus | | |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 4] | | |
| | |
Internet-Draft Structure of | | of the BCP? |
| | Currently, the document does have some explicit text for it, which |
IASA December 2004 | | appears to |
| | |
| | |
3. Text Needed | | |
| | |
4. Text Proposed | | |
| | |
5. Text Accepted | | |
| | |
6. No change proposed | | |
| | |
7. No change needed | | |
| | |
8. Document Updated | | |
| | |
Please be sure to | | be enough to guide us all if a separation turns out |
check the | | necessary in the future. Also, it seems IETF consensus on |
| | choosing Scenario O means that we (the IETF) trust ISOC. |
| | |
| | o Do we need separate bank accounts? Consensus seems to be not to |
| | ask for that. So this document does not claim so now. Instead we |
| | specify "Divisional Accounting" (Section 5.1). |
| | |
issue tracker for | | o Do we need to be more specific as to how reserves are built for |
| | emergency situations, or can we leave that at ISOC's discretion? |
| | It seems we are OK with current text. |
| | |
the latest status of | | o We have added a set of |
all tracked issues. | | |
| | |
2. Definitions and Principles | | |
| | |
This section describes terminology and underlying principles used in | | principles (Section 2.2). Some |
the rest of | | of them |
this document. | | have been edited a little bit. The remainder |
| | |
2.1 Alphabet Soup | | |
| | |
Although most of the terms, abbreviations, and acronyms used in this | | of the |
document | | document |
are reasonably well-known, first-time readers may find this | | still contains |
alphabet soup confusing. This section therefore attempts to provide | | |
a | | a fair amount of detail (based on the principles) |
quick summary. | | but potentially some |
| | |
IAB: Internet Architecture Board (see [RFC2026], [RFC2850]). | | |
| | |
IAD: Internet Administrative Director, defined by this document. | | |
| | |
IAOC: Internet Administrative Oversight Committee, defined by this | | |
document. | | |
| | |
IASA: IETF Administrative Support Activity, defined by this document. | | |
| | |
IESG: Internet Engineering Steering Group (see [RFC2026], [RFC3710]). | | |
| | |
IETF: Internet Engineering Task Force (see [RFC3233]). | | |
| | |
ISOC: Internet Society (see [RFC2031] and [ISOC]). | | |
| | |
| | |
2.2 Principles of | | of those details can be removed. Some |
| | details have been removed or reworded. In any event, the editors |
the IASA, IETF and ISOC relationship | | believe the level of detail is now OK, and that |
| | |
This section attempts to describe principles underlying the | | the details |
mechanisms described in this document. | | |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 5] | | Austein & Wijnen Expires June 7, 2005 [Page 4] |
| | |
Internet-Draft Structure of IASA December 2004 | | Internet-Draft Structure of IASA December 2004 |
| | |
| | |
| | themselves are |
| | |
| | |
1. The IETF intends to establish a structure (the IASA) in order to | | in sync with the |
get IETF administrative functions managed appropriately, | | |
according to good administrative, fiscal, and management | | |
principles. | | principles. Section 5.6 may be |
The IASA includes the IAD and | | longer and more detailed than strictly necessary, but since we |
the | | believe it to be in sync with the principle we have defined, we |
| | think it's harmless. |
| | |
| | o 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. Revision (02) added a variance |
IAOC, and shall be | | clause (see Section 3), and startup variances can be handled by |
| | that. |
| | |
| | o Do we need wording about the ownership of IETF tools |
housed within ISOC. | | |
| | |
2. The IAD and | | and data? We |
| | have some text (in Section 2.2) about IPR, which has been checked |
| | by Jorge Contreras. We believe that this text covers copyright. |
IAOC shall not have | | We also have text about software tools under IAD responsibilities. |
any authority over the | | So the editors consider this issue closed. |
| | |
IETF | | o Do we need to add text to protect IETF from |
standards development activities. This document does not modify | | |
ISOC's other roles related to the | | the hypothetical case |
IETF standard process. | | of an IAD or an IAOC going amok? |
| | |
3. The IAD | | The IAD can be suspended or |
and IAOC, in cooperation with the ISOC President/CEO and | | fired, and the IAOC can be recalled, and so maybe that is |
| | sufficient. This issue has not been discussed much yet; does that |
| | mean that this is not |
staff, shall develop an annual budget for the | | an issue and that the document is OK with |
IASA. The | | respect to this topic? The editors believe it is not an issue |
budget | | anymore unless someone asks us |
must clearly identify all expected direct and indirect | | |
expenditures related to | | to open it again. If you think we |
| | should reopen it, please send text. |
| | |
the IASA. ISOC, through its normal | | o We believe that the current text on |
procedures, shall evaluate and adopt the | | the IETF Executive Director |
| | has consensus. |
| | |
IASA budget as part of | | o With regard |
ISOC's own budget process and commit to ensuring funds to support | | to voting by |
the | | the IAOC, we believe we have rough |
approved budget. | | consensus that |
| | |
4. Responsibility for the | | the current text is OK. We do not have unanimity |
| | though. |
| | |
evaluation, review and negotiation of | | o We believe there is consensus that |
contracts and other IETF administrative and support agreements | | |
and other expenditures of funds under the IASA shall rest with | | the IAB chair should |
the IAD, operating in accordance with policies and procedures set | | |
by the IAOC and consistent with ISOC operating policies. | | |
| | |
5. Once funds or in-kind donations have been credited to the IETF | | |
accounts, they shall be irrevocably allocated to the support of | | |
the IETF. | | |
| | |
6. There shall be a | | be a |
detailed public accounting to separately | | voting member |
identify all funds available to and all expenditures relating to | | |
the IETF and to the IASA, including any donations, of funds or | | |
in-kind, received by ISOC for IETF-related activities. In-kind | | |
donations shall only be accepted at the direction of the IAD and | | of the |
IAOC. | | IAOC. |
| | |
7. The | | The text does say so. |
| | |
| | |
| | 1.3 Open Issues |
| | |
IETF, through the IASA, shall have a perpetual right to | | Note to RFC Editor: Please remove this section prior to |
| | publication. |
| | |
use, | | Summary |
display, distribute, reproduce, modify and create derivatives of | | of open issues |
all data created in support of IETF activities. | | |
| | |
8. The IASA shall establish a target for a reserve fund to | | for which we need to find specific IETF |
cover | | consensus so that editors can put |
normal operating expenses and meeting expenses in accordance with | | in correct |
prudent planning, and | | and agreed-upon text. |
| | |
| | o Are designated donations specified appropriately? In particular, |
| | does requiring that donations not be "unduly restricted" address |
ISOC shall work with the IASA to build up | | previously stated concerns? This is what the current text says. |
and maintain the reserve. | | |
| | |
The remainder of this document contains details based on the above | | |
principles. | | |
| | |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 6] | | Austein & Wijnen Expires June 7, 2005 [Page 5] |
| | |
Internet-Draft Structure of IASA December 2004 | | Internet-Draft Structure of IASA December 2004 |
| | |
| | |
| | It is not yet clear whether the current text |
| | |
| | |
2.3 Community Consensus and Grant of Authority | | |
| | |
The IETF is | | is acceptable to |
| | ISOC. We may need to check this with ISOC's accountants first. |
| | |
| | o It's not yet clear whether we have too much about the IAD task. |
| | Should that task be specified elsewhere, initially by the |
| | Transition Team, later by IAOC or some committee? We need people |
| | to speak up on this. Is the current text OK? |
| | |
a consensus-based group, and authority to act on behalf | | o Would we want the IAOC to sign off on |
of the | | the yearly (or more |
community requires a high degree of consensus and the | | frequent) reports in some formal sense within a reasonable amount of time? This might protect the IAD from some form |
continued consent of | | of open-ended |
| | lingering responsibility for previous years. It might also |
| | protect against having somebody, five years from now, state "this |
the | | is wrong and oh by the way this was already wrong N years ago." |
| | |
community. After a careful process of | | o How should we deal with conflicts between |
deliberation, a broad-based community consensus emerged to house the | | the IAD, |
IETF Administrative Support Activity (IASA) within the | | the IAOC and |
Internet | | ISOC? |
Society. This document reflects that | | This is complicated by the fact that ISOC officially |
consensus. | | employs the IAD while |
| | |
2.4 Termination and Change | | |
| | |
Any change to this agreement shall require a similar level of | | a small committee hires |
community consensus and deliberation and | | and fires and |
shall be reflected by a | | evaluates |
subsequent Best Current Practice (BCP) document. | | |
| | |
2.5 Effective Date for Commencement of IASA | | |
| | |
The procedures in this document shall become operational immediately | | |
after this document has been approved by the process defined in BCP 9 | | the IAD. No new discussion or text |
[RFC2026] and has | | has come up since |
| | draft version 01. |
| | |
been affirmed by a resolution of the ISOC Board of | | o How should we deal with disagreements between the ISOC Board of |
| | Trustees |
Trustees. | | |
| | |
3. Structure of the IASA | | |
| | |
The IASA structure is designed to ensure accountability and | | and |
transparency of the | | the IAOC regarding business decisions, spending, |
| | hiring, etc? |
| | |
IETF administrative and | | o When do we do a check with accountants and legal advisors? Can |
fiscal activities to the | | that be done during |
IETF | | IETF Last Call, or must that happen first? |
| | |
community. The IETF Administrative Oversight Committee (IAOC) | | o The text on an appeal against |
directs and oversees the IASA. The IAOC | | the IAOC (Section 3.4 is pretty |
consists of volunteers, all | | fresh, |
chosen directly or indirectly by the IETF community, as well as | | |
appropriate ex officio members from ISOC and IETF leadership. The | | and some seem |
IAOC shall be accountable to the IETF community for the | | |
effectiveness, efficiency and transparency of the IASA. | | |
| | |
The IASA consists initially of a single full-time ISOC employee, the | | |
IETF Administrative Director (IAD), who is entitled to act on behalf | | to want |
of the IASA at the direction of the IAOC. The IAD is likely to | | to narrow down what can be appealed. |
| | Not clear that we have consensus yet. |
| | |
| | |
draw | | 2. Definitions |
on financial, legal and | | and Principles |
| | |
administrative support furnished by ISOC | | This section describes terminology |
support staff or consultants. Costs for ISOC support staff and | | and underlying principles used in |
consultants are allocated based on actual expenses or on some other | | |
allocation model determined by consultation between the | | the rest of this document. |
| | |
IAOC and | | 2.1 Alphabet Soup |
ISOC. | | |
| | |
Although the IAD is an ISOC employee, he or she works under the | | Although most |
direction of the IAOC. The IAD is selected and hired by a committee | | of the terms, abbreviations, and acronyms used in |
of the IAOC. The members of this | | this |
committee are | | document are reasonably well-known, first-time readers may find this |
appointed by the | | alphabet soup confusing. |
IAOC, and consist at minimum of the ISOC President and the IETF | | |
Chair. This | | This section therefore attempts to provide |
| | a quick summary. |
| | |
same committee is responsible for setting the IAD's | | IAB: Internet Architecture Board (see [RFC2026], [RFC2850]). |
initial compensation, reviewing the performance of the IAD | | |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 7] | | Austein & Wijnen Expires June 7, 2005 [Page 6] |
| | |
Internet-Draft Structure of IASA December 2004 | | Internet-Draft Structure of IASA December 2004 |
| | |
| | |
| | IAD: Internet Administrative Director, defined by this document. |
| | |
| | IAOC: Internet Administrative Oversight Committee, defined by this |
| | document. |
| | |
| | IASA: IETF Administrative Support Activity, defined by this document. |
| | |
| | IESG: Internet Engineering Steering Group (see [RFC2026], [RFC3710]). |
| | |
| | ISOC: Internet Society (see [RFC2031] |
| | |
| | |
periodically, and | | and [ISOC]). |
| | |
| | |
determining any changes to the IAD's employment and | | 2.2 Principles of the IASA, |
compensation. | | |
| | |
In principle, IETF administrative functions should be outsourced. | | IETF |
The IAD is responsible for negotiating and | | and ISOC relationship |
| | |
maintaining such | | This section attempts |
contracts, as well as providing any coordination necessary to make | | to describe principles underlying |
sure the | | the |
| | mechanisms described in this document. |
| | |
| | 1. The IETF intends to establish a structure (the IASA) in order to |
IETF administrative support functions | | get IETF administrative functions managed appropriately, |
| | according to good administrative, fiscal, and management |
are covered properly. | | principles. |
The IAOC is accountable for the structure of the IASA and thus | | The IASA includes the IAD and the IAOC, and shall |
decides which functions are to be | | be |
| | housed within ISOC. |
| | |
outsourced. All outsourcing must | | 2. The IAD, IAOC |
be via well-defined contracts or equivalent instruments. Both | | |
outsourced and | | and ISOC shall not have any authority over the IETF |
| | standards development activities. |
| | |
in-house functions must be clearly specified and | | 3. The IAD and IAOC, |
documented with well-defined deliverables, service level agreements, | | with advice from the ISOC President/CEO |
and | | and |
transparent accounting for the | | staff, shall develop an annual budget for the IASA. The budget |
| | must clearly identify all expected direct and indirect |
| | expenditures related to the IASA. ISOC, through its normal |
cost of such functions. | | procedures, shall evaluate and adopt |
| | |
If the IASA | | the IASA budget as part of |
cannot comply with the | | ISOC's own budget process and commit to ensuring funds to support the approved budget. |
| | |
procedures described in this | | 4. Responsibility |
document for legal, accounting or practical reasons, the | | for the evaluation, review and negotiation of |
| | contracts and other IETF administrative and support agreements |
IAOC shall | | and other expenditures of funds under the IASA shall rest with |
report that fact to the community, along with | | the IAD, operating in accordance with policies and procedures set |
the variant procedure | | by |
the IAOC | | the IAOC and consistent with ISOC operating policies. |
| | |
| | 5. There shall be a detailed public accounting to separately |
intends to follow. If the problem is a long-term one, the | | identify all funds available to and all expenditures relating to the IETF and to the IASA, including any donations, of funds or |
| | in-kind, received by ISOC for IETF-related activities. In-kind |
| | donations |
IAOC shall ask the IETF to update this document to reflect the | | shall only be accepted at the direction of the |
changed procedure. | | |
| | |
3.1 IAD | | IAD and |
| | IAOC. |
| | |
Responsibilities | | 6. |
| | |
The IAD is responsible for working with the IAOC and others to | | The IETF, through the IASA, shall have a perpetual right to use, |
| | |
| | |
| | |
| | Austein & Wijnen Expires June 7, 2005 [Page 7] |
| | |
| | Internet-Draft Structure |
understand the administrative requirements of | | of IASA December 2004 |
| | |
| | |
the IETF, and | | display, distribute, reproduce, modify and create derivatives of |
| | all data created in support of IETF activities. |
| | |
for | | 7. The IASA shall establish a target for a reserve fund to cover |
| | normal operating expenses and meeting expenses in accordance with |
| | prudent planning, and ISOC shall work with |
managing the IASA to | | the IASA to build up |
meet those needs. This includes determining the | | and maintain the reserve. |
| | |
| | The remainder |
structure of the | | of this document contains details based on the above |
| | principles. |
| | |
IASA effort, establishing an operating budget, | | 2.3 Community Consensus |
negotiating contracts with service providers, managing the business | | |
relationship with those providers, and establishing mechanisms to | | and Grant of Authority |
track their performance. The IAD may also manage other contractors | | The IETF is a consensus-based group, |
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 | | and authority to act on behalf |
transparent | | of the |
manner, and for producing regular monthly, quarterly, and annual | | |
financial and operational updates for IAOC and IETF community review. | | community requires a high degree of consensus |
| | |
The IAD is responsible for administering the IETF finances, managing | | |
separate financial accounts for the IASA, and establishing and | | and |
administering the | | the |
IASA budget. While ISOC will need to put some | | continued consent of |
financial controls in place to protect ISOC's fiscal stability, the | | the community. After a careful process |
IAD (with IAOC approval, as appropriate) should have signing | | |
authority consistent with carrying out IASA work effectively, | | |
efficiently and independently. If there are any problems regarding | | |
the level of | | of |
financial approval granted to the | | deliberation, a broad-based community consensus emerged to house the |
IAD, the | | IETF Administrative Support Activity (IASA) within the Internet |
| | Society. This document reflects that consensus. |
| | |
IAOC and | | 2.4 Termination and Change |
| | |
ISOC | | Any change to this agreement |
shall work out a | | shall require a similar level of |
policy that is mutually agreeable, and shall do so | | community consensus and deliberation and shall be reflected by |
within a | | a |
| | subsequent Best Current Practice (BCP) document. |
| | |
reasonable timeframe. | | 2.5 Effective Date for Commencement |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 8] | | |
| | |
Internet-Draft Structure of IASA December 2004 | | of IASA |
| | |
| | |
The | | The procedures in this document shall become operational immediately |
IAD negotiates service contracts, with input, as appropriate, | | after this document has been approved |
from other bodies, and with review, as appropriate, by the | | by the process defined in BCP 9 |
IAOC. The | | [RFC2026] and has been affirmed by a Resolution |
IAOC should establish guidelines for what level of review is expected | | of agreement by the |
based on contract type, size, cost, or duration. ISOC | | ISOC Board of Trustees. |
| | |
executes | | 3. Structure |
contracts on behalf of the | | of the IASA |
| | |
IASA, after whatever review ISOC requires | | The IASA structure is designed |
to ensure | | to ensure accountability and |
that the | | transparency of the IETF administrative and fiscal activities to the |
| | IETF community. The IETF Administrative Oversight Committee (IAOC) |
contracts meet ISOC's legal and financial | | directs and oversees the IASA. |
requirements. | | |
| | |
The IAD is responsible for ensuring that all | | The IAOC consists of volunteers, all |
contracts give IASA and | | chosen directly or indirectly by |
the IETF | | the IETF community, as well as |
the perpetual right to use, display, distribute, reproduce, | | appropriate ex officio members from ISOC |
modify and create derivatives of all data created in support of IETF | | and IETF leadership. The |
| | IAOC shall be accountable |
activities. This is necessary to make sure the IETF has access to | | to the IETF community for |
the | | the |
data it needs at all times, and to ensure that the | | effectiveness, efficiency and transparency of the IASA. |
| | |
IASA can | | The IASA consists initially of a single full-time ISOC employee, the |
change contractors as needed without disrupting IETF work. | | IETF Administrative Director (IAD), |
| | |
Whenever reasonable, if software is developed under an | | an officer entitled to act on |
IASA contract | | behalf of the IASA at |
it should should remain usable by the IETF beyond the terms of the | | the direction of the IAOC. |
contract. Some ways of achieving this are by IASA ownership or an | | |
open source license; an open source license is preferable. The IAD | | The IAD is likely |
shall decide how best to serve the IETF's interests when making such | | to draw on financial, legal |
contracts. | | |
| | |
The IAD and | | and administrative support furnished by |
| | |
| | |
| | |
| | Austein & Wijnen Expires June 7, 2005 [Page 8] |
| | |
| | Internet-Draft Structure of IASA December 2004 |
| | |
| | |
| | ISOC support staff or consultants. Costs for ISOC support staff and |
IAOC are | | consultants are allocated based on actual expenses or on some other |
responsible for making all business decisions | | allocation model determined by consultation between |
regarding the | | the IAOC and |
| | ISOC. |
| | |
IASA. In particular, the ISOC Board of Trustees shall | | Although the IAD is an ISOC employee, he |
not have direct influence over the choice of IASA contractors or IETF | | or she works under |
meeting sponsors. This restriction is meant to enforce the | | the |
| | direction |
separation between fund raising and the actual operation of the | | of the IAOC. |
standards process. | | |
| | |
The IAD prepares an annual budget, which is subject to review and | | The IAD is selected and hired |
approval by | | by a committee |
the IAOC. The | | of the IAOC. The members of this committee are appointed by the |
| | IAOC, and consist at minimum of the ISOC President and the IETF |
IAD is responsible for | | Chair. This same committee is responsible for setting the IAD's |
| | initial compensation, reviewing the performance of the IAD |
presenting this | | periodically, and determining any changes |
budget to the | | to the IAD's employment and |
| | compensation. |
| | |
ISOC Board of Trustees, as part of ISOC's annual | | In principle, IETF administrative functions should be outsourced. |
financial planning process. The IAOC is responsible for | | The IAD is responsible for negotiating and maintaining such |
| | contracts, as well as providing any coordination necessary to make |
ensuring the | | sure |
budget's suitability for meeting the IETF community's administrative | | the IETF administrative support functions are covered properly. |
| | The |
needs, but the IAOC does not bear fiduciary responsibility for ISOC. | | IAOC is accountable for the structure |
The ISOC Board of Trustees therefore needs to review and understand | | of |
the budget and | | the IASA and thus |
planned activity in enough detail to | | decides which functions are to be outsourced. All outsourcing must |
| | be via well-defined contracts or equivalent instruments. If any |
| | functions are performed in-house, they must be clearly specified and |
| | documented with well-defined deliverables, service level agreements, |
| | and transparent accounting for the cost of such functions. |
| | |
carry out their | | If the |
fiduciary responsibility properly. The IASA | | IASA cannot comply with the procedures described in this |
| | document for legal, accounting or practical reasons, the IAOC shall |
| | report that fact to the community, along with the variant procedure |
publishes its complete | | the IAOC intends |
budget to | | to follow. If the problem is a long-term one, the |
the IETF | | IAOC shall ask the IETF to update this document to reflect the |
| | changed procedure. |
| | |
community each year. | | 3.1 IAD |
| | |
3.2 IAOC Responsibilities | | Responsibilities |
| | |
The IAOC's role is to | | The IAD is responsible for working with the IAOC and others to |
provide appropriate direction to the IAD, to | | understand the administrative requirements of |
review the IAD's regular reports, and | | the IETF, and for |
to oversee the IASA functions | | managing the IASA |
to ensure that the | | to meet those needs. This includes determining the |
administrative needs of the | | structure of the IASA effort, establishing an operating budget, |
| | 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 |
IETF community are | | contractors or employees are engaged in IASA-related work. |
being properly met. The IAOC's mission is not to be be engaged in | | The IAD is responsible for running IASA in an open and transparent |
| | manner, and for producing regular monthly, quarterly, and annual |
| | financial and operational updates for IAOC |
the day-to-day administrative work of IASA, but rather to provide | | |
appropriate direction, oversight and approval. | | and IETF community review. |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 9] | | Austein & Wijnen Expires June 7, 2005 [Page 9] |
| | |
Internet-Draft Structure of IASA December 2004 | | Internet-Draft Structure of IASA December 2004 |
| | |
| | |
| | The IAD is responsible for administering |
| | |
| | |
Therefore, the | | the IETF finances, managing |
IAOC's responsibilities are: | | a separate financial account for |
| | |
o To select the IAD and provide high-level review and | | the IASA, and establishing and |
| | administering the IASA budget. While ISOC will need to put some |
direction for | | financial controls |
his or her work. This task should be handled by a sub-committee, | | |
as described in Section 3. | | in place to protect ISOC's fiscal stability, |
| | |
o To review the | | the |
| | IAD (with IAOC approval, as appropriate) should have signing |
| | authority consistent with carrying out IASA work effectively, |
IAD's plans and contracts to ensure that they will | | efficiently and independently. If there are any problems regarding |
meet the administrative needs of the IETF. | | the level of financial approval granted to the IAD, |
| | |
o To track whether the IASA functions are meeting the IETF | | the IAOC |
community's administrative needs, and | | and ISOC |
to work | | shall work out a policy that is mutually agreeable, and shall do so |
| | within a reasonable timeframe. |
| | |
| | The IAD negotiates service contracts, with input, as appropriate, |
with the | | from other bodies, and with review, as appropriate, by the IAOC. The |
IAD to | | IAOC should establish guidelines |
determine a plan for corrective action if they are not. | | for what level of |
| | |
o To review | | review is expected |
| | based on contract type, size, cost, or duration. ISOC executes |
the IAD's budget proposals to ensure that they will meet | | contracts on behalf of the IASA, after whatever review ISOC requires to ensure that the contracts meet ISOC's legal |
the IETF's needs, and review the IAD's regular financial | | and financial |
| | requirements. |
| | |
reports. | | The IAD is responsible for ensuring |
| | |
o To ensure that the IASA | | that all contracts give the IASA |
is run in a transparent and accountable | | and the IETF all rights in data needed to satisfy |
manner. While the | | the principle of |
day-to-day work should be delegated to the IAD | | data access. This is necessary to make sure the IETF has access to |
and others, the IAOC is responsible for ensuring that IASA | | the data it needs at all times, |
finances and operational status are tracked appropriately, and | | and to ensure |
that monthly, quarterly, and annual financial and operational | | that |
reports are published to the | | the IASA can |
IETF | | change contractors as needed without disrupting IETF work. |
| | |
| | Whenever reasonable, if software is developed under an IASA contract |
community. | | it should should remain usable by |
| | |
o To designate, in consultation with the IAB and the IESG, the | | the IETF beyond the terms of the |
| | contract. Some ways of achieving this are by IASA ownership |
person or | | or an |
| | open source license; an open source license is preferrable. The IAD |
people who carry out the | | shall decide how best to serve the IETF's interests when making such |
| | contracts. |
| | |
tasks which other IETF process | | The IAD and IAOC |
documents say are | | are responsible for making all business decisions |
| | regarding the IASA. In particular, the ISOC Board of Trustees shall |
carried out by the IETF | | not have direct influence over the choice of IASA contractors or IETF |
Executive Director. | | meeting sponsors. This restriction |
| | |
The IAOC's role is to | | is meant to enforce the |
direct and review, not perform, the work of the | | separation between fund raising and the actual operation of the |
| | standards process. |
| | |
| | The |
IAD and IASA. The IAOC holds periodic teleconferences and | | IAD prepares an annual budget, which is subject |
face-to-face meetings as needed to carry out the IAOC's duties | | to review |
efficiently and | | and |
effectively. | | approval by |
| | |
If there is no IAD or the IAD is | | the IAOC. The IAD is responsible for presenting this |
unavailable, the IAOC may | | budget to the ISOC Board |
temporarily assign the IAD's duties to individual members of the | | of Trustees, as part |
IAOC. | | |
| | |
3.3 Relationship of | | of ISOC's annual |
the IAOC to Existing IETF Leadership | | financial planning process. |
| | |
The IAOC is directly accountable to the IETF community for the | | The IAOC is responsible for ensuring the |
| | budget's suitability for meeting |
performance of the | | the IETF community's administrative |
IASA. However, the | | needs, but the IAOC does not bear fiduciary responsibility for ISOC. |
nature of the IAOC's work | | The ISOC Board of Trustees therefore needs to review |
involves treating the IESG and IAB as major internal customers of the | | and understand the budget |
administrative support services. The IAOC and the IAD should not | | and planned activity in enough detail to carry out |
consider their | | their |
work successful unless the IESG and IAB are also | | fiduciary responsibility properly. |
satisfied with the administrative support that the IETF is receiving. | | |
| | |
3.4 IAOC Decision Making | | |
| | |
The IAOC attempts to reach all decisions unanimously. If unanimity | | The IASA publishes its complete |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 10] | | Austein & Wijnen Expires June 7, 2005 [Page 10] |
| | |
Internet-Draft Structure of IASA December 2004 | | Internet-Draft Structure of IASA December 2004 |
| | |
| | |
| | budget to |
| | |
| | |
cannot be achieved, the | | the IETF community each year. |
| | |
IAOC | | 3.2 IAOC Responsibilities |
| | |
chair may conduct informal polls to | | The IAOC's role is to provide appropriate direction to |
determine the | | the IAD, to |
consensus of the group. In cases where it is | | review the IAD's regular reports, and to oversee |
necessary, some decisions may be made by voting. For the purpose of | | the IASA functions |
judging consensus or voting, only the "voting members" (as defined in | | |
Section 4) shall be counted. If voting results in a tie, then IAOC | | |
chair decides how to proceed with the decision process. | | to ensure that the administrative needs |
| | |
IAOC decisions are taken by a majority of the non-conflicted IAOC | | of the IETF community |
members who are | | are |
available to vote, whether in | | being properly met. The IAOC's mission is not to be be engaged in |
person or via other | | the day-to-day administrative work of IASA, but rather |
reasonable means determined to | | to provide |
| | appropriate direction, oversight and approval. |
| | |
be suitable by the | | Therefore, the IAOC's responsibilities are: |
| | |
members of the | | o To select the IAD and provide high-level review and direction for |
| | his or her work. This task should |
IAOC. The IAOC decides further details about its decision-making | | |
rules. These rules will be | | be handled by a sub-committee, |
| | as described in Section 3. |
| | |
made public. | | o To review the IAD's plans |
| | |
The IAOC shall establish and publish rules to | | and contracts to ensure that they will |
handle conflict of | | meet the administrative needs of the IETF. |
| | |
| | o To track whether the IASA functions are meeting the IETF |
| | community's administrative needs, |
interest situations. | | |
| | |
All IAOC decisions shall be minuted, and | | and to work with the IAD to |
| | determine a plan for corrective action if they are not. |
| | |
IAOC minutes shall be | | o To review the IAD's budget proposals to ensure |
published regularly. | | |
| | |
If someone believes that | | that they will meet |
the | | the IETF's needs, and review the IAD's regular financial reports. |
| | |
IAOC has violated the IAOC rules and | | o To ensure that the IASA is run in a transparent and accountable |
| | manner. While |
procedures, he or she can ask the IETF leadership to investigate the | | the day-to-day work should be delegated to the IAD |
| | and others, |
matter, using the same procedure as is used for | | the IAOC is responsible for ensuring that IASA |
| | finances and operational status are tracked appropriately, and |
| | that monthly, quarterly, and annual financial and operational |
| | reports are published to the IETF community. |
| | |
appeals of procedural | | o To designate, |
issues in the IETF, starting with the IESG. | | in consultation with the IAB and |
| | |
If the IESG, | | the IESG, the |
IAB or the | | person or people who carry out the tasks which other IETF process |
ISOC Board of Trustees find that procedures | | documents say are carried out by |
have been violated, they may advise the | | the IETF Executive Director. |
| | |
IAOC, but do not have | | The IAOC's role is to direct and review, not perform, the work |
authority to overturn or change a decision of the | | of the |
IAOC. | | IAD and IASA. |
| | |
The IAOC | | The IAOC holds periodic teleconferences and |
| | face-to-face meetings as needed to carry out the IAOC's duties |
| | efficiently and effectively. |
| | |
plays no role in appeals of WG Chair, IESG, or IAB | | 3.3 Relationship of the |
decisions. | | |
| | |
4. IAOC Membership, Selection and Accountability | | IAOC to Existing IETF Leadership |
| | |
The IAOC shall consist of eight voting members who shall be selected | | The IAOC is directly accountable to |
as follows: | | |
| | |
o 2 members appointed by the IETF Nominations Committee (NomCom); | | the IETF community for |
| | |
o 1 member appointed by the | | the |
IESG; | | performance of |
| | |
o 1 member appointed by the IAB; | | the IASA. However, |
| | |
o 1 member appointed by the ISOC Board of | | the nature of the IAOC's work |
Trustees; | | involves treating the IESG and |
| | |
o The IETF Chair (ex officio); | | |
| | |
o The IAB Chair (ex officio); | | IAB as major internal customers of the |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 11] | | Austein & Wijnen Expires June 7, 2005 [Page 11] |
| | |
Internet-Draft Structure of IASA December 2004 | | Internet-Draft Structure of IASA December 2004 |
| | |
| | |
| | administrative support services. |
| | |
| | |
o The | | The IAOC and the IAD should not |
ISOC President/CEO (ex officio). | | consider their work successful unless the IESG and IAB are |
| | |
The IETF Administrative Director also | | also |
serves, ex officio, as a | | satisfied with the administrative support that |
non-voting member of the | | the IETF is receiving. |
| | |
IAOC. | | 3.4 IAOC Decision Making |
| | |
The IAOC may also choose to | | The IAOC attempts to reach all decisions unanimously. If unanimity |
invite liaisons from other groups, but is | | cannot be achieved, |
not required to do so; the IAOC decides whether or not to | | the IAOC chair may conduct informal polls to |
have a | | determine |
liaison to any particular group. Any such liaisons are non-voting. | | |
Responsibility for selecting the individual filling a particular | | the consensus of |
liaison role lies with the | | the group. In cases where it is |
body from which the | | necessary, some decisions may be made by voting. For the purpose of |
IAOC has requested the | | judging consensus or voting, only the "voting members" (as defined in |
| | Section 4) shall be counted. If voting results in |
liaison. | | |
| | |
Appointed members of the IAOC serve two year terms. IAOC terms | | |
normally end at the first IETF meeting of a year, just as as IAB and | | a tie, then |
IESG terms do. | | |
| | |
The members of the IAOC | | IAOC |
shall select one of its appointed voting | | chair decides how |
members to serve as the chair of the IAOC, with all of the | | to proceed with the decision process. |
| | |
duties and | | If someone believes that |
responsibilities normally associated with such a position. The term | | |
of the IAOC chair shall be one year, with no restriction on renewal. | | the IAOC has violated |
The chair of the IAOC | | the IAOC rules and |
may be removed at any time by the affirmative | | procedures, he or she can ask the IETF leadership to investigate |
vote of two-thirds of the | | the |
voting members of the IAOC, or as a result | | matter, using the same procedure as is used for appeals |
of | | of procedural |
| | issues in the IETF, starting with the IESG. |
| | |
his or her departure from the IAOC. | | If the IESG, IAB or the ISOC Board |
| | |
The chair of | | of Trustees find that procedures |
the IAOC shall have the authority to manage the | | have been violated, they may advise the IAOC, but do not have authority to overturn or change a decision |
activities and meetings of the IAOC. The IAOC Chair has no | | of the IAOC. The IAOC plays no role in appeals of WG Chair, IESG, or IAB |
| | decisions. |
| | |
formal | | 4. |
duty to represent the IAOC, except as directed by IAOC consensus. | | IAOC Membership, Selection and Accountability |
| | |
The two NomCom-appointed IAOC | | The IAOC shall consist of eight voting members who shall be selected |
| | as follows: |
| | |
members are chosen using the | | o 2 members appointed by the IETF Nominations Committee (NomCom); |
| | |
procedures | | o 1 member appointed by |
described in RFC 3777 [RFC3777]. For the | | the IESG; |
| | |
initial IAOC selection, the | | o 1 member appointed by the IAB; |
| | |
| | o 1 member appointed |
IESG will provide the list of desired qualifications for these | | |
positions; in later years, the IAOC will provide this qualification | | |
list. The IESG will serve as the confirming body for IAOC | | |
appointments by the NomCom. | | by the ISOC Board |
| | |
While there are no hard rules regarding how the IAB and the IESG | | |
should select members of | | of Trustees; |
| | |
the IAOC, such appointees need not be | | o |
current IAB or IESG members (and probably should not be, if only to | | |
avoid overloading the existing leadership). The IAB and IESG should | | The |
choose people with some knowledge of contracts and financial | | |
procedures, who are familiar with the administrative support needs of | | |
the IAB, the IESG, or the IETF | | IETF Chair (ex officio); |
| | |
standards process. The IAB | | o The IAB Chair (ex officio); |
| | |
and IESG | | o |
should follow a fairly open process for these selections, perhaps | | |
with an open call for nominations or a period of public comment on | | |
the candidates. The procedure for IAB selection of ISOC | | The ISOC President/CEO (ex officio). |
| | |
| | The IETF Administrative Director also serves, ex officio, as a |
Board of | | non-voting member of |
Trustees [RFC3677] might be a good model for how this could work. | | |
After the IETF gains some experience with IAOC selection, these | | the IAOC. |
selection mechanisms should be documented more formally. | | |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 12] | | Austein & Wijnen Expires June 7, 2005 [Page 12] |
| | |
Internet-Draft Structure of IASA December 2004 | | Internet-Draft Structure of IASA December 2004 |
| | |
| | |
| | The IAOC may also |
| | |
| | |
Although the IAB, the IESG and the ISOC Board of Trustees choose | | choose to invite liaisons from other groups, but is |
some | | not required to |
members of the IAOC, those members do not directly represent the | | do so; |
bodies that chose them. All members of the IAOC | | the IAOC decides whether or not to have a |
are | | liaison to any particular group. Any such liaisons are non-voting. |
| | Responsibility for selecting the individual filling a particular |
accountable | | liaison role with |
directly to the IETF community. To receive direct feedback from the | | the body from which the IAOC has requested the |
| | liaison. |
| | |
| | Appointed members of |
community, the IAOC holds an open meeting at least once per year | | the IAOC serve two year terms. IAOC terms |
at | | normally end at the first |
an IETF meeting. This may take the form of an open IAOC plenary or a | | IETF meeting of a year, just as as IAB and |
| | IESG terms do. |
working meeting held during an IETF meeting slot. The form and | | The members of the IAOC shall select one |
contents of | | of its appointed voting |
this meeting are left to the discretion of the | | members to serve as the chair of the IAOC, with all of the duties and |
IAOC | | responsibilities normally associated with such a position. |
Chair. The | | The term |
IAOC should also consider open mailing lists or other | | of the IAOC chair shall be one year, |
means to establish open communication with | | with no restriction on renewal. |
the community. | | The chair of the |
| | |
IAOC | | IAOC may be removed at any time by the affirmative |
members are subject to recall in the | | vote of two-thirds of the voting members of the IAOC, or as a result |
event that an IAOC member | | of |
abrogates his or her duties or acts against the | | his or her departure from the IAOC. |
| | |
best interests of the | | The chair of the |
IETF community. Any appointed IAOC member, including those appointed | | IAOC shall have the authority to manage |
by the | | the |
IAB, IESG or ISOC Board of Trustees, may be recalled using the | | activities and meetings of the IAOC. The |
recall procedure defined in RFC 3777 [RFC3777]. IAOC | | IAOC Chair has no formal |
members are | | duty |
not, however, subject to recall by | | to represent the IAOC, except as directed by IAOC consensus. |
| | |
| | The two NomCom-appointed IAOC members are chosen using the procedures |
the bodies that appointed them. | | described in RFC 3777 [RFC3777]. For the initial IAOC selection, |
| | |
If a vacancy occurs among the | | the |
appointed members, this is filled by | | IESG will provide |
the appointing body for | | the list of desired qualifications for these |
that position according to its procedures. | | positions; in later years, the |
| | |
4.1 Initial IAOC | | IAOC will provide this qualification |
Selection | | list. |
| | |
The initial IAOC selection will start after this document is approved | | The IESG will serve |
as | | as the confirming body for IAOC |
a BCP by the | | appointments by the NomCom. |
| | |
IESG and accepted by the | | While there are no hard rules regarding how the IAB and the IESG |
ISOC Board of | | should select members of the IAOC, such appointees need not be |
| | current IAB or IESG members (and probably should not be, if only to |
Trustees. The | | avoid overloading the existing leadership). The IAB |
IESG, IAB, and ISOC Board of Trustees should | | and IESG should |
make their selections | | choose people with some knowledge |
within 45-days of BCP approval, and | | of contracts and financial |
the NomCom should make their | | procedures, who are familiar with the administrative support needs of the IAB, the IESG, or |
selections as quickly as possible while complying with the documented | | the IETF standards process. |
NomCom procedures. The | | The IAB and IESG |
IAOC will become active as soon as a | | should follow a fairly open process for these selections, perhaps |
majority | | with an open call for nominations |
(three or more) of the appointed members have been selected. | | or a period of public comment on the candidates. The procedure for IAB selection of |
| | |
Initially, the IESG and the ISOC Board of Trustees will make one-year | | ISOC Board of Trustees [RFC3677] might be |
appointments, the IAB will make a | | a good model for how this could work. |
two-year appointment, and the | | After the IETF gains some experience with IAOC selection, these |
| | selection mechanisms should be documented more formally. |
| | |
| | Although the IAB, the IESG |
NomCom will make one one-year appointment and | | and the ISOC Board of Trustees choose some |
| | members of the IAOC, those members do not directly represent the |
one two-year | | bodies that chose them. All members |
appointment. This will establish a pattern in which approximately | | |
half of the IAOC | | of the IAOC are accountable |
is selected each year. | | directly |
| | |
5. IASA Funding | | |
| | |
The IASA manages money from three sources: | | |
| | |
1. IETF meeting revenues; | | |
| | |
2. Designated donations to ISOC (both monetary and in-kind); | | to |
| | |
3. Other ISOC support. | | |
| | |
Note that the goal is to achieve and maintain a viable IETF support | | the IETF community. To receive direct feedback from the |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 13] | | Austein & Wijnen Expires June 7, 2005 [Page 13] |
| | |
Internet-Draft Structure of IASA December 2004 | | Internet-Draft Structure of IASA December 2004 |
| | |
| | |
| | community, the IAOC holds an open meeting at least once per year at |
| | an |
| | |
| | |
function based on available funding sources. The IETF community | | IETF meeting. This may take |
expects the IAOC | | the form of an open IAOC plenary or a |
and | | working meeting held during an IETF meeting slot. The form and |
ISOC to work together to attain that goal, and | | contents of this meeting are left to the discretion |
recognizes that doing so will require striking some sort of balance. | | of |
For example, dropping the | | the IAOC |
| | Chair. The IAOC should also consider open mailing lists or other |
meeting fees to | | means to establish open communication with the community. |
| | |
$0 and expecting ISOC to | | IAOC members are subject to recall in the event that an IAOC member |
| | abrogates his or her duties or acts against |
pick up the slack would not be viable in the | | the best interests of the |
| | IETF community. Any appointed IAOC member, including those appointed |
long term, and neither | | by |
would be raising the | | the IAB, IESG or ISOC Board of Trustees, may be recalled using the |
meeting fees to prohibitive levels in | | recall procedure defined in RFC 3777 [RFC3777]. IAOC members are |
order to | | not, however, subject to recall |
fund all non-meeting-related activities. | | |
| | |
5.1 Divisional Accounting | | |
| | |
For bookkeeping purposes, funds managed by | | by the bodies that appointed them. |
| | |
| | 4.1 Initial IAOC Selection |
| | |
| | The initial IAOC selection will start after this document is approved |
IASA should be accounted | | as |
for in a separate set of accounts which can be rolled-up periodically | | a BCP by the IESG and accepted by |
to the equivalent of | | the ISOC Board of Trustees. The |
a balance sheet and | | IESG, IAB, and ISOC Board of Trustees should make their selections |
a profit and loss statement | | within 45-days of BCP approval, and |
for IASA alone after taking into account the | | the NomCom should make their |
| | selections as quickly as possible while complying with the documented |
effect of common items | | NomCom procedures. The IAOC will become active as soon |
paid for or received by ISOC as a | | as a majority |
whole. | | (three or more) |
| | |
5.2 IETF Meeting Revenues | | |
| | |
Meeting revenues are an important source of funds for IETF functions. | | of |
The IAD, in consultation with the | | the appointed members have been selected. |
| | |
IAOC, sets the meeting fees as part | | Initially, the IESG and the ISOC Board |
of | | of Trustees will make one-year |
the budgeting process. All meeting revenues shall be credited to | | appointments, the IAB will make a two-year appointment, and |
the | | the |
appropriate IASA accounts. | | NomCom will make one one-year appointment |
| | |
5.3 Designated Donations, Monetary and | | and one two-year |
| | appointment. This will establish a pattern in which approximately |
In-Kind | | half |
| | |
Donations are an essential component of | | of the IAOC is selected each year. |
| | |
| | 5. IASA Funding |
| | |
| | The IASA manages money from three sources: |
| | |
| | 1. IETF meeting revenues; |
| | |
| | 2. Designated donations to ISOC (both monetary and in-kind); |
| | |
| | 3. Other ISOC support. |
| | |
| | Note that the goal is to achieve and maintain a viable IETF support |
| | function based on available funding sources. The IETF community |
| | expects the IAOC and ISOC to work together to attain that goal, and |
| | recognizes that doing so will require striking some sort of balance. |
| | For example, dropping the meeting fees to $0 and expecting ISOC to |
| | pick up the slack would not be viable in the long term, and neither |
| | would be raising the meeting fees to prohibitive levels in order to |
| | fund all non-meeting-related activities. |
| | |
| | |
| | |
| | Austein & Wijnen Expires June 7, 2005 [Page 14] |
| | |
| | Internet-Draft Structure of IASA December 2004 |
| | |
| | |
| | 5.1 Divisional Accounting |
| | |
| | For bookkeeping purposes, funds managed by IASA should be accounted |
| | for in a separate set of accounts which can be rolled-up periodically |
| | to the equivalent of a balance sheet and a profit and loss statement |
| | for IASA alone after taking into account the effect of common items |
| | paid for or received by ISOC as a whole. |
| | |
| | 5.2 IETF Meeting Revenues |
| | |
| | Meeting revenues are an important source of funds for IETF functions. |
| | The IAD, in consultation with the IAOC, sets the meeting fees as part |
| | of the budgeting process. All meeting revenues shall be credited to |
| | the appropriate IASA account. |
| | |
| | 5.3 Designated Donations, Monetary and In-Kind |
| | |
funding. The IASA undertakes | | Donations are an essential component of funding. The IASA undertakes |
no direct fund-raising activities. This establishes a practice of | | no direct fund-raising activities. This establishes a practice of |
separating IETF administrative and standards activities from | | separating IETF administrative and standards activities from |
fund-raising activities, and helps ensure that no undue influence may | | fund-raising activities, and helps ensure that no undue influence may |
be ascribed to those from whom funds are raised. | | be ascribed to those from whom funds are raised. |
| | |
ISOC shall create and maintain appropriate structures and programs to | | ISOC shall create and maintain appropriate structures and programs to |
coordinate donations intended to support the work of the IETF, and | | coordinate donations intended to support the work of the IETF, and |
these will include mechanisms for both in-kind and direct | | these will include mechanisms for both in-kind and direct |
contributions to the work supported by IASA. Since ISOC will be the | | 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 | | sole entity through whom donations may be made to the work of the |
IETF, ISOC shall ensure that those programs are not unduly | | IETF, ISOC shall ensure that those programs are not unduly |
restrictive. For the benefit of individuals, smaller organizations | | restrictive. For the benefit of individuals, smaller organizations |
and countries with developing economies, ISOC shall maintain programs | | and countries with developing economies, ISOC shall maintain programs |
that allow for designated donations to the IETF. | | that allow for designated donations to the IETF. |
| | |
Editors' note: Some have suggested we need explicit IETF consensus | | Editors' note: Some have suggested we need explicit IETF consensus |
on the above. So if you do not agree, please speak up ASAP. | | on the above. So if you do not agree, please speak up ASAP. |
| | |
Editors' note: Removed "either using an overhead model or other | | Editors' note: Removed "either using an overhead model or other |
unrestricted donation program." because it is too detailed and | | unrestricted donation program." because it is too detailed and |
prescriptive. Send objections ASAP if you do not agree. | | prescriptive. Send objections ASAP if you do not agree. |
| | |
| | ISOC shall create appropriate administrative structures to coordinate |
| | such donations with the IASA. In-kind resources are owned by |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 14] | | |
| | |
Internet-Draft Structure of IASA December 2004 | | |
| | |
| | |
In-kind resources are owned by the ISOC on behalf of the IETF and | | the ISOC on behalf of the IETF and |
shall be reported and accounted for in a manner that identifies them | | shall be reported and accounted for in a manner that identifies them |
as such. Designated monetary donations shall be credited to the | | as such. Designated monetary donations shall be credited to the |
appropriate IASA | | appropriate IASA account. |
| | |
| | |
| | |
| | |
| | |
| | |
| | Austein & Wijnen Expires June 7, 2005 [Page 15] |
| | |
accounts. | | Internet-Draft Structure of IASA December 2004 |
| | |
5.4 Other ISOC Support | | 5.4 Other ISOC Support |
| | |
Other ISOC support shall be based on the budget process as specified | | Other ISOC support shall be based on the budget process as specified |
in Section 6. ISOC shall periodically credit additional funds to the | | in Section 6. ISOC shall credit the appropriate |
IASA accounts | | IASA accounts at |
to cover anticipated expenditures for that period | | least quarterly. |
within the yearly budget. | | |
| | |
If ISOC pays any other IETF expenses directly, without transferring | | If ISOC pays any other IETF expenses directly, without transferring |
funds to the IASA, this shall be documented as a footnote to the IASA | | funds to the IASA, this shall be documented as a footnote to the IASA |
accounts. | | accounts. |
| | |
5.5 IASA Expenses | | 5.5 IASA Expenses |
| | |
The IASA exists to support the IETF. Therefore, only expenses | | The IASA exists to support the IETF. Therefore, only expenses |
related to supporting the IETF may be debited from the IASA accounts. | | related to supporting the IETF may be debited from the IASA account. |
| | |
5.6 Operating Reserve | | 5.6 Operating Reserve |
| | |
As an initial guideline and in normal operating circumstances, the | | As an initial guideline and in normal operating circumstances, the |
IASA should have an operating reserve for its activities sufficient | | IASA should have an operating reserve for its activities sufficient |
to cover 6-months of non-meeting operational expenses, plus twice the | | to cover 6-months of non-meeting operational expenses, plus twice the |
recent average for meeting contract guarantees. However, the IASA | | recent average for meeting contract guarantees. However, the IASA |
shall establish a target for a reserve fund to cover normal operating | | shall establish a target for a reserve fund to cover normal operating |
expenses and meeting expenses in accordance with prudent planning. | | expenses and meeting expenses in accordance with prudent planning. |
Rather than having the IASA attempt to build that reserve in its | | Rather than having the IASA attempt to build that reserve in its |
separate accounts, the IASA looks to ISOC to build and provide that | | separate accounts, the IASA looks to ISOC to build and provide that |
operational reserve, through whatever mechanisms ISOC deems | | operational reserve, through whatever mechanisms ISOC deems |
appropriate: line of credit, financial reserves, meeting cancellation | | appropriate: line of credit, financial reserves, meeting cancellation |
insurance, and so forth. Such reserves do not appear | | insurance, and so forth. Such reserves do not appear |
instantaneously; the goal is to reach this level of reserves within 3 | | 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 | | 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 | | reserve for use by IASA for use in the event of IETF meeting |
cancellation or other unexpected fiscal emergencies. These reserves | | cancellation or other unexpected fiscal emergencies. These reserves |
shall only be spent on IETF support functions. | | shall only be spent on IETF support functions. |
| | |
6. IASA Budget Process | | 6. IASA Budget Process |
| | |
While the IASA sets a budget for the IETF's administrative needs, its | | While the IASA sets a budget for the IETF's administrative needs, its |
budget process clearly needs to be closely coordinated with ISOC's. | | budget process clearly needs to be closely coordinated with ISOC's. |
The specific timeline shall be established each year by IASA and | | The specific timeline shall be established each year. A |
ISOC. As an example, a general annual timeline for budgeting is: | | general annual timeline for budgeting is: |
| | |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 15] | | |
| | |
Internet-Draft Structure of IASA December 2004 | | |
| | |
| | |
July 1: The IAD presents a budget proposal (prepared in consultation | | July 1: The IAD presents a budget proposal |
with ISOC staff) for the following fiscal year, with 3 year | | for the following fiscal year, with 3 year |
projections, to the IAOC. | | projections, to the IAOC. |
| | |
August 1: The IAOC approves the budget proposal for IETF purposes, | | August 1: The IAOC approves the budget proposal for IETF purposes, |
after any appropriate revisions. As the ISOC President is part of | | after any appropriate revisions. As the ISOC President is part of |
the IAOC, the IAOC should have a preliminary indication of how the | | the IAOC, the IAOC should have a preliminary indication of how the |
budget will fit with ISOC's own budgetary expectations. The | | budget will fit with ISOC's own budgetary expectations. The |
| | |
| | |
| | |
| | Austein & Wijnen Expires June 7, 2005 [Page 16] |
| | |
| | Internet-Draft Structure of IASA December 2004 |
budget proposal is passed to the ISOC Board of Trustees for review | | budget proposal is passed to the ISOC Board of Trustees for review |
in accordance with their fiduciary duty. | | in accordance with their fiduciary duty. |
| | |
September 1: The ISOC Board of Trustees approves the budget proposal | | September 1: The ISOC Board of Trustees approves the budget proposal |
provisionally. During the next 2 months, the budget may be | | provisionally. During the next 2 months, the budget may be |
revised to be integrated in ISOC's overall budgeting process. | | revised to be integrated in ISOC's overall budgeting process. |
| | |
November 1: Final budget to the ISOC Board for approval. | | November 1: Final budget to the ISOC Board for approval. |
| | |
The dates described above are examples, and are subject to change. | | The dates described above are subject to change, and |
They will most likely be modified each year based on the dates of the | | will most likely be modified each year based on the dates of the |
second and third IETF meetings of that year. They also need to be | | second and third IETF meetings of that year. |
synchronized with the ISOC budgeting process. | | |
| | |
The IAD shall provide monthly accountings of expenses, and shall | | The IAD shall provide monthly accountings of expenses, and shall |
update expenditures forecasts every quarter. This may require | | update expenditures forecasts every quarter. This may require |
adjustment of the IASA budget: if so, the revised budget will need to | | 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, | | be approved by the IAOC, the ISOC President/CEO and, if necessary, |
the ISOC Board of Trustees. | | the ISOC Board of Trustees. |
| | |
7. ISOC Responsibilities for IASA | | 7. ISOC Responsibilities for IASA |
| | |
Within ISOC, support for the IASA shall meet the following goals: | | Within ISOC, support for the IASA shall meet the following goals: |
| | |
Transparency: The IETF community shall have complete visibility into | | Transparency: The IETF community shall have complete visibility into |
the financial and legal structure of the ISOC standards activity. | | the financial and legal structure of the ISOC standards activity. |
In particular, a detailed budget for the entire standards | | In particular, a detailed budget for the entire standards |
activity, quarterly financial reports, and audited annual | | activity, quarterly financial reports, and audited annual |
financial reports shall all be available to the IETF community. | | financial reports shall all be available to the IETF community. |
In addition, key contract material and MOUs shall also be publicly | | In addition, key contract material and MOUs shall also be publicly |
available. The IAD and IAOC are responsible for providing regular | | available. The IAD and IAOC are responsible for providing regular |
overviews of the state of the IASA to the IETF community. | | overviews of the state of the IASA to the IETF community. |
| | |
Unification: As part of this arrangement, ISOC's sponsorship of the | | Unification: As part of this arrangement, ISOC's sponsorship of the |
RFC Editor, IAB and IESG shall be managed as part of the IASA | | RFC Editor, IAB and IESG shall be managed as part of the IASA |
under the IAOC. | | under the IAOC. |
| | |
Independence: The IASA shall be distinct from other ISOC activities. | | Independence: The IASA shall be distinct from other ISOC activities. |
ISOC will support the IASA through the mechanisms specified in | | ISOC will support the IASA through the mechanisms specified in |
this document and its successors. | | this document and its successors. |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 16] | | |
| | |
Internet-Draft Structure of IASA December 2004 | | |
| | |
| | |
Support: ISOC shall work with the IAD and IAOC to ensure appropriate | | Support: ISOC shall work with the IAD and IAOC to ensure appropriate |
financial support for the IASA, following the mechanisms described | | financial support for the IASA, following the mechanisms described |
in this document and its successors. | | in this document and its successors. |
| | |
Removability: While there is no current plan to transfer the legal | | Removability: While there is no current plan to transfer the legal |
and financial home of the IASA to another corporation, the IASA | | and financial home of the IASA to another corporation, the IASA |
shall be structured to enable a clean transition in the event that | | shall be structured to enable a clean transition in the event that |
the IETF community decides that such a | | the IETF community decides, through BCP publication, that such a |
| | |
| | |
| | |
| | Austein & Wijnen Expires June 7, 2005 [Page 17] |
| | |
transition is required and | | Internet-Draft Structure of IASA December 2004 transition is required. |
documents its consensus in a formal document (currently called a | | |
BCP). In such a case, the IAOC shall give ISOC a minimum of six | | In such a case, the IAOC shall give ISOC a minimum of six |
months notice before the transition formally occurs. During that | | months notice before the transition formally occurs. During that |
period, the IAOC and ISOC shall work together to create a smooth | | period, the IAOC and ISOC shall work together to create a smooth |
transition that does not result in any significant service outages | | transition that does not result in any significant service outages |
or missed IETF meetings. All contracts executed by ISOC on behalf | | or missed IETF meetings. All contracts executed by ISOC on behalf |
of IASA shall either include a clause allowing termination by ISOC | | of IASA shall either include a clause allowing termination or transfer by ISOC |
with six months notice, or shall be transferable to another | | with six months notice, or shall be transferable to another |
corporation in the event that the IASA transitions away from ISOC. | | corporation in the event that the IASA transitions away from ISOC. |
Any accrued funds, any IETF-specific intellectual property rights, | | Any accrued funds, any IETF-specific intellectual property rights, |
and any IETF-specific data and tools shall also transition to the | | and any IETF-specific data and tools shall also transition to the |
new entity. | | new entity. |
| | |
Within the constraints outlined above, all other details of how to | | Within the constraints outlined above, all other details of how to |
structure this activity within ISOC (whether as a cost center, a | | structure this activity within ISOC (whether as a cost center, a |
department, or a formal subsidiary) shall be determined by ISOC in | | department, or a formal subsidiary) shall be determined by ISOC in |
consultation with the IAOC. | | consultation with the IAOC. |
| | |
8. Security Considerations | | 8. Security Considerations |
| | |
This document describes the structure of the IETF's administrative | | This document describes the structure of the IETF's administrative |
support activity. It introduces no security considerations for the | | support activity. It introduces no security considerations for the |
Internet. | | Internet. |
| | |
9. IANA Considerations | | 9. IANA Considerations |
| | |
This document has no IANA considerations in the traditional sense. | | This document has no IANA considerations in the traditional sense. |
However, some of the information in this document may affect how the | | However, some of the information in this document may affect how the |
IETF standards process interfaces with IANA, so IANA may be | | IETF standards process interfaces with IANA, so IANA may be |
interested in the contents. | | interested in the contents. |
| | |
10. Acknowledgements | | 10. Acknowledgements |
| | |
The editors would like to thank everyone who provided feedback on | | The editors would like to thank everyone who provided feedback on |
this document or any of its predecessors back to the original | | this document or any of its predecessors back to the original |
"Scenario O" e-mail message. In particular, the editors would like | | "Scenario O" e-mail message. In particular, the editors would like |
to thank: Bernard Aboba, Harald Alvestrand, Fred Baker, Scott | | to thank: Bernard Aboba, Harald Alvestrand, Fred Baker, Scott |
Bradner, Scott Brim, Brian Carpenter, Dave Crocker, Avri Doria, Tony | | Bradner, Brian Carpenter, Dave Crocker, Avri Doria, Tony |
Hain, Joel Halpern, Ted Hardie, Sam Hartman, Geoff Huston, John | | Hain, Joel Halpern, Ted Hardie, Sam Hartman, Geoff Huston, John |
Klensin, Valdis Kletnieks, Eliot Lear, Henrik Levkowetz, Carl | | Klensin, Valdis Kletnieks, Eliot Lear, Henrik Levkowetz, Carl |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 17] | | |
| | |
Internet-Draft Structure of IASA December 2004 | | |
| | |
| | |
Malamud, Allison Mankin, Eric Rescorla, Glenn Ricart, and Lynn St | | Malamud, Allison Mankin, Eric Rescorla, Glenn Ricart, and Lynn St |
Amour. | | Amour. |
| | |
Special thanks are due to Leslie Daigle and Margaret Wasserman, who | | Special thanks are due to Leslie Daigle and Margaret Wasserman, who |
wrote the original "Scenario O" message and edited the earliest | | wrote the original "Scenario O" message and edited the earliest |
versions of this document. | | versions of this document. |
| | |
Special thanks are also due to Henrik Levkowetz for kindly | | |
volunteering to maintain the issue tracking system associated with | | |
this document. | | |
| | |
No doubt the above list is incomplete. We apologize to anyone whom | | No doubt the above list is incomplete. We apologize to anyone whom |
we left out. | | we left out. |
| | |
| | |
| | |
| | Austein & Wijnen Expires June 7, 2005 [Page 18] |
| | |
| | Internet-Draft Structure of IASA December 2004 |
| | |
This document was written using the xml2rfc tool described in RFC | | This document was written using the xml2rfc tool described in RFC |
2629 [RFC2629]. | | 2629 [RFC2629]. |
| | |
11. References | | 11. References |
| | |
11.1 Normative References | | 11.1 Normative References |
| | |
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision | | [RFC2026] Bradner, S., "The Internet Standards Process -- Revision |
3", BCP 9, RFC 2026, October 1996. | | 3", BCP 9, RFC 2026, October 1996. |
| | |
[RFC3716] Advisory, IAB., "The IETF in the Large: Administration and | | [RFC3716] Advisory, IAB., "The IETF in the Large: Administration and |
Execution", RFC 3716, March 2004. | | Execution", RFC 3716, March 2004. |
| | |
[RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and | | [RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and |
Recall Process: Operation of the Nominating and Recall | | Recall Process: Operation of the Nominating and Recall |
Committees", BCP 10, RFC 3777, June 2004. | | Committees", BCP 10, RFC 3777, June 2004. |
| | |
11.2 Informative References | | 11.2 Informative References |
| | |
[ISOC] Internet Society, "Internet Society By-Laws", February | | [ISOC] Internet Society, "Internet Society By-Laws", February |
2001, | | 2001, |
<http://www.isoc.org/isoc/general/trustees/bylaws.shtml>. | | <http://www.isoc.org/isoc/general/trustees/bylaws.shtml>. |
| | |
[RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031, October | | [RFC2031] Huizer, E., "IETF-ISOC relationship", RFC 2031, October |
1996. | | 1996. |
| | |
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, | | [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, |
June 1999. | | June 1999. |
| | |
[RFC2850] Internet Architecture Board and B. Carpenter, "Charter of | | [RFC2850] Internet Architecture Board and B. Carpenter, "Charter of |
the Internet Architecture Board (IAB)", BCP 39, RFC 2850, | | the Internet Architecture Board (IAB)", BCP 39, RFC 2850, |
May 2000. | | May 2000. |
| | |
[RFC3233] Hoffman, P. and S. Bradner, "Defining the IETF", BCP 58, | | |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 18] | | |
| | |
Internet-Draft Structure of IASA December 2004 | | |
| | |
| | |
RFC 3233, February 2002. | | |
| | |
[RFC3668] Bradner, S., "Intellectual Property Rights in IETF | | [RFC3668] Bradner, S., "Intellectual Property Rights in IETF |
Technology", BCP 79, RFC 3668, February 2004. | | Technology", BCP 79, RFC 3668, February 2004. |
| | |
[RFC3677] Daigle, L. and Internet Architecture Board, "IETF ISOC | | [RFC3677] Daigle, L. and Internet Architecture Board, "IETF ISOC |
Board of Trustee Appointment Procedures", BCP 77, RFC | | Board of Trustee Appointment Procedures", BCP 77, RFC |
3677, December 2003. | | 3677, December 2003. |
| | |
[RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, February | | [RFC3710] Alvestrand, H., "An IESG charter", RFC 3710, February |
2004. | | 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 appendix (including all of | | |
its subsections) prior to publication. | | |
| | |
This document was produced as part of the overall IETF Administrative | | |
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 | | |
feedback on this document. It can be found at: | | |
| | |
https://rt.psg.com (user: ietf, password: ietf, queue: iasa-bcp). | | |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 19] | | |
| | |
Internet-Draft Structure of IASA December 2004 | | |
| | |
| | |
This text corresponds to $Revision: 1.1 $ of the XML source for this | | |
document. | | |
| | |
A.1 Changes in draft-ietf-iasa-bcp-03.txt | | |
| | |
o Removed "Closed Issues" section, replaced "Open Issues" section | | |
with another pointer to the RT ticket queue, since that is now | | |
more likely to be up-to-date than any list in this document. | | |
| | |
o Added text that IAOC specifies and publishes rules for conflict | | |
resolution. See issue #754. | | |
| | |
o Changed text on quarterly credits to IASA accounts as per | | |
discussion in issue #748. Issue seems not closed yet. | | |
| | |
o Clarifications in budget process, see issue #749. | | |
| | |
o Editorial change on wording "rights in data" as per issue #735. | | |
| | |
o Editorial changes as per issue #727. | | |
| | |
o Clarified text about requirements for in-house and outsourced | | |
activities. Issue #723. | | |
| | |
o Added text about how an IAOC vacancy is dealt with. Issue #741. | | |
| | |
o Removed a redundant sentence on donation coordination. Issue | | |
#738. | | |
| | |
o Added text to state that IAOC decisions are minuted and minutes | | |
are published. Issues #714 and #718. | | |
| | |
o Refined text on removability (BCP doc) as per issue #751. | | |
| | |
o Removed word "officer" from text, as per issue #731. | | |
| | |
o Added a 2nd paragraph on IAOC decision making rules. Issue #746. | | |
| | |
o Added text at the end of Section 3.2 to make IAOC responsible for | | |
filling in if there is no IAD or when IAD is not available. Issue | | |
#744. | | |
| | |
o Clarified text in 2nd principle. Issue #730. | | |
| | |
o Added IETF to Section 2.1. Issue #743. | | |
| | |
o Changed wording of 3rd principle in Section 2.2 to make it clearer | | |
that budget development is an iterative process that happens in | | |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 20] | | Austein & Wijnen Expires June 7, 2005 [Page 19] |
| | |
Internet-Draft Structure of IASA December 2004 | | Internet-Draft Structure of IASA December 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 appendix (including all of |
| | its subsections) prior to publication. |
| | |
| | This document was produced as part of the overall IETF Administrative |
| | Restructuring (AdminRest) effort. Information |
| | |
| | |
cooperation with ISOC. | | |
| | |
o Added a principle about the | | about the effort and |
| | related documents can be found at: |
| | |
| | http://www.alvestrand.no/ietf/adminrest |
| | |
fact that IETF money stays IETF money | | We are using an issue tracker |
once credited to IETF accounts. | | to track |
| | |
o Changed the | | the editorial and substantive |
word "account" into "accounts" at a few places to be | | feedback on this document. It can be found at: |
| | |
| | https://rt.psg.com (user: ietf, password: ietf, queue: iasa-bcp). |
| | |
| | We ended up not using the issue tracker so much. Instead we have |
| | listed open issues (and now also closed issues) |
more in | | in this document |
| | itself. |
| | |
| | $Revision: 1.1 $ |
| | |
line with the concept of divisional accounting. | | A.1 |
| | |
| | |
A.2 Changes in draft-ietf-iasa-bcp-02.txt | | Changes in draft-ietf-iasa-bcp-02.txt |
| | |
o Split issues list into separate lists of open issues and closed | | o Split issues list into separate lists of open issues and closed |
issues (as seen by the editors). | | issues (as seen by the editors). Everyone should check Section |
| | 1.3 and Section 1.2 carefully to see whether they agree with the |
Removed some inline editors' | | editors' characterization of these issues. Removed some inline editors' |
comments when we believed that an issue has been | | comments when we believed that an issue has been |
| | |
| | |
| | |
| | Austein & Wijnen Expires June 7, 2005 [Page 20] |
| | |
resolved. | | Internet-Draft Structure of IASA December 2004 resolved. |
| | |
o Added Section 2.5 on when the procedures in this document become | | o Added Section 2.5 on when the procedures in this document become |
effective. | | effective. |
| | |
o Changed text in Section 5 to state that the goal is a viable IASA | | o Changed text in Section 5 to state that the goal is a viable IASA |
based on all funding as opposed to just meeting fees and | | based on all funding as opposed to just meeting fees and |
designated donations. | | designated donations. |
| | |
o Added text to Section 2.2 stating that funds and donations shall | | o Added text to Section 2.2 stating that funds and donations shall |
be irrevocably assigned to IETF. | | be irrevocably assigned to IETF. |
| | |
o Removed section on IAD Committees. | | o Removed section on IAD Committees. |
| | |
o Changed the text in Section 4 on IAOC Chair selection and | | o Changed the text in Section 4 on IAOC Chair selection and |
responsibilities. It is now very similar to IAB chair selection | | responsibilities. It is now very similar to IAB chair selection |
as in RFC2850. | | as in RFC2850. |
| | |
o Various textual clarifications. This also includes several | | o Various textual clarifications. This also includes several |
changes of "will" and "should" into "shall". | | changes of "will" and "should" into "shall". |
| | |
o Moved disclaimer of variance procedure to Section 3 and | | o Moved disclaimer of variance procedure to Section 3 and |
generalized it. | | generalized it. |
| | |
o Improved wording on IPR in Section 2.2 and added specific text for | | o Improved wording on IPR in Section 2.2 and added specific text for |
IAD to ensure we have proper rights to any IPR. Section 5.1 | | IAD to ensure we have proper rights to any IPR. Section 5.1 |
| | |
o Cleanup Section 7. | | o Cleanup Section 7. |
| | |
| | |
| | A.2 |
| | |
| | |
A.3 Changes in draft-ietf-iasa-bcp-01.txt | | Changes in draft-ietf-iasa-bcp-01.txt |
| | |
o Added a list of open issues (Section 1.2). | | o Added a list of open issues (Section 1.3). |
| | |
o Added that small committee determines initial compensation for | | o Added that small committee determines initial compensation for |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 21] | | |
| | |
Internet-Draft Structure of IASA December 2004 | | |
| | |
| | |
IAD. | | IAD. |
| | |
o Added a set of Principles (Section 2.2) on which any details are | | o Added a set of Principles (Section 2.2) on which any details are |
(should be) based. | | (should be) based. |
| | |
o Added "Community Consensus and Grant of Authority" (Section 2.3). | | o Added "Community Consensus and Grant of Authority" (Section 2.3). |
| | |
o Added more acknowledgments (no doubt still incomplete). | | o Added more acknowledgments (no doubt still incomplete). |
| | |
o Clarified Section 5 and subsections. Added Editors' note. | | o Clarified Section 5 and subsections. Added Editors' note. |
| | |
o Clarified what happens if IAOC voting results in a tie. | | o Clarified what happens if IAOC voting results in a tie. |
| | |
| | |
| | |
| | |
| | Austein & Wijnen Expires June 7, 2005 [Page 21] |
| | |
| | Internet-Draft Structure of IASA December 2004 |
| | |
o Changed the selection of person(s) to act as IETF Executive | | o Changed the selection of person(s) to act as IETF Executive |
Director. | | Director. |
| | |
o Added a disclaimer in Section 5, stating that IAOC can deal with | | o Added a disclaimer in Section 5, stating that IAOC can deal with |
changes because of legal, accounting or practical reasons. | | changes because of legal, accounting or practical reasons. |
| | |
o Removed "insurance" example in Section 5.4. | | o Removed "insurance" example in Section 5.4. |
| | |
o Added a reference to ISOC bylaws. | | o Added a reference to ISOC bylaws. |
| | |
o Stop using term "liaison" to mean "non-voting IAOC member"; | | o Stop using term "liaison" to mean "non-voting IAOC member"; |
instead, spell out which members are voting and which are not. | | instead, spell out which members are voting and which are not. |
Add text allowing IAOC to request non-voting liaisons from other | | Add text allowing IAOC to request non-voting liaisons from other |
bodies. | | bodies. |
| | |
o Various editorial cleanups. | | o Various editorial cleanups. |
| | |
| | |
| | A.3 |
| | |
| | |
A.4 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 Section 5. |
| | |
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. |
| | |
o Changed 2nd paragraph in "Structure of IASA" section to replace | | o Changed 2nd paragraph in "Structure of IASA" section to replace |
the fuzzy term "executive-level" and to be clear about cost | | the fuzzy term "executive-level" and to be clear about cost |
aspects. | | aspects. |
| | |
o Made it explicit that the IESG's role as a confirming body only | | o Made it explicit that the IESG's role as a confirming body only |
applies to IAOC appointments made by the NomCom. | | applies to IAOC appointments made by the NomCom. |
| | |
o Editorial changes at various places in the document. | | o Editorial changes at various places in the document. |
| | |
| | |
| | A.4 |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 22] | | |
| | |
Internet-Draft Structure of IASA December 2004 | | |
| | |
| | |
A.5 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 |
| | |
| | |
| | |
| | Austein & Wijnen Expires June 7, 2005 [Page 22] |
| | |
| | Internet-Draft Structure of IASA December 2004 |
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. |
| | |
| | |
| | A.5 |
| | |
| | |
A.6 Origin of draft-wasserman-iasa-bcp-00.txt | | Origin 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. |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
Austein & Wijnen Expires June 23, 2005 [Page 23] | | Austein & Wijnen Expires June 7, 2005 [Page 23] |
| | |
Internet-Draft Structure of IASA December 2004 | | Internet-Draft Structure of IASA December 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 June 23, 2005 [Page 24] | | Austein & Wijnen Expires June 7, 2005 [Page 24] |
| | |
| |
|