IETF Logo Mail Archive

Re: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice

Barry Leiba <barryleiba@computer.org> Fri, 28 September 2012 00:38 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED08321F8441 for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 17:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.067
X-Spam-Level:
X-Spam-Status: No, score=-103.067 tagged_above=-999 required=5 tests=[AWL=-0.090, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tUQKHghLMFd8 for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 17:38:38 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 11A3F21F8442 for <ietf@ietf.org>; Thu, 27 Sep 2012 17:38:37 -0700 (PDT)
Received: by bkcjc3 with SMTP id jc3so2739607bkc.31 for <ietf@ietf.org>; Thu, 27 Sep 2012 17:38:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=PTUFvgNGvfKvW2UPPHgcPuO30RrHMF46mdGkSQbceIs=; b=m/BiyhddwnDGnUyMnA9gRzcb6QLfulMQCetoiAB6aPZ4cyPpLto1IXXVr+HFALFwPq iVDiciA+C6T69x+QNyLK/0t8I2Rvlvl44MoRjFA9H1SBVmk+gfM0JmbHNfzk5JmTnVPA zQkSZ8TX2DrEtJvONXey3StgDpZwt0JSQJYWh5Ymz3WSMnHhm9LYAUIyGkcYUkSBAfz3 sK4B2np3Ay3djR5l0CeBlgKnA/SjMcMXzpKV0GY+i2GjgPdc8QgQZwszuhvQzF7XKZ2r w0fuOOhGuMWQvWlyFDYjqH0kXrt+xi/cySdPkRYErzQqTL6RgbHreEeRZi4I+1do90+y 68ew==
MIME-Version: 1.0
Received: by 10.152.48.111 with SMTP id k15mr4632122lan.17.1348792716808; Thu, 27 Sep 2012 17:38:36 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.91.33 with HTTP; Thu, 27 Sep 2012 17:38:36 -0700 (PDT)
In-Reply-To: <8098D3F7-A030-49F0-ADBC-EE2F2F360D15@vigilsec.com>
References: <20120927150522.9680.50930.idtracker@ietfa.amsl.com> <8098D3F7-A030-49F0-ADBC-EE2F2F360D15@vigilsec.com>
Date: Thu, 27 Sep 2012 20:38:36 -0400
X-Google-Sender-Auth: KPdSSDDCwKjmGHTH7vv2pk_0lCM
Message-ID: <CAC4RtVA4xNndP=ok7DzoZJRz14Ox8q7yCh57wwcUoS6QGHpf1Q@mail.gmail.com>
Subject: Re: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice
From: Barry Leiba <barryleiba@computer.org>
To: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Sep 2012 00:38:39 -0000

> RFC 3777 says:
>
>    Member Recall: This is the process by which the behavior of a sitting
>       member of the IESG or IAB may be questioned, perhaps resulting in
>       the removal of the sitting member.
>
> The community should also be able to recall an IAOC member.

As Dave says, that alters the scope of the document:
The version that SM and I worked on jointly *did* include more changes
related to the IAOC (and it still didn't try to touch recall).  But
you asked that we trim it back to my original proposal to keep it
simple, and to avoid a lot of involved discussion.  If we add the
recall bit, there's a lot more that we'd really have to add, and I
don't think we want to do that.  It's not clear at all that we simply
want to lump the IAOC recall process in with the others.

For example, all IAB and IESG members are appointed by NomCom, while
only two IAOC members are; do we want the recall process to apply to
all IAOC members, or only the NomCom-appointed ones?  Maybe it should
be all, or maybe only the body that appointed them should be able to
remove them.  Whichever we decide, it's not just a simple matter of
adding another sentence into the draft.

I recommend that we don't go there in this document, and address that
issue in a more comprehensive update later.

Barry

v2.23.0 | Report a Bug | By Email