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

[Chengli <[e-mail]>]

Hi Hang and Peng,

I think the word ‘may’ tell us that this is a potential work only when it is needed.

Normally, we will not make a design team so quick, but everything depends on the WG discussion if a new WG is created.

So yes, you are right.

Respect,
Cheng



From: Can [mailto:[e-mail]] On Behalf Of Peng Liu
Sent: Monday, October 31, 2022 4:47 PM
To: Shihang(Vincent) <[e-mail]>; can <[e-mail]>; dyncast <[e-mail]>
Subject: Re: [Can] Scope and suggested charter statement for Computing Aware Networking(CAN)

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]<mailto:[e-mail]>

From: Shihang(Vincent)<mailto:[e-mail]>
Date: 2022-10-31 11:28
To: Peng Liu<mailto:[e-mail]>; can<mailto:[e-mail]>; dyncast<mailto:[e-mail]>; 张佳兴<mailto:[e-mail]>
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]<mailto:[e-mail]>> On Behalf Of Peng Liu
Sent: Saturday, October 29, 2022 9:49 PM
To: can <[e-mail]<mailto:[e-mail]>>; dyncast <[e-mail]<mailto:[e-mail]>>; 张佳兴 <[e-mail]<mailto:[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]<mailto:[e-mail]>