Re: I-D Action: draft-hardie-iaoc-iab-update-00.txt

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 11 February 2016 05:21 UTC

Return-Path: <spencerdawkins.ietf@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 BFD8B1A8F41 for <ietf@ietfa.amsl.com>; Wed, 10 Feb 2016 21:21: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 hinCBa80s7hm for <ietf@ietfa.amsl.com>; Wed, 10 Feb 2016 21:21:00 -0800 (PST)
Received: from mail-yk0-x22e.google.com (mail-yk0-x22e.google.com [IPv6:2607:f8b0:4002:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 335081A8F44 for <ietf@ietf.org>; Wed, 10 Feb 2016 21:21:00 -0800 (PST)
Received: by mail-yk0-x22e.google.com with SMTP id z7so16898577yka.3 for <ietf@ietf.org>; Wed, 10 Feb 2016 21:21:00 -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=UVwpqUg0hhPX5covPsxHdcl1s7ecIghl9TIQdvPmbSk=; b=zf3zzNDlwhysm+kudLi1cXCDcah+hXX+OWc9Mgi5FDoxxeUQLueq0BR4ztanrFQjx4 YiOthPSn1hvDvMdqj94V6d5j3EGCtBpv0BZvCaeF59cLeLd/+jnxuncKyttjsf7Tu0VQ BAzeVypqj0B0F2EgLzj75dWBj8DlqKjRl6flGfp5owV7kfBE9DaHCXuDvsvapdOkILao ++OMHOsdQd6u4+OFYtrk3XpkDchOD36EMTw6+HSA3r4GcKzEiEiPfAdTCI7vOXxYSbHH /M7C4Dqi0UgssLlPZzmQdCP9wIimsJ2LkkOp5xVIdZ7+i7c+KbNMq0zeq3MsHJy5zS5f IL4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=UVwpqUg0hhPX5covPsxHdcl1s7ecIghl9TIQdvPmbSk=; b=dqtTSnvle2ndq93E/eVuh3tbmDZGfu8K2rYOYXQ5iCxfgXIPa1H5rvjq3/mQv1Xz6i tuH+Z2HgEuHznoDvzaDVNN6JAcyVS5pRXsirj9gIAmS7ZmK1O+86UG1PiJMFIIAAc4wZ 2TCgChtnvCCZFcvogPs1R3BOOFI9X9PAN4Q93akO65Qe4DadrQS3PpPsfYfgY69XoFVt vHwrur4ObBZBp/JJ5Cys32IxW7IiUdiklLH/qSBdiEXlx+0kCdZ+1Vtvf+/cs042g07t 9YKZtc/uTkg7TUxGc+BZJg6PHgf3LUOciSwozvIv76LweuPF3fQTix/BJCPBC9N5evPU amjg==
X-Gm-Message-State: AG10YOTF36LsjYZHOGCXnlxddaUfsT0Zcms8kDk3FdvEl78l9FDHl1hxnmW65ej+4+SW9EKyxgZw4ytXl82cPA==
MIME-Version: 1.0
X-Received: by 10.37.29.193 with SMTP id d184mr23669145ybd.111.1455168059526; Wed, 10 Feb 2016 21:20:59 -0800 (PST)
Received: by 10.37.99.65 with HTTP; Wed, 10 Feb 2016 21:20:59 -0800 (PST)
In-Reply-To: <CAC4RtVBrtxyro+2EOSAOop7xDr-z7xu97kuVzPzaFoBzj_5jTg@mail.gmail.com>
References: <20160202182036.26498.27650.idtracker@ietfa.amsl.com> <56B10131.7040603@gmail.com> <C8F5EEE2CF0CBC7E3BB44477@JcK-HP8200.jck.com> <56B12368.2070609@comcast.net> <CAC4RtVBrtxyro+2EOSAOop7xDr-z7xu97kuVzPzaFoBzj_5jTg@mail.gmail.com>
Date: Wed, 10 Feb 2016 23:20:59 -0600
Message-ID: <CAKKJt-fryazj5EXuYyQ4hQgzTMVbyYhUuR_rcRE7zWkrUCzwVQ@mail.gmail.com>
Subject: Re: I-D Action: draft-hardie-iaoc-iab-update-00.txt
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary="001a1142789046d9f0052b77b71f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/0PXW4NOW9DIOmuU6KJJxEY2mDKE>
Cc: IETF discussion list <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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 11 Feb 2016 05:21:02 -0000

I'm agreeing with Barry, with one addition ...

On Wed, Feb 10, 2016 at 9:46 PM, Barry Leiba <barryleiba@computer.org>
wrote:

> > Let me suggest that instead of delegating the IAB chair responsibilities
> we,
> > instead, change the ex-officio status that the various chairs currently
> have
> > to observer status, change the organizational appointees to permit
> > (require?) appointment from their appointing organizations, and  also add
> > two or three additional permanent members to the IAOC, those members to
> be
> > selected in alternate years by the Nomcom.
>
> First, I think it would be entirely reasonable to add two voting
> members to the IAOC for a couple of reasons:
>
> 1. Temporary absences will be less disruptive.  I'm not sure how much
> of an issue that has actually been on the IAOC, though, so I don't
> know how important this is.
>
> 2. Adding two NomCom-selected voting members would increase the pool
> of potential IAOC chairs to seven (from five).  Making sure there's
> someone on the IAOC who is eligible to chair, willing to chair, and
> capable of chairing is sometimes a difficult issue now.
>
> Now, a variant here:
> In addition to that, the IESG has chatted in the past about ceding its
> appointment to the NomCom, and there was significant support in the
> IESG for such a move (which, yes, would require updating RFC 4071).
> Our thought in the discussion was twofold:
>
> 1. RFC 4071 explicitly says that we are not appointing an IAOC member
> to represent the IESG in any way: we're making the appointment, and
> the IAB is making theirs, but once the appointments are made those
> members act in the same way as the NomCom-appointed ones.
>
> 2. The idea that the IESG should have its own appointment because it
> will look at the candidates differently and will pick with different
> criteria than the NomCom would is valid in theory, but has little or
> no applicability in practice.  In many ways, it would be better to let
> the NomCom balance its choices while selecting two (or even three)
> IAOC members at the same time.
>
> There could be one difficulty: If we were to move both the IESG and
> IAB appointments to the NomCom *and* add two new NomCom appointments,
> the NomComs would be selecting three IAOC members each year.  Finding
> suitable candidates would be a challenge.  A big one.  On the other
> hand, the IESG's list of candidates usually includes the incumbent and
> the volunteers that the NomCom didn't select, so, again, there isn't a
> real change there in practice.


I'm remembering being on either the IESG or the IAB during a race condition
with Nomcom because the volunteer lists overlapped significantly (as in,
all but one person under consideration were on both lists), and whichever
body I was on was holding up naming its appointee because we didn't know
who Nomcom was going to pick, and we couldn't ask. We really were
duplicating almost all of Nomcom's work, and the people willing to serve
were filling out two sets of questionnaires which, I suspect, included a
lot of information requested in both places.

So I'm thinking "no real change in practice" is even more true.

Spencer

p.s. I note that if you're on Nomcom, selecting candidates for confirmation
is your only responsibility, while if you're on either the IAB or IESG,
it's competing with other responsibilities, but perhaps other folk
multi-task better than I do ...