| Internet-Draft | CNIA | July 2023 |
| Yao, et al. | Expires 8 January 2024 | [Page] |
This document describes a Computing and Network Information Awareness (CNIA)system architecture for Computing-Aware Traffic Steering (CATS). Based on the CATS framework, this document further describes a proposal detailed awareness architecture about the network information and computing information. It includes a new component and the corresponding interfaces and workflows in the CATS control plane.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 8 January 2024.¶
Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
Computing-Aware Traffic Steering (CATS)[I-D.ldbc-cats-framework]aims to solve the problem of how the network edge can steer traffic between clients of a service and sites offering the service. To enable the computing- and network-aware traffic steering decisions, awareness of computing information and network information is the foundation.¶
Currently there are some work being done on the classification and awareness of computing and network information. As described in[I-D.du-cats-computing-modeling-description], there could be two models of computing information: one is some detailed computing parameters, and another is a comprehensive computing level parameter. Further, the former includes some static information such as service ability, and some dynamic information such as service status. This modeling document could be a solid foundation of CATS. For the awareness solution of computing and network information, the current recommended methods are generally BGP[I-D.ietf-idr-5g-edge-service-metadata], BGP-LS[I-D.ls-idr-bgp-ls-service-metadata], and BGP-FS[I-D.yi-idr-bgp-fs-edge-service-metadata]. CATS Service Metric Agent(C-SMA) and CATS Path Selector (C-PS) components defined in [I-D.ldbc-cats-framework] could be deployed in different locations.¶
Overall, the current awareness technology is some sporadic solutions. This document hopes to comprehensively sort out the computing and network awareness method and defines a comprehensive awareness architecture to support the different types of computing and network information, to facilitate the deployment of CATS. This awareness architecture acts as the control plane of CATS.¶
To consider various kinds of computing and network information, a control center component is additionally introduced on the basis of CATS framework. As a comprehensive awareness architecture CNIA supports both distributed,centralized,hybrid awareness models.¶
For some coarse-grained and relatively static information with low update frequency, it is recommended to be aware in a distributed way. The distributed way has better robustness and high scalability.¶
For some fine-grained dynamic information with a high update frequency, it is recommended to aware it in a centralized way. Frequent information updates will greatly increase the burden on network devices and are not conducive to information convergence. The centralized way is more suitable for the management of fine-grained dynamic information. This comprehensive-aware model is consistent with the design philosophy of segment routing architecture[RFC8402]. The services that require planning for dynamic resources, such as TE(Traffic Engineering), are implemented by a centralized controller. The BE(best-effort) service is still preserved on the devices and implemented in a distributed manner, which could take advantage of distributed robustness and reduce the burden of interfacing between the controller and devices, facilitating deployment.¶
CATS-control center
+----------------------------------+
| +------+ |
| | C-CIB| |
| +------+ +------+ | +----------+
| | C-PCE| | restful |cloud |
| +------+ +------+ |.........|management|
| | C-NIB| | |platform |
| +------+ | +----------+
+----------------------------------+ | |
: CATS-SBI | |
: | |
+----------------------------------+ | |
| CATS-Router2 | +--------+ |
+------+ |CATS-Router1 +-------+ |......|service | |
|client|.....|+---------| ..| C-SMA | | |instance| |
+------+ ||C-TC|C-PS+ .... +-------+ | +--------+ |
|+---------+ : +-------+ | +--------+
| ..| C-NMA | |.........|service |
| +-------+ | |instance|
+----------------------------------+ +--------+
Figure 1: CNIA System Arhicteture
¶
To realize the scheduling of fine-grained computing information, the control center introduces several components and interface:¶
Maintain fine-grained computing information, such as service connections,CPU performance,which may be obtained from the CATS-routers or from the cloud management platform.¶
Maintain fine-grained network information, such as remaining bandwidth,delay, which could be obtained from the routers.¶
Calculate optimal computing resource and network path based on C-CIB and C-NIB, and generate path policy and deliver to the CATS-routers.¶
An extended interface based on the traditional controller southbound interface between the CATS-routers and the CATS-control center, could be used to report network and computing information from CATS routers to the CATS-control center, and also could be used to send path and service policy information or compute information to CATS-routers.¶
Given the comprehensive architecture described above, this document proposes a comprehensive awareness system of the deployment location, real-time resource and service status, load information and requirements of computing resources and services. On the one hand, the network aggregates the computing and network metrics reported by multiple nodes to build a globally unified computing and network status view. On the other hand, the network completes the unified analysis of service, computing and network requirements, realizes the comprehensive perception and provides guarantee for computing-aware scheduling based on service requirement.¶
Currently the detailed network and computing parameters used by CATS have not yet reached a consensus in the industry, in order to avoid introducing too much signaling overhead into the whole network advertisement, this document proposes to classify the content of the computing advertisement according to the characteristics of the content and frequency of information announcement, and adopt different information awareness methods and information announcement protocols. As shown in Table 1, the computing and network information could be classified into capability information and status information. Capability information contains the deployment location and identifier information, and so on. Status information tends to be some real-time status parameters of the network and computing, such as remaining bandwidth,delay,service connections,CPU performance. This type of information is mainly used for some services that are sensitive to network and computing status, such as AR/VR services.¶
| Awareness information | Network information | Computing information |
|---|---|---|
| Capability parameters | Device location; Device type; Topology information | Service ID; Service-domain name; Computing energy consumption; Computing cost; Peak value of available computing |
| Status parameters | Service policy information; Traffic information (bandwidth,delay,packet loss rate,delay jitter) | Number of available service connections; Available resources; CPU/GPU/NPU performance; Storage capacity; Service delay |
Table 1 provides some detailed parameters examples about the two kinds of awareness information.¶
For some services that are sensitive to computing and network status, especially latency, such as AV/VR services, the network needs to be able to perceive detailed computing information and network information to meet the strict requirements of the service. This kind of computing information could be aware by the CATS-control center by restful interface from cloud management platform. The network information could be aware by the BGP-LS or telemetry interface to get the status parameters such as remaining bandwidth and the delay. Further, CATS-control center performs service scheduling according to the computing information and network information, then generates routing policy and sends to CATS ingress router . When CATS ingress router receives the service demand from the client, it selects the optimal service instance and network policy, and maintains the instance affinity subsequently.¶
For some high-value customers, hybrid awareness can be deployed to accurately match customer requirements. After the CATS-control center obtains computing and network information through SBI or restful interfaces, the details of this information are directly transmitted to the CATS ingress routers. The device performs accurate resource matching and continuous experience detection after receiving service traffic.¶
For distributed mode, the ingress CATS router responsibles for collecting computing and network information and scheduling service. When the ingress CATS router receives the service demand from the client it makes decision of the service instance to access independently according to the service instances status and network status and maintains instance affinity. The detailed workflow can be seen in[I-D.ldbc-cats-framework].¶