From yaokehan@chinamobile.com Tue Oct 24 00:50:20 2023 Return-Path: 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 5B30CC1519B4 for ; Tue, 24 Oct 2023 00:50:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.905 X-Spam-Level: X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 6UQ1eb9A-1fe for ; Tue, 24 Oct 2023 00:50:16 -0700 (PDT) Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 136ABC15199D for ; Tue, 24 Oct 2023 00:50:13 -0700 (PDT) X-RM-TagInfo: emlType=0 X-RM-SPAM-FLAG: 00000000 Received: from spf.mail.chinamobile.com (unknown[172.16.121.83]) by rmmx-syy-dmz-app10-12010 (RichMail) with SMTP id 2eea65377731673-c076c; Tue, 24 Oct 2023 15:50:11 +0800 (CST) X-RM-TRANSID: 2eea65377731673-c076c X-RM-SPAM-FLAG: 00000000 Received: from yaokehan@chinamobile.com ( [10.2.54.60] ) by ajax-webmail-syy-appsvrnew02-11012 (Richmail) with HTTP; Tue, 24 Oct 2023 15:50:10 +0800 (CST) Date: Tue, 24 Oct 2023 15:50:10 +0800 (CST) From: =?utf-8?B?5aea5p+v57+w?= To: dispatch Cc: =?utf-8?B?5b6Q5LiW6JCN?= , liyizhou , "hongyi.huang" , KUTSCHER Dirk Dirk K Message-ID: <2b0465377338b22-00021.Richmail.00000090782935283333@chinamobile.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_867_953643660.1698133810177" X-Priority: 3 X-RM-TRANSID: 2b0465377338b22-00021 Encrypt-Channel: web X-RM-OA-ENC-TYPE: 0 X-RM-FontColor: 0 X-CLIENT-INFO: X-TIMING=0&X-MASSSENT=0&X-SENSITIVE=0 X-Mailer: Richmail_Webapp(V2.4.27) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2023 07:50:20 -0000 ------=_Part_867_953643660.1698133810177 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: 7bit 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)" Tue, 24 October 2023 02:40 UTCShow header 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 we39ve 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 ------=_Part_867_953643660.1698133810177 Content-Type: text/html;charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hi chairs,


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

  &nb= sp; 

    We have just uploaded two I-Ds about tanspo= rt design problems, use cases, and requirements for collective communicatio= n.

    We think= this work is quite relavant to ART area, since distributed application nee= d application-transport-network cross-layer co-design. <= /p>

https://datatracker.ietf.org= /doc/draft-yao-tsvwg-cco-problem-statement-and-usecases/<= /p>

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


   =  * Title: Collectve Communication Optimization: Use cases, Problems an= d Requirements

    * Presenter: Kehan Yao<= br/>

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

    * Onsite

=

BR,

Kehan=




"Pengshuping (Peng Shuping)" <pengshu= ping@huawei.com> Tue, 24 October 2023 02:40 UTCShow header

Maybe we could segment a sin=
gle DISPATCH session into multiple parts, e.g. Cross-area, ART area, WIT ar=
ea 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.=20

In the current dispatch agenda, we put time for each presentation to give p=
eople a rough indication about the session schedule, aiming to assist peopl=
e 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 age=
nda.=20

Shuping


------=_Part_867_953643660.1698133810177--