IETF Logo Mail Archive

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

"Andrew G. Malis" <agmalis@gmail.com> Wed, 09 August 2017 21:33 UTC

Return-Path: <agmalis@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 32FF7132339 for <ietf-nomcom@ietfa.amsl.com>; Wed, 9 Aug 2017 14:33:49 -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 AK6ZcXb8P5tD for <ietf-nomcom@ietfa.amsl.com>; Wed, 9 Aug 2017 14:33:47 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (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 DB696132191 for <ietf-nomcom@ietf.org>; Wed, 9 Aug 2017 14:33:46 -0700 (PDT)
Received: by mail-oi0-x22f.google.com with SMTP id x3so73851146oia.1 for <ietf-nomcom@ietf.org>; Wed, 09 Aug 2017 14:33:46 -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=DYizO/fEWCbkfhJdwp4i/zq6rxP65rzLpIoCvcrNb4k=; b=f6o9dz0rljQCRtg3WO9WfVPNayZVLbtNqIHYgmz7NHI88MgcjYdu65/V4gEdJooH/E oirQZZvoqrQs/AnZjG1tMpvw6vQipIPM8iJ2VtHNI4jK38KVNrOcbB7LkBDI8sGWged5 y5KxyqnTIa8oarKRQ/SiUgS7NiV9IykTMJNG+RYDBjWuMratIpGpzRMAhDYu3VylKr+u wpSsf/SOzCCPcti0CNa7mumrbW4leY68fbNOyuLk+Pc9vCrYrnjdzyIVhx+cEuiJA9we Kq2mT5IhgRYYd6ZN7Cq6rVVoXkj5he+B3am5uqKdoXyGXePZXZlDLOCn1Ond7Ulpv8E/ qNlQ==
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=DYizO/fEWCbkfhJdwp4i/zq6rxP65rzLpIoCvcrNb4k=; b=gAnXCrsypFzS+YTijtEg3WDNTes50CjKMy55iJBwo0+yw50mhTi6D27t1EE+8Vsmpm czTVvKjjfjKaePkp7tqN0W1ry6vDRRkg0LrdQ7imLVXo4tvYGrjZb3/odBXHx608SPl6 ebmWuVWQTGLJG59AXU4e/GTgoJDDVMf3VtMWqOSj3VFEOcbLV2IeHititjNZpaQPRGkG x/IlEOCZpq0Cnebx6HqWxV+wM8fBQiNbcZxlMXcAARbh6iwt4bDCK4KAF+VJvgk6xVYH lZLgn/J0o+BsSMq6o/gNTdILtY5y/VXqSX6oUBNIdqixBBXmOe3VnwhrdOXp9A6JB4Ak MfOA==
X-Gm-Message-State: AHYfb5hd/l1cjmZx/cl0PyFlLeNc7XXVLxgeSRR3QxGS+VqbY/Uwkbxy qpFxMx6CELdDzL1OjMfzdIRyJTgPPQ==
X-Received: by 10.202.213.79 with SMTP id m76mr9874249oig.54.1502314426293; Wed, 09 Aug 2017 14:33:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.232.34 with HTTP; Wed, 9 Aug 2017 14:33:25 -0700 (PDT)
In-Reply-To: <5f26388a-93aa-7133-6973-de669a9bb2f4@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>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 09 Aug 2017 17:33:25 -0400
Message-ID: <CAA=duU2hn-6=OzvZrfuz0agvzxvV0euXP4nsnjdksUpsnAyfJQ@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Robert Sparks <rjsparks@nostrum.com>, NomCom-Discussion <ietf-nomcom@ietf.org>
Content-Type: multipart/alternative; boundary="001a113acab2b861ae055658d5f7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/EuPvjzXT6IMS_aP-z_7da0Xxw_A>
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 21:33:49 -0000

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.

Cheers,
Andy


On Wed, Aug 9, 2017 at 4:15 PM, Brian E Carpenter <
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
> https://www.ietf.org/mailman/listinfo/ietf-nomcom
>

v2.23.0 | Report a Bug | By Email