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 17:10 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 964AA132350 for <ietf-nomcom@ietfa.amsl.com>; Wed, 9 Aug 2017 10:10:27 -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 u1ikc37lBqSa for <ietf-nomcom@ietfa.amsl.com>; Wed, 9 Aug 2017 10:10:20 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (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 7D2EA132256 for <ietf-nomcom@ietf.org>; Wed, 9 Aug 2017 10:10:20 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id s143so43859811ywg.1 for <ietf-nomcom@ietf.org>; Wed, 09 Aug 2017 10:10:20 -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=wrO9VqAuYIfv4sqxQHpCQP5pxo/37RVSHCt+7WrcIO4=; b=AuthRQHbelz3jIPe/z1QQvdUn8LWoUB9h3BOaYeuWpRU/e2o2cBbsMRZYSFafkNgzQ g9OM2HEhiCr501Exe9nsIO9pdNGrFTNRWdq+pxliLX47ivTLa22EHwQbomqXSF61axwc ZVXsQQ5/V0wvwGwhO4+AY40UHjs5tR53MwqPugwYy6O8mIaWJ1sB7Y+iDhJn2vzIh9/m QtRqSuetluSPp9tHFnp4lII3FkSJwrYJBsQiCcdiDPjDrRf7w3t8ncAUSYb8Fw6Rj0pU JDiddAmNaBC7nrIuNGlsD+BXQgAeZs/rgU7vNtjhw6Ucz4/e4QJA46xQS+667cwE/ACT Tvow==
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=wrO9VqAuYIfv4sqxQHpCQP5pxo/37RVSHCt+7WrcIO4=; b=W9kiMAsnfkAEY5cKUduoO0MH0lXg5MKt6SymFWPDPwL5c5UEH7mdDspkteYW4QhMnP MDqmuWdlqLj6LmbyAf57NNRTj1hK1TiGqYTQpJ+cz5UINby9K11laEikP0+gOK5XYRp2 kyqgv2Bf7/oUjGfj08a7b1uVKd0wlfjjWWGPsUShH5+bNlEff29NFjeASqcogEq+WLwJ b8uSFc0/7Qx4sJ4jTFzUTPTd6xB4TSjPRa2S+YUKg+dTgN/5NhZfW0+wLEVj3ZeTfaZC 3UJGVceyvPJggZ2vBPoC+X9anGUELEXnLCUvBJHgwwRF/Hrd/5IWtSBPnm51p/m5flKM lAeQ==
X-Gm-Message-State: AHYfb5hSgLLDwDVpaYtdwbOvJQFFsnOlkrkTrsQ/QdhGTjao4WmUdYxh aHU/AJBlZCSbVAnTmHNkFYJUnCvZgA==
X-Received: by 10.129.141.9 with SMTP id d9mr3045284ywg.339.1502298619377; Wed, 09 Aug 2017 10:10:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.52.79 with HTTP; Wed, 9 Aug 2017 10:10:18 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20170809085713.0df50b60@elandnews.com>
References: <CAKKJt-cd2-tS=3QnvRcsDKcZ8=o5Z98wUr-=tp8OeP9J1M0M8g@mail.gmail.com> <6.2.5.6.2.20170809085713.0df50b60@elandnews.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 09 Aug 2017 12:10:18 -0500
Message-ID: <CAKKJt-fWePSfOQzTi_LFiLbSvcb6HGo5CVcuqFSeQpw61pZBJg@mail.gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: NomCom-Discussion <ietf-nomcom@ietf.org>
Content-Type: multipart/alternative; boundary="f403045e60128e19c70556552757"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/mtYGRnJu5venp23TkmHsKy8_Fh8>
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 17:10:28 -0000

Hi, SM,

On Wed, Aug 9, 2017 at 11:03 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Spencer,
>
> [Cc trimmed]
>
> At 19:44 08-08-2017, Spencer Dawkins at IETF wrote:
>
>> At Alissa Cooper's request, I put together a short draft that updates BCP
>> 10, the Nomcom process, adding a reminder that Nomcoms can ask the IAOC to
>> provide an advisor, and the IAOC can provide one.
>>
>
> The new text in Section 6.1 says: ""may propose the addition of an
> advisor" in the first paragraph and "Committee members are encouraged to
> propose the addition of an advisor" in the second paragraph.  I read that
> as meaning that the editor is saying two slightly different things.


I think you're reading that part correctly. The problem is, that the editor
wasn't saying two slightly different things clearly :-(

The first paragraph is intended to say "you can do this", and the second
paragraph is intended to say, "you don't have to do this, but you really
want to".

So, something needs to change. Let's see where the conversation in
Michael's thread ends up, because if the role becomes required, that text
changes significantly anyway, but thanks for the usual careful read -
you're right.

Spencer