RE: NomCom randomness results... delayed

"Peter Yee" <peter@akayla.com> Thu, 06 July 2017 21:00 UTC

Return-Path: <peter@akayla.com>
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 C1A621317D2 for <ietf@ietfa.amsl.com>; Thu, 6 Jul 2017 14:00:45 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 IYSy-xh0VGYD for <ietf@ietfa.amsl.com>; Thu, 6 Jul 2017 14:00:43 -0700 (PDT)
Received: from p3plsmtpa12-07.prod.phx3.secureserver.net (p3plsmtpa12-07.prod.phx3.secureserver.net [68.178.252.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ACD912EA58 for <ietf@ietf.org>; Thu, 6 Jul 2017 14:00:43 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by :SMTPAUTH: with SMTP id TDsiddi9pKEkdTDsidmRHm; Thu, 06 Jul 2017 14:00:12 -0700
From: Peter Yee <peter@akayla.com>
To: sarikaya@ieee.org
Cc: 'IETF' <ietf@ietf.org>
References: <149935833402.2269.4238729858373783963.idtracker@ietfa.amsl.com> <573cd826-66f3-46cf-e191-b58b367276f3@comcast.net> <CAC8QAcf5f9BrZVfdReGN9_bmgK8Z5gn=+5frw-vUZVS9khpaWw@mail.gmail.com>
In-Reply-To: <CAC8QAcf5f9BrZVfdReGN9_bmgK8Z5gn=+5frw-vUZVS9khpaWw@mail.gmail.com>
Subject: RE: NomCom randomness results... delayed
Date: Thu, 06 Jul 2017 14:00:27 -0700
Message-ID: <06e701d2f69a$e5adba10$b1092e30$@akayla.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_06E8_01D2F660.394FA560"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQCRV8v0HLk1D/UMEjSCPMhQV2WhEQKBWb7oAfPOvq+kptxD0A==
Content-Language: en-us
X-CMAE-Envelope: MS4wfLTga0W7yaiz6vJIehew38Mj8S8VgFs4WZkKGSNJzUISqGK68RvmlsbZbzJDx06Pg9D4w7n5VfOCYWkpiTsPwkAB4OfLDZbOZltpnyh9JYNOnuy4f8Sl fpYW66LLN57kPXlXWKw33reU3kz0T7eEmOqXi1nGx3lNFMvyQERYjJwo
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/02ZXdYSpv155kfGtG5JcwqDs3OA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 06 Jul 2017 21:00:46 -0000

For the 2017-2018 NomCom, you would have needed to check the box for registration for any of IETF 96-98 (Berlin, Seoul, and Chicago).  Your checking the box on the IETF 99 registration form will put you on the list of the 2018-2019 NomCom, assuming you are eligible.

 

                -Peter

 

From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Behcet Sarikaya
Sent: Thursday, July 06, 2017 1:45 PM
To: Michael StJohns
Cc: IETF
Subject: Re: NomCom randomness results... delayed

 

Hi all,

Regarding the list of volunteers, I had checked the box for volunteering for Nomcom when I registered for IETF 99 with payment,despite that my name is not in the list.

What makes?

Regards,

Behcet

 

On Thu, Jul 6, 2017 at 1:21 PM, Michael StJohns <mstjohns@comcast.net> wrote:

On 7/6/2017 12:25 PM, NomCom Chair 2017 wrote:

I had planned to pull the randomness results today, but there will be a slight delay.  While the EuroMillions and Powerball results are available (nothing like the lottery for being timely), the US debt numbers are still only showing the values for July 3rd.  The July 4th US holiday may have something to do with that, although I would have expected the July 5th numbers to be up by now.

My plan for the moment is to examine the numbers tomorrow and see if the expected US debt data are available.  If so, I'll run with the published inputs.  If not, I'll have to use the latest available US debt numbers, which I will document in the randomness results announcement.  Please let me know if this plan causes any concerns.

Peter Yee
NomCom Chair 2017-18
peter at akayla dot com
nomcom-chair-2017 at ietf dot org

Hi Peter -

You should pick a new date and a new set of variables, and announce rather than mixing and matching data you (we) already know with something you would pick later.  That maintains the integrity of the process by keeping human choice out of the process.  I'd probably also provide a caveat for when the data isn't available (e.g. a substitute).

Mike