--- 1/draft-ietf-opsawg-yang-vpn-service-pm-06.txt 2022-04-25 01:13:12.363397056 -0700 +++ 2/draft-ietf-opsawg-yang-vpn-service-pm-07.txt 2022-04-25 01:13:12.435398876 -0700 @@ -1,24 +1,24 @@ OPSAWG Working Group B. Wu, Ed. Internet-Draft Q. Wu, Ed. Intended status: Standards Track Huawei -Expires: 16 October 2022 M. Boucadair, Ed. +Expires: 27 October 2022 M. Boucadair, Ed. Orange O. Gonzalez de Dios Telefonica B. Wen Comcast - 14 April 2022 + 25 April 2022 A YANG Model for Network and VPN Service Performance Monitoring - draft-ietf-opsawg-yang-vpn-service-pm-06 + draft-ietf-opsawg-yang-vpn-service-pm-07 Abstract The data model for network topologies defined in RFC 8345 introduces vertical layering relationships between networks that can be augmented to cover network and service topologies. This document defines a YANG module for performance monitoring (PM) of both networks and VPN services that can be used to monitor and manage network performance on the topology at higher layer or the service topology between VPN sites. @@ -31,21 +31,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on 16 October 2022. + This Internet-Draft will expire on 27 October 2022. Copyright Notice Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights @@ -58,44 +58,45 @@ 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Network and VPN Service Performance Monitoring Model Usage . 4 3.1. Collecting Data via Pub/Sub Mechanism . . . . . . . . . . 5 3.2. Collecting Data On-demand . . . . . . . . . . . . . . . . 6 4. Description of The Data Model . . . . . . . . . . . . . . . . 6 4.1. Layering Relationship between Multiple Layers of Topology . . . . . . . . . . . . . . . . . . . . . . . . 6 - 4.2. Network Level . . . . . . . . . . . . . . . . . . . . . . 8 + 4.2. Network Level . . . . . . . . . . . . . . . . . . . . . . 9 4.3. Node Level . . . . . . . . . . . . . . . . . . . . . . . 9 4.4. Link and Termination Point Level . . . . . . . . . . . . 10 - 5. Network and VPN Service Performance Monitoring YANG Module . 14 + 5. Network and VPN Service Performance Monitoring YANG Module . 15 6. Security Considerations . . . . . . . . . . . . . . . . . . . 29 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 - 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30 - 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 30 + 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 31 + 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 31 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 31 10.1. Normative References . . . . . . . . . . . . . . . . . . 31 10.2. Informative References . . . . . . . . . . . . . . . . . 33 - Appendix A. Illustrating Examples . . . . . . . . . . . . . . . 35 + Appendix A. Illustrative Examples . . . . . . . . . . . . . . . 35 A.1. VPN Performance Subscription Example . . . . . . . . . . 35 A.2. Example of VPN Performance Snapshot . . . . . . . . . . . 36 A.3. Example of Percentile Monitoring . . . . . . . . . . . . 38 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38 1. Introduction [RFC8969] describes a framework for automating service and network - management with YANG models. It defines that the performance - measurement telemetry model to be tied with the service, such as - Layer 3 VPN and Layer 2 VPN, or network models to monitor the overall - network performance or Service Level Agreement (SLA). + management with YANG [RFC6020] models. It defines that the + performance measurement telemetry model should be tied to the + services (such as a Layer 3 VPN or Layer 2 VPN) or to the network + models to monitor the overall network performance and the Service + Level Agreements (SLAs). The performance of VPN services is associated with the performance changes of the underlay network that carries VPN services, such as the delay of the underlay tunnels and the packet loss status of the device interfaces. Additionally, the integration of Layer 2/Layer 3 VPN performance and network performance data enables the orchestrator to subscribe to VPN service performance in a unified manner. Therefore, this document defines a YANG module for both network and VPN service performance monitoring (PM). The module can be used to monitor and manage network performance on the topology level or the @@ -138,21 +139,22 @@ L2VPN Layer 2 Virtual Private Network L3VPN Layer 3 Virtual Private Network L2NM L2VPN Network Model L3NM L3VPN Network Model MPLS Multiprotocol Label Switching OAM Operations, Administration, and Maintenance OWAMP One-Way Active Measurement Protocol PE Provider Edge PM Performance Monitoring - SLA Service Level Agreements + SLA Service Level Agreement + TP Termination Point, as defined in [RFC8345] section 4.2 TWAMP Two-Way Active Measurement Protocol VPLS Virtual Private LAN Service VPN Virtual Private Network 3. Network and VPN Service Performance Monitoring Model Usage Models are key for automating network management operations. According to [RFC8969], together with service and network models, performance measurement telemetry models are needed to monitor network performance to meet specific service requirements (typically @@ -184,24 +186,25 @@ As shown in Figure 1, in the context of the layering model architecture described in [RFC8309], the network and VPN service performance monitoring (PM) model can be used to expose a set of performance information to the above layer. Such information can be used by an orchestrator to subscribe to performance data. The network controller will then notify the orchestrator about corresponding parameter changes. Before using the model, the controller needs to establish complete topology visibility of the network and VPN. For example, the - controller can use information from [RFC8345], [I-D.ietf-opsawg-sap] - or VPN instances. Then the controller derives network or VPN level - performance data by aggregating (and filtering) lower-level data - collected via monitoring counters of the involved devices. + controller can use network information from [RFC8345], + [I-D.ietf-opsawg-sap] or VPN information from [RFC9182], + [I-D.ietf-opsawg-l2nm]. Then the controller derives network or VPN + level performance data by aggregating (and filtering) lower-level + data collected via monitoring counters of the involved devices. The network or VPN performance data can be based on different sources. For example, the performance monitoring data per link in the underlying network can be collected using a network performance measurement method such as One-Way Active Measurement Protocol (OWAMP) [RFC4656], Two-Way Active Measurement Protocol (TWAMP) [RFC5357], and Multiprotocol Label Switching (MPLS) Loss and Delay Measurement [RFC6374]. The performance monitoring information reflecting the quality of the network or VPN service (e.g., end-to- end network performance data between source node and destination node @@ -222,22 +225,23 @@ using the tagging methods defined in [I-D.ietf-netmod-node-tags]. 3.1. Collecting Data via Pub/Sub Mechanism Some applications such as service-assurance applications, which must maintain a continuous view of operational data and state, can use the subscription model specified in [RFC8641] to subscribe to the specific network performance data or VPN service performance data they are interested in, at the data source. For example, network or VPN topology updates may be obtained through on-change notifications - [RFC8641]. For dynamic-changing PM data, various notifications can - be specified to obtain more complete data. A periodic notification + [RFC8641]. For dynamic PM data, various notifications can be + specified to obtain more complete data. A periodic notification + [RFC8641] can be specified to obtain real-time performance data, a replay notification defined in [RFC5277] or [RFC8639] can be specified to obtain historical data, or alarm notifications [RFC8632] can be specified to get alarms for the metrics which exceed or fall below the performance threshold. The data source can, then, use the network and VPN service assurance model defined in this document and the YANG Push model [RFC8641] to distribute specific telemetry data to target recipients. @@ -246,99 +250,101 @@ To obtain a snapshot of a large amount of performance data from a network topology or VPN network, service-assurance applications may retrieve information using the network and VPN service PM model through a NETCONF [RFC6241] or a RESTCONF [RFC8040] interface. For example, a specified "link-id" of a VPN can be used as a filter in a RESTCONF GET request to retrieve per-link VPN PM data. 4. Description of The Data Model This document defines the YANG module, "ietf-network-vpn-pm", which - is an augmentation to the "ietf-network" and "ietf-network-topology". + is an augmentation to the "ietf-network" and "ietf-network-topology" + modules. The performance monitoring data augments the service topology as shown in Figure 2. - +----------------------+ +-----------------------+ - |ietf-network | |Network and VPN Service| - |ietf-network-topology |<---------|Performance Monitoring | - +----------------------+ augments | Model | - +-----------------------+ + +----------------------+ +---------------------+ + |ietf-network | | | + |ietf-network-topology |<---------| ietf-network-vpn-pm | + +----------------------+ augments | | + +---------------------+ Figure 2: Module Augmentation 4.1. Layering Relationship between Multiple Layers of Topology [RFC8345] defines a YANG data model for network/service topologies and inventories. The service topology described in [RFC8345] includes the virtual topology for a service layer above Layer 1 (L1), Layer 2 (L2), and Layer 3 (L3). This service topology has the generic topology elements of node, link, and terminating point. One typical example of a service topology is described in Figure 3 of [RFC8345]: two VPN service topologies instantiated over a common L3 topology. Each VPN service topology is mapped onto a subset of nodes from the common L3 topology. Figure 3 illustrates an example of a topology that maps between the VPN service topology and an underlying network: VPN 1 VPN 2 - +-----------------------+ +---------------------+ + +------------------------+ +------------------------+ / / / / - /S1C_[VN3]::: / /S2A S2B / - / \ ::::: / / _[VN1]______[VN3]_ / - / \ : / / : : / Overlay - / \ :: : : : : : : / - /S1B_[VN2]____[VN1]_S1A / / : : : / - +--------:-------:------+ +---:----:----------:-+ - : : :: : : : : + / S1C_[VN3]::: / / / + / \ ::::: / / S2A_[VN1]____[VN3]_S2B / + / \ ::: / / : : / Overlay + / \ :::::::::::: : : / + / S1B_[VN2]____[VN1]_S1A / / : : / + +---------:-------:------+ +-------:-:----------:---+ + : : :::::::::::: : : : : : : : - Site-1A : +-------:--: ----- -------- : -------:-----+ Site-1C - [CE1]___: /__ ___ [N1]__________________ [N2]__ :___ /__[CE3] + Site-1A : +-------:-:------------------:-------:-----+ Site-1C + [CE1]___:_/_______[N1]___________________[N2]___:____/__[CE3] :/ / / \ _____/ / : / - [CE5]___ : ___ / / \ _____/ / :: / - Site-2A /: / \ / / : / - / : [N5] / : / Underlay Network - / : / __/ \__ / : / - / : / ___/ \__ / : / + [CE5]_____:_______/ / \ _____/ / :: / + Site-2A /: / \ / / :: / + / : [N5] / :: / Underlay Network + / : / __/ \__ / :: / + / : / ___/ \__ /:: / Site-1B / : / ___/ \ / : / Site-2B -[CE2]_ /________[N4]_________________ [N3]:::_____/____[CE4] +[CE2]__/________[N4]__________________[N3]________/____[CE4] + / / +------------------------------------------+ Legend: - N:node VN:VPN-Node S:Site - __ Link - : Mapping between networks + N:Node VN:VPN-Node S:Site CE:Customer Edge + __ Link within a network layer + : Mapping between network layers Figure 3: Example of Topology Mapping Between VPN Service Topology and Underlying Network - As shown in Figure 3, two VPN services topologies are both built on - top of one common underlying physical network: + As shown in Figure 3, two VPN services topologies are built on top of + one common underlying physical network: VPN 1: This service topology supports hub-spoke communications for 'customer 1' connecting the customer's access at three sites: 'Site-1A', 'Site-1B', and 'Site-1C'. These sites are connected to nodes that are mapped to node 1 (N1), node 2 (N2), and node 4 (N4) in the underlying physical network. 'Site-1A' plays the role of hub while 'Site-1B' and 'Site-1C' are configured as spoke. VPN 2: This service supports any-to-any communications for 'customer 2' connecting the customer's access at two sites: 'Site-2A' and 'Site-2B'. These sites are connected to nodes that are mapped to nodes 1 (N1) and node 3 (N3)5 in the underlying physical network. 'Site-2A' and 'Site-2B' have 'any-to-any' role. Apart from the association between the VPN topology and the underlay topology, VPN Network PM can also provide the performance status of the underlay network and VPN services. For example, network PM can - provide link PM statistics and port statistics. VPN PM can provides + provide link PM statistics and port statistics. VPN PM can provide statistics on VPN access interfaces, the number of current VRF routes or L2VPN MAC entry of VPN nodes, and performance statistics on the logical point-to-point link between source and destination VPN nodes or between source and destination VPN access interfaces. Figure 4 illustrates an example of VPN PM and the difference between two VPN PM measurement methods. One is the VPN tunnel PM and the other is inter-VPN-access interface PM. +-----------------------------------------------------+ | | @@ -356,42 +362,42 @@ +-----------------------------------------------------+ | | | | +----+ | TP+-----+ Link +---+ Link +-----+TP | +----+ | CE4+-+----------+ N1 +-------+-N2+-------+ N3 +----------+-+CE5 | +----+ | 1-1+-----+1-2 2-1+---+2-2 3-1+-----+3-2 | +----+ | | | | +-----------------------------------------------------+ Legend: - N:node VN:VPN-Node + N:node VN:VPN-Node TP:Termination Point -:Link Figure 4: An Example of VPN PM 4.2. Network Level For network performance monitoring, the container of "networks" in [RFC8345] does not need to be extended. For VPN service performance monitoring, the container "service-type" is defined to indicate the VPN type, e.g., L3VPN or Virtual Private LAN Service (VPLS). The values are taken from [RFC9181]. When a network topology instance contains the L3VPN or other L2VPN network type, it represents a VPN instance that can perform performance monitoring. The tree in Figure 5 is a part of ietf-network-vpn-pm tree. It defines the following set of network level attributes: "vpn-id": Refers to an identifier of VPN service defined in - [RFC9181]). This identifier is used to correlate the performance + [RFC9181]. This identifier is used to correlate the performance status with the network service configuration. "vpn-service-topology": Indicates the type of the VPN topology. This model supports "any-to-any", "Hub and Spoke" (where Hubs can exchange traffic), and "Hub and Spoke disjoint" (where Hubs cannot exchange traffic) that are taken from [RFC9181]. These VPN topology types can be used to describe how VPN sites communicate with each other. module: ietf-network-vpn-pm @@ -427,43 +433,44 @@ attribute: "role": Defines the role in a particular VPN service topology. The roles are taken from [RFC9181] (e.g., any-to-any-role, spoke-role, hub-role). augment /nw:networks/nw:network/nw:node: +--rw pm-attributes +--rw node-type? identityref +--ro entry-summary - | +--ro ipv4 + | +--ro ipv4-num | | +--ro maximum-routes? uint32 | | +--ro total-active-routes? uint32 - | +--ro ipv6 + | +--ro ipv6-num | | +--ro maximum-routes? uint32 | | +--ro total-active-routes? uint32 | +--ro mac-num | +--ro mac-num-limit? uint32 | +--ro total-active-mac-num? uint32 +--rw role? identityref Figure 6: Node Level YANG Tree of the Hierarchies 4.4. Link and Termination Point Level The tree in Figure 7 is the link and termination point (TP) part of ietf-network-vpn-pm tree. The 'links' are classified into two types: topology link defined in - [RFC8345] and abstract link of a VPN between PEs. + [RFC8345] and abstract link of a VPN between PEs defined in this + module. - The performance data of a link is a collection of counters that - report the performance status. + The performance data of a link is a collection of counters and gauges + that report the performance status. augment /nw:networks/nw:network/nt:link: +--rw pm-attributes +--rw low-percentile? percentile +--rw intermediate-percentile? percentile +--rw high-percentile? percentile +--rw measurement-interval? uint32 +--ro start-time? yang:date-and-time +--ro end-time? yang:date-and-time +--ro pm-source? identityref @@ -607,21 +614,24 @@ VPN PM type ("vpn-pm-type"): Indicates the VPN performance type, which can be inter-vpn-access-interface PM or VPN underlay-tunnel PM. These two methods are common VPN measurement methods. The inter-VPN-access-interface PM is to monitor the performance of logical point-to-point connections between a source and a destination VPN access interfaces. And the underlay-tunnel PM is to monitor the performance of underlay tunnels of VPNs. The inter-VPN-access-interface PM includes PE-PE monitoring. Therefore, only one of the two methods is needed , and the model defines "choice" to indicate these two methods, which also allows - other methods to be extended. + other methods to be extended. The inter-VPN-access-interface PM + is defined as an empty leaf, which is not bound to a specific VPN + access interface. The source or destination VPN access interface + of the measurement can be augmented as needed. VPN underlay transport type ("vpn-underlay-transport-type"): Indicat es the abstract link protocol-type of a VPN, such as GRE or IP-in- IP. The leaf refers to an identifier of the "underlay-transport" defined in [RFC9181], which describes the transport technology to carry the traffic of the VPN service. For the data nodes of 'termination-point' depicted in Figure 7, the module defines the following minimal set of statistics: @@ -638,21 +648,21 @@ network access defined in [RFC9182] or [I-D.ietf-opsawg-l2nm]. When multiple VPN network accesses are created using the same physical port, finer-grained metrics can be monitored. If a TP is associated with only a single VPN, this list is not required. 5. Network and VPN Service Performance Monitoring YANG Module The "ietf-network-vpn-pm" module uses types defined in [RFC8345], [RFC6991], [RFC8532], and [RFC9181]. - file "ietf-network-vpn-pm@2022-04-08.yang" + file "ietf-network-vpn-pm@2022-04-25.yang" module ietf-network-vpn-pm { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm"; prefix nvp; import ietf-yang-types { prefix yang; reference "RFC 6991: Common YANG Types"; } @@ -714,21 +723,21 @@ This version of this YANG module is part of RFC XXXX (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; // RFC Ed.: update the date below with the date of RFC // publication and remove this note. // RFC Ed.: replace XXXX with actual RFC number and remove // this note. - revision 2022-04-08 { + revision 2022-04-25 { description "Initial revision."; reference "RFC XXXX: A YANG Model for Network and VPN Service Performance Monitoring"; } identity node-type { description "Base identity for node type"; @@ -827,40 +833,41 @@ if the percentile is set to 95.00 and the 95th percentile one-way delay is 2 milliseconds, then the 95 percent of the sample value is less than or equal to 2 milliseconds."; } grouping entry-summary { description "Entry summary grouping used for network topology augmentation."; + container entry-summary { config false; description "Container for VPN or network entry summary."; - container ipv4 { + container ipv4-num { leaf maximum-routes { type uint32; description "Indicates the maximum number of IPv4 routes for the VPN."; } leaf total-active-routes { type uint32; description "Indicates total active IPv4 routes for the VPN."; } description "IPv4-specific parameters."; } - container ipv6 { + container ipv6-num { leaf maximum-routes { type uint32; description "Indicates the maximum number of IPv6 routes for the VPN."; } leaf total-active-routes { type uint32; description "Indicates total active IPv6 routes for the VPN."; @@ -1266,22 +1273,24 @@ "Augments the network topology link with VPN service performance monitoring attributes."; choice vpn-pm-type { description "The VPN PM type of this logical point-to-point unidirectional VPN link."; case inter-vpn-access-interface { leaf inter-vpn-access-interface { type empty; description - "This is a placeholder for inter-vpn-access-interface PM. - There is no technology to be defined."; + "This is a placeholder for inter-vpn-access-interface PM, + which is not bound to a specific VPN access interface. + The source or destination VPN access interface + of the measurement can be augmented as needed."; } } case underlay-tunnel { leaf vpn-underlay-transport-type { type identityref { base vpn-common:protocol-type; } config false; description "The leaf indicates the underlay transport type of @@ -1441,20 +1449,29 @@ [RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)", RFC 3393, DOI 10.17487/RFC3393, November 2002, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . + [RFC4026] Andersson, L. and T. Madsen, "Provider Provisioned Virtual + Private Network (VPN) Terminology", RFC 4026, + DOI 10.17487/RFC4026, March 2005, + . + + [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private + Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February + 2006, . + [RFC4656] Shalunov, S., Teitelbaum, B., Karp, A., Boote, J., and M. Zekauskas, "A One-way Active Measurement Protocol (OWAMP)", RFC 4656, DOI 10.17487/RFC4656, September 2006, . [RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J. Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)", RFC 5357, DOI 10.17487/RFC5357, October 2008, . @@ -1503,63 +1520,60 @@ Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, . [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, . + [RFC8571] Ginsberg, L., Ed., Previdi, S., Wu, Q., Tantsura, J., and + C. Filsfils, "BGP - Link State (BGP-LS) Advertisement of + IGP Traffic Engineering Performance Metric Extensions", + RFC 8571, DOI 10.17487/RFC8571, March 2019, + . + [RFC8641] Clemm, A. and E. Voit, "Subscription to YANG Notifications for Datastore Updates", RFC 8641, DOI 10.17487/RFC8641, September 2019, . [RFC9181] Barguil, S., Gonzalez de Dios, O., Ed., Boucadair, M., Ed., and Q. Wu, "A Common YANG Data Model for Layer 2 and Layer 3 VPNs", RFC 9181, DOI 10.17487/RFC9181, February 2022, . 10.2. Informative References [I-D.ietf-netmod-node-tags] Wu, Q., Claise, B., Liu, P., Du, Z., and M. Boucadair, "Self-Describing Data Object Tags in YANG Data Models", Work in Progress, Internet-Draft, draft-ietf-netmod-node- tags-06, 21 February 2022, . [I-D.ietf-opsawg-l2nm] - Barguil, S., Dios, O. G. D., Boucadair, M., and L. A. - Munoz, "A Layer 2 VPN Network YANG Model", Work in - Progress, Internet-Draft, draft-ietf-opsawg-l2nm-12, 22 - November 2021, . + Boucadair, M., Dios, O. G. D., Barguil, S., and L. A. + Munoz, "A YANG Network Data Model for Layer 2 VPNs", Work + in Progress, Internet-Draft, draft-ietf-opsawg-l2nm-13, 14 + April 2022, . [I-D.ietf-opsawg-sap] Boucadair, M., Dios, O. G. D., Barguil, S., Wu, Q., and V. Lopez, "A Network YANG Model for Service Attachment Points (SAPs)", Work in Progress, Internet-Draft, draft-ietf- opsawg-sap-04, 11 April 2022, . - [RFC4026] Andersson, L. and T. Madsen, "Provider Provisioned Virtual - Private Network (VPN) Terminology", RFC 4026, - DOI 10.17487/RFC4026, March 2005, - . - - [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private - Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February - 2006, . - [RFC5277] Chisholm, S. and H. Trevino, "NETCONF Event Notifications", RFC 5277, DOI 10.17487/RFC5277, July 2008, . [RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S. Previdi, "OSPF Traffic Engineering (TE) Metric Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015, . [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF @@ -1572,62 +1586,56 @@ [RFC8309] Wu, Q., Liu, W., and A. Farrel, "Service Models Explained", RFC 8309, DOI 10.17487/RFC8309, January 2018, . [RFC8570] Ginsberg, L., Ed., Previdi, S., Ed., Giacalone, S., Ward, D., Drake, J., and Q. Wu, "IS-IS Traffic Engineering (TE) Metric Extensions", RFC 8570, DOI 10.17487/RFC8570, March 2019, . - [RFC8571] Ginsberg, L., Ed., Previdi, S., Wu, Q., Tantsura, J., and - C. Filsfils, "BGP - Link State (BGP-LS) Advertisement of - IGP Traffic Engineering Performance Metric Extensions", - RFC 8571, DOI 10.17487/RFC8571, March 2019, - . - [RFC8632] Vallin, S. and M. Bjorklund, "A YANG Data Model for Alarm Management", RFC 8632, DOI 10.17487/RFC8632, September 2019, . [RFC8639] Voit, E., Clemm, A., Gonzalez Prieto, A., Nilsen-Nygaard, E., and A. Tripathy, "Subscription to YANG Notifications", RFC 8639, DOI 10.17487/RFC8639, September 2019, . [RFC8969] Wu, Q., Ed., Boucadair, M., Ed., Lopez, D., Xie, C., and L. Geng, "A Framework for Automating Service and Network Management with YANG", RFC 8969, DOI 10.17487/RFC8969, January 2021, . [RFC9182] Barguil, S., Gonzalez de Dios, O., Ed., Boucadair, M., Ed., Munoz, L., and A. Aguado, "A YANG Network Data Model for Layer 3 VPNs", RFC 9182, DOI 10.17487/RFC9182, February 2022, . -Appendix A. Illustrating Examples +Appendix A. Illustrative Examples A.1. VPN Performance Subscription Example The example shown in Figure 8 illustrates how a client subscribes to the performance monitoring information between nodes ('node-id') A and B in the L3 network topology. The performance monitoring parameter that the client is interested in is end-to-end loss. POST /restconf/operations /ietf-subscribed-notifications:establish-subscription { "ietf-subscribed-notifications:input":{ "stream-subtree-filter":{ "ietf-network:networks":{ "network":{ - "network-id":"l3-network", + "network-id":"foo:l3-network", "ietf-network-vpn-pm:service-type":{ "ietf-vpn-common:l3vpn":{} }, "node":[ { "node-id":"A", "ietf-network-vpn-pm:pm-attributes":{ "node-type":"PE" }, "termination-point":{ @@ -1729,21 +1736,21 @@ Figure 9 A.3. Example of Percentile Monitoring The following shows an example of a percentile measurement for a VPN link. { "ietf-network-topology:link": [ { - "link-id": "vpn1-link1", + "link-id": "foo:vpn1-link1", "source": { "source-node": "vpn-node1" }, "destination": { "dest-node": "vpn-node3" }, "ietf-network-vpn-pm:pm-attributes": { "low-percentile": "20.00", "intermediate-percentile": "50.00", "high-percentile": "90.00",