idnits 2.17.00 (12 Aug 2021) /tmp/idnits63981/draft-hardie-iaoc-iab-update-02.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 18, 2016) is 2277 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 normative reference: RFC 3777 (Obsoleted by RFC 7437) -- Obsolete informational reference (is this intentional?): RFC 4333 (Obsoleted by RFC 8711) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Hardie 3 Internet-Draft A. Sullivan 4 Updates: RFC4071 (if approved) Dyn 5 Intended status: Best Current Practice R. Housley 6 Expires: August 19, 2016 Vigil Security 7 February 18, 2016 9 Updating the ex officio member of the IAB in the IAOC 10 draft-hardie-iaoc-iab-update-02 12 Abstract 14 This document updates the way in which the ex officio member from the 15 IAB who serves on the IAOC is appointed in order to better match the 16 skills set out in RFC 4333. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on August 19, 2016. 35 Copyright Notice 37 Copyright (c) 2016 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents (http://trustee.ietf.org/ 42 license-info) in effect on the date of publication of this document. 43 Please review these documents carefully, as they describe your rights 44 and restrictions with respect to this document. Code Components 45 extracted from this document must include Simplified BSD License text 46 as described in Section 4.e of the Trust Legal Provisions and are 47 provided without warranty as described in the Simplified BSD License. 49 1. Introduction 51 [RFC4071] describes the membership of the IAOC and assigns two roles 52 to the Internet Architecture Board: appointing a member from the 53 community and providing a member from the IAB. The ex officio member 54 provided by the IAB is currently required to be the IAB Chair. 55 [RFC4333] sets out selection guidelines for members of the IAOC. 56 This document proposes an update to RFC 4071 to allow a different IAB 57 member to serve, in order to better meet the criteria set out in RFC 58 4333. 60 2. Proposed change 62 This document proposes to allow the IAB to select from among its 63 members the individual who best matches the criteria set out in IAOC 64 member selection guidelines RFC 4333. This might be a different 65 person than the person best able to carry out the other duties of the 66 IAB Chair. Should it happen that the IAB Chair is also the best 67 person to serve on the IAOC, then the IAB Chair may serve; it is 68 simply no longer required. 70 The individual named by the IAB will serve a renewable one year term, 71 subject to the recall of the IAB by the same means the IAB chair is 72 removed (an affirmative vote of two-thirds of the IAB). All IAB 73 members are also subject to recall under the terms of [RFC3777]. 75 Given the nature of the IAOC responsibilities, it is advantageous 76 that the appointment of an IAB member to the IAOC be approximately as 77 stable as the appointment of the IAB chair. 79 The resulting changes to RFC 4071 are: 81 In section 4, where the document on membership currently says "The 82 IAB Chair (ex officio);", we propose "An IAB member designated for a 83 one-year term." 85 3. Security Considerations 87 This document describes an administrative change rather than a 88 protocol. 90 4. IANA Considerations 92 This document currently has no actions for IANA. 94 5. Acknowledgements 96 Olaf Kolkman was kind enough to review and provide suggestions to an 97 early version of this document. Lou Berger, Brian Carpenter, Leslie 98 Daigle, Martin Duerst, Bob Hinden, John Klensin, Mike St. Johns, and 99 Suzanne Woolf provided additional comments on version 1. 101 6. References 103 6.1. Normative References 105 [RFC4071] Austein, R.Ed., and B. Wijnen, Ed., "Structure of the 106 IETF Administrative Support Activity (IASA)", BCP 101, RFC 107 4071, DOI 10.17487/RFC4071, April 2005, . 110 [RFC3777] Galvin, J., Ed., "IAB and IESG Selection, Confirmation, 111 and Recall Process: Operation of the Nominating and Recall 112 Committees", RFC 3777, DOI 10.17487/RFC3777, June 2004, 113 . 115 6.2. Informative References 117 [RFC4333] Huston, G.Ed., and B. Wijnen, Ed., "The IETF 118 Administrative Oversight Committee (IAOC) Member Selection 119 Guidelines and Process", BCP 113, RFC 4333, DOI 10.17487/ 120 RFC4333, December 2005, . 123 Authors' Addresses 125 Ted Hardie 127 Email: ted.ietf@gmail.com 129 Andrew Sullivan 130 Dyn 132 Email: asullivan@dyn.com 134 Russ Housley 135 Vigil Security 137 Email: housley@vigilsec.com