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

Joel Halpern <jmh@joelhalpern.com> Thu, 10 August 2017 00:42 UTC

Return-Path: <jmh@joelhalpern.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 3941C1324D3 for <ietf-nomcom@ietfa.amsl.com>; Wed, 9 Aug 2017 17:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 QN1sVW60GMdi for <ietf-nomcom@ietfa.amsl.com>; Wed, 9 Aug 2017 17:42:08 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 408A6131CB2 for <ietf-nomcom@ietf.org>; Wed, 9 Aug 2017 17:42:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 28A9B429EDE; Wed, 9 Aug 2017 17:42:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1502325728; bh=UA3VK5sjW/lBGUf7bC1Uwl37PgLTmu68Wr/oKvfA010=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=pkQB8Yyk4Uecoh/1AuhtvXAmpS/yXxUaSQ6ZThQCtCSil0/exRZJFa6KnhClg4Jaz lh3vAYseYPcUgrof6CN1HVNCCD09u1IeCPyRe8p7j0Hb2tO2cFVtLH7UqHrG3llGL+ s3BxZeIYzwzdHZarvRCePug1FCJLZ84aJtTc0tmE=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [50.225.209.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 94B14429ED5; Wed, 9 Aug 2017 17:42:07 -0700 (PDT)
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: NomCom-Discussion <ietf-nomcom@ietf.org>
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>
From: Joel Halpern <jmh@joelhalpern.com>
Message-ID: <6e62d88a-ba0e-18eb-3a45-88851b6e7c46@joelhalpern.com>
Date: Wed, 09 Aug 2017 20:42:06 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAKKJt-chkcrJRfCU1_MHb47H7GZNHafkbwVZKNsxh2pQzXyiYA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/nwzrx--Rm2Po1HC3RIJUN39Crp4>
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 00:42:10 -0000

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.

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

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
>