Subject: Dyncast (dynamic anycast)

From: Liyizhou <[email-masked]>
Date: Mon, 2 Nov 2020 09:16:44 +0000

Hi folks,

We submitted two drafts about dyncast (dynamic anycast).

draft-geng-rtgwg-cfn-dyncast-ps-usecase<https://datatracker.ietf.org/doc/draft-geng-rtgwg-cfn-dyncast-ps-usecase/>
draft-li-rtgwg-cfn-dyncast-architecture<https://datatracker.ietf.org/doc/draft-li-rtgwg-cfn-dyncast-architecture/>

Edge computing puts the potential requirements on better load balancing among the computing resources hosted on different edges. The number of such edges could be thousand or even more depending on where the computing resources are located.
The expected approach is to consider both network status and computing resources at the same time to determine the best place to forward a new computing demand to. Current solution usually uses DNS-like approach, select the service instance first (the lowest load or roughly the geographically closest instance) and then direct the demand to it regardless how good or bad the network path reaching it.

Anycast based service addressing methodology could be used here to reach the best edge in terms of both computation resource and network status at the same time. Flow affinity and computing aware routing needs to be enhanced in such an anycast architecture. It is called dynamic anycast in the drafts.

If you have any comments or suggestions, please drop us an email. Appreciated.

Regards,
Yizhou