neotec                                                      R. Pang, Ed.
Internet-Draft                                                T. He, Ed.
Intended status: Standards Track                            China Unicom
Expires: 20 April 2025                                   17 October 2024


Service Funciton Orchestration Interface for Cloud Network Collaboration
                    draft-pang-sfc-interface-cnc-00

Abstract

   This document focuses on interface requirements between network
   controller and service function orchestrator, as well as between
   cloud controller and service function orchestrator.

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 20 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.






Pang & He                 Expires 20 April 2025                 [Page 1]

Internet-Draft            SFO Interface for CNC             October 2024


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Background and Motivation . . . . . . . . . . . . . . . . . .   2
   3.  Architecture of service function chaining orchestration . . .   3
     3.1.  Service Overview  . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Work Flow Overview  . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   In the background of cloud network collaboration, an increasing
   number of value-added service functions in operator networks need to
   be deployed on demand or dynamically adjusted.  These service
   functions , such as FW, WAF, etc. can be deployed in the central
   cloud resource pool or at the edge of user networks.  Therefore, when
   conducting service function orchestration, it is necessary to
   exchange information with cloud controller and network controller.
   Therefore, it is necessary to standardize the interface requirements
   between network controller and service function orchestration, as
   well as the interface between cloud controller and service function
   orchestration.

1.1.  Terminology

1.2.  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 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

2.  Background and Motivation

   Cloud network collaboration(CNC) is a collaborative work mode based
   on cloud computing and network technology, which connects users,
   devices, and cloud services through the network, enabling users and
   devices to efficiently share cloud data, files, applications, and
   resources, and work together in real-time, achieving cross regional,
   cross organizational, and cross platform collaborative cooperation,
   improving work efficiency and enterprise competitiveness.





Pang & He                 Expires 20 April 2025                 [Page 2]

Internet-Draft            SFO Interface for CNC             October 2024


   With the development of network and business, there is a growing need
   to deploy and dynamically adjust various value-added service
   functions on demand, such as FW, WAF, etc.  Initially, these service
   functions can be deployed either in a central cloud resource pool or
   at the edge of the user network.  However, with the continuous
   improvement of network performance requirements such as network
   quality and request delay, the need for flexible scaling of service
   functions has also increased.  Simultaneously, the advancement of
   edge computing technology has prompted operators to deploy service
   functions across multiple edge nodes as per requirement.  These edge
   nodes collaborate seamlessly through the network and use SFC
   technology to connect service functions.  This approach not only
   fulfills users' need for flexible scheduling of service functions,
   but reduces response time, optimizes resource allocation, and
   enhances network efficiency.

   Based on the requirements of service function chaining, it is
   necessary to define interface requirements between network
   controller, cloud controller and service function orchestrator.

3.  Architecture of service function chaining orchestration

                            +------------------------------------------+
                            |     service function orchestrator        |
                            |                                          |
                            +------------------------------------------+
                                R1  /                              \ R2
                     +-----------------------+           +----------------------+
                     | network controller    |           |   cloud controlle    |
                     |                       |           |                      |
                     +-----------------------+           +----------------------+
                                |                                     |
                     +-----------------------+           +-----------------------+
                     |network infrastructure |           | cloud infrastructure  |
                     |                       |           |                       |
                     +-----------------------+           +-----------------------+

             Figure 1: Architecture of SFC orchestration

   The service function orchestrator is connected with the network
   controller and cloud control.  The service function orchestrator
   obtains network information from the network controller through R1
   and obtains computing resource pool information cloud controller from
   through R2, including value-added services that can be provided by
   the cloud infrastructure.






Pang & He                 Expires 20 April 2025                 [Page 3]

Internet-Draft            SFO Interface for CNC             October 2024


   The service function orchestrator is mainly focus on service
   orchestrating based on network resources and computing resources
   which are mentioned above.  According to users’ service requirements,
   orchestration system selects the suitable computing resources to
   provide services and decide the service path.  The orchestration
   system stores network information, service information and computing
   resources.

3.1.  Service Overview

   TBD

3.2.  Work Flow Overview

   TBD

4.  Security Considerations

   TBD




5.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

Authors' Addresses

   Pang Ran (editor)
   China Unicom
   Beijing
   China
   Email: pangran@chinaunicom.cn


   Tao He (editor)
   China Unicom
   Beijing
   China
   Email: het21@chinaunicom.cn



Pang & He                 Expires 20 April 2025                 [Page 4]