idnits 2.17.1 draft-daigle-adminrest-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([2], [3], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 154 has weird spacing: '...cted by and s...' == Line 238 has weird spacing: '...tion of the N...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 8, 2004) is 7383 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Historic draft: draft-iab-advcomm (ref. '1') -- Possible downref: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '3' == Outdated reference: A later version (-09) exists of draft-ietf-nomcom-rfc2727bis-08 Summary: 5 errors (**), 0 flaws (~~), 5 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group L. Daigle 3 Internet-Draft H. Alvestrand 4 Expires: August 8, 2004 February 8, 2004 6 A Proposal for IETF Administrative Restructuring 7 draft-daigle-adminrest-00.txt 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as Internet- 17 Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt. 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 This Internet-Draft will expire on August 8, 2004. 32 Copyright Notice 34 Copyright (C) The Internet Society (2004). All Rights Reserved. 36 Abstract 38 This document outlines a proposal for an administrative oversight 39 entity for the collection of activities that allow the IETF to carry 40 out its work. The current description of the IETF's work can be 41 found in [2]. The proposal is based on the observations and 42 recommendations outlined in the IAB Advisory Committee report ([1]). 43 The motivation for this proposal is described separately ([3]). 44 These 4 documents must be read together for completeness. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. Proposal Overview . . . . . . . . . . . . . . . . . . . . . 3 50 3. IETF Administration Group (AG) . . . . . . . . . . . . . . . 4 51 3.1 AG Activities . . . . . . . . . . . . . . . . . . . . . . . 4 52 3.1.1 Administration . . . . . . . . . . . . . . . . . . . . . . . 4 53 3.1.2 Operations . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 3.2 AG Composition . . . . . . . . . . . . . . . . . . . . . . . 4 55 3.3 AG Committees . . . . . . . . . . . . . . . . . . . . . . . 5 56 4. Board of the Administration Group (BAG) . . . . . . . . . . 5 57 4.1 BAG Activities . . . . . . . . . . . . . . . . . . . . . . . 5 58 4.2 BAG Composition . . . . . . . . . . . . . . . . . . . . . . 5 59 5. Security Considerations . . . . . . . . . . . . . . . . . . 6 60 References . . . . . . . . . . . . . . . . . . . . . . . . . 6 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 6 62 Full Copyright Statement . . . . . . . . . . . . . . . . . . 8 64 1. Introduction 66 This document outlines a proposal for an administrative oversight 67 entity for the collection of activities that allow the IETF to carry 68 out the work described in [2]. The specific motivation for the 69 proposal can be found in [3], and these were prepared in response to 70 the outcome of the IAB Advisory Committee, published in [1]. All 4 71 documents must be read for completeness. 73 This purpose of this proposal is to present the concepts and 74 structural relationship to existing IETF activities. It deliberately 75 remains agnostic about the specific implementation form of any 76 eventual organizational structure. Details and more formal 77 procedural guidelines implementing the structure outlined in this 78 document will be set out in subsequent formal documents such as 79 bylaws and/or constitutional documents, as appropriate to the formal 80 structure chosen for implementation. 82 Specific goals of this restructuring are to recognize and preserve 83 the community-driven nature of the IETF's work, and to continue to 84 support it through the formalization of a single administrative 85 umbrella that is openly accountable to that same community. 87 2. Proposal Overview 89 This proposal preserves the existing IETF standardization process 90 structure, led by the IESG and IAB in their respective roles, and 91 introduces a new Administration Group (AG) to carry out the formal 92 administration processes of IETF organization. Like the IAB and the 93 IESG, the AG (through its Board) is accountable to the IETF community 94 as a whole. 96 In short, the responsibilities for the different IETF bodies can be 97 characterized as: 99 IAB: architecture and longterm technical overview; sponsorship 100 and organization of the IRTF; appeals; confirmation of IESG 101 appointments; oversight of standards process 103 IESG: management of standards work (working groups, documents, and 104 process) 106 AG: administrative arm of IETF organization; establishes and 107 manages contracts; proposes and executes budget plans; does NOT 108 change or influence the standards process 110 3. IETF Administration Group (AG) 112 An IETF Administration Group (AG) is proposed to provide the unified 113 administrative management of all IETF supporting functions. This 114 group is ultimately accountable to IETF participants, as described 115 below. 117 The AG will not replace any existing IETF support structure although 118 it subsumes some tasks that have been handled on an ad hoc basis by 119 IAB or IESG members or others. It will rather complement the 120 existing work (RFC-Editor, Secretariat, IANA protocol parameter 121 assignments), and take on the role of overall coordination and 122 management of the administration. This will permit unification of 123 fund-raising activities, flexibility in balancing budget allocations, 124 and coherence in management across the functions. 126 3.1 AG Activities 128 3.1.1 Administration 130 The AG is responsible for the administrative activities associated 131 with the IETF organization. Today, most of the operational work that 132 permits the IETF to continue creating and managing standards is done 133 by a disparate group of organizations dedicated to the ongoing health 134 of the Internet. It is expected that those organizations will 135 continue to do the work as they do today, but the AG will provide 136 administrative oversight for the IETF operational process, and will 137 give those organizations a clear anchor. The AG will negotiate and 138 formalize contracts with the organizations that provide support for 139 IETF functions, and will be responsible for ensuring their timely 140 payment and performance review. 142 3.1.2 Operations 144 As part of this activity, the AG will exercise financial control for 145 the whole IETF activity -- either handling the funds directly, or 146 providing executive oversight for the bodies that do. The AG will be 147 responsible for developing viable financial plans to support the IETF 148 activity, to better match revenue and costs across the board of IETF 149 support activities. 151 3.2 AG Composition 153 There will be one person designated as the manager of the AG. This 154 person will be selected by and serve at the pleasure of the Board of 155 the AG. 157 3.3 AG Committees 159 The expectation is that the manager of the AG will constitute 160 special-purpose, chartered committees to bring in expertise (e.g., 161 financial) or differing perspectives when and as necessary. These 162 committees may consist of subsets of the IAB and/or IESG, selected 163 IETF participants, or external experts, depending on the need. 165 These committees are advisory in nature -- the manager of the AG is 166 responsible for the outcome, including presenting and supporting any 167 material to the Board, as and when appropriate. 169 4. Board of the Administration Group (BAG) 171 The BAG provides oversight of the AG's activities, ensuring that they 172 are carried out in accordance with the IETF mission, and that 173 appropriate operational support is provided for the IAB, IESG, 174 working groups, etc, to carry out their chartered work. 176 4.1 BAG Activities 178 Election of Chair and Secretary of the BAG 180 Selection of manager of the AG 182 Budget approval 184 Financial review 186 Approval of major contracts and funding proposals 188 Publication of audited IETF financials 190 4.2 BAG Composition 192 At a minimum, the BAG will have 5 voting members: 194 IETF Chair 196 IAB Chair 198 3 appointed members with staggered 3 year renewable terms; these 199 members are selected by (though not necessarily members of) ISOC, 200 the IAB, the IESG. 202 The BAG also has, at a minimum, 3 non-voting members: 204 manager of the AG 206 a representative of the IETF's legal counsel 208 a treasurer (if necessary; appointment process TBD) 210 The BAG will organize itself to elect a Secretary and a Chair for 211 one-year, renewable appointments. The Secretary may be any BAG 212 member; the Chair must be a voting member of the BAG. 214 Although appointed by ISOC, the IAB and IESG, the BAG is accountable 215 directly to the IETF community. At any time, a recall against an 216 appointed BAG member may be proposed by members of the IETF community 217 (procedure to be defined). Once a BAG member has been recalled, they 218 are ineligible to be re-appointed (for a period analogous to that 219 outlined in [4]). 221 5. Security Considerations 223 This document does not discuss Internet protocols, and thereby 224 introduces no security issues for their operation. 226 References 228 [1] AdvComm, AdvComm., "The IETF in the Large: Administration and 229 Execution", draft-iab-advcomm-01 (work in progress), December 230 2003. 232 [2] Alvestrand, H., "IETF Mission Statement", February 2004. 234 [3] Alvestrand, H. and L. Daigle, "IETF Administration 235 Restructuring: Motivation", February 2004. 237 [4] Galvin, J., "IAB and IESG Selection, Confirmation, and Recall 238 Process: Operation of the Nominating and Recall Committees", 239 draft-ietf-nomcom-rfc2727bis-08 (work in progress), October 240 2002. 242 Authors' Addresses 244 Leslie Daigle 246 EMail: leslie@thinkingcat.com, leslie@verisignlabs.com 247 Harald Alvestrand 249 EMail: harald@alvestrand.no 251 Full Copyright Statement 253 Copyright (C) The Internet Society (2004). All Rights Reserved. 255 This document and translations of it may be copied and furnished to 256 others, and derivative works that comment on or otherwise explain it 257 or assist in its implementation may be prepared, copied, published 258 and distributed, in whole or in part, without restriction of any 259 kind, provided that the above copyright notice and this paragraph are 260 included on all such copies and derivative works. However, this 261 document itself may not be modified in any way, such as by removing 262 the copyright notice or references to the Internet Society or other 263 Internet organizations, except as needed for the purpose of 264 developing Internet standards in which case the procedures for 265 copyrights defined in the Internet Standards process must be 266 followed, or as required to translate it into languages other than 267 English. 269 The limited permissions granted above are perpetual and will not be 270 revoked by the Internet Society or its successors or assigns. 272 This document and the information contained herein is provided on an 273 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 274 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 275 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 276 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 277 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 279 Acknowledgement 281 Funding for the RFC Editor function is currently provided by the 282 Internet Society.