IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 09 August 2017 19:02 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 DA52213247C; Wed, 9 Aug 2017 12:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 pTvhWKNRvjQk; Wed, 9 Aug 2017 12:02:15 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1954132471; Wed, 9 Aug 2017 12:02:14 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 8506C2009E; Wed, 9 Aug 2017 15:04:29 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A6308806BA; Wed, 9 Aug 2017 15:02:13 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
cc: "ietf@ietf.org" <ietf@ietf.org>, NomCom-Discussion <ietf-nomcom@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
In-Reply-To: <CAKKJt-fxhFnnK3T2nVj2bD=Ve7z6L0oJFjYFqBb59TusJDwFzQ@mail.gmail.com>
References: <CAKKJt-cd2-tS=3QnvRcsDKcZ8=o5Z98wUr-=tp8OeP9J1M0M8g@mail.gmail.com> <4622.1502292425@obiwan.sandelman.ca> <CAKKJt-fxhFnnK3T2nVj2bD=Ve7z6L0oJFjYFqBb59TusJDwFzQ@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 09 Aug 2017 15:02:13 -0400
Message-ID: <21862.1502305333@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/1l9-TEbLzXZ5TJLy7aubB5dDc4Q>
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 19:02:17 -0000

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
    > Yeah. I'm kind of dancing here, because I'm trying to reuse terminology in a
    > new and exciting(?) way.

understood.

    > This document could

    > * Remind the Nomcom that they will probably need help understanding what the
    > IAOC does, so they should ask, OR
    > * Tell the IAOC to appoint (let's call it) an Advisor, at the same time the
    > IAB and IESG are appointing liaisons.

    > The first option is where I headed, because I tend to write permissive BCP
    > text ("BCP text is hard to get right").

I think that I'd prefer the IAOC be told to pick someone, but I'm listening
to other opinions.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email