Re: List of volunteers for the 2020-2021 NomCom

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 29 June 2020 03:22 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0F703A0796 for <ietf@ietfa.amsl.com>; Sun, 28 Jun 2020 20:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 EUVJ5YL7GSIn for <ietf@ietfa.amsl.com>; Sun, 28 Jun 2020 20:22:58 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51B303A0795 for <ietf@ietf.org>; Sun, 28 Jun 2020 20:22:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 9F4EB38996 for <ietf@ietf.org>; Sun, 28 Jun 2020 23:20:11 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id EYU8ucj9KlLv for <ietf@ietf.org>; Sun, 28 Jun 2020 23:20:09 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id BACE538995 for <ietf@ietf.org>; Sun, 28 Jun 2020 23:20:09 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 25A34F11 for <ietf@ietf.org>; Sun, 28 Jun 2020 23:22:55 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: List of volunteers for the 2020-2021 NomCom
In-Reply-To: <b0e8aaf7-b0bd-b9b4-feec-d9518d42aa58@gmail.com>
References: <159336028613.24238.3976538366030551355@ietfa.amsl.com> <183EB027-B2EA-4CAC-AB7F-4135CC5EFA06@att.com> <9859.1593390955@localhost> <8ED40272-57A9-4B7C-A9BD-4348A4052FE9@akamai.com> <CAChr6SxvQN=EAMAFF72A+ArQqY8vHvOP9bjoa0gP18o-F3+3uQ@mail.gmail.com> <b0e8aaf7-b0bd-b9b4-feec-d9518d42aa58@gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512"; protocol="application/pgp-signature"
Date: Sun, 28 Jun 2020 23:22:55 -0400
Message-ID: <17321.1593400975@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kSgebK02ZjkxG8hIQGxaj1ydVr8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2020 03:23:00 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> People who contract with a company for more than 50% of their time
    >> spent doing IETF activities will be considered affiliated with that
    >> company.

    > then the above statement about honor and integrity would not have been part of the BCP.

I just don't understand the "IETF activities" part :-)

I'm employed by Big-Router-Company for 100% of my time, and
I spend 80% of the time writing code, and 20% of my time doing IETF work
(writing drafts..) then I think we'd all agree I work for Big-Router-Company, right?

If I'm contracted to Company1 to write code for 80% of my time,
and I'm contracted to Company2 to write drafts for 20% of my time,

I think we'd say I'm effectively Company1's body.
Whether Company1 has any other IETF people or not, is another question :-)
Doesn't matter that I write code.

The point is that I probably can't be told what to do as a nomcom person by
Company2.

I am neutral as to whether the NomCom should have any publically stated rule
or not.  I don't think I had a rule as NomCom chair, but I did ask when it
was unclear, and the 50% mark was important to

Yes, there are many ways to game this, but not in an honourable way.
(And I've already disclosed to the NomCom chair, btw)

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