idnits 2.17.00 (12 Aug 2021) /tmp/idnits37698/draft-hardie-iaoc-iab-update-00.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 02, 2016) is 2300 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 (~~), 1 warning (==), 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 Intended status: Best Current Practice A. Sullivan 5 Expires: August 5, 2016 Dyn 6 R. Housley 7 Vigil Security 8 February 02, 2016 10 Updating the ex-officio member of the IAB in the IAOC 11 draft-hardie-iaoc-iab-update-00 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 ex officio member from the IAB who serves on the 19 IAOC in order to better account for that change and better match the 20 skills set out in RFC 4333. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on August 5, 2016. 39 Copyright Notice 41 Copyright (c) 2016 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 1. Introduction 56 At the time of the administrative restructuring of the IETF which 57 gave rise to the IAOC[RFC4071], the IAB made very little use of long- 58 lived programs. In part because of the adjustments to the RFC Editor 59 model[RFC6635], the IAB now makes extensive use of such programs, and 60 the IAB structures much of its long-lived efforts as programs. This 61 document proposes to set up one such program, and to have the IAB 62 member that leads that program serve as the IAB's ex officio member 63 of the IAOC instead of the IAB chair serving in this role. 65 2. IAOC Review Program Structure 67 While many IAB programs include invited experts, the intent is for 68 this program to be composed of a small number of sitting IAB members, 69 possibly including the Executive Director, if one has been appointed. 71 The program members will be responsible to review all public 72 correspondence of the IAOC to the community. This would include 73 reviews of requests for proposals at that point at which they are 74 made public, along with the public minutes of the IAOC meetings and 75 any other reports which the IAOC may be produced. 77 In addition, the IAB shall designate one sitting IAB member to serve 78 as program lead. The program lead shall act as the ex officio as a 79 member of the IAOC, as the IAB chair does now. Other program members 80 are available to advise the ex officio IAB member of the IAOC, should 81 the member request it. 83 Note that the ex officio member also serves as a Trustee of the IETF 84 Trust, since its members are defined as being the members of the 85 IAOC. 87 3. Reasoning 89 While there are clearly advantages to having a single individual 90 share state as IAB Chair, IESG member, and IAOC member, this also 91 weighs significantly on the time of the selected individual. Moving 92 one or more responsibilities into other forums is one approach to 93 mitigating the burden on a single individual. 95 Given that the program structure has worked well in other contexts to 96 manage the work of the IAB, adapting it to this purpose seems a 97 logical approach to adjusting the current working methods. Having a 98 dedicated set of reviewers for RFPs, minutes, and other 99 correspondence will also increase the input provided to the IAOC and 100 the understanding of that state in the IAB as a whole. 102 This also allows the IAB to select from among its members the 103 individual who best matches the criteria set out in IOAC member 104 selection guidelines[RFC4333] while simultaneously serving on one of 105 the IAOC's customer organizations. This might be a different person 106 than the person best able to carry the other duties of the IAB Chair. 107 Should it happen that the IAB Chair is also the best person to serve 108 on the IAOC, then the IAB Chair may serve as lead of the program. 110 4. Security Considerations 112 This document describes an administrative change rather than a 113 protocol. There is a possibility that this administrative change 114 might result in less information flowing between the IAB and IAOC, 115 but the existence of a larger program mitigates this risk. 117 5. IANA Considerations 119 This document currently has no actions for IANA. 121 6. Acknowledgements 123 Olaf Kolkman was kind enough to review and provide suggestions to an 124 early version of this document. 126 7. References 128 7.1. Normative References 130 [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the 131 IETF Administrative Support Activity (IASA)", BCP 101, 132 RFC 4071, DOI 10.17487/RFC4071, April 2005, 133 . 135 7.2. Informative References 137 [RFC4333] Huston, G., Ed. and B. Wijnen, Ed., "The IETF 138 Administrative Oversight Committee (IAOC) Member Selection 139 Guidelines and Process", BCP 113, RFC 4333, 140 DOI 10.17487/RFC4333, December 2005, 141 . 143 [RFC6635] Kolkman, O., Ed., Halpern, J., Ed., and IAB, "RFC Editor 144 Model (Version 2)", RFC 6635, DOI 10.17487/RFC6635, June 145 2012, . 147 Authors' Addresses 149 Ted Hardie 151 Email: ted.ietf@gmail.com 153 Andrew Sullivan 154 Dyn 156 Email: asullivan@dyn.com 158 Russ Housley 159 Vigil Security 161 Email: housley@vigilsec.com