Re: [ietf-nomcom] Fwd: New Version Notification for draft-dawkins-iesg-nomcom-advisor-iaoc-00.txt

"Adrian Farrel" <adrian@olddog.co.uk> Thu, 03 August 2017 09:09 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf-nomcom@ietfa.amsl.com
Delivered-To: ietf-nomcom@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 218D1131D1A for <ietf-nomcom@ietfa.amsl.com>; Thu, 3 Aug 2017 02:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 Tt9DA12epA7z for <ietf-nomcom@ietfa.amsl.com>; Thu, 3 Aug 2017 02:09:19 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CE84132325 for <ietf-nomcom@ietf.org>; Thu, 3 Aug 2017 02:09:15 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v73997PK015671; Thu, 3 Aug 2017 10:09:07 +0100
Received: from 950129200 (25.70.114.87.dyn.plus.net [87.114.70.25]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v73995g4015636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Aug 2017 10:09:06 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Spencer Dawkins at IETF' <spencerdawkins.ietf@gmail.com>, 'NomCom-Discussion' <ietf-nomcom@ietf.org>
Cc: 'Alexey Melnikov' <aamelnikov@fastmail.fm>
References: <CAKKJt-ckdcGE0_GXqRhVJkh+T8_odkD2QCOhfm-w1COWGRNcFw@mail.gmail.com>
In-Reply-To: <CAKKJt-ckdcGE0_GXqRhVJkh+T8_odkD2QCOhfm-w1COWGRNcFw@mail.gmail.com>
Date: Thu, 03 Aug 2017 10:09:04 +0100
Message-ID: <014b01d30c38$2848fc10$78daf430$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_014C_01D30C40.8A102330"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGpdmMQO+1Mp9RZkzaXlaoCeayn16LFfltw
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23234.005
X-TM-AS-Result: No--26.882-10.0-31-10
X-imss-scan-details: No--26.882-10.0-31-10
X-TMASE-MatchedRID: vWvnoyq7eMxbJCKOm3VRCaj5v7I4/SgYIZnpVU5Vh5bDWyVjzEqpvGKH pZv+RSYvnhLJWEjAGHPtP6Pv+A+w8w/80a3o2lzSIFBEE5CFomIiBIwVnqqixZAKUibQNUrS1/5 Upb6/94i8IKanJHvnZm7hbmASKcrp/auzApmkedEwEhHW5KVAzxH6y9a7QCl/QLhNmgIRxg5W3Z WqiXYbmIn3uZMbLHbFQs0ueGZxVcNBXoFkn1Z4Vt3HBFohOctM0+QbBcjoBewGEn2iDG04tq+zL yPWlXeQjlL/hujrw1tDfxQ/WK0M/Lebfccgl9iNTuOOxH2rT/HS7l9oY/zO1JJ8xD5rV15ZItI8 7B4WWSIPjOdXhbMBrmMdYzySsvg8j/xLIaDSshHIvQIyugvKdXmd+25VkQszygAO5QccC3iyn7R Jlv/chozrT6Ke+UlrT7jCYv2QJPGHxi2fvkKUM/Q1K5DO1u1D0L2eqCmMq5beqxAOXbCz6Yxj2g ynNQ8jPvm9QgHL9uBwUSK4/EeOxSOSuAnftGqPjNnoU1fopotpgrYvic2QdZ6Ss6O2bihGoEzCi UbLtjyRGA23JsTa34Dqq/69HfgsA7f8DkoYc/90PA/ki2kI7EtU4/pKr/obDsbtrO33TVeLFgnz +hpr+XW0oJLOugKBj1RGQOB2Vvn9GaYSzB/sh6Jd7mc2dRi3oEozraubH2nx6gF+AN4QjuBe5QR mIfivPwbcb/CNUOlwvDydhBUuyCAXLFyLhL5W5GdZsk1yqBeP7GAQSe5/nfbBROhn2OIGPC7j/m zpDFqfL6D8TtOZrM87s4OnYGuCwXotg6ps9+GbKItl61J/yZUdXE/WGn0FSlnU38LCY8u1MF0/q NNIN9bkrsq6X+UeRRgndEtDQrKhT7kHV6Dixgu0JaBoEGMYtF8LMRoB0lrI+LKKOeOaBJRMZUCE HkRt
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/TEn7UgMda90GMF9UIN9XhPh5k04>
Subject: Re: [ietf-nomcom] Fwd: New Version Notification for draft-dawkins-iesg-nomcom-advisor-iaoc-00.txt
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-nomcom/>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Aug 2017 09:09:22 -0000

Hey Spencer,
 
Thanks for this work. Will help the whole thing go better.
 
My gut feeling is to be nervous about "an advisor who is knowledgeable about IAOC operations" but not actually serving on the IAOC is that the input and feedback about the operation, direction, and needs of the *current* IAOC may be significantly skewed.
 
You would not, I think, suggest that the advisory part of the role of the IESG liaison could be filled by a non-serving person.
 
I do understand that you are trying to find a way in which the advisor is not selected from a pool of one. But that might be a price that is not worth paying.
 
Anyway, I see the IAOC made up as:
 
- appointed by NomCom for 2 years (odd year)
- appointed by NomCom for 2 years (even year)
- appointed by the IESG for 2 years (even year)
- appointed by the IAB for 2 years (odd year)
- appointed by the ISOC Board of Trustees for two years (even year)
- ISOC President/CEO (ex officio) (annual)
- IETF Chair (ex officio) (two year cycle, odd year)
- IAB Chair (ex officio) -(annual)
- IAD (non-voting) (annual)
 
It is debatable whether you would want any of the bottom four to be the advisor although I note that you haven't excluded them in your text.
I assume that you do not want a candidate to be the advisor (and maybe you should explicitly make that point?).
Obviously outgoing (i.e., standing down) members could be the advisor.
So in odd years you appear to have a choice of at least 3 members (possibly more if someone plans to stand down).
And in even years you appear to have a choice of at least 2 members (possibly more if someone plans to stand down).
 
I consider that preferable to allowing the IAOC to send someone who might not have the right reading of the current dynamic.
 
It should not be the case that this advisor role is a significant additional burden on the workload.
 
Thanks,
Adrian
 
From: ietf-nomcom [mailto:ietf-nomcom-bounces@ietf.org] On Behalf Of Spencer Dawkins at IETF
Sent: 02 August 2017 22:31
To: NomCom-Discussion
Cc: Alexey Melnikov
Subject: [ietf-nomcom] Fwd: New Version Notification for draft-dawkins-iesg-nomcom-advisor-iaoc-00.txt
 
Dear Nomcom Process Devotees,
 
Alissa has asked me to put together a short(!) draft that will remind future Nomcoms to request IAOC to provide an Advisor.
 
Details are below.
 
I'd like to discuss this draft on this mailing list initially.
 
Please comment and question as appropriate.
 
Thanks,
 
Spencer
 
---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Wed, Aug 2, 2017 at 4:27 PM
Subject: New Version Notification for draft-dawkins-iesg-nomcom-advisor-iaoc-00.txt
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>



A new version of I-D, draft-dawkins-iesg-nomcom-advisor-iaoc-00.txt
has been successfully submitted by Spencer Dawkins and posted to the
IETF repository.

Name:           draft-dawkins-iesg-nomcom-advisor-iaoc
Revision:       00
Title:          IAB, IESG, and IAOC Selection, Confirmation, and Recall Process: IAOC Advisor for the Nominating Committee
Document date:  2017-08-02
Group:          Individual Submission
Pages:          6
URL:            https://www.ietf.org/internet-drafts/draft-dawkins-iesg-nomcom-advisor-iaoc-00.txt
Status:         https://datatracker.ietf.org/doc/draft-dawkins-iesg-nomcom-advisor-iaoc/
Htmlized:       https://tools.ietf.org/html/draft-dawkins-iesg-nomcom-advisor-iaoc-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-dawkins-iesg-nomcom-advisor-iaoc-00


Abstract:
   This specification formalizes an ad hoc practice used to provide
   advice to the IETF Nominating Committee about the operations of the
   IETF Administrative Oversight Committee.

   This document updates RFC 7437.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat