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

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Wed, 25 October 2023 09:34 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 DF466C1519B4 for <dispatch@ietfa.amsl.com>; Wed, 25 Oct 2023 02:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.903
X-Spam-Level:
X-Spam-Status: No, score=-6.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=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_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 1ck0tCoqY4kN for <dispatch@ietfa.amsl.com>; Wed, 25 Oct 2023 02:34:21 -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 85713C1519AC for <dispatch@ietf.org>; Wed, 25 Oct 2023 02:34:21 -0700 (PDT)
Received: from lhrpeml500002.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4SFkJL0T2Sz67Clh for <dispatch@ietf.org>; Wed, 25 Oct 2023 17:33:38 +0800 (CST)
Received: from kwepemi500009.china.huawei.com (7.221.188.199) by lhrpeml500002.china.huawei.com (7.191.160.78) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Wed, 25 Oct 2023 10:34:18 +0100
Received: from canpemm500008.china.huawei.com (7.192.105.151) by kwepemi500009.china.huawei.com (7.221.188.199) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Wed, 25 Oct 2023 17:34:16 +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.031; Wed, 25 Oct 2023 17:34:16 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: 姚柯翰 <yaokehan@chinamobile.com>, dispatch <dispatch@ietf.org>
CC: KUTSCHER Dirk Dirk K <dku@hkust-gz.edu.cn>, Yizhou Li <liyizhou@huawei.com>, 徐世萍 <xushiping@chinamobile.com>
Thread-Topic: [dispatch] IETF 118 - do you have something for DISPATCH?
Thread-Index: AQHaBk62Y/ti/L0eTOmtDA7S4xkwW7BaPnug
Date: Wed, 25 Oct 2023 09:34:16 +0000
Message-ID: <c0c42ae00daa41aeb1af327403a1bd38@huawei.com>
References: <2b0465377338b22-00021.Richmail.00000090782935283333@chinamobile.com>
In-Reply-To: <2b0465377338b22-00021.Richmail.00000090782935283333@chinamobile.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_c0c42ae00daa41aeb1af327403a1bd38huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/vZer9QMUEvjgiPmMfn-3ELUOAqE>
Subject: Re: [dispatch] IETF 118 - 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: Wed, 25 Oct 2023 09:34:23 -0000

Hi Kehan,

Your request has been received. Currently we have put you in the ART area sub-session part as you suggested. However, we can only accommodate 10mins for you. We do have 10mins left for Flextime & AOB. It will be up to the ADs to decide how to use this period of time.

I’d suggest that you could introduce your work and trigger more discussions before the meeting, which will make people be more familiar with your proposal and facilitate the discussions in the meeting. Hope this helps.

Best Regards,
Shuping


From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of 姚柯翰
Sent: Tuesday, October 24, 2023 3:50 PM
To: dispatch <dispatch@ietf.org>
Cc: KUTSCHER Dirk Dirk K <dku@hkust-gz.edu.cn>; Yizhou Li <liyizhou@huawei.com>; 徐世萍 <xushiping@chinamobile.com>
Subject: Re: [dispatch] IETF 118 - do you have something for DISPATCH?


Hi chairs,



    This is Kehan Yao from China Mobile. We want to apply for a slot in IETF118 to make a presentation if time permits.



    We have just uploaded two I-Ds about tansport design problems, use cases, and requirements for collective communication.

    We think this work is quite relavant to ART area, since distributed application need application-transport-network cross-layer co-design.

    Here is the link: https://datatracker.ietf.org/doc/draft-yao-tsvwg-cco-problem-statement-and-usecases/

    and https://datatracker.ietf.org/doc/draft-yao-tsvwg-cco-requirement-and-analysis/



    * Title: Collectve Communication Optimization: Use cases, Problems and Requirements

    * Presenter: Kehan Yao

    * Time Required: 10mins at least, 15mins if permitted

    * Onsite



BR,

Kehan







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

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com<mailto:pengshuping@huawei.com>> Tue, 24 October 2023 02:40 UTCShow header<https://mailarchive.ietf.org/arch/browse/dispatch/>

Maybe we could segment a single DISPATCH session into multiple parts, e.g. Cross-area, ART area, WIT area and SEC area, and allocate the received requests into each corresponding part. This allocation could be requested by the presenters or suggested by Chairs or Community in the mailing list.



In the current dispatch agenda, we put time for each presentation to give people a rough indication about the session schedule, aiming to assist people to make their own time schedule.



If we've got more requests that cannot be held with one DISPATCH, then we could consider to request a couple of slots for DISPATCH in the IETF agenda.



Shuping