Re: NomCom 2017: Call for nominations (IAOC mid-term replacement)
John C Klensin <john-ietf@jck.com> Fri, 21 September 2018 18:54 UTC
Return-Path: <john-ietf@jck.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 7BE46130E13 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 11:54:00 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 VXColKO4opEL for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 11:53:58 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96377130DD7 for <ietf@ietf.org>; Fri, 21 Sep 2018 11:53:58 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1g3QYv-000PIo-1O; Fri, 21 Sep 2018 14:53:57 -0400
Date: Fri, 21 Sep 2018 14:53:51 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Hardie <ted.ietf@gmail.com>, Bob Hinden <bob.hinden@gmail.com>
cc: IETF <ietf@ietf.org>
Subject: Re: NomCom 2017: Call for nominations (IAOC mid-term replacement)
Message-ID: <CD3E681F1D3FEB5B3B30F38B@PSB>
In-Reply-To: <CA+9kkMAJTxyGHQZB1_AmsYSDMv9WJ5HJ84TsezMx=X8os8Ltbw@mail.gmail.com>
References: <153751304247.5248.16139403406206453769.idtracker@ietfa.amsl.com> <CA+9kkMC18JMx0Oqq+frTr+bWNCXfwBRHbAk8U1upy1f8aid9=Q@mail.gmail.c om> <CA223321-E8B9-4798-B6A5-1B8EDEFEAEE0@gmail.com> <CA+9kkMAJTxyGHQZB1_AmsYSDMv9WJ5HJ84TsezMx=X8os8Ltbw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mjAreV6GiPluCvBRAtsbeGdPMT8>
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: Fri, 21 Sep 2018 18:54:00 -0000
--On Friday, September 21, 2018 11:19 -0700 Ted Hardie <ted.ietf@gmail.com> wrote: > On Fri, Sep 21, 2018 at 11:13 AM, Bob Hinden > <bob.hinden@gmail.com> wrote: > >> > And to be clear on just how abbreviated, the LLC board is >> > already >> meeting and the document which shifts the Trustee selection >> algorithm is in IETF Last Call. There is a race condition >> here that could result in this selection never actually >> serving. >> >> The trust documents are finishing IASA 2.0 w.g. last call. >> As far as I can tell none of the IASA 2.0 documents are in >> IETF last call. > Bob, > > You're right, my apologies. I saw the gen-art review pass, > and I mentally assumed I had missed the IETF Last Call. It > turns out it was triggered before the Last Call was issued. > As those on the list saw, the chairs today indicated that they > will request publication soon. > > Ted Bob and Ted, Independent of the above, I think the key question is still the one raised by Ted's note and the responses from Leslie and Glenn: even if this position were to be filled by 24 October (see https://datatracker.ietf.org/nomcom/2017/ and note that the schedule there allows zero time for community feedback), would there be enough functional work for the IAOC to do before it shuts down entirely to justify the expenditure of candidate, Nomcom, community, and IESG time to make filling the position worthwhile? If the IAOC is, by that time, just a placeholder until the IETF Trust gets sorted out, I can't imagine that a vacant position for a few weeks would be harmful enough to justify a lot of investment. Perhaps others can imagine that but, given (especially) Glenn's comments, I think they should explain. Otherwise, my conclusion is just about the same as Ted's (and Leslie's and Glenn's) even if the schedule is a bit longer: we shouldn't invest significant time in filling that position. john
- NomCom 2017: Call for nominations (IAOC mid-term … NomCom Chair 2017
- Re: NomCom 2017: Call for nominations (IAOC mid-t… Ted Hardie
- Re: NomCom 2017: Call for nominations (IAOC mid-t… Leslie Daigle
- Re: NomCom 2017: Call for nominations (IAOC mid-t… Glenn Deen
- Re: NomCom 2017: Call for nominations (IAOC mid-t… Bob Hinden
- Re: NomCom 2017: Call for nominations (IAOC mid-t… Ted Hardie
- Re: NomCom 2017: Call for nominations (IAOC mid-t… Bob Hinden
- Re: NomCom 2017: Call for nominations (IAOC mid-t… John C Klensin