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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 10 August 2017 01:10 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 352FE1323BA for <ietf-nomcom@ietfa.amsl.com>; Wed, 9 Aug 2017 18:10:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 NWRPo1FvLSY1 for <ietf-nomcom@ietfa.amsl.com>; Wed, 9 Aug 2017 18:10:56 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (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 BCA891201F8 for <ietf-nomcom@ietf.org>; Wed, 9 Aug 2017 18:10:55 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id p68so50185219ywg.0 for <ietf-nomcom@ietf.org>; Wed, 09 Aug 2017 18:10:55 -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=k4RRuMQh4pBD4nlZx/H0Byrau23Fr8qImKqOeJQ8PO0=; b=uYlV7DYPVLTAZUSmkKIgyutw0KCGpnMb574yLN3tirOHEk6ccqi3/iwa4BxVQwpZxP fnQxL6ynZpTRgxPCa7y39zho8aLZ4cpjfnRWxtKQhKgOivDWUaz+Wi7vbD4ySaYdQEPt 1C4Sdpk1l92zk4mQNEQsRL7ZCJugsGpFnHAbUTA2NLtmLf/Me6lRnLKhcSWSBKMfYGt8 aVkH5AXNmLCcpzDuXNseAxK6R0Sl35PyKQfxqujefVJ2br5KxjBPWaRnx8pBQgSMYXGL qzgxgPNCtGR0qTC0MZTUJ7JDsyl3YaaXd5wZzMP0DFNfn2nr+7Jt8tMebvrljj3LC7BD juXg==
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=k4RRuMQh4pBD4nlZx/H0Byrau23Fr8qImKqOeJQ8PO0=; b=TpkHGfPV/m/k4WbpoKVXfOFzKlWSqHzbLAATOcZy98X7JDto7CtqQSfPvGmykb7nnI HgTXkcCjE632IEkz/oZhJOJvVK6bhDpCsvEbIAS4yotulwkQRS1zC329qcT451MdnHgn ZqYfkb6vyd7bo8xI8m2cjvhi7Vr3YceiHPvbyI/1YKABmQMR1PbMHwKFt2DtP25Pdq1F WgUSgnc8bzN8jYlIOp0ZSegk19PQcv1tb4Dibz0pnDMvMMwVnPjquJ4XdRUDZHRwhfob 71SjfhOjadSgrOmJz6Oz+oPTRDQnH3BiGCXzskFZxEXaT7SoVJtBpXsct1bgWrUWb8sh l88Q==
X-Gm-Message-State: AHYfb5i6Wxq1N3eKibDYqw3mPPWKozeieKDafE1MqlZEGeQKjYqOmCDT 9y8S1QGKI/DJV72DLNceurchIjcG0S5Z
X-Received: by 10.129.96.85 with SMTP id u82mr8445848ywb.57.1502327454868; Wed, 09 Aug 2017 18:10:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.52.79 with HTTP; Wed, 9 Aug 2017 18:10:54 -0700 (PDT)
In-Reply-To: <6e62d88a-ba0e-18eb-3a45-88851b6e7c46@joelhalpern.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.com> <6e62d88a-ba0e-18eb-3a45-88851b6e7c46@joelhalpern.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 09 Aug 2017 20:10:54 -0500
Message-ID: <CAKKJt-dJ2Z1wsqXveg7+PR13d2bH61pHR753gEamwqWv4f+hKQ@mail.gmail.com>
To: Joel Halpern <jmh@joelhalpern.com>
Cc: NomCom-Discussion <ietf-nomcom@ietf.org>
Content-Type: multipart/alternative; boundary="001a11471de248ae3d05565bde8c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/l4bolELCoMyJC9QLC45y2DWyJB4>
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, 10 Aug 2017 01:10:58 -0000

Hi, Joel,

On Wed, Aug 9, 2017 at 7:42 PM, Joel Halpern <jmh@joelhalpern.com> wrote:

> As the IAOC is not an approval body, I have trouble seeing why the nomcom
> would need to send anything to the IAOC.  Even if the Nomcom had
> operational feedback from the community about the IAOC as a body, it seems
> to me that the advisor would not be the means to send such back.
>

There's certainly no reason why that feedback would HAVE to go through one
person, so, yeah, I think so.

The IAOC not being an approval body was the other reason I was OK with not
requiring the person the IAOC sent to the Nomcom to carry out several of
the liaison responsibilities, as well.


> I seem to be in the minority, but I like calling this something other than
> liaison, because of the set of roles that apply to liaisons, but not to
> this IAOC suggested information source.
>
> I mildly prefer Spencer's current formulation that the nomcom asks for the
> advisor.  The factor that strikes me is that this way the nomcom and its
> chair can ensure that they are comfortable with the appointee. (That is not
> their right with the liaisons, as those individuals are responsible to
> their providing bodies.)
>

I wasn't thinking about that, but I like the side effect. Joel, that does
act as a safety valve, because the set of possible advisors from the IAOC
isn't bounded, the way the existing liaisons from confirming bodies are.

This is Spencer's Opinion, but after hanging around the Nomcom past chairs
(at Russ's request, while compiling the issues that fed into
https://datatracker.ietf.org/doc/draft-dawkins-nomcom-3777-issues/), I came
away with the feeling that the Nomcom is given really wide discretion,
because there is no Plan B if process rules got in the way of a Nomcom
delivering candidate slates.  The Prime Directive is "come up with slates
of confirmable candidates in a timely fashion and maintain confidentialty".
If that happens, mission accomplished.

That's why I thought adding advice for Nomcoms is OK, but adding hard
requirements probably isn't OK.

And that's why I thought it was best to encourage the Nomcom committee
members to request an advisor, in the usual way, and allow them to ask the
IAOC for suggestions, but not to require them to have an advisor, and not
to constrain who the IAOC might suggest. As Joel points out, the current
draft doesn't require the Nomcom to accept that suggestion.

And finding out whether Spencer's Opinion is anyone else's opinion, is why
we're having this conversation now :-)

Spencer


> Yours,
> Joel
>
> On 8/9/17 7:03 PM, Spencer Dawkins at IETF wrote:
>
>> Dear all,
>>
>> On Wed, Aug 9, 2017 at 4:33 PM, Andrew G. Malis <agmalis@gmail.com
>> <mailto:agmalis@gmail.com>> wrote:
>>
>>     Brian,
>>
>>     “Liaison” as an actual person can be one-way, I’ve often seen the
>>     case where there are two liaison individuals between a pair of
>>     organizations, one for each direction.
>>
>>
>> Well, I think Andy is right here (the IAB certainly appoints IETF
>> liaisons to other SDOs as directional), but that's side-stepping the more
>> interesting question, which is not what we call this role, but whether we
>> expect Nomcom to send anything back to the IAOC via the (the draft calls
>> it) advisor.
>>
>> And that question may not need to affect the resulting text (
>> https://tools.ietf.org/html/rfc7437#section-4.9 says
>>
>>     An advisor is responsible for such duties as specified by the
>>     invitation that resulted in the appointment.
>>
>> which is pretty darned broad), but if it might affect the resulting text,
>> that would be good to know sooner, rather than later.
>>
>> Thanks,
>>
>> Spencer
>>
>>     Cheers,
>>     Andy
>>
>>
>>     On Wed, Aug 9, 2017 at 4:15 PM, Brian E Carpenter
>>     <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>>
>>     wrote:
>>
>>         (Adjusted the CC)
>>
>>         On 10/08/2017 06:48, Robert Sparks wrote:
>>         > Spencer -
>>         >
>>         > The attempt to avoid the term liaison is not working well for
>> me.
>>
>>         'Liaison' implies 2-way communication; 'advisor' implies 1-way
>>         comunication.
>>         I think we need to decide which we want.
>>
>>              Brian
>>
>>         _______________________________________________
>>         ietf-nomcom mailing list
>>         ietf-nomcom@ietf.org <mailto:ietf-nomcom@ietf.org>
>>         https://www.ietf.org/mailman/listinfo/ietf-nomcom
>>         <https://www.ietf.org/mailman/listinfo/ietf-nomcom>
>>
>>
>>
>>     _______________________________________________
>>     ietf-nomcom mailing list
>>     ietf-nomcom@ietf.org <mailto:ietf-nomcom@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/ietf-nomcom
>>     <https://www.ietf.org/mailman/listinfo/ietf-nomcom>
>>
>>
>>
>>
>> _______________________________________________
>> ietf-nomcom mailing list
>> ietf-nomcom@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-nomcom
>>
>>
>