[Secdispatch] For the DISPATCH topics in the coming IETF126 meeting
"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Mon, 06 July 2026 03:38 UTC
Return-Path: <pengshuping@huawei.com>
X-Original-To: secdispatch@mail2.ietf.org
Delivered-To: secdispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id DCE0610F8C28C; Sun, 5 Jul 2026 20:38:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1783309096; bh=VeNBloi55xcSy8wHdG+XmYtMNLYXBiZ9+0PSjqOPepM=; h=From:To:CC:Subject:Date; b=Y7dkfTxagbGw6mDLG0CB0c6PPlPk9uat4z6vRdEsT0gG0xplxZCtbUqU753qTgCC3 F+QCs4NRGjk4auvg8WwDUQbWD0e6ZotKTc1AV4aWigSFdmXGLgH6nu+GWQytsrvhHa 4of8dRODggCoCoKIXjKwYb3PXflFuc1brDa947to=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level:
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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_PASS=-0.001] autolearn=ham autolearn_force=no
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 a8-G3hw-ZDSj; Sun, 5 Jul 2026 20:38:14 -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 EA8BF10F8C27C; Sun, 5 Jul 2026 20:38:12 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.224.150]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4gtqmX0Rz8zHnGg3; Mon, 6 Jul 2026 11:37:16 +0800 (CST)
Received: from kwepemh500011.china.huawei.com (unknown [7.202.181.142]) by mail.maildlp.com (Postfix) with ESMTPS id 4792540572; Mon, 6 Jul 2026 11:38:11 +0800 (CST)
Received: from kwepemf500018.china.huawei.com (7.202.181.5) 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; Mon, 6 Jul 2026 11:37:38 +0800
Received: from kwepemf500017.china.huawei.com (7.202.181.4) by kwepemf500018.china.huawei.com (7.202.181.5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Mon, 6 Jul 2026 11:37:38 +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; Mon, 6 Jul 2026 11:37:38 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: "dispatch@ietf.org" <dispatch@ietf.org>
Thread-Topic: For the DISPATCH topics in the coming IETF126 meeting
Thread-Index: Ad0M99li+DYojGGTRlqQaHfu34eeAg==
Date: Mon, 06 Jul 2026 03:37:38 +0000
Message-ID: <5ebc0e2ec541473da090726d1b941623@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.181.66]
Content-Type: multipart/alternative; boundary="_000_5ebc0e2ec541473da090726d1b941623huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: EKLJ24CVJUX4NWFN5BBAC22SASBEG5AR
X-Message-ID-Hash: EKLJ24CVJUX4NWFN5BBAC22SASBEG5AR
X-MailFrom: pengshuping@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-secdispatch.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "secdispatch@ietf.org" <secdispatch@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Secdispatch] For the DISPATCH topics in the coming IETF126 meeting
List-Id: Security Dispatch <secdispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/OwSEuAp3U7jb_0BFC5Ida6UqY9E>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Owner: <mailto:secdispatch-owner@ietf.org>
List-Post: <mailto:secdispatch@ietf.org>
List-Subscribe: <mailto:secdispatch-join@ietf.org>
List-Unsubscribe: <mailto:secdispatch-leave@ietf.org>
Hi, For those who have requested a slot, please further explicitly provide your answers to the following requirements by replying in the mailing list if you have not done so. Thank you! Requirements: • Please confirm that the presenter has registered the IETF126 and please indicate whether to attend online or remotely. • Please provide the draft links associated to your presentation. • Interoperability Needs: Highlight the interoperability requirements of your proposal. • Deployment Interest: Provide evidence of interest from parties who are planning to deploy your work. For people who only subscribed to the secdispatch@ietf.org<mailto:secdispatch@ietf.org>, please subscribe to the dispatch@ietf.org<mailto:dispatch@ietf.org>. To subscribe: https://www.ietf.org/mailman/listinfo/dispatch Best Regards, Shuping For the Chairs of the DISPATCH WG From: Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com> Sent: Saturday, June 6, 2026 1:47 AM To: dispatch@ietf.org; secdispatch <secdispatch@ietf.org> Subject: [dispatch] DISPATCH/SECDISPATCH - Call for topics for Vienna. All, We are now accepting agenda topics for the upcoming IETF 126 meeting. If you have ART or SEC areas work you'd like to present, discuss, or dispatch, please reach out to us and get involved. Joint DISPATCH Session Announcement For IETF 126, the ART DISPATCH will be held jointly with SECDISPATCH. If you'd like time during this meeting to present your work or ideas, please email us to request a slot. If you're not familiar with the purpose of DISPATCH or have questions about introducing new work to the IETF, don’t hesitate to contact us—we’re here to help guide you through the process. Interim Meeting Announcement: Due to the high volume of requests received so far, we are planning to host an interim meeting focused on AI-related drafts prior to IETF 126. NOTES: Request Confirmation: If you’ve already submitted requests for dispatching via the DISPATCH or SECDISPATCH mailing lists, please confirm your interest in presenting by explicitly indicating that you'd like a slot in the upcoming session. This confirmation implies that you will register for the meeting, either on-site or online. Proposal Requirements: Based on discussions from our last meeting (IETF 125), all requests must clearly demonstrate: * Interoperability Needs: Highlight the interoperability requirements of your proposal. * Deployment Interest: Provide evidence of interest from parties who are planning to deploy your work. Regards, Jim, Shuping, Daniel, and Rifaat (chairs of the DISPATCH and SECDISPATCH WGs)
- [Secdispatch] For the DISPATCH topics in the comi… Pengshuping (Peng Shuping)
- [Secdispatch] Re: [dispatch] For the DISPATCH top… Roger Anderson
- [Secdispatch] Re: For the DISPATCH topics in the … Andrew Campling
- [Secdispatch] Re: For the DISPATCH topics in the … Dick Hardt
- [Secdispatch] Re: For the DISPATCH topics in the … Mark Norton