idnits 2.17.00 (12 Aug 2021) /tmp/idnits38039/draft-hardie-iaoc-iab-update-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 05, 2016) is 2297 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4071 (Obsoleted by RFC 8711) -- Obsolete informational reference (is this intentional?): RFC 4333 (Obsoleted by RFC 8711) -- Obsolete informational reference (is this intentional?): RFC 6635 (Obsoleted by RFC 8728) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Hardie 3 Internet-Draft 4 Updates: RFC4071 (if approved) A. Sullivan 5 Intended status: Best Current Practice Dyn 6 Expires: August 8, 2016 R. Housley 7 Vigil Security 8 February 05, 2016 10 Updating the ex officio member of the IAB in the IAOC 11 draft-hardie-iaoc-iab-update-01 13 Abstract 15 At the time the IETF Administrative Oversight Committee was set up 16 the Internet Architecture Board had an internal structure 17 significantly different from its current structure. This document 18 aims to update the way in which the ex officio member from the IAB 19 who serves on the IAOC is appointed, in order to better account for 20 that change and better match the skills set out in RFC 4333. After 21 community discussion, it is likely that this document will be split 22 into two distinct parts: one which updates the IAOC membership 23 section of the relevant BCP and another which describes the IAB's 24 program. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on August 8, 2016. 43 Copyright Notice 45 Copyright (c) 2016 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 1. Introduction 60 At the time of the administrative restructuring of the IETF which 61 gave rise to the IAOC, the IAB made very little use of long-lived 62 programs. In part because of the adjustments to the RFC Editor 63 model[RFC6635], the IAB now makes extensive use of such programs, and 64 the IAB structures much of its long-lived efforts as programs. This 65 document proposes to set up one such program and to have the IAB 66 member that leads that program serve as the IAB's ex officio member 67 of the IAOC instead of the IAB chair serving in this role. 69 2. IAOC Review Program Structure 71 While many IAB programs include invited experts, the intent is for 72 this program to be composed of a small number of sitting IAB members, 73 possibly including the Executive Director, if one has been appointed. 75 The IAB shall designate one sitting IAB member to serve as program 76 lead. The program lead shall act as the ex officio as a member of 77 the IAOC, as the IAB chair did under Section 4 of [RFC4071]. 79 Other program members will be available to advise the ex officio IAB 80 member of the IAOC, should the member request it. In order to 81 provide that advice, program members will keep up to date on all 82 public correspondence of the IAOC to the community. This will 83 include reviewing public minutes of the IAOC meetings, any reports 84 produced by the IAOC, and any requests for proposals which have been 85 made public. 87 Note that the ex officio member also serves as a Trustee of the IETF 88 Trust, since its members are defined as being the members of the 89 IAOC. 91 3. Reasoning 93 While there are clearly advantages to having a single individual 94 share state as IAB Chair, IESG member, and IAOC member, this also 95 weighs significantly on the time of the selected individual. Moving 96 one or more responsibilities into other forums is one approach to 97 mitigating the burden on a single individual. 99 Given that the program structure has worked well in other contexts to 100 manage the work of the IAB, adapting it to this purpose seems a 101 logical approach to adjusting the current working methods. Having a 102 dedicated set of reviewers for RFPs, minutes, and other 103 correspondence will also increase the input provided to the IAOC and 104 the understanding of that state in the IAB as a whole. 106 This also allows the IAB to select from among its members the 107 individual who best matches the criteria set out in IOAC member 108 selection guidelines[RFC4333] while simultaneously serving on one of 109 the IAOC's customer organizations. This might be a different person 110 than the person best able to carry out the other duties of the IAB 111 Chair. Should it happen that the IAB Chair is also the best person 112 to serve on the IAOC, then the IAB Chair may serve as lead of the 113 program. 115 4. Security Considerations 117 This document describes an administrative change rather than a 118 protocol. There is a possibility that this administrative change 119 might result in less information flowing between the IAB and IAOC, 120 but the existence of a larger program mitigates this risk. 122 5. IANA Considerations 124 This document currently has no actions for IANA. 126 6. Acknowledgements 128 Olaf Kolkman was kind enough to review and provide suggestions to an 129 early version of this document. Lou Berger, Brian Carpenter, Leslie 130 Daigle, Martin Duerst, Bob Hinden, John Klensin, and Mike St. Johns 131 provided additional comments. 133 7. References 135 7.1. Normative References 137 [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the 138 IETF Administrative Support Activity (IASA)", BCP 101, 139 RFC 4071, DOI 10.17487/RFC4071, April 2005, 140 . 142 7.2. Informative References 144 [RFC4333] Huston, G., Ed. and B. Wijnen, Ed., "The IETF 145 Administrative Oversight Committee (IAOC) Member Selection 146 Guidelines and Process", BCP 113, RFC 4333, 147 DOI 10.17487/RFC4333, December 2005, 148 . 150 [RFC6635] Kolkman, O., Ed., Halpern, J., Ed., and IAB, "RFC Editor 151 Model (Version 2)", RFC 6635, DOI 10.17487/RFC6635, June 152 2012, . 154 Authors' Addresses 156 Ted Hardie 158 Email: ted.ietf@gmail.com 160 Andrew Sullivan 161 Dyn 163 Email: asullivan@dyn.com 165 Russ Housley 166 Vigil Security 168 Email: housley@vigilsec.com