RE: NomCom is Open for Community Feedback

"STARK, BARBARA H" <bs7652@att.com> Fri, 16 October 2020 12:53 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 7B0653A0F1D for <ietf@ietfa.amsl.com>; Fri, 16 Oct 2020 05:53:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 h5hpiLFXKKZS for <ietf@ietfa.amsl.com>; Fri, 16 Oct 2020 05:53:27 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 DD63C3A0F1C for <ietf@ietf.org>; Fri, 16 Oct 2020 05:53:26 -0700 (PDT)
Received: from pps.filterd (m0049458.ppops.net [127.0.0.1]) by m0049458.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id 09GCqrie046180; Fri, 16 Oct 2020 08:53:25 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049458.ppops.net-00191d01. with ESMTP id 3469qdnptb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 16 Oct 2020 08:53:25 -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 09GCrO1t009837; Fri, 16 Oct 2020 08:53:25 -0400
Received: from zlp30488.vci.att.com (zlp30488.vci.att.com [135.47.91.93]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 09GCrKuD009775 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 16 Oct 2020 08:53:20 -0400
Received: from zlp30488.vci.att.com (zlp30488.vci.att.com [127.0.0.1]) by zlp30488.vci.att.com (Service) with ESMTP id CD1B6400AF90; Fri, 16 Oct 2020 12:53:20 +0000 (GMT)
Received: from GAALPA1MSGEX1CF.ITServices.sbc.com (unknown [135.50.89.113]) by zlp30488.vci.att.com (Service) with ESMTPS id B6079400AF73; Fri, 16 Oct 2020 12:53:20 +0000 (GMT)
Received: from GAALPA1MSGEX1CB.ITServices.sbc.com (135.50.89.109) by GAALPA1MSGEX1CF.ITServices.sbc.com (135.50.89.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2044.4; Fri, 16 Oct 2020 08:53:08 -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.006; Fri, 16 Oct 2020 08:53:08 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: 'Bob Hinden' <bob.hinden@gmail.com>
CC: 'IETF' <ietf@ietf.org>
Subject: RE: NomCom is Open for Community Feedback
Thread-Topic: NomCom is Open for Community Feedback
Thread-Index: AQHWo0K4sQkHjt/ICUij0ct7sWo14amZjIGAgACaCcA=
Date: Fri, 16 Oct 2020 12:53:07 +0000
Message-ID: <eaeee2b0c62445f6909e571c3a5ea45d@att.com>
References: <160280093891.25177.8409710768708519471@ietfa.amsl.com> <FA51045C-15C6-456A-95B5-90D53B904A67@gmail.com>
In-Reply-To: <FA51045C-15C6-456A-95B5-90D53B904A67@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.10.114.218]
x-tm-snts-smtp: E085F359F5D979CDF9BF7722715DF657D2365784682D9148105747EEE64D0C422
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-10-16_06:2020-10-16, 2020-10-16 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 impostorscore=0 adultscore=0 malwarescore=0 bulkscore=0 phishscore=0 spamscore=0 suspectscore=0 mlxlogscore=999 mlxscore=0 priorityscore=1501 clxscore=1011 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2010160094
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X3RsDZ9J9dsmvD7PgHGLcf8-HT4>
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, 16 Oct 2020 12:53:29 -0000

Hi Bob,

> Barbara,
> 
> I see that at the end of the feedback form there are three topics:
> 
>   IESG Expectations of Proposed Standard
>   IESG and IAB as servants of the community
>   Engaging with external, impacted stakeholders
> 
> Could you provide more background on what the NomCom is looking for?
> The current descriptions are a bit sparse.

Thanks for asking.
Apparently I forgot to include the ietf list on my previous Announcement. <sigh>
No wonder (hopefully that's the reason) I got so little feedback.
https://datatracker.ietf.org/nomcom/ann/202641/

Summary: Several people have provided comments to NomCom on topics they'd
like us to keep in mind as we go through our process. But we need to get more community 
input on these topics to get a better sense of what the overall community thinks. We
also need to know if there are other topics to consider.
 
I've copied the text of that Announcement below, so you don't have to follow the link.
It provides more about the source of the first two topics. The 3rd topic (engaging with
external stakeholders) was about how the IESG should relate with non-technical forums 
and stakeholders that are affected by the non-technical consequences of new IETF 
standards, like governments and regulators. I'll ask the originator of that topic to
either send more on that to the ietf list to generate discussion or for 
permission to include the text provided to NomCom.
Thx,
Barbara

=========== Announcement sent last week =======

Hi IETFers,
NomCom has entered a "quiet" week where nominations are now closed 
and feedback on nominees hasn't started (the nominees have through 
October 13 to accept nominations and provide questionnaire responses; 
NomCom opens up for nominee feedback on Oct 14).

But "quiet" is boring. So I'd like to use this opportunity to encourage input on "Topics". 

We've received input and feedback on some broader IETF issues from 
some people. To get a better sense of where the community stands 
on these Topics (and to know if there are other Topics we should think 
about when interviewing nominees and selecting candidates), we need 
more community input. These Topics are intended to help provide 
NomCom with guidance and prioritization on what values and 
competencies the community would like to see represented in both the 
individual and the holistic composition of its leadership.

Topics received so far are listed on 
https://datatracker.ietf.org/nomcom/2020/feedback/

They are: 
- IESG expectations of Proposed Standard
- IESG and IAB as servants of the community

In case you're wondering, these were taken from Brian Carpenter's open 
letter to NomCom (https://www.ietf.org/id/draft-carpenter-nomcom2020-letter-00.html). 
We also received some similar input (not from Brian) during IETF 108 
NomCom office hours.

There are many good ways for you to provide input to NomCom on 
broader (not nominee-specific) topics:
1. Discussion on the ietf email list (for those who feel comfortable doing so)
2. Go to https://datatracker.ietf.org/nomcom/2020/feedback/ , click on 
one of the Topics listed at the right, and enter your thoughts (an excellent 
mechanism for those not fully comfortable with the ietf list)
3. An email to nomcom20@ietf.org (also an excellent mechanism for 
those not comfortable with the ietf list, and can be used to suggest new 
topics as well as comment on existing topics)
4. Attend our Office Hours (dates and times in November to be announced)

NomCom is expected to represent the IETF community. We need your 
thoughtful input and feedback to do this well.

Next week I'll send an announcement calling for nominee feedback.