Re: [Gendispatch] A gendispatch session at IETF 118?
"Salz, Rich" <rsalz@akamai.com> Tue, 26 September 2023 15:17 UTC
Return-Path: <rsalz@akamai.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B52DCC14F73E; Tue, 26 Sep 2023 08:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G91dOOABxS1h; Tue, 26 Sep 2023 08:17:04 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 D22A2C14F74A; Tue, 26 Sep 2023 08:17:03 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.17.1.22/8.17.1.22) with ESMTP id 38Q9s1I7019292; Tue, 26 Sep 2023 16:17:02 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h= from:to:cc:subject:date:message-id:references:in-reply-to :content-type:mime-version; s=jan2016.eng; bh=SO0M3IW/6Ucnr905UH B4nvIOrXmRYUM8R+g7oH5Oblc=; b=BjYT3uaZjfVFrtRzdzfdYsqQS7rYRstq8Z Iqa1Zs02v770U6Osvc9CqcXIE2uI9ud2rtQoGZiDD4pv7e/AXkVjSPfS4G4aiQqv QULyeOPgeWVsRkFX9KZ+XAs5YD482Mp8NC+qmlc0iEv0osiaZAYHD/O284HLRZfh InNhplGBnfhiSqdaAKSOxnbrvDJU6kEm4nwc26nom6ZnYY+tRVDbMsxxAzxI+MmM wUug3UkhfhO/ArhJD4DzZ85phklA7Oac9xmN/cNtK4gf4FTaVrjSibh7/D6Fy6yB ma0nQWiVEmtWvqiNLMjcggmf8T9TCm8NeLkj7PGxtLQg642ieo5A==
Received: from prod-mail-ppoint3 (a72-247-45-31.deploy.static.akamaitechnologies.com [72.247.45.31] (may be forged)) by m0050102.ppops.net-00190b01. (PPS) with ESMTPS id 3tayc4m00u-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 26 Sep 2023 16:17:01 +0100 (BST)
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.17.1.19/8.17.1.19) with ESMTP id 38QDi5FP020167; Tue, 26 Sep 2023 11:17:00 -0400
Received: from email.msg.corp.akamai.com ([172.27.50.205]) by prod-mail-ppoint3.akamai.com (PPS) with ESMTPS id 3tacwxqv0x-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 26 Sep 2023 11:17:00 -0400
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com (172.27.50.203) by ustx2ex-dag4mb6.msg.corp.akamai.com (172.27.50.205) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.25; Tue, 26 Sep 2023 08:17:00 -0700
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com ([172.27.50.203]) by ustx2ex-dag4mb4.msg.corp.akamai.com ([172.27.50.203]) with mapi id 15.02.1258.025; Tue, 26 Sep 2023 08:17:00 -0700
From: "Salz, Rich" <rsalz@akamai.com>
To: "gendispatch@ietf.org" <gendispatch@ietf.org>
CC: Geoff Huston <gih902@gmail.com>, GENDISPATCH Chairs <gendispatch-chairs@ietf.org>
Thread-Topic: [Gendispatch] A gendispatch session at IETF 118?
Thread-Index: AdncoC9LMVIvFSjIQgCjNMyUUjOvMQ==
Date: Tue, 26 Sep 2023 15:17:00 +0000
Message-ID: <AE377BF7-819C-4C19-B022-CAC81D36A517@akamai.com>
References: <6036cbfa3f204dcebdd2a2393a6101ab@huawei.com> <9b9a6c68-877b-42c5-9231-e95f0df4e190@betaapp.fastmail.com> <4cb7e10e-673d-27cf-1115-d721c5aa1a1e@cs.tcd.ie> <ed7b3d50-25d2-d82d-3514-3d5282f18c56@joelhalpern.com> <90816281-ce30-2112-4ea5-355e14105e06@gmail.com> <4935A0FA-F4B2-4ABE-8825-11485B30230B@akamai.com> <c43e5f49-a974-c3d9-2a8c-263257a07ec1@gmail.com> <3D3DDDF4-B211-4222-AC43-24B00906EFE0@gmail.com>
In-Reply-To: <3D3DDDF4-B211-4222-AC43-24B00906EFE0@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.76.23082700
x-originating-ip: [172.27.118.139]
Content-Type: multipart/alternative; boundary="_000_AE377BF7819C4C19B022CAC81D36A517akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.267,Aquarius:18.0.980,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-09-26_11,2023-09-26_01,2023-05-22_02
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 phishscore=0 malwarescore=0 mlxscore=0 bulkscore=0 mlxlogscore=868 adultscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2309180000 definitions=main-2309260132
X-Proofpoint-ORIG-GUID: p8UG6N63qo2egiQLXwmXJN-BF5GdPuqI
X-Proofpoint-GUID: p8UG6N63qo2egiQLXwmXJN-BF5GdPuqI
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.267,Aquarius:18.0.980,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-09-26_12,2023-09-26_01,2023-05-22_02
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 lowpriorityscore=0 spamscore=0 malwarescore=0 suspectscore=0 bulkscore=0 priorityscore=1501 adultscore=0 clxscore=1011 impostorscore=0 mlxlogscore=904 mlxscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2309180000 definitions=main-2309260133
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/fCHgAYha-PDL9ly7WjmS_iVSbO8>
Subject: Re: [Gendispatch] A gendispatch session at IETF 118?
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Sep 2023 15:17:07 -0000
> Rich Salz and I have been reflecting on our experiences in NOMCOM 2022 and would like to present on a yet-to-be-submitted draft that proposes some changes to the nomcom processes at a gendispatch session at IETF118 Here is the draft we would like to present: A new version of Internet-Draft draft-rsalz-gih-nomcom-2years-00.txt has been successfully submitted by Rich Salz and posted to the IETF repository. Name: draft-rsalz-gih-nomcom-2years Revision: 00 Title: Two-year terms for NomCom volunteers Date: 2023-09-26 Group: Individual Submission Pages: 7 URL: https://www.ietf.org/archive/id/draft-rsalz-gih-nomcom-2years-00.txt Status: https://datatracker.ietf.org/doc/draft-rsalz-gih-nomcom-2years HTML: https://www.ietf.org/archive/id/draft-rsalz-gih-nomcom-2years-00 HTMLized: https:// datatracker.ietf.org/doc/html/draft-rsalz-gih-nomcom-2years Abstract: Each year the NomCom process is actually two processes -- finding out anew how to be a NomCom and conduct its business, and then undertaking the work of the NomCom in selecting individuals to undertake the various roles for which the NomCom has responsibility. This applies to both the chair and to the voting volunteer members of the NomCom. The inclusion of the past chair into the NomCom as a non-voting member mitigates this to some extent, but the past chair is constrained as to the level of advice that can be offerred. This acts an impediment to making concrete changes for future incarnations of the Nomcom that would improve the overall Nomcom process. The NomCom process could benefit from greater levels of continuity from year-to-year to reduce the amount of time taken to by the new Nomcom to define its intended mode of operation and allow the operation each incarnation of the Nomcom with a greater level of consistency. This document changes the term of office for NomCom voting volunteers from one to two years. It also changes the term of office for the NomCom Chair from two to three.
- [Gendispatch] A gendispatch session at IETF 118? Pengshuping (Peng Shuping)
- Re: [Gendispatch] A gendispatch session at IETF 1… Martin Thomson
- Re: [Gendispatch] A gendispatch session at IETF 1… Stephen Farrell
- Re: [Gendispatch] A gendispatch session at IETF 1… Joel Halpern
- Re: [Gendispatch] A gendispatch session at IETF 1… Brian E Carpenter
- Re: [Gendispatch] A gendispatch session at IETF 1… Joel Halpern
- Re: [Gendispatch] A gendispatch session at IETF 1… Joel Halpern
- Re: [Gendispatch] A gendispatch session at IETF 1… Martin Thomson
- Re: [Gendispatch] A gendispatch session at IETF 1… Eliot Lear
- Re: [Gendispatch] A gendispatch session at IETF 1… Martin Thomson
- Re: [Gendispatch] A gendispatch session at IETF 1… Salz, Rich
- Re: [Gendispatch] A gendispatch session at IETF 1… Stephen Farrell
- Re: [Gendispatch] A gendispatch session at IETF 1… Eric Rescorla
- Re: [Gendispatch] A gendispatch session at IETF 1… Joel Halpern
- Re: [Gendispatch] A gendispatch session at IETF 1… Paul Hoffman
- Re: [Gendispatch] A gendispatch session at IETF 1… Brian E Carpenter
- Re: [Gendispatch] A gendispatch session at IETF 1… Geoff Huston
- Re: [Gendispatch] A gendispatch session at IETF 1… Robert Sparks
- Re: [Gendispatch] A gendispatch session at IETF 1… Rob Sayre
- Re: [Gendispatch] A gendispatch session at IETF 1… Eliot Lear
- Re: [Gendispatch] A gendispatch session at IETF 1… Jim Reid
- Re: [Gendispatch] A gendispatch session at IETF 1… Rob Sayre
- Re: [Gendispatch] A gendispatch session at IETF 1… Salz, Rich