Networking Working Group Q. Wu
Internet-Draft Huawei
Intended status: Informational M. Boucadair
Expires: September 9, 2019 Orange
Y. Lee
March 8, 2019

Framework for Automating Service and Network Management with YANG


Model driven service and network management provides a programmatic and standards-based way of representing virtual services or networks and configuration to the network device that are used to construct the service. It can be used at various phases of service and network management life cycle such as service instantiation, service provision, optimization, monitoring, and diagnostic. Also, it can be designed to automate network management and provide closed-loop control for the sake of agile service creation, delivery and maintenance.

This document provides a framework that describes and discusses an architecture for service and network management automation with YANG Modeling technologies. An applicability of YANG data model to automation of virtualized network service is also investigated.

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

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 September 9, 2019.

Copyright Notice

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

Table of Contents

1. Introduction

The manage system usually comprise service activation/provision system and service enforcement system. Tranditional service delivery work flow, from customer order to practical service provision, the work flow process typically involves inputting data sequentially into multiple OSS/BSS applications managed by different departments; Many of these applications are custom built over the years and operating in silo mode; Lacking of standard data input/output also causes lots of challenge in system integration and results in manual data entry; Customer MACD(Move, Add, Change, Delete) will incur the same repetitive process in many cases. Secondly traditional service fulfill system lack a programmatic and standards-based way of writing configurations to any network device and has slow response to the network changes and doesn't provide real time monitoring capability in high frequency and in high throughput on the current state of the system. Therefore model driven network management becomes crutial to address these chanllenges.

For years, the IETF has been driving the industry transition from an overloaded Software Defined Networking (SDN) buzzword to focus on specific areas such as modeling-driven network management. [RFC7149] provides a first tentative to rationalize that space by identifying concrete technical domains that need to be considered:

Models are key for each of these technical items. Automation is a key step to improve the agility of network operations and infrastructure.

In the later development, as described in [RFC8199], YANG module developers have taken both top-down and bottom-up approaches to develop modules and establish mapping between network technology and customer requirements on the top or abstracting common construct from various network technologies. At the time of writing this document (2018), we see the large number of data models including configuration models and service models developed or under development in IETF covering much of networking protocols and techniques. In addition, how these models work together to fully configure a device, or manage a set of devices involved in a service aren't developed yet in IETF.

This document takes both bottom up approach and top down approach to provide a framework that discusses the architecture for network management automation, with a focus on network virtualization environment.

This document also describes specific YANG modules needed to realize connectivity services and investigates how top down built model (e.g., customer-facing data models) interact with bottom up built model (network resource-facing data models) in the context of service delivery and assurance.

2. Architectural Concepts

2.1. Data Models: Layering and Representation

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 IETF has developed large number of 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 models providing a common model construct for higher level network services, which can be further mapped to network technology-specific models at lower layer.

Network level modules mostly follow bottom up approach and are mainly network resource-facing model 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 bottom up approach and are mostly technology-specific modules used to realize a service.

2.2. Service Activation and Provision Automation

To provide more agile service offering, Service level module can be used by the operator to communicate with the customer and have rapid response to customer needs. Network level module can be translated from service level module and used to provision, monitor, instantiate the service and provide lifecycle management of network resource,e.g., expose network resource to the customer or operators.

2.3. Service Enforcement Configuration Model Composition

To provide network management automation, lower level technology-specific models need to be assembled together to provision each involved network function/device and operate the network based on service requirements described in the service level model.

IETF RTGWG working group has already been tasked to define service elements configuration model composition mechanism and develop several composition model such as network instance model, logical network element model and device model.

These models can be used to setup and administrate both virtualized system and physical system.

2.4. A Catalog for YANG Modules

The idea of a catalog is similar to service catalogs in traditional IT environments. Service catalogs serve as a software-based registries of available services with information needed to discover and invoke available services.

The IETF has already tasked to develop a YANG catalog which can be used to manage not only IETF defined modules, but also non-IETF defined ones [I-D.clacla-netmod-model-catalog].

The YANG catalog allows to align IETF work with other SDOs work and prevent duplicated building blocks being developed. It also encourages reusability of common building blocks.

The YANG catalog allows both YANG developers and operators to discover the more mature YANG modules that may be used to automate services operations .

3. IETF YANG Modules: An Overview

   <<Network Service and Resource Models>>
| << Network Service Models>>                                           |
| +----------------+ +----------------+ +-------------+                 |
| |      L3SM      | |     L2SM       | | TEAS VN     |    L1CSM        |
| |  Service Model | |  Service Model | |Service Model| Service Model   |
| +----------------+ +----------------+ +-------------+                 |
|-------------------------------------------------------------------    |
| << Network Resource Models >>                                         |
|      +------------+  +-------+  +----------------+   +------------+   |
|      |Network Topo|  | Tunnel|  |Path Computation|   |OAM,PM,Alarm|   |
|      |   Models   |  | Models|  | API Models     |   |   Models   |   |
|      +------------+  +-------+  +----------------+   +------------+   |
 <Network Element Models>>
|  <<Composition Models>>                                               |
|      +-------------+ +---------------+ +----------------+             |
|      |Device Model | |Logical Network| |Network Instance|             |
|      |             | |Element Model  | |   Model        |             |
|      +-------------+ +---------------+ +----------------+             |
|---------------------------------------------------------------------- |
| << Component Models>>                                                 |
|                                   +----------+                        |
|+---------++---------+ +---------+ |Common    |+---------+             |
|| Routing ||Transport| | Policy  | |(interface||Multicast|+-------+    |
||(e.g.,BGP||(e.g.,   | |(e.g,ACL | |multicast || (IGMP   ||OAM,PM,|    |
|| OSPF..) || MPLS..) | |  QoS..) | | IP...   )|| MLD..)  ||Alarm  | ...|
|+---------++---------+ +---------+ +----------++---------++-------+    |

3.1. Network Service and Resource Models

Service and Network Resource modules define what the "service"/"resource" is. These modules can be classified into two categories:

3.1.1. Network Service Models: Definition and Samples

As described in [RFC8309], the service is some form of connectivity between customer sites and the Internet or between customer sites across the network operator's network and across the Internet. Such connectivity service is described without resource allocation or with half service resource correlation.

For example,

3.1.2. Network Resource Models

Figure 1 shows a set of Network resource YANG modules such as topology models, tunnel models:

                     |                             |
    Topo YANG Models |    Tunnel YANG Models       |Resource NM Tool
   ------------------------------------------------|-- ------------
+------------+       |                             |
|Network Top |       | +------+  +-----------+     |       +-------+
|   Model    |       | |Other |  | TE Tunnel |     |       | LIME  |
+----+-------+       | |Tunnel|  +------+----+     |       | Model |
     |   +--------+  | +------+         |          |       |/PM/OAM|
     |---+Svc Topo|  |         +--------+-+--------+       |  Model|
     |   +--------+  |    +----+---+  +---+----+ +-+-----+ +-------+
     |   +--------+  |    |MPLS-TE |  |RSVP-TE | |SR TE  | +--------+
     |---+L2 Topo |  |    | Tunnel |  | Tunnel | |Tunnel | |  Alarm |
     |   +--------+  |    +--------+  +--------+ +-------+ |  Model |
     |   +--------+  |                                     +--------+
     |---+TE Topo |  |                                   +-----------+
     |   +--------+  |                                   |Path       |
     |   +--------+  |                                   |Computation|
     +---+L3 Topo |                                      |API Model  |
         +----|---+                                      +-----------+
    |         |         |
+---|---+  +--|---+ +---|-+
|SR Topo|  |SR TE | |L3 TE|
| Model |  | Topo | |Topo |
+-------+  +------+ +-----+

Figure 1: Sample Resource Facing Network Models

Topology YANG Models:

Tunnel YANG Models:

Resource NM Tool Models:

3.2. Network Element 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   |
      | +-------+
      | +-------+
      | +-------+

Figure 2

Network Element models are used to describe how a service can be implemented by activating and tweaking a set of functions (enabled in one or multiple devices) that are involved in the service delivery.

3.2.1. Model Composition Schema Mount

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.

3.2.2. Protocol/Function Configuration Models

[I-D.ietf-idr-bgp-yang-model] defines a YANG module for configuring and managing BGP, including protocol, policy, and operational aspects based on data center, carrier and content provider operational requirements.
[I-D.ietf-mpls-base-yang] defines a base model for MPLS which serves as a base framework for configuring and managing an MPLS switching subsystem. It is expected that other MPLS technology YANG models (e.g. MPLS LSP Static, LDP or RSVP-TE models) will augment the MPLS base YANG model.
[I-D.asechoud-netmod-diffserv-model] describes a YANG model of Differentiated Services for configuration and operations.
Access Control List (ACL) is one of the basic elements used to configure device forwarding behavior. It is used in many networking technologies such as Policy Based Routing, Firewalls etc. [I.D-ietf-netmod-acl-model] describes a data model of Access Control List (ACL) basic building blocks.
For the sake of network automation and the need for programming Network Address Translation (NAT) function in particular, a data model for configuring and managing the NAT is essential. [I.D-ietf-opsawg-nat-yang] defines a YANG module for the NAT function.
[I-D.ietf-pim-yang] defines a YANG module that can be used to configure and manage Protocol Independent Multicast (PIM) devices. [I-D.ietf-pim-igmp-mld-yang] defines a YANG module that can be used to configure and manage Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) devices. [I-D.ietf-pim-igmp-mld-snooping-yang] defines a YANG data model that can be used to configure and manage Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping devices.
[I-D.ietf-bess-evpn-yang] defines a YANG data model for Ethernet VPN services.The model is agnostic of the underlay. It apply to MPLS as well as to VxLAN encapsulation. The model is also agnostic of the services including E-LAN, E-LINE and E-TREE services. This document mainly focuses on EVPN and Ethernet-Segment instance framework.
[I-D.ietf-bess-l3vpn-yang] defines a YANG model that can be used to configure and manage BGP L3VPNs [RFC4364]. It contains VRF sepcific parameters as well as BGP specific parameters applicable for L3VPNs.
[I-D.ietf-bess-l2vpn-yang] defines a YANG data model for MPLS based Layer 2 VPN services (L2VPN) [RFC4664] and includes switching between the local attachment circuits. The L2VPN model covers point-to-point VPWS and Multipoint VPLS services. These services use signaling of Pseudowires across MPLS networks using LDP [RFC8077][RFC4762] or BGP[RFC4761].
Routing Policy:
[I-D.ietf-rtgwg-policy-model] defines a YANG data model for configuring and managing routing policies in a vendor-neutral way and based on actual operational practice. The model provides a generic policy framework which can be augmented with protocol-specific policy configuration.
[I-D.ietf-bfd-yang]defines a YANG data model that can be used to configure and manage Bidirectional Forwarding Detection (BFD) [RFC5880]. BFD is a network protocol which is used for liveness detection of arbitrary paths between systems.
[I-D.ietf-spring-sr-yang] a YANG data model for segment routing configuration and operation. [I-D.raza-spring-srv6-yang] defines a YANG data model for Segment Routing IPv6 (SRv6) base. The model serves as a base framework for configuring and managing an SRv6 subsystem and expected to be augmented by other SRv6 technology models accordingly.
Core Routing:
[RFC8349] defines the core routing data model, which is intended as a basis for future data model development covering more-sophisticated routing systems. It is expected that other Routing technology YANG models (e.g. VRRP, RIP, ISIS, OSPF models) will augment the Core Routing base YANG model.
PM Models:

[I.D-ietf-ippm-twamp-yang] defines a data model for client and server implementations of the Two-Way Active Measurement Protocol (TWAMP).

[I.D-ietf-ippm-stamp-yang] defines the data model for implementations of Session-Sender and Session-Reflector for Simple Two-way Active Measurement Protocol (STAMP) mode using YANG.

[RFC8194] defines a data model for Large-Scale Measurement Platforms (LMAPs).

4. YANG model Catalog for L3VPN Service

The model catalog provides enough information for users to determine which YANG modules or module bundles are available to describe a specific service or technology. 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, NAT model, these network element models can be grouped into different release bundles or feature bundle using Schema Mount technology to meet different tailored requirements and realize L3VPN service. To support the creation of logical network elements on a network device and enable automation of virtualized network, Logical Network Element(LNE) model can be used to manages its own set of modules such as ACL, QoS, Network Instance modules.

5. YANG model Catalog for 5G Transport Service

   <==================          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

  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 

Overview of Structure of NS in 3GPP 5GS

The overview of structure of Network slice in the 3GPP 5GS is shown in Figure 4. The terms are described in the 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 and 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 will be translated into a set of network element configuration parameters, these configuration parameters will go to different network element models and group them together to form feature bundle or service bundle to get L3VPN network setup.

6. Architecture Overview

The architectural considerations and conclusions described in the previous section lead to the architecture described in this section and illustrated in Figure 3.

The interfaces and interactions shown in the figure and labeled (a) through (j) are further described in Section 5.1.

      +-----------------+                                        ------
      |Service Requester|                                           |
      +-----------------+                                           |
+-------------|--------------------------------------------------+ Service Level
|    +--------V---------+                +------------+          |  |
|    | Service Exposure |----------------- IP Service |          |  |
|    +-------(b)--------+                |  Mapping   |          |  |
|             |                          +--(c)-|-----+          |  |
|             |                                 |                ------
| |---------->|<----------------+               |                |  |
| |  +--------V---------+       |               |                |  |
| |  | IP Service to TE         |      +------->|<-----------+   |  |
| |  |    Mapping       |       |      |        |            |   |  |
| |  +-------(f)--------+       |      | +------|-----+      |   |  |
| |           |           +-----|-----+| | IP Service |  +---+--+|  |
| |  +--------V---------+ |TE Resource|| | Composition|  |Alarm/||Network Level
| |  |     TE Path      | | Exposure  || +--(d)-|-----+  |  PM  ||  |
| |  |   Management       +----(h)----+|        |        +-(g) -+|  |
| |  +-------(e)--------+       |      | +------|------+         |  |
| |           |                 |      | | IP Service  |     |   |  |
| |           +-----------------+      | | Provision   +-----|   |  |
| |                                    | +-(e)--|------+         |  |
| |                        +-----------++                        |  |
| |                        | Resource   |                        |  |
| |                        | Collection |                        |  |
| |------------------------+&Abstraction|                        |  |
|                          +----(a)-----+                        ------

Figure 3: Service and Network Management Automation with YANG

6.1. End-to-End Service Delivery and Service Assurance Procedure

6.1.1. Resource Collection and Abstraction (a)

Network Resource 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 resource. Applying polling-based solutions to retrieve network resource also imposes a load on networks, devices, and applications.These limitations can be addressed by including generic object subscription mechanisms within network elements.

These resources can be modelled using network topology model, 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 have multiple overlay topologies built on top of the same underlay topology, and the underlay topology can be also built from one or more lower layer underlay topology.

In some cases, there may have multiple overlay topologies built on top of the same underlay topology, and the underlay topology can be also built from one or more lower layer underlay topology. The network resources and management objects in these multi-layer topologies are not recommended to be exposed to customers who (will) order the service from the management system, instead it will be exposed to the management system for IP service mapping and TE path Management.

The abstract view is likely to be technology-agnostic.

6.1.2. Service Exposure & Abstraction (b)

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 L3SM service model to request L3VPN service by providing the abstract technical characterization of the intended service. Such L3VPN service describes various aspects of network infrastructure, including devices and their subsystems, and relevant protocols operating at the link and network layers across multiple device. The L3SM service model can be used to interact with the network infrastructure, e.g., configure sites, decide QoS parameters to be applied to end to end connectivity between VPN sites, select PEs, CEs, etc.

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 is corresponding 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.

6.1.3. IP Service Mapping (c)

Service abstraction starts with high-level abstractions exposing the business capabilities or capturing customer requirements. Then, it needs to maps 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, we describe VPN service topology including sites relationship, 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 underlying network topology. For detailed interaction, please refer to Section 6.1.8

In addition, there is a need to decide on a mapping between service abstraction and underlying specific network technologies. Take L3SM service model as an example, to realize 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, these configuration models include:

6.1.4. IP Service Composition (d)

These detailed configuration models are further assembled together into service bundle described inFigure 2 using, e.g., device model, logical network element model or network instance model 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).

6.1.5. IP Service Provision (e)

IP Service Provision is used to provision network infrastructure using various configuration models, e.g., use network element models such as BGP, ACL, QoS, Interface model, Network instance models to configure PE and CE device within the site. BGP Policy model is used to establish VPN membership between sites and VPN Service Topology. Traditionally, "push" service element configuration model one by one to the network device and provide association between an interface and each service element configuration model is not efficient.

To automate configuration of the service elements, we first assemble all related network elements models into logical network element model defined in [RFC8530] and then establish association with an interface and a set of network element configurations.

In addition, IP Service Provision can be used to setup tunnels between sites and setup tunnels between PE and CE within the site when tunnels related configuration parameters can be generated from service abstraction.However when tunnels related configuration parameters can not be generated from service abstraction, IP Service to TE Mapping procedure is required.

6.1.6. Performance Measurement and Alarm Telemetry (f)

Once the tunnel is setup, PM and Warning information per tunnel or per link based on network topology can be collected and report to the management system. This information can be used to optimize the network or provide troubleshooting support.

6.1.7. IP Service to TE Mapping (g)

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). L3SM Service model proposes parameters and constraints that can influence the meshing of the site-network-access.

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 Overlay Resource model can be used to calculate node and link resource to Meet service requirements based on Network Topology models collected at step (a).

6.1.8. Path Management (h)

Path Management includes Path computation and Path setup. For example, we can translate L3SM service model into resource facing VN Model, with selected PE and CE in each site, we can calculate point to point or multipoint end to end path between sites based on VN 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 VN topology.

6.1.9. TE Resource Exposure (i)

When tunnels related configuration parameters can not be generated from service abstraction, IP Service to TE Mapping procedure can be used to generate TE Resource Exposure view, this TE reource Exposure view can be modeled as resource facing VN model which is translated and instantiated from L3SM model and manage TE resource 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:

7. Model usage in automated virtualized network environment: Sample Examples

7.1. Network initiated resource creation

                      | Management System | (3)(4)(5)

       /     _[CE2]                      _[CE3]                 /
      /    _/  :   \_                  _/  :   \_              /
     /   _/     :    \_              _/     :    \_           /
    /  _/        :     \_          _/        :     \_        /
   /  /           :      \        /           :      \      /
  /[CE1]_________________[PE1] [PE2]_________________[CE4] /
        +---------------------+    +---------------------+"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].

7.2. Customer initiated Dynamic Resource Creation

                      | Management System | (3)(4)(5)

       /     _[CE2]                      _[CE3]                 /
      /    _/  :   \_                  _/  :   \_              /
     /   _/     :    \_              _/     :    \_           /
    /  _/        :     \_          _/        :     \_        /
   /  /           :      \        /           :      \      /
  /[CE1]_________________[PE1] [PE2]_________________[CE4] /
                                                        "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].

8. Security Considerations

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:

9. IANA Considerations

There are no IANA requests or assignments included in this document.

10. Contributors

   Shunsuke Homma


11. Informative References

[I-D.arkko-arch-virtualization] Arkko, J., Tantsura, J., Halpern, J. and B. Varga, "Considerations on Network Virtualization and Slicing", Internet-Draft draft-arkko-arch-virtualization-01, March 2018.
[I-D.asechoud-netmod-diffserv-model] Choudhary, A., Shah, S., Jethanandani, M., Liu, B. and N. Strahle, "YANG Model for Diffserv", Internet-Draft draft-asechoud-netmod-diffserv-model-03, June 2015.
[I-D.clacla-netmod-model-catalog] Clarke, J. and B. Claise, "YANG module for", Internet-Draft draft-clacla-netmod-model-catalog-03, April 2018.
[I-D.evenwu-opsawg-yang-composed-vpn] Even, R., Bo, W., Wu, Q. and Y. Cheng, "YANG Data Model for Composed VPN Service Delivery", Internet-Draft draft-evenwu-opsawg-yang-composed-vpn-02, March 2019.
[I-D.homma-slice-provision-models] Homma, S., Nishihara, H., Miyasaka, T., Galis, A., OV, V., Lopez, D., Contreras, L., Ordonez-Lucena, J., Martinez-Julia, P., Qiang, L., Rokui, R., Ciavaglia, L. and X. Foy, "Network Slice Provision Models", Internet-Draft draft-homma-slice-provision-models-00, February 2019.
[I-D.ietf-bess-evpn-yang] Brissette, P., Shah, H., Hussain, I., Tiruveedhula, K. and J. Rabadan, "Yang Data Model for EVPN", Internet-Draft draft-ietf-bess-evpn-yang-06, October 2018.
[I-D.ietf-bess-l2vpn-yang] Shah, H., Brissette, P., Chen, I., Hussain, I., Wen, B. and K. Tiruveedhula, "YANG Data Model for MPLS-based L2VPN", Internet-Draft draft-ietf-bess-l2vpn-yang-09, October 2018.
[I-D.ietf-bess-l3vpn-yang] Jain, D., Patel, K., Brissette, P., Li, Z., Zhuang, S., Liu, X., Haas, J., Esale, S. and B. Wen, "Yang Data Model for BGP/MPLS L3 VPNs", Internet-Draft draft-ietf-bess-l3vpn-yang-04, October 2018.
[I-D.ietf-bfd-yang] Rahman, R., Zheng, L., Jethanandani, M., Networks, J. and G. Mirsky, "YANG Data Model for Bidirectional Forwarding Detection (BFD)", Internet-Draft draft-ietf-bfd-yang-17, August 2018.
[I-D.ietf-ccamp-alarm-module] Vallin, S. and M. Bjorklund, "YANG Alarm Module", Internet-Draft draft-ietf-ccamp-alarm-module-07, January 2019.
[I-D.ietf-ccamp-flexigrid-media-channel-yang] Madrid, U., Perdices, D., Lopezalvarez, V., Dios, O., King, D., Lee, Y. and G. Galimberti, "YANG data model for Flexi-Grid media-channels", Internet-Draft draft-ietf-ccamp-flexigrid-media-channel-yang-01, October 2018.
[I-D.ietf-ccamp-flexigrid-yang] Madrid, U., Perdices, D., Lopezalvarez, V., Dios, O., King, D., Lee, Y. and G. Galimberti, "YANG data model for Flexi-Grid Optical Networks", Internet-Draft draft-ietf-ccamp-flexigrid-yang-02, October 2018.
[I-D.ietf-ccamp-l1csm-yang] Fioccola, G., Lee, K., Lee, Y., Dhody, D. and D. Ceccarelli, "A YANG Data Model for L1 Connectivity Service Model (L1CSM)", Internet-Draft draft-ietf-ccamp-l1csm-yang-08, September 2018.
[I-D.ietf-ccamp-mw-yang] Ahlberg, J., Ye, M., Li, X., Spreafico, D. and M. Vaupotic, "A YANG Data Model for Microwave Radio Link", Internet-Draft draft-ietf-ccamp-mw-yang-13, November 2018.
[I-D.ietf-ccamp-otn-topo-yang] Zheng, H., Guo, A., Busi, I., Sharma, A., Liu, X., Belotti, S., Xu, Y., Wang, L. and O. Dios, "A YANG Data Model for Optical Transport Network Topology", Internet-Draft draft-ietf-ccamp-otn-topo-yang-06, February 2019.
[I-D.ietf-ccamp-otn-tunnel-model] Zheng, H., Guo, A., Busi, I., Sharma, A., Rao, R., Belotti, S., Lopezalvarez, V., Li, Y. and Y. Xu, "OTN Tunnel YANG Model", Internet-Draft draft-ietf-ccamp-otn-tunnel-model-06, February 2019.
[I-D.ietf-ccamp-wson-tunnel-model] Lee, Y., Dhody, D., Guo, A., Lopezalvarez, V., King, D., Yoon, B. and R. Vilata, "A Yang Data Model for WSON Tunnel", Internet-Draft draft-ietf-ccamp-wson-tunnel-model-02, October 2018.
[I-D.ietf-idr-bgp-model] Patel, K., Jethanandani, M. and S. Hares, "BGP YANG Model for Service Provider Networks", Internet-Draft draft-ietf-idr-bgp-model-04, February 2019.
[I-D.ietf-ippm-stamp-yang] Mirsky, G., Xiao, M. and W. Luo, "Simple Two-way Active Measurement Protocol (STAMP) Data Model", Internet-Draft draft-ietf-ippm-stamp-yang-03, March 2019.
[I-D.ietf-ippm-twamp-yang] Civil, R., Morton, A., Rahman, R., Jethanandani, M. and K. Pentikousis, "Two-Way Active Measurement Protocol (TWAMP) Data Model", Internet-Draft draft-ietf-ippm-twamp-yang-13, July 2018.
[I-D.ietf-lime-yang-connection-oriented-oam-model] Kumar, D., Wu, Q. and Z. Wang, "Generic YANG Data Model for Connection Oriented Operations, Administration, and Maintenance(OAM) protocols", Internet-Draft draft-ietf-lime-yang-connection-oriented-oam-model-07, February 2018.
[I-D.ietf-lime-yang-connectionless-oam] Kumar, D., Wang, Z., Wu, Q., Rahman, R. and S. Raghavan, "Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols that use Connectionless Communications", Internet-Draft draft-ietf-lime-yang-connectionless-oam-18, November 2017.
[I-D.ietf-lime-yang-connectionless-oam-methods] Kumar, D., Wang, Z., Wu, Q., Rahman, R. and S. Raghavan, "Retrieval Methods YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols that use Connectionless Communications", Internet-Draft draft-ietf-lime-yang-connectionless-oam-methods-13, November 2017.
[I-D.ietf-mpls-base-yang] Saad, T., Raza, K., Gandhi, R., Liu, X. and V. Beeram, "A YANG Data Model for MPLS Base", Internet-Draft draft-ietf-mpls-base-yang-10, February 2019.
[I-D.ietf-netmod-acl-model] Jethanandani, M., Agarwal, S., Huang, L. and D. Blair, "Network Access Control List (ACL) YANG Data Model", Internet-Draft draft-ietf-netmod-acl-model-21, November 2018.
[I-D.ietf-pim-igmp-mld-snooping-yang] Zhao, H., Liu, X., Liu, Y., Sivakumar, M. and A. Peter, "A Yang Data Model for IGMP and MLD Snooping", Internet-Draft draft-ietf-pim-igmp-mld-snooping-yang-07, January 2019.
[I-D.ietf-pim-igmp-mld-yang] Liu, X., Guo, F., Sivakumar, M., McAllister, P. and A. Peter, "A YANG data model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD)", Internet-Draft draft-ietf-pim-igmp-mld-yang-10, January 2019.
[I-D.ietf-pim-yang] Liu, X., McAllister, P., Peter, A., Sivakumar, M., Liu, Y. and f. hu, "A YANG Data Model for Protocol Independent Multicast (PIM)", Internet-Draft draft-ietf-pim-yang-17, May 2018.
[I-D.ietf-rtgwg-device-model] Lindem, A., Berger, L., Bogdanovic, D. and C. Hopps, "Network Device YANG Logical Organization", Internet-Draft draft-ietf-rtgwg-device-model-02, March 2017.
[I-D.ietf-rtgwg-policy-model] Qu, Y., Tantsura, J., Lindem, A. and X. Liu, "A YANG Data Model for Routing Policy Management", Internet-Draft draft-ietf-rtgwg-policy-model-05, January 2019.
[I-D.ietf-spring-sr-yang] Litkowski, S., Qu, Y., Lindem, A., Sarkar, P. and J. Tantsura, "YANG Data Model for Segment Routing", Internet-Draft draft-ietf-spring-sr-yang-12, February 2019.
[I-D.ietf-teas-actn-vn-yang] Lee, Y., Dhody, D., Ceccarelli, D., Bryskin, I., Yoon, B., Wu, Q. and P. Park, "A Yang Data Model for VN Operation", Internet-Draft draft-ietf-teas-actn-vn-yang-04, February 2019.
[I-D.ietf-teas-sf-aware-topo-model] Bryskin, I., Liu, X., Lee, Y., Guichard, J., Contreras, L., Ceccarelli, D. and J. Tantsura, "SF Aware TE Topology YANG Model", Internet-Draft draft-ietf-teas-sf-aware-topo-model-02, September 2018.
[I-D.ietf-teas-te-service-mapping-yang] Lee, Y., Dhody, D., Ceccarelli, D., Tantsura, J., Fioccola, G. and Q. Wu, "Traffic Engineering and Service Mapping Yang Model", Internet-Draft draft-ietf-teas-te-service-mapping-yang-00, March 2019.
[I-D.ietf-teas-yang-l3-te-topo] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H. and O. Dios, "YANG Data Model for Layer 3 TE Topologies", Internet-Draft draft-ietf-teas-yang-l3-te-topo-03, October 2018.
[I-D.ietf-teas-yang-path-computation] Busi, I., Belotti, S., Lopezalvarez, V., Dios, O., Sharma, A., Shi, Y., Vilata, R., Sethuraman, K., Scharf, M. and D. Ceccarelli, "Yang model for requesting Path Computation", Internet-Draft draft-ietf-teas-yang-path-computation-04, November 2018.
[I-D.ietf-teas-yang-rsvp-te] Beeram, V., Saad, T., Gandhi, R., Liu, X., Bryskin, I. and H. Shah, "A YANG Data Model for RSVP-TE Protocol", Internet-Draft draft-ietf-teas-yang-rsvp-te-05, February 2019.
[I-D.ietf-teas-yang-sr-te-topo] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H. and S. Litkowski, "YANG Data Model for SR and SR TE Topologies", Internet-Draft draft-ietf-teas-yang-sr-te-topo-03, October 2018.
[I-D.ietf-teas-yang-te] Saad, T., Gandhi, R., Liu, X., Beeram, V. and I. Bryskin, "A YANG Data Model for Traffic Engineering Tunnels and Interfaces", Internet-Draft draft-ietf-teas-yang-te-19, February 2019.
[I-D.ietf-teas-yang-te-topo] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H. and O. Dios, "YANG Data Model for Traffic Engineering (TE) Topologies", Internet-Draft draft-ietf-teas-yang-te-topo-19, February 2019.
[RFC7149] Boucadair, M. and C. Jacquenet, "Software-Defined Networking: A Perspective from within a Service Provider Environment", RFC 7149, DOI 10.17487/RFC7149, March 2014.
[RFC7297] Boucadair, M., Jacquenet, C. and N. Wang, "IP Connectivity Provisioning Profile (CPP)", RFC 7297, DOI 10.17487/RFC7297, July 2014.
[RFC8194] Schoenwaelder, J. and V. Bajpai, "A YANG Data Model for LMAP Measurement Agents", RFC 8194, DOI 10.17487/RFC8194, August 2017.
[RFC8199] Bogdanovic, D., Claise, B. and C. Moberg, "YANG Module Classification", RFC 8199, DOI 10.17487/RFC8199, July 2017.
[RFC8299] Wu, Q., Litkowski, S., Tomotaki, L. and K. Ogaki, "YANG Data Model for L3VPN Service Delivery", RFC 8299, DOI 10.17487/RFC8299, January 2018.
[RFC8309] Wu, Q., Liu, W. and A. Farrel, "Service Models Explained", RFC 8309, DOI 10.17487/RFC8309, January 2018.
[RFC8328] Liu, W., Xie, C., Strassner, J., Karagiannis, G., Klyus, M., Bi, J., Cheng, Y. and D. Zhang, "Policy-Based Management Framework for the Simplified Use of Policy Abstractions (SUPA)", RFC 8328, DOI 10.17487/RFC8328, March 2018.
[RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., Ananthakrishnan, H. and X. Liu, "A YANG Data Model for Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March 2018.
[RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X., Ananthakrishnan, H. and N. Bahadur, "A YANG Data Model for Layer 3 Topologies", RFC 8346, DOI 10.17487/RFC8346, March 2018.
[RFC8349] Lhotka, L., Lindem, A. and Y. Qu, "A YANG Data Model for Routing Management (NMDA Version)", RFC 8349, DOI 10.17487/RFC8349, March 2018.
[RFC8466] Wen, B., Fioccola, G., Xie, C. and L. Jalil, "A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery", RFC 8466, DOI 10.17487/RFC8466, October 2018.
[RFC8512] Boucadair, M., Sivakumar, S., Jacquenet, C., Vinapamula, S. and Q. Wu, "A YANG Module for Network Address Translation (NAT) and Network Prefix Translation (NPT)", RFC 8512, DOI 10.17487/RFC8512, January 2019.
[RFC8528] Bjorklund, M. and L. Lhotka, "YANG Schema Mount", RFC 8528, DOI 10.17487/RFC8528, March 2019.
[RFC8529] Berger, L., Hopps, C., Lindem, A., Bogdanovic, D. and X. Liu, "YANG Data Model for Network Instances", RFC 8529, DOI 10.17487/RFC8529, March 2019.
[RFC8530] Berger, L., Hopps, C., Lindem, A., Bogdanovic, D. and X. Liu, "YANG Model for Logical Network Elements", RFC 8530, DOI 10.17487/RFC8530, March 2019.

Authors' Addresses

Qin Wu Huawei 101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China EMail:
Mohamed Boucadair Orange Rennes 35000 France EMail:
Young Lee Huawei EMail: