IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 09 August 2017 20:15 UTC

Return-Path: <brian.e.carpenter@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 6DAD2132476 for <ietf-nomcom@ietfa.amsl.com>; Wed, 9 Aug 2017 13:15:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 feCX7LOHgDO1 for <ietf-nomcom@ietfa.amsl.com>; Wed, 9 Aug 2017 13:15:43 -0700 (PDT)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (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 BAB9C13244C for <ietf-nomcom@ietf.org>; Wed, 9 Aug 2017 13:15:43 -0700 (PDT)
Received: by mail-pf0-x232.google.com with SMTP id c28so32096632pfe.3 for <ietf-nomcom@ietf.org>; Wed, 09 Aug 2017 13:15:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=d9gCnQ6Ozw4CSkf87muUaj6uaBHeRUxawZjp3WMH1e0=; b=aP3apcpnjaCnPhPFwRaVHYu/Owgq2ui03mwstS7ey8825UzSrOOUM8jEK4eRij9KLN mh4muwl19/eZQ6kyBGAJgUTo2Pgr3ih7Ttmt3iuB/BDjzHf6uJ9Q3kaUcxsvtkNiWvkX IUFydzVwq1LzdAOcJRIMO+/Rty4pkcNyDqHCMzfF7y8xdTqbQmMqO+4bveHLAWUFMj+u MULy4kPoNrSo5cK9uMhtfG9LzgBFNRy+KL+wMpGoTv76brr3B7Jwc1SWnU5i/MV66YKd NFhxS5Knuych+1wVdGHN0zD4Od4Q5Jl5WDgvkhTjfFAsKTRJjtkiRxZ7mj0cKijqZhDy nyEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=d9gCnQ6Ozw4CSkf87muUaj6uaBHeRUxawZjp3WMH1e0=; b=JWNWjq3j4vlBzB3RRno8Y8JOgG8wOOvPCvqT/rZq6V73xa8tafzVJjhLMySJZpuLYL CsVhBPUpA/8Ik0niK1d11EL58ggdh3dVKLazIf0lJiC7SiBrMKd2IY5iefowxMkXsaHc +HH5TCsXsbJU000V400YKcswgozDVWZtlkvgqBtEopXPy5Gy3u3PHLODrvS+eOJWQHZ+ MVzWETYGMyii1hIkef4XtQ0ngBDANTK/n6RtvO0rdJzyWF0lUL7hklwHfdRoSMoFZMCE 4BP3Q3yjiB+K7HmX/QbZrbjJ44r5l/6R6iDqxxYYCJ6Uy+6afYpwjNYljMcznGNLvtyZ DLQQ==
X-Gm-Message-State: AHYfb5iy3odN6/ygHpL1vieLeybgWIA/NZsjqA2AhrJA09fmeaT4hSdQ BtrA/cTihTBcpQ==
X-Received: by 10.84.178.129 with SMTP id z1mr10367982plb.260.1502309743343; Wed, 09 Aug 2017 13:15:43 -0700 (PDT)
Received: from ?IPv6:2406:e007:521f:1:28cc:dc4c:9703:6781? ([2406:e007:521f:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id r25sm7887368pgu.7.2017.08.09.13.15.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Aug 2017 13:15:42 -0700 (PDT)
To: Robert Sparks <rjsparks@nostrum.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>
Cc: NomCom-Discussion <ietf-nomcom@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5f26388a-93aa-7133-6973-de669a9bb2f4@gmail.com>
Date: Thu, 10 Aug 2017 08:15:44 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <1250df52-b5b3-4f71-bab1-790d156af1e9@nostrum.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/DCVkCbwQE0_bHwHb_hpzlryn9QE>
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: Wed, 09 Aug 2017 20:15:45 -0000

(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

v2.23.0 | Report a Bug | By Email