Re: Updating BCP 10 -- NomCom

Allison Mankin <allison.mankin@gmail.com> Fri, 09 January 2015 19:27 UTC

Return-Path: <allison.mankin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFFA91A9252 for <ietf@ietfa.amsl.com>; Fri, 9 Jan 2015 11:27:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VYUO6v3RjkZq for <ietf@ietfa.amsl.com>; Fri, 9 Jan 2015 11:27:00 -0800 (PST)
Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E1DE1A0089 for <ietf@ietf.org>; Fri, 9 Jan 2015 11:27:00 -0800 (PST)
Received: by mail-qg0-f48.google.com with SMTP id j5so10469052qga.7 for <ietf@ietf.org>; Fri, 09 Jan 2015 11:26:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=b/pwHT8bPxU1urCY/onykoGnVzxG3a7ETT2goEClWd8=; b=Vu9lLgqjnRYTr2QLkYIHRlcFeCXnV+nfCBFB28GzPRlOK42w0JP5kyBiMTlRvrsqpB /GWlqB9zrZntcQzAKM926wC+p64G/EH6LnzLaanO8G1X/PxmYgw3S91ZBVFHFrg6JO6j +b9AzaL6e0DH77pCiit2ADAlv3AVVDU0OS0rEZUk4UEtRhqBhG6yAAQg2s9wYnfIOech 0w6yqu0nvxOrmTG+NKxnx6OBfx3P5vDHA46AhZkVqcplEapNrIKJfNH9Qgoym5mprPNf YL7JW6j2gwny/eo3/ICvth++g8wUTJCBDedjXwgLPZaRZbxNyFso2sbGjnBquWJuVP+G 7rbg==
MIME-Version: 1.0
X-Received: by 10.140.21.229 with SMTP id 92mr28328387qgl.33.1420831619699; Fri, 09 Jan 2015 11:26:59 -0800 (PST)
Received: by 10.96.144.71 with HTTP; Fri, 9 Jan 2015 11:26:59 -0800 (PST)
In-Reply-To: <12811.1420831053@sandelman.ca>
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <CAP8yD=uky=fbJNA5KjCSk3q+u036++c+pnR_3inmvnOECxRRKA@mail.gmail.com> <12811.1420831053@sandelman.ca>
Date: Fri, 9 Jan 2015 14:26:59 -0500
Message-ID: <CAP8yD=t5wbONu=TRDXap6oDk-btyx4zLKENsoeeMgbSs9hq2+g@mail.gmail.com>
Subject: Re: Updating BCP 10 -- NomCom
From: Allison Mankin <allison.mankin@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=001a11c12f8cfa5bb6050c3d2377
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/6pj2T7rvcCLAiQePestGnGpVyEA>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Jan 2015 19:27:02 -0000

On 9 January 2015 at 14:17, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Allison Mankin <allison.mankin@gmail.com> wrote:
>     > 1. Improved transition for Chairs - my thought is to add a Future
> Chair
>     > early so that she or he can observe.  Right now we've been tending
>     > mainly to select as Chairs people who were recently Nomcom members.
> My
>
> Oh, yes, we almost forgot: we need a turn-over ceremony at the "Second
> meeting"
> (probably should be the Admin plenary), when the new nomcom is now
> *CLEARLY*
> responsible for any open positions.


> This is also when the past nomcom-chair and committee members can
> completely
> and irrevocably destroy any private keys and notes they might have kept,
> and the secretariat can remove any email aliases that might be around and
> might get autocompleted.

​​


>
> I don't know if this needs to go into 7437, but it needs to written down.
>
​Agreed and I think at least some of it should be in the BCP - it's part of
the workflow.
​


>
>     > 2. During my tenure we had to invoke the thoughtful BCP 10 allowance
> to
>     > operate with 9 members rather than 10, because one of our members
>     > became permanently unavailable.  We had some risk of losing another
>     > late in the game as well, and I think this is always a risk.
> Therefore
>     > I'd like to see the addition of one warm spare, selected during the
>     > random draw, who joins meetings, observes, conceivably helps with
>     > interviewing, and is available quickly to participate if there is a
>
> We discussed drawing the name, but I didn't know you anticipating them
> joining too...  I'm thinking about this.
>

I hadn't thought about them not joining :-) They could be a cold spare,
that'd serve too.
In either case, just drawing the person wouldn't be enough - that spare
person would have
to be publicly announced and verified by the various folks who check and
verify the random process.