[Gendispatch] GENDISPATCH outcome for IETF126
"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Thu, 23 July 2026 08:33 UTC
Return-Path: <pengshuping@huawei.com>
X-Original-To: gendispatch@mail2.ietf.org
Delivered-To: gendispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 5BEBC11D17C2D; Thu, 23 Jul 2026 01:33:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784795591; bh=WCZjcKx32OZAih7oiErscxMR++4pgmd8XHsyYxua6jg=; h=From:To:CC:Subject:Date; b=w8bLbtUnxLv9OuHM6akmZe8DSrZXiUEvefvWdTP3tqO+TPG+4bV7QzMGPd6q7bvRB 7QggFlNt1O2evEiIvyAWZbMWCvg0omubFQ1skR2QI9jZYcCP1IPXD2lgdK/SziT/UN PY/Ym/NbjvHYUboDfvz5vTLwvseFLfsw4RjuemgA=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.394
X-Spam-Level:
X-Spam-Status: No, score=-4.394 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=huawei.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5KiRSKwUHcRD; Thu, 23 Jul 2026 01:33:10 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 1D45C11D17C22; Thu, 23 Jul 2026 01:33:10 -0700 (PDT)
dkim-signature: v=1; a=rsa-sha256; d=huawei.com; s=dkim; c=relaxed/relaxed; q=dns/txt; h=From; bh=omy5OPZvV3IKTnoYWyfR4XTHTebs6c+c47Yh28mlosk=; b=lHmLJJ/qcoa5CMOisaImNC9V8GdDzdibXisCm8ayaWiTrlsgR2WajOePFPOweROIChfSGtVsN Z+Ssnw+MsVO7MmYXvuwJ8frXF6zU81eFRsOYL3ZvpQG9oNP0Habm7JkTxN5QpzdHWRzcTqBTWWf b0jbk02ATTNq8mi+zQeBLr4=
Received: from mail.maildlp.com (unknown [172.18.224.107]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4h5PWc1ZfpzJ46Q7; Thu, 23 Jul 2026 16:32:44 +0800 (CST)
Received: from kwepemh500011.china.huawei.com (unknown [7.202.181.142]) by mail.maildlp.com (Postfix) with ESMTPS id 4090F4058B; Thu, 23 Jul 2026 16:33:07 +0800 (CST)
Received: from kwepemf100018.china.huawei.com (7.202.181.17) by kwepemh500011.china.huawei.com (7.202.181.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Thu, 23 Jul 2026 16:33:03 +0800
Received: from kwepemf500017.china.huawei.com (7.202.181.4) by kwepemf100018.china.huawei.com (7.202.181.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.36; Thu, 23 Jul 2026 16:33:03 +0800
Received: from kwepemf500017.china.huawei.com ([7.202.181.4]) by kwepemf500017.china.huawei.com ([7.202.181.4]) with mapi id 15.02.1544.011; Thu, 23 Jul 2026 16:33:03 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: "gendispatch@ietf.org" <gendispatch@ietf.org>
Thread-Topic: GENDISPATCH outcome for IETF126
Thread-Index: Ad0ada1l5efrw/Z+Qryu7QrfUcy6zg==
Date: Thu, 23 Jul 2026 08:33:03 +0000
Message-ID: <472dafb6287c4b9ea751bba9b602d12b@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.145.204]
Content-Type: multipart/alternative; boundary="_000_472dafb6287c4b9ea751bba9b602d12bhuaweicom_"
MIME-Version: 1.0
Message-ID-Hash: N7Y5M6BMIYM5RH3QG2DOFSSUJMMV2FSL
X-Message-ID-Hash: N7Y5M6BMIYM5RH3QG2DOFSSUJMMV2FSL
X-MailFrom: pengshuping@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "gendispatch-chairs@ietf.org" <gendispatch-chairs@ietf.org>, "gendispatch-ads@ietf.org" <gendispatch-ads@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Gendispatch] GENDISPATCH outcome for IETF126
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/H_weGAG_6WJo8AnXicsgFsUcAMw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Owner: <mailto:gendispatch-owner@ietf.org>
List-Post: <mailto:gendispatch@ietf.org>
List-Subscribe: <mailto:gendispatch-join@ietf.org>
List-Unsubscribe: <mailto:gendispatch-leave@ietf.org>
Hi, Please find the dispatch outcomes for IETF126, based on the suggested list as shown below. 1. Derivative Works Presenter: Brian E Carpenter (Remote) draft-sayre-gendispatch-derivative > dispatch outcome: Recommend additional discussion in ipr-wg@ietf.org, followed by review by legal counsel 2. Composition and Comportment of the IETF Nominating Committee Presenter: Mallory Knodel (Remote) draft-knodel-nomcom-gender-representation > dispatch outcome: Recommend additional discussion in eligibility-discuss@ietf.org on a document with reduced scope Here are the list of suggested dispatch outcomes, 1. Direct the work to an existing WG 2. Propose a new focused WG 3. Recommend to hold a full BOF 4. Publish as AD-sponsored (assuming AD is willing) 5. Recommend additional discussion or community development (e.g., with a new non-WG mailing list) 6. Find that work is not appropriate for IETF Please let the Chairs know if any amendment is needed. Thank you! Shuping & Martin
- [Gendispatch] GENDISPATCH outcome for IETF126 Pengshuping (Peng Shuping)