Re: [Dyncast] [Can] Scope and suggested charter statement for Computing Aware Networking(CAN)

huang.guangping@zte.com.cn Wed, 02 November 2022 01:52 UTC

Return-Path: <huang.guangping@zte.com.cn>
X-Original-To: dyncast@ietfa.amsl.com
Delivered-To: dyncast@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E32BC1524D2; Tue, 1 Nov 2022 18:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 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, UNPARSEABLE_RELAY=0.001, 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 F09JtwOR3ZzC; Tue, 1 Nov 2022 18:52:31 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91198C14CE2A; Tue, 1 Nov 2022 18:52:29 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.251.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4N28z02Mysz4xVng; Wed, 2 Nov 2022 09:52:28 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxct.zte.com.cn (FangMail) with ESMTPS id 4N28yQ1gHRz4y0v3; Wed, 2 Nov 2022 09:51:58 +0800 (CST)
Received: from szxlzmapp03.zte.com.cn ([10.5.231.207]) by mse-fl2.zte.com.cn with SMTP id 2A21pmVX098344; Wed, 2 Nov 2022 09:51:48 +0800 (+08) (envelope-from huang.guangping@zte.com.cn)
Received: from mapi (szxlzmapp01[null]) by mapi (Zmail) with MAPI id mid17; Wed, 2 Nov 2022 09:51:49 +0800 (CST)
Date: Wed, 02 Nov 2022 09:51:49 +0800
X-Zmail-TransId: 2b036361cd3572c951ba
X-Mailer: Zmail v1.0
Message-ID: <202211020951498358342@zte.com.cn>
In-Reply-To: <20221031164709695837445@chinamobile.com>
References: DB841E37-3092-4D3B-B59C-75611627D316@futurewei.com, 2a876605.4069.18423cfaa99.Coremail.zhangjiaxing20g@ict.ac.cn, 20221029214925550849399@chinamobile.com, 7a51d84597fb4a4c999e598211ba6576@huawei.com, 20221031164709695837445@chinamobile.com
Mime-Version: 1.0
From: huang.guangping@zte.com.cn
To: liupengyjy@chinamobile.com
Cc: shihang9@huawei.com, can@ietf.org, dyncast@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 2A21pmVX098344
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04-192.168.250.138.novalocal with ID 6361CD5C.004 by FangMail milter!
X-FangMail-Envelope: 1667353948/4N28z02Mysz4xVng/6361CD5C.004/192.168.251.13/[192.168.251.13]/mxct.zte.com.cn/<huang.guangping@zte.com.cn>
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6361CD5C.004/4N28z02Mysz4xVng
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/nGiofQILwWKrD_AKDs8Y5mId-dg>
Subject: Re: [Dyncast] [Can] Scope and suggested charter statement for Computing Aware Networking(CAN)
X-BeenThere: dyncast@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Anycast <dyncast.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dyncast>, <mailto:dyncast-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dyncast/>
List-Post: <mailto:dyncast@ietf.org>
List-Help: <mailto:dyncast-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dyncast>, <mailto:dyncast-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2022 01:52:35 -0000

Hi Peng,thanks for the charter work.


I have a minor comment below.


----



There are existing solutions that utilize end point resource information for selecting the server instance, such as DNS, ALTO, or Layer 4 & Layer 7 load balancers. Common to all those solutions is the exposure and usage of network conditions for decision making, while none of the existing solution integrate the computing resource conditions with the network conditions for deciding on the optimal paths.


----


Daniel Huang : As far as the existing solutions which mainly reside in layer 4 and beyond is concerned, it occurs to me that common to all of these solutions is that either the computing resource status (DNS, GSLB etc) or the networking status (LB, ALTO etc) is taken into consideration rather than both of the resource status integrated to optimize the path selection which CAN would chiefly address and the emerging use cases actually demand.






Best regards.


Daniel Huang































黄光平 huangguangping






标准团队/有线规划部 Wireline architecture team./Wireline Product R&D Institute









南京市雨花区软件大道50号中兴通讯2号楼 
R&D Building, ZTE
Corporation Software Road No.50, 
Yuhua District, Nanjing, P..R.China, 210012 
M: +86 13770311052 
E: huang.guangping@zte.com.cn 
www.zte.com.cn




Original



From: PengLiu <liupengyjy@chinamobile.com>
To: shihang9 <shihang9@huawei.com>;can <can@ietf.org>;dyncast <dyncast@ietf.org>;
Date: 2022年10月31日 16:41
Subject: Re: [Dyncast] [Can] Scope and suggested charter statement for Computing Aware Networking(CAN)


--  
Dyncast mailing list
Dyncast@ietf.org
https://www.ietf.org/mailman/listinfo/dyncast

 Hi Hang Shi,

Thanks for the comments. The design team will focus on the problem statement, use case, gap and reqs work, while it is the proposal and could be further discussed.

Regards,
Peng


--------------------------------------------------------------------------------

liupengyjy@chinamobile.com


 

From: Shihang(Vincent)
Date: 2022-10-31 11:28
To: Peng Liu; can; dyncast; 张佳兴
Subject: RE: [Can] Scope and suggested charter statement for Computing Aware Networking(CAN)





Hi Peng,


 


Thanks for your work.


1 comment below:


 


> CAN allows ingress nodes to consider computing-related resource


> conditions in routing decisions. As such, the CAN WG may develop an


> informational document, or create a design team, to define use cases,


> gap analysis, requirements, characterization of the computing-related


> resources, and how those conditions impact the ingress nodes routing decision process.


 


Do we need to put the “create design team” in charter? I assume every WG is free to create the design team as it see fit.


 


Best,


Hang Shi


 



From: Can <can-bounces@ietf.org> On Behalf Of Peng Liu
 Sent: Saturday, October 29, 2022 9:49 PM
 To: can <can@ietf.org>; dyncast <dyncast@ietf.org>; 张佳兴 <zhangjiaxing20g@ict.ac.cn>
 Subject: [Can] Scope and suggested charter statement for Computing Aware Networking(CAN)




 


Hi Jason, All, 



 


Thanks for mentioning that. The suggested scope and charter statement for CAN could be found at https://github.com/CAN-IETF/CAN-BoF-ietf115/blob/main/README.md. It described the overview of CAN, motivations , use cases, brief gap analysis, technical directions, work items and milestones. We would like to invite all the people who are interested in this work to review and comments on it.



 


BTW, the updated problem statement&usecase, gap analysis&requirements drafts could be found at https://datatracker.ietf.org/wg/can/documents/. Any comments on the drafts are also welcome.



 


Regards,



Peng



 
--------------------------------------------------------------------------------



liupengyjy@chinamobile.com