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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 09 August 2017 23:03 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 C7B8F127B60 for <ietf-nomcom@ietfa.amsl.com>; Wed, 9 Aug 2017 16:03:42 -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 RSux644nOv5M for <ietf-nomcom@ietfa.amsl.com>; Wed, 9 Aug 2017 16:03:41 -0700 (PDT)
Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::233]) (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 CE8501204DA for <ietf-nomcom@ietf.org>; Wed, 9 Aug 2017 16:03:40 -0700 (PDT)
Received: by mail-yw0-x233.google.com with SMTP id s143so48950876ywg.1 for <ietf-nomcom@ietf.org>; Wed, 09 Aug 2017 16:03:40 -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=G7gqKEaHgPJmfhpjWMXWkStGZQjCbS/DETvGK8QnQ78=; b=DqylX18m7lgtFfiJfclysUTkGSkPVfRLAOb6BbLCrJNgCIPx0ANPN4Ue0yNSRVGHPa y2KYFeR8UdpFKcIMfWPtII3BGNBq0teVaAEAw50Wamxcvoh6rlyt9t7hrmRSC58fuisE W4OeRAolPnEEppyKa8SgaOduutDbWOJhHnLOiG3k37KcM1JauQDI0I7IFQK3wdZxFevS 9CnP6LCgeWYyAULw6rKsjWvVaFcKVtKDKFYRA7YlUO2YFn0XDR06YMORp41628OluRUP 1PZbUdIklk/szhwxcJWAndM36XTVAZnUxV4CWQG3o1Aj3ErTHP9pqIfcNARfwSE3UO/6 /G1Q==
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=G7gqKEaHgPJmfhpjWMXWkStGZQjCbS/DETvGK8QnQ78=; b=ObYMWQjO8d62i3cLvxbFL20IlffaC5tnZHJJZs3wa7NQzQO3WZc/7edcEk2OPqAjwT NOh7lO5jXJv8xA7Jm5W/ogOyfP2XQcNET2nlPRETj7gb5jmFhiD8V1U7hSu0cCCRpGAu W1uy3eraduP04F6cfZzaqYmJR/1ayowytXfI0elrMTu/gPxsmFvRFYfp++EuIq9dsxM+ Mm2piXiShf4np1D4+ira0RL9/48oogTo33dyktTpcgf85xl2otJUl5rxF3fin3SISGyX NOyk8p/6qrozKFYwaitPU4chE/6RY6pOi2HN4Uu06fY36YyVldm8qwGTjMSCTJyi161C FOXg==
X-Gm-Message-State: AHYfb5gFNh9CkB0k2SzcCS51GVmwv6scQMitsHPT09PkQS1TwuJrez5u spTJvcL/IW+w8V2ojIJFNqgvLnFdEw==
X-Received: by 10.37.15.139 with SMTP id 133mr7492641ybp.75.1502319819811; Wed, 09 Aug 2017 16:03:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.52.79 with HTTP; Wed, 9 Aug 2017 16:03:39 -0700 (PDT)
In-Reply-To: <CAA=duU2hn-6=OzvZrfuz0agvzxvV0euXP4nsnjdksUpsnAyfJQ@mail.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> <CAA=duU2hn-6=OzvZrfuz0agvzxvV0euXP4nsnjdksUpsnAyfJQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 09 Aug 2017 18:03:39 -0500
Message-ID: <CAKKJt-chkcrJRfCU1_MHb47H7GZNHafkbwVZKNsxh2pQzXyiYA@mail.gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, NomCom-Discussion <ietf-nomcom@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
Content-Type: multipart/alternative; boundary="001a113f498a32fcca05565a1715"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/O6W5OfXVAoPx6ljyEPew0MwNZ50>
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 23:03:43 -0000

Dear all,

On Wed, Aug 9, 2017 at 4:33 PM, Andrew G. Malis <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> 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
>>
>
>
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom
>
>