Updated Recall Procedures for IETF Leadership
draft-rescorla-istar-recall-00

Document Type Active Internet-Draft (individual)
Last updated 2019-05-16
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        E. Rescorla
Internet-Draft                                                   Mozilla
Intended status: Informational                                M. StJohns
Expires: November 17, 2019                                    Consultant
                                                            May 16, 2019

             Updated Recall Procedures for IETF Leadership
                     draft-rescorla-istar-recall-00

Abstract

   This document proposes a new set of recall procedures for members of
   the IESG and IAB.  Instead of a revised nomcom process, these
   procedures are based on the body expelling their own members.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on November 17, 2019.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Rescorla & StJohns      Expires November 17, 2019               [Page 1]
Internet-Draft                 New Recall                       May 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   3.  Expulsion Procedure . . . . . . . . . . . . . . . . . . . . .   3
   4.  Effectiveness Date  . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   Section 7 of [RFC7437] describes a recall procedure for IAB and IESG
   members.  This procedure involves a petition from 20 nomcom-eligible
   community members followed by the formation of a recall committee
   using procedures similar to those of the nomcom.  This procedure has
   never been executed, although in at least one case the petition phase
   got fairly far before the relevant member resigned.

   One might draw a number of conclusions here, including:

   o  There is very little need for any kind of recall, except in the
      most exceptional circumstances.

   o  The recall system is so unwieldy that it is undeployable even in
      the most egregious cases.

   This document takes the position that while recalls should be
   relatively rare, some mechanism is needed, but that the current
   mechanism is not well-constructed, both because it is hard to
   initiate and because it is slow (partly by design), with the result
   that it often seems easier to just wait for the next nomcom cycle.
   In addition, because of the stochastic nature of the nomcom, it is a
   potential source of abuse by those wishing to relitigate the past
   nomcom.

   This document proposes an alternate structure which is designed to
   deal with just egregious cases (e.g., total member checkout, major
   misconduct) but is also faster because it doesn't involve spinning up
   the nomcom machinery (twice, once to recall and once to replace).  In
   this structure, the IAB/IESG would vote to expel the offending member
   with consent from the other body.  The rationale here is that the
   body themselves is in the best position to know when a member really
   needs to be removed.

Rescorla & StJohns      Expires November 17, 2019               [Page 2]
Internet-Draft                 New Recall                       May 2019

   The intent is that this be an alternative to the existing recall
   procedure, thus preserving a community mechanism for removing
   members.

2.  Conventions and Definitions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
Show full document text