Application Aware Computing Network

Introduction Many services deploy their service instances in multiple geographically distributed sites to get better response time. As described in , traffic steering that takes into account both the computing resource metric and network metric would improve the QoE of several services, e.g., AR/VR and intelligent transportation. A CATS framework is described in . It defines following core concepts:

CATS service identifier represents a service which consists of multiple service contact instances.
Service contact instance affinity means that packet that belongs to a flow should always goes to the same service contact instance.

These concepts are similar to APN described in . The Application-aware Networking (APN) framework[I-D.li-apn-framework] defines that application-aware information (i.e. APN attribute) including APN identification (ID) and/or APN parameters (e.g. network performance requirements) is encapsulated at network edge devices and carried in packets traversing an APN domain in order to facilitate service provisioning, perform fine-granularity traffic steering and network resource adjustment. [I-D.li-apn-app-side-framework] defines the extension of the APN framework for the application side. In this extension, the APN resources of an APN domain is allocated to applications which compose and encapsulate the APN attribute in packets. The APN ID includes application group ID and user group ID. Application group ID can be used as part of CATS service identifier. User group ID + application group ID can be used as CATS flow ID. This document describes a CATS framework using APN. The realization can use APN framework for application side.

Terminology This document reuses terms defined in and .

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Locator and APN ID In CATS, the packet needs to carry the locator information and the application identifier information. The application identifier information can be carried in APN ID. As described in , the length of the APN ID can be 32bit, 64 bit or 128bit. Depending on whether APN ID can fit into 128bit, the following two formats are defined. They carry the same information and can be used in different deployment scenarios.

APN Segment APN segment is an SRv6 SID[RFC8986], consisting of LOC:FUNCT:ARG, where:

LOC is routable and leads to the service contact instance.
FUNCT is APN ID which consists of user group id and application group ID. The length of APN ID is 32 bit or 64 bit.

LOC + APN ID If 128 bit is not enough to hold the APN ID + LOC. Then the APN ID can be put in other places as described in , e.g., IPv6 extension header.

Overview For simplicity, this document use APN segment as an illustration example, see .

Architecture Overview

Realization of CATS Framework Components The LOC + application group ID in the APN segment is used as CATS service identifier. The CATS overlay is established from the Ingress CATS-Router to an Egress CATS-Router. The CATS Traffic Classifier is running at the Ingress CATS-Router. Depending on the deployment, the CATS Path Selector, C-SMA and C-NMA can be centralized or distributed. CIS-ID is used to forward the packet to a specific CATS service contact instance. The choice of the CIS-ID is out of scope.

Realization of CATS Framework Workflow

Service Announcement Locator is routable and leads to service contact instances. The locator is announced in anycast. The locator and application group ID may be learned by client using a rendezvous service (DNS, for example). The user group ID may be learned through a protocol between the client and server. The detailed rendezvous procedure is out of scope.

Metric Distribution As described in CATS framework, the metrics needs to be distributed along with the CS-ID route. The detailed control plane solution depends on the deployment model (distributed, centralized or hybrid) and is out of scope of this document. A sample procedure using distributed model is provided to illustrate the core process, see . The C-SMA running as stand alone component at each service contact instance. In addition to the route announcement of LOC, C-SMA also distributes the application group ID and the computing metric to the Egress. The egress then pass the [(LOC, application group ID), computing metric] to the ingress node. The protocol extension used to carry the information is out of scope.

Service Request Processing The service request packet has the destination address set to APN segment. The C-TC component in Ingress uses LOC + application group ID to match the service, finding the optimal service contact instance. Then the best path to the corresponding service instance is selected by C-PS. The packet is encapsulated and forwarded using the overlay path. The Egress decapsulates the packet then forward it to the service contact instance.

Service Instance Affinity As per , the packets belong to the same flow should goes to the same service contact instance. This document defines flow identifier as the tuple (locator, user group ID, app group ID). By assigning the user group ID and app group ID, the service can archive customizable flow affinity without relying on traditional (IP, port) tuple.

APN for Real Locator defines real locator for CATS. When implementing solution of APN for CATS, the real locator can be carried in APN Para. Other procedure is the same as defined in .

Security Considerations This document does not introduce any new security considerations.

IANA Considerations TBD.