draft-ietf-opsawg-model-automation-framework-01.txt   draft-ietf-opsawg-model-automation-framework-02.txt 
Networking Working Group 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: August 29, 2020 Orange Expires: September 18, 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
February 26, 2020 March 17, 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-01 draft-ietf-opsawg-model-automation-framework-02
Abstract Abstract
Data models for service and network management provides a Data models for service and network management provides a
programmatic approach for representing (virtual) services or networks programmatic approach for representing (virtual) services or networks
and deriving (1) configuration information that will be communicated and deriving (1) configuration information that will be communicated
to network and service components that are used to build and deliver to network and service components that are used to build and deliver
the service and (2) state information that will be monitored and the service and (2) state information that will be monitored and
tracked. Indeed, data models can be used during various phases of tracked. Indeed, data models can be used during various phases of
the service and network management life cycle, such as service the service and network management life cycle, such as service
skipping to change at page 2, line 12 skipping to change at page 2, line 12
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 August 29, 2020. This Internet-Draft will expire on September 18, 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
skipping to change at page 3, line 5 skipping to change at page 3, line 5
4.1.4. Service Diagnosis . . . . . . . . . . . . . . . . . . 13 4.1.4. Service Diagnosis . . . . . . . . . . . . . . . . . . 13
4.1.5. Service Decommission . . . . . . . . . . . . . . . . 13 4.1.5. Service Decommission . . . . . . . . . . . . . . . . 13
4.2. Service Fullfillment Management Procedure . . . . . . . . 13 4.2. Service Fullfillment Management Procedure . . . . . . . . 13
4.2.1. Intended Configuration Provision . . . . . . . . . . 13 4.2.1. Intended Configuration Provision . . . . . . . . . . 13
4.2.2. Configuration Validation . . . . . . . . . . . . . . 14 4.2.2. Configuration Validation . . . . . . . . . . . . . . 14
4.2.3. Performance Monitoring/Model-driven Telemetry . . . . 14 4.2.3. Performance Monitoring/Model-driven Telemetry . . . . 14
4.2.4. Fault Diagnostic . . . . . . . . . . . . . . . . . . 15 4.2.4. Fault Diagnostic . . . . . . . . . . . . . . . . . . 15
4.3. Multi-layer/Multi-domain Service Mapping . . . . . . . . 15 4.3. Multi-layer/Multi-domain Service Mapping . . . . . . . . 15
4.4. Service Decomposing . . . . . . . . . . . . . . . . . . . 15 4.4. Service Decomposing . . . . . . . . . . . . . . . . . . . 15
5. YANG Data Model Integration Examples . . . . . . . . . . . . 15 5. YANG Data Model Integration Examples . . . . . . . . . . . . 16
5.1. L3VPN Service Delivery . . . . . . . . . . . . . . . . . 15 5.1. L3VPN Service Delivery . . . . . . . . . . . . . . . . . 16
5.2. VN Lifecycle Management . . . . . . . . . . . . . . . . . 17 5.2. VN Lifecycle Management . . . . . . . . . . . . . . . . . 17
5.3. Event-based Telemetry in the Device Self management . . . 18 5.3. Event-based Telemetry in the Device Self Management . . . 18
6. Security Considerations . . . . . . . . . . . . . . . . . . . 19 6. Security Considerations . . . . . . . . . . . . . . . . . . . 19
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
10.1. Normative References . . . . . . . . . . . . . . . . . . 20 10.1. Normative References . . . . . . . . . . . . . . . . . . 20
10.2. Informative References . . . . . . . . . . . . . . . . . 21 10.2. Informative References . . . . . . . . . . . . . . . . . 21
Appendix A. Layered YANG Modules Example Overview . . . . . . . 29 Appendix A. Layered YANG Modules Examples Overview . . . . . . . 27
A.1. Service Models: Definition and Samples . . . . . . . . . 29 A.1. Service Models: Definition and Samples . . . . . . . . . 27
A.2. Network Models: Definitions and Samples . . . . . . . . . 30 A.2. Network Models: Samples . . . . . . . . . . . . . . . . . 28
A.3. Device Models: Definitions and Samples . . . . . . . . . 32 A.3. Device Models: Samples . . . . . . . . . . . . . . . . . 30
A.3.1. Model Composition . . . . . . . . . . . . . . . . . . 33 A.3.1. Model Composition . . . . . . . . . . . . . . . . . . 31
A.3.2. Device Models: Definitions and Samples . . . . . . . 34 A.3.2. Device Models: Samples . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35
1. Introduction 1. Introduction
The service management system usually comprises service activation/ The service management system usually comprises 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 order
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
skipping to change at page 4, line 16 skipping to change at page 4, line 16
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-requirement-derived dynamic resource o Techniques used by service-derived dynamic resource allocation and
allocation and policy enforcement schemes, so that networks can be policy enforcement schemes, so that networks can be programmed
programmed accordingly. accordingly.
o Dynamic feedback mechanisms that are meant to assess how o Dynamic feedback mechanisms that are meant to assess how
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 perspective. service fulfillment and assurance perspective.
Models are key for each of these technical items. Service and Models are key for each of these technical items. Service and
network management automation is an important step to improve the network management automation is an important step to improve the
agility of network operations. Models are also important to ease agility of network operations. Models are also important to ease
integrating multi-vendor solutions. integrating multi-vendor solutions.
skipping to change at page 5, line 6 skipping to change at page 5, line 6
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 provider perspective
irrespective of the origin of a data module; it can accommodate even irrespective of the origin of a data module; it can accommodate even
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 to be exhaustive. approach (Section 5), but it does not claim nor aim to be exhaustive.
2. Terminology 2. 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
skipping to change at page 5, line 48 skipping to change at page 5, line 48
[RFC8519]). [RFC8519]).
3. Architectural Concepts & Goals 3. Architectural Concepts & Goals
3.1. Data Models: Layering and Representation 3.1. Data Models: Layering and Representation
As described in [RFC8199], layering of modules allows for better As described in [RFC8199], layering of modules allows for better
reusability of lower-layer modules by higher-level modules while reusability of lower-layer modules by higher-level modules while
limiting duplication of features across layers. limiting duplication of features across layers.
The data modules can be classified into Service, Network, and Device The 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., L3VPN), which can be mapped to higher level network services (e.g., L3VPN), which can be mapped to
network technology-specific modules at lower layers (e.g., tunnel, network technology-specific modules at lower layers (e.g., tunnel,
routing, QoS, security). For example, the service level can be used routing, QoS, security). For example, the service level can be used
to characterise the network service(s) to be ensured between service to 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 the communication scope (pipe, hose,
skipping to change at page 7, line 35 skipping to change at page 7, line 35
* Statistics on aggregate traffic to adjust capacity * Statistics on aggregate traffic to adjust capacity
* Failures * Failures
* Planned maintenance operations * Planned maintenance operations
* Triggered by thresholds * Triggered by thresholds
Figure 2: Sample Attributes Captured in a Service Model Figure 2: Sample Attributes Captured in a Service Model
Network Models are mainly network resource-facing modules and Network Models are mainly network resource-facing modules and
describe various aspects of a network infrastructure, including describe various aspects of a network infrastructure, including
devices and their subsystems, and relevant protocols operating at the devices and their subsystems, and relevant protocols operating at the
link and network layers across multiple devices (e.g., Network link and network layers across multiple devices (e.g., network
topology and traffic-engineering Tunnel modules). topology and traffic-engineering tunnel modules).
Device (and function) Models usually follow a bottom-up approach and Device (and function) Models usually follow a bottom-up approach and
are mostly technology-specific modules used to realize a service are mostly technology-specific modules used to realize a service
(e.g., BGP, NAT). (e.g., BGP, NAT).
Each level maintains a view of the supported YANG modules provided by Each level maintains a view of the supported YANG modules provided by
low-levels (see for example, Appendix A). low-levels (see for example, Appendix A).
Figure 3 illustrates the overall layering model. Figure 3 illustrates the overall layering model.
skipping to change at page 8, line 41 skipping to change at page 8, line 41
| | | |
| | | |
| +-----------------------+ | | +-----------------------+ |
| | 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 an operator to expose its services to
its customers. Exposing such models allows to automate the its customers. Exposing such models allows to automate the
activation and the delivery of service orders. One or more activation of service orders and thus the service delivery. One or
monolithic Service Models can be used in the context of a composite more monolithic Service Models can be used in the context of a
service activation request (e.g., delivery of a caching composite service activation request (e.g., delivery of a caching
infrastructure over a VPN). Such modules are used to feed a infrastructure over a VPN). Such modules are used to feed a
decision-making intelligence to adequately accommodate customer's decision-making intelligence to adequately accommodate customer's
needs. needs.
Such modules may also be used jointly with services that require Such modules may also 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 DDoS defined by the DOTS WG to dynamically trigger requests to handle DDoS
attacks [I-D.ietf-dots-signal-channel][I-D.ietf-dots-data-channel]. attacks [I-D.ietf-dots-signal-channel][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
skipping to change at page 10, line 23 skipping to change at page 10, line 23
e.g., policies that contain conditions can trigger the generation and e.g., policies that contain conditions can trigger the generation and
pushing of new telemetry data. 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 lead to the The architectural considerations described in Section 3 led to the
architecture described in this section and illustrated in Figure 4. architecture described in this section and illustrated in Figure 4.
+------------------+ +------------------+
Service level | | Service level | |
----------- V | ----------- V |
E2E E2E E2E E2E E2E E2E E2E E2E
Service -- Service --------> Service --->Service ---+ Service -- Service --------> Service --->Service ---+
Exposure Creation ^ Optimization | Diagnosis | Exposure Creation ^ Optimization | Diagnosis |
/Modification | | | /Modification | | |
| |Diff | V | |Diff | V
skipping to change at page 14, line 21 skipping to change at page 14, line 21
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 the document, as well as routing policies associated listed in the document, as well as routing policies associated
with those protocols. with those protocols.
o Multicast Support o Multicast Support
o NAT or address sharing o Address sharing
o Security function o Security function
This specific configuration models can be used to configure PE and CE This specific configuration models can be used to configure Provider
devices within the site, e.g., a BGP policy model can be used to Edge (PE) and Customer Edge (CE) devices within the site, e.g., a BGP
establish VPN membership between sites and VPN Service Topology. policy model can be used to establish VPN membership between sites
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. For example, a customer and ensure the configuration take effect. For example, a customer
creates an interface "et-0/0/0" but the interface does not physically creates an interface "et-0/0/0" but the interface does not physically
exist at this point, then configuration data appears in the exist at this point, then configuration data appears in the
<intended> status but does not appear in <operational> datastore. <intended> status but does not appear in <operational> datastore.
4.2.3. Performance Monitoring/Model-driven Telemetry 4.2.3. Performance Monitoring/Model-driven Telemetry
skipping to change at page 15, line 8 skipping to change at page 15, line 10
the current status of the network. the current status of the network.
The management system should subscribe to updates of a YANG datastore The management system should subscribe to updates of a YANG datastore
in all the network devices for performance monitoring purpose and in all the network devices for performance monitoring purpose and
build full topological visibility to the network by aggregating and build full topological visibility to the network by aggregating and
filtering these operational state from different sources. filtering these operational state from different sources.
4.2.4. Fault Diagnostic 4.2.4. Fault Diagnostic
When configuration is in effect in the device, some device may be When configuration is in effect in the device, some device may be
misconfigured(e.g.,device links are not consistent on both sides of mis-configured(e.g.,device links are not consistent on both sides of
the network connection), network resources be misallocated and the network connection), network resources be mis-allocated and
services may be negatively affected without knowing what is going on services may be negatively affected without knowing what is going on
in the network. in the network.
Technology-dependent nodes and RPC commands are defined in Technology-dependent nodes and RPC commands are defined in
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.4can be used to deal with these base model described in Section 4.1.4 can be used to deal with these
challenges. challenges.
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 exchange for fault used to trigger technology specific OAM message exchange for fault
verification and fault isolation,e.g., TRILL Multicast Tree verification and fault isolation,e.g., 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
skipping to change at page 18, line 25 skipping to change at page 18, line 29
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 TEAS VN model and
corresponding TE Tunnel model can be used to subscribe to corresponding TE Tunnel model can be used to subscribe to
performance measurement data and notify all the parameter changes performance measurement data and notify all the parameter changes
and network performance change related to VN topology or Tunnel and network 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).
5.3. Event-based Telemetry in the Device Self management 5.3. Event-based Telemetry in the Device Self Management
+----------------+ +----------------+
| | | |
| Controller | | Controller |
+----------------+ +----------------+
| |
| |
ECA | ECA |
Model| ^ Model| ^
| |Notif | |Notif
skipping to change at page 19, line 10 skipping to change at page 19, line 12
In reference to Figure 7, the following steps are performed to In reference to Figure 7, the following steps are performed to
monitor state changes of managed objects or resource in the device monitor state changes of managed objects or resource in the device
and provide device self management within the network management and provide device self management within the network management
automation architecture defined in this document: 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 send updates only when the value exceeds
a certain threshold for the first time but not again until the a certain threshold for the first time but not again until the
threshold is cleared.), which constitute an event-driven policy threshold is cleared), which constitute an event-driven policy or
or network control logic in the controller. network control logic in the controller.
2. The controller pushes ECA policy to the network device and 2. The controller pushes ECA policy to the network device and
delegate network control logic to the network device. delegate network control logic to the network device.
3. The network device generates ECA script from ECA model and 3. The network device generates ECA script from ECA model and
execute ECA script or network control logic based on Event. execute ECA script or network control logic based on Event.
Event based notification or telemetry can be triggered if a Event based notification or telemetry can be triggered if a
certain condition is satisfied (model driven telemetry operation certain condition is satisfied (model driven telemetry operation
in Section 4.2.3). in Section 4.2.3).
skipping to change at page 21, line 7 skipping to change at page 21, line 7
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
10.2. Informative References 10.2. Informative References
[I-D.arkko-arch-virtualization]
Arkko, J., Tantsura, J., Halpern, J., and B. Varga,
"Considerations on Network Virtualization and Slicing",
draft-arkko-arch-virtualization-01 (work in progress),
March 2018.
[I-D.asechoud-netmod-diffserv-model]
Choudhary, A., Shah, S., Jethanandani, M., Liu, B., and N.
Strahle, "YANG Model for Diffserv", draft-asechoud-netmod-
diffserv-model-03 (work in progress), June 2015.
[I-D.clacla-netmod-model-catalog]
Clarke, J. and B. Claise, "YANG module for
yangcatalog.org", draft-clacla-netmod-model-catalog-03
(work in progress), April 2018.
[I-D.homma-slice-provision-models]
Homma, S., Nishihara, H., Miyasaka, T., Galis, A., OV, V.,
Lopez, D., Contreras, L., Ordonez-Lucena, J., Martinez-
Julia, P., Qiang, L., Rokui, R., Ciavaglia, L., and X.
Foy, "Network Slice Provision Models", draft-homma-slice-
provision-models-02 (work in progress), November 2019.
[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.
skipping to change at page 22, line 5 skipping to change at page 21, line 30
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-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-ccamp-alarm-module]
Vallin, S. and M. Bjorklund, "YANG Alarm Module", draft-
ietf-ccamp-alarm-module-09 (work in progress), April 2019.
[I-D.ietf-ccamp-flexigrid-media-channel-yang]
Madrid, U., Perdices, D., Lopezalvarez, V., Dios, O.,
King, D., Lee, Y., and G. Galimberti, "YANG data model for
Flexi-Grid media-channels", draft-ietf-ccamp-flexigrid-
media-channel-yang-02 (work in progress), March 2019.
[I-D.ietf-ccamp-flexigrid-yang]
Madrid, U., Perdices, D., Lopezalvarez, V., King, D., Lee,
Y., and H. Zheng, "YANG data model for Flexi-Grid Optical
Networks", draft-ietf-ccamp-flexigrid-yang-05 (work in
progress), January 2020.
[I-D.ietf-ccamp-l1csm-yang]
Lee, Y., Lee, K., Zheng, H., Dhody, D., Dios, O., and D.
Ceccarelli, "A YANG Data Model for L1 Connectivity Service
Model (L1CSM)", draft-ietf-ccamp-l1csm-yang-10 (work in
progress), September 2019.
[I-D.ietf-ccamp-mw-yang]
Ahlberg, J., Ye, M., Li, X., Spreafico, D., and M.
Vaupotic, "A YANG Data Model for Microwave Radio Link",
draft-ietf-ccamp-mw-yang-13 (work in progress), November
2018.
[I-D.ietf-ccamp-otn-topo-yang]
Zheng, H., Busi, I., Liu, X., Belotti, S., and O. Dios, "A
YANG Data Model for Optical Transport Network Topology",
draft-ietf-ccamp-otn-topo-yang-09 (work in progress),
November 2019.
[I-D.ietf-ccamp-otn-tunnel-model]
Zheng, H., Busi, I., Belotti, S., Lopezalvarez, V., and Y.
Xu, "OTN Tunnel YANG Model", draft-ietf-ccamp-otn-tunnel-
model-09 (work in progress), November 2019.
[I-D.ietf-ccamp-wson-tunnel-model]
Lee, Y., Zheng, H., Guo, A., Lopezalvarez, V., King, D.,
Yoon, B., and R. Vilata, "A Yang Data Model for WSON
Tunnel", draft-ietf-ccamp-wson-tunnel-model-04 (work in
progress), September 2019.
[I-D.ietf-dots-data-channel] [I-D.ietf-dots-data-channel]
Boucadair, M. and T. Reddy.K, "Distributed Denial-of- Boucadair, M. and T. Reddy.K, "Distributed Denial-of-
Service Open Threat Signaling (DOTS) Data Channel Service Open Threat Signaling (DOTS) Data Channel
Specification", draft-ietf-dots-data-channel-31 (work in Specification", draft-ietf-dots-data-channel-31 (work in
progress), July 2019. progress), July 2019.
[I-D.ietf-dots-signal-channel] [I-D.ietf-dots-signal-channel]
Reddy.K, T., Boucadair, M., Patil, P., Mortensen, A., and Reddy.K, T., Boucadair, M., Patil, P., Mortensen, A., and
N. Teague, "Distributed Denial-of-Service Open Threat N. Teague, "Distributed Denial-of-Service Open Threat
Signaling (DOTS) Signal Channel Specification", draft- Signaling (DOTS) Signal Channel Specification", draft-
ietf-dots-signal-channel-41 (work in progress), January ietf-dots-signal-channel-41 (work in progress), January
2020. 2020.
[I-D.ietf-i2rs-yang-l2-network-topology]
Dong, J., Wei, X., WU, Q., Boucadair, M., and A. Liu, "A
YANG Data Model for Layer-2 Network Topologies", draft-
ietf-i2rs-yang-l2-network-topology-13 (work in progress),
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-07 (work in progress), October 2019. bgp-model-08 (work in progress), February 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-12 (work in progress), February 2020. yang-14 (work in progress), March 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-09 (work in progress), January pim-igmp-mld-snooping-yang-09 (work in progress), January
2020. 2020.
[I-D.ietf-pim-igmp-mld-yang]
Liu, X., Guo, F., Sivakumar, M., McAllister, P., and A.
Peter, "A YANG Data Model for Internet Group Management
Protocol (IGMP) and Multicast Listener Discovery (MLD)",
draft-ietf-pim-igmp-mld-yang-15 (work in progress), June
2019.
[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-08 (work in progress), January 2020. policy-model-09 (work in progress), March 2020.
[I-D.ietf-softwire-iftunnel]
Boucadair, M., Farrer, I., and R. Asati, "Tunnel Interface
Types YANG Module", draft-ietf-softwire-iftunnel-07 (work
in progress), June 2019.
[I-D.ietf-softwire-yang] [I-D.ietf-rtgwg-qos-model]
Farrer, I. and M. Boucadair, "YANG Modules for IPv4-in- Choudhary, A., Jethanandani, M., Strahle, N., Aries, E.,
IPv6 Address plus Port (A+P) Softwires", draft-ietf- and I. Chen, "YANG Model for QoS", draft-ietf-rtgwg-qos-
softwire-yang-16 (work in progress), January 2019. model-00 (work in progress), October 2019.
[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.
[I-D.ietf-supa-generic-policy-data-model] [I-D.ietf-supa-generic-policy-data-model]
Halpern, J. and J. Strassner, "Generic Policy Data Model Halpern, J. and J. Strassner, "Generic Policy Data Model
for Simplified Use of Policy Abstractions (SUPA)", draft- for Simplified Use of Policy Abstractions (SUPA)", draft-
ietf-supa-generic-policy-data-model-04 (work in progress), ietf-supa-generic-policy-data-model-04 (work in progress),
June 2017. June 2017.
[I-D.ietf-teas-actn-pm-telemetry-autonomics] [I-D.ietf-teas-actn-pm-telemetry-autonomics]
Lee, Y., Dhody, D., Karunanithi, S., Vilata, R., King, D., Lee, Y., Dhody, D., Karunanithi, S., Vilata, R., King, D.,
and D. Ceccarelli, "YANG models for VN/TE Performance and D. Ceccarelli, "YANG models for VN/TE Performance
Monitoring Telemetry and Scaling Intent Autonomics", Monitoring Telemetry and Scaling Intent Autonomics",
draft-ietf-teas-actn-pm-telemetry-autonomics-01 (work in draft-ietf-teas-actn-pm-telemetry-autonomics-02 (work in
progress), October 2019. 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-07 (work in progress), October 2019. teas-actn-vn-yang-08 (work in progress), March 2020.
[I-D.ietf-teas-sf-aware-topo-model]
Bryskin, I., Liu, X., Lee, Y., Guichard, J., Contreras,
L., Ceccarelli, D., and J. Tantsura, "SF Aware TE Topology
YANG Model", draft-ietf-teas-sf-aware-topo-model-04 (work
in progress), November 2019.
[I-D.ietf-teas-te-service-mapping-yang]
Lee, Y., Dhody, D., Fioccola, G., WU, Q., Ceccarelli, D.,
and J. Tantsura, "Traffic Engineering (TE) and Service
Mapping Yang Model", draft-ietf-teas-te-service-mapping-
yang-02 (work in progress), September 2019.
[I-D.ietf-teas-yang-l3-te-topo]
Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
O. Dios, "YANG Data Model for Layer 3 TE Topologies",
draft-ietf-teas-yang-l3-te-topo-05 (work in progress),
July 2019.
[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-08 (work in
progress), December 2019. progress), December 2019.
[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-07 (work in progress), July draft-ietf-teas-yang-rsvp-te-08 (work in progress), March
2019. 2020.
[I-D.ietf-teas-yang-sr-te-topo]
Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
S. Litkowski, "YANG Data Model for SR and SR TE
Topologies", draft-ietf-teas-yang-sr-te-topo-06 (work in
progress), November 2019.
[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
Interfaces", draft-ietf-teas-yang-te-22 (work in Interfaces", draft-ietf-teas-yang-te-23 (work in
progress), November 2019. progress), March 2020.
[I-D.ietf-teas-yang-te-topo] [I-D.ietf-teas-yang-te-topo]
Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
O. Dios, "YANG Data Model for Traffic Engineering (TE) O. Dios, "YANG Data Model for Traffic Engineering (TE)
Topologies", draft-ietf-teas-yang-te-topo-22 (work in Topologies", draft-ietf-teas-yang-te-topo-22 (work in
progress), June 2019. progress), June 2019.
[I-D.ietf-trill-yang-oam] [I-D.ietf-trill-yang-oam]
Kumar, D., Senevirathne, T., Finn, N., Salam, S., Xia, L., Kumar, D., Senevirathne, T., Finn, N., Salam, S., Xia, L.,
and H. Weiguo, "YANG Data Model for TRILL Operations, and H. Weiguo, "YANG Data Model for TRILL Operations,
skipping to change at page 29, line 19 skipping to change at page 27, line 12
RFC 8532, DOI 10.17487/RFC8532, April 2019, RFC 8532, DOI 10.17487/RFC8532, April 2019,
<https://www.rfc-editor.org/info/rfc8532>. <https://www.rfc-editor.org/info/rfc8532>.
[RFC8533] Kumar, D., Wang, M., Wu, Q., Ed., Rahman, R., and S. [RFC8533] Kumar, D., Wang, M., Wu, Q., Ed., Rahman, R., and S.
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>.
Appendix A. Layered YANG Modules Example Overview [RFC8675] Boucadair, M., Farrer, I., and R. Asati, "A YANG Data
Model for Tunnel Interface Types", RFC 8675,
DOI 10.17487/RFC8675, November 2019,
<https://www.rfc-editor.org/info/rfc8675>.
It is not the intent of this document to provide an inventory of [RFC8676] Farrer, I., Ed. and M. Boucadair, Ed., "YANG Modules for
IPv4-in-IPv6 Address plus Port (A+P) Softwires", RFC 8676,
DOI 10.17487/RFC8676, November 2019,
<https://www.rfc-editor.org/info/rfc8676>.
Appendix A. Layered YANG Modules Examples Overview
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 Quality Of Service (QoS), performance, and
availability, for example) to properly forward traffic to the said availability, for example) to properly forward traffic to the said
"Destination" [RFC7297]. "Destination" [RFC7297].
For example: For example:
o 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 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 VN model [I-D.ietf-teas-actn-vn-yang]provides a YANG data model o The Virtual Network (VN) model [I-D.ietf-teas-actn-vn-yang]
generally applicable to any mode of Virtual Network (VN) provides a YANG data model applicable to any mode of VN operation.
operation.
A.2. Network Models: Definitions and Samples A.2. Network Models: Samples
Figure 8 depicts a set of Network models such as topology models or Figure 8 depicts a set of Network models such as topology models or
tunnel models: tunnel models:
| | | |
Topo YANG modules | Tunnel YANG modules | Topo YANG modules | Tunnel YANG modules |
------------------------------------------------| ------------------------------------------------|
+------------+ | | +------------+ | |
|Network Top | | +------+ +-----------+ | |Network Top | | +------+ +-----------+ |
| Model | | |Other | | TE Tunnel | | | Model | | |Other | | TE Tunnel | |
skipping to change at page 30, line 38 skipping to change at page 28, line 38
+--------+ | +--------+ |
Figure 8: Sample Resource Facing Network Models Figure 8: Sample Resource Facing Network Models
Topology YANG module Examples: Topology YANG module Examples:
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 L3 Topology Models
[RFC8346] defines a data model for representing and manipulating [RFC8346] defines a data model for representing and manipulating
L3 Topologies. This model is extended from the network topology Layer 3 topologies. This model is extended from the network
model defined in [RFC8345] with L3 topologies specifics. topology model defined in [RFC8345] with L3 topologies specifics.
o L2 Topology Models o L2 Topology Models
[I.D-ietf-i2rs-yang-l2-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 L2 topologies. This model is
extended from the network topology model defined in [RFC8345] with extended from the network topology model defined in [RFC8345] with
L2 topologies specifics. Layer 2 topologies specifics.
Tunnel YANG module Examples: Tunnel YANG module Examples:
o Tunnel identities [I-D.ietf-softwire-iftunnel] to ease o Tunnel identities to ease manipulating extensions to specific
manipulating extensions to specific tunnels. 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 SR 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 Segment Routing (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 Network Models: Other Network Models:
o Path Computation API Model o Path Computation API Model:
[I.D-ietf-teas-path-computation] YANG module for a stateless RPC [I-D.ietf-teas-yang-path-computation] YANG module for a stateless
which complements the stateful solution defined in [I.D-ietf-teas- RPC which complements the stateful solution defined in
yang-te]. [I-D.ietf-teas-yang-te].
o OAM Models (including Fault Management (FM) and Performance o OAM Models (including Fault Management (FM) and Performance
Monitoring) Monitoring):
[RFC8532] defines a base YANG module for the management of OAM [RFC8532] defines a base YANG module for the management of OAM
protocols that use Connectionless Communications. [RFC8533] protocols that use Connectionless Communications. [RFC8533]
defines a retrieval method YANG module for connectionless OAM defines a retrieval method YANG module for connectionless OAM
protocols. [RFC8531] defines a base YANG module for connection protocols. [RFC8531] defines a base YANG module for connection
oriented OAM protocols. These three models are intended to oriented OAM protocols. These three models are intended to
provide consistent reporting, configuration and representation for provide consistent reporting, configuration, and representation
connection-less OAM and Connection oriented OAM separately. for connection-less OAM and Connection oriented OAM separately.
Alarm monitoring is a fundamental part of monitoring the network. Alarm monitoring is a fundamental part of monitoring the network.
Raw alarms from devices do not always tell the status of the Raw alarms from devices do not always tell the status of the
network services or necessarily point to the root cause. [I.D- network services or necessarily point to the root cause. RFC8632
ietf-ccamp-alarm-module] defines a YANG module for alarm defines a YANG module for alarm management.
management.
o Generic Policy Model o Generic Policy Model:
The Simplified Use of Policy Abstractions (SUPA) policy-based The Simplified Use of Policy Abstractions (SUPA) policy-based
management framework [RFC8328] defines base YANG modules management framework [RFC8328] defines base YANG modules
[I-D.ietf-supa-generic-policy-data-model]to encode policy. These [I-D.ietf-supa-generic-policy-data-model] to encode policy. These
models point to device-, technology-, and service-specific YANG models point to other device-, technology-, and service-specific
modules developed elsewhere. Policy rules within an operator's YANG modules. Policy rules within an operator's environment can
environment can be used to express high-level, possibly network- be used to express high-level, possibly network-wide, policies to
wide, policies to a network management function (within a a network management function (within a controller, an
controller, an orchestrator, or a network element). The network orchestrator, or a network element). The network management
management function can then control the configuration and/or function can then control the configuration and/or monitoring of
monitoring of network elements and services. This document network elements and services. This document describes the SUPA
describes the SUPA basic framework, its elements, and interfaces. basic framework, its elements, and interfaces.
A.3. Device Models: Definitions and Samples A.3. Device Models: Samples
Network Element models (Figure 9) are used to describe how a service Network Element models (Figure 9) 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. The infrastructures) that are involved in the service delivery. Figure 9
following figure uses IETF defined models as an example. uses IETF-defined models as an example.
+----------------+ +----------------+
--|Device Model | --|Device Model |
| +----------------+ | +----------------+
| +------------------+ | +------------------+
+---------------+ | |Logical Network | +---------------+ | |Logical Network |
| | --| Element Mode | | | --| Element Mode |
| Architecture | | +------------------+ | Architecture | | +------------------+
| | | +----------------------+ | | | +----------------------+
+-------+-------+ --|Network Instance Mode | +-------+-------+ --|Network Instance Mode |
skipping to change at page 33, line 50 skipping to change at page 31, line 50
| +-------+ | +-------+
--|OSPF-SR| --|OSPF-SR|
+-------+ +-------+
Figure 9: Network Element Modules Overview Figure 9: 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
represented as an example YANG module, with all of the related represented as an example YANG module, with all of the related
component models logically organized in a way that is component models logically organized in a way that is
operationally intuitive, but this model is not expected to be operationally intuitive, but this model is not expected to be
implemented. implemented.
o Logical Network Element Model o Logical Network Element Model
[RFC8530] defines a logical network element module which can be [RFC8530] defines a logical network element module which can be
skipping to change at page 34, line 38 skipping to change at page 32, line 38
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)
schema. schema.
That capability does not cover design time. That capability does not cover design time.
A.3.2. Device Models: Definitions and Samples A.3.2. Device Models: Samples
BGP: [I-D.ietf-idr-bgp-yang-model] defines a YANG module for The following provides an overview of some device models that can be
used within a network. This list is not comprehensive.
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.asechoud-netmod-diffserv-model] describes a YANG QoS: [I-D.ietf-rtgwg-qos-model] describes a YANG module of
module of Differentiated Services for configuration and Differentiated Services for configuration and operations.
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 Access Control List (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. [RFC8512] defines a YANG module for the
NAT function covering a variety of NAT flavors such as NAT function covering a variety of NAT flavors such as
Network Address Translation from IPv4 to IPv4 (NAT44), Network Address Translation from IPv4 to IPv4 (NAT44),
Network Address and Protocol Translation from IPv6 Clients Network Address and Protocol Translation from IPv6 Clients
to IPv4 Servers (NAT64), customer-side translator (CLAT), to IPv4 Servers (NAT64), customer-side translator (CLAT),
Stateless IP/ICMP Translation (SIIT), Explicit Address Stateless IP/ICMP Translation (SIIT), Explicit Address
Mappings (EAM) for SIIT, IPv6-to-IPv6 Network Prefix Mappings (EAM) for SIIT, IPv6-to-IPv6 Network Prefix
Translation (NPTv6), and Destination NAT. [RFC8513] Translation (NPTv6), and Destination NAT. [RFC8513]
specifies a YANG module for the DS-Lite AFTR. specifies a DS-Lite YANG module.
Stateless Address Sharing: [I-D.ietf-softwire-yang] specifies a YANG Stateless Address Sharing: [RFC8676] specifies a YANG module for A+P
module for A+P address sharing, including Lightweight address sharing, including Lightweight 4over6, Mapping of
4over6, Mapping of Address and Port with Encapsulation Address and Port with Encapsulation (MAP-E), and Mapping
(MAP-E), and Mapping of Address and Port using Translation of Address and Port using Translation (MAP-T) softwire
(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. [I-D.ietf-pim-igmp-mld-yang] defines a (PIM) devices.
YANG module that can be used to configure and manage
Internet Group Management Protocol (IGMP) and Multicast RFC8652 defines a YANG module that can be used to
Listener Discovery (MLD) devices. [I-D.ietf-pim-igmp-mld-
snooping-yang] 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) Snooping (IGMP) and Multicast Listener Discovery (MLD) devices.
devices.
[I-D.ietf-pim-igmp-mld-snooping-yang] defines a YANG
module that can be used to configure and manage Internet
Group Management Protocol (IGMP) and Multicast Listener
Discovery (MLD) Snooping devices.
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 apply to MPLS as well as to VxLAN underlay. It applies to MPLS as well as to VxLAN
encapsulation. The model is also agnostic of the services encapsulation. The module is also agnostic to the
including E-LAN, E-LINE and E-TREE services. This services, including E-LAN, E-LINE, and E-TREE services.
document mainly focuses on EVPN and Ethernet-Segment
instance framework.
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.
L2VPN: [I-D.ietf-bess-l2vpn-yang] defines a YANG module for MPLS L2VPN: [I-D.ietf-bess-l2vpn-yang] defines a YANG module for MPLS
based Layer 2 VPN services (L2VPN) [RFC4664] and includes based Layer 2 VPN services (L2VPN) [RFC4664] and includes
switching between the local attachment circuits. The switching between the local attachment circuits. The
L2VPN model covers point-to-point VPWS and Multipoint VPLS L2VPN model covers point-to-point VPWS and Multipoint VPLS
services. These services use signaling of Pseudowires services. These services use signaling of Pseudowires
across MPLS networks using LDP [RFC8077][RFC4762] or BGP across MPLS networks using LDP [RFC8077][RFC4762] or BGP
[RFC4761]. [RFC4761].
Routing Policy: [I-D.ietf-rtgwg-policy-model] defines a YANG module Routing Policy: [I-D.ietf-rtgwg-policy-model] defines a YANG module
for configuring and managing routing policies in a vendor- for configuring and managing routing policies based on
neutral way and based on actual operational practice. The operational practice. The module provides a generic
model provides a generic policy framework which can be policy framework which can be augmented with protocol-
augmented with protocol-specific policy configuration. specific policy configuration.
BFD: [I-D.ietf-bfd-yang]defines a YANG module that can be used BFD: Bidirectional Forwarding Detection (BFD) [RFC5880] is a
to configure and manage Bidirectional Forwarding Detection network protocol which is used for liveness detection of
(BFD) [RFC5880]. BFD is a network protocol which is used arbitrary paths between systems. [I-D.ietf-bfd-yang]
for liveness detection of arbitrary paths between systems. defines a YANG module that can be used to configure and
manage BFD.
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. [I-D.raza-spring- routing configuration and operation.
srv6-yang] defines a YANG module for Segment Routing IPv6
(SRv6) base. The model serves as a base framework for
configuring and managing an SRv6 subsystem and expected to
be augmented by other SRv6 technology models accordingly.
Core Routing: [RFC8349] defines the core routing data model, which 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).
Authors' Addresses Authors' Addresses
Qin Wu (editor) Qin Wu (editor)
 End of changes. 79 change blocks. 
246 lines changed or deleted 156 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/