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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 24 August 2017 21:01 UTC

Return-Path: <spencerdawkins.ietf@gmail.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 4B27E132403 for <ietf-nomcom@ietfa.amsl.com>; Thu, 24 Aug 2017 14:01:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 zuQ7Y-ormABf for <ietf-nomcom@ietfa.amsl.com>; Thu, 24 Aug 2017 14:01:13 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (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 3513A1323A8 for <ietf-nomcom@ietf.org>; Thu, 24 Aug 2017 14:01:13 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id y64so3807201ywf.1 for <ietf-nomcom@ietf.org>; Thu, 24 Aug 2017 14:01:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xwjduL52sNqWy+NH6NFusPnYrHiX7W6Wc59W7S8Ewfg=; b=VMDCcabxKStb7nWOQ4HdK0MR6q1GeXeSuzV5WkwuXyj0cmfM+3C+2tfYviyMDV/wKT Qt9y8xmw5gA0aKHHodqVa37u33DoQHZm2leD0FJXhkSlU10TH/d8P3O/pv8jki4FPXPW aLiydhzGuVgYCw23ziW78C259KY1x2LiA1ewTqcUuIRKx6g0urOOIQPJZk4TqZ6ksYZf 09eWkrL/suz1agaUk6Jdkl2mr5UpcQ40hcw7k7XkoRECGamhxxAEYWLVZ84Np1A+ow65 nslj70G0d6VDMQqPmG3R2K9PhsqFAlVKqxng8LCyXTzrno9pjNpL+Rf7xxr2eWdqmQ8z nIjA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xwjduL52sNqWy+NH6NFusPnYrHiX7W6Wc59W7S8Ewfg=; b=N5kDWz0RYbx4WD7ME7ryu44VnlPf3rlnV531jLs3NUjgh/ZsYPXdCNzE4f9RbyMXoP /JQHjqAebCjEF1lNMSaWtrOxu2Bk7x8XPfMYNXjUtQpC6rTi0erxiCEEo+TtJKk/3Q4H odoUCeXpKYlu8rlrSaw2D+FNdsCWcGo5HnShZ0SJUGeXwUU18ZJFC+8L9yvWmbuWR6mz UoCaOPGqxJvS8zPEEaEhhi0poU+Kfn2KDSR+6Obm9pElZ6mvxe6ppVQpHFTks3qYOujs I3tICDk5RVAaXTtHwVNTOo6QA25fwJehjqUUnSYyhz6yz8rCRMF/jYJpZYF0BDx73gG6 7xSQ==
X-Gm-Message-State: AHYfb5ibTg6s6u++VYFBiE/uixOYkb0dM94QrGDDDNAkU7y2zI689Amc F7C1cEBcjUibimezXwTWaO8G/D49Ueke
X-Received: by 10.129.229.4 with SMTP id s4mr5938150ywl.130.1503608472142; Thu, 24 Aug 2017 14:01:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.2.148 with HTTP; Thu, 24 Aug 2017 14:01:11 -0700 (PDT)
In-Reply-To: <2e2ecf8a-e843-795b-f96b-b183e2b3a84c@cs.tcd.ie>
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.com> <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>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 24 Aug 2017 16:01:11 -0500
Message-ID: <CAKKJt-crXRBdu2+vVzuptk-rknTFsHCg=xhPM6YqsD-e=7_7dw@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: NomCom-Discussion <ietf-nomcom@ietf.org>
Content-Type: multipart/alternative; boundary="089e08222cb4dd090105578620a9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/pZHpxfUi0oVtMG0Oc6SVZWu79EM>
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:01:16 -0000

Hi, Stephen,

On Thu, Aug 24, 2017 at 11:17 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie
> wrote:

>
> Hiya,
>
> On 23/08/17 04:11, Spencer Dawkins at IETF wrote:
> > Hi, Stephen,
> >
> > On Wed, Aug 9, 2017 at 8:53 PM, Stephen Farrell <
> stephen.farrell@cs.tcd.ie>
> > wrote:
> >
> >>
> >> Hiya,
> >>
> >> FWIW, my take:
> >>
> >> - I don't care if we use the term liaison or advisor
> >> - I do think the IAOC has to pick the person
> >> - I do think every nomcom needs such a person helping
> >>   out
> >>
> >
> > Sorry for my delay in responding.
>
> Ditto:-)
>
> >
> > On your other points, I think I know what to do with your feedback, but
> > this one is worth talking about some more.
> >
> > There are different levels of "Nomcoms needing someone who speaks
> IAOC-ese
> > fairly fluently".
> >
> > I'm shooting for "don't forget to think about how you'll know whether
> > you've got a viable IAOC candidate to forward to the confirming body, and
> > if you don't know who can help, the IAOC should be well-placed to make
> > suggestions about people
> > who can help".
> >
> > I could be shooting for "the Nomcom has to ask for help", or even "has to
> > ask the IAOC for help".
> >
> > At the extreme, I could be shooting for "change the definition of
> committee
> > membership so that if you don't have representation from the IAOC, you've
> > got a really big problem", to match not having a liaison from the IAB or
> > IESG.
>
> It's not a hill on which I'd die, but I don't think it extreme
> to expect every nomcom to have an IAOC-helper, even for years
> when there is no IAOC appointment for nomcom to make. So I think
> your last target above is the better one.
>

I agree with your starting point, for a couple of reasons.

First, in private conversations, I am told that some Nomcoms get feedback
about AD nominees that is actually more appropriate for IAOC nominees,
because the community isn't quite sure where the dividing line between the
two bodies is. I don't know more details, because that feedback is
Nomcom-confidential, and I wasn't on the Nomcom(s) where that happened,
but, yes, having someone who can say "but that's our job" in the room seems
helpful, whether that particular Nomcom is reviewing an IAOC position or
not.

(I wouldn't be surprised to hear that Nomcoms have also gotten feedback
about IAOC nominees that should have been pointed at IESG nominees, but no
one has told me that, so forget I said it)

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 ...



I am fine with the description of "helper" being vague-ish to
> allow for iasa2 etc.
>
> Cheers,
> S.
>
> >
> > Are people comfortable with this being more permissive than prescriptive?
> >
> > Thanks,
> >
> > Spencer
> >
> >
> >> - I'm fine if a recent but not current IAOC member is
> >>   the stuckee, where recent is say <= 2 years since
> >>   being an IAOC appointee. Weasel wording around that
> >>   goal is fine so long as the intent is clear.
> >> - If the stuckee is not a current IAOC member, then I
> >>   think there needs to be some form of appeal of the
> >>   appointment possible, even if that's via some hard
> >>   to exercise mechanism.
> >>
> >> S.
> >>
> >>
> >
>
>