Re: [Dyncast] CAN BoF issues #26 #28 #29 #31

["[e-mail]" <[e-mail]>]

Hi Daniel,

Thanks for the draft, I suggest to create another thread to discuss this if you want, to prevent being covered by the issues discussion. 

BTW, The 'CAN architecture' has not been posted until now, and the 'CAN underlay' in your email may more explanation or re-wording. 

Regards,
Peng


[e-mail]
 
From: [e-mail]
Date: 2022-07-09 14:49
To: [e-mail]
CC: dirk.trossen=[e-mail]; [e-mail]; [e-mail]
Subject: Re: [Dyncast]CAN BoF issues #26 #28 #29 #31
Hi everyone, we've post a draft proposing a solution of hierarchical computing status maintaining as well as two segment service flow forwarding under CAN architecture.
the key point is the computing status should be aggregated and maintained in such a different way that the dynamics of computing would not undermine the existing routing scheme, and there's also a good opportunity for CAN underLay to be aware of the service SLA (networking and computing) through the computing service identification.
Any comments, suggestions and contributions would be greatly appreciated.
https://datatracker.ietf.org/doc/draft-huang-two-segment-routing-solution-of-can/

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: [e-mail] <[e-mail]>
To: Dirk Trossen <dirk.trossen=[e-mail]>;黄光平10039714;
Cc: linda.dunbar <[e-mail]>;dyncast <[e-mail]>;
Date: 2022年07月06日 15:40
Subject: Re: [Dyncast] CAN BoF issues #26 #28 #29 #31
--  
Dyncast mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/dyncast

Yes, if we consider the actual deployment, maybe the ingress is also the egress in some cases, which could also be found more or less in the dyncast arch draft.

Regards,
Peng


[e-mail]
 
From: Dirk Trossen
Date: 2022-07-06 14:17
To: [e-mail]; [e-mail]
CC: [e-mail]; [e-mail]
Subject: Re: [Dyncast] CAN BoF issues #26 #28 #29 #31
Hi Daniel,
 
As Peng pointed out, it depends on where the D-MA decide but also what is the binding ID in the specific deployment. If a DC ingress is exposed as a BID, then it’s also likely running the D-MA. If the instance is directly exposing its address as BID, it may also likely realize its own D-MA.
 
One can now look at both, i.e., the DC ingress or the instance itself, as the CAN egress, which aligns with your view below.
 
Best,
 
Dirk
 
From: Dyncast [mailto:[e-mail]] On Behalf Of [e-mail]
Sent: 06 July 2022 05:11
To: [e-mail]
Cc: [e-mail]; [e-mail]
Subject: Re: [Dyncast] CAN BoF issues #26 #28 #29 #31
 
hi Linda and Peng,
it occurs to me that what we call "ingress" and "egress" is a logical term in terms of end2end flow while the actual CAN nodes upon which ingress and egress reside will have to operate both as ingress when it's the access node and egress when it's the proxy node of computing site.  IMHO, every CAN node which ususally is the edge network node needs to maintain the said computing status as well as executing the according forwarding actions, and the rest nodes would not be impacted by CAN protocol as well as encapsulation.
 
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: [e-mail] <[e-mail]>
To: linda.dunbar <[e-mail]>;dyncast <[e-mail]>;
Date: 2022年07月06日 10:47
Subject: Re: [Dyncast] CAN BoF issues #26 #28 #29 #31
--  
Dyncast mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/dyncast
Hi Linda,
 
It depends on the specific realization of D-MA(Dyncast Metric Agent) which gathers instances and network-related information. 
 
The D-MA may run in the egress(will impact) or separately on edge nodes(will not impact) . 
 
As for the packet sending from egress to instance, there might be local policy but that is not the basic demand of CAN dyncast.
 
Regards,
Peng


[e-mail]
 
From: Linda Dunbar
Date: 2022-07-05 23:58
To: [e-mail]; dyncast
CC: David R. Oran; rtgwg
Subject: Re: [Dyncast] CAN BoF issues #26 #28 #29 #31
Peng,
 
For the #28: Does CAN Dyncast impact the Egress routers as well? When the computing site load changes, which entity notify the ingress nodes?
 
 
#28 Will CAN dyncast impact each and every router? How to avoid loops? 
CAN proposes an ingress-based architecture, so not every router will need to be impacted. If aspects of signaling will be realized via an existing routing protocol, it may impact but that will depend on the final solution.
Thanks, Linda
 
From: rtgwg <[e-mail]> On Behalf Of [e-mail]
Sent: Monday, July 4, 2022 5:17 AM
To: dyncast <[e-mail]>
Cc: David R. Oran <[e-mail]>; rtgwg <[e-mail]>
Subject: CAN BoF issues #26 #28 #29 #31
 
Dear All,
 
Here are the responses to issues #26 #28 #29 #31, which are related to dyncast. Any comments are welcome.
 
This email is also copied to the questioner (https://datatracker.ietf.org/doc/minutes-113-can/), hope for further suggestions and confirmations. Thanks.
 
#26 What's the assumed scale of a D-router? 10 ^ 6 sessions? 100^ 8? What's the assumed update rate? !Gb? 1Tb?
This question is only relevant if d-routers would maintain session information, which is not a given since it depends on the chosen solution. Update rates for compute/network metric information will heavily depend on the chosen algorithm for instance selection.
 
#28 Will CAN dyncast impact each and every router? How to avoid loops? 
CAN proposes an ingress-based architecture, so not every router will need to be impacted. If aspects of signaling will be realized via an existing routing protocol, it may impact but that will depend on the final solution.
 
#29 Is dyncast proposed to encapsulate? 
This will depend on the proposed solution. At this stage, the work is proposed more for control plane.
 
#31 For Dyncast, when the time is short, is it possible for the router to decide the routing? It is too fast. 
Solutions for dyncast may be as simple as a weighted round robin on possible (binding identifier) table entries, which should be implementable at the suitable speed. Also, depending on the realization of affinity, the ingress decision may not be required for every request.
 
Any detailed discussion is expected to be only within dyncast mailing list. You can also check and add your comments to any of them(https://github.com/CAN-IETF/CAN-BoF-ietf113/issues).  
 
Regards,
Peng
 


[e-mail]
 
From: Linda Dunbar
Date: 2022-05-11 06:11
To: [e-mail]
Subject: [Dyncast] Categories of the CAN BoF issues
CAN BoF proponents:
 
Many thanks for creating the CAN BoF issues tracking  in the Github: https://github.com/CAN-IETF/CAN-BoF-ietf113/issues/created_by/CAN-IETF?page=1&q=is%3Aopen+is%3Aissue+author%3ACAN-IETF
 
I went through the issues captured in the Github and characterized them into groups. Some issues can be lumped together for the discussion. There are quite a few issues related to the requirements, which need to be clarified.
 
Best Regards, Linda
 
 
Issues associated with Applications vs. Underlay networks:
·         Consider not to load underlay network with application details. #35
·         We have multiple upper layer application. Do we have additional needs for routing(e.g. WG?) or we are using those applications and won't need such new WG? #30
·         It needs application information too, so it can't just make a decision at the network layer. #23
·         This is not striked as a routing problem; it's all service discovery that can be done in higher layers. #21
·         3GPP and URSP solve this based on UPF selection. It uses both endpoint + application. #20
·         One overlay plane per application. Resources/metric specific to the plane. #19
·         How does the application layer or the transport layer learn the network status to steering traffic? #16
 
Need more clear requirements for CAN (to be addressed by draft-liu-dyncast-ps-usecases):
·         Need to understand if three are requirement to avoid extra messages or 1ms of latency #36
·         Regarding the flow affinity, is it from network perspective or from application/computation perspective? #33
·         How to effectively compute paths? Shall we put CPUs into account? #32
·         What happens when the user moves? If so we also need to move application context. #25
·         It can only move the services around as fast as it can update the routing plane. which comes back to the point about service discovery (waiting for convergence/distribution as opposed to just updating the SD server) #24
·         Whether the interests of the organization deploying the application and the organization providing the network connectivity are aligned. Google doesn't worry about this because they are both. #17
o    The question is more what the scope and semantic of information is that will need to cross organizational boundaries. This needs further study, in particular when assuming stakeholder division between service and network provider.
·         It seems impossible to satisfy that requirement simultaneously with the latency requirement. #15
·         It wasn't clear that how hard of a requirement session persistence is. #13
o    A session usually creates ephemeral state. If execution changes from one (e.g., virtualized) service instance to another, state/context needs transfer to another. Such required transfer of state/context makes it desirable to have session persistence (or instance affinity) as the default, removing the need for explicit context transfer, while also supporting an explicit state/context transfer (e.g., when metrics change significantly).
·         Should it select UPF based on the application? Steering is done per user? or per application? #9
·         This seems to assume conventional non-distributed applications just running at the edge. what about modern frameworks like Sapphire? and Ray? #7
o    It would be good to understand the multi-site requirements of such framework, which I have understood to mainly run in single DCs.
·         Relation to 3GPP UPF #6
·         Relation to ALTO #5
·         Do the mobility issues and associated protocols are also in scope? There are scenarios where routing alone would not be sufficient. #4
·         What is the position in the edge location regarding to UPF? #3
·         Is there some sort of authorization model so that an edge can indicate whether or not it will provide compute services? #2
·         What is CNC and the relationship with CAN #1
 
Measurement of the Computing Resources (to be addressed by draft-du-computing-resource-representation):
·         It is hard to use existing work to measure the computation, but we can optimize the latency through the performance monitoring. We have performance/measurement matrix over there. #34
·         Clarifications on the computing resource, its requirements and characteristics would be helpful. #27
·         Each application may have a different definition of "resources" these then have to be boiled down into a single topology Network Aware Computing (NAC! :) does scale #14
·         Is computing resource measurable? #10
o    It is, and how to use the measurement would be solution related. See IFIP Networking 2022 paper on how to simply expose “computing capability” and achieve better steering with such simple measure.
·         Why compute resource is different with other resources? #8
·          
Load Balance based solutions:
·         The point is that we need a standardized LB protocol #18
·         The LB as part of the application itself is superior (part of the distributed application itself is to obtain and keep updating the "best" unicast location to use). #22
·         If there is anything missing from current lbs that would prevent their use as-is? other than there is for market reasons no interop standard between different lbs? #12
·         For the load balance, should it learn the network’s status? #11
·          
Dyncast based Solution issues:
·         For Dyncast, when the time is short, is it possible for the router to decide the routing? It is too fast. #31
·         Is dyncast proposed to encapsulate? #29
·         Will CAN dyncast impact each and every router? How to avoid loops? #28
·         What's the assumed scale of a D-router? 10 ^ 6 sessions? 100^ 8? What's the assumed update rate? !Gb? 1Tb? #26