A Framework for Automating Service and Network Management with YANG
draft-ietf-opsawg-model-automation-framework-09
The information below is for an old version of the document.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8969.
|
|
---|---|---|---|
Authors | Qin Wu , Mohamed Boucadair , Diego Lopez , Chongfeng Xie , Liang Geng | ||
Last updated | 2020-10-23 | ||
Replaces | draft-wu-model-driven-management-virtualization | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews |
TSVART Last Call review
(of
-06)
by Tommy Pauly
Ready w/issues
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Adrian Farrel | ||
Shepherd write-up | Show Last changed 2020-06-16 | ||
IESG | IESG state | Became RFC 8969 (Informational) | |
Consensus boilerplate | Yes | ||
Telechat date | (None) | ||
Responsible AD | Robert Wilton | ||
Send notices to | Adrian Farrel <adrian@olddog.co.uk> | ||
IANA | IANA review state | IANA OK - No Actions Needed |
draft-ietf-opsawg-model-automation-framework-09
[I-D.ietf-spring-sr-yang] Litkowski, S., Qu, Y., Lindem, A., Sarkar, P., and J. Tantsura, "YANG Data Model for Segment Routing", draft- ietf-spring-sr-yang-22 (work in progress), August 2020. [I-D.ietf-teas-actn-pm-telemetry-autonomics] Lee, Y., Dhody, D., Karunanithi, S., Vilata, R., King, D., and D. Ceccarelli, "YANG models for VN/TE Performance Monitoring Telemetry and Scaling Intent Autonomics", draft-ietf-teas-actn-pm-telemetry-autonomics-03 (work in progress), July 2020. [I-D.ietf-teas-actn-vn-yang] Lee, Y., Dhody, D., Ceccarelli, D., Bryskin, I., and B. Yoon, "A YANG Data Model for VN Operation", draft-ietf- teas-actn-vn-yang-09 (work in progress), July 2020. [I-D.ietf-teas-yang-path-computation] Busi, I., Belotti, S., Lopez, V., Sharma, A., and Y. Shi, "Yang model for requesting Path Computation", draft-ietf- teas-yang-path-computation-10 (work in progress), July 2020. [I-D.ietf-teas-yang-rsvp-te] Beeram, V., Saad, T., Gandhi, R., Liu, X., Bryskin, I., and H. Shah, "A YANG Data Model for RSVP-TE Protocol", draft-ietf-teas-yang-rsvp-te-08 (work in progress), March 2020. [I-D.ietf-teas-yang-te] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, "A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths and Interfaces", draft-ietf-teas-yang-te-25 (work in progress), July 2020. [I-D.ietf-trill-yang-oam] Kumar, D., Senevirathne, T., Finn, N., Salam, S., Xia, L., and H. Weiguo, "YANG Data Model for TRILL Operations, Administration, and Maintenance (OAM)", draft-ietf-trill- yang-oam-05 (work in progress), March 2017. [I-D.ogondio-opsawg-uni-topology] Dios, O., barguil, s., WU, Q., and M. Boucadair, "A YANG Model for User-Network Interface (UNI) Topologies", draft- ogondio-opsawg-uni-topology-01 (work in progress), April 2020. Wu, et al. Expires April 26, 2021 [Page 31] Internet-Draft Service and Network Management Automation October 2020 [I-D.www-opsawg-yang-vpn-service-pm] Bo, W., WU, Q., Boucadair, M., Dios, O., Wen, B., Liu, C., and H. Xu, "A YANG Model for Network and VPN Service Performance Monitoring", draft-www-opsawg-yang-vpn- service-pm-01 (work in progress), July 2020. [I-D.wwx-netmod-event-yang] Bierman, A., WU, Q., Bryskin, I., Birkholz, H., Liu, X., and B. Claise, "A YANG Data model for ECA Policy Management", draft-wwx-netmod-event-yang-09 (work in progress), July 2020. [IPPM] IANA, "Performance Metrics", March 2020, <https://www.iana.org/assignments/performance-metrics/ performance-metrics.xhtml>. [RFC4176] El Mghazli, Y., Ed., Nadeau, T., Boucadair, M., Chan, K., and A. Gonguet, "Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and Management", RFC 4176, DOI 10.17487/RFC4176, October 2005, <https://www.rfc-editor.org/info/rfc4176>. [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 2006, <https://www.rfc-editor.org/info/rfc4364>. [RFC4664] Andersson, L., Ed. and E. Rosen, Ed., "Framework for Layer 2 Virtual Private Networks (L2VPNs)", RFC 4664, DOI 10.17487/RFC4664, September 2006, <https://www.rfc-editor.org/info/rfc4664>. [RFC4761] Kompella, K., Ed. and Y. Rekhter, Ed., "Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling", RFC 4761, DOI 10.17487/RFC4761, January 2007, <https://www.rfc-editor.org/info/rfc4761>. [RFC4762] Lasserre, M., Ed. and V. Kompella, Ed., "Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling", RFC 4762, DOI 10.17487/RFC4762, January 2007, <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>. Wu, et al. Expires April 26, 2021 [Page 32] Internet-Draft Service and Network Management Automation October 2020 [RFC5486] Malas, D., Ed. and D. Meyer, Ed., "Session Peering for Multimedia Interconnect (SPEERMINT) Terminology", RFC 5486, DOI 10.17487/RFC5486, March 2009, <https://www.rfc-editor.org/info/rfc5486>. [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, <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 Networking: A Perspective from within a Service Provider Environment", RFC 7149, DOI 10.17487/RFC7149, March 2014, <https://www.rfc-editor.org/info/rfc7149>. [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", RFC 7224, DOI 10.17487/RFC7224, May 2014, <https://www.rfc-editor.org/info/rfc7224>. [RFC7276] Mizrahi, T., Sprecher, N., Bellagamba, E., and Y. Weingarten, "An Overview of Operations, Administration, and Maintenance (OAM) Tools", RFC 7276, DOI 10.17487/RFC7276, June 2014, <https://www.rfc-editor.org/info/rfc7276>. [RFC7297] Boucadair, M., Jacquenet, C., and N. Wang, "IP Connectivity Provisioning Profile (CPP)", RFC 7297, DOI 10.17487/RFC7297, July 2014, <https://www.rfc-editor.org/info/rfc7297>. [RFC7317] Bierman, A. and M. Bjorklund, "A YANG Data Model for System Management", RFC 7317, DOI 10.17487/RFC7317, August 2014, <https://www.rfc-editor.org/info/rfc7317>. [RFC7455] Senevirathne, T., Finn, N., Salam, S., Kumar, D., Eastlake 3rd, D., Aldrin, S., and Y. Li, "Transparent Interconnection of Lots of Links (TRILL): Fault Management", RFC 7455, DOI 10.17487/RFC7455, March 2015, <https://www.rfc-editor.org/info/rfc7455>. [RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function Chaining (SFC) Architecture", RFC 7665, DOI 10.17487/RFC7665, October 2015, <https://www.rfc-editor.org/info/rfc7665>. Wu, et al. Expires April 26, 2021 [Page 33] Internet-Draft Service and Network Management Automation October 2020 [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 Maintenance Using the Label Distribution Protocol (LDP)", STD 84, RFC 8077, DOI 10.17487/RFC8077, February 2017, <https://www.rfc-editor.org/info/rfc8077>. [RFC8194] Schoenwaelder, J. and V. Bajpai, "A YANG Data Model for LMAP Measurement Agents", RFC 8194, DOI 10.17487/RFC8194, August 2017, <https://www.rfc-editor.org/info/rfc8194>. [RFC8199] Bogdanovic, D., Claise, B., and C. Moberg, "YANG Module Classification", RFC 8199, DOI 10.17487/RFC8199, July 2017, <https://www.rfc-editor.org/info/rfc8199>. [RFC8299] Wu, Q., Ed., Litkowski, S., Tomotaki, L., and K. Ogaki, "YANG Data Model for L3VPN Service Delivery", RFC 8299, DOI 10.17487/RFC8299, January 2018, <https://www.rfc-editor.org/info/rfc8299>. [RFC8309] Wu, Q., Liu, W., and A. Farrel, "Service Models Explained", RFC 8309, DOI 10.17487/RFC8309, January 2018, <https://www.rfc-editor.org/info/rfc8309>. [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore Architecture (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, <https://www.rfc-editor.org/info/rfc8342>. [RFC8343] Bjorklund, M., "A YANG Data Model for Interface Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, <https://www.rfc-editor.org/info/rfc8343>. [RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., Ananthakrishnan, H., and X. Liu, "A YANG Data Model for Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March 2018, <https://www.rfc-editor.org/info/rfc8345>. Wu, et al. Expires April 26, 2021 [Page 34] Internet-Draft Service and Network Management Automation October 2020 [RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X., Ananthakrishnan, H., and N. Bahadur, "A YANG Data Model for Layer 3 Topologies", RFC 8346, DOI 10.17487/RFC8346, March 2018, <https://www.rfc-editor.org/info/rfc8346>. [RFC8348] Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A YANG Data Model for Hardware Management", RFC 8348, DOI 10.17487/RFC8348, March 2018, <https://www.rfc-editor.org/info/rfc8348>. [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for Routing Management (NMDA Version)", RFC 8349, DOI 10.17487/RFC8349, March 2018, <https://www.rfc-editor.org/info/rfc8349>. [RFC8466] Wen, B., Fioccola, G., Ed., Xie, C., and L. Jalil, "A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery", RFC 8466, DOI 10.17487/RFC8466, October 2018, <https://www.rfc-editor.org/info/rfc8466>. [RFC8512] Boucadair, M., Ed., Sivakumar, S., Jacquenet, C., Vinapamula, S., and Q. Wu, "A YANG Module for Network Address Translation (NAT) and Network Prefix Translation (NPT)", RFC 8512, DOI 10.17487/RFC8512, January 2019, <https://www.rfc-editor.org/info/rfc8512>. [RFC8513] Boucadair, M., Jacquenet, C., and S. Sivakumar, "A YANG Data Model for Dual-Stack Lite (DS-Lite)", RFC 8513, DOI 10.17487/RFC8513, January 2019, <https://www.rfc-editor.org/info/rfc8513>. [RFC8519] Jethanandani, M., Agarwal, S., Huang, L., and D. Blair, "YANG Data Model for Network Access Control Lists (ACLs)", RFC 8519, DOI 10.17487/RFC8519, March 2019, <https://www.rfc-editor.org/info/rfc8519>. [RFC8525] Bierman, A., Bjorklund, M., Schoenwaelder, J., Watsen, K., and R. Wilton, "YANG Library", RFC 8525, DOI 10.17487/RFC8525, March 2019, <https://www.rfc-editor.org/info/rfc8525>. [RFC8528] Bjorklund, M. and L. Lhotka, "YANG Schema Mount", RFC 8528, DOI 10.17487/RFC8528, March 2019, <https://www.rfc-editor.org/info/rfc8528>. Wu, et al. Expires April 26, 2021 [Page 35] Internet-Draft Service and Network Management Automation October 2020 [RFC8529] Berger, L., Hopps, C., Lindem, A., Bogdanovic, D., and X. Liu, "YANG Data Model for Network Instances", RFC 8529, DOI 10.17487/RFC8529, March 2019, <https://www.rfc-editor.org/info/rfc8529>. [RFC8530] Berger, L., Hopps, C., Lindem, A., Bogdanovic, D., and X. Liu, "YANG Model for Logical Network Elements", RFC 8530, DOI 10.17487/RFC8530, March 2019, <https://www.rfc-editor.org/info/rfc8530>. [RFC8531] Kumar, D., Wu, Q., and Z. Wang, "Generic YANG Data Model for Connection-Oriented Operations, Administration, and Maintenance (OAM) Protocols", RFC 8531, DOI 10.17487/RFC8531, April 2019, <https://www.rfc-editor.org/info/rfc8531>. [RFC8532] Kumar, D., Wang, Z., Wu, Q., Ed., Rahman, R., and S. Raghavan, "Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications", RFC 8532, DOI 10.17487/RFC8532, April 2019, <https://www.rfc-editor.org/info/rfc8532>. [RFC8533] Kumar, D., Wang, M., Wu, Q., Ed., Rahman, R., and S. Raghavan, "A YANG Data Model for Retrieval Methods for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications", RFC 8533, DOI 10.17487/RFC8533, April 2019, <https://www.rfc-editor.org/info/rfc8533>. [RFC8632] Vallin, S. and M. Bjorklund, "A YANG Data Model for Alarm Management", RFC 8632, DOI 10.17487/RFC8632, September 2019, <https://www.rfc-editor.org/info/rfc8632>. [RFC8641] Clemm, A. and E. Voit, "Subscription to YANG Notifications for Datastore Updates", RFC 8641, DOI 10.17487/RFC8641, September 2019, <https://www.rfc-editor.org/info/rfc8641>. [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 Model for Tunnel Interface Types", RFC 8675, DOI 10.17487/RFC8675, November 2019, <https://www.rfc-editor.org/info/rfc8675>. Wu, et al. Expires April 26, 2021 [Page 36] Internet-Draft Service and Network Management Automation October 2020 [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>. [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>. [RFC8791] Bierman, A., Bjoerklund, M., and K. Watsen, "YANG Data Structure Extensions", RFC 8791, DOI 10.17487/RFC8791, June 2020, <https://www.rfc-editor.org/info/rfc8791>. [RFC8795] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and O. Gonzalez de Dios, "YANG Data Model for Traffic Engineering (TE) Topologies", RFC 8795, DOI 10.17487/RFC8795, August 2020, <https://www.rfc-editor.org/info/rfc8795>. Appendix A. Layered YANG Modules Examples Overview This appendix lists a set of YANG 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 tools and mechanisms used in specific network and service management domains; such inventory can be found in documents such as [RFC7276]. The reader may refer to the YANG Catalog (<https://www.yangcatalog.org>) or the public Github YANG repository (<https://github.com/YangModels/yang>) to query existing YANG models. The YANG Catalog includes some metadata to indicate the module type ('module-classification') [I-D.clacla-netmod-model-catalog]. Note that the mechanism defined in [I-D.ietf-netmod-module-tags] allows to associate tags with YANG modules in order to help classifying the modules. A.1. Service Models: Definition and Samples As described in [RFC8309], the service is "some form of connectivity between customer sites and the Internet and/or between customer sites across the network operator's network and across the Internet". More concretely, an IP connectivity service can be defined as the IP transfer capability characterized by a (Source Nets, Destination Nets, Guarantees, Scope) tuple where "Source Nets" is a group of unicast IP addresses, "Destination Nets" is a group of IP unicast Wu, et al. Expires April 26, 2021 [Page 37] Internet-Draft Service and Network Management Automation October 2020 and/or multicast addresses, and "Guarantees" reflects the guarantees (expressed in terms of QoS, performance, and availability, for example) to properly forward traffic to the said "Destination" [RFC7297]. For example: o The L3SM [RFC8299] defines the L3VPN service ordered by a customer from a network operator. o The L2SM [RFC8466] defines the L2VPN service ordered by a customer from a network operator. 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. L2SM and L3SM are customer service models as per [RFC8309]. A.2. Schema Mount Modularity and extensibility were among the leading design principles of the YANG data modeling language. As a result, the same YANG module can be combined with various sets of other modules and thus form a data model that is tailored to meet the requirements of a specific use case. [RFC8528] defines a mechanism, denoted schema mount, that allows for mounting one data model consisting of any number of YANG modules at a specified location of another (parent) schema. A.3. Network Models: Samples L2NM [I-D.ietf-opsawg-l2nm] and L3NM [I-D.ietf-opsawg-l3sm-l3nm] are examples of YANG network models. Figure 9 depicts a set of additional network models such as topology and tunnel models: Wu, et al. Expires April 26, 2021 [Page 38] Internet-Draft Service and Network Management Automation October 2020 +-------------------------------+-------------------------------+ | Topology YANG modules | Tunnel YANG modules | +-------------------------------+-------------------------------+ | +------------------+ | | | |Network Topologies| | +------+ +-----------+ | | | Model | | |Other | | TE Tunnel | | | +--------+---------+ | |Tunnel| +----+------+ | | | +---------+ | +------+ | | | +---+Service | | +----------+---------+ | | | |Topology | | | | | | | | +---------+ | | | | | | | +---------+ |+----+---+ +----+---+ +---+---+| | +---+Layer 3 | ||MPLS-TE | |RSVP-TE | | SR-TE || | | |Topology | || Tunnel | | Tunnel | |Tunnel || | | +---------+ |+--------+ +--------+ +-------+| | | +---------+ | | | +---+TE | | | | | |Topology | | | | | +---------+ | | | | +---------+ | | | +---+Layer 3 | | | | |Topology | | | | +---------+ | | +-------------------------------+-------------------------------+ Figure 9: Sample Resource Facing Network Models Examples of topology YANG modules are listed below: o Network Topologies Model: [RFC8345] defines a base model for network topology and inventories. Network topology data include link, node, and terminate-point resources. o TE Topology Model: [RFC8795] defines a YANG data model for representing and manipulating TE topologies. This module is extended from network topology model defined in [RFC8345] with TE topologies related content. This model contains technology-agnostic TE Topology building blocks that can be augmented and used by other technology-specific TE topology models. o Layer 3 Topology Model: [RFC8346] defines a YANG data model for representing and manipulating Layer 3 topologies. This model is extended from the network topology model defined in [RFC8345] with Layer 3 topologies specifics. Wu, et al. Expires April 26, 2021 [Page 39] Internet-Draft Service and Network Management Automation October 2020 o Layer 2 Topology Model: [I-D.ietf-i2rs-yang-l2-network-topology] defines a YANG data model for representing and manipulating Layer 2 topologies. This model is extended from the network topology model defined in [RFC8345] with Layer 2 topology specifics. Examples of tunnel YANG modules are provided below: o Tunnel identities: [RFC8675] defines a collection of YANG identities used as interface types for tunnel interfaces. o TE Tunnel Model: [I-D.ietf-teas-yang-te] defines a YANG module for the configuration and management of TE interfaces, tunnels, and LSPs. o Segment Routing (SR) Traffic Engineering (TE) Tunnel Model: [I-D.ietf-teas-yang-te] augments the TE generic and MPLS-TE model(s) and defines a YANG module for SR-TE specific data. o MPLS-TE Model: [I-D.ietf-teas-yang-te] augments the TE generic and MPLS-TE model(s) and defines a YANG module for MPLS-TE configurations, state, RPC and notifications. o RSVP-TE MPLS Model: [I-D.ietf-teas-yang-rsvp-te] augments the RSVP-TE generic module with parameters to configure and manage signaling of MPLS RSVP-TE LSPs. Other sample network models are listed hereafter: o Path Computation API Model: [I-D.ietf-teas-yang-path-computation] YANG module for a stateless RPC which complements the stateful solution defined in [I-D.ietf-teas-yang-te]. o OAM Models (including Fault Management (FM) and Performance Monitoring): [RFC8532] defines a base YANG module for the management of OAM protocols that use Connectionless Communications. [RFC8533] defines a retrieval method YANG module for connectionless OAM Wu, et al. Expires April 26, 2021 [Page 40] Internet-Draft Service and Network Management Automation October 2020 protocols. [RFC8531] defines a base YANG module for connection oriented OAM protocols. These three models are intended to provide consistent reporting, configuration, and representation for connection-less OAM and Connection oriented OAM separately. Alarm monitoring is a fundamental part of monitoring the network. Raw alarms from devices do not always tell the status of the network services or necessarily point to the root cause. [RFC8632] defines a YANG module for alarm management. A.4. Device Models: Samples Network Element models (listed in Figure 10) are used to describe how a service can be implemented by activating and tweaking a set of functions (enabled in one or multiple devices, or hosted in cloud infrastructures) that are involved in the service delivery. For example, the L3VPN service will involve many PEs and require manipulating the following modules: o Routing management [RFC8349] o BGP [I-D.ietf-idr-bgp-model] o PIM [I-D.ietf-pim-yang] o NAT management [RFC8512] o QoS management [I-D.ietf-rtgwg-qos-model] o ACLs [RFC8519] Figure 10 uses IETF-defined data models as an example. Wu, et al. Expires April 26, 2021 [Page 41] Internet-Draft Service and Network Management Automation October 2020 +------------------------+ +-+ Device Model | | +------------------------+ | +------------------------+ +---------------+ | | Logical Network | | | +-+ Element Model | | Architecture | | +------------------------+ | | | +------------------------+ +-------+-------+ +-+ Network Instance Model | | | +------------------------+ | | +------------------------+ | +-+ Routing Type Model | | +------------------------+ +-------+----------+----+------+------------+-----------+------+ | | | | | | | +-+-+ +---+---+ +----+----+ +--+--+ +----+----+ +--+--+ | |ACL| |Routing| |Transport| | OAM | |Multicast| | PM | Others +---+ +-+-----+ +----+----+ +--+--+ +-----+---+ +--+--+ | +-------+ | +------+ | +--------+ | +-----+ | +-----+ +-+Core | +-+ MPLS | +-+ BFD | +-+IGMP | +-+TWAMP| | |Routing| | | Base | | +--------+ | |/MLD | | +-----+ | +-------+ | +------+ | +--------+ | +-----+ | +-----+ | +-------+ | +------+ +-+LSP Ping| | +-----+ +-+OWAMP| +-+ BGP | +-+ MPLS | | +--------+ +-+ PIM | | +-----+ | +-------+ | | LDP | | +--------+ | +-----+ | +-----+ | +-------+ | +------+ +-+MPLS-TP | | +-----+ +-+LMAP | +-+ ISIS | | +------+ +--------+ +-+ MVPN| +-----+ | +-------+ +-+ MPLS | +-----+ | +-------+ |Static| +-+ OSPF | +------+ | +-------+ | +-------+ +-+ RIP | | +-------+ | +-------+ +-+ VRRP | | +-------+ | +-------+ +-+SR/SRv6| | +-------+ | +-------+ +-+ISIS-SR| | +-------+ | +-------+ +-+OSPF-SR| +-------+ Figure 10: Network Element Modules Overview Wu, et al. Expires April 26, 2021 [Page 42] Internet-Draft Service and Network Management Automation October 2020 A.4.1. Model Composition o Logical Network Element Model [RFC8530] defines a logical network element module which can be used to manage the logical resource partitioning that may be present on a network device. Examples of common industry terms for logical resource partitioning are Logical Systems or Logical Routers. o Network Instance Model [RFC8529] defines a network instance module. This module can be used to manage the virtual resource partitioning that may be present on a network device. Examples of common industry terms for virtual resource partitioning are VRF instances and Virtual Switch Instances (VSIs). A.4.2. Device Management The following list enumerates some YANG modules that can be used for device management: o [RFC8348]: defines a YANG module for the management of hardware. o [RFC7317]: defines the "ietf-system" YANG module that provides many features such as the configuration and the monitoring of system or system control operations (e.g., shutdown, restart, setting time) identification. o [RFC8341]: defines a network configuration access control YANG module. A.4.3. Interface Management The following provides some YANG modules that can be used for interface management: o [RFC7224]: defines a YANG module for interface type definitions. o [RFC8343]: defines a YANG module for the management of network interfaces. A.4.4. Some Device Model Examples The following provides an overview of some device models that can be used within a network. This list is not comprehensive. Wu, et al. Expires April 26, 2021 [Page 43] Internet-Draft Service and Network Management Automation October 2020 L2VPN: [I-D.ietf-bess-l2vpn-yang] defines a YANG module for MPLS based Layer 2 VPN services (L2VPN) [RFC4664] and includes switching between the local attachment circuits. The L2VPN model covers point-to-point VPWS and Multipoint VPLS services. These services use signaling of Pseudowires across MPLS networks using LDP [RFC8077][RFC4762] or BGP [RFC4761]. EVPN: [I-D.ietf-bess-evpn-yang] defines a YANG module for Ethernet VPN services. The model is agnostic of the underlay. It applies to MPLS as well as to VxLAN encapsulation. The module is also agnostic to the services, including E-LAN, E-LINE, and E-TREE services. L3VPN: [I-D.ietf-bess-l3vpn-yang] defines a YANG module that can be used to configure and manage BGP L3VPNs [RFC4364]. It contains VRF specific parameters as well as BGP specific parameters applicable for L3VPNs. Core Routing: [RFC8349] defines the core routing YANG data model, which is intended as a basis for future data model development covering more-sophisticated routing systems. It is expected that other Routing technology YANG modules (e.g., VRRP, RIP, ISIS, OSPF models) will augment the Core Routing base YANG module. MPLS: [I-D.ietf-mpls-base-yang] defines a base model for MPLS which serves as a base framework for configuring and managing an MPLS switching subsystem. It is expected that other MPLS technology YANG modules (e.g., MPLS LSP Static, LDP, or RSVP-TE models) will augment the MPLS base YANG module. BGP: [I-D.ietf-idr-bgp-model] defines a YANG module for configuring and managing BGP, including protocol, policy, and operational aspects based on data center, carrier, and content provider operational requirements. Routing Policy: [I-D.ietf-rtgwg-policy-model] defines a YANG module for configuring and managing routing policies based on operational practice. The module provides a generic policy framework which can be augmented with protocol- specific policy configuration. SR/SRv6: [I-D.ietf-spring-sr-yang] a YANG module for segment routing configuration and operation. Wu, et al. Expires April 26, 2021 [Page 44] Internet-Draft Service and Network Management Automation October 2020 BFD: Bidirectional Forwarding Detection (BFD) [RFC5880] is a network protocol which is used for liveness detection of arbitrary paths between systems. [I-D.ietf-bfd-yang] defines a YANG module that can be used to configure and manage BFD. Multicast: [I-D.ietf-pim-yang] defines a YANG module that can be used to configure and manage Protocol Independent Multicast (PIM) devices. [RFC8652] defines a YANG module that can be used to configure and manage Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) devices. [I-D.ietf-pim-igmp-mld-snooping-yang] defines a YANG module that can be used to configure and manage Internet Group Management Protocol (IGMP) and Multicast Listener 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). PM: [I-D.ietf-ippm-twamp-yang] defines a YANG data model for client and server implementations of the Two-Way Active Measurement Protocol (TWAMP). [I-D.ietf-ippm-stamp-yang] defines the data model for implementations of Session-Sender and Session-Reflector for Simple Two-way Active Measurement Protocol (STAMP) mode using YANG. [RFC8194] defines a YANG data model for Large-Scale Measurement Platforms (LMAPs). ACL: Access Control List (ACL) is one of the basic elements used to configure device forwarding behavior. It is used in many networking technologies such as Policy Based Routing, firewalls, etc. [RFC8519] describes a YANG data model of ACL basic building blocks. QoS: [I-D.ietf-rtgwg-qos-model] describes a YANG module of Differentiated Services for configuration and operations. NAT: For the sake of network automation and the need for programming Network Address Translation (NAT) function in particular, a YANG data model for configuring and managing the NAT is essential. Wu, et al. Expires April 26, 2021 [Page 45] Internet-Draft Service and Network Management Automation October 2020 [RFC8512] defines a YANG module for the NAT function covering a variety of NAT flavors such as Network Address Translation from IPv4 to IPv4 (NAT44), Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers (NAT64), customer-side translator (CLAT), Stateless IP/ ICMP Translation (SIIT), Explicit Address Mappings (EAM) 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 address sharing, including Lightweight 4over6, Mapping of Address and Port with Encapsulation (MAP-E), and Mapping of Address and Port using Translation (MAP-T) softwire mechanisms. Authors' Addresses Qin Wu (editor) Huawei 101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China Email: bill.wu@huawei.com Mohamed Boucadair (editor) Orange Rennes 35000 France Email: mohamed.boucadair@orange.com Diego R. Lopez Telefonica I+D Spain Email: diego.r.lopez@telefonica.com Wu, et al. Expires April 26, 2021 [Page 46] Internet-Draft Service and Network Management Automation October 2020 Chongfeng Xie China Telecom Beijing China Email: xiechf@chinatelecom.cn Liang Geng China Mobile Email: gengliang@chinamobile.com Wu, et al. Expires April 26, 2021 [Page 47]