Re: [ietf-nomcom] BCP 10 Update, adding an IAOC Advisor to the Nominating Committee

John C Klensin <john-ietf@jck.com> Thu, 24 August 2017 21:49 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf-nomcom@ietfa.amsl.com
Delivered-To: ietf-nomcom@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07E051323B5 for <ietf-nomcom@ietfa.amsl.com>; Thu, 24 Aug 2017 14:49:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 F7HuC2NvDUrZ for <ietf-nomcom@ietfa.amsl.com>; Thu, 24 Aug 2017 14:49:00 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7577126BFD for <ietf-nomcom@ietf.org>; Thu, 24 Aug 2017 14:49:00 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dkzzm-000F5E-Ni; Thu, 24 Aug 2017 17:48:58 -0400
Date: Thu, 24 Aug 2017 17:48:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
cc: NomCom-Discussion <ietf-nomcom@ietf.org>
Message-ID: <84754C020045513D2990D80F@PSB>
In-Reply-To: <CAKKJt-crXRBdu2+vVzuptk-rknTFsHCg=xhPM6YqsD-e=7_7dw@mail.gmail.com>
References: <CAKKJt-cd2-tS=3QnvRcsDKcZ8=o5Z98wUr-=tp8OeP9J1M0M8g@mail.gmail.com> <4622.1502292425@obiwan.sandelman.ca> <CAKKJt-fxhFnnK3T2nVj2bD=Ve7z6L0oJFjYFqBb59TusJDwFzQ@mail.gmail.com> <1250df52-b5b3-4f71-bab1-790d156af1e9@nostrum.com> <5f26388a-93aa-7133-6973-de669a9bb2f4@gmail.com> <CAA=duU2hn-6=OzvZrfuz0agvzxvV0euXP4nsnjdksUpsnAyfJQ@mail.gmail.com> <CAKKJt-chkcrJRfCU1_MHb47H7GZNHafkbwVZKNsxh2pQzXyiYA@mail.gmail.c om> <6e62d88a-ba0e-18eb-3a45-88851b6e7c46@joelhalpern.com> <CAKKJt-dJ2Z1wsqXveg7+PR13d2bH61pHR753gEamwqWv4f+hKQ@mail.gmail.com> <0c83a20d-325b-d928-a157-638fcaf81adf@cs.tcd.ie> <CAKKJt-dsUt-bwtFiDY3Lek52QnmJT6z4O9+Bv3Py1He1vMW3-A@mail.gmail.com> <2e2ecf8a-e843-795b-f96b-b183e2b3a84c@cs.tcd.ie> <CAKKJt-crXRBdu2+vVzuptk-rknTFsHCg=xhPM6YqsD-e=7_7dw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/eT99RnU5z_aViWuB842lp3bR0z8>
Subject: Re: [ietf-nomcom] BCP 10 Update, adding an IAOC Advisor to the Nominating Committee
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-nomcom/>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Aug 2017 21:49:03 -0000


--On Thursday, August 24, 2017 16:01 -0500 Spencer Dawkins at
IETF <spencerdawkins.ietf@gmail.com> wrote:

> Second, and more important than it should be, the reason the
> past Nomcom didn't ask for a liaison from IAOC was because
> it's not part of https://tools.ietf.org/html/rfc7437, and the
> past chair/advisor didn't think of it, because he had not
> reviewed an IAOC position and hadn't asked for a liaison when
> he was chair. So, if a Nomcom doesn't have an IAOC advisor
> because they're not reviewing an IAOC position, our running
> code is that it's easy to forget to ask for one when a Nomcom
> does review an IAOC position ;-)
> 
> Let me chew on how I can say that Nomcoms really need that
> input, but what I'm concerned about is that a Nominating
> Committee is defined as
> 
>    The nominating committee comprises at least a Chair, 10
> voting    volunteers, two liaisons, and an advisor.
> 
> and if I state having an IAOC advisor is a (new) requirement,
> a Nominating Committee that doesn't have one would be
> vulnerable to an appeal to the ISOC board, because the
> structure doesn't match what's in the BCP - and because we're
> talking about IASA 2.0, sending a representative for IAOC may
> not even make sense, but the BCP text wouldn't go away by
> itself (BCP text that could go away by itself was the point of
> https://tools.ietf.org/html/rfc3933, but whatever).
> 
> I may be excessively sensitive about making this prescriptive,
> because we had to write a new BCP to make a one-word change in
> a couple of BCPs, so I'm happy to listen to reason.
> 
> Spencer, (in this case) as author of
> https://tools.ietf.org/html/rfc7475, which was less simple
> than you might hope ...
>...

Spencer, noting the concerns I expressed in my earlier note,
consider saying, instead of, "there will be an IAOC Liaison" (or
helper, observer, hanger-on) something like "before starting its
work to filter and select candidates, the Nomcom will consider
which bodies from which to seek advice or representation with
that consideration including, but not necessarily limited to,
all bodies to which Nomcoms are charged with appointing members
whether members are being appointed in that year or not".  That
consideration process will include the precise role of any
individuals included in the Nomcom's work with regard to whether
they simply provide information when asked or participate in
some or all Nomcom discussions or deliberations."

I'm sure you can write better sentences, but an approach like
that reminds the Nomcom that the IAOC is relevant, that, if the
Nomcom should in the future start appointing people to other
bodies internal or external to the IETF, we don't have to redo
this.  And I think it is IASA 2.0 proof -- it that process
abolishes the IAOC and creates three bodies named Tom, Dick, and
Harry, the document still works and the Nomcom gets to figure
out who is relevant.

     john