Re: NomCom randomness results... delayed

Behcet Sarikaya <sarikaya2012@gmail.com> Thu, 06 July 2017 21:10 UTC

Return-Path: <sarikaya2012@gmail.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 76B3613168B for <ietf@ietfa.amsl.com>; Thu, 6 Jul 2017 14:10:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 o3pa1J8OCrf7 for <ietf@ietfa.amsl.com>; Thu, 6 Jul 2017 14:10:39 -0700 (PDT)
Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::234]) (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 96939131553 for <ietf@ietf.org>; Thu, 6 Jul 2017 14:10:38 -0700 (PDT)
Received: by mail-wr0-x234.google.com with SMTP id 77so19884062wrb.1 for <ietf@ietf.org>; Thu, 06 Jul 2017 14:10:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ZdvEzs2c3D0hDvuwjHsYahaBgm8vF7t584eeKfKhHCA=; b=FEVV5oBwgNCf0GngWUV8QQDWyPCfKAjzUSXFixvF2BJCbe5sVK70GHp5TB4cxKOHgz 0UA6AahidAcVv9/Pul5NCl2pJZTIVWsM9wN382KP4O+rtHbvJRaV8k90B3aBuYQRfYn4 YCr2yryGfzMen0J0usPqJ7sX46kq+3fKN1bVPr1cLzcahwXjVm9ujzmZ2a11NfQNY5L3 naaFAZg4Bi2yn+gOh7sk54oB2o7SCd3aqJQlLrTvJCg0cHh/Prkbq35ip+BvldrutfS8 3Scb3bjFJiQfFlBUGmc0RqjepqExo+fBSBMGn8x6WYemAH+5QFnJCv/JxnfPzqZsCcsS r68Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=ZdvEzs2c3D0hDvuwjHsYahaBgm8vF7t584eeKfKhHCA=; b=YwxdyyllglrKdkKBbUyE4eZBwoLfT+epm8Dm0YhKLGg2xIZlgAo8jF0UYYui50buHT VZ4hSKAbs5w/QMXMHrdpOFDlRJ5sO2sX5J1enSiehzg1B5jqSaxjRl/uPFuaQuNttQxG GrFrB4Xka+YtEQh565OTE/oR2xiUwiA3dmGX4nAe3sKhJaiC6bBoJ4S1cjLwBD7q76jT nNdJdBpN2j6edM+5k7lWqU83/mDihL7GSTVJtJ1/wUvJqTCjzpxOmeXbLGDpmbh4tQdK FHJjYcyfOgpiu/FCPQfX4c7ErUH0YkKplrT7wmSLCdCdVgUNnsEjqn60mdMJsBXrRNHH MA6A==
X-Gm-Message-State: AKS2vOzL2qt1ixrKoVTW/QB/8pa+7+H9LixRxEk+G8Be42GgiYo7Nnq5 dXAiu4OnFhTXqRqFoRKvO4aWMeNPbtSE
X-Received: by 10.223.171.3 with SMTP id q3mr41442813wrc.12.1499375437168; Thu, 06 Jul 2017 14:10:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.138.207 with HTTP; Thu, 6 Jul 2017 14:10:36 -0700 (PDT)
Reply-To: sarikaya@ieee.org
In-Reply-To: <06e701d2f69a$e5adba10$b1092e30$@akayla.com>
References: <149935833402.2269.4238729858373783963.idtracker@ietfa.amsl.com> <573cd826-66f3-46cf-e191-b58b367276f3@comcast.net> <CAC8QAcf5f9BrZVfdReGN9_bmgK8Z5gn=+5frw-vUZVS9khpaWw@mail.gmail.com> <06e701d2f69a$e5adba10$b1092e30$@akayla.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Thu, 06 Jul 2017 16:10:36 -0500
Message-ID: <CAC8QAccB+GQAPTjgT=yepz-o76Q9Mv6AxMPDdwvcWTtVpD6v=A@mail.gmail.com>
Subject: Re: NomCom randomness results... delayed
To: Peter Yee <peter@akayla.com>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1b440a5148a00553ac8c08"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OsPLe-NuUhLyhryr0yEY_Mmblm4>
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:10:40 -0000

Hi Peter,


On Thu, Jul 6, 2017 at 4:00 PM, Peter Yee <peter@akayla.com> wrote:

> 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.
>
>
>

Thanks. This was not what I understood when I checked the box. Maybe it
should be made clearer in the future forms.
This is the question in the form:

Are you willing to volunteer for the Nomcom?


Behcet

>                 -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
>
>
>