Re: [ietf-nomcom] BCP 10 Update, adding an IAOC Advisor to the Nominating Committee
Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 10 August 2017 05:31 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 D4BB7132542 for <ietf-nomcom@ietfa.amsl.com>; Wed, 9 Aug 2017 22:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 5aCCRb6Z24WN for <ietf-nomcom@ietfa.amsl.com>; Wed, 9 Aug 2017 22:31:13 -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 E6D73132519 for <ietf-nomcom@ietf.org>; Wed, 9 Aug 2017 22:31:12 -0700 (PDT)
Received: by mail-pf0-x232.google.com with SMTP id o86so36938438pfj.1 for <ietf-nomcom@ietf.org>; Wed, 09 Aug 2017 22:31:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=x/3W2J7cs/Onwxc27+VyXExHBKqOqMdV1FyUVXwGtdE=; b=XGmV5ruCGDkihkXRzERT6Sfo0CaeYiGSycNW0MVr2EzBNzA9iiJTSHVb2i1weMhyfu TYet3YDoftqNpP2YFKAuV/uBbGrGYOZ+OS3HFxqVUX93ItxYr0sa9V0l4LHCzpWbrZNu RMK33/q/ZeCKx15J1g2Xo8lClfIZ+VOFEtnKUB0Zh3bIV8D2vUX1bDbcoh21ZsJb+EM3 9F/P16qgE3AMXMNJPCpfem5v0dLiGzCKhE6GNfYkIug8loGCJDGffzMfgT3ZykYZSKgo h0zQ5oZqtDGBoetyyR4qpOETwGtprPtjyC8kfcycVcs0IR7L3yA3MpaJCBxnT4zvu6/u ts5w==
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:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=x/3W2J7cs/Onwxc27+VyXExHBKqOqMdV1FyUVXwGtdE=; b=r0+SpiPRhzX7Q4iqAcu09UfzwRvkvKdX1SGf41WP6gqdF5SWGS0+hCmzkMIgMrF35D n9JevT7SxQYQFFrL4rsMfayAd2AvLZnK7kIOBLWEqpzukLRd5log1xnsWrrrHha3pJ6M qWisYOLXAkCVlDiml41Y3ydWCXi8mSWKvzOlQuiC7ru+tiugcPRkyv6BSzDgylL/YwIJ MkMJbr5Rbu3U4/n26m46BJtwZb4G08Xxry5RWOLNKVkFKSmL6i2p0ZZd9QtV0pbrJhQ3 hRB8jSWd2Dw3l+42LIlRjilS+lUeCugkuPKyItdz3QOzbRccF89rHd3xQ9UGtC5bz0B1 zkiw==
X-Gm-Message-State: AHYfb5i/gET0HjXErVEXkVrEtdEmWE95XqeD5aLAmT6/xbjewydfJ8LU zMMdEPMO0vYp5+Ke
X-Received: by 10.98.109.65 with SMTP id i62mr10915021pfc.309.1502343072217; Wed, 09 Aug 2017 22:31:12 -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 f88sm10931204pff.74.2017.08.09.22.31.09 for <ietf-nomcom@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Aug 2017 22:31:11 -0700 (PDT)
To: 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> <6e62d88a-ba0e-18eb-3a45-88851b6e7c46@joelhalpern.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <10f48675-7a42-1f9a-0d75-e75bf9468c5d@gmail.com>
Date: Thu, 10 Aug 2017 17:31:13 +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: <6e62d88a-ba0e-18eb-3a45-88851b6e7c46@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/8YK60gE3cea8rXCmJePQi7sOLQs>
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 05:31:15 -0000
On 10/08/2017 12:42, Joel Halpern 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. > > 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.) That's what I wanted to say, but said in a confusing way. Brian > > 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 >> > > _______________________________________________ > ietf-nomcom mailing list > ietf-nomcom@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-nomcom >
- [ietf-nomcom] BCP 10 Update, adding an IAOC Advis… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Michael Richardson
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… S Moonesamy
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Michael Richardson
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Brian E Carpenter
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Andrew G. Malis
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Joel Halpern
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Scott O. Bradner
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Stephen Farrell
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Joel M. Halpern
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Brian E Carpenter
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… John C Klensin
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Stephen Farrell
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… John C Klensin
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… John C Klensin
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Stephen Farrell
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… John C Klensin
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF