Re: NomCom 2017: Call for nominations (IAOC mid-term replacement)
"Leslie Daigle" <ldaigle@thinkingcat.com> Fri, 21 September 2018 16:46 UTC
Return-Path: <ldaigle@thinkingcat.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 493E3130EAA for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 09:46:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=thinkingcat.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 2Vmo2Vq8d21L for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 09:46:22 -0700 (PDT)
Received: from pdx1-sub0-mail-a15.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3ED36130EC5 for <ietf@ietf.org>; Fri, 21 Sep 2018 09:46:22 -0700 (PDT)
Received: from pdx1-sub0-mail-a15.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a15.g.dreamhost.com (Postfix) with ESMTP id 9630E800FD; Fri, 21 Sep 2018 09:46:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :cc:subject:date:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=thinkingcat.com; bh=u a1TxGkBmJ94uYfHk83MUGaDuRY=; b=G54nDaQy/25y+4Pc3jV0nmENI+4THOZiv wh6X0AlbIAavX4CPkfEtRFXEod12SCHi7UIrz25b2jMRJ8jgmA6DShxJB5ZUSXJU F+LBUEtJw02GqJ0D8mBLBauM/CRo89sCuv3kTAoB+mpF63kJzOuRbYOkGfiFNE81 Zq/JerFUPI=
Received: from [169.254.23.175] (vtelinet-216-66-102-83.vermontel.net [216.66.102.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by pdx1-sub0-mail-a15.g.dreamhost.com (Postfix) with ESMTPSA id BE788800FB; Fri, 21 Sep 2018 09:46:20 -0700 (PDT)
X-DH-BACKEND: pdx1-sub0-mail-a15
X-DH-BACKEND: pdx1-sub0-mail-a15
From: Leslie Daigle <ldaigle@thinkingcat.com>
To: Peter Yee <peter@akayla.com>
Cc: IETF <ietf@ietf.org>
Subject: Re: NomCom 2017: Call for nominations (IAOC mid-term replacement)
Date: Fri, 21 Sep 2018 12:45:37 -0400
X-Mailer: MailMate (1.12r5523)
Message-ID: <A7CF9165-13B9-43BE-B871-2E3CD0AA70E7@thinkingcat.com>
In-Reply-To: <CA+9kkMC18JMx0Oqq+frTr+bWNCXfwBRHbAk8U1upy1f8aid9=Q@mail.gmail.com>
References: <153751304247.5248.16139403406206453769.idtracker@ietfa.amsl.com> <CA+9kkMC18JMx0Oqq+frTr+bWNCXfwBRHbAk8U1upy1f8aid9=Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_09E7BA33-7F3F-433D-9F15-634C68AD27B6_="
Embedded-HTML: [{"HTML":[1311, 12187], "plain":[702, 10382], "uuid":"186202B1-9022-4166-BC54-0F7162D28F21"}]
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Oohc72gxdqFv3dRV95tyVgiWMHk>
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 16:46:35 -0000
What Ted said, plus: the wording of your note, and the lack of announcement from the IAOC to say they are looking to fill that position, leaves me with a question. Did the IAOC ask/does the IAOC believe the position needs to be filled? That’s not a Nomcom decision — from RFC 7437: “ The nominating committee does not select the open positions to be reviewed; it is instructed as to which positions to review.” Leslie. -- ------------------------------------------------------------------- Leslie Daigle Principal, ThinkingCat Enterprises ldaigle@thinkingcat.com ------------------------------------------------------------------- On 21 Sep 2018, at 12:29, Ted Hardie wrote: > Greetings, > > A few observations in-line, as an individual. > > On Thu, Sep 20, 2018 at 11:57 PM, NomCom Chair 2017 < > nomcom-chair-2017@ietf.org> wrote: > >> Greetings from the 2017-2018 NomCom! >> >> No, you have not entered another one of our time loops. The >> 2017-2018 >> NomCom continues to exist for special needs until the end of the >> Bangkok >> IETF meeting. And we find ourselves in one of those special needs >> situations at the moment. As you are probably aware, Andrew Sullivan >> has >> stepped down from his NomCom-selected position on the IAOC. > > > Just to note that Andrew's new position as ISOC CEO makes him an *ex > officio *member, so he remains on the IAOC. Kathy Brown, the previous > CEO, > is the member who has actually dropped. It is the shift in role which > means it is the NomCom's job to consider how to fill the position. > > >> RFC 7437 indicates that mid-term vacancies are the responsibility of >> the >> previous NomCom (i.e., not the 2018-2019 NomCom), so that’s why you >> are >> hearing from me. >> >> Now you will be aware that the IETF LLC Board will supplant the IAOC >> sooner or later. Hopefully sooner. The IETF Trust draws its >> trustees from >> the IAOC, but going forward that will obviously change since there >> will no >> longer be an IAOC. Until then, the replacement of IETF Trust >> trustees is >> done through the replacement of IAOC members. Thus, the 2017-2018 >> NomCom >> needs nominees who are willing to serve on the IAOC (and IETF Trust) >> for >> what will likely be an abbreviated period. > > > 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. > > > >> To be very clear, this call for nominees is distinct from the >> on-going >> efforts of the 2018-2019 NomCom. That NomCom is already hard at work >> to >> fill IESG, IAB, and LLC Board positions. >> >> This is a call for nominations to the IAOC. We need one person to >> fill >> out the remainder of Andrew’s appointment to the IAOC and the >> corresponding >> service to the IETF Trust. The role will exist until both the IAOC >> is >> ended and the IETF Trust is placed under the IETF LLC with the new >> rules >> that are being drafted for the selection of trustees. >> > > The Trust is not going under the LLC. The Trust will have a new > selection > method for its members, rather than re-using the IAOC as a pool, but > it is > and will remain a distinct legal entity. I'll also point out that > Andrew > remains a Trustee, since he remains on the IAOC because of his new > role. > It is Kathy Brown who is no longer a Trustee. > > > >> While it may seem like a fair amount of effort to seat a replacement >> for >> Andrew on the IAOC, I believe this is the prudent move to make. I do >> not >> wish to set a precedent that the IETF NomCom selectively submits to >> its >> responsibilities under RFC 7437 by choosing whether to make a >> selection. >> And if the new handling of trustee selection takes longer to put into >> place >> than projected, it would be a good if not critical thing to have a >> full set >> IETF Trust trustees available. I’ve conferred with the members of >> the >> NomCom and we are prepared to make the effort to select a new IAOC >> candidate. We are aware that this is a heavyweight process for >> what is a fairly lightweight need, so we appreciate the >> community’s >> support in completing our work. I do realize that there are those in >> the >> community who advocate dispensing with the rules and not making the >> appointment, but I prefer to take a conservative approach and follow >> the >> ratified directions of the community in this matter by adhering to >> RFC >> 7437. As always, the IETF mailing list is available to debate the >> matter, >> perhaps with an eye towards a future revision of RFC 7437. >> >> > That very RFC 7437 complicates the matter by giving a 6-week time > frame in >> which the replacement must be made. (A discussion of amending RFC >> 7437 in >> that regard would be interesting after we are done here, but is >> outside of >> the NomCom’s jurisdiction.) The timer started when we were >> notified of >> Andrew’s resignation – that notification came on September 11, >> 2018 and it >> has taken us a while to determine and prepare for our next steps. >> Those >> next steps are to find a replacement for Andrew as expeditiously as >> we >> can. We have a deadline of October 23rd for completion of the >> selection >> and confirmation process. >> >> I appreciate the NomCom's fidelity to its duty and I thoroughly >> understand > why they do not wish to selectively assume their responsibilities. > But > I'll point an option here that can be taken by the community to avoid > the > bureaucratic hassle of actually adding someone to the IAOC for a term > that > may be minutes long: > > No one volunteers. > > If there are no volunteers, the section 5.1 of RFC 7437 quite clearly > applies: > > 5.1 <https://tools.ietf.org/html/rfc7437#section-5.1>. Discretion > > All rules and special circumstances not otherwise specified are at > the discretion of the committee. > > Exceptional circumstances will occasionally arise during the normal > operation of the nominating committee. This rule is intended to > foster the continued forward progress of the committee. > > Any member of the committee may propose a rule for adoption by the > committee. The rule must be approved by the committee according to > its established voting mechanism. > > All members of the committee should consider whether the exception > is > worthy of mention in the next revision of this document and > follow-up > accordingly. > > I believe that if no one volunteers, the NomCom gains the discretion > to do > nothing, which is the sensible thing to do when faced with a > bureaucratic > necessity of no practical impact and of our own making. > > So, my personal advice to those considering volunteering: you serve > the > community better by giving the NomCom the discretion to do nothing at > all. > > Ted > > > > >> To that end, the 2017-2018 Nominating Committee is seeking >> nominations >> from now until September 26, 2018. We are aware that is not a lot of >> time >> for interested parties, but the overall timeline is highly >> compressed. >> Details for the timeline can be found on the NomCom’s home page: >> >> https://datatracker.ietf.org/nomcom/2017/ >> >> Nominations may be made by selecting the Nominate link at the top of >> the >> NomCom 2017 home page, or by visiting the following URL: >> >> https://datatracker.ietf.org/nomcom/2017/nominate/ >> >> {Note that nominations made using the web tool require an ietf.org >> datatracker account. You can create a datatracker ietf.org account >> if you don't have one already by visiting the following URL: >> https://datatracker.ietf.org/accounts/create/ } >> >> If you are unable to use the web form, nominations may instead be >> made by >> email to nomcom-17 at ietf dot org. If using email, please include >> the word >> "Nominate" in the Subject and indicate in the email who is being >> nominated >> and their email address (to confirm acceptance of the nomination). >> If you are nominating someone other than yourself, please tell us if >> we >> may tell the nominee that you were the one who made the nomination. >> >> Self-nomination is welcome! >> >> Desired expertise for this position is the same as for any other IAOC >> member selection. The write-up for the desired expertise can be >> found at: >> >> https://datatracker.ietf.org/nomcom/2017/expertise/#iaoc-short-term-member >> >> Willing nominees are asked to fill out a questionnaire. The >> questionnaire >> is available now and is due back to the NomCom by October 3rd. We >> realize >> that NomCom questionnaires are fairly lengthy. Nominees are simply >> asked >> to fill it out as best as can be done. Since we may not have enough >> time >> to interview nominees (there being little time as it is and >> interviews >> possibly being difficult to coordinate), we will be relying heavily >> on >> community feedback and what can be gleaned from the questionnaires. >> Feedback may immediately be submitted for all nominees who accept >> their >> nomination. While NomComs generally prefer to open feedback at a >> specified >> point in time after nominations are closed, our tight schedule does >> not >> permit this luxury, and therefore we are taking immediate feedback. >> The >> deadline for feedback is also October 3rd. >> >> NomCom 2017-2018 follows the policy for "Open Disclosure of Willing >> Nominees" described in BCP 10/RFC 7437. As stated in RFC 7437: "The >> list >> of nominees willing to be considered for positions under review in >> the >> current NomCom cycle is not confidential". Willing nominees for this >> position will be listed in a publicly accessible way, e.g., anyone >> with a >> datatracker account may access the lists. Additionally, the >> nomination >> form asks if we may share your own name with the nominee. In all >> other >> ways, the confidentiality requirements of BCP 10 remain in effect. >> All >> feedback and all NomCom deliberations will remain confidential and >> will not >> be disclosed. >> >> There is a field on the form you can mark in order to allow the >> NomCom to >> tell the nominee that you were the one who made the nomination. This >> defaults to “no” - so if you don't mark the field we won’t >> tell. >> >> In order to ensure time to collect sufficient community feedback >> about >> each of the willing nominees, nominations must be received by the >> NomCom on >> or before September 26, 2018. >> >> Please submit your nominations as early as possible for the sake of >> your >> nominees. Note that nominations should not wait for management >> permission, >> as it is easier to decline the nomination than put one in late. >> >> You are welcome to contact the entire NomCom at nomcom-17 at ietf dot >> org >> with your input and questions. If you are having troubles with the >> NomCom >> website such as nominating someone, filling out a questionnaire, or >> providing nominee feedback, please let me know directly at the >> addresses >> given below. >> >> Thank you for your help in identifying qualified nominees! >> >> Peter Yee >> NomCom Chair 2017-18 >> nomcom-chair-2017 at ietf dot org >> peter at akayla dot com >> >>
- 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