idnits 2.17.1 draft-iab-iesg-iaoc-selection-01.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 347. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 324. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 331. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 337. ** 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 (June 8, 2005) is 6890 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 4 Group B. Wijnen, Ed. 5 Internet-Draft IESG 6 Expires: December 10, 2005 June 8, 2005 8 Process for the IAB and IESG selection of IAOC members 9 draft-iab-iesg-iaoc-selection-01.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 December 10, 2005. 36 Copyright Notice 38 Copyright (C) The Internet Society (2005). 40 Abstract 42 This memo outlines the process by which the IAB and the IESG makes 43 selections of members of the IETF Administrative Oversight Committee. 45 Document Revision Notes 47 [RFC Editor: Please remove this section prior to publication.] 48 The following changes have been made to the draft: 50 draft-iab-iesg-iaoc-selection-01: 52 Section 3.1 Nominations and Eligibility 53 Reworded a potential ambiguity over recusal in selection. 55 draft-iab-iesg-iaoc-selection-00: 57 Merged drafts 58 This document is a merge of the IAB and IESG drafts on IAOC 59 selection. 61 draft-iab-iaoc-selection-01: 63 Confirmation of selected Candidate 64 On the basis that this is an IAB selection as distinct from an 65 IETF selection, the step of confirmation of the selected 66 candidate by the IESG has been removed. 68 Section 3.4 Timeframe 69 Extended the time frame to allow for a total time of between 5 70 to 7 weeks for this process. 72 1. Introduction 74 The IETF Administrative Support Activity (IASA) provides the 75 administrative structure required to support the IETF standards 76 process and to support the IETF's technical activities. Within this 77 activity is the office of an Internet Administrative Director (IAD) 78 and the Internet Administrative Oversight Committee (IAOC). In 79 addition to the ex-officio roles of the IETF Chair and IAB Chair on 80 this committee, the IAB and IESG are each responsible for the 81 appointment of one voting member of this committee. 83 This memo outlines the process by which the IAB and IESG make their 84 selections. This process will also be used in the event of mid-term 85 vacancies that may arise with these positions. 87 1.1 Overview of IAOC 89 The IASA is described in [RFC4071]. It is headed by a full-time 90 Internet Society (ISOC) employee, the IETF Administrative Director 91 (IAD), an officer empowered to act on behalf of the IASA at the 92 direction of the IAOC. 94 The IAOC's role is to provide appropriate direction to the IAD, to 95 review the IAD's regular reports, and to oversee the IASA functions 96 to ensure that the administrative needs of the IETF community are 97 being properly met. The IAOC's mission is not to be engaged in the 98 day-to-day administrative work of IASA, but rather to provide 99 appropriate direction, oversight and approval. 101 As described in [RFC4071], the IAOC's responsibilities are: 103 o To select the IAD and provide high-level review and direction for 104 his or her work. This task should be handled by a sub-committee, 105 as described in [RFC4071]. 107 o To review the IAD's plans and contracts to ensure that they will 108 meet the administrative needs of the IETF. 110 o To track whether the IASA functions are meeting the IETF 111 community's administrative needs, and to work with the IAD to 112 determine a plan for corrective action if they are not. 114 o To review the IAD's budget proposals to ensure that they will meet 115 the IETF's needs, and review the IAD's regular financial reports. 117 o To ensure that the IASA is run in a transparent and accountable 118 manner. While the day-to-day work should be delegated to the IAD 119 and others, the IAOC is responsible for ensuring that IASA 120 finances and operational status are tracked appropriately, and 121 that monthly, quarterly, and annual financial and operational 122 reports are published to the IETF community. 124 o To designate, in consultation with the IAB and the IESG, the 125 person or people who carry out the tasks which other IETF process 126 documents say are carried out by the IETF Executive Director. 128 The IAOC's role is to direct and review, not perform, the work of the 129 IAD and IASA. The IAOC holds periodic teleconferences and face-to- 130 face meetings as needed to carry out the IAOC's duties efficiently 131 and effectively. 133 1.2 Overview of Selection Process 135 In brief, this document describes the time frame and procedures for 136 the IAB and IESG to solicit public input and make a selection for the 137 position. 139 2. Desirable Qualifications and Selection Criteria for IAB and IESG 140 Nominated IAOC members 142 Candidates for these IAOC positions should have knowledge of the 143 IETF, knowledge of contracts and financial procedures, and 144 familiarity with the administrative support needs of the IAB, the 145 IESG, and the IETF standards process. 147 The candidates are also expected to be able to understand the 148 respective roles and responsibilities of the IETF and ISOC in this 149 activity, and be able to articulate these roles within the IETF 150 community. 152 The candidates will also be expected to exercise all the duties of an 153 IAOC member, including being prepared to undertake any associated 154 responsibilities, including the setting of administrative support 155 policies, oversight of the administrative operations of the IETF, 156 representing the interests of the IETF to the IAOC, and be able to 157 undertake full participation in all Committee meetings and Committee 158 activities. 160 In the case of the IAB-selected member of the IAOC, this individual 161 does not directly represent the IAB. Similarly for the IESG-selected 162 member of the IAOC, this individual does not directly represent the 163 IESG. The IAB and IESG selected members are accountable directly to 164 the IETF community. 166 3. IAB and IESG Selection Process of an IAOC member 168 3.1 Nominations and Eligibility 170 The IAB and IESG will alternate year by year in making a public call 171 for nominations on the ietf-announce@ietf.org mailing list. The 172 public call will specify the manner by which nominations will be 173 accepted and the means by which the list of nominees will be 174 published. 176 Self-nominations are permitted. Along with the name and contact 177 information for each candidate, details about the candidate's 178 background and qualifications for the position should be attached to 179 the nomination. All IETF participants, including working group 180 chairs, IETF Nominating Committee members, IAB and IESG members are 181 eligible for nomination. 183 IAB members who accept a nomination for an IAB-selected position will 184 recuse themselves from IAB selection discussions. Similarly, IESG 185 members who accept a nomination for an IESG-selected position will 186 recuse themselves from IESG selection discussions. 188 3.2 Selection 190 The selecting body will publish the list of nominated persons prior 191 to making a decision, allowing time for the community to pass any 192 relevant comments to that body. 194 The selecting body will review the nomination material, any submitted 195 comments, and make their selection. 197 3.3 Care of Personal Information 199 The following procedures will be used by the IAB and IESG in managing 200 candidates' personal information: 202 o The candidate's name will be published, with all other candidate 203 names, at the close of the nominations period. 205 o Except as noted above, all information provided to the IAB or IESG 206 during this process will be kept as confidential to that body. 208 3.4 Term of Office and Selection Timeframe 210 The IAB and IESG expect to seat their selected committee member at 211 the first IETF meeting of every second year, for a two year term of 212 office. The IAB and IESG will alternate each year in undertaking a 213 selection, except for the initial selection. For the first year the 214 IAB and IESG will operate their selection process concurrently. Also 215 for the first year the IESG-selected candidate will serve on the 216 committee for an initial term ending with the first IETF meeting of 217 the following year, and the IAB-selected candidate will serve for a 218 term one year longer than the IESG-selected candidate. Thereafter 219 the candidates will be seated for two year terms. 221 Basic time frame requirements for the selection process are as 222 follows: 224 o 2 - 3 weeks for solicitation of nominations. 226 o 3 - 4 weeks for review of nominees, deliberation and selection. 228 In November of every year, the selecting body of that year will 229 announce the specific dates for the selection process for that year, 230 following the guidelines above. 232 3.5 Mid-term Vacancies 234 This document describes the process for the general appointment of 235 IAB-selected and IESG-selected IAOC members. However, if the 236 appointed member is unable to serve the full two year term, the 237 selecting body may, at its discretion, immediately select a 238 replacement to serve the remainder of the term using the interim 239 process defined in Section 3.5.1. If the selecting body does not 240 invoke the interim process, the next biannual selection process will 241 fill the vacancy. 243 3.5.1 Interim Appointment Process 245 If the selecting body elects to fill the mid-term vacancy before the 246 next biannual selection, a separate time line will be announced and 247 the remainder of the process described in this document will be 248 followed. 250 4. Acknowledgements 252 This document is based extensively on RFC 3677 [RFC3677]. It has 253 benefited from helpful review comments from Harald Alvestrand, Brian 254 Carpenter Leslie Daigle, Rob Evans, Michael Patton and Margaret 255 Wasserman. 257 5. Informative References 259 [RFC3677] Daigle, L. and Internet Architecture Board, "IETF ISOC 260 Board of Trustee Appointment Procedures", BCP 77, 261 RFC 3677, December 2003. 263 [RFC4071] Austein, R. and B. Wijnen, "Structure of the IETF 264 Administrative Support Activity (IASA)", BCP 101, 265 RFC 4071, April 2005. 267 Authors' Addresses 269 Geoff Huston (editor) 271 Email: gih@apnic.net 272 Bert Wijnen (editor) 273 Internet Engineering Steering Group 275 Email: bwijnen@lucent.com 277 Appendix A. IAB Members 279 Internet Architecture Board members at the time this document was 280 drafted were: 282 Bernard Aboba 283 Loa Andersson 284 Brian Carpenter 285 Leslie Daigle 286 Patrik Faltstrom 287 Bob Hinden 288 Kurtis Lindqvist 289 David Meyer 290 Pekka Nikander 291 Eric Rescorla 292 Pete Resnick 293 Janathan Rosenberg 294 Lixia Zhang 296 Appendix B. IESG Members 298 Internet Engineering Steering Group members at the time this document 299 was drafted were: 301 Brian Carpenter 302 Bill Fenner 303 Ted Hardie 304 Sam Hartman 305 Scott Hollenbeck 306 Russell Housley 307 David Kessens 308 Allison Mankin 309 Mark Townsley 310 Jon Peterson 311 Margaret Wasserman 312 Bert Wijnen 313 Alex Zinin 315 Intellectual Property Statement 317 The IETF takes no position regarding the validity or scope of any 318 Intellectual Property Rights or other rights that might be claimed to 319 pertain to the implementation or use of the technology described in 320 this document or the extent to which any license under such rights 321 might or might not be available; nor does it represent that it has 322 made any independent effort to identify any such rights. Information 323 on the procedures with respect to rights in RFC documents can be 324 found in BCP 78 and BCP 79. 326 Copies of IPR disclosures made to the IETF Secretariat and any 327 assurances of licenses to be made available, or the result of an 328 attempt made to obtain a general license or permission for the use of 329 such proprietary rights by implementers or users of this 330 specification can be obtained from the IETF on-line IPR repository at 331 http://www.ietf.org/ipr. 333 The IETF invites any interested party to bring to its attention any 334 copyrights, patents or patent applications, or other proprietary 335 rights that may cover technology that may be required to implement 336 this standard. Please address the information to the IETF at 337 ietf-ipr@ietf.org. 339 Disclaimer of Validity 341 This document and the information contained herein are provided on an 342 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 343 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 344 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 345 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 346 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 347 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 349 Copyright Statement 351 Copyright (C) The Internet Society (2005). This document is subject 352 to the rights, licenses and restrictions contained in BCP 78, and 353 except as set forth therein, the authors retain all their rights. 355 Acknowledgment 357 Funding for the RFC Editor function is currently provided by the 358 Internet Society.