Re: NomCom is Open for Community Feedback
Bob Hinden <bob.hinden@gmail.com> Fri, 16 October 2020 15:34 UTC
Return-Path: <bob.hinden@gmail.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 742CC3A0F9E for <ietf@ietfa.amsl.com>; Fri, 16 Oct 2020 08:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 lYn4g94lBlLP for <ietf@ietfa.amsl.com>; Fri, 16 Oct 2020 08:34:14 -0700 (PDT)
Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AB2A3A0F99 for <ietf@ietf.org>; Fri, 16 Oct 2020 08:34:14 -0700 (PDT)
Received: by mail-wm1-x330.google.com with SMTP id q5so3428443wmq.0 for <ietf@ietf.org>; Fri, 16 Oct 2020 08:34:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=TPg1o1ZV3IWUmyjHEhWz1x+3cKXqAhfGe/F6bOjYLlc=; b=KFQwl58QfY/R6VyORjTZ8xSpH0wM1TuHH2nSvMUPZelJOaeV1Gnp23iEJmK50n2n5z k5OE8flce6E78ZVqaOt64TXl2eh9RKa0esfQuaIqs5JWXoXNnZ86T1tLJce6kPBBYtCw kOIO0TdOb6d6ztsdaWj/RmD5+uZL0pk6nlAjX6fCtW82qWPvDnzDW/dlx4YOZLGHcaTt PQr1UbaD1MVeZCKGLQ9MrnqeBQ2l+2zHHDurlxqSax+iBrXeUHWERffY/v9LpM8gwpoS u72E9cid1z+6gw4sDal91ZcYvcpYgW0Q4UbVRhBQi600CXAXYxmYmdAoEaOw9gNTB916 Fpyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=TPg1o1ZV3IWUmyjHEhWz1x+3cKXqAhfGe/F6bOjYLlc=; b=KsAR9Wi1axTOzhgjtBHZ4J5a7/RFvbkb4ZJioyRZQDy50w5NZKHYni8mcT2sx5DNxX SVYn48Xqe88hMOpOJUsY3JHcOjSQF7MDhYjF2clJzbhoAQCQJrFPfnP10Hia9KrZt9xo ClmGafHUA2g4q1ZpH95FusDf+U8TvZNtj/Ov8SSoavZ5kbFLkt0HH3pNSWyXGa9gEK3f BEFDJXU1TrCmxjfzGpu47bdPC5qVba/ixuflXKqGt0oPCgiveyDvQlHfcNz50Z7L3FhG p2+I3ZqDNGjyKnzti4nDAJ7SIThIJP8ixeUUlBpjvvK+0wvsGADKHTEyqYruKkymI7+F XOQQ==
X-Gm-Message-State: AOAM533X+2FgeFybeix/GIvFPNrdm7EQIdTd2rcs4caqsB0R/iU8M8HD LCQZbBJE41i9y0qGyTFhAFA=
X-Google-Smtp-Source: ABdhPJxm54LNJyvO/db1FQtyxh13hpzQREGZAyqYInkwYTlTVBQl58o/nn2YspRXEkgknaKJZ5yfCg==
X-Received: by 2002:a7b:c08c:: with SMTP id r12mr4155332wmh.184.1602862452881; Fri, 16 Oct 2020 08:34:12 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:8c25:bc1:6706:fa4a? ([2601:647:5a00:ef0b:8c25:bc1:6706:fa4a]) by smtp.gmail.com with ESMTPSA id u6sm3073920wmj.40.2020.10.16.08.34.10 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Oct 2020 08:34:11 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <EDC2297C-B5EC-4DE5-A7EF-D2D7CB972308@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E8CA9646-127E-45AA-983B-F10284E841DA"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Subject: Re: NomCom is Open for Community Feedback
Date: Fri, 16 Oct 2020 08:34:08 -0700
In-Reply-To: <eaeee2b0c62445f6909e571c3a5ea45d@att.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
To: "STARK, BARBARA H" <bs7652@att.com>
References: <160280093891.25177.8409710768708519471@ietfa.amsl.com> <FA51045C-15C6-456A-95B5-90D53B904A67@gmail.com> <eaeee2b0c62445f6909e571c3a5ea45d@att.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jZOQjUhYtVeLO5LdAyR7zi5spUI>
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 15:34:16 -0000
Barbara, Thanks, very helpful. Bob > On Oct 16, 2020, at 5:53 AM, STARK, BARBARA H <bs7652@att.com> wrote: > > 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.
- NomCom is Open for Community Feedback NomCom Chair 2020
- Re: NomCom is Open for Community Feedback Toerless Eckert
- Re: NomCom is Open for Community Feedback Bob Hinden
- RE: NomCom is Open for Community Feedback STARK, BARBARA H
- Re: NomCom is Open for Community Feedback tom petch
- RE: NomCom is Open for Community Feedback Adrian Farrel
- RE: NomCom is Open for Community Feedback STARK, BARBARA H
- Re: NomCom is Open for Community Feedback Bob Hinden