idnits 2.17.1 draft-iab-iesg-iaoc-selection-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 402. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 379. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 386. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 392. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to 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 a Security Considerations section. ** 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.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (September 19, 2005) is 6794 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) -- Obsolete informational reference (is this intentional?): RFC 4071 (Obsoleted by RFC 8711) Summary: 5 errors (**), 0 flaws (~~), 2 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Architecture Board, G. Huston, Ed. 3 Internet Engineering Steering APNIC 4 Group B. Wijnen, Ed. 5 Internet-Draft IESG 6 Expires: March 23, 2006 September 19, 2005 8 IAOC Member Selection Guidelines and Process 9 draft-iab-iesg-iaoc-selection-03.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on March 23, 2006. 36 Copyright Notice 38 Copyright (C) The Internet Society (2005). 40 Abstract 42 This memo outlines the guidelines for selection of members of the 43 IETF Administrative Oversight Committee, and describes the selection 44 process used by the IAB and the IESG. 46 Document Revision Notes 48 [RFC Editor: Please remove this section prior to publication.] 49 The following changes have been made to the draft: 51 draft-iab-iesg-iaoc-selection-03: 53 Title and Abstract 54 Changed title and abstract to reflect the inclusion of general 55 guidelines for selection of IAOC members, as well as the IAB 56 and IESG selection process description. 58 Section 2. Desirable Qualifications and Selection Criteria for 59 IETF Nominated IAOC members 60 Change of 4th paragraph to improve readability. 62 Section 3.4 Term of Office and Selection Timeframe 63 Change nomination period to 3 - 4 weeks. 65 Section 3.5 Mid-term Vacancies, Section 3.5.1. Interim Appointment 66 Process 67 Change "biannual" to "two year". 69 draft-iab-iesg-iaoc-selection-02: 71 Section 1. Introduction 72 Added a comment that the Nominations Committee shall use the 73 qualifications and section criteria described in this document, 74 and that the ISOC Board of Trustees may also make use of these 75 criteria and qualifications. 77 Section 2. Qualifications and Selection Criteria 78 Added a comment that the Nominations Committee-selected member 79 is accountable to the entire IETF (as per IESG and IAB-selected 80 members). 82 draft-iab-iesg-iaoc-selection-01: 84 Section 3.1 Nominations and Eligibility 85 Reworded a potential ambiguity over recusal in selection. 87 draft-iab-iesg-iaoc-selection-00: 89 Merged drafts 90 This document is a merge of the IAB and IESG drafts on IAOC 91 selection. 93 draft-iab-iaoc-selection-01: 95 Confirmation of selected Candidate 96 On the basis that this is an IAB selection as distinct from an 97 IETF selection, the step of confirmation of the selected 98 candidate by the IESG has been removed. 100 Section 3.4 Timeframe 101 Extended the time frame to allow for a total time of between 5 102 to 7 weeks for this process. 104 1. Introduction 106 The IETF Administrative Support Activity (IASA) provides the 107 administrative structure required to support the IETF standards 108 process and to support the IETF's technical activities. Within this 109 activity is the office of an Internet Administrative Director (IAD) 110 and the Internet Administrative Oversight Committee (IAOC). In 111 addition to the ex-officio roles of the IETF Chair and IAB Chair on 112 this committee, the IAB and IESG are each responsible for the 113 appointment of one voting member of this committee. 115 This memo outlines the process by which the IAB and IESG make their 116 selections. This process will also be used in the event of mid-term 117 vacancies that may arise with these positions. 119 The document also provides guidance to the IETF Nominations Committee 120 regarding desireable qualifications and selection criteria for IAOC 121 candidates. 123 The same guidance may be used by the ISOC Board of Trustees within 124 their process of IAOC member appointment. 126 1.1. Overview of IAOC 128 The IASA is described in [RFC4071]. It is headed by a full-time 129 Internet Society (ISOC) employee, the IETF Administrative Director 130 (IAD), an officer empowered to act on behalf of the IASA at the 131 direction of the IAOC. 133 The IAOC's role is to provide appropriate direction to the IAD, to 134 review the IAD's regular reports, and to oversee the IASA functions 135 to ensure that the administrative needs of the IETF community are 136 being properly met. The IAOC's mission is not to be engaged in the 137 day-to-day administrative work of IASA, but rather to provide 138 appropriate direction, oversight and approval. 140 As described in [RFC4071], the IAOC's responsibilities are: 142 o To select the IAD and provide high-level review and direction for 143 his or her work. This task should be handled by a sub-committee, 144 as described in [RFC4071]. 146 o To review the IAD's plans and contracts to ensure that they will 147 meet the administrative needs of the IETF. 149 o To track whether the IASA functions are meeting the IETF 150 community's administrative needs, and to work with the IAD to 151 determine a plan for corrective action if they are not. 153 o To review the IAD's budget proposals to ensure that they will meet 154 the IETF's needs, and review the IAD's regular financial reports. 156 o To ensure that the IASA is run in a transparent and accountable 157 manner. While the day-to-day work should be delegated to the IAD 158 and others, the IAOC is responsible for ensuring that IASA 159 finances and operational status are tracked appropriately, and 160 that monthly, quarterly, and annual financial and operational 161 reports are published to the IETF community. 163 o To designate, in consultation with the IAB and the IESG, the 164 person or people who carry out the tasks which other IETF process 165 documents say are carried out by the IETF Executive Director. 167 The IAOC's role is to direct and review, not perform, the work of the 168 IAD and IASA. The IAOC holds periodic teleconferences and face-to- 169 face meetings as needed to carry out the IAOC's duties efficiently 170 and effectively. 172 1.2. Overview of Selection Process 174 In brief, this document describes the time frame and procedures for 175 the IAB and IESG to solicit public input and make a selection for the 176 position. 178 2. Desirable Qualifications and Selection Criteria for IETF Nominated 179 IAOC members 181 The qualifications and selection criteria described in this section 182 shall be used by the IAB and IESG in selecting a suitably qualified 183 candidate for the IAOC position. As described in [RFC4071] the IETF 184 Nominations Committee also has the responsibility to select IAOC 185 members, and the Nominations Committee shall also use these 186 desireable qualifications and selection criteria to guide their 187 selection process. The same guidance may be used by the ISOC Board 188 of Trustees within their process of IAOC member appointment. 190 Candidates for these IAOC positions should have knowledge of the 191 IETF, knowledge of contracts and financial procedures, and 192 familiarity with the administrative support needs of the IAB, the 193 IESG, and the IETF standards process. 195 The candidates are also expected to be able to understand the 196 respective roles and responsibilities of the IETF and ISOC in this 197 activity, and be able to articulate these roles within the IETF 198 community. 200 The candidates will also be expected to exercise all the duties of an 201 IAOC member, including being prepared to undertake any associated 202 responsibilities. These include, but are not limited to, the setting 203 of administrative support policies, oversight of the administrative 204 operations of the IETF, and representing the interests of the IETF to 205 the IAOC. The candidates must be able to undertake full 206 participation in all Committee meetings and Committee activities. 208 In the case of the IAB-selected member of the IAOC, this individual 209 does not directly represent the IAB. Similarly for the IESG-selected 210 member of the IAOC, this individual does not directly represent the 211 IESG. The IAB and IESG selected members are accountable directly to 212 the IETF community. 214 In the case of IAOC members selected by the IETF Nominations 215 Committee, such members do not represent any particular sub-grouping 216 of IETF participants. IETF Nominations Committee selected IAOC 217 members are accountable directly to the entire IETF community. 219 3. IAB and IESG Selection Process of an IAOC member 221 3.1. Nominations and Eligibility 223 The IAB and IESG will alternate year by year in making a public call 224 for nominations on the ietf-announce@ietf.org mailing list. The 225 public call will specify the manner by which nominations will be 226 accepted and the means by which the list of nominees will be 227 published. 229 Self-nominations are permitted. Along with the name and contact 230 information for each candidate, details about the candidate's 231 background and qualifications for the position should be attached to 232 the nomination. All IETF participants, including working group 233 chairs, IETF Nominating Committee members, IAB and IESG members are 234 eligible for nomination. 236 IAB members who accept a nomination for an IAB-selected position will 237 recuse themselves from IAB selection discussions. Similarly, IESG 238 members who accept a nomination for an IESG-selected position will 239 recuse themselves from IESG selection discussions. 241 3.2. Selection 243 The selecting body will publish the list of nominated persons prior 244 to making a decision, allowing time for the community to pass any 245 relevant comments to that body. 247 The selecting body will review the nomination material, any submitted 248 comments, and make their selection. 250 3.3. Care of Personal Information 252 The following procedures will be used by the IAB and IESG in managing 253 candidates' personal information: 255 o The candidate's name will be published, with all other candidate 256 names, at the close of the nominations period. 258 o Except as noted above, all information provided to the IAB or IESG 259 during this process will be kept as confidential to that body. 261 3.4. Term of Office and Selection Timeframe 263 The IAB and IESG expect to seat their selected committee member at 264 the first IETF meeting of every second year, for a two year term of 265 office. The IAB and IESG will alternate each year in undertaking a 266 selection, except for the initial selection. For the first year the 267 IAB and IESG will operate their selection process concurrently. Also 268 for the first year the IESG-selected candidate will serve on the 269 committee for an initial term ending with the first IETF meeting of 270 the following year, and the IAB-selected candidate will serve for a 271 term one year longer than the IESG-selected candidate. Thereafter 272 the candidates will be seated for two year terms. 274 Basic time frame requirements for the selection process are as 275 follows: 277 o 3 - 4 weeks for solicitation of nominations. 279 o 3 - 4 weeks for review of nominees, deliberation and selection. 281 In November of every year, the selecting body of that year will 282 announce the specific dates for the selection process for that year, 283 following the guidelines above. 285 3.5. Mid-term Vacancies 287 This document describes the process for the general appointment of 288 IAB-selected and IESG-selected IAOC members. However, if the 289 appointed member is unable to serve the full two year term, the 290 selecting body may, at its discretion, immediately select a 291 replacement to serve the remainder of the term using the interim 292 process defined in Section 3.5.1. If the selecting body does not 293 invoke the interim process, the next regularly scheduled two-year 294 selection process will fill the vacancy. 296 3.5.1. Interim Appointment Process 298 If the selecting body elects to fill the mid-term vacancy before the 299 next regularly scheduled two-year selection process, a separate time 300 line will be announced and the remainder of the process described in 301 this document will be followed. 303 4. Acknowledgements 305 This document is based extensively on RFC 3677 [RFC3677]. It has 306 benefited from helpful review comments from Harald Alvestrand, Brian 307 Carpenter, Leslie Daigle, Rob Evans, Michael Patton, Mark Townsley, 308 and Margaret Wasserman. 310 5. Informative References 312 [RFC3677] Daigle, L. and Internet Architecture Board, "IETF ISOC 313 Board of Trustee Appointment Procedures", BCP 77, 314 RFC 3677, December 2003. 316 [RFC4071] Austein, R. and B. Wijnen, "Structure of the IETF 317 Administrative Support Activity (IASA)", BCP 101, 318 RFC 4071, April 2005. 320 Appendix A. IAB Members 322 Internet Architecture Board members at the time this document was 323 drafted were: 325 Bernard Aboba 326 Loa Andersson 327 Brian Carpenter 328 Leslie Daigle 329 Patrik Faltstrom 330 Bob Hinden 331 Kurtis Lindqvist 332 David Meyer 333 Pekka Nikander 334 Eric Rescorla 335 Pete Resnick 336 Janathan Rosenberg 337 Lixia Zhang 339 Appendix B. IESG Members 341 Internet Engineering Steering Group members at the time this document 342 was drafted were: 344 Brian Carpenter 345 Bill Fenner 346 Ted Hardie 347 Sam Hartman 348 Scott Hollenbeck 349 Russell Housley 350 David Kessens 351 Allison Mankin 352 Mark Townsley 353 Jon Peterson 354 Margaret Wasserman 355 Bert Wijnen 356 Alex Zinin 358 Authors' Addresses 360 Geoff Huston (editor) 361 APNIC 363 Email: gih@apnic.net 365 Bert Wijnen (editor) 366 Internet Engineering Steering Group 368 Email: bwijnen@lucent.com 370 Intellectual Property Statement 372 The IETF takes no position regarding the validity or scope of any 373 Intellectual Property Rights or other rights that might be claimed to 374 pertain to the implementation or use of the technology described in 375 this document or the extent to which any license under such rights 376 might or might not be available; nor does it represent that it has 377 made any independent effort to identify any such rights. Information 378 on the procedures with respect to rights in RFC documents can be 379 found in BCP 78 and BCP 79. 381 Copies of IPR disclosures made to the IETF Secretariat and any 382 assurances of licenses to be made available, or the result of an 383 attempt made to obtain a general license or permission for the use of 384 such proprietary rights by implementers or users of this 385 specification can be obtained from the IETF on-line IPR repository at 386 http://www.ietf.org/ipr. 388 The IETF invites any interested party to bring to its attention any 389 copyrights, patents or patent applications, or other proprietary 390 rights that may cover technology that may be required to implement 391 this standard. Please address the information to the IETF at 392 ietf-ipr@ietf.org. 394 Disclaimer of Validity 396 This document and the information contained herein are provided on an 397 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 398 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 399 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 400 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 401 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 402 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 404 Copyright Statement 406 Copyright (C) The Internet Society (2005). This document is subject 407 to the rights, licenses and restrictions contained in BCP 78, and 408 except as set forth therein, the authors retain all their rights. 410 Acknowledgment 412 Funding for the RFC Editor function is currently provided by the 413 Internet Society.