[Secdispatch] IETF-Wide Dispatch – Call for topics
"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Tue, 18 June 2024 14:15 UTC
Return-Path: <pengshuping@huawei.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E56BC14F6BF; Tue, 18 Jun 2024 07:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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
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 h3TG1NXb2E-L; Tue, 18 Jun 2024 07:15:24 -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 ietfa.amsl.com (Postfix) with ESMTPS id 19764C14F61E; Tue, 18 Jun 2024 07:15:24 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4W3TDK3tp1z6JBCw; Tue, 18 Jun 2024 22:10:25 +0800 (CST)
Received: from lhrpeml100005.china.huawei.com (unknown [7.191.160.25]) by mail.maildlp.com (Postfix) with ESMTPS id 3FB0E140B54; Tue, 18 Jun 2024 22:15:21 +0800 (CST)
Received: from canpemm100008.china.huawei.com (7.192.104.152) by lhrpeml100005.china.huawei.com (7.191.160.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Tue, 18 Jun 2024 15:15:20 +0100
Received: from canpemm500008.china.huawei.com (7.192.105.151) by canpemm100008.china.huawei.com (7.192.104.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Tue, 18 Jun 2024 22:15:18 +0800
Received: from canpemm500008.china.huawei.com ([7.192.105.151]) by canpemm500008.china.huawei.com ([7.192.105.151]) with mapi id 15.01.2507.039; Tue, 18 Jun 2024 22:15:18 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: "Alldispatch@ietf.org" <Alldispatch@ietf.org>, secdispatch <secdispatch@ietf.org>, "dispatch@ietf.org" <dispatch@ietf.org>, "gendispatch@ietf.org" <gendispatch@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "ops-area@ietf.org" <ops-area@ietf.org>, "witarea@ietf.org" <witarea@ietf.org>
Thread-Topic: IETF-Wide Dispatch – Call for topics
Thread-Index: AdqzAAPLYtFr+gYwSX6B+fRsHQJGsQOiaHGg
Date: Tue, 18 Jun 2024 14:15:17 +0000
Message-ID: <cfff99e3339a4e1ba3a231346270ef77@huawei.com>
References: <4780b9da32294f9ea7294a91c59802f6@huawei.com>
In-Reply-To: <4780b9da32294f9ea7294a91c59802f6@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.84.29.185]
Content-Type: multipart/alternative; boundary="_000_cfff99e3339a4e1ba3a231346270ef77huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: FTFQT7LPTPC7OVRBBD2XNLTQ3732S5AS
X-Message-ID-Hash: FTFQT7LPTPC7OVRBBD2XNLTQ3732S5AS
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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Secdispatch] IETF-Wide Dispatch – Call for topics
List-Id: Security Dispatch <secdispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/N0L0Z-NCJLEHzMwPVyg56I3doW4>
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 everyone, We're calling for agenda topics for our next IETF-Wide Dispatch meeting at IETF 120. If you have any topic that you'd like dispatching or that you think will be of interest to the ART, SEC, or GEN areas, or elsewhere in the IETF, get in touch and get involved. If you would like time at the meeting to discuss your work or ideas, please reply to this email with your request by June 24th. Please, take a look at the following SecDispatch Wiki for more information about what we are looking for when you submit your request: https://wiki.ietf.org/group/secdispatch With further guidance from IESG, we will have strict time requirement for each pitch, likely 5 mins for explaining the proposal and 10 mins for collecting the community feedback and Chairs summary. The Chairs have prepared a slides template to assist presenters to prepare slides (max 5 slides including motivation, background and hoped outcome). Please note that if you also present in HotRFC, the content must be different and with different goals. Regards, ALLDISPATCH Chairs
- [Secdispatch] IETF-Wide Dispatch – Call for topics Pengshuping (Peng Shuping)
- [Secdispatch] Re: [Alldispatch] IETF-Wide Dispatc… Carsten Bormann
- [Secdispatch] IETF-Wide Dispatch – Call for topics Pengshuping (Peng Shuping)