RE: Additional advisors (was: RE: Challenge: Re: Challenge: was Re: Updated Nomcom 2020-2021: Result of random selection process)
"STARK, BARBARA H" <bs7652@att.com> Thu, 16 July 2020 22:37 UTC
Return-Path: <bs7652@att.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 CF7403A0DBD for <ietf@ietfa.amsl.com>; Thu, 16 Jul 2020 15:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 9AWtSfvkjBb3 for <ietf@ietfa.amsl.com>; Thu, 16 Jul 2020 15:37:45 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 EF39D3A0DBB for <ietf@ietf.org>; Thu, 16 Jul 2020 15:37:45 -0700 (PDT)
Received: from pps.filterd (m0049287.ppops.net [127.0.0.1]) by m0049287.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id 06GMWeIs045651 for <ietf@ietf.org>; Thu, 16 Jul 2020 18:37:45 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049287.ppops.net-00191d01. with ESMTP id 32afrkj1c8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf@ietf.org>; Thu, 16 Jul 2020 18:37:45 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 06GMbgBB009145 for <ietf@ietf.org>; Thu, 16 Jul 2020 18:37:44 -0400
Received: from zlp30484.vci.att.com (zlp30484.vci.att.com [135.47.91.179]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 06GMbdl3008924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Thu, 16 Jul 2020 18:37:40 -0400
Received: from zlp30484.vci.att.com (zlp30484.vci.att.com [127.0.0.1]) by zlp30484.vci.att.com (Service) with ESMTP id 8F9794009E63 for <ietf@ietf.org>; Thu, 16 Jul 2020 22:37:39 +0000 (GMT)
Received: from GAALPA1MSGEX1CB.ITServices.sbc.com (unknown [135.50.89.109]) by zlp30484.vci.att.com (Service) with ESMTPS id 72DE64009E72 for <ietf@ietf.org>; Thu, 16 Jul 2020 22:37:39 +0000 (GMT)
Received: from GAALPA1MSGEX1CB.ITServices.sbc.com (135.50.89.109) by GAALPA1MSGEX1CB.ITServices.sbc.com (135.50.89.109) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2044.4; Thu, 16 Jul 2020 18:37:35 -0400
Received: from GAALPA1MSGEX1CB.ITServices.sbc.com ([135.50.89.109]) by GAALPA1MSGEX1CB.ITServices.sbc.com ([135.50.89.109]) with mapi id 15.01.2044.004; Thu, 16 Jul 2020 18:37:35 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Additional advisors (was: RE: Challenge: Re: Challenge: was Re: Updated Nomcom 2020-2021: Result of random selection process)
Thread-Topic: Additional advisors (was: RE: Challenge: Re: Challenge: was Re: Updated Nomcom 2020-2021: Result of random selection process)
Thread-Index: AQHWWiugysM1WKO48kC0CwfJJehNyKkI71IAgAATLQCAABX/AIAAGE0AgAAAr4CAAAX/gIABlmHg
Date: Thu, 16 Jul 2020 22:37:35 +0000
Message-ID: <e81d188fc8c44a18b4ccb0972f991b65@att.com>
References: <20200713234315.GA21036@faui48f.informatik.uni-erlangen.de> <EC4D8627-D7B1-4665-9EC7-ABC3C360D832@comcast.net> <20200714035329.GA59164@faui48f.informatik.uni-erlangen.de> <6.2.5.6.2.20200714005918.0f811330@elandnews.com> <alpine.OSX.2.23.453.2007140745300.92835@samuels-air> <85e2c2a29dd74c63b9b3650a1a1a9f2f@att.com> <alpine.OSX.2.23.453.2007141755040.855@samuels-air> <CABmDk8n+bq50KrWzjkpfQUfOGRyqwDL_fnKQAhMfkiVVvcu3kQ@mail.gmail.com> <61AF0161-547E-4A27-B043-C706E420E3BB@sobco.com> <CAJc3aaMaGeKvYuOUWEG_EcY8+eLiMURcM+_q3LiD+VJFahpZ2A@mail.gmail.com> <A84DB5F4-2646-49BA-81DD-4944D5DE71BD@episteme.net> <9A20A23A-986F-4908-9FEE-B8A1FBB6438D@sobco.com> <57BA52BD-836D-4FFD-8678-E2413099805B@episteme.net>
In-Reply-To: <57BA52BD-836D-4FFD-8678-E2413099805B@episteme.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.10.65.193]
x-tm-snts-smtp: 8E1C5B1FB1D5D1B60899EB3469D085AD8F6F3D860A20115DB6B86F849322B1232
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-07-16_11:2020-07-16, 2020-07-16 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 malwarescore=0 priorityscore=1501 clxscore=1015 suspectscore=0 phishscore=0 adultscore=0 impostorscore=0 mlxlogscore=999 lowpriorityscore=0 mlxscore=0 spamscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2006250000 definitions=main-2007160146
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yEA7pDIWzxSHerdhqdXx8nGFlDA>
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: Thu, 16 Jul 2020 22:37:48 -0000
Thank you all for your advice regarding advisors. I'm putting discussion of advisors on the agenda for my initial NomCom meeting. <attempt at humor>I'm tempted to add ietf@ietf.org as an additional advisor -- but not one with access to confidential info.</attempt at humor> Barbara > -----Original Message----- > From: Pete Resnick > > On 15 Jul 2020, at 12:57, Scott O. Bradner wrote: > > > is there something I missed where the chair said that was happening > > (Henrik would be able to vote on procedures or candidates?) > > It sounded from the chair's note of Tue, 14 Jul 2020 21:08:28 +0000 that she > thought that the assorted additional folks in question were already > appointed as advisors. Sam pointed out that if they were advisors, they > would have the ability to vote on procedures, and therefore their > appointment as advisors ought to be approved by the voting members. > (Nobody thought they could vote on candidates, but only that they would be > part of the deliberations.) After Sam's note, Mary, Victor, and you replied > with defenses of Henrik being the tools advisor. That seemed curious, since > none of you addressed Sam's point, and nobody ever suggested that Henrik > shouldn't be tools advisor, which is why I replied. > > pr > > >> On Jul 15, 2020, at 1:54 PM, Pete Resnick <resnick@episteme.net> > >> wrote: > >> > >> Nobody objected to Henrik (or anyone else) being the Tools Advisor, > >> or to any of the other non-8713-listed advisors being on NomCom. The > >> only concern is that the voting members and the 8713-listed > >> non-voting members need to explicitly decide whether or not they will > >> (a) participate in deliberations and (b) be able to vote on > >> procedural matters of the NomCom. The chair can't simply add > >> additional advisors who can vote to change the procedures of the > >> NomCom without the approval of the voting members of the NomCom. > >> > >> pr > >> > >> On 15 Jul 2020, at 11:27, Victor Kuarsingh wrote: > >> > >> > >> > >> On Wed, Jul 15, 2020 at 11:09 AM Scott O. Bradner <sob@sobco.com> > >> wrote: > >> Henrik has been tools advisor just about forever - well he was the > >> tools advisor back when I was on the IESG - he came with the job as > >> nomcom chair - I do not recall that previous chairs specifically > >> appointed him he was just "it" > >> > >> but the key point is in the citation you provide " advisor to > >> participate in some or all of the deliberations of the committee" > >> > >> the tools advisor does not "participate in some or all of the > >> deliberations of the committee" > >> so is not covered under RFC 8713 section 4.3 - the chair has the > >> power to appoint advisors that do not participate in some or all of > >> the deliberations of the committee as long as the advisor has minimal > >> contact with the confidential information the nomcom collects (and > >> Henrik can be trusted with confidential information in any case > >> - he has been there & done that > >> > >> I say 'move on, there is nothing to do here' > >> > >> > >> Having worked with him on Nomcom, I have no concerns with his > >> involvement as a tools advisor. > >> > >> regards, > >> > >> Victor K > >> > >> > >> > >> Scott > >> > >>> On Jul 15, 2020, at 10:00 AM, Mary B <mary.h.barnes@gmail.com> > >>> wrote: > >>> > >>> I'm very puzzled over the concern about Henrik as Tools Advisor. He > >>> was tools advisor way back when I was Nomcom chair 2009-2010 and I > >>> know it goes back at least to the one prior. He has been an > >>> essential part of the process from that perspective. But, he did not > >>> (and I assume still does not) participate in any deliberations at > >>> all and as I recall he actually can't see any of the comments input > >>> by the community. But, his role has a dramatic impact on the > >>> ability of the nomcom to review the community input in the form > >>> other than a bunch of emails and of course, his work also has > >>> provided the community a nice tool so that we can provide that > >>> input. > >>> > >>> As far as other advisors, I will add that I do think it's important > >>> that their roles are clear cut from the outset in terms of the scope > >>> being providing input into the specific roles for the organization > >>> they represent or in the case of Suresh on process aspects. There > >>> had been Nomcoms where liaisons were more active, which I disagree > >>> with, but it is up to the specific Nomcom in terms of how they take > >>> input. > >>> > >>> If the concern is that there will be lots of folks that can see your > >>> input to the Nomcom, you can always provide input anonymously by > >>> contacting the chair or a Nomcom member with whom you're > comfortable > >>> sharing. > >>> > >>> Regards, > >>> Mary.. > >>> > >>> On Tue, Jul 14, 2020 at 5:11 PM Samuel Weiler <weiler@csail.mit.edu> > >>> wrote: > >>> On Tue, 14 Jul 2020, STARK, BARBARA H wrote: > >>> > >>>> I needed the tools advisor in place when I started the volunteer > >>>> process. > >>> > >>> ..... > >>> > >>>> I also asked Suresh to be an advisor, as permitted by RFC 8713. > >>> > >>> My read of RFC8713 section 4.3 is that you are not premitted to > >>> appoint advisors on your own. The relevant text is: > >>> > >>> Any committee member may propose the addition of an advisor to > >>> participate in some or all of the deliberations of the > >>> committee. > >>> The addition must be approved by the committee according to its > >>> established voting mechanism. > >>> > >>> I do not object to you having sought advice from Henrik and Suresh > >>> up to this point, but, as I wrote this morning, I hope that you will > >>> propose these new advisors to the NomCom once it is seated and give > >>> the NomCom (excluding the two proposed additions) the opportunity to > >>> approve the additions (or not, as they deem appropriate). > >>> > >>> I look forward to your confirmation that you will take this path. > >>> > >>> -- Sam > >>> > >>> > >>>>> From: Samuel Weiler > >>>>> Sent: Tuesday, July 14, 2020 6:46 AM > >>>>> > >>>>> On Tue, 14 Jul 2020, S Moonesamy wrote: > >>>>> > >>>>>> There is a special past-past chair advisor. The explanation for > >>>>>> that is "this year is so strange". Making such an appointment > >>>>>> was not discussed during the evaluation of the document which was > >>>>>> published as RFC 8788. There isn't any information about which > >>>>>> rule(s) was used to make that appointment. > >>>>> > >>>>> The list at [1] also includes Henrik as a tools team advisor. > >>>>> > >>>>> One might presume that the NomCom chair intends to propose both > >>>>> additional advisors to the NomCom according to the usual process > >>>>> in section > >>>>> 4.3 of RFC8713. It is odd to see them announced before the voting > >>>>> memebers of NomCom are seated. > >>>>> > >>>>> It is interesting how the number of non-voting NomCom members > has > >>>>> grown over time. This list has nine(!) non-voting members, and > >>>>> that is before the voting members have been seated and potentially > >>>>> added more. > >>>>> NomCom 2019 had 8. NomCom 2018 had 7. NomCom 2017 had 6. > >>>>> NomComs 2016 and 2015 each had only 5. [2] > >>>>> > >>>>> If I were a voting member of this NomCom, I would be concerned > >>>>> about being overwhelmed by advisors, particularly since the > >>>>> advisors get a vote on procedural matters, including the removal > >>>>> of voting NomCom members.. > >>>>> > >>>>> -- Sam > >>>>> > >>>>> > >>>>> [1] > >>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.i > >>>>> etf.org_nomcom_2020_&d=DwIBAg&c=LFYZ- > o9_HUMeMTSQicvjIg&r=LoGzhC-8s > >>>>> > c8SY8Tq4vrfog&m=gkzPWOkPAQyFQsbmEULkAewFDOyYuyMoKwrrVakfltE& > s=8yKW > >>>>> gNsk2Epq1ZhvoSr6J2ABEbMfJAtdAqt_pgaroNE&e= > >>>>> > >>>>> [2] n.b. I'm looking at the lists at [1]. It is possible these > >>>>> NomComs added advisors that are not listed. I'm pretty sure > >>>>> NomCom > >>>>> 2015 added Henrik as an advisor. > > > -- > Pete Resnick https://urldefense.proofpoint.com/v2/url?u=https- > 3A__www.episteme.net_&d=DwIBAg&c=LFYZ- > o9_HUMeMTSQicvjIg&r=LoGzhC- > 8sc8SY8Tq4vrfog&m=gkzPWOkPAQyFQsbmEULkAewFDOyYuyMoKwrrVakflt > E&s=BbE9_ilXns8O1nds-mZq0_gNF-6Y7oYu-z0FWo9zmcQ&e= > All connections to the world are tenuous at best
- Updated Nomcom 2020-2021: Result of random select… NomCom Chair 2020
- Challenge: was Re: Updated Nomcom 2020-2021: Resu… Michael StJohns
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Salz, Rich
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Mary B
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Kyle Rose
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … John C Klensin
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Yoav Nir
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Samuel Weiler
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Martin Duke
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Michael StJohns
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Olafur Gudmundsson
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Joseph Touch
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Benjamin Kaduk
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Joseph Touch
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Benjamin Kaduk
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Melinda Shore
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Joseph Touch
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Yoav Nir
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Yoav Nir
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Yoav Nir
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Eliot Lear
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Michael StJohns
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Yoav Nir
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Yoav Nir
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Rob Sayre
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Brian E Carpenter
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Mike StJohns
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Victor Kuarsingh
- RE: Challenge: was Re: Updated Nomcom 2020-2021: … STARK, BARBARA H
- RE: Challenge: was Re: Updated Nomcom 2020-2021: … Vittorio Bertola
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Eliot Lear
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Michael StJohns
- RE: Challenge: was Re: Updated Nomcom 2020-2021: … STARK, BARBARA H
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Michael StJohns
- Challenge: Re: Challenge: was Re: Updated Nomcom … Toerless Eckert
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Mike StJohns
- Re: Challenge: Re: Challenge: was Re: Updated Nom… John C Klensin
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Toerless Eckert
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Toerless Eckert
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Benjamin Kaduk
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Rob Sayre
- Re: Challenge: Re: Challenge: was Re: Updated Nom… John C Klensin
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Toerless Eckert
- Re: Challenge: Re: Challenge: was Re: Updated Nom… S Moonesamy
- RE: Challenge: was Re: Updated Nomcom 2020-2021: … Mehmet Ersue
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Samuel Weiler
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Victor Kuarsingh
- Re: Challenge: Re: Challenge: was Re: Updated Nom… S Moonesamy
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Victor Kuarsingh
- RE: Challenge: Re: Challenge: was Re: Updated Nom… STARK, BARBARA H
- Additional advisors (was: RE: Challenge: Re: Chal… Samuel Weiler
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Warren Kumari
- Re: Additional advisors (was: RE: Challenge: Re: … John C Klensin
- Re: Additional advisors (was: RE: Challenge: Re: … Mary B
- Re: Additional advisors (was: RE: Challenge: Re: … Scott O. Bradner
- Re: Additional advisors (was: RE: Challenge: Re: … Victor Kuarsingh
- Re: Additional advisors (was: RE: Challenge: Re: … Michael Richardson
- Re: Additional advisors (was: RE: Challenge: Re: … Pete Resnick
- Re: Additional advisors (was: RE: Challenge: Re: … Scott O. Bradner
- Re: Additional advisors (was: RE: Challenge: Re: … John C Klensin
- Re: Additional advisors (was: RE: Challenge: Re: … Samuel Weiler
- Re: Additional advisors (was: RE: Challenge: Re: … Pete Resnick
- RE: Additional advisors (was: RE: Challenge: Re: … STARK, BARBARA H
- Re: Additional advisors (was: RE: Challenge: Re: … Randy Bush
- Re: Additional advisors Brian E Carpenter