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

[Peng Liu <[e-mail]>]

Hi Daniel,

Thanks. Good summary, CAN wants to find a right way to meet the use case that considering both computing and network status at the same time. We will consider your points in the drafts or slides updates. 

Regards.
Peng


[e-mail]
 
From: [e-mail]
Date: 2022-11-02 09:51
To: [e-mail]
CC: [e-mail]; [e-mail]; [e-mail]
Subject: Re: [Dyncast] [Can] Scope and suggested charter statement for Computing Aware Networking(CAN)
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: [phone] 
E: [e-mail] 
www.zte.com.cn
Original
From: PengLiu <[e-mail]>
To: shihang9 <[e-mail]>;can <[e-mail]>;dyncast <[e-mail]>;
Date: 2022年10月31日 16:41
Subject: Re: [Dyncast] [Can] Scope and suggested charter statement for Computing Aware Networking(CAN)
--  
Dyncast mailing list
[e-mail]
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


[e-mail]
 
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 <[e-mail]> On Behalf Of Peng Liu
Sent: Saturday, October 29, 2022 9:49 PM
To: can <[e-mail]>; dyncast <[e-mail]>; 张佳兴 <[e-mail]>
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


[e-mail]