idnits 2.17.1 draft-rescorla-istar-recall-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 (May 16, 2019) is 1808 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 7437 (Obsoleted by RFC 8713) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group E. Rescorla 3 Internet-Draft Mozilla 4 Intended status: Informational M. StJohns 5 Expires: November 17, 2019 Consultant 6 May 16, 2019 8 Updated Recall Procedures for IETF Leadership 9 draft-rescorla-istar-recall-00 11 Abstract 13 This document proposes a new set of recall procedures for members of 14 the IESG and IAB. Instead of a revised nomcom process, these 15 procedures are based on the body expelling their own members. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on November 17, 2019. 34 Copyright Notice 36 Copyright (c) 2019 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (https://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3 53 3. Expulsion Procedure . . . . . . . . . . . . . . . . . . . . . 3 54 4. Effectiveness Date . . . . . . . . . . . . . . . . . . . . . 4 55 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 56 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 57 7. Normative References . . . . . . . . . . . . . . . . . . . . 4 58 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 60 1. Introduction 62 Section 7 of [RFC7437] describes a recall procedure for IAB and IESG 63 members. This procedure involves a petition from 20 nomcom-eligible 64 community members followed by the formation of a recall committee 65 using procedures similar to those of the nomcom. This procedure has 66 never been executed, although in at least one case the petition phase 67 got fairly far before the relevant member resigned. 69 One might draw a number of conclusions here, including: 71 o There is very little need for any kind of recall, except in the 72 most exceptional circumstances. 74 o The recall system is so unwieldy that it is undeployable even in 75 the most egregious cases. 77 This document takes the position that while recalls should be 78 relatively rare, some mechanism is needed, but that the current 79 mechanism is not well-constructed, both because it is hard to 80 initiate and because it is slow (partly by design), with the result 81 that it often seems easier to just wait for the next nomcom cycle. 82 In addition, because of the stochastic nature of the nomcom, it is a 83 potential source of abuse by those wishing to relitigate the past 84 nomcom. 86 This document proposes an alternate structure which is designed to 87 deal with just egregious cases (e.g., total member checkout, major 88 misconduct) but is also faster because it doesn't involve spinning up 89 the nomcom machinery (twice, once to recall and once to replace). In 90 this structure, the IAB/IESG would vote to expel the offending member 91 with consent from the other body. The rationale here is that the 92 body themselves is in the best position to know when a member really 93 needs to be removed. 95 The intent is that this be an alternative to the existing recall 96 procedure, thus preserving a community mechanism for removing 97 members. 99 2. Conventions and Definitions 101 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 102 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 103 "OPTIONAL" in this document are to be interpreted as described in BCP 104 14 [RFC2119] [RFC8174] when, and only when, they appear in all 105 capitals, as shown here. 107 3. Expulsion Procedure 109 In this model, any formal member of either the IAB or the IESG, with 110 the exception of the IETF chair, may be expelled by that body. 111 Specifically, for the IESG, this means all area directors other than 112 the IETF chair and for the IAB this means all IAB members other than 113 the IETF chair, liaisons, and ex officio members. 115 The body MAY use any procedures of its choice to debate the issue, 116 but the final vote MUST be by a 2/3 majority of the formal members 117 other than the affected member. Prior to that vote, the member MUST 118 be notified and have an opportunity to provide a statement to be 119 considered by the voting members. 121 Members MAY appeal their expulsion to the body which would ordinarily 122 confirm nomcom appointments (the IAB for IESG members and the ISOC 123 Board of Trustees for IAB members). This appeal MUST be filed within 124 7 days or the expulsion becomes effective. 126 In case of an appeal, the body proposing the expulsion shall send a 127 note to the confirming body explaining its reasons for the expulsion. 128 The member being proposed for expulsion shall have access to that 129 statement and shall be allowed to submit a statement explaining why 130 the expulsion should not be sustained. The member shall have 3 131 business days after receipt of the explusion statement to submit 132 their statement. 134 The confirming body shall complete their deliberations within one 135 calendar week of receiving the expulsion statement and response. If 136 the confirming body does not vote to confirm the expulsion by a 2/3 137 majority by the end of this deadline, the expulsion shall not be 138 sustained. 140 The contents of the statement on the reasons for expulsion shall be 141 held confidential by both bodies. However, the member being proposed 142 for expulsion in their sole discretion, MAY make their statement 143 public. 145 Deliberations and votes by both bodies - including the fact that 146 expulsion is being considered - shall be private (and among only the 147 members voting) and only the fact of a successful vote yea shall be 148 reported publicly. The number of votes for or against shall not be 149 reported. If at any time the member resigns from the position prior 150 to the completion of an appeal, the fact of the expulsion process 151 shall not be reported. 153 Upon either the expiration of the appeal period or an affirmative 154 vote by the confirming body, the expulsion takes effect immediately. 155 At this point, their seat is treated as a mid-term vacancy and 156 handled according to Section 3.5 of [RFC7437]. 158 If an expulsion vote is taken and fails and/or an expulsion is not 159 sustained by the confirming body, no expulsion of that member may be 160 proposed for 6 months after the initiation of the proceedings. 162 The Chair of the IETF may not be removed by expulsion. 164 4. Effectiveness Date 166 This process applies to members selected by Nomcoms after the 167 publication date of this document. 169 5. Security Considerations 171 This document introduces a new mechanism for removing IAB and IESG 172 members, so is a potential way to suppress existing views. 173 Supermajority requirements and the possibility of appeal limits the 174 impact of this. 176 6. IANA Considerations 178 This document has no IANA actions. 180 7. Normative References 182 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 183 Requirement Levels", BCP 14, RFC 2119, 184 DOI 10.17487/RFC2119, March 1997, 185 . 187 [RFC7437] Kucherawy, M., Ed., "IAB, IESG, and IAOC Selection, 188 Confirmation, and Recall Process: Operation of the 189 Nominating and Recall Committees", BCP 10, RFC 7437, 190 DOI 10.17487/RFC7437, January 2015, 191 . 193 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 194 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 195 May 2017, . 197 Authors' Addresses 199 Eric Rescorla 200 Mozilla 202 Email: ekr@rtfm.com 204 Michael StJohns 205 Consultant 207 Email: mstjohns@comcast.net