[dispatch] IETF 123 - do you have something for DISPATCH?
"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Sat, 21 June 2025 08:13 UTC
Return-Path: <pengshuping@huawei.com>
X-Original-To: dispatch@mail2.ietf.org
Delivered-To: dispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 3638B37AF3F9; Sat, 21 Jun 2025 01:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.185
X-Spam-Level:
X-Spam-Status: No, score=-4.185 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] 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 lWcWgcZYDOLA; Sat, 21 Jun 2025 01:13:31 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 35F8037AF3F2; Sat, 21 Jun 2025 01:13:31 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4bPRss3HY5z6M5nr; Sat, 21 Jun 2025 16:12:49 +0800 (CST)
Received: from kwepemh500011.china.huawei.com (unknown [7.202.181.142]) by mail.maildlp.com (Postfix) with ESMTPS id 87A6E14027A; Sat, 21 Jun 2025 16:13:28 +0800 (CST)
Received: from kwepemf500016.china.huawei.com (7.202.181.3) 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; Sat, 21 Jun 2025 16:13:26 +0800
Received: from kwepemf500017.china.huawei.com (7.202.181.4) by kwepemf500016.china.huawei.com (7.202.181.3) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Sat, 21 Jun 2025 16:13:26 +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; Sat, 21 Jun 2025 16:13:26 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: dispatch <dispatch@ietf.org>
Thread-Topic: IETF 123 - do you have something for DISPATCH?
Thread-Index: AdvihALoMrQH1D35TfaKVJMZ3empzA==
Date: Sat, 21 Jun 2025 08:13:26 +0000
Message-ID: <2523f80c121649b581a198e03c80026a@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.85.159.33]
Content-Type: multipart/alternative; boundary="_000_2523f80c121649b581a198e03c80026ahuaweicom_"
MIME-Version: 1.0
Message-ID-Hash: D6U3HGJZZCY43FUCNHGJDOPFJY3HBGVD
X-Message-ID-Hash: D6U3HGJZZCY43FUCNHGJDOPFJY3HBGVD
X-MailFrom: pengshuping@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dispatch.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "dispatch-chairs@ietf.org" <dispatch-chairs@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dispatch] IETF 123 - do you have something for DISPATCH?
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/_JQHb3Giyofvpt3tNCg2AvkudZc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Owner: <mailto:dispatch-owner@ietf.org>
List-Post: <mailto:dispatch@ietf.org>
List-Subscribe: <mailto:dispatch-join@ietf.org>
List-Unsubscribe: <mailto:dispatch-leave@ietf.org>
Hi everyone, We're calling for agenda topics for our next meeting at IETF 123. No matter how big or small, if you have something you'd like dispatching or that you think will be of interest to the ART AREA, get in touch and get involved. **Please note that in this IETF 123 meeting, the ART dispatch will be joint with SEC + WIT Dispatch, and ARTAREA. In the preliminary agenda, this joint session is arranged on July 21st, 2025, Monday. As always, it will be the first session of the IETF week. If you would like time at the meeting to discuss your work or ideas, please email Jim and me. We're keen to hear from you! And if you're not really sure what this dispatching thing is for, or if you have any questions about bringing new work, please get in touch with us all the same - we're here to help. We look forward to hearing from you. PS. We have updated the DISPATCH WG wiki (https://wiki.ietf.org/group/dispatch) to include more information on how to prepare for attending the session and your presentations in DISPATCH and so on. Hope they are helpful. If you have any suggestions on improving this wiki page and adding more materials, please feel free to email us. Thank you! Jim and Shuping
- [dispatch] IETF 123 - do you have something for D… Pengshuping (Peng Shuping)