draft-ietf-opsawg-model-automation-framework-03.txt   draft-ietf-opsawg-model-automation-framework-04.txt 
OPSAWG Q. Wu, Ed. OPSAWG Q. Wu, Ed.
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Informational M. Boucadair, Ed. Intended status: Informational M. Boucadair, Ed.
Expires: November 29, 2020 Orange Expires: December 16, 2020 Orange
D. Lopez D. Lopez
Telefonica I+D Telefonica I+D
C. Xie C. Xie
China Telecom China Telecom
L. Geng L. Geng
China Mobile China Mobile
May 28, 2020 June 14, 2020
A Framework for Automating Service and Network Management with YANG A Framework for Automating Service and Network Management with YANG
draft-ietf-opsawg-model-automation-framework-03 draft-ietf-opsawg-model-automation-framework-04
Abstract Abstract
Data models for service and network management provides a Data models provide a programmatic approach to represent services and
programmatic approach for representing services or networks and networks. Concretely, they can be used to derive configuration
deriving (1) configuration information that will be communicated to information for network and service components, and state information
network and service components that are used to build and deliver the that will be monitored and tracked. Data models can be used during
service and (2) state information that will be monitored and tracked. the service and network management life cycle, such as service
Indeed, data models can be used during various phases of the service instantiation, provisioning, optimization, monitoring, diagnostic,
and network management life cycle, such as service instantiation, and assurance. Data models are also instrumental in the automation
provisioning, optimization, monitoring, diagnostic, and assurance. of network management, and they can provide closed-loop control for
Also, data models 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 adaptive and deterministic service creation, delivery, and
maintenance. maintenance.
This document describes an architecture for service and network This document describes an architecture for service and network
management automation that takes advantage of YANG modeling management automation that takes advantage of YANG modeling
technologies. This architecture is drawn from a network provider technologies. This architecture is drawn from a Network Operator
perspective irrespective of the origin of a data module; it can thus perspective irrespective of the origin of a data module; it can thus
accommodate modules that are developed outside the IETF. accommodate modules that are developed outside the IETF.
The document aims in particular to exemplify an approach that
specifies the journey from technology-agnostic services to
technology-specific actions.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 29, 2020. This Internet-Draft will expire on December 16, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology and Acronyms . . . . . . . . . . . . . . . . . . 5
3. Architectural Concepts and Goals . . . . . . . . . . . . . . 5 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Data Models: Layering and Representation . . . . . . . . 5 2.2. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Automation of Service Delivery Procedures . . . . . . . . 8 3. Architectural Concepts and Goals . . . . . . . . . . . . . . 6
3.3. Service Fullfillment Automation . . . . . . . . . . . . . 9 3.1. Data Models: Layering and Representation . . . . . . . . 6
3.4. YANG Modules Integration . . . . . . . . . . . . . . . . 9 3.2. Automation of Service Delivery Procedures . . . . . . . . 9
4. Functional Bocks and Interactions . . . . . . . . . . . . . . 10 3.3. Service Fullfillment Automation . . . . . . . . . . . . . 10
4.1. Service Lifecycle Management Procedure . . . . . . . . . 11 3.4. YANG Modules Integration . . . . . . . . . . . . . . . . 10
4.1.1. Service Exposure . . . . . . . . . . . . . . . . . . 12 4. Functional Bocks and Interactions . . . . . . . . . . . . . . 11
4.1.2. Service Creation/Modification . . . . . . . . . . . . 12 4.1. Service Lifecycle Management Procedure . . . . . . . . . 12
4.1.3. Service Optimization . . . . . . . . . . . . . . . . 12 4.1.1. Service Exposure . . . . . . . . . . . . . . . . . . 13
4.1.4. Service Diagnosis . . . . . . . . . . . . . . . . . . 13 4.1.2. Service Creation/Modification . . . . . . . . . . . . 13
4.1.5. Service Decommission . . . . . . . . . . . . . . . . 13 4.1.3. Service Optimization . . . . . . . . . . . . . . . . 13
4.2. Service Fullfillment Management Procedure . . . . . . . . 13 4.1.4. Service Diagnosis . . . . . . . . . . . . . . . . . . 14
4.2.1. Intended Configuration Provision . . . . . . . . . . 14 4.1.5. Service Decommission . . . . . . . . . . . . . . . . 14
4.2.2. Configuration Validation . . . . . . . . . . . . . . 14 4.2. Service Fullfillment Management Procedure . . . . . . . . 14
4.2.3. Performance Monitoring/Model-driven Telemetry . . . . 15 4.2.1. Intended Configuration Provision . . . . . . . . . . 15
4.2.4. Fault Diagnostic . . . . . . . . . . . . . . . . . . 15 4.2.2. Configuration Validation . . . . . . . . . . . . . . 15
4.3. Multi-layer/Multi-domain Service Mapping . . . . . . . . 15 4.2.3. Performance Monitoring/Model-driven Telemetry . . . . 16
4.4. Service Decomposing . . . . . . . . . . . . . . . . . . . 16 4.2.4. Fault Diagnostic . . . . . . . . . . . . . . . . . . 16
4.3. Multi-Layer/Multi-Domain Service Mapping . . . . . . . . 16
5. YANG Data Model Integration Examples . . . . . . . . . . . . 16 4.4. Service Decomposing . . . . . . . . . . . . . . . . . . . 17
5.1. L3VPN Service Delivery . . . . . . . . . . . . . . . . . 16 5. YANG Data Model Integration Examples . . . . . . . . . . . . 17
5.2. VN Lifecycle Management . . . . . . . . . . . . . . . . . 18 5.1. L2VPN/L3VPN Service Delivery . . . . . . . . . . . . . . 17
5.3. Event-based Telemetry in the Device Self Management . . . 19 5.2. VN Lifecycle Management . . . . . . . . . . . . . . . . . 19
6. Security Considerations . . . . . . . . . . . . . . . . . . . 20 5.3. Event-based Telemetry in the Device Self Management . . . 20
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 21 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22
10.1. Normative References . . . . . . . . . . . . . . . . . . 22 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.2. Informative References . . . . . . . . . . . . . . . . . 23 10.1. Normative References . . . . . . . . . . . . . . . . . . 23
Appendix A. Layered YANG Modules Examples Overview . . . . . . . 30 10.2. Informative References . . . . . . . . . . . . . . . . . 24
A.1. Service Models: Definition and Samples . . . . . . . . . 30 Appendix A. Layered YANG Modules Examples Overview . . . . . . . 32
A.2. Network Models: Samples . . . . . . . . . . . . . . . . . 30 A.1. Service Models: Definition and Samples . . . . . . . . . 32
A.3. Device Models: Samples . . . . . . . . . . . . . . . . . 33 A.2. Network Models: Samples . . . . . . . . . . . . . . . . . 32
A.3.1. Model Composition . . . . . . . . . . . . . . . . . . 34 A.3. Device Models: Samples . . . . . . . . . . . . . . . . . 35
A.3.2. Device Models: Samples . . . . . . . . . . . . . . . 35 A.3.1. Model Composition . . . . . . . . . . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38 A.3.2. Device Models: Samples . . . . . . . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40
1. Introduction 1. Introduction
Service management systems usually comprise service activation/ Service management systems usually comprise service activation/
provision and service operation. Current service delivery provision and service operation. Current service delivery
procedures, from the processing of customer's requirements and order procedures, from the processing of customer's requirements and orders
to service delivery and operation, typically assume the manipulation to service delivery and operation, typically assume the manipulation
of data sequentially into multiple OSS/BSS applications that may be of data sequentially into multiple OSS/BSS applications that may be
managed by different departments within the service provider's managed by different departments within the service provider's
organization (e.g., billing factory, design factory, network organization (e.g., billing factory, design factory, network
operation center, etc.). In addition, many of these applications operation center). In addition, many of these applications have been
have been developed in-house over the years and operating in a silo developed in-house over the years and operate in a silo mode:
mode:
o The lack of standard data input/output (i.e., data model) raises o The lack of standard data input/output (i.e., data model) raises
many challenges in system integration and often results in manual many challenges in system integration and often results in manual
configuration tasks. configuration tasks.
o Service fulfillment systems might have a limited visibility on the o Service fulfillment systems might have a limited visibility on the
network state and therefore have slow response to network changes. network state and therefore have slow response to network changes.
Software Defined Networking (SDN) becomes crucial to address these Software Defined Networking (SDN) becomes crucial to address these
challenges. SDN techniques [RFC7149] are meant to automate the challenges. SDN techniques are meant to automate the overall service
overall service delivery procedures and typically rely upon delivery procedures and typically rely upon standard data models.
(standard) data models that are used to not only reflect service These models are used to not only reflect service providers' savoir-
providers'savoir-faire but also to dynamically instantiate and faire, but also to dynamically instantiate and enforce a set of
enforce a set of (service-inferred) policies that best accommodate service-inferred policies that best accommodate what has been defined
what has been (contractually) defined (and possibly negotiated) with and possibly negotiated with the customer. [RFC7149] provides a
the customer. [RFC7149] provides a first tentative to rationalize first tentative attempt to rationalize that service provider's view
that service provider's view on the SDN space by identifying concrete on the SDN space by identifying concrete technical domains that need
technical domains that need to be considered and for which solutions to be considered and for which solutions can be provided:
can be provided:
o Techniques for the dynamic discovery of topology, devices, and o Techniques for the dynamic discovery of topology, devices, and
capabilities, along with relevant information and data models that capabilities, along with relevant information and data models that
are meant to precisely document such topology, devices, and their are meant to precisely document such topology, devices, and their
capabilities. capabilities.
o Techniques for exposing network services [RFC8309] and their o Techniques for exposing network services [RFC8309] and their
characteristics. characteristics.
o Techniques used by service-derived dynamic resource allocation and o Techniques used by service-derived dynamic resource allocation and
skipping to change at page 4, line 30 skipping to change at page 4, line 25
efficiently a given policy (or a set thereof) is enforced from a efficiently a given policy (or a set thereof) is enforced from a
service fulfillment and assurance perspectives. service fulfillment and assurance perspectives.
Models are key for each of the aforementioned four technical items. Models are key for each of the aforementioned four technical items.
Service and network management automation is an important step to Service and network management automation is an important step to
improve the agility of network operations. Models are also important improve the agility of network operations. Models are also important
to ease integrating multi-vendor solutions. to ease integrating multi-vendor solutions.
YANG [RFC7950] module developers have taken both top-down and bottom- YANG [RFC7950] module developers have taken both top-down and bottom-
up approaches to develop modules [RFC8199] and to establish a mapping up approaches to develop modules [RFC8199] and to establish a mapping
between a network technology and customer requirements on the top or between a network technology and customer requirements at the top or
abstracting common construct from various network technologies on the abstracting common constructs from various network technologies at
bottom. At the time of writing this document (2020), there are many the bottom. At the time of writing this document (2020), there are
data models including configuration and service models that have been many data models including configuration and service models that have
specified or are being specified by the IETF. They cover many of the been specified or are being specified by the IETF. They cover many
networking protocols and techniques. However, how these models work of the networking protocols and techniques. However, how these
together to configure a device, manage a set of devices involved in a models work together to configure a device, manage a set of devices
service, or provide a service is something that is not currently involved in a service, or provide a service is something that is not
documented either within the IETF or other Standards Developing currently documented either within the IETF or other Standards
Organizations (SDOs) (e.g., MEF). Development Organizations (SDOs).
This document describes an architectural framework for service and This document describes an architectural framework for service and
network management automation (Section 3) that takes advantage of network management automation (Section 3) that takes advantage of
YANG modeling technologies and investigates how different layer YANG YANG modeling technologies and investigates how different layer YANG
data models interact with each other (e.g., service mapping, model data models interact with each other (e.g., service mapping, model
composing) in the context of service delivery and fulfillment composing) in the context of service delivery and fulfillment
(Section 4). (Section 4).
This framework is drawn from a network provider perspective This framework is drawn from a Network Operator perspective
irrespective of the origin of a data module; it can accommodate irrespective of the origin of a data module; it can accommodate
modules that are developed outside the IETF. modules that are developed outside the IETF.
The document identifies a list of use cases to exemplify the proposed The document identifies a list of use cases to exemplify the proposed
approach (Section 5), but it does not claim nor aim to be exhaustive. approach (Section 5), but it does not claim nor aim to be exhaustive.
2. Terminology 2. Terminology and Acronyms
2.1. Terminology
The following terms are defined in [RFC8309][RFC8199] and are not The following terms are defined in [RFC8309][RFC8199] and are not
redefined here: redefined here:
o Network Operator o Network Operator
o Customer o Customer
o Service o Service
skipping to change at page 5, line 30 skipping to change at page 5, line 29
o Service Model o Service Model
o Network Element Module o Network Element Module
In addition, the document makes use of the following terms: In addition, the document makes use of the following terms:
Network Model: Describes a network level abstraction (or a subset of Network Model: Describes a network level abstraction (or a subset of
aspects of a network infrastructure), including devices and their aspects of a network infrastructure), including devices and their
subsystems, and relevant protocols operating at the link and subsystems, and relevant protocols operating at the link and
network layers across multiple devices. It can be used by a network layers across multiple devices. This model corresponds to
network operator to allocate resources (e.g., tunnel resource, the Network Configuration Model discussed in [RFC8309].
topology resource) for the service or schedule resources to meet
the service requirements defined in a Service Model.
Device Model: Refers to the Network Element YANG data module It can be used by a Network Operator to allocate resources (e.g.,
described in [RFC8199]. Device Models are also used to refer to tunnel resource, topology resource) for the service or schedule
model a function embedded in a device (e.g., Network Address resources to meet the service requirements defined in a Service
Translation (NAT) [RFC8512], Access Control Lists (ACLs) Model.
[RFC8519]).
Device Model: Refers to the Network Element YANG data model
described in [RFC8199] or the Device Configuration Model discussed
in [RFC8309].
Device Models are also used to refer to model a function embedded
in a device (e.g., Network Address Translation (NAT) [RFC8512],
Access Control Lists (ACLs) [RFC8519]).
2.2. Acronyms
The following acronyms are used in the document:
ACL Access Control List
CE Customer Edge
ECA Event Condition Action
L2VPN Layer 2 Virtual Private Network
L3VPN Layer 3 Virtual Private Network
NAT Network Address Translation
OAM Operations, Administration, and Maintenance
OWD One-Way Delay
PE Provider Edge
QoS Quality of Service
RD Route Distinguisher
RT Route Target
SDN Software Defined Networking
TE Traffic Engineering
VN Virtual Network
VPN Virtual Private Network
VRF Virtual Routing and Forwarding
3. Architectural Concepts and Goals 3. Architectural Concepts and Goals
3.1. Data Models: Layering and Representation 3.1. Data Models: Layering and Representation
As described in Section 2 of [RFC8199], layering of modules allows As described in Section 2 of [RFC8199], layering of modules allows
for better reusability of lower-layer modules by higher-level modules for better reusability of lower-layer modules by higher-level modules
while limiting duplication of features across layers. while limiting duplication of features across layers.
Data models can be classified into Service, Network, and Device Data models can be classified into Service, Network, and Device
Models. Different Service Models may rely on the same set of Network Models. Different Service Models may rely on the same set of Network
and/or Device Models. and/or Device Models.
Service Models traditionally follow top-down approach and are mostly Service Models traditionally follow top-down approach and are mostly
customer-facing YANG modules providing a common model construct for customer-facing YANG modules providing a common model construct for
higher level network services (e.g., Layer 3 Virtual Private Network higher level network services (e.g., Layer 3 Virtual Private Network
(L3VPN)), which can be mapped to network technology-specific modules (L3VPN)). Such modules can be mapped to network technology-specific
at lower layers (e.g., tunnel, routing, Quality of Service (QoS), modules at lower layers (e.g., tunnel, routing, Quality of Service
security). For example, the service level can be used to (QoS), security). For example, the service level can be used to
characterise the network service(s) to be ensured between service characterise the network service(s) to be ensured between service
nodes (ingress/egress) such as the communication scope (pipe, hose, nodes (ingress/egress) such as:
funnel, ...), the directionality (inbound/outbound), the traffic
performance guarantees (one-way delay (OWD), one-way loss, ...), etc.
Figure 1 depicts the example of a VoIP service provider that relies o the communication scope (pipe, hose, funnel, ...),
upon connectivity services offered by a Network Operator. These o the directionality (inbound/outbound),
connectivity services can be captured in a YANG Service Module that o the traffic performance guarantees (One-Way Delay (OWD) [RFC7679],
reflects the service attributes that are shown in Figure 2. This One-Way Loss [RFC7680], ...),
example follows the IP Connectivity Provisioning Profile template o link capacity [RFC5136][I-D.ietf-ippm-capacity-metric-method],
defined in [RFC7297]. o etc.
Figure 1 depicts the example of a VoIP service that relies upon
connectivity services offered by a Network Operator. In this
example, the VoIP service is offered to the Network Operator's
customers by Service Provider (SP1). In order to provide global VoIP
reachability, SP1 service site interconnects with other Service
Providers service sites typically by interconnecting Session Border
Elements (SBEs) and Data Border Elements (DBEs) [RFC5486][RFC6406].
For other VoIP destinations, sessions are forwarded over the
Internet. These connectivity services can be captured in a YANG
Service Module that reflects the service attributes that are shown in
Figure 2. This example follows the IP Connectivity Provisioning
Profile template defined in [RFC7297].
,--,--,--. ,--,--,--. ,--,--,--. ,--,--,--.
,-' SP1 `-. ,-' SP2 `-. ,-' SP1 `-. ,-' SP2 `-.
( Service Site ) ( Service Site ) ( Service Site ) ( Service Site )
`-. ,-' `-. ,-' `-. ,-' `-. ,-'
`--'--'--' `--'--'--' `--'--'--' `--'--'--'
x | o * * | x | o * * |
(2)x | o * * | (2)x | o * * |
,x-,--o-*-. (1) ,--,*-,--. ,x-,--o-*-. (1) ,--,*-,--.
,-' x o * * * * * * * * * `-. ,-' x o * * * * * * * * * `-.
( x o +----( Internet ) ( x o +----( Internet )
User---(x x x o o o o o o o o o o o o o o o o o o User---(x x x o o o o o o o o o o o o o o o o o o
`-. Provider ,-' `-. ,-' (3) `-. ,-' `-. ,-' (3)
`--'--'--' `--'--'--' `--'--'--' `--'--'--'
Network Operator
**** (1) Inter-SP connectivity **** (1) Inter-SP connectivity
xxxx (2) Customer to SP connectivity xxxx (2) Customer to SP connectivity
oooo (3) SP to any destination connectivity oooo (3) SP to any destination connectivity
Figure 1: An Example of Service Connectivty Components Figure 1: An Example of Service Connectivty Components
Connectivity: Scope and Guarantees Connectivity: Scope and Guarantees
* Inter-SP connectivity (1) (1) Inter-SP connectivity
- Pipe scope from the local to the remote VoIP gateway - Pipe scope from the local to the remote SBE/DBE
- Full guarantees class - Full guarantees class
* Customer to SP connectivity (2) (2) Customer to SP connectivity
- Hose/Funnel scope connecting the local VoIP gateway - Hose/Funnel scope connecting the local SBE/DBE
to the customer access points to the customer access points
- Full guarantees class - Full guarantees class
* SP to any destination connectivity (3) (3) SP to any destination connectivity
- Hose/Funnel scope from the local VoIP gateway to the - Hose/Funnel scope from the local SBE/DBE to the
Internet gateway Internet gateway
- Delay guarantees class - Delay guarantees class
Flow Identification Flow Identification
* Destination IP address * Destination IP address (SBE, DBE)
(Session Border Element (SBE), Data Border Element (DBE))
[RFC5486]
* DSCP marking * DSCP marking
Traffic Isolation Traffic Isolation
* VPN * VPN
Routing & Forwarding Routing & Forwarding
* Routing rule to exclude some ASes from the inter-domain * Routing rule to exclude some ASes from the inter-domain
paths paths
Notifications (including feedback) Notifications (including feedback)
* Statistics on aggregate traffic to adjust capacity * Statistics on aggregate traffic to adjust capacity
* Failures * Failures
* Planned maintenance operations * Planned maintenance operations
skipping to change at page 8, line 13 skipping to change at page 9, line 13
"Controller" elements. "Controller" elements.
+-----------------------------------------------------------------+ +-----------------------------------------------------------------+
| +-----------------------+ | | +-----------------------+ |
| | Orchestrator | Hierarchy Abstraction | | | Orchestrator | Hierarchy Abstraction |
| |+---------------------+| | | |+---------------------+| |
| || Service Modeling || Service Model | | || Service Modeling || Service Model |
| |+---------------------+| (Customer Oriented) | | |+---------------------+| (Customer Oriented) |
| | | Scope: "1:1" Pipe model | | | | Scope: "1:1" Pipe model |
| | | Bidirectional | | | | Bidirectional |
| |+---------------------+| +-+ BW:100M,OWD +-+ | | |+---------------------+| +-+ Capacity,OWD +-+ |
| ||Service Orchestration|| | +---------------+ | | | ||Service Orchestration|| | +----------------+ | |
| |+---------------------+| +-+ +-+ | | |+---------------------+| +-+ +-+ |
| +-----------------------+ 1. Ingress 2. Egress | | +-----------------------+ 1. Ingress 2. Egress |
| | | |
| | | |
| | | |
| +-----------------------+ Network Model | | +-----------------------+ Network Model |
| | Controller | (Operator Oriented) | | | Controller | (Operator Oriented) |
| |+---------------------+| +-+ +--+ +---+ +-+ | | |+---------------------+| +-+ +--+ +---+ +-+ |
| || Network Modeling || | | | | | | | | | | || Network Modeling || | | | | | | | | |
| |+---------------------+| | o----o--o----o---o---o | | | |+---------------------+| | o----o--o----o---o---o | |
| |+---------------------+| +-+ +--+ +---+ +-+ | | |+---------------------+| +-+ +--+ +---+ +-+ |
| ||network Orchestration| src dst | | ||Network Orchestration|| src dst |
| |+---------------------+| L3VPN over TE | | |+---------------------+| L3VPN over TE |
| | | Instance Name/Access Interface | | | | Instance Name/Access Interface |
| +-----------------------+ Proto Type/BW/RD,RT/etc. mapping| | +-----------------------+ Protocol Type/Capacity/RD/RT/... |
| for hop | | mapping for hop |
| | | |
| | | |
| +-----------------------+ | | +-----------------------+ |
| | Device | Device Model | | | Device | Device Model |
| |+--------------------+ | | | |+--------------------+ | |
| || Device Modeling | | Interface add, BGP Peer, | | || Device Modeling | | Interface add, BGP Peer, |
| |+--------------------+ | Tunnel id, QoS/TE | | |+--------------------+ | Tunnel ID, QoS/TE, ... |
| +-----------------------+ | | +-----------------------+ |
+-----------------------------------------------------------------+ +-----------------------------------------------------------------+
Figure 3: Layering and Representation Figure 3: Layering and Representation
3.2. Automation of Service Delivery Procedures 3.2. Automation of Service Delivery Procedures
Service Models can be used by an operator to expose its services to Service Models can be used by a Network Operator to expose its
its customers. Exposing such models allows to automate the services to its customers. Exposing such models allows to automate
activation of service orders and thus the service delivery. One or the activation of service orders and thus the service delivery. One
more monolithic Service Models can be used in the context of a or more monolithic Service Models can be used in the context of a
composite service activation request (e.g., delivery of a caching composite service activation request (e.g., delivery of a caching
infrastructure over a VPN). Such models are used to feed a decision- infrastructure over a VPN). Such models are used to feed a decision-
making intelligence to adequately accommodate customer's needs. making intelligence to adequately accommodate customer's needs.
Also, such models may be used jointly with services that require Also, such models may be used jointly with services that require
dynamic invocation. An example is provided by the service modules dynamic invocation. An example is provided by the service modules
defined by the DOTS WG to dynamically trigger requests to handle defined by the DOTS WG to dynamically trigger requests to handle
Distributed Denial-of-Service (DDoS) attacks Distributed Denial-of-Service (DDoS) attacks [RFC8783].
[I-D.ietf-dots-data-channel].
Network Models can be derived from Service Models and used to Network Models can be derived from Service Models and used to
provision, monitor, instantiate the service, and provide lifecycle provision, monitor, instantiate the service, and provide lifecycle
management of network resources. Doing so is meant to: management of network resources. Doing so is meant to:
o expose network resources to customers (including other operators) o expose network resources to customers (including other Network
to provide service fulfillment and assurance Operators) to provide service fulfillment and assurance
o allow customers (or operators) to dynamically adjust the network o allow customers (or Network Operators) to dynamically adjust the
resources based on service requirements as described in Service network resources based on service requirements as described in
Models (e.g., Figure 2) and the current network performance Service Models (e.g., Figure 2) and the current network
information described in the telemetry modules. performance information described in the telemetry modules.
3.3. Service Fullfillment Automation 3.3. Service Fullfillment Automation
To operate a service, Device Models derived from Service Models and/ To operate a service, the settings of the parameters in the Device
or Network Models can be used to provision each involved network Models are derived from Service Models and/or Network Models and are
function/device with the proper configuration information, and used to:
operate the network based on service requirements as described in the
Service Model(s) and local operational guidelines. o Provision each involved network function/device with the proper
configuration information.
o Operate the network based on service requirements as described in
the Service Model(s) and local operational guidelines.
In addition, the operational state including configuration that is in In addition, the operational state including configuration that is in
effect together with statistics should be exposed to upper layers to effect together with statistics should be exposed to upper layers to
provide better network visibility (and assess to what extent the provide better network visibility and assess to what extent the
derived low level modules are consistent with the upper level derived low level modules are consistent with the upper level inputs.
inputs).
Filters are enforced on the notifications that are communicated to Filters are enforced on the notifications that are communicated to
Service layers. The type (and frequency) of notifications may be Service layers. The type and frequency of notifications may be
agreed in the Service Model. agreed in the Service Model.
Note that it is important to correlate telemetry data with Note that it is important to correlate telemetry data with
configuration data to be used for closed loops at the different configuration data to be used for closed loops at the different
stages of service delivery, from resource allocation to service stages of service delivery, from resource allocation to service
operation, in particular. operation, in particular.
3.4. YANG Modules Integration 3.4. YANG Modules Integration
To support top-down service delivery, YANG modules at different To support top-down service delivery, YANG modules at different
levels or at the same level need to be integrated together for proper levels or at the same level need to be integrated together for proper
service delivery (including, proper network setup). For example, the service delivery (including, proper network setup). For example, the
service parameters captured in Service Models need to be decomposed service parameters captured in Service Models need to be decomposed
into a set of (configuration/notification) parameters that may be into a set of configuration/notification parameters that may be
specific to one or more technologies; these technology-specific specific to one or more technologies; these technology-specific
parameters are grouped together to define technology-specific device parameters are grouped together to define technology-specific device
level models or network level models. level models or network level models.
In addition, these technology-specific Device or Network Models can In addition, these technology-specific Device or Network Models can
be further integrated with each other using the schema mount be further integrated with each other using the schema mount
mechanism [RFC8528] to provision each involved network function/ mechanism [RFC8528] to provision each involved network function/
device or each involved administrative domain to support newly added device or each involved administrative domain to support newly added
module or features. A collection of Device Models integrated module or features. A collection of Device Models integrated
together can be loaded and validated during the implementation time. together can be loaded and validated during the implementation time.
skipping to change at page 10, line 29 skipping to change at page 11, line 31
telemetry automation, e.g., policies that contain conditions can telemetry automation, e.g., policies that contain conditions can
trigger the generation and pushing of new telemetry data. trigger the generation and pushing of new telemetry data.
Performance measurement telemetry can be used to provide service Performance measurement telemetry can be used to provide service
assurance at Service and/or Network levels. Performance measurement assurance at Service and/or Network levels. Performance measurement
telemetry model can tie with Service or Network Models to monitor telemetry model can tie with Service or Network Models to monitor
network performance or Service Level Agreement. network performance or Service Level Agreement.
4. Functional Bocks and Interactions 4. Functional Bocks and Interactions
The architectural considerations described in Section 3 led to the The architectural considerations described in Section 3 lead to the
architecture described in this section and illustrated in Figure 4. architecture described in this section and illustrated in Figure 4.
+------------------+ +------------------+
Service level | | ................. | |
----------- V | Service level | |
E2E E2E E2E E2E V |
Service -- Service --------> Service --->Service ---+ E2E E2E E2E E2E
Exposure Creation ^ Optimization | Diagnosis | Service --> Service ---------> Service -----> Service -----+
/Modification | | | Exposure Creation ^ Optimization ^ Diagnosis |
| |Diff | V /Modification | | |
Multi-layer | | E2E | E2E | |Diff | V
Multi-domain | | Service | Service Multi-layer | | E2E | E2E
Service Mapping| +------ Assurance ---+ Decommission Multi-domain | | Service | Service
| ^ Service Mapping| +------ Assurance --+ Decommission
|<-----------------+ | | ^
Network level | | +----+ ................. |<-----------------+ |
------------ V | | Network level | | +-------+
Specific Specific | V | |
Service ----+---> Service ---+--+ Specific Specific |
Creation ^ Optimization | | Service --------> Service <--+ |
/Modification | | | Creation ^ Optimization | |
| |Diff | | /Modification | | |
| | Specific----+ | | |Diff | |
Service | | Service | | | Specific --+ |
Decomposing | +------Assurance ----+ Service | | Service |
| ^ Decomposing | +----- Assurance ----+
| | Aggregation | ^
Device level | +------------+ ................. | | Aggregation
------------ V | Device level | +------------+
Service Intent V |
Fullfillment Config ------> Config ----> Performance -->Fault Service Intent |
Provision Validate Monitoring Diagnostic Fulfillment Config ----> Config ----> Performance ----> Fault
Provision Validate Monitoring Diagnostic
Figure 4: Service and Network Lifecycle Management Figure 4: Service and Network Lifecycle Management
4.1. Service Lifecycle Management Procedure 4.1. Service Lifecycle Management Procedure
Service lifecycle management includes end-to-end service lifecycle Service lifecycle management includes end-to-end service lifecycle
management at the service level and technology specific network management at the service level and technology specific network
lifecycle management at the network level. lifecycle management at the network level.
The end-to-end service lifecycle management is technology-independent The end-to-end service lifecycle management is technology-independent
skipping to change at page 12, line 23 skipping to change at page 13, line 23
(ordering and order handling). One typical example is that a (ordering and order handling). One typical example is that a
customer can use a L3VPN Service Model (L3SM) to request L3VPN customer can use a L3VPN Service Model (L3SM) to request L3VPN
service by providing the abstract technical characterization of the service by providing the abstract technical characterization of the
intended service between customer sites. intended service between customer sites.
Service Model catalogs can be created along to expose the various Service Model catalogs can be created along to expose the various
services and the information needed to invoke/order a given service. services and the information needed to invoke/order a given service.
4.1.2. Service Creation/Modification 4.1.2. Service Creation/Modification
A customer is (usually) unaware of the technology that the network A customer is usually unaware of the technology that the Network
operator has available to deliver the service, so the customer does Operator has available to deliver the service, so the customer does
not make requests specific to the underlying technology but is not make requests specific to the underlying technology but is
limited to making requests specific to the service that is to be limited to making requests specific to the service that is to be
delivered. This service request can be issued using the Service delivered. This service request can be issued using a Service Model.
Model.
Upon receiving a service request, the service orchestrator/management Upon receiving a service request, and assuming that appropriate
system should first verify whether the service requirements in the authentication and authorization checks have been made, the service
service request can be met (i.e., whether there is sufficient orchestrator/management system should verify whether the service
resources that can be allocated with the requested guarantees). requirements in the service request can be met (i.e., whether there
is sufficient resources that can be allocated with the requested
guarantees).
If the request is accepted, the service orchestrator/management If the request is accepted, the service orchestrator/management
system maps such service request to its view. This view can be system maps such service request to its view. This view can be
described as a technology specific network model or a set of described as a technology specific network model or a set of
technology specific Device Models and this mapping may include a technology specific Device Models and this mapping may include a
choice of which networks and technologies to use depending on which choice of which networks and technologies to use depending on which
service features have been requested. service features have been requested.
In addition, a customer may require to change the underlying network In addition, a customer may require to change the underlying network
infrastructure to adapt to new customer's needs and service infrastructure to adapt to new customer's needs and service
requirements. This service modification can be issued following the requirements. This service modification can be issued following the
same Service Model used by the service request. same Service Model used by the service request.
4.1.3. Service Optimization 4.1.3. Service Optimization
Service optimization is a technique that gets the configuration of Service optimization is a technique that gets the configuration of
the network updated due to network changes, incidents mitigation, or the network updated due to network changes, incidents mitigation, or
new service requirements. One typical example is once a tunnel or a new service requirements. One typical example is once a tunnel or a
VPN is setup, Performance monitoring information or telemetry VPN is setup, Performance monitoring information or telemetry
information per tunnel (or per VPN) can be collected and feed into information per tunnel (or per VPN) can be collected and fed into the
the management system. If the network performance doesn't meet the management system. If the network performance doesn't meet the
service requirements, the management system can create new VPN service requirements, the management system can create new VPN
policies capturing network service requirements and populate them policies capturing network service requirements and populate them
into the network. into the network.
Both network performance information and policies can be modelled Both network performance information and policies can be modelled
using YANG. With Policy-based management, self-configuration and using YANG. With Policy-based management, self-configuration and
self-optimization behavior can be specified and implemented. self-optimization behavior can be specified and implemented.
4.1.4. Service Diagnosis 4.1.4. Service Diagnosis
skipping to change at page 14, line 15 skipping to change at page 15, line 15
Intended configuration at the device level is derived from Network Intended configuration at the device level is derived from Network
Models at the network level or Service Model at the service level and Models at the network level or Service Model at the service level and
represents the configuration that the system attempts to apply. Take represents the configuration that the system attempts to apply. Take
L3SM as a Service Model example to deliver a L3VPN service, we need L3SM as a Service Model example to deliver a L3VPN service, we need
to map the L3VPN service view defined in the Service Model into to map the L3VPN service view defined in the Service Model into
detailed intended configuration view defined by specific detailed intended configuration view defined by specific
configuration models for network elements, configuration information configuration models for network elements, configuration information
includes: includes:
o VPN Routing and Forwarding (VRF) definition, including VPN policy o Virtual Routing and Forwarding (VRF) definition, including VPN
expression policy expression
o Physical Interface(s) o Physical Interface(s)
o IP layer (IPv4, IPv6) o IP layer (IPv4, IPv6)
o QoS features such as classification, profiles, etc. o QoS features such as classification, profiles, etc.
o Routing protocols: support of configuration of all protocols o Routing protocols: support of configuration of all protocols
listed in a service request, as well as routing policies listed in a service request, as well as routing policies
associated with those protocols. associated with those protocols.
skipping to change at page 14, line 44 skipping to change at page 15, line 44
These specific configuration models can be used to configure Provider These specific configuration models can be used to configure Provider
Edge (PE) and Customer Edge (CE) devices within a site, e.g., a BGP Edge (PE) and Customer Edge (CE) devices within a site, e.g., a BGP
policy model can be used to establish VPN membership between sites policy model can be used to establish VPN membership between sites
and VPN Service Topology. and VPN Service Topology.
4.2.2. Configuration Validation 4.2.2. Configuration Validation
Configuration validation is used to validate intended configuration Configuration validation is used to validate intended configuration
and ensure the configuration take effect. and ensure the configuration take effect.
For example, a customer creates an interface "et-0/0/0" but the For example, a customer creates an interface "eth-0/0/0" but the
interface does not physically exist at this point, then configuration interface does not physically exist at this point, then configuration
data appears in the <intended> status but does not appear in data appears in the <intended> status but does not appear in
<operational> datastore. <operational> datastore.
4.2.3. Performance Monitoring/Model-driven Telemetry 4.2.3. Performance Monitoring/Model-driven Telemetry
When configuration is in effect in the device, <operational> When configuration is in effect in the device, <operational>
datastore holds the complete operational state of the device datastore holds the complete operational state of the device
including learned, system, default configuration, and system state. including learned, system, default configuration, and system state.
However, the configurations and state of a particular device does not However, the configurations and state of a particular device does not
skipping to change at page 15, line 40 skipping to change at page 16, line 40
technology-specific YANG data models which can use and extend the technology-specific YANG data models which can use and extend the
base model described in Section 4.1.4 to deal with these issues. base model described in Section 4.1.4 to deal with these issues.
These RPC commands received in the technology-dependent node can be These RPC commands received in the technology-dependent node can be
used to trigger technology-specific OAM message exchanges for fault used to trigger technology-specific OAM message exchanges for fault
verification and fault isolation For example, TRILL Multicast Tree verification and fault isolation For example, TRILL Multicast Tree
Verification (MTV) RPC command [I-D.ietf-trill-yang-oam] can be used Verification (MTV) RPC command [I-D.ietf-trill-yang-oam] can be used
to trigger Multi-Destination Tree Verification Message defined in to trigger Multi-Destination Tree Verification Message defined in
[RFC7455] to verify TRILL distribution tree integrity. [RFC7455] to verify TRILL distribution tree integrity.
4.3. Multi-layer/Multi-domain Service Mapping 4.3. Multi-Layer/Multi-Domain Service Mapping
Multi-layer/Multi-domain Service Mapping allows to map an end-to-end Multi-layer/Multi-domain Service Mapping allows to map an end-to-end
abstract view of the service segmented at different layers or abstract view of the service segmented at different layers or
different administrative domains into domain-specific view. different administrative domains into domain-specific view.
One example is to map service parameters in L3VPN service model into One example is to map service parameters in L3VPN service model into
configuration parameters such as Route Distinguisher (RD), Route configuration parameters such as Route Distinguisher (RD), Route
Target (RT), and VRF in L3VPN network model. Target (RT), and VRF in L3VPN network model.
Another example is to map service parameters in L3VPN service model Another example is to map service parameters in L3VPN service model
into Traffic Engineered (TE) tunnel parameter (e.g., Tunnel ID) in TE into Traffic Engineered (TE) tunnel parameter (e.g., Tunnel ID) in TE
model and Virtual Network (VN) parameters (e.g., Access Point (AP) model and Virtual Network (VN) parameters (e.g., Access Point (AP)
list, VN members) in Traffic Engineering Architecture and Signaling list, VN members) in the YANG data model for VN operation
(TEAS) VN model [I-D.ietf-teas-actn-vn-yang]. [I-D.ietf-teas-actn-vn-yang].
4.4. Service Decomposing 4.4. Service Decomposing
Service Decomposing allows to decompose service model at the service Service Decomposing allows to decompose service model at the service
level or network model at the network level into a set of device/ level or network model at the network level into a set of device/
function models at the device level. These Device Models may be tied function models at the device level. These Device Models may be tied
to specific device types or classified into a collection of related to specific device types or classified into a collection of related
YANG modules based on service types and features offered, and load at YANG modules based on service types and features offered, and load at
the implementation time before configuration is loaded and validated. the implementation time before configuration is loaded and validated.
5. YANG Data Model Integration Examples 5. YANG Data Model Integration Examples
The following subsections provides some data models integration The following subsections provides some data models integration
examples. examples.
5.1. L3VPN Service Delivery 5.1. L2VPN/L3VPN Service Delivery
In reference to Figure 5, the following steps are performed to In reference to Figure 5, the following steps are performed to
deliver the L3VPN service within the network management automation deliver the L3VPN service within the network management automation
architecture defined in this document: architecture defined in this document:
1. The Customer requests to create two sites (as per service 1. The Customer requests to create two sites (as per service
creation operation in Section 4.2.1) relying upon a L3SM Service creation operation in Section 4.2.1) relying upon a L3SM Service
model with each having one network access connectivity: model with each having one network access connectivity, for
example:
* Site A: Network-Access A, Bandwidth=20M, for class "foo", * Site A: Network-Access A, Link Capacity = 20 Mbps, for class
guaranteed-bw-percent = 10, One-Way-Delay=70 msec "foo", guaranteed-capacity-percent = 10, average-One-Way-Delay
= 70 ms.
* Site B: Network-Access B, Bandwidth=30M, for class "foo1", * Site B: Network-Access B, Link Capacity = 30 Mbps, for class
guaranteed-bw-percent = 15, One-Way-Delay=60 msec "foo1", guaranteed-capacity-percent = 15, average-One-Way-
Delay = 60 ms.
2. The Orchestrator extracts the service parameters from the L3SM 2. The Orchestrator extracts the service parameters from the L3SM
model. Then, it uses them as input to translate ("service model. Then, it uses them as input to translate ("service
mapping operation" in Section 4.4) them into an orchestrated mapping operation" in Section 4.4) them into an orchestrated
configuration of network elements (e.g., RD, RT, VRF) that are configuration of network elements (e.g., RD, RT, VRF) that are
part of the L3NM network model. part of the L3VPN Network YANG Model specified in
[I-D.ietf-opsawg-l3sm-l3nm].
3. The Controller takes orchestrated configuration parameters in the 3. The Controller takes orchestrated configuration parameters in the
L3NM network model and translates them into orchestrated L3NM network model and translates them into orchestrated
("service decomposing operation" in ) configuration of network ("service decomposing operation" in ) configuration of network
elements that are part of, e.g., BGP, QoS, Network Instance elements that are part of, e.g., BGP, QoS, Network Instance
model, IP management, and interface models. model, IP management, and interface models.
[I-D.ogondio-opsawg-uni-topology] can be used for representing, [I-D.ogondio-opsawg-uni-topology] can be used for representing,
managing, and controlling the User Network Interface (UNI) topology. managing, and controlling the User Network Interface (UNI) topology.
L3SM | L3SM |
Service | Service |
Model | Model |
+--------------------+----------------------------+ +----------------------+--------------------------+
| +-----V- -------+ | | +--------V--------+ |
| Orchestrator |Service Mapping| | | | Service Mapping | |
| +-----+---------+ | | +--------+--------+ |
| | | | Orchestrator | |
+--------------------+----------------------------+ +----------------------+--------------------------+
L3NM | L3NM | ^ UNI Topology Model
Network| Network| |
Model | Model | |
+--------------------+----------------------------+ +----------------------+--------------------------+
| Controller+--------V-----------+ | | +----------V-----------+ |
| | Service Decomposing| | | | Service Decomposing | |
| +-++------------++---+ | | +---++--------------++-+ |
| || || | | || || |
| || || | | Controller || || |
+-------------++---------- ++--------------------+ +---------------++--------------++----------------+
|| || || ||
|| || || BGP, ||
||BGP,QoS || || QoS, ||
|| || || Interface, ||
+----------+|NI,Intf,IP |+-----------------+ +------------+| NI, |+--------------+
+--+--+ +++---+ --+---+ +--+--+ | | IP | |
| CE1 |------| PE1 | | PE2 | ---------+ CE2 | +--+--+ +--+--+ +--+--+ +--+--+
+-----+ +-----+ +-----+ +-----+ | CE1 +-------+ PE1 | | PE2 +---------+ CE2 |
+-----+ +-----+ +-----+ +-----+
Legend:
Intf: Interface
Figure 5: L3VPN Service Delivery Example (Current) Figure 5: L3VPN Service Delivery Example (Current)
L3NM inherits some of data elements from the L3SM. Nevertheless, the L3NM inherits some of data elements from the L3SM. Nevertheless, the
L3NM does not expose some information to the above layer such as the L3NM does not expose some information to the above layer such as the
capabilities of an underlying network (which can be used to drive capabilities of an underlying network (which can be used to drive
service order handling) or notifications (to notify subscribers about service order handling) or notifications (to notify subscribers about
specific events or degradations as per agreed SLAs). Some of this specific events or degradations as per agreed SLAs). Some of this
information can be provided using, e.g., information can be provided using, e.g.,
[I-D.www-bess-yang-vpn-service-pm]. A target overall model is [I-D.www-bess-yang-vpn-service-pm]. A target overall model is
depicted in Figure 6. depicted in Figure 6.
L3SM | ^ L3SM | ^
Service | | Notifications Service | | Notifications
Model | | Model | |
+--------------------+----------------------------+ +----------------------+--------------------------+
| +-----V---------+ | | +--------V--------+ |
| Orchestrator |Service Mapping| | | | Service Mapping | |
| +-----+---------+ | | +--------+--------+ |
| | | | Orchestrator | |
+--------------------+----------------------------+ +----------------------+--------------------------+
L3NM | ^ L3NM | ^ UNI Topology Model
Network| | L3NM Notifications Network| | L3NM Notifications
Model | | L3NM Capabilities Model | | L3NM Capabilities
+--------------------+----------------------------+ +----------------------+--------------------------+
| Controller+--------V-----------+ | | +----------V-----------+ |
| | Service Decomposing| | | | Service Decomposing | |
| +-++------------++---+ | | +---++--------------++-+ |
| || || | | || || |
| || || | | Controller || || |
+-------------++---------- ++--------------------+ +---------------++--------------++----------------+
|| || || ||
|| || || BGP, ||
||BGP,QoS || || QoS, ||
|| || || Interface, ||
+----------+|NI,Intf,IP |+-----------------+ +------------+| NI, |+--------------+
+--+--+ +++---+ --+---+ +--+--+ | | IP | |
| CE1 |------| PE1 | | PE2 | ---------+ CE2 | +--+--+ +--+--+ +--+--+ +--+--+
+-----+ +-----+ +-----+ +-----+ | CE1 +-------+ PE1 | | PE2 +---------+ CE2 |
Legend: +-----+ +-----+ +-----+ +-----+
Intf: Interface
Figure 6: L3VPN Service Delivery Example (Target) Figure 6: L3VPN Service Delivery Example (Target)
Note that a similar analysis can be performed for Layer 2 VPNs
(L2VPNs). A L2VPN Service Model (L2SM) is defined in [RFC8466],
while the L2VPN Network YANG Model (L2NM) is specified in
[I-D.barguil-opsawg-l2sm-l2nm].
5.2. VN Lifecycle Management 5.2. VN Lifecycle Management
In reference to Figure 7, the following steps are performed to In reference to Figure 7, the following steps are performed to
deliver the VN service within the network management automation deliver the VN service within the network management automation
architecture defined in this document: architecture defined in this document:
1. Customer requests (service exposure operation in Section 4.1.1) 1. Customer requests (service exposure operation in Section 4.1.1)
to create 'VN' based on Access point, association between VN and to create 'VN' based on Access point, association between VN and
Access point, VN member defined in the VN YANG module. Access point, VN member defined in the VN YANG module.
2. The orchestrator creates the single abstract node topology based 2. The orchestrator creates the single abstract node topology based
on the information captured in an VN YANG module. on the information captured in an VN YANG module.
3. The Customer exchanges connectivity-matrix on abstract node and 3. The Customer exchanges connectivity-matrix on abstract node and
explicit path using TE topology model with the orchestrator. explicit path using TE topology model with the orchestrator.
This information can be used to instantiate VN and setup tunnels This information can be used to instantiate VN and setup tunnels
between source and destination endpoints (service creation between source and destination endpoints (service creation
operation in Section 4.1.2). operation in Section 4.1.2).
4. The telemetry model which augments the TEAS VN model and 4. The telemetry model which augments the VN model and corresponding
corresponding TE tunnel model can be used to subscribe to TE tunnel model can be used to subscribe to performance
performance measurement data and notify all the parameter changes measurement data and notify all the parameter changes and network
and network performance change related to VN topology or Tunnel performance change related to VN topology or Tunnel
[I-D.ietf-teas-actn-pm-telemetry-autonomics] and provide service [I-D.ietf-teas-actn-pm-telemetry-autonomics] and provide service
assurance (service optimization operation in Section 4.1.3). assurance (service optimization operation in Section 4.1.3).
| |
VN | VN |
Service | Service |
Model | Model |
+----------------------|--------------------------+ +----------------------|--------------------------+
| Orchestrator | | | Orchestrator | |
| +--------V--------+ | | +--------V--------+ |
| | Service Mapping | | | | Service Mapping | |
| +-----------------+ | | +-----------------+ |
+----------------------+--------------------^-----+ +----------------------+--------------------^-----+
TE | Telemetry TE | Telemetry
Tunnel | Model Tunnel | Model
Model | | Model | |
+----------------------V--------------------+----+ +----------------------V--------------------+-----+
| Controller | | Controller |
| | | |
+-------------------------------------------------+ +-------------------------------------------------+
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+
| CE1 |------| PE1 | | PE2 |---------+ CE2 | | CE1 +------+ PE1 | | PE2 +------+ CE2 |
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+
Figure 7: A VN Service Delivery Example Figure 7: A VN Service Delivery Example
5.3. Event-based Telemetry in the Device Self Management 5.3. Event-based Telemetry in the Device Self Management
In reference to Figure 8, the following steps are performed to In reference to Figure 8, the following steps are performed to
monitor state changes of managed objects or resource in the device monitor state changes of managed objects or resources in a network
and provide device self management within the network management device and provide device self-management within the network
automation architecture defined in this document: management automation architecture defined in this document:
1. To control which state a network device should be in or is 1. To control which state a network device should be in or is
allowed to be in at any given time, a set of conditions and allowed to be in at any given time, a set of conditions and
actions are defined and correlated with network events (e.g., actions are defined and correlated with network events (e.g.,
allow the NETCONF server send updates only when the value exceeds allow the NETCONF server to send updates only when the value
a certain threshold for the first time but not again until the exceeds a certain threshold for the first time, but not again
threshold is cleared), which constitute an event-driven policy or until the threshold is cleared), which constitute ECA policy or
network control logic in the controller. an event-driven policy control logic that can be executed on the
device (e.g., [I-D.wwx-netmod-event-yang]).
2. The controller pushes ECA policy to the network device and 2. To provide rapid autonomic response that can exhibit self-
delegate network control logic to the network device. management properties, the controller pushes the ECA policy to
the network device and delegates network control logic to the
network device.
3. The network device generates ECA script from ECA model and 3. The network device uses the ECA model to subscribe to the event
execute ECA script or network control logic based on Event. source, e.g., an event stream or datastore state data conveyed to
Event based notification or telemetry can be triggered if a the server via YANG Push subscription, monitors state parameters,
certain condition is satisfied (model-driven telemetry operation and takes simple and instant actions when associated event
in Section 4.2.3). condition on state parameters is met. ECA notifications can be
generated as the result of actions based on event stream
subscription or datastore subscription (model-driven telemetry
operation discussed in Section 4.2.3).
+----------------+ +----------------+
| | | <----+
| Controller | | Controller | |
+-------+--------+ +-------+--------+ |
| | |
| | |
ECA | ECA | | ECA
Model| ^ Model | | Notification
| |Notification | |
| | | |
+------------V-------------+-------+ +------------V-------------+-----+
|Device | Reconfiguration |Device | |
| +-------+ +---------+ +--+---+ | | +-------+ +---------+ +--+---+ |
| | Event +-> Event +->Event | | | | Event +-> Event +->Event | |
| | Source| |Condition| |Action| | | | Source| |Condition| |Action| |
| +-------+ +---------+ +------+ | | +-------+ +---------+ +------+ |
+--------Update------trigger-------+ +--------------------------------+
Figure 8: Event-based Telemetry Figure 8: Event-based Telemetry
6. Security Considerations 6. Security Considerations
The YANG modules cited in this document define schema for data that The YANG modules cited in this document define schema for data that
are designed to be accessed via network management protocols such as are designed to be accessed via network management protocols such as
NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is
the secure transport layer, and the mandatory-to-implement secure the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
skipping to change at page 21, line 10 skipping to change at page 22, line 19
Security considerations specific to each of the technologies and Security considerations specific to each of the technologies and
protocols listed in the document are discussed in the specification protocols listed in the document are discussed in the specification
documents of each of these protocols. documents of each of these protocols.
Security considerations specific to this document are listed below: Security considerations specific to this document are listed below:
o Create forwarding loops by mis-configuring the underlying network. o Create forwarding loops by mis-configuring the underlying network.
o Leak sensitive information: special care should be considered when o Leak sensitive information: special care should be considered when
translating between the various layers introduced in the document. translating between the various layers in Section 4 or when
aggregating data retrieved from various sources. The Network
Operator must enforce means to protect privacy-related information
included in cutsomer-facing models.
o Some Service Models may include a traffic isolation clause, o Some Service Models may include a traffic isolation clause,
appropriate technology-specific actions must be enforced to avoid appropriate technology-specific actions must be enforced to avoid
that traffic is accessible to non-authorized parties. that traffic is accessible to non-authorized parties.
7. IANA Considerations 7. IANA Considerations
There are no IANA requests or assignments included in this document. There are no IANA requests or assignments included in this document.
8. Acknowledgements 8. Acknowledgements
Thanks to Joe Clark, Greg Mirsky, and Shunsuke Homma for the review. Thanks to Joe Clark, Greg Mirsky, Shunsuke Homma, Brian Carpenter,
and Adrian Farrel for the review.
9. Contributors 9. Contributors
Christian Jacquenet Christian Jacquenet
Orange Orange
Rennes, 35000 Rennes, 35000
France France
Email: Christian.jacquenet@orange.com Email: Christian.jacquenet@orange.com
Luis Miguel Contreras Murillo Luis Miguel Contreras Murillo
Telifonica Telifonica
Email: luismiguel.contrerasmurillo@telefonica.com Email: luismiguel.contrerasmurillo@telefonica.com
Oscar Gonzalez de Dios Oscar Gonzalez de Dios
Telefonica Telefonica
Madrid Madrid
ES ES
Email: oscar.gonzalezdedios@telefonica.com Email: oscar.gonzalezdedios@telefonica.com
Chongfeng Xie
China Telecom
Beijing
China
Email: xiechf.bri@chinatelecom.cn
Weiqiang Cheng Weiqiang Cheng
China Mobile China Mobile
Email: chengweiqiang@chinamobile.com Email: chengweiqiang@chinamobile.com
Young Lee Young Lee
Sung Kyun Kwan University Sung Kyun Kwan University
Email: younglee.tx@gmail.com Email: younglee.tx@gmail.com
skipping to change at page 23, line 24 skipping to change at page 24, line 16
Access Control Model", STD 91, RFC 8341, Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018, DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>. <https://www.rfc-editor.org/info/rfc8341>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
10.2. Informative References 10.2. Informative References
[I-D.barguil-opsawg-l2sm-l2nm]
Barguil, S., Dios, O., Boucadair, M., Munoz, L., Jalil,
L., and J. Ma, "A Layer 2 VPN Network YANG Model", draft-
barguil-opsawg-l2sm-l2nm-02 (work in progress), May 2020.
[I-D.ietf-bess-evpn-yang] [I-D.ietf-bess-evpn-yang]
Brissette, P., Shah, H., Hussain, I., Tiruveedhula, K., Brissette, P., Shah, H., Hussain, I., Tiruveedhula, K.,
and J. Rabadan, "Yang Data Model for EVPN", draft-ietf- and J. Rabadan, "Yang Data Model for EVPN", draft-ietf-
bess-evpn-yang-07 (work in progress), March 2019. bess-evpn-yang-07 (work in progress), March 2019.
[I-D.ietf-bess-l2vpn-yang] [I-D.ietf-bess-l2vpn-yang]
Shah, H., Brissette, P., Chen, I., Hussain, I., Wen, B., Shah, H., Brissette, P., Chen, I., Hussain, I., Wen, B.,
and K. Tiruveedhula, "YANG Data Model for MPLS-based and K. Tiruveedhula, "YANG Data Model for MPLS-based
L2VPN", draft-ietf-bess-l2vpn-yang-10 (work in progress), L2VPN", draft-ietf-bess-l2vpn-yang-10 (work in progress),
July 2019. July 2019.
[I-D.ietf-bess-l3vpn-yang] [I-D.ietf-bess-l3vpn-yang]
Jain, D., Patel, K., Brissette, P., Li, Z., Zhuang, S., Jain, D., Patel, K., Brissette, P., Li, Z., Zhuang, S.,
Liu, X., Haas, J., Esale, S., and B. Wen, "Yang Data Model Liu, X., Haas, J., Esale, S., and B. Wen, "Yang Data Model
for BGP/MPLS L3 VPNs", draft-ietf-bess-l3vpn-yang-04 (work for BGP/MPLS L3 VPNs", draft-ietf-bess-l3vpn-yang-04 (work
in progress), October 2018. in progress), October 2018.
[I-D.ietf-bess-mvpn-yang]
Liu, Y., Guo, F., Litkowski, S., Liu, X., Kebler, R., and
M. Sivakumar, "Yang Data Model for Multicast in MPLS/BGP
IP VPNs", draft-ietf-bess-mvpn-yang-02 (work in progress),
December 2019.
[I-D.ietf-bfd-yang] [I-D.ietf-bfd-yang]
Rahman, R., Zheng, L., Jethanandani, M., Pallagatti, S., Rahman, R., Zheng, L., Jethanandani, M., Pallagatti, S.,
and G. Mirsky, "YANG Data Model for Bidirectional and G. Mirsky, "YANG Data Model for Bidirectional
Forwarding Detection (BFD)", draft-ietf-bfd-yang-17 (work Forwarding Detection (BFD)", draft-ietf-bfd-yang-17 (work
in progress), August 2018. in progress), August 2018.
[I-D.ietf-dots-data-channel]
Boucadair, M. and T. Reddy.K, "Distributed Denial-of-
Service Open Threat Signaling (DOTS) Data Channel
Specification", draft-ietf-dots-data-channel-31 (work in
progress), July 2019.
[I-D.ietf-i2rs-yang-l2-network-topology] [I-D.ietf-i2rs-yang-l2-network-topology]
Dong, J., Wei, X., WU, Q., Boucadair, M., and A. Liu, "A Dong, J., Wei, X., WU, Q., Boucadair, M., and A. Liu, "A
YANG Data Model for Layer-2 Network Topologies", draft- YANG Data Model for Layer-2 Network Topologies", draft-
ietf-i2rs-yang-l2-network-topology-13 (work in progress), ietf-i2rs-yang-l2-network-topology-13 (work in progress),
March 2020. March 2020.
[I-D.ietf-idr-bgp-model] [I-D.ietf-idr-bgp-model]
Jethanandani, M., Patel, K., Hares, S., and J. Haas, "BGP Jethanandani, M., Patel, K., Hares, S., and J. Haas, "BGP
YANG Model for Service Provider Networks", draft-ietf-idr- YANG Model for Service Provider Networks", draft-ietf-idr-
bgp-model-08 (work in progress), February 2020. bgp-model-08 (work in progress), February 2020.
[I-D.ietf-ippm-capacity-metric-method]
Morton, A., Geib, R., and L. Ciavattone, "Metrics and
Methods for IP Capacity", draft-ietf-ippm-capacity-metric-
method-01 (work in progress), March 2020.
[I-D.ietf-ippm-stamp-yang] [I-D.ietf-ippm-stamp-yang]
Mirsky, G., Xiao, M., and W. Luo, "Simple Two-way Active Mirsky, G., Xiao, M., and W. Luo, "Simple Two-way Active
Measurement Protocol (STAMP) Data Model", draft-ietf-ippm- Measurement Protocol (STAMP) Data Model", draft-ietf-ippm-
stamp-yang-05 (work in progress), October 2019. stamp-yang-05 (work in progress), October 2019.
[I-D.ietf-ippm-twamp-yang] [I-D.ietf-ippm-twamp-yang]
Civil, R., Morton, A., Rahman, R., Jethanandani, M., and Civil, R., Morton, A., Rahman, R., Jethanandani, M., and
K. Pentikousis, "Two-Way Active Measurement Protocol K. Pentikousis, "Two-Way Active Measurement Protocol
(TWAMP) Data Model", draft-ietf-ippm-twamp-yang-13 (work (TWAMP) Data Model", draft-ietf-ippm-twamp-yang-13 (work
in progress), July 2018. in progress), July 2018.
[I-D.ietf-mpls-base-yang] [I-D.ietf-mpls-base-yang]
Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A
YANG Data Model for MPLS Base", draft-ietf-mpls-base- YANG Data Model for MPLS Base", draft-ietf-mpls-base-
yang-14 (work in progress), March 2020. yang-14 (work in progress), March 2020.
[I-D.ietf-opsawg-l3sm-l3nm]
Barguil, S., Dios, O., Boucadair, M., Munoz, L., and A.
Aguado, "A Layer 3 VPN Network YANG Model", draft-ietf-
opsawg-l3sm-l3nm-03 (work in progress), April 2020.
[I-D.ietf-pim-igmp-mld-snooping-yang] [I-D.ietf-pim-igmp-mld-snooping-yang]
Zhao, H., Liu, X., Liu, Y., Sivakumar, M., and A. Peter, Zhao, H., Liu, X., Liu, Y., Sivakumar, M., and A. Peter,
"A Yang Data Model for IGMP and MLD Snooping", draft-ietf- "A Yang Data Model for IGMP and MLD Snooping", draft-ietf-
pim-igmp-mld-snooping-yang-10 (work in progress), May pim-igmp-mld-snooping-yang-12 (work in progress), May
2020. 2020.
[I-D.ietf-pim-yang] [I-D.ietf-pim-yang]
Liu, X., McAllister, P., Peter, A., Sivakumar, M., Liu, Liu, X., McAllister, P., Peter, A., Sivakumar, M., Liu,
Y., and f. hu, "A YANG Data Model for Protocol Independent Y., and f. hu, "A YANG Data Model for Protocol Independent
Multicast (PIM)", draft-ietf-pim-yang-17 (work in Multicast (PIM)", draft-ietf-pim-yang-17 (work in
progress), May 2018. progress), May 2018.
[I-D.ietf-rtgwg-device-model] [I-D.ietf-rtgwg-device-model]
Lindem, A., Berger, L., Bogdanovic, D., and C. Hopps, Lindem, A., Berger, L., Bogdanovic, D., and C. Hopps,
"Network Device YANG Logical Organization", draft-ietf- "Network Device YANG Logical Organization", draft-ietf-
rtgwg-device-model-02 (work in progress), March 2017. rtgwg-device-model-02 (work in progress), March 2017.
[I-D.ietf-rtgwg-policy-model] [I-D.ietf-rtgwg-policy-model]
Qu, Y., Tantsura, J., Lindem, A., and X. Liu, "A YANG Data Qu, Y., Tantsura, J., Lindem, A., and X. Liu, "A YANG Data
Model for Routing Policy Management", draft-ietf-rtgwg- Model for Routing Policy Management", draft-ietf-rtgwg-
policy-model-11 (work in progress), May 2020. policy-model-15 (work in progress), June 2020.
[I-D.ietf-rtgwg-qos-model] [I-D.ietf-rtgwg-qos-model]
Choudhary, A., Jethanandani, M., Strahle, N., Aries, E., Choudhary, A., Jethanandani, M., Strahle, N., Aries, E.,
and I. Chen, "YANG Model for QoS", draft-ietf-rtgwg-qos- and I. Chen, "YANG Model for QoS", draft-ietf-rtgwg-qos-
model-01 (work in progress), April 2020. model-01 (work in progress), April 2020.
[I-D.ietf-spring-sr-yang] [I-D.ietf-spring-sr-yang]
Litkowski, S., Qu, Y., Lindem, A., Sarkar, P., and J. Litkowski, S., Qu, Y., Lindem, A., Sarkar, P., and J.
Tantsura, "YANG Data Model for Segment Routing", draft- Tantsura, "YANG Data Model for Segment Routing", draft-
ietf-spring-sr-yang-15 (work in progress), January 2020. ietf-spring-sr-yang-15 (work in progress), January 2020.
skipping to change at page 25, line 36 skipping to change at page 26, line 46
progress), March 2020. progress), March 2020.
[I-D.ietf-teas-actn-vn-yang] [I-D.ietf-teas-actn-vn-yang]
Lee, Y., Dhody, D., Ceccarelli, D., Bryskin, I., and B. Lee, Y., Dhody, D., Ceccarelli, D., Bryskin, I., and B.
Yoon, "A Yang Data Model for VN Operation", draft-ietf- Yoon, "A Yang Data Model for VN Operation", draft-ietf-
teas-actn-vn-yang-08 (work in progress), March 2020. teas-actn-vn-yang-08 (work in progress), March 2020.
[I-D.ietf-teas-yang-path-computation] [I-D.ietf-teas-yang-path-computation]
Busi, I., Belotti, S., Lopezalvarez, V., Sharma, A., and Busi, I., Belotti, S., Lopezalvarez, V., Sharma, A., and
Y. Shi, "Yang model for requesting Path Computation", Y. Shi, "Yang model for requesting Path Computation",
draft-ietf-teas-yang-path-computation-08 (work in draft-ietf-teas-yang-path-computation-09 (work in
progress), December 2019. progress), June 2020.
[I-D.ietf-teas-yang-rsvp-te] [I-D.ietf-teas-yang-rsvp-te]
Beeram, V., Saad, T., Gandhi, R., Liu, X., Bryskin, I., Beeram, V., Saad, T., Gandhi, R., Liu, X., Bryskin, I.,
and H. Shah, "A YANG Data Model for RSVP-TE Protocol", and H. Shah, "A YANG Data Model for RSVP-TE Protocol",
draft-ietf-teas-yang-rsvp-te-08 (work in progress), March draft-ietf-teas-yang-rsvp-te-08 (work in progress), March
2020. 2020.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"A YANG Data Model for Traffic Engineering Tunnels and "A YANG Data Model for Traffic Engineering Tunnels and
skipping to change at page 26, line 29 skipping to change at page 27, line 41
Model for User-Network Interface (UNI) Topologies", draft- Model for User-Network Interface (UNI) Topologies", draft-
ogondio-opsawg-uni-topology-01 (work in progress), April ogondio-opsawg-uni-topology-01 (work in progress), April
2020. 2020.
[I-D.www-bess-yang-vpn-service-pm] [I-D.www-bess-yang-vpn-service-pm]
WU, Q., Boucadair, M., Dios, O., Wen, B., Liu, C., and H. WU, Q., Boucadair, M., Dios, O., Wen, B., Liu, C., and H.
Xu, "A YANG Model for Network and VPN Service Performance Xu, "A YANG Model for Network and VPN Service Performance
Monitoring", draft-www-bess-yang-vpn-service-pm-06 (work Monitoring", draft-www-bess-yang-vpn-service-pm-06 (work
in progress), April 2020. in progress), April 2020.
[I-D.wwx-netmod-event-yang]
Birkholz, H., WU, Q., Bryskin, I., Liu, X., and B. Claise,
"A YANG Data model for ECA Policy Management", draft-wwx-
netmod-event-yang-07 (work in progress), May 2020.
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
2006, <https://www.rfc-editor.org/info/rfc4364>. 2006, <https://www.rfc-editor.org/info/rfc4364>.
[RFC4664] Andersson, L., Ed. and E. Rosen, Ed., "Framework for Layer [RFC4664] Andersson, L., Ed. and E. Rosen, Ed., "Framework for Layer
2 Virtual Private Networks (L2VPNs)", RFC 4664, 2 Virtual Private Networks (L2VPNs)", RFC 4664,
DOI 10.17487/RFC4664, September 2006, DOI 10.17487/RFC4664, September 2006,
<https://www.rfc-editor.org/info/rfc4664>. <https://www.rfc-editor.org/info/rfc4664>.
[RFC4761] Kompella, K., Ed. and Y. Rekhter, Ed., "Virtual Private [RFC4761] Kompella, K., Ed. and Y. Rekhter, Ed., "Virtual Private
LAN Service (VPLS) Using BGP for Auto-Discovery and LAN Service (VPLS) Using BGP for Auto-Discovery and
Signaling", RFC 4761, DOI 10.17487/RFC4761, January 2007, Signaling", RFC 4761, DOI 10.17487/RFC4761, January 2007,
<https://www.rfc-editor.org/info/rfc4761>. <https://www.rfc-editor.org/info/rfc4761>.
[RFC4762] Lasserre, M., Ed. and V. Kompella, Ed., "Virtual Private [RFC4762] Lasserre, M., Ed. and V. Kompella, Ed., "Virtual Private
LAN Service (VPLS) Using Label Distribution Protocol (LDP) LAN Service (VPLS) Using Label Distribution Protocol (LDP)
Signaling", RFC 4762, DOI 10.17487/RFC4762, January 2007, Signaling", RFC 4762, DOI 10.17487/RFC4762, January 2007,
<https://www.rfc-editor.org/info/rfc4762>. <https://www.rfc-editor.org/info/rfc4762>.
[RFC5136] Chimento, P. and J. Ishac, "Defining Network Capacity",
RFC 5136, DOI 10.17487/RFC5136, February 2008,
<https://www.rfc-editor.org/info/rfc5136>.
[RFC5486] Malas, D., Ed. and D. Meyer, Ed., "Session Peering for [RFC5486] Malas, D., Ed. and D. Meyer, Ed., "Session Peering for
Multimedia Interconnect (SPEERMINT) Terminology", Multimedia Interconnect (SPEERMINT) Terminology",
RFC 5486, DOI 10.17487/RFC5486, March 2009, RFC 5486, DOI 10.17487/RFC5486, March 2009,
<https://www.rfc-editor.org/info/rfc5486>. <https://www.rfc-editor.org/info/rfc5486>.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<https://www.rfc-editor.org/info/rfc5880>. <https://www.rfc-editor.org/info/rfc5880>.
[RFC6406] Malas, D., Ed. and J. Livingood, Ed., "Session PEERing for
Multimedia INTerconnect (SPEERMINT) Architecture",
RFC 6406, DOI 10.17487/RFC6406, November 2011,
<https://www.rfc-editor.org/info/rfc6406>.
[RFC7149] Boucadair, M. and C. Jacquenet, "Software-Defined [RFC7149] Boucadair, M. and C. Jacquenet, "Software-Defined
Networking: A Perspective from within a Service Provider Networking: A Perspective from within a Service Provider
Environment", RFC 7149, DOI 10.17487/RFC7149, March 2014, Environment", RFC 7149, DOI 10.17487/RFC7149, March 2014,
<https://www.rfc-editor.org/info/rfc7149>. <https://www.rfc-editor.org/info/rfc7149>.
[RFC7276] Mizrahi, T., Sprecher, N., Bellagamba, E., and Y. [RFC7276] Mizrahi, T., Sprecher, N., Bellagamba, E., and Y.
Weingarten, "An Overview of Operations, Administration, Weingarten, "An Overview of Operations, Administration,
and Maintenance (OAM) Tools", RFC 7276, and Maintenance (OAM) Tools", RFC 7276,
DOI 10.17487/RFC7276, June 2014, DOI 10.17487/RFC7276, June 2014,
<https://www.rfc-editor.org/info/rfc7276>. <https://www.rfc-editor.org/info/rfc7276>.
skipping to change at page 27, line 31 skipping to change at page 29, line 11
Connectivity Provisioning Profile (CPP)", RFC 7297, Connectivity Provisioning Profile (CPP)", RFC 7297,
DOI 10.17487/RFC7297, July 2014, DOI 10.17487/RFC7297, July 2014,
<https://www.rfc-editor.org/info/rfc7297>. <https://www.rfc-editor.org/info/rfc7297>.
[RFC7455] Senevirathne, T., Finn, N., Salam, S., Kumar, D., Eastlake [RFC7455] Senevirathne, T., Finn, N., Salam, S., Kumar, D., Eastlake
3rd, D., Aldrin, S., and Y. Li, "Transparent 3rd, D., Aldrin, S., and Y. Li, "Transparent
Interconnection of Lots of Links (TRILL): Fault Interconnection of Lots of Links (TRILL): Fault
Management", RFC 7455, DOI 10.17487/RFC7455, March 2015, Management", RFC 7455, DOI 10.17487/RFC7455, March 2015,
<https://www.rfc-editor.org/info/rfc7455>. <https://www.rfc-editor.org/info/rfc7455>.
[RFC7679] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton,
Ed., "A One-Way Delay Metric for IP Performance Metrics
(IPPM)", STD 81, RFC 7679, DOI 10.17487/RFC7679, January
2016, <https://www.rfc-editor.org/info/rfc7679>.
[RFC7680] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton,
Ed., "A One-Way Loss Metric for IP Performance Metrics
(IPPM)", STD 82, RFC 7680, DOI 10.17487/RFC7680, January
2016, <https://www.rfc-editor.org/info/rfc7680>.
[RFC8077] Martini, L., Ed. and G. Heron, Ed., "Pseudowire Setup and [RFC8077] Martini, L., Ed. and G. Heron, Ed., "Pseudowire Setup and
Maintenance Using the Label Distribution Protocol (LDP)", Maintenance Using the Label Distribution Protocol (LDP)",
STD 84, RFC 8077, DOI 10.17487/RFC8077, February 2017, STD 84, RFC 8077, DOI 10.17487/RFC8077, February 2017,
<https://www.rfc-editor.org/info/rfc8077>. <https://www.rfc-editor.org/info/rfc8077>.
[RFC8194] Schoenwaelder, J. and V. Bajpai, "A YANG Data Model for [RFC8194] Schoenwaelder, J. and V. Bajpai, "A YANG Data Model for
LMAP Measurement Agents", RFC 8194, DOI 10.17487/RFC8194, LMAP Measurement Agents", RFC 8194, DOI 10.17487/RFC8194,
August 2017, <https://www.rfc-editor.org/info/rfc8194>. August 2017, <https://www.rfc-editor.org/info/rfc8194>.
[RFC8199] Bogdanovic, D., Claise, B., and C. Moberg, "YANG Module [RFC8199] Bogdanovic, D., Claise, B., and C. Moberg, "YANG Module
skipping to change at page 29, line 39 skipping to change at page 31, line 29
Raghavan, "A YANG Data Model for Retrieval Methods for the Raghavan, "A YANG Data Model for Retrieval Methods for the
Management of Operations, Administration, and Maintenance Management of Operations, Administration, and Maintenance
(OAM) Protocols That Use Connectionless Communications", (OAM) Protocols That Use Connectionless Communications",
RFC 8533, DOI 10.17487/RFC8533, April 2019, RFC 8533, DOI 10.17487/RFC8533, April 2019,
<https://www.rfc-editor.org/info/rfc8533>. <https://www.rfc-editor.org/info/rfc8533>.
[RFC8632] Vallin, S. and M. Bjorklund, "A YANG Data Model for Alarm [RFC8632] Vallin, S. and M. Bjorklund, "A YANG Data Model for Alarm
Management", RFC 8632, DOI 10.17487/RFC8632, September Management", RFC 8632, DOI 10.17487/RFC8632, September
2019, <https://www.rfc-editor.org/info/rfc8632>. 2019, <https://www.rfc-editor.org/info/rfc8632>.
[RFC8652] Liu, X., Guo, F., Sivakumar, M., McAllister, P., and A.
Peter, "A YANG Data Model for the Internet Group
Management Protocol (IGMP) and Multicast Listener
Discovery (MLD)", RFC 8652, DOI 10.17487/RFC8652, November
2019, <https://www.rfc-editor.org/info/rfc8652>.
[RFC8675] Boucadair, M., Farrer, I., and R. Asati, "A YANG Data [RFC8675] Boucadair, M., Farrer, I., and R. Asati, "A YANG Data
Model for Tunnel Interface Types", RFC 8675, Model for Tunnel Interface Types", RFC 8675,
DOI 10.17487/RFC8675, November 2019, DOI 10.17487/RFC8675, November 2019,
<https://www.rfc-editor.org/info/rfc8675>. <https://www.rfc-editor.org/info/rfc8675>.
[RFC8676] Farrer, I., Ed. and M. Boucadair, Ed., "YANG Modules for [RFC8676] Farrer, I., Ed. and M. Boucadair, Ed., "YANG Modules for
IPv4-in-IPv6 Address plus Port (A+P) Softwires", RFC 8676, IPv4-in-IPv6 Address plus Port (A+P) Softwires", RFC 8676,
DOI 10.17487/RFC8676, November 2019, DOI 10.17487/RFC8676, November 2019,
<https://www.rfc-editor.org/info/rfc8676>. <https://www.rfc-editor.org/info/rfc8676>.
[RFC8783] Boucadair, M., Ed. and T. Reddy.K, Ed., "Distributed
Denial-of-Service Open Threat Signaling (DOTS) Data
Channel Specification", RFC 8783, DOI 10.17487/RFC8783,
May 2020, <https://www.rfc-editor.org/info/rfc8783>.
Appendix A. Layered YANG Modules Examples Overview Appendix A. Layered YANG Modules Examples Overview
This appendix lists a set of data models that can be used for the
delivery of connectivity services. These models can be classified as
Service, Network, or Device Models.
It is not the intent of this appendix to provide an inventory of It is not the intent of this appendix to provide an inventory of
tools and mechanisms used in specific network and service management tools and mechanisms used in specific network and service management
domains; such inventory can be found in documents such as [RFC7276]. domains; such inventory can be found in documents such as [RFC7276].
A.1. Service Models: Definition and Samples A.1. Service Models: Definition and Samples
As described in [RFC8309], the service is "some form of connectivity As described in [RFC8309], the service is "some form of connectivity
between customer sites and the Internet and/or between customer sites between customer sites and the Internet and/or between customer sites
across the network operator's network and across the Internet". More across the Network Operator's network and across the Internet". More
concretely, an IP connectivity service can be defined as the IP concretely, an IP connectivity service can be defined as the IP
transfer capability characterized by a (Source Nets, Destination transfer capability characterized by a (Source Nets, Destination
Nets, Guarantees, Scope) tuple where "Source Nets" is a group of Nets, Guarantees, Scope) tuple where "Source Nets" is a group of
unicast IP addresses, "Destination Nets" is a group of IP unicast unicast IP addresses, "Destination Nets" is a group of IP unicast
and/or multicast addresses, and "Guarantees" reflects the guarantees and/or multicast addresses, and "Guarantees" reflects the guarantees
(expressed in terms of Quality Of Service (QoS), performance, and (expressed in terms of QoS, performance, and availability, for
availability, for example) to properly forward traffic to the said example) to properly forward traffic to the said "Destination"
"Destination" [RFC7297]. [RFC7297].
For example: For example:
o The L3SM model [RFC8299] defines the L3VPN service ordered by a o The L3SM model [RFC8299] defines the L3VPN service ordered by a
customer from a network operator. customer from a Network Operator.
o The L2SM model [RFC8466] defines the L2VPN service ordered by a o The L2SM model [RFC8466] defines the L2VPN service ordered by a
customer from a network operator. customer from a Network Operator.
o The Virtual Network (VN) model [I-D.ietf-teas-actn-vn-yang] o The Virtual Network (VN) model [I-D.ietf-teas-actn-vn-yang]
provides a YANG data model applicable to any mode of VN operation. provides a YANG data model applicable to any mode of VN operation.
L2SM and L3SM are customer service models as per [RFC8309].
A.2. Network Models: Samples A.2. Network Models: Samples
Figure 9 depicts a set of Network Models such as topology models or L2NM [I-D.barguil-opsawg-l2sm-l2nm] and L3NM
tunnel models: [I-D.ietf-opsawg-l3sm-l3nm] are examples of YANG Network Models.
Topology | Tunnel | Figure 9 depicts a set of additional Network Models such as topology
YANG modules | YANG modules | and tunnel models:
---------------------+-------------------------------|
+------------+ | | +-------------------------------+-------------------------------+
|Network Topo| | +------+ +-----------+ | | Topology YANG modules | Tunnel YANG modules |
| Model | | |Other | | TE Tunnel | | +-------------------------------+-------------------------------+
+----+-------+ | |Tunnel| +----+------+ | | +------------+ | |
| +--------+ | +------+ | | | |Network Topo| | +------+ +-----------+ |
|---+Svc Topo| | +----------+---------+ | | | Model | | |Other | | TE Tunnel | |
| +--------+ | | | | | | +----+-------+ | |Tunnel| +----+------+ |
| +--------+ |+----+---+ +----+---+ +---+---+| | | +--------+ | +------+ | |
|---+L2 Topo | ||MPLS-TE | |RSVP-TE | |SR TE || | +---+Svc Topo| | +----------+---------+ |
| +--------+ || Tunnel | | Tunnel | |Tunnel || | | +--------+ | | | | |
| +--------+ |+--------+ +--------+ +-------+| | | +--------+ |+----+---+ +----+---+ +---+---+|
|---+TE Topo | | | | +---+L2 Topo | ||MPLS-TE | |RSVP-TE | | SR-TE ||
| +--------+ | | | | +--------+ || Tunnel | | Tunnel | |Tunnel ||
| +--------+ | | | | +--------+ |+--------+ +--------+ +-------+|
+---+L3 Topo | | | | +---+TE Topo | | |
+--------+ | | | | +--------+ | |
Legend: | | +--------+ | |
Topo: Topology | +---+L3 Topo | | |
Svc: Service | +--------+ | |
+-------------------------------+-------------------------------+
Legend:
Topo: Topology
Svc: Service
Figure 9: Sample Resource Facing Network Models Figure 9: Sample Resource Facing Network Models
Examples of topology YANG modules are listed below: Examples of topology YANG modules are listed below:
o Network Topology Models: [RFC8345] defines a base model for o Network Topology Models: [RFC8345] defines a base model for
network topology and inventories. Network topology data include network topology and inventories. Network topology data include
link resource, node resource, and terminate-point resources. link resource, node resource, and terminate-point resources.
o TE Topology Models: [I-D.ietf-teas-yang-te-topo] defines a data o TE Topology Models: [I-D.ietf-teas-yang-te-topo] defines a data
model for representing and manipulating TE topologies. model for representing and manipulating TE topologies.
This module is extended from network topology model defined in This module is extended from network topology model defined in
[RFC8345] with TE topologies specifics. This model contains [RFC8345] with TE topologies specifics. This model contains
technology-agnostic TE Topology building blocks that can be technology-agnostic TE Topology building blocks that can be
augmented and used by other technology-specific TE topology augmented and used by other technology-specific TE topology
models. models.
o L3 Topology Models o Layer 3 Topology Models:
[RFC8346] defines a data model for representing and manipulating [RFC8346] defines a data model for representing and manipulating
Layer 3 topologies. This model is extended from the network Layer 3 topologies. This model is extended from the network
topology model defined in [RFC8345] with L3 topologies specifics. topology model defined in [RFC8345] with Layer 3 topologies
specifics.
o L2 Topology Models o Layer 2 Topology Models:
[I-D.ietf-i2rs-yang-l2-network-topology] defines a data model for [I-D.ietf-i2rs-yang-l2-network-topology] defines a data model for
representing and manipulating L2 topologies. This model is representing and manipulating Layer 2 topologies. This model is
extended from the network topology model defined in [RFC8345] with extended from the network topology model defined in [RFC8345] with
Layer 2 topologies specifics. Layer 2 topologies specifics.
Examples of tunnel YANG modules are provided below: Examples of tunnel YANG modules are provided below:
o Tunnel identities to ease manipulating extensions to specific o Tunnel identities to ease manipulating extensions to specific
tunnels [RFC8675]. tunnels [RFC8675].
o TE Tunnel Model: o TE Tunnel Model:
[I-D.ietf-teas-yang-te] defines a YANG module for the [I-D.ietf-teas-yang-te] defines a YANG module for the
configuration and management of TE interfaces, tunnels, and LSPs. configuration and management of TE interfaces, tunnels, and LSPs.
o SR TE Tunnel Model: o Segment Routing (SR) Traffic Engineering (TE) Tunnel Model:
[I-D.ietf-teas-yang-te] augments the TE generic and MPLS-TE [I-D.ietf-teas-yang-te] augments the TE generic and MPLS-TE
model(s) and defines a YANG module for Segment Routing (SR) TE model(s) and defines a YANG module for SR-TE specific data.
specific data.
o MPLS TE Model: o MPLS-TE Model:
[I-D.ietf-teas-yang-te] augments the TE generic and MPLS-TE [I-D.ietf-teas-yang-te] augments the TE generic and MPLS-TE
model(s) and defines a YANG module for MPLS TE configurations, model(s) and defines a YANG module for MPLS-TE configurations,
state, RPC and notifications. state, RPC and notifications.
o RSVP-TE MPLS Model: o RSVP-TE MPLS Model:
[I-D.ietf-teas-yang-rsvp-te] augments the RSVP-TE generic module [I-D.ietf-teas-yang-rsvp-te] augments the RSVP-TE generic module
with parameters to configure and manage signaling of MPLS RSVP-TE with parameters to configure and manage signaling of MPLS RSVP-TE
LSPs. LSPs.
Other sample Network Models are listed hereafter: Other sample Network Models are listed hereafter:
skipping to change at page 34, line 5 skipping to change at page 36, line 5
basic framework, its elements, and interfaces. basic framework, its elements, and interfaces.
A.3. Device Models: Samples A.3. Device Models: Samples
Network Element models (Figure 10) are used to describe how a service Network Element models (Figure 10) are used to describe how a service
can be implemented by activating and tweaking a set of functions can be implemented by activating and tweaking a set of functions
(enabled in one or multiple devices, or hosted in cloud (enabled in one or multiple devices, or hosted in cloud
infrastructures) that are involved in the service delivery. infrastructures) that are involved in the service delivery.
Figure 10 uses IETF-defined models as an example. Figure 10 uses IETF-defined models as an example.
+----------------------+ +------------------------+
+-| Device Model | +-+ Device Model |
| +----------------------+ | +------------------------+
| +----------------------+ | +------------------------+
+---------------+ | | Logical Network | +---------------+ | | Logical Network |
| | +-| Element Model | | | +-+ Element Model |
| Architecture | | +----------------------+ | Architecture | | +------------------------+
| | | +----------------------+ | | | +------------------------+
+-------+-------+ +-|Network Instance Model| +-------+-------+ +-+ Network Instance Model |
| | +----------------------+ | | +------------------------+
| | +----------------------+ | | +------------------------+
| +-| Routing Type Model | | +-+ Routing Type Model |
| +----------------------+ | +------------------------+
+-------+----------+----+--------+------------+-----------+-------+ +-------+----------+----+------+------------+-----------+------+
| | | | | | | | | | | | | |
+-+-+ +---+---+ +----+----+ +-+-+ +-----+---+ +---+-+ | +-+-+ +---+---+ +----+----+ +--+--+ +----+----+ +--+--+ |
|ACL| |Routing| |Transport| |OAM| |Multicast| | PM | Others |ACL| |Routing| |Transport| | OAM | |Multicast| | PM | Others
+---+ |-------+ +---------+ +---+ +---------+ +-----+ +---+ +-+-----+ +----+----+ +--+--+ +-----+---+ +--+--+
| +-------+ | +----------+ | +-------+ | +-----+ | +-----+ | +-------+ | +------+ | +--------+ | +-----+ | +-----+
+-|Core | +-|MPLS Basic| +-|BFD | +-|IGMP | +-|TWAMP| +-+Core | +-+ MPLS | +-+ BFD | +-+IGMP | +-+TWAMP|
| |Routing| | +----------+ | +-------+ | |/MLD | | +-----+ | |Routing| | | Base | | +--------+ | |/MLD | | +-----+
| +-------+ +-|MPLS LDP | +-|LSP Ping | +-----+ +-|OWAMP| | +-------+ | +------+ | +--------+ | +-----+ | +-----+
+-|BGP | | +----------+ | +-------+ +-|PIM | | +-----+ | +-------+ | +------+ +-+LSP Ping| | +-----+ +-+OWAMP|
| +-------+ +-|MPLS Static +-|MPLS-TP| | +-----+ +-|LMAP | +-+ BGP | +-+ MPLS | | +--------+ +-+ PIM | | +-----+
+-|ISIS | +----------+ +-------+ +-|MVPN | +-----+ | +-------+ | | LDP | | +--------+ | +-----+ | +-----+
| +-------+ +-----+ | +-------+ | +------+ +-+MPLS-TP | | +-----+ +-+LMAP |
+-|OSPF | +-+ ISIS | | +------+ +--------+ +-+ MVPN| +-----+
| +-------+ | +-------+ +-+ MPLS | +-----+
+-|RIP | | +-------+ |Static|
| +-------+ +-+ OSPF | +------+
+-|VRRP | | +-------+
| +-------+ | +-------+
+-|SR/SRv6| +-+ RIP |
| +-------+ | +-------+
+-|ISIS-SR| | +-------+
| +-------+ +-+ VRRP |
+-|OSPF-SR| | +-------+
+-------+ | +-------+
+-+SR/SRv6|
| +-------+
| +-------+
+-+ISIS-SR|
| +-------+
| +-------+
+-+OSPF-SR|
+-------+
Figure 10: Network Element Modules Overview Figure 10: Network Element Modules Overview
A.3.1. Model Composition A.3.1. Model Composition
o Device Model o Device Model
[I-D.ietf-rtgwg-device-model] presents an approach for organizing [I-D.ietf-rtgwg-device-model] presents an approach for organizing
YANG modules in a comprehensive logical structure that may be used YANG modules in a comprehensive logical structure that may be used
to configure and operate network devices. The structure is itself to configure and operate network devices. The structure is itself
skipping to change at page 35, line 22 skipping to change at page 37, line 30
used to manage the logical resource partitioning that may be used to manage the logical resource partitioning that may be
present on a network device. Examples of common industry terms present on a network device. Examples of common industry terms
for logical resource partitioning are Logical Systems or Logical for logical resource partitioning are Logical Systems or Logical
Routers. Routers.
o Network Instance Model o Network Instance Model
[RFC8529] defines a network instance module. This module can be [RFC8529] defines a network instance module. This module can be
used to manage the virtual resource partitioning that may be used to manage the virtual resource partitioning that may be
present on a network device. Examples of common industry terms present on a network device. Examples of common industry terms
for virtual resource partitioning are Virtual Routing and for virtual resource partitioning are VRF instances and Virtual
Forwarding (VRF) instances and Virtual Switch Instances (VSIs). Switch Instances (VSIs).
A.3.1.1. Schema Mount A.3.1.1. Schema Mount
Modularity and extensibility were among the leading design principles Modularity and extensibility were among the leading design principles
of the YANG data modeling language. As a result, the same YANG of the YANG data modeling language. As a result, the same YANG
module can be combined with various sets of other modules and thus 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 form a data model that is tailored to meet the requirements of a
specific use case. [RFC8528] defines a mechanism, denoted schema specific use case. [RFC8528] defines a mechanism, denoted schema
mount, that allows for mounting one data model consisting of any mount, that allows for mounting one data model consisting of any
number of YANG modules at a specified location of another (parent) number of YANG modules at a specified location of another (parent)
skipping to change at page 36, line 4 skipping to change at page 38, line 11
BGP: [I-D.ietf-idr-bgp-model] defines a YANG module for BGP: [I-D.ietf-idr-bgp-model] defines a YANG module for
configuring and managing BGP, including protocol, policy, configuring and managing BGP, including protocol, policy,
and operational aspects based on data center, carrier, and and operational aspects based on data center, carrier, and
content provider operational requirements. content provider operational requirements.
MPLS: [I-D.ietf-mpls-base-yang] defines a base model for MPLS MPLS: [I-D.ietf-mpls-base-yang] defines a base model for MPLS
which serves as a base framework for configuring and which serves as a base framework for configuring and
managing an MPLS switching subsystem. It is expected that managing an MPLS switching subsystem. It is expected that
other MPLS technology YANG modules (e.g., MPLS LSP Static, other MPLS technology YANG modules (e.g., MPLS LSP Static,
LDP or RSVP-TE models) will augment the MPLS base YANG LDP, or RSVP-TE models) will augment the MPLS base YANG
module. module.
QoS: [I-D.ietf-rtgwg-qos-model] describes a YANG module of QoS: [I-D.ietf-rtgwg-qos-model] describes a YANG module of
Differentiated Services for configuration and operations. Differentiated Services for configuration and operations.
ACL: Access Control List (ACL) is one of the basic elements ACL: Access Control List (ACL) is one of the basic elements
used to configure device forwarding behavior. It is used used to configure device forwarding behavior. It is used
in many networking technologies such as Policy Based in many networking technologies such as Policy Based
Routing, Firewalls, etc. [RFC8519] describes a data model Routing, Firewalls, etc. [RFC8519] describes a data model
of ACL basic building blocks. of ACL basic building blocks.
NAT: For the sake of network automation and the need for NAT: For the sake of network automation and the need for
programming Network Address Translation (NAT) function in programming Network Address Translation (NAT) function in
particular, a data model for configuring and managing the particular, a data model for configuring and managing the
NAT is essential. [RFC8512] defines a YANG module for the NAT is essential.
NAT function covering a variety of NAT flavors such as
Network Address Translation from IPv4 to IPv4 (NAT44), [RFC8512] defines a YANG module for the NAT function
Network Address and Protocol Translation from IPv6 Clients covering a variety of NAT flavors such as Network Address
to IPv4 Servers (NAT64), customer-side translator (CLAT), Translation from IPv4 to IPv4 (NAT44), Network Address and
Stateless IP/ICMP Translation (SIIT), Explicit Address Protocol Translation from IPv6 Clients to IPv4 Servers
Mappings (EAM) for SIIT, IPv6-to-IPv6 Network Prefix (NAT64), customer-side translator (CLAT), Stateless IP/
Translation (NPTv6), and Destination NAT. [RFC8513] ICMP Translation (SIIT), Explicit Address Mappings (EAM)
specifies a DS-Lite YANG module. for SIIT, IPv6-to-IPv6 Network Prefix Translation (NPTv6),
and Destination NAT.
[RFC8513] specifies a DS-Lite YANG module.
Stateless Address Sharing: [RFC8676] specifies a YANG module for A+P Stateless Address Sharing: [RFC8676] specifies a YANG module for A+P
address sharing, including Lightweight 4over6, Mapping of address sharing, including Lightweight 4over6, Mapping of
Address and Port with Encapsulation (MAP-E), and Mapping Address and Port with Encapsulation (MAP-E), and Mapping
of Address and Port using Translation (MAP-T) softwire of Address and Port using Translation (MAP-T) softwire
mechanisms. mechanisms.
Multicast: [I-D.ietf-pim-yang] defines a YANG module that can be used Multicast: [I-D.ietf-pim-yang] defines a YANG module that can be used
to configure and manage Protocol Independent Multicast to configure and manage Protocol Independent Multicast
(PIM) devices. (PIM) devices.
RFC8652 defines a YANG module that can be used to [RFC8652] defines a YANG module that can be used to
configure and manage Internet Group Management Protocol configure and manage Internet Group Management Protocol
(IGMP) and Multicast Listener Discovery (MLD) devices. (IGMP) and Multicast Listener Discovery (MLD) devices.
[I-D.ietf-pim-igmp-mld-snooping-yang] defines a YANG [I-D.ietf-pim-igmp-mld-snooping-yang] defines a YANG
module that can be used to configure and manage Internet module that can be used to configure and manage Internet
Group Management Protocol (IGMP) and Multicast Listener Group Management Protocol (IGMP) and Multicast Listener
Discovery (MLD) Snooping devices. Discovery (MLD) Snooping devices.
[I-D.ietf-bess-mvpn-yang] defines a YANG data model to
configure and manage Multicast in MPLS/BGP IP VPNs
(MVPNs).
EVPN: [I-D.ietf-bess-evpn-yang] defines a YANG module for EVPN: [I-D.ietf-bess-evpn-yang] defines a YANG module for
Ethernet VPN services. The model is agnostic of the Ethernet VPN services. The model is agnostic of the
underlay. It applies to MPLS as well as to VxLAN underlay. It applies to MPLS as well as to VxLAN
encapsulation. The module is also agnostic to the encapsulation. The module is also agnostic to the
services, including E-LAN, E-LINE, and E-TREE services. services, including E-LAN, E-LINE, and E-TREE services.
L3VPN: [I-D.ietf-bess-l3vpn-yang] defines a YANG module that can L3VPN: [I-D.ietf-bess-l3vpn-yang] defines a YANG module that can
be used to configure and manage BGP L3VPNs [RFC4364]. It be used to configure and manage BGP L3VPNs [RFC4364]. It
contains VRF specific parameters as well as BGP specific contains VRF specific parameters as well as BGP specific
parameters applicable for L3VPNs. parameters applicable for L3VPNs.
skipping to change at page 37, line 42 skipping to change at page 40, line 7
SR/SRv6: [I-D.ietf-spring-sr-yang] a YANG module for segment SR/SRv6: [I-D.ietf-spring-sr-yang] a YANG module for segment
routing configuration and operation. routing configuration and operation.
Core Routing: [RFC8349] defines the core routing data model, which Core Routing: [RFC8349] defines the core routing data model, which
is intended as a basis for future data model development is intended as a basis for future data model development
covering more-sophisticated routing systems. It is covering more-sophisticated routing systems. It is
expected that other Routing technology YANG modules (e.g., expected that other Routing technology YANG modules (e.g.,
VRRP, RIP, ISIS, OSPF models) will augment the Core VRRP, RIP, ISIS, OSPF models) will augment the Core
Routing base YANG module. Routing base YANG module.
PM: PM: [I-D.ietf-ippm-twamp-yang] defines a data model for client
[I-D.ietf-ippm-twamp-yang] defines a data model for client
and server implementations of the Two-Way Active and server implementations of the Two-Way Active
Measurement Protocol (TWAMP). Measurement Protocol (TWAMP).
[I-D.ietf-ippm-stamp-yang] defines the data model for [I-D.ietf-ippm-stamp-yang] defines the data model for
implementations of Session-Sender and Session-Reflector implementations of Session-Sender and Session-Reflector
for Simple Two-way Active Measurement Protocol (STAMP) for Simple Two-way Active Measurement Protocol (STAMP)
mode using YANG. mode using YANG.
[RFC8194] defines a data model for Large-Scale Measurement [RFC8194] defines a data model for Large-Scale Measurement
Platforms (LMAPs). Platforms (LMAPs).
skipping to change at page 38, line 38 skipping to change at page 40, line 47
Telefonica I+D Telefonica I+D
Spain Spain
Email: diego.r.lopez@telefonica.com Email: diego.r.lopez@telefonica.com
Chongfeng Xie Chongfeng Xie
China Telecom China Telecom
Beijing Beijing
China China
Email: xiechf.bri@chinatelecom.cn Email: xiechf@chinatelecom.cn
Liang Geng Liang Geng
China Mobile China Mobile
Email: gengliang@chinamobile.com Email: gengliang@chinamobile.com
 End of changes. 103 change blocks. 
412 lines changed or deleted 530 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/