CAN

CFN-dyncast: Load Balancing the Edges via the Network

Tutorial

1. CFN-Dyncast Overview [EN]

Publication URL: PDF - CFN-Dyncast Overview

Introduction:

Compute First Networking (CFN) leverages both computing and networking status to help determine the optimal edge among multiple edge sites with different geographic locations to serve a specific edge computing request.

2. Innovation and Practice of CFN Based on IPv6+ [CN]

Publication URL: PDF - Innovation and Practice of CFN Based on IPv6+

Introduction:

This slide introduces the innovation and pratice of CFN based on IPv6+ technologies.

3. Innovation of Computing-Aware Routing in Intelligent IP Network

Publication URL: PDF - Innovation of Computing-Aware Routing in Intelligent IP Network

Introduction:

This slide introduces the innovation of computing-aware routing.

Paper

1. IEEE WCNC 2021

Publication URL: Paper - CFN-dyncast: Load Balancing the Edges via the Network

Publication URL: Slides - Jianwei Mao (speaker)

Publication URL: Meeting Video - Bing Liu (Remy) (speaker)

Introduction:

Multi-access Edge Computing (MEC) is a promising business paradigm in the 5G network. The principle “the nearest is the best” may not apply in some cases. How to break the boundaries among individual MEC sites and leverage the computing resources as an integrity, is the key to improve the user experience and improve the usage efficiency of computing and network resources. This paper proposes CFN-dyncast, a distributed technique that dispatches clients’ demands to an optimal site according to the load of each computing site and the network status. This paper also introduces the related design considerations, the implementation and the evaluation comparing to other load balancing techniques.

IETF

Drafts

Computing-Aware Traffic Steering (CATS) Problem Statement, Use Cases, and Requirements

Publication URL: https://datatracker.ietf.org/doc/draft-ietf-cats-usecases-requirements/

Introduction:

Distributed computing is a tool that service providers can use to
   achieve better service response time and optimized energy
   consumption.  In such a distributed computing environment, providing
   services by utilizing computing resources hosted in various computing
   facilities aids support of services such as computationally intensive
   and delay sensitive services.  Ideally, compute services are balanced
   across servers and network resources to enable higher throughput and
   lower response times.  To achieve this, the choice of server and
   network resources should consider metrics that are oriented towards
   compute capabilities and resources instead of simply dispatching the
   service requests in a static way or optimizing solely on connectivity
   metrics.  The process of selecting servers or service instance
   locations, and of directing traffic to them on chosen network
   resources is called “Computing-Aware Traffic Steering” (CATS).

This document provides the problem statement and the typical
   scenarios for CATS, which shows the necessity of considering more
   factors when steering traffic to the appropriate computing resource
   to best meet the customer’s expectations and deliver the requested
   service.

Computing-Aware Traffic Steering (CATS) Gap Analysis

Publication URL: https://datatracker.ietf.org/doc/html/draft-yao-cats-gap-analysis

Introduction:

This document provides gap analysis for problem statement and use cases for Computing-Aware Traffic Steering(CATS) that are outlined in[I-D.ietf-cats-usecases-requirements]. It identifies the key engineering investigation areas that require potential architecture improvements and protocol enhancements so as to reach the optimal balance between compute services, via the proper choice of servers, and network paths, with the holistic consideration of metrics that are comprised of network status, coupled with the compute capabilities and resources.

Computing Information Description in Computing-Aware Traffic Steering

Publication URL: https://datatracker.ietf.org/doc/html/draft-du-cats-computing-modeling-description

Introduction:

This document describes the considerations and the potential architecture of the computing information that needs to be notified into the network in Computing-Aware Traffic Steering (CATS).

A Framework for Computing-Aware Traffic Steering (CATS)

Publication URL: https://datatracker.ietf.org/doc/draft-ldbc-cats-framework/

Introduction:

This document describes a framework for Computing-Aware Traffic
   Steering (CATS).  Particularly, the document identifies a set of CATS
   components, describes their interactions, and exemplifies the
   workflow of the control and data planes.

Computing-Aware Traffic Steering (CATS) Using Segment Routing

Publication URL: https://datatracker.ietf.org/doc/html/draft-lbdd-cats-dp-sr

Introduction:

This document describes a solution that adheres to the Computing-Aware Traffic Steering (CATS) framework. The solution uses anycast IP addresses as the CATS service identifier and Segment Routing (SR) as the data plane encapsulation to achieve computing-aware traffic steering among multiple services instances.

Application Aware Computing Network

Publication URL: https://datatracker.ietf.org/doc/html/draft-li-cats-application-aware-computing-network

Introduction:

This document describes a solution framework that adheres to the CATS framework. The solution uses APN as part of the CATS service identifier and flow identifier.

CATS based on Real Locator

Publication URL: https://datatracker.ietf.org/doc/html/draft-shi-cats-with-real-locator

Introduction:

This document describes a solution framework that adheres to the CATS framework. The solution uses anycast IP addresses as the CATS service identifier and real locator of the service contact instance as the CATS Instance Selection ID.

Design analysis of methods for distributing the computing metric

Publication URL: https://datatracker.ietf.org/doc/draft-shi-cats-analysis-of-metric-distribution/

Introduction:

This document analyses different methods for distributing the
   computing metrics from service instances to the ingress router.

BGP Extension for 5G Edge Service Metadata

Publication URL: https://datatracker.ietf.org/doc/html/draft-ietf-idr-5g-edge-service-metadata

Introduction:

This draft describes a new Metadata Path Attribute and some Sub-TLVs for egress routers to advertise the Metadata about the attached edge services (ES). The edge service Metadata can be used by the ingress routers in the 5G Local Data Network to make path selections not only based on the routing cost but also the running environment of the edge services. The goal is to improve latency and performance for 5G edge services.

The extension enables an edge service at one specific location to be more preferred than the others with the same IP address (ANYCAST) to receive data flow from a specific source, like a specific User Equipment (UE).

IGP Extension for 5G Edge Computing Service

Publication URL: https://datatracker.ietf.org/doc/html/draft-dunbar-lsr-5g-edge-compute

Introduction:

This draft describes using additional site capacity and
   preference related metrics to influence the SPF and using
   Flexible Algorithms to indicate the topologies those
   metrics are applied. The purpose is to differentiate
   multiple paths with similar routing distance to one
   destination in 5G Local Data Network (LDN)to achieve
   optimal performance.

Distribution of Service Metadata in BGP-LS

Publication URL: https://datatracker.ietf.org/doc/html/draft-ls-idr-bgp-ls-service-metadata

Introduction:

In edge computing, a service may be deployed on multiple instances within one or more sites, called edge service. The edge service is associated with an ANYCAST address in IP layer, and the route of it with potential service metadata will be distributed to the network. The Edge Service Metadata can be used by ingress routers to make path selections not only based on the routing cost but also the running environment of the edge services.

The service route with metadata can be collected by a PCE(Path Compute Element) or an analyzer for calculating the best path to the best site/instance. This draft describes a mechanism to collect the information of the service routes and related service metadata in BGP-LS.

Distribution of Service Metadata in BGP FlowSpec

Publication URL: https://datatracker.ietf.org/doc/html/draft-yi-idr-bgp-fs-edge-service-metadata

Introduction:

In edge computing, a service may be deployed on multiple instances within one or more sites, called edge service. The edge service is associated with an ANYCAST IP address, and the route of it along with service metadata can be collected by a central controller. The controller may process the metadata and distribute the result to ingress routers using BGP FlowSpec. The service metadata can be used by ingress routers to make path selections not only based on the routing cost but also the running environment of the edge services. This document describes a mechanism to distribute the information of the service routes and related service metadata using BGP FlowSpec.

Hybrid Computing and Network Awareness and Routing Solution for CATS

Publication URL: https://datatracker.ietf.org/doc/html/draft-yi-cats-hybrid-solution

Introduction:

Computing-Aware Traffic Steering (CATS) is a traffic engineering architecture that takes the dynamic changes of computing and network resources into account when forwarding traffic to appropriate service instances for processing. For the development of the current network, it is important to have a solution that meets different types of service requirements and can be deployed reasonably. Therefore, this document proposes a hybrid solution to provide differentiated and flexible traffic streering capabilities for different service while saving the cost of retrofitting existing network equipment.

IPv6 Solution for 5G Edge Computing Sticky Service

Publication URL: https://datatracker.ietf.org/doc/html/draft-dunbar-6man-5g-edge-compute-sticky-service

Introduction:

This draft describes the IPv6-based solutions that can stick an application flow originated from a mobile device to the same ANYCAST server location when the mobile device moves from one 5G cell site to another.

5G Edge Services Use Cases

Publication URL: https://datatracker.ietf.org/doc/html/draft-dunbar-cats-edge-service-metrics

Introduction:

This draft describes the 5G Edge computing use cases for CATS
   and how BGP can be used to propagate additional IP layer
   detectable information about the 5G edge data centers so that
   the ingress routers in the 5G Local Data Network can make
   path selections based on not only the routing distance but
   also the IP Layer relevant metrics of the destinations. The
   goal is to improve latency and performance for 5G Edge
   Computing (EC) services even when the detailed servers
   running status are unavailable.

Meetings

1. CFN-dyncast Side Meeting @IETF109

Publication URL: https://github.com/dyncast/ietf109

2. CFN-dyncast Side Meeting @IETF110

Publication URL: https://github.com/dyncast/ietf110

3. CAN BoF @IETF 113(Non WG forming)

Agenda URL: https://datatracker.ietf.org/doc/agenda-113-can/

Material URL: https://datatracker.ietf.org/meeting/113/session/can

4. CAN BoF @IETF 115(WG forming)

Agenda URL: https://datatracker.ietf.org/doc/agenda-115-can/

Material URL: https://datatracker.ietf.org/meeting/115/session/can

5. CATS WG meetings

Publication URL: https://datatracker.ietf.org/wg/cats/meetings/

CCSA

General technical requirements of Computing and Network Convergence

Publication URL: CCSA Standard - General technical requirements of Computing and Network Convergence

Introduction:

This document defines the architecture and technical requirement of Computing and Network Convergence.

Demo

OpenSource

News

1. CFN enables Smart Security Protection solution in the network of China Unicom(Beijing)

In the 5th Future Network Development Conference, China Unicom Research Institute, China Unicom(Beijing) and Huawei published this practice in the network of China Unicom(Beijing).

IETF Mailing List

CFN Dyncast (Archived)
Address: dyncast@ietf.org

Archives: https://mailarchive.ietf.org/arch/browse/dyncast/

To subscribe: https://www.ietf.org/mailman/listinfo/dyncast

CAN (Archived)

Address: can@ietf.org

Archives: https://mailarchive.ietf.org/arch/browse/can/

To subscribe: https://www.ietf.org/mailman/listinfo/can

CATS (Active)

Address: cats@ietf.org

Archives: https://mailarchive.ietf.org/arch/browse/cats/

To subscribe: https://www.ietf.org/mailman/listinfo/cats