Re: [dispatch] IETF 114 - do you have something for DISPATCH?

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Tue, 05 July 2022 03:00 UTC

Return-Path: <pengshuping@huawei.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87592C14F73D for <dispatch@ietfa.amsl.com>; Mon, 4 Jul 2022 20:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-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] 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 Rgs4GcPAM_dj for <dispatch@ietfa.amsl.com>; Mon, 4 Jul 2022 20:00:35 -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 D1526C14F607 for <dispatch@ietf.org>; Mon, 4 Jul 2022 20:00:34 -0700 (PDT)
Received: from fraeml707-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4LcS5s5YMsz6H80Q; Tue, 5 Jul 2022 10:57:53 +0800 (CST)
Received: from canpemm100008.china.huawei.com (7.192.104.152) by fraeml707-chm.china.huawei.com (10.206.15.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 5 Jul 2022 05:00:31 +0200
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_128_GCM_SHA256) id 15.1.2375.24; Tue, 5 Jul 2022 11:00:29 +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.2375.024; Tue, 5 Jul 2022 11:00:29 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: Anton Tveretin <tveretinas@yandex.ru>
CC: DISPATCH list <dispatch@ietf.org>
Thread-Topic: [dispatch] IETF 114 - do you have something for DISPATCH?
Thread-Index: AQHYj+JJuwphgI4JhkWv/9a6hFaK6K1u/kaQ
Date: Tue, 05 Jul 2022 03:00:29 +0000
Message-ID: <45712c0a4acc40269ba9d6a0521a8759@huawei.com>
References: <78331656965210@mail.yandex.ru>
In-Reply-To: <78331656965210@mail.yandex.ru>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.153.177.224]
Content-Type: multipart/alternative; boundary="_000_45712c0a4acc40269ba9d6a0521a8759huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/I7DHgQi97yiqKRJLD4fVCCoAY1Y>
Subject: Re: [dispatch] IETF 114 - do you have something for DISPATCH?
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2022 03:00:36 -0000

Hi Anton,

Please let us know about the title of the two I-Ds you would like to present and the time you would require. We will try to arrange.

Best Regards,
Shuping

From: Anton Tveretin [mailto:tveretinas@yandex.ru]
Sent: Tuesday, July 5, 2022 4:12 AM
To: Pengshuping (Peng Shuping) <pengshuping@huawei.com>
Cc: DISPATCH list <dispatch@ietf.org>
Subject: Re: [dispatch] IETF 114 - do you have something for DISPATCH?

Hi Shuping,
I have 2 I-Ds for over 6 years. I missed the time at the previous IETF. I don't know whether I will have a chance to prepare a presentation now. I have an important contract now ;)
Sincerely yours, Anton.