[Gendispatch] Plan for IETF122
"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Fri, 07 February 2025 07:54 UTC
Return-Path: <pengshuping@huawei.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 7FB11C1CAE9A; Thu, 6 Feb 2025 23:54:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.204
X-Spam-Level:
X-Spam-Status: No, score=-4.204 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=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_BLOCKED=0.001, 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 J12HidI6Z5oD; Thu, 6 Feb 2025 23:54:33 -0800 (PST)
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 714D4C1E0D9C; Thu, 6 Feb 2025 23:54:33 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Yq5lR6CM2z6L5DF; Fri, 7 Feb 2025 15:51:47 +0800 (CST)
Received: from lhrpeml100012.china.huawei.com (unknown [7.191.174.184]) by mail.maildlp.com (Postfix) with ESMTPS id C8F941402A5; Fri, 7 Feb 2025 15:54:31 +0800 (CST)
Received: from kwepemf100017.china.huawei.com (7.202.181.16) by lhrpeml100012.china.huawei.com (7.191.174.184) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Fri, 7 Feb 2025 07:54:31 +0000
Received: from kwepemf500017.china.huawei.com (7.202.181.4) by kwepemf100017.china.huawei.com (7.202.181.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Fri, 7 Feb 2025 15:54:28 +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; Fri, 7 Feb 2025 15:54:28 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: "gendispatch@ietf.org" <gendispatch@ietf.org>
Thread-Topic: Plan for IETF122
Thread-Index: Adt5NKARrCFZQcTiTZK4abYTH+7tbg==
Date: Fri, 07 Feb 2025 07:54:28 +0000
Message-ID: <755da25517ba4c44aedbacce481f7268@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.41.150]
Content-Type: multipart/alternative; boundary="_000_755da25517ba4c44aedbacce481f7268huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: XFW6XHAEQ3TLJT3HK2TPE7KINTSLA6P6
X-Message-ID-Hash: XFW6XHAEQ3TLJT3HK2TPE7KINTSLA6P6
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>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Gendispatch] Plan for IETF122
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/CVBAdFBaekARyONaJLa8MSMEH_Q>
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 folks, As you may have already known that there will be no ALLDISPATCH meeting from IETF122 [1]. So we can continue to having a separate gendispatch session, and you can start discussions in the gendispatch mailing list. If you have a plan to present something in the coming IETF meeting, please let Martin and myself know, better within the following week. So we could know whether a gendispatch session is actually needed at IETF122. Please note that this is not an official slot collection. Just let us know about your thoughts. Thank you! [1] https://mailarchive.ietf.org/arch/msg/ietf/nEjqzz8m7-7Xfep63Li1lxXe9cc/ Martin & Shuping
- [Gendispatch] Plan for IETF122 Pengshuping (Peng Shuping)