NeoTec X. Gao, Ed. Internet-Draft X. Yi, Ed. Intended status: Standards Track R. Pang, Ed. Expires: 24 April 2025 China Unicom J. Dong, Ed. Huawei 21 October 2024 Analysis of Service Management Interface for Cloud-network Convergence draft-gao-neotec-interface-cnc-00 Abstract This document analyzes the cloud-network convergence service management interface. Status of This Memo 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 24 April 2025. Copyright Notice Copyright (c) 2024 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. Gao, et al. Expires 24 April 2025 [Page 1] Internet-Draft Interface for Cloud-network Convergence October 2024 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Conventions and Definitions . . . . . . . . . . . . . . . . . 2 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3.1. Cloud gaming scene case . . . . . . . . . . . . . . . . . 3 3.2. Financial Industry Case . . . . . . . . . . . . . . . . . 3 4. Interface requirements for cloud-network convergence service management . . . . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . 6 7.2. Informative References . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 1. Introduction Cloud-network convergence service requires the organic combination of cloud resources (such as computing, storage, applications, etc.) with network connectivity, transmission, and distribution capabilities, providing users with a one-stop solution. To achieve seamless integration of cloud and network services, it is necessary to standardize cloud and network interfaces. This article describes the interface definitions and requirements for intra cloud network and inter cloud network, in order to achieve full process management of resource and service strategy configuration, business process and status monitoring, resource scheduling, and service performance optimization. Simultaneously discuss the specific protocols for interface implementation and the security issues of data transmission. 2. Conventions and Definitions 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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 3. Use Cases Gao, et al. Expires 24 April 2025 [Page 2] Internet-Draft Interface for Cloud-network Convergence October 2024 3.1. Cloud gaming scene case Taking a cloud gaming platform as an example, it provides various types of games, and users do not need to install large game files on their local devices. They only need to connect to the cloud gaming server through the network to play games smoothly. When users access cloud gaming services，Cloud-network convergence service management interface creates a network connection between the user, operator network, and cloud based on the user access point. On the operator network side, business creation is achieved by calling relevant interfaces to open up the operator network channel. On the cloud side, by calling relevant interfaces, the subnet to which the cloud game service deployment belongs is confirmed, and a virtual router is created to interface with the operator's network devices, thereby supporting game players to directly access the cloud service. 3.2. Financial Industry Case Large banks typically adopt a hybrid cloud architecture to meet the growing demand for digital business, storing core business data in private cloud data centers to ensure data security. At the same time, utilizing the resources of public clouds to meet the elastic needs of some non core businesses. When users conduct online banking transactions, in order to ensure the security and reliability of the network path from the user end to the bank's private cloud data center, cloud-network convergence service management interface creates a connection service of user-operator network-cloud ; When data deployed in the public cloud is transferred and backed up to the private cloud, the cloud-network convergence service management interface creates a network connection service of cloud-operator network-cloud. In addition, when facing network failures or sudden high traffic situations, real-time monitoring of network quality (including latency, packet loss, and other parameters) is carried out through network status monitoring interfaces to facilitate fault location and analysis, quickly switch business traffic to backup network paths or public cloud resources, and ensure the continuity of financial services. When there is a demand for big data transmission, end-to-end bandwidth elasticity changes are made through the cloud-network convergence service management interface to meet the demand for large bandwidth in data transmission. In the existing standards, there are few business data models or network models for northbound controllers, and there is a lack of standardized requirements for cloud-network convergence management interfaces, including flexible allocation of cloud network resources, end-to-end business management (opening, changing, and network status monitoring), and other interface definitions. Therefore, it is necessary to conduct a detailed analysis and standardization of the Gao, et al. Expires 24 April 2025 [Page 3] Internet-Draft Interface for Cloud-network Convergence October 2024 cloud-network convergence service management interface,better support for convergence services such as user cloud entry and inter cloud interconnection,promote interoperability of cloud and network resources across different providers, and achieve seamless integration of cloud and network services. 4. Interface requirements for cloud-network convergence service management The cloud-network convergence service management interface mainly refers to the northbound interface of the network controller and the cloud controller, as well as the northbound interface of the orchestrator, as shown in the following figure. It usually exists in the form of RESTful API (Representational State Transfer Application Programming Interface), which facilitates users to manage through scripts or automated tools.IN1 mainly manages cloud network related resources, including physical and virtual topologies, and manages, allocates, and recycles network resources used by tenants. IN2 mainly manages the relevant resources of the operator's network, including but not limited to routers, topology, links, etc. It can flexibly and virtually allocate network resources, process business requests, and provide specific functions according to the business needs and network conditions of different customers, including but not limited to L3 VPN, L2 VPN, etc. It can also monitor the network status. IN3 mainly manages and orchestrates cloud-network convergence service. Gao, et al. Expires 24 April 2025 [Page 4] Internet-Draft Interface for Cloud-network Convergence October 2024 + ---------------+ | APP | + ---------------+ /|\ | IN3 +----------------+ | orchestrator | +----------------+ /\ / \ IN1 / \ IN2 / \ +----------------+ +------------------+ |Cloud controller| |network controller| +----------------+ +------------------+ | | | | +----------------+ +------------------+ |Network resource| | network resource| +----------------+ +------------------+ Figure1:Schematic diagram of cloud-network convergence service management interface IN1 refers to the northbound interface of the cloud controller, and the specific content and description are as follows: * Network resource management interface: supports the creation,modification, deletion, and query of virtual network resources. * Subnet management interface: supports the creation, modification, deletion, and query of subnet resources. * Virtual router resource management interface: supports the creation, modification, deletion, and query of virtual router resources. * Security group resource management interface: supports the creation, modification, deletion of security groups, and query of corresponding security rules. * Network status monitoring interface: supports monitoring of network latency, packet loss, and other performance indicators. IN2 refers to the northbound interface of the network controller, and its specific content and description are as follows: Gao, et al. Expires 24 April 2025 [Page 5] Internet-Draft Interface for Cloud-network Convergence October 2024 * Network Service Management Interface: supports the creation, modification (bandwidth, routing, QoS), deletion, and query of network services (supporting MPLS, SR-MPLS, SRv6, and other services) based on user requirements; * Network status monitoring interface: supports monitoring of network latency, packet loss, and other performance indicators. IN3 refers to the northbound interface of orchestrator, and its specific content and description are as follows: * Service management interface:supports the creation, modification, deletion, and query of cloud-network convergence services; * End to end status monitoring interface: supports monitoring the performance of cloud-network convergence services such as latency and packet loss. TBD 5. Security Considerations It is necessary to ensure the encryption of interface communication to prevent data from being stolen or tampered with during transmission. Identity authentication and authorization management should be carried out to ensure that only legitimate users or systems can access and operate cloud network resources. TBD 6. IANA Considerations TBD 7. References 7.1. Normative References [RFC6208] Sankar, K., Ed. and A. Jones, "Cloud Data Management Interface (CDMI) Media Types", RFC 6208, DOI 10.17487/RFC6208, April 2011, . 7.2. Informative References [I-D.dxs-neotec-crossdomain-net-mgnt-dm] Dunbar, L., Xie, C., and Q. Sun, "Cross-Domain Cloud and Network Resource Management Data Model", Work in Progress, Gao, et al. Expires 24 April 2025 [Page 6] Internet-Draft Interface for Cloud-network Convergence October 2024 Internet-Draft, draft-dxs-neotec-crossdomain-net-mgnt-dm- 00, 14 October 2024, . [I-D.ietf-teas-te-service-mapping-yang] Lee, Y., Dhody, D., Fioccola, G., Wu, Q., Ceccarelli, D., and J. Tantsura, "Traffic Engineering (TE) and Service Mapping YANG Data Model", Work in Progress, Internet- Draft, draft-ietf-teas-te-service-mapping-yang-16, 20 October 2024, . Authors' Addresses Xing Gao (editor) China Unicom Beijing China Email: gaox60@chinaunicom.cn Xinxin Yi (editor) China Unicom Beijing China Email: yixx3@chinaunicom.cn Ran Pang (editor) China Unicom Beijing China Email: pangran@chinaunicom.cn Jie Dong (editor) Huawei Beijing China Email: jie.dong@huawei.com Gao, et al. Expires 24 April 2025 [Page 7]