| Networking Working Group | Q. Wu |
| Internet-Draft | Huawei |
| Intended status: Informational | M. Boucadair |
| Expires: January 4, 2020 | C. Jacquenet |
| Orange | |
| L. Miguel Contreras Murillo | |
| Telifonica | |
| D. Lopez | |
| Telefonica I+D | |
| C. Xie | |
| China Telecom | |
| W. Cheng | |
| China Mobile | |
| Y. Lee | |
| Futurewei | |
| July 3, 2019 |
A Framework for Automating Service and Network Management with YANG
draft-wu-model-driven-management-virtualization-05
Data models for service and network management provides a programmatic approach for representing (virtual) services or networks and deriving configuration information that will be forwarded to network and service components that are used to build and deliver the service. Data Models can be used during various phases of the service and network management life cycle, such as service instantiation, service provisioning, optimization, monitoring, and diagnostic. Also, data models are are instrumental in the automation of network management. They also provide closed-loop control for the sake of adaptive and deterministic service creation, delivery, and maintenance.
This document provides a framework that describes and discusses an architecture for service and network management automation that takes advantage of YANG modeling technologies. This framework is drawn from a network provider perspective irrespective of the origin of a data module andcan accommodate even modules that are developed outside the IETF.
The document aims to exemplify an approach that specifies the journey from technology-agnostic services to technology-specific actions.
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 January 4, 2020.
Copyright (c) 2019 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 Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
The service management system usually comprises service activation/ provision and service operation. Current service delivery procedures, from the processing of customer's requirements and order to service delivery and operation, typically assume the manipulation of data sequentially into multiple OSS/BSS applications that may be managed by different departments within the service provider's organization (e.g., billing factory, design factory, network operation center, etc.). In addition, many of these applications have been developed in-house over the years and operating in a silo mode. The lack of standard data input/output (i.e., data model) also raises many challenges in system integration and often results in manual configuration tasks. Secondly, many current service fulfillment might not support real time streaming telemetry capability in high frequency and in high throughput on the current state of networking and therefore have slow response to the network changes. Software Defined Networking (SDN) becomes crucial to address these challenges.
Software-Defined Networking techniques [RFC7149] are meant to automate the overall service delivery procedures and typically rely upon (standard) data models that are used to not only reflect service providers'savoir-faire but also to dynamically instantiate and enforce a set of (service-inferred) policies that best accommodate what has been (contractually) defined (and possibly negotiated) with the customer. [RFC7149] provides a first tentative to rationalize that service provider's view on the SDN space by identifying concrete technical domains that need to be considered and for which solutions can be provided:
Models are key for each of these technical items. Service and network management automation is an important step to improve the agility of network operations and infrastructures.
YANG module developers have taken both top-down and bottom-up approaches to develop modules [RFC8199] and to establish a mapping between network technology and customer requirements on the top or abstracting common construct from various network technologies on the bottom. At the time of writing this document (2019), there are many data models including configuration and service models that have been specified or are being specified by the IETF. They cover many of the networking protocols and techniques. However, how these models work together to configure a device, manage a set of devices involved in a service, or even provide a service is something that is not currently documented either within the IETF or other SDOs (e.g., MEF).
This document provides a framework that describes and discusses an architecture for service and network management automation that takes advantage of YANG modeling technologies and investigates how different layer YANG data models interact with each other (e.g., service mapping, model composing) in the context of service delivery and fulfillment. This framework is drawn from a network provider perspective irrespective of the origin of a data module andcan accommodate even modules that are developed outside the IETF.
The document also identifies a list of modules and use cases to exemplify the proposed approach, but it does not claim to be exhaustive.
It is not the intent of this document to provide an inventory of tools and mechanisms used in specific network and service management domains; such inventory can be found in documents such as [RFC7276].
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.
The following terms are defined in [RFC8309][RFC8199] and are not redefined here:
The following terms are defined in this document as follows:
Figure 1 provides an overview of various macro-functional blocks at different levels that articulate the various YANG data modules. In this figure, we use IETF defined YANG data model as an example Models.
<<Network Service Models>> +-------------------------------------------------------------------------+ | << Network Service Models>> | | +----------------+ +----------------+ | | | L3SM | | L2SM | | | | Service Model | | Service Model | ............. | | +----------------+ +----------------+ | +------------------------------------------------------------------------ + <<Network Resource Models>> +------------------------------------------------------------------------ + | << Network Resource Models >> | | +------------+ +-------+ +----------------+ +------------+ | | |Network Topo| | Tunnel| |Path Computation| |FM/PM/Alarm | | | | Models | | Models| | API Models | | OAM Models|... | | +------------+ +-------+ +----------------+ +------------+ | +-------------------------------------------------------------------------+ -------------------------------------------------------------------------- <Network Element Models>> +-------------------------------------------------------------------------+ | <<Composition Models>> | | +-------------+ +---------------+ +----------------+ | | |Device Model | |Logical Network| |Network Instance| | | | | |Element Model | | Model | ... | | +-------------+ +---------------+ +----------------+ | |-------------------------------------------------------------------------| | << Function Models>> | |+---------++---------++---------++----------++---------++---------+ | || || || ||Common || || OAM: | | || Routing ||Transport|| Policy ||(interface||Multicast|| | | ||(e.g.,BGP||(e.g., ||(e.g, ACL||multicast || (IGMP ||FM,PM, | | || OSPF) || MPLS) || QoS) || IP, ... )|| MLD,...)||Alarm | ... | |+---------++---------++---------++----------++---------++---------+ | +-------------------------------------------------------------------------+
Figure 1: An overview of Layered YANG Modules
As described in [RFC8309], the service is "some form of connectivity between customer sites and the Internet and/or between customer sites across the network operator's network and across the Internet". More concretely, an IP connectivity service can be defined as the IP transfer capability characterized by a (Source Nets, Destination Nets, Guarantees, Scope) tuple where "Source Nets" is a group of unicast IP addresses, "Destination Nets" is a group of IP unicast and/or multicast addresses, and "Guarantees" reflects the guarantees (expressed in terms of Quality Of Service (QoS), performance, and availability, for example) to properly forward traffic to the said "Destination" [RFC7297].
For example:
Figure 2 depicts a set of Network resource YANG modules such as topology models or tunnel models:
| |
Topo YANG modules | Tunnel YANG modules |Resource NM Tool
------------------------------------------------|-- ------------
+------------+ | |
|Network Top | | +------+ +-----------+ | +-------+
| Model | | |Other | | TE Tunnel | | | LIME |
+----+-------+ | |Tunnel| +------+----+ | | Model |
| +--------+ | +------+ | | |/PM/FM |
|---+Svc Topo| | +--------+-+--------+ |Model |
| +--------+ | +----+---+ +---+----+ +-+-----+ +-------+
| +--------+ | |MPLS-TE | |RSVP-TE | |SR TE | +--------+
|---+L2 Topo | | | Tunnel | | Tunnel | |Tunnel | | Alarm |
| +--------+ | +--------+ +--------+ +-------+ | Model |
| +--------+ | +--------+
|---+TE Topo | | +-----------+
| +--------+ | |Path |
| +--------+ | |Computation|
+---+L3 Topo | | |API Model |
+--------+ | +-----------+
Figure 2: Sample Resource Facing Network Models
Topology YANG module Examples:
Tunnel YANG module Examples:
Resource NM Tool Models:
+----------------+
--|Device Model |
| +----------------+
| +------------------+
+---------------+ | |Logical Network |
| | --| Element Mode |
| Architecture | | +------------------+
| | | +----------------------+
+-------+-------+ --|Network Instance Mode |
| | +----------------------+
| | +-------------------+
| --|Routing Type Model |
| +-------------------+
+-------+----------+----+------+------------+-----------+-------+
| | | | | | |
+-+-+ +---+---+ +--+------+ +-+-+ +-----+---+ +---+-+ |
|ACL| |Routing| |Transport| |OAM| |Multicast| | PM | Others
+---+ |-------+ +---------+ +---+ +---------+ +-----+
| +-------+ +----------+ +-------+ +-----+ +-----+
--|Core | |MPLS Basic| |BFD | |IGMP | |TWAMP|
| |Routing| +----------+ +-------+ |/MLD | +-----+
| +-------+ |MPLS LDP | |LSP Ping +-----+ |OWAMP|
--|BGP | +----------+ +-------+ |PIM | +-----+
| +-------+ |MPLS Static |MPLS-TP| +-----+ |LMAP |
--|ISIS | +----------+ +-------+ |MVPN | +-----+
| +-------+ +-----+
--|OSPF |
| +-------+
--|RIP |
| +-------+
--|VRRP |
| +-------+
--|SR/SRv6|
| +-------+
--|ISIS-SR|
| +-------+
--|OSPF-SR|
+-------+
Figure 3: Network Element Modules Overview
Network Element models (Figure 3) are used to describe how a service can be implemented by activating and tweaking a set of functions (enabled in one or multiple devices, or hosted in cloud infrastructures) that are involved in the service delivery. The following figure uses IETF defined models as an example.
Modularity and extensibility were among the leading design principles of the YANG data modeling language. As a result, the same YANG module can be combined with various sets of other modules and thus form a data model that is tailored to meet the requirements of a specific use case. [RFC8528] defines a mechanism, denoted schema mount, that allows for mounting one data model consisting of any number of YANG modules at a specified location of another (parent) schema.
That capability does not cover design time.
As described in [RFC8199], layering of modules allows for better reusability of lower-layer modules by higher-level modules while limiting duplication of features across layers.
The data modules developed by IETF can be classified into service level, network level and device level modules. Different service level modules may rely on the same set of network level or device level modules. Service level modules usually follow top down approach and are mostly customer-facing modules providing a common model construct for higher level network services, which can be further mapped to network technology-specific modules at lower layer.
Network level modules mostly follow a bottom-up approach and are mainly network resource-facing modules and describe various aspects of a network infrastructure, including devices and their subsystems, and relevant protocols operating at the link and network layers across multiple devices (e.g., Network topology and TE Tunnel modules).
Device level modules usually follow a bottom-up approach and are mostly technology-specific modules used to realize a service.
To dynamically provide service offerings, Service level modules can be used by an operator. One or more monolithic Service modules can be used in the context of a composite service activation request (e.g., delivery of a caching infrastructure over a VPN). Such modules are used to feed a decision-making intelligence to adequately accommodate customer's needs.
Also, such modules may be used jointly with services that require dynamic invocation. An example is provided by the service modules defined by the DOTS WG to dynamically trigger requests to handle DDoS attacks [I-D.ietf-dots-signal-channel][I-D.ietf-dots-data-channel].
Network level modules can be derived from service level modules and used to provision, monitor, instantiate the service and provide lifecycle management of network resources, e.g., expose network resources to customers or operators to provide service fulfillment and assurance and allow customers or operators to dynamically adjust the network resources based on service requirements as described in service level modules and the current network performance information described in the Northbound telemetry modules.
To operate the service, Device level modules derived from Service level modules or Network level modules can be used to provision each involved network function/device with the proper configuration information, and operate the network based on service requirements as described in the Service level module(s).
In addition, the operational state including configuration that is in effect together with statistics should be exposed to upper layers to provide better network visibility (and assess to what extent the derived low level modules are consistent with the upper level inputs). Note that it is important to relate telemetry data with configuration data to used closed loops at the different stages of service delivery, from resource allocation to service operation, in particular.
To support top-down service delivery, the service parameters captured in service level module(s) need to be decomposed into a set of configuration parameters that may be specific to one or more technologies; these technology-specific parameters will be grouped together per technique to define technology-specific device level modules or network level modules.
In addition, these technology-specific device level models can be further assembled together to provision each involved network function/device or each involved administrative domain to improve provision efficiency.
For example, IETF rtgwg and netmod working groups have already been tasked to define a model composition mechanism (i.e., Schema Mount mechanism) and relevant grouping base models such as network instance model, logical network element model . The model composition mechanism can be used to assembler different model together while grouping based models can be used to setup and administrate both virtualized system and physical systems .
IETF also developed a YANG catalog tool to manage metadata around IETF- defined modules; it allows both YANG developers and operators to discover appropriate YANG modules that may be used to automate services operations. This YANG tool catalog tools can be used to select appropriate models for grouping purposes or even to identify gaps.
The architectural considerations described in the previous section lead to the architecture described in this section and illustrated in Figure 4.
The interfaces and interactions shown in the figure and labeled (a) through (j) are further described in Section 4.1.
+-----------------+ ----------------
|Service Requester| Service Level|
+-----------------+ |
+-------------|--------------------------------------------------+ |
| | +----------------------+ | |
| | | | | |
| +--------V---------+ | +------------+ +---+--+| |
| | Service Exposure |-------------V--- IP Service | |Alarm/|| |
| +-------(b)--------+ | Mapping | | PM || |
| | +--(c)-|-----+ +-(g) -+| |
| | | | |
| +---------->|<----------------+ +------------+ |
| | | | | -------------+--
| | | | | Network Level|
| | +--------V---------+ | | | |
| | | IP Service to TE | +------->|<-----------+ | |
| | | Mapping | | | | | | |
| | +-------(f)--------+ | | +------|-----+ | | |
| | | +-----|-----+| | IP Service | +---+--+| |
| | +--------V---------+ |TE Resource|| | Composition| |Alarm/|| |
| | | TE Path | | Exposure || +--(d)-|-----+ | PM || |
| | | Management +----(h)----+| | +-(g) -+| |
| | +-------(e)--------+ | | +------|------+ | |
| | | | | | IP Service | | | |
| | +-----------------+ | | Provision +-----| | |
| | | +-(e)--|------+ | |
| | +-----------++ | |
| | | Resource | | |
| | | Collection | | |
| |------------------------+&Abstraction| | |
| +----(a)-----+ ----------------
+----------------------------------------------------------------+
Figure 4: Service and Network Management Automation with YANG
Network Resources such as links, nodes, or terminate-point resources can be collected from the network and aggregated or abstracted to the management system. Periodic fetching of data is not an adequate solution for applications requiring frequent or prompt updates of network resources. Applying polling-based solutions to retrieve network resource information impacts networks, devices, and applications’ loads. These limitations can be addressed by including generic object subscription mechanisms within network elements.
These resources can be modelled using network topology models, L3 topology model, L2 topology model, TE topology model, L3 TE topology model, SR TE topology models at different layers.
In some cases, there may be multiple overlay topologies built on top of the same underlay topology, and the underlay topology can also be built from one or more lower layer underlay topologies. The network resources and management objects in these multi-layer topologies are not recommended to be exposed to customers, but rather exposed to the management system for IP service mapping and Path Management.
Service exposure & abstraction is used to capture services offered to customers.
Service abstraction can be used by a customer to request a service (ordering and order handling). One typical example is that a customer can use a L3SM service model to request L3VPN service by providing the abstract technical characterization of the intended service.
Service catalogs can be created to expose the various services and the information needed to invoke/order a given service.
YANG modules can be grouped into various service bundles; each service bundle corresponds to a set of YANG modules that have been released or published. Then, a mapping can be established between service abstraction at higher layer and service bundle or a set of YANG modules at lower layer.
Service abstraction starts with high-level abstractions exposing the business capabilities or capturing customer requirements. Then, it needs to map them to resource abstraction and specific network technologies.
Therefore, the interaction between service abstraction in the overlay and network resource abstraction in the underlay is required. For example, in the L3SM service model, a VPN service topology is described as e.g., hub and spoke and any-to-any, single-homed, dual-homed, multi-homed relation between PEs and CEs, but we don't know how this service topology can be mapped into the underlying network topology Section 4.1.8
In addition, there is a need to decide on a mapping between service abstraction and the underlying specific network technologies. Take L3SM service model as an example, to deliver a L3VPN service, we need to map L3SM service view defined in Service model into detailed configuration view defined by specific configuration models for network elements, configuartion information includes:
These configuration models are further grouped together into service bundles, as described in Figure 3using, e.g., device models, logical network element models or network instance models defined in [I.D-ietf-rtgwg-device-model] [RFC8530] [RFC8529] and provide the association between an interface and its associated LNE and NI and populate them into appropriate devices(e.g., PE and CE).
IP Service Provision is used to provide IP network devices with a set of configuration information, e.g., network element models such as BGP, ACL, QoS, Interface model, Network instance models to configure PE and CE devices within the site, etc. A BGP policy model is used to establish VPN membership between sites and VPN Service Topology. Experience shows that "pushing" configuration information to each device one after the other is not efficient.
To automate the configuration of service elements, we first assemble all the related network elements models into logical network element model as defined in [RFC8530] and then establish an association with an interface and a set of network element configurations.
In addition, not all the parameters of the service level model or network level model(e.g., mapped from service level model) needs to be specified, in many cases, some default values, or even some values depending of some contextual information (e.g., the particular service / network element / location / etc) should be taken to automate the configuration process.
Seconldy, IP Service Provision can be used to setup tunnels between sites and setup tunnels between PEs and CEs based upon tunnel-related configuration information that can be derived from service abstraction. However, when tunnel-related configuration parameters cannot be generated from service abstraction, other service Mapping procedure is required,e.g.,IP Service to TE mapping procdure described in Section 4.1.7.
Once the tunnel or VPN is setup, PM and Alarm information per tunnel or per link based on network topology can be collected and report to the management system. This information can be further aggregated and abstracted from layered network topology to monitor and manage network Performance on the topology at different layer or the overlay topology between VPN sites. These network performance information or VPN performance information (e.g., latency or bandwidth utilization between two VPN sites) can be put into NBI telemetry model or NBI performance monitoring model at either service level or network level to further optimize the network or provide troubleshooting support.
Take L3VPN service model as an example, the management system will use L3SM service model to determine where to connect each site- network-access of a particular site to the provider network (e.g., PE, aggregation switch). The L3SM Service model includes parameters that can help design the VPN, according to customer's requirements, for example.
Nodes used to connect a site may be captured in relevant clauses of a service exposure model (e.g., Customer Nodes Map [RFC7297]).
When Site location is determined, PE and CE device location will be selected. Then we can replace parameters and constraints that can influence the meshing of the site-network-access with specified PE and CE device information associated with site-network-access and generate resource facing VN Overlay Resource model. One example of resource facing VN Overlay Resource model is TEAS VN Service Model [I-D.ietf-teas-actn-vn-yang].
This VN model can be used to calculate node and link resource to meet service requirements based on Network Topology models collected at step (a).
Path Management includes Path computation and Path setup. For example, we can derive an instantiated L3SM service model into a resource facing VN Model, with selected PE and CE in each site, we can calculate point- to-point or multipoint end-to-end paths between sites based on the VPN Overlay Resource Model.
After identifying node and link resources required to meet service requirements, the mapping between overlay topology and underlay topology can be established, e.g., establish an association between VPN service topology defined in customer-facing model and underlying network topology defined in the TE topology model (e.g., one overlay node is supported by multiple underlay nodes, one overlay link is supported by multiple underlay nodes) and generate end-to-end VPN topology.
When tunnel-related configuration parameters cannot be derived from service abstraction, IP Service-to-TE Mapping procedure can be used to generate TE Resource Exposure view, this TE resource Exposure view can be modeled as a resource-facing VPN model which is translated and instantiated from a L3SM model and manage TE resources based on path management information and PM and alarm telemetry information.
Operators may use this dedicated TE resource Exposure view to dynamically capture the overall network status and topology to:
Take L3VPN service as an example, IETF has already developed L3VPN service model [RFC8299] which can be used to describe L3VPN service. To enforce L3VPN service and program the network, a set of network element models are needed, e.g., BGP model, Network Instance model, ACL model, Multicast Model, QoS model, or NAT model.
These network element models can be grouped into different release bundles or feature bundles using Schema Mount technology to meet different tailored requirements and deliver the L3VPN service.
To support the creation of logical network elements on a network device and deliver a virtualized network, Logical Network Element (LNE) models can be used to manage its own set of modules such as ACL, QoS, or Network Instance modules.
<================== E2E-NSI =======================>
: : : : :
: : : : :
<====== RAN-NSSI ======><=TRN-NSSI=><====== CN-NSSI ======>VL[APL]
: : : : : : : : :
: : : : : : : : :
RW[NFs ]<=TRN-NSSI=>[NFs ]<=TRN-NSSI=>[NFs ]<=TRN-NSSI=>[NFs ]VL[APL]
. . . . . . . . . . . . .. . . . . . . . . . . . . ..
.,----. ,----. ,----.. ,----. .,----. ,----. ,----..
UE--|RAN |---| TN |---|RAN |---| TN |---|CN |---| TN |---|CN |--[APL]
.|NFs | `----' |NFs |. `----' .|NFs | `----' |NFs |.
.`----' `----'. .`----' `----'.
. . . . . . . . . . . . .. . . . . . . . . . . . . ..
RW RAN MBH CN DN
*Legends
UE: User Equipment
RAN: Radio Access Network
CN: Core Network
DN: Data Network
TN: Transport Network
MBH: Mobile Backhaul
RW: Radio Wave
NF: Network Function
APL: Application Server
NSI: Network Slice Instance
NSSI: Network Slice Subnet Instance
Figure 5: Overview of Structure of NS in 3GPP 5GS
The overview of network slice structure as defined in the 3GPP 5GS is shown in Figure 5. The terms are described in specific 3GPP documents (e.g., [TS.23.501-3GPP] and [TS.28.530-3GPP]).
To support 5G service (e.g., 5G MBB service), L3VPN service model [RFC8299] and TEAS VN model [I-D. ietf-teas-actn-vn-yang] can be both provided to describe 5G MBB Transport Service or connectivity service. L3VPN service model is used to describe end-to-end connectivity service while TEAS VN model is used to describe TE connectivity service between VPN sites or between RAN NFs and Core network NFs.
VN in TEAS VN model and support point-to-point or multipoint-to-multipoint connectivity service and can be seen as one example of network slice.
TE Service mapping model can be used to map L3VPN service requests onto underlying network resource and TE models to get TE network setup.
For IP VPN service provision, L3VPN service model is used to derive a set of configuration parameterswhich will be bound to different network element models and group them together to form feature or service bundles to deliver the VPN service.
|(2)
|
V
+-------------------+
| Management System | (3)(4)(5)
+-------------------+
+--------------------------------------------------------+
/ _[CE2] _[CE3] /
/ _/ : \_ _/ : \_ /
/ _/ : \_ _/ : \_ /
/ _/ : \_ _/ : \_ /
/ / : \ / : \ /
/[CE1]_________________[PE1] [PE2]_________________[CE4] /
+---------:--------------:------------:--------------:---+
"Service"
--------------------------------------------------------------------
+---------------------+ +---------------------+"Resource"
/ [Y5]... / / [Z5]______[Z3] /
/ / \ : / / : \_ / : /
/ / \ : / / : \_ / : /
/ / \ : / / : \ / : /
/ [Y4]____[Y1] : / / : [Z2] : /
+------:-------:---:--+ +---:---------:-----:-+ ^
vNet1 : : : : : : vNet2 |
: : : : : : |(1)
: +-------:---:-----:------------:-----:-----+ |
: / [X1]__:___:___________[X2] : / |
:/ / \_ : : _____/ / : / |
: / \_ : _____/ / : /
/: / \: / / : /
/ : / [X5] / : /
/ : / __/ \__ / : /
/ : / ___/ \__ / : /
/ : / ___/ \ / : /
/ [X4]__________________[X3]..: /
+------------------------------------------+
L3 Topology
The following steps are performed to deliver the service within the network management automation architecture proposed in this document:
The network initiated resource creation is similar to ready-made Network Slice creation pattern discussed in Section 5.1 of [I-D.homma-slice-provision-models].
|(2)
|
V
+-------------------+
| Management System | (3)(4)(5)
+-------------------+
+--------------------------------------------------------+
/ _[CE2] _[CE3] /
/ _/ : \_ _/ : \_ /
/ _/ : \_ _/ : \_ /
/ _/ : \_ _/ : \_ /
/ / : \ / : \ /
/[CE1]_________________[PE1] [PE2]_________________[CE4] /
+---------:--------------:------------:--------------:---+
"Service"
--------------------------------------------------------------------
"Resource" ^
: |
: : : |(1)
: +-------:---:-----:------------:-----:-----+ |
: / [X1]__:___ __________[X2] / |
:/ / \_ : _____/ / / |
: / \_ : _____/ / /
/: / \: / / /
/ : / [X5] / /
/ : / __/ \__ / /
/ : / ___/ \__ / /
/ : / ___/ \ / /
/ [X4]__________________[X3]. /
+------------------------------------------+
L3 Topology
The following steps are performed to deliver the service within the network management automation architecture proposed in this document:
The customer-initiated resource creation is similar to customer made Network Slice creation pattern discussed in Section 5.2 of [I-D.homma-slice-provision-models].
Security considerations specific to each of the technologies and protocols listed in the document are discussed in the specification documents of each of these techniques.
(Potential) security considerations specific to this document are listed below:
There are no IANA requests or assignments included in this document.
Shunsuke Homma Japan Email: s.homma0718+ietf@gmail.com
Thanks to Joe Clark and Greg Mirsky for the review.