draft-ietf-opsawg-yang-vpn-service-pm-01.txt   draft-ietf-opsawg-yang-vpn-service-pm-02.txt 
OPSAWG Working Group B. Wu, Ed. OPSAWG Working Group B. Wu, Ed.
Internet-Draft Q. Wu, Ed. Internet-Draft Q. Wu, Ed.
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Expires: January 7, 2022 M. Boucadair, Ed. Expires: 23 July 2022 M. Boucadair, Ed.
Orange Orange
O. Gonzalez de Dios O. Gonzalez de Dios
Telefonica Telefonica
B. Wen B. Wen
Comcast Comcast
C. Liu 19 January 2022
China Unicom
H. Xu
China Telecom
July 6, 2021
A YANG Model for Network and VPN Service Performance Monitoring A YANG Model for Network and VPN Service Performance Monitoring
draft-ietf-opsawg-yang-vpn-service-pm-01 draft-ietf-opsawg-yang-vpn-service-pm-02
Abstract Abstract
The data model defined in RFC 8345 introduces vertical layering The data model for network topologies defined in RFC 8345 introduces
relationships between networks that can be augmented to cover network vertical layering relationships between networks that can be
and service topologies. This document defines a YANG module for both augmented to cover network and service topologies. This document
network performance monitoring (PM) and VPN service performance defines a YANG module for performance monitoring (PM) of both
monitoring that can be used to monitor and manage network performance networks and VPN services that can be used to monitor and manage
on the topology at higher layer or the service topology between VPN network performance on the topology at higher layer or the service
sites. topology between VPN sites.
The YANG model defined in this document is designed as an
augmentation to the network topology YANG model defined in RFC 8345
and draws on relevant YANG types defined in RFC 6991, RFC 8345, and
RFC 8532.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 7, 2022.
This Internet-Draft will expire on 23 July 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 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/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Revised BSD License text as
include Simplified BSD License text as described in Section 4.e of described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as provided without warranty as described in the Revised BSD License.
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Network and VPN Service Performance Monitoring Model Usage . 3 3. Network and VPN Service Performance Monitoring Model Usage . 3
3.1. Collecting Data via Pub/Sub Mechanism . . . . . . . . . . 5 3.1. Collecting Data via Pub/Sub Mechanism . . . . . . . . . . 5
3.2. Collecting Data via Retrieval Methods . . . . . . . . . . 5 3.2. Collecting Data via Retrieval Methods . . . . . . . . . . 5
4. Description of The Data Model . . . . . . . . . . . . . . . . 5 4. Description of The Data Model . . . . . . . . . . . . . . . . 5
4.1. Layering Relationship between Multiple Layers of Topology 5 4.1. Layering Relationship between Multiple Layers of
Topology . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2. Network Level . . . . . . . . . . . . . . . . . . . . . . 7 4.2. Network Level . . . . . . . . . . . . . . . . . . . . . . 7
4.3. Node Level . . . . . . . . . . . . . . . . . . . . . . . 7 4.3. Node Level . . . . . . . . . . . . . . . . . . . . . . . 8
4.4. Link and Termination Point Level . . . . . . . . . . . . 8 4.4. Link and Termination Point Level . . . . . . . . . . . . 9
5. Network and VPN Service Performance Monitoring YANG Module . 11 5. Network and VPN Service Performance Monitoring YANG Module . 12
6. Security Considerations . . . . . . . . . . . . . . . . . . . 23 6. Security Considerations . . . . . . . . . . . . . . . . . . . 25
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 24 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 27
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 24 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 27
10.1. Normative References . . . . . . . . . . . . . . . . . . 24 10.1. Normative References . . . . . . . . . . . . . . . . . . 27
10.2. Informative References . . . . . . . . . . . . . . . . . 26 10.2. Informative References . . . . . . . . . . . . . . . . . 29
Appendix A. Illustrating Examples . . . . . . . . . . . . . . . 27 Appendix A. Illustrating Examples . . . . . . . . . . . . . . . 30
A.1. Example of Pub/Sub Retrieval . . . . . . . . . . . . . . 27 A.1. Example of Pub/Sub Retrieval . . . . . . . . . . . . . . 30
A.2. Example of RPC-based Retrieval . . . . . . . . . . . . . 29 A.2. Example of RPC-based Retrieval . . . . . . . . . . . . . 32
A.3. Example of Percentile Monitoring . . . . . . . . . . . . 30 A.3. Example of Percentile Monitoring . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34
1. Introduction 1. Introduction
[RFC8969] describes a framework for automating service and network [RFC8969] describes a framework for automating service and network
management with YANG models, proposing the performance measurement management with YANG models. It proposes that the performance
telemetry model to be tied with the service, such as Layer 3 VPN and measurement telemetry model to be tied with the service, such as
Layer 2 VPN, or network models to monitor the overall network Layer 3 VPN and Layer 2 VPN, or network models to monitor the overall
performance or Service Level Agreements (SLA). network performance or Service Level Agreements (SLA).
This document defines a YANG module [RFC7950] for both network The performance of VPN services is associated with the performance
performance monitoring and VPN service performance monitoring. This changes of the underlay network that carries VPN services, such as
module can be used to monitor and manage network performance on the the delay of the underlay tunnels and the packet loss status of the
topology level or the service topology between VPN sites, in device interfaces. Additionally, the integration of Layer 2/Layer 3
particular. 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
service topology between VPN sites, in particular.
This document does not introduce new metrics for network performance This document does not introduce new metrics for network performance
or mechanisms for measuring network performance, but uses the or mechanisms for measuring network performance, but uses the
existing mechanisms and statistics to show the performance monitoring existing mechanisms and statistics to display the performance
statistics at the network and service layers. The YANG module monitoring statistics at the network and service layers. All these
defined in this document is designed as an augmentation to the metrics are defined as unidirectional metrics.
network topology YANG model defined in [RFC8345].
This document uses the common VPN YANG module defined in The YANG module defined in this document is designed as an
[I-D.ietf-opsawg-vpn-common]. augmentation to the network topology YANG model defined in [RFC8345]
and draws on relevant YANG types defined in [RFC6991], [RFC8345],
[RFC8532], and [I-D.ietf-opsawg-vpn-common].
Appendix A provides a set of examples to illustrate the use of the Appendix A provides a set of examples to illustrate the use of the
module. module.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The following terms are defined in [RFC7950] and are used in this
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and specification:
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119][RFC8174] when, and only when, they appear in all
capitals, as shown here.
Tree diagrams used in this document follow the notation defined in * augment
[RFC8340].
* data model
* data node
The terminology for describing YANG data models is found in
[RFC7950].
The tree diagrams used in this document follow the notation defined
in [RFC8340].
3. Network and VPN Service Performance Monitoring Model Usage 3. Network and VPN Service Performance Monitoring Model Usage
Models are key for automating network management operations. Models are key for automating network management operations.
According to [RFC8969], together with service and network models, According to [RFC8969], together with service and network models,
performance measurement telemetry models are needed to monitor performance measurement telemetry models are needed to monitor
network performance to meet specific service requirements (typically network performance to meet specific service requirements (typically
captured in an SLA). The YANG module defined in this document is captured in an SLA).
designed to derive VPN or network level performance data based on
lower-level data collected via monitoring counters of the involved
devices.
+---------------+ +---------------+
| Customer | | Customer |
+-------+-------+ +-------+-------+
| |
Customer Service Models | Customer Service Models |
| |
+-------+---------+ +-------+---------+
| Service | | Service |
| Orchestration | | Orchestration |
skipping to change at page 4, line 26 skipping to change at page 4, line 26
Network Service Models | | Network and VPN Service PM Models Network Service Models | | Network and VPN Service PM Models
| | | |
+------+-+--------+ +------+-+--------+
| Network | | Network |
| Controller | | Controller |
+-------+---------+ +-------+---------+
| |
+-----------------------+------------------------+ +-----------------------+------------------------+
Network Network
Figure 1: Reference Architecture Figure 1: Reference Architecture
As shown in Figure 1, in the context of layering model architecture As shown in Figure 1, in the context of layering model architecture
described in [RFC8309], the network and VPN service performance described in [RFC8309], the network and VPN service performance
monitoring (PM) model can be used to expose some performance monitoring (PM) model can be used to expose a set of performance
information to the above layer. Such an information can be used by information to the above layer. Such information can be used by an
an orchestrator to subscribe to performance data. The network orchestrator to subscribe to performance data. The network
controller will then notify the orchestrator about corresponding controller will then notify the orchestrator about corresponding
parameter changes. parameter changes.
Before using the network and VPN service PM model, the mapping Before using the network and VPN service PM model, the mapping
between the VPN service topology and the underlying physical network between the VPN service topology and the underlying physical network
should be setup. Also, the performance monitoring data per link in should be set up.
the underlying network can be collected using network performance
measurement method such as MPLS Loss and Delay Measurement [RFC6374].
The performance monitoring information reflecting the quality of the The YANG module defined in this document is designed to derive VPN or
network or VPN service (e.g., end to end network performance data network level performance data based on lower-level data collected
between source node and destination node in the network or between via monitoring counters of the involved devices. The performance
VPN sites) can be computed and aggregated, for example, the monitoring data per link in the underlying network can be collected
information from Traffic Engineering Database (TED), defined in using a network performance measurement method such as MPLS Loss and
[RFC7471], [RFC8570], or [RFC8571] or LMAP [RFC8194]. 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
in the network or between VPN sites) can be computed and aggregated,
for example, using the information from the Traffic Engineering
Database (TED), [RFC7471] [RFC8570] [RFC8571] or LMAP [RFC8194].
The measurement and report intervals that are associated with these The measurement and report intervals that are associated with these
performance data usually depend on the configuration parameters. performance data usually depend on the configuration of the specific
measurement method or collection method or various combinations.
This document defines a network-wide measurement interval to align
measurement requirements for networks or VPN services.
In addition, the amount of performance data collected from the
devices can be huge. To avoid receiving a large amount of
operational data of VPN instances, VPN interfaces, or tunnels, the
network controller can specifically subscribe to metric-specific data
using the tagging methods defined in [I-D.ietf-netmod-node-tags].
3.1. Collecting Data via Pub/Sub Mechanism 3.1. Collecting Data via Pub/Sub Mechanism
Some applications such as service-assurance applications, which must Some applications such as service-assurance applications, which must
maintain a continuous view of operational data and state, can use the maintain a continuous view of operational data and state, can use the
subscription model [RFC8641] to subscribe to the specific network subscription model specified in[RFC8641] to subscribe to the specific
performance data or VPN service performance data they are interested network performance data or VPN service performance data they are
in, at the data source. interested in, at the data source.
The data source can, then, use the network and VPN service assurance The data source can, then, use the network and VPN service assurance
model defined in this document and the YANG Push model [RFC8641] to model defined in this document and the YANG Push model [RFC8641] to
distribute specific telemetry data to target recipients. distribute specific telemetry data to target recipients.
3.2. Collecting Data via Retrieval Methods 3.2. Collecting Data via Retrieval Methods
To obtain a snapshot of a large amount of performance data from a To obtain a snapshot of a large amount of performance data from a
network element (including network controllers), service-assurance network element (including network controllers), service-assurance
applications may use methods such as retrieving performance data or applications may use methods such as retrieving performance data or
skipping to change at page 6, line 8 skipping to change at page 6, line 20
Layer 2 (L2), and Layer 3 (L3). This service topology has the Layer 2 (L2), and Layer 3 (L3). This service topology has the
generic topology elements of node, link, and terminating point. One generic topology elements of node, link, and terminating point. One
typical example of a service topology is described in Figure 3 of typical example of a service topology is described in Figure 3 of
[RFC8345]: two VPN service topologies instantiated over a common L3 [RFC8345]: two VPN service topologies instantiated over a common L3
topology. Each VPN service topology is mapped onto a subset of nodes topology. Each VPN service topology is mapped onto a subset of nodes
from the common L3 topology. from the common L3 topology.
Figure 3 illustrates an example of a topology that maps between the Figure 3 illustrates an example of a topology that maps between the
VPN service topology and an underlying network: VPN service topology and an underlying network:
VPN 1 VPN 2 VPN 1 VPN 2
+-----------------------+ +---------------------+ +-----------------------+ +---------------------+
/S1C-[VN3]... / /S2A S2B / / / / /
/ / \ ::::: / / -[VN1]______[VN3]- / /S1C_[VN3]::: / /S2A S2B /
/ / \ : / / : : / / \ ::::: / / _[VN1]______[VN3]_ /
/ / \ S1A :: : : : : : : / / \ : / / : : /Service Overlay
/S1B-[VN2]____[VN1]-- / / : : : / / \ :: : : : : : : /
+--------:-------:------+ +---:----:----------:-+ /S1B_[VN2]____[VN1]_S1A / / : : : /
: : :: : : : : +--------:-------:------+ +---:----:----------:-+
: : : : : : : :: : : : :
Site-1A : +-------:--: ----- -------- : -------:-----+ Site-1C : : : : :
[CE1]___: /__ ___ [N1]__________________ [N2]__ :___ /__[CE3] Site-1A : +-------:--: ----- -------- : -------:-----+ Site-1C
:/ / / \ _____/ / : / [CE1]___: /__ ___ [N1]__________________ [N2]__ :___ /__[CE3]
[CE5]___ : ___ / / \ _____/ / :: / :/ / / \ _____/ / : /
Site-2A /: / \ / / : / [CE5]___ : ___ / / \ _____/ / :: /
/ : [N5] / : / Site-2A /: / \ / / : /
/ : / __/ \__ / : / / : [N5] / : / Underlay Network
/ : / ___/ \__ / : / / : / __/ \__ / : /
Site-1B / : / ___/ \ / : / Site-2B / : / ___/ \__ / : /
[CE2]-/------- [N4]_________________ [N3]:::-----/----[CE4] Site-1B / : / ___/ \ / : / Site-2B
+------------------------------------------+ [CE2]_ /________[N4]_________________ [N3]:::_____/____[CE4]
+------------------------------------------+
Legend: N:node VN:VPN-Node Legend:
N:node VN:VPN-Node S:Site
__ Link
: Mapping between networks
Figure 3: Example of Topology Mapping Between VPN Service Topology Figure 3: Example of Topology Mapping Between VPN Service
and Underlying Network Topology and Underlying Network
As shown in Figure 3, two VPN services topologies are both built on As shown in Figure 3, two VPN services topologies are both built on
top of one common underlying physical network: top of one common underlying physical network:
VPN 1: This service topology supports hub-spoke communications for VPN 1: This service topology supports hub-spoke communications for
'customer 1' connecting the customer's access at three sites: 'customer 1' connecting the customer's access at three sites:
'Site-1A', 'Site-1B', and 'Site-1C'. These sites are connected to '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) 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 in the underlying physical network. 'Site-1A' plays the role of
hub while 'Site-1B' and 'Site-1C' are configured as spoke. hub while 'Site-1B' and 'Site-1C' are configured as spoke.
VPN 2: This service supports any-to-any communications for VPN 2: This service supports any-to-any communications for 'customer
'customer 2' connecting the customer's access at two sites: 'Site- 2' connecting the customer's access at two sites: 'Site-2A' and
2A' and 'Site-2B'. These sites are connected to nodes that are 'Site-2B'. These sites are connected to nodes that are mapped to
mapped to nodes 1 (N1) and node 3 (N3)5 in the underlying physical nodes 1 (N1) and node 3 (N3)5 in the underlying physical network.
network. 'Site-2A' and 'Site-2B' have 'any-to-any' role. 'Site-2A' and 'Site-2B' have 'any-to-any' role.
4.2. Network Level 4.2. Network Level
For network performance monitoring, the container of "networks" in For network performance monitoring, the container of "networks" in
[RFC8345] do not need to be extended. [RFC8345] does not need to be extended.
For VPN service performance monitoring, the container "service-type" For VPN service performance monitoring, the container "service-type"
is defined to indicate the VPN type, e.g., L3VPN or Virtual Private is defined to indicate the VPN type, e.g., L3VPN or Virtual Private
LAN Service (VPLS). The values are taken from LAN Service (VPLS). The values are taken from
[I-D.ietf-opsawg-vpn-common]. When a network topology instance [I-D.ietf-opsawg-vpn-common]. When a network topology instance
contains the L3VPN or other L2VPN network type, it represents a VPN contains the L3VPN or other L2VPN network type, it represents a VPN
instance that can perform performance monitoring. instance that can perform performance monitoring.
This model defines the following set of network level attributes: The tree in Figure 4 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 "vpn-id": Refers to an identifier of VPN service defined in
[I-D.ietf-opsawg-vpn-common]). This identifier is used to [I-D.ietf-opsawg-vpn-common]). This identifier is used to
correlate the performance status with the network service correlate the performance status with the network service
configuration. configuration.
"vpn-service-topology": Indicates the type of VPN topology. This "vpn-service-topology": Indicates the type of the VPN topology.
model supports "any-to-any", "Hub and Spoke" (where Hubs can This model supports "any-to-any", "Hub and Spoke" (where Hubs can
exchange traffic), and "Hub and Spoke disjoint" (where Hubs cannot exchange traffic), and "Hub and Spoke disjoint" (where Hubs cannot
exchange traffic) that are taken from exchange traffic) that are taken from
[I-D.ietf-opsawg-vpn-common]. These VPN topology types can be [I-D.ietf-opsawg-vpn-common]. These VPN topology types can be
used to describe how VPN sites communicate with each other. used to describe how VPN sites communicate with each other.
module: ietf-network-vpn-pm module: ietf-network-vpn-pm
augment /nw:networks/nw:network/nw:network-types: augment /nw:networks/nw:network/nw:network-types:
+--rw service-type! +--rw service-type!
+--rw service-type? identityref +--rw service-type? identityref
augment /nw:networks/nw:network: augment /nw:networks/nw:network:
+--rw vpn-pm-attributes +--rw vpn-pm-attributes
+--rw vpn-id? vpn-common:vpn-id +--rw vpn-id? vpn-common:vpn-id
+--rw vpn-service-topology? identityref +--rw vpn-service-topology? identityref
Figure 4: Network Level View of the Hierarchies Figure 4: Network Level YANG Tree of the Hierarchies
4.3. Node Level 4.3. Node Level
The tree in Figure 5 is the node part of ietf-network-vpn-pm tree.
For network performance monitoring, a container of "pm-attributes" is For network performance monitoring, a container of "pm-attributes" is
augmented to the list of "node" that are defined in [RFC8345]. And augmented to the list of "node" that are defined in [RFC8345]. The
the leaf of "node-type" indicates the device type of Provider Edge "node-type" indicates the device type of Provider Edge (PE), Provider
(PE), Provider (P) device, or Autonomous System Border Router (ASBR), (P) device, or Autonomous System Border Router (ASBR), so that the
so that the performance metric between any two nodes each with performance metric between any two nodes each with specific node type
specific node type can be reported. can be reported.
For VPN service performance monitoring, this model defines only the For VPN service performance monitoring, the model defines the
following minimal set of node level network topology attributes: following minimal set of node level network topology attributes:
"role": Defines the role in a particular VPN service topology. The "role": Defines the role in a particular VPN service topology. The
roles are taken from [I-D.ietf-opsawg-vpn-common] (e.g., any-to- roles are taken from [I-D.ietf-opsawg-vpn-common] (e.g., any-to-
any-role, spoke-role, hub-role). any-role, spoke-role, hub-role).
"vpn-summary-statistics": Lists a set of IPv4 statistics, IPv6 "vpn-summary-statistics": Lists a set of IPv4 statistics, IPv6
statistics, and MAC statistics. These statistics are specified statistics, and MAC statistics. These statistics are specified
separately. separately.
skipping to change at page 8, line 28 skipping to change at page 9, line 5
+--ro ipv4 +--ro ipv4
| +--ro maximum-routes? uint32 | +--ro maximum-routes? uint32
| +--ro total-active-routes? uint32 | +--ro total-active-routes? uint32
+--ro ipv6 +--ro ipv6
| +--ro maximum-routes? uint32 | +--ro maximum-routes? uint32
| +--ro total-active-routes? uint32 | +--ro total-active-routes? uint32
+--ro mac-num +--ro mac-num
+--ro mac-num-limit? uint32 +--ro mac-num-limit? uint32
+--ro total-active-mac-num? uint32 +--ro total-active-mac-num? uint32
Figure 5: Node Level View of the Hierarchies Figure 5: Node Level YANG Tree of the Hierarchies
4.4. Link and Termination Point Level 4.4. Link and Termination Point Level
The tree in Figure 6 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 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.
The performance data of a link is a collection of counters that The performance data of a link is a collection of counters that
report the performance status. report the performance status.
augment /nw:networks/nw:network/nt:link: augment /nw:networks/nw:network/nt:link:
+--rw pm-attributes +--rw pm-attributes
+--rw low-percentile? percentile +--rw low-percentile? percentile
+--rw middle-percentile? percentile +--rw middle-percentile? percentile
+--rw high-percentile? percentile +--rw high-percentile? percentile
+--ro pm-source? string +--rw measurement-interval? uint32
+--ro reference-time? yang:date-and-time +--ro reference-time? yang:date-and-time
+--ro measurement-interval? uint32 +--ro pm-source? identityref
+--ro pm-statistics +--ro one-way-pm-statistics
| +--ro loss-statistics | +--ro loss-statistics
| | +--ro packet-loss-count? yang:counter64 | | +--ro packet-loss-count? yang:counter64
| | +--ro packet-reorder-count? yang:counter64 | | +--ro loss-ratio? percentage
| | +--ro packets-out-of-seq-count? yang:counter64
| | +--ro packets-dup-count? yang:counter64
| | +--ro loss-ratio? percentage
| +--ro delay-statistics | +--ro delay-statistics
| | +--ro direction? identityref
| | +--ro unit-value? identityref | | +--ro unit-value? identityref
| | +--ro min-delay-value? yang:gauge64 | | +--ro min-delay-value? yang:gauge64
| | +--ro max-delay-value? yang:gauge64 | | +--ro max-delay-value? yang:gauge64
| | +--ro low-delay-percentile? yang:gauge64 | | +--ro low-delay-percentile? yang:gauge64
| | +--ro middle-delay-percentile? yang:gauge64 | | +--ro middle-delay-percentile? yang:gauge64
| | +--ro high-delay-percentile? yang:gauge64 | | +--ro high-delay-percentile? yang:gauge64
| +--ro jitter-statistics | +--ro jitter-statistics
| +--ro unit-value? identityref | +--ro unit-value? identityref
| +--ro min-jitter-value? yang:gauge32 | +--ro min-jitter-value? yang:gauge32
| +--ro max-jitter-value? yang:gauge32 | +--ro max-jitter-value? yang:gauge32
| +--ro low-jitter-percentile? yang:gauge32 | +--ro low-jitter-percentile? yang:gauge32
| +--ro middle-jitter-percentile? yang:gauge32 | +--ro middle-jitter-percentile? yang:gauge32
| +--ro high-jitter-percentile? yang:gauge32 | +--ro high-jitter-percentile? yang:gauge32
+--ro protocol-type? identityref +--ro vpn-underlay-transport-type? identityref
+--ro vpn-one-way-pm-statistics* [class-id]
+--ro class-id string
+--ro loss-statistics
| +--ro packet-loss-count? yang:counter64
| +--ro loss-ratio? percentage
+--ro delay-statistics
| +--ro unit-value? identityref
| +--ro min-delay-value? yang:gauge64
| +--ro max-delay-value? yang:gauge64
| +--ro low-delay-percentile? yang:gauge64
| +--ro middle-delay-percentile? yang:gauge64
| +--ro high-delay-percentile? yang:gauge64
+--ro jitter-statistics
+--ro unit-value? identityref
+--ro min-jitter-value? yang:gauge32
+--ro max-jitter-value? yang:gauge32
+--ro low-jitter-percentile? yang:gauge32
+--ro middle-jitter-percentile? yang:gauge32
+--ro high-jitter-percentile? yang:gauge32
augment /nw:networks/nw:network/nw:node/nt:termination-point: augment /nw:networks/nw:network/nw:node/nt:termination-point:
+--ro pm-statistics +--ro pm-statistics
+--ro reference-time? yang:date-and-time
+--ro inbound-octets? yang:counter64 +--ro inbound-octets? yang:counter64
+--ro inbound-unicast? yang:counter64 +--ro inbound-unicast? yang:counter64
+--ro inbound-nunicast? yang:counter64 +--ro inbound-nunicast? yang:counter64
+--ro inbound-discards? yang:counter32 +--ro inbound-discards? yang:counter32
+--ro inbound-errors? yang:counter64 +--ro inbound-errors? yang:counter64
+--ro inbound-unknown-protocol? yang:counter64 +--ro inbound-unknown-protocol? yang:counter64
+--ro outbound-octets? yang:counter64 +--ro outbound-octets? yang:counter64
+--ro outbound-unicast? yang:counter64 +--ro outbound-unicast? yang:counter64
+--ro outbound-nunicast? yang:counter64 +--ro outbound-nunicast? yang:counter64
+--ro outbound-discards? yang:counter64 +--ro outbound-discards? yang:counter64
+--ro outbound-errors? yang:counter64 +--ro outbound-errors? yang:counter64
+--ro vpn-network-access* [network-access-id]
+--ro network-access-id vpn-common:vpn-id
+--ro reference-time? yang:date-and-time
+--ro inbound-octets? yang:counter64
+--ro inbound-unicast? yang:counter64
+--ro inbound-nunicast? yang:counter64
+--ro inbound-discards? yang:counter32
+--ro inbound-errors? yang:counter64
+--ro inbound-unknown-protocol? yang:counter64
+--ro outbound-octets? yang:counter64
+--ro outbound-unicast? yang:counter64
+--ro outbound-nunicast? yang:counter64
+--ro outbound-discards? yang:counter64
+--ro outbound-errors? yang:counter64
Figure 6: Link and Termination point Level View of the hierarchies Figure 6: Link and Termination point Level YANG Tree of the
hierarchies
For the data nodes of 'link' depicted in Figure 6, the YANG module For the data nodes of 'link' depicted in Figure 6, the YANG module
defines the following minimal set of link-level performance defines the following minimal set of link-level performance
attributes: attributes:
Percentile parameters: The module supports reporting delay and Percentile parameters: The module supports reporting delay and
jitter metric by percentile values. By default, low percentile jitter metric by percentile values. By default, low percentile
(10th percentile), mid percentile (50th percentile), high (10th percentile), mid percentile (50th percentile), high
percentile (90th percentile) are used. Setting a percentile into percentile (90th percentile) are used. Setting a percentile to
0.00 indicates the client is not interested in receiving 0.00 indicates the client is not interested in receiving
particular percentile. If all percentile nodes are set to 0.00, particular percentile. If all percentile nodes are set to 0.00,
this represents that no percentile related nodes will be reported this represents that no percentile related nodes will be reported
for a given performance metric (e.g. one-way delay, one-way delay for a given performance metric (e.g., one-way delay, one-way delay
variation) and only peak/min values will be reported. For variation) and only peak/min values will be reported. For
example, a client can inform the server that it is interested in example, a client can inform the server that it is interested in
receiving only high percentiles. Then for a given link, at a receiving only high percentiles. Then for a given link, at a
given "reference-time" "measurement-interval", the 'high-delay- given "reference-time" and "measurement-interval", the 'high-
percentile' and 'high-jitter-percentile' will be reported. An delay-percentile' and 'high-jitter-percentile' will be reported.
example to illustrate the use of percentiles is provided in An example to illustrate the use of percentiles is provided in
Appendix A.3. Appendix A.3.
"pm-source": Indicates the performance monitoring source. The data PM source ("pm-source"): Indicates the performance monitoring
for the topology link can be based, e.g., on BGP-LS [RFC8571]. source. The data for the topology link can be based, e.g., on
The statistics of the VPN abstract links can be collected based BGP-LS [RFC8571]. The statistics of the VPN abstract links can be
upon VPN OAM mechanisms, e.g., OAM mechanisms specified in collected based upon VPN OAM mechanisms, e.g., OAM mechanisms
[I-D.ietf-opsawg-l3sm-l3nm], or Ethernet service OAM specified in specified in [I-D.ietf-opsawg-l3sm-l3nm], or Ethernet service OAM
[I-D.ietf-opsawg-l2nm]. Alternatively, the data can be based upon specified in [I-D.ietf-opsawg-l2nm]. Alternatively, the data can
the underlay technology OAM mechanisms, for example, GRE tunnel be based upon the underlay technology OAM mechanisms, for example,
OAM. GRE tunnel OAM.
Loss Statistics: A set of loss statistics attributes that are used Measurement interval ("measurement-interval"): Specifies the
to measure end to end loss between VPN sites or between any two performance measurement interval, in seconds.
network nodes. The exact loss value or the loss percentage can be
reported.
Delay Statistics: A set of delay statistics attributes that are used Reference time ("reference-time"): Indicates the start time of the
to measure end to end latency between VPN sites or between any two performance measurement for link statistics. For termination
network nodes. The peak/min values or percentile values can be point metrics, this parameter indicates the timestamp when the
reported. counters are obtained.
Jitter Statistics: A set of IP Packet Delay Variation [RFC3393] Loss statistics: A set of one-way loss statistics attributes that
statistics attributes that are used to measure end to end jitter are used to measure end to end loss between VPN sites or between
between VPN sites or between any two network nodes. The peak/min any two network nodes. The exact loss value or the loss
values or percentile values can be reported. percentage can be reported.
"protocol-type": Indicates the abstract link protocol-type of a VPN, Delay statistics: A set of one-way delay statistics attributes that
such as GRE or IP-in-IP. The leaf refers to an identifier of the are used to measure end to end latency between VPN sites or
"underlay-transport" defined in [I-D.ietf-opsawg-vpn-common], between any two network nodes. The peak/min values or percentile
which describes the transport technology to carry the traffic of values can be reported.
the VPN service.
Jitter statistics: A set of one-way IP Packet Delay Variation
[RFC3393] statistics attributes that are used to measure end to
end jitter between VPN sites or between any two network nodes.
The peak/min values or percentile values can be reported.
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 [I-D.ietf-opsawg-vpn-common], which describes the
transport technology to carry the traffic of the VPN service.
VPN PM statistics ("vpn-unidirectional-pm-statistics"): Lists
performance measurement statistics for the abstract underlay link
between VPN PEs with given "class-id" names. The list is defined
separately from "one-way-pm-statistics", which is used to collect
generic metrics for unspecified "class-id" names.
For the data nodes of 'termination-point' depicted in Figure 6, the For the data nodes of 'termination-point' depicted in Figure 6, the
module defines the following minimal set of statistics: module defines the following minimal set of statistics:
Inbound statistics: A set of inbound statistics attributes that are Inbound statistics: A set of inbound statistics attributes that are
used to measure the inbound statistics of the termination point, used to measure the inbound statistics of the termination point,
such as received packets, received packets with errors, etc. such as received packets, received packets with errors, etc.
Outbound statistics: A set of outbound statistics attributes that Outbound statistics: A set of outbound statistics attributes that
are used to measure the outbound statistics of the termination are used to measure the outbound statistics of the termination
point, such as sent packets, packets that could not be sent due to point, such as sent packets, packets that could not be sent due to
errors, etc. errors, etc.
VPN network access ("vpn-network-access"): Lists counters of the VPN
network access defined in [I-D.ietf-opsawg-l3sm-l3nm] or
[I-D.ietf-opsawg-l2nm]. When multiple VPN network accesses are
created using the same physical port, finer-grained metrics can be
monitored.
5. Network and VPN Service Performance Monitoring YANG Module 5. Network and VPN Service Performance Monitoring YANG Module
The "ietf-network-vpn-pm" module uses types defined in [RFC8345], The "ietf-network-vpn-pm" module uses types defined in [RFC8345],
[RFC6991], and [RFC8532]. [RFC6991], [RFC8532], and [I-D.ietf-opsawg-vpn-common].
<CODE BEGINS> file "ietf-network-vpn-pm@2021-07-06.yang" <CODE BEGINS> file "ietf-network-vpn-pm@2021-01-18.yang"
module ietf-network-vpn-pm { module ietf-network-vpn-pm {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm"; namespace "urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm";
prefix nvp; prefix nvp;
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
reference reference
"RFC 6991: Common YANG Types"; "RFC 6991: Common YANG Types";
} }
import ietf-vpn-common { import ietf-vpn-common {
prefix vpn-common; prefix vpn-common;
reference reference
"RFC CCCC: A Layer 2/3 VPN Common YANG Model"; "RFC XXXX: A Layer 2/3 VPN Common YANG Model.";
} // RFC Ed.: replace XXXX with actual RFC number and remove
import ietf-network { // this note.
prefix nw; }
reference import ietf-network {
"RFC 8345: A YANG Data Model for Network prefix nw;
Topologies, Section 6.1"; reference
} "RFC 8345: A YANG Data Model for Network
import ietf-network-topology { Topologies, Section 6.1";
prefix nt; }
reference import ietf-network-topology {
"RFC 8345: A YANG Data Model for Network prefix nt;
Topologies, Section 6.2"; reference
} "RFC 8345: A YANG Data Model for Network
import ietf-lime-time-types { Topologies, Section 6.2";
prefix lime; }
reference import ietf-lime-time-types {
"RFC 8532: Generic YANG Data Model for the Management of prefix lime;
Operations, Administration, and Maintenance reference
(OAM) Protocols That Use Connectionless Communications"; "RFC 8532: Generic YANG Data Model for the Management of
} Operations, Administration, and Maintenance
(OAM) Protocols That Use Connectionless Communications";
}
organization organization
"IETF OPSAWG Working Group"; "IETF OPSAWG Working Group";
contact contact
"Editor: Qin Wu "Editor: Qin Wu
<bill.wu@huawei.com> <bill.wu@huawei.com>
Editor: Bo Wu Editor: Bo Wu
<lana.wubo@huawei.com> <lana.wubo@huawei.com>
Editor: Mohamed Boucadair Editor: Mohamed Boucadair
<mohamed.boucadair@orange.com>"; <mohamed.boucadair@orange.com>";
description description
"This module defines a model for Network and VPN Service Performance "This module defines a model for Network and VPN Service Performance
monitoring. monitoring.
Copyright (c) 2021 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
This version of this YANG module is part of RFC XXXX; see // RFC Ed.: update the date below with the date of RFC
the RFC itself for full legal notices."; // publication and remove this note.
// RFC Ed.: replace XXXX with actual RFC number and remove
// this note.
revision 2021-07-06 { revision 2022-01-18 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Model for Network and VPN Service Performance "RFC XXXX: A YANG Model for Network and VPN Service Performance
Monitoring"; Monitoring";
} }
identity node-type { identity node-type {
description description
"Base identity for node type"; "Base identity for node type";
} }
identity pe { identity pe {
base node-type; base node-type;
description description
"Identity for Provider Edge (PE) type."; "Provider Edge (PE) node type.";
} }
identity asbr { identity asbr {
base node-type; base node-type;
description description
"Identity for Autonomous System Border Router (ASBR) type."; "Autonomous System Border Router (ASBR) node type.";
} }
identity p { identity p {
base node-type; base node-type;
description description
"Identity for P type."; "P node type.";
} }
identity direction { identity pm-source-type {
description description
"Base identity for measurement direction including "Base identity from which specific performance monitoring
one-way measurement and two-way measurement."; mechanism types are derived.";
} }
identity one-way { identity pm-source-bgpls {
base direction; base pm-source-type;
description description
"Identity for one-way measurement."; "Indicates BGP-LS as the performance monitoring metric source";
} reference
"RFC8571: BGP - Link State (BGP-LS) Advertisement of
IGP Traffic Engineering Performance Metric Extensions";
}
identity two-way { identity pm-source-twamp {
base direction; base pm-source-type;
description description
"Identity for two-way measurement."; "Indicates Two-Way Active Measurement Protocol(TWAMP)
} as the performance monitoring metric source.";
reference
"RFC5357: : A Two-Way Active Measurement Protocol (TWAMP)";
}
typedef percentage { identity pm-source-y-1731 {
type decimal64 { base pm-source-type;
fraction-digits 5; description
range "0..100"; "Indicates Ethernet OAM Y.1731 as the performance monitoring
} metric source.";
description reference
"Percentage."; "ITU-T Y.1731";
} }
typedef percentile { typedef percentage {
type decimal64 { type decimal64 {
fraction-digits 5; fraction-digits 5;
} range "0..100";
description }
"The percentile is a statistical value that indicates that a description
certain percentage of a set of data falls below it."; "Percentage.";
} }
grouping vpn-summary-statistics { typedef percentile {
description type decimal64 {
"VPN Statistics grouping used for network topology fraction-digits 5;
augmentation."; range "1..100";
container vpn-summary-statistics { }
config false; description
description "The percentile is a statistical value that indicates that a
"Container for VPN summary statistics."; certain percentage of a set of data falls below it.";
container ipv4 { }
leaf maximum-routes {
type uint32;
description
"Total routes for the VPN.";
}
leaf total-active-routes {
type uint32;
description
"Total active routes for the VPN.";
}
description
"IPv4-specific parameters.";
}
container ipv6 {
leaf maximum-routes {
type uint32;
description
"Total routes for the VPN.";
}
leaf total-active-routes {
type uint32;
description
"Total active routes for the VPN.";
}
description
"IPv6-specific parameters.";
}
container mac-num {
leaf mac-num-limit {
type uint32;
description
"Maximum number of MAC addresses.";
}
leaf total-active-mac-num {
type uint32;
description
"Total active MAC entries for the VPN.";
}
description
"MAC statistics.";
}
}
}
grouping link-error-statistics { grouping vpn-summary-statistics {
description description
"Grouping for per link error statistics."; "VPN Statistics grouping used for network topology
container loss-statistics { augmentation.";
description container vpn-summary-statistics {
"Per link loss statistics."; config false;
leaf packet-loss-count { description
type yang:counter64; "Container for VPN summary statistics.";
description container ipv4 {
"Total received packet drops count."; leaf maximum-routes {
} type uint32;
leaf packet-reorder-count { description
type yang:counter64; "Indicates the maximum number of IPv4 routes for the VPN.";
description }
"Total received packet reordered count."; leaf total-active-routes {
} type uint32;
leaf packets-out-of-seq-count { description
type yang:counter64; "Indicates total active IPv4 routes for the VPN.";
description }
"Total received out of sequence count."; description
} "IPv4-specific parameters.";
leaf packets-dup-count { }
type yang:counter64; container ipv6 {
description leaf maximum-routes {
"Total received packet duplicates count."; type uint32;
} description
leaf loss-ratio { "Indicates the maximum number of IPv6 routes for the VPN.";
type percentage; }
description leaf total-active-routes {
"Loss ratio of the packets. Express as percentage type uint32;
of packets lost with respect to packets sent."; description
} "Indicates total active IPv6 routes for the VPN.";
} }
} description
"IPv6-specific parameters.";
}
container mac-num {
leaf mac-num-limit {
type uint32;
description
"Maximum number of MAC addresses.";
}
leaf total-active-mac-num {
type uint32;
description
"Total active MAC entries for the VPN.";
}
description
"MAC statistics.";
}
}
}
grouping link-loss-statistics {
description
"Grouping for per link error statistics.";
container loss-statistics {
description
"Per link loss statistics.";
leaf packet-loss-count {
type yang:counter64;
description
"Total received packet drops count.";
}
leaf loss-ratio {
type percentage;
description
"Loss ratio of the packets. Express as percentage
of packets lost with respect to packets sent.";
}
}
}
grouping link-delay-statistics { grouping link-delay-statistics {
description description
"Grouping for per link delay statistics"; "Grouping for per link delay statistics.";
container delay-statistics {
description
"Link delay summarized information. By default,
one way measurement protocol (e.g., OWAMP) is used
to measure delay.";
leaf unit-value {
type identityref {
base lime:time-unit-type;
}
default "lime:milliseconds";
description
"Time units, where the options are s, ms, ns, etc.";
}
leaf min-delay-value {
type yang:gauge64;
description
"Minimum observed one-way delay.";
}
leaf max-delay-value {
type yang:gauge64;
description
"Maximum observed one-way delay.";
}
leaf low-delay-percentile {
type yang:gauge64;
description
"Low percentile of observed one-way delay with
specific measurement method.";
}
leaf middle-delay-percentile {
type yang:gauge64;
description
"Middle percentile of observed one-way delay with
specific measurement method.";
}
leaf high-delay-percentile {
type yang:gauge64;
description
"High percentile of observed one-way delay with
specific measurement method.";
}
}
}
container delay-statistics { grouping link-jitter-statistics {
description description
"Link delay summarised information. By default, "Grouping for per link jitter statistics.";
one way measurement protocol (e.g., OWAMP) is used container jitter-statistics {
to measure delay."; description
leaf direction { "Link jitter summarized information. By default,
type identityref { jitter is measured using one-way IP Packet Delay Variation
base direction; (IPDV).";
} leaf unit-value {
default "one-way"; type identityref {
description base lime:time-unit-type;
"Define measurement direction including one way }
measurement and two way measurement."; default "lime:milliseconds";
} description
leaf unit-value { "Time units, where the options are s, ms, ns, etc.";
type identityref { }
base lime:time-unit-type; leaf min-jitter-value {
} type yang:gauge32;
default "lime:milliseconds"; description
description "Minimum observed one-way jitter.";
"Time units, where the options are s, ms, ns, etc."; }
} leaf max-jitter-value {
leaf min-delay-value { type yang:gauge32;
type yang:gauge64; description
description "Maximum observed one-way jitter.";
"Minimum delay value observed."; }
} leaf low-jitter-percentile {
leaf max-delay-value { type yang:gauge32;
type yang:gauge64; description
description "Low percentile of observed one-way jitter.";
"Maximum delay value observed."; }
} leaf middle-jitter-percentile {
leaf low-delay-percentile { type yang:gauge32;
type yang:gauge64; description
description "Middle percentile of observed one-way jitter.";
"Low percentile of the delay observed with }
specific measurement method."; leaf high-jitter-percentile {
} type yang:gauge32;
leaf middle-delay-percentile { description
type yang:gauge64; "High percentile of observed one-way jitter.";
description }
"Middle percentile of the delay observed with }
specific measurement method."; }
}
leaf high-delay-percentile {
type yang:gauge64;
description
"High percentile of the delay observed with
specific measurement method.";
}
}
}
grouping link-jitter-statistics { grouping tp-svc-telemetry {
description leaf reference-time {
"Grouping for per link jitter statistics"; type yang:date-and-time;
container jitter-statistics { config false;
description description
"Link jitter summarised information. By default, "Indicates the time when the statistics are collected.";
jitter is measured using IP Packet Delay Variation }
(IPDV)."; leaf inbound-octets {
leaf unit-value { type yang:counter64;
type identityref { description
base lime:time-unit-type; "The total number of octets received on the
} interface, including framing characters.";
default "lime:milliseconds"; }
description leaf inbound-unicast {
"Time units, where the options are s, ms, ns, etc."; type yang:counter64;
} description
leaf min-jitter-value { "Inbound unicast packets were received, and delivered
type yang:gauge32; to a higher layer during the last period.";
description }
"Minimum jitter value observed."; leaf inbound-nunicast {
} type yang:counter64;
leaf max-jitter-value { description
type yang:gauge32; "The number of non-unicast (i.e., subnetwork-
description broadcast or subnetwork-multicast) packets
"Maximum jitter value observed."; delivered to a higher-layer protocol.";
} }
leaf low-jitter-percentile { leaf inbound-discards {
type yang:gauge32; type yang:counter32;
description description
"Low percentile of the jitter observed."; "The number of inbound packets which were chosen
} to be discarded even though no errors had been
leaf middle-jitter-percentile { detected to prevent their being deliverable to a
type yang:gauge32; higher-layer protocol.";
description
"Middle percentile of the jitter observed.";
}
leaf high-jitter-percentile {
type yang:gauge32;
description
"High percentile of the jitter observed.";
}
}
}
grouping tp-svc-telemetry {
leaf inbound-octets {
type yang:counter64;
description
"The total number of octets received on the
interface, including framing characters.";
}
leaf inbound-unicast {
type yang:counter64;
description
"Inbound unicast packets were received, and delivered
to a higher layer during the last period.";
}
leaf inbound-nunicast {
type yang:counter64;
description
"The number of non-unicast (i.e., subnetwork-
broadcast or subnetwork-multicast) packets
delivered to a higher-layer protocol.";
}
leaf inbound-discards {
type yang:counter32;
description
"The number of inbound packets which were chosen
to be discarded even though no errors had been
detected to prevent their being deliverable to a
higher-layer protocol.";
}
leaf inbound-errors {
type yang:counter64;
description
"The number of inbound packets that contained
errors preventing them from being deliverable to a
higher-layer protocol.";
}
leaf inbound-unknown-protocol {
type yang:counter64;
description
"The number of packets received via the interface
which were discarded because of an unknown or
unsupported protocol.";
}
leaf outbound-octets {
type yang:counter64;
description
"The total number of octets transmitted out of the
interface, including framing characters.";
}
leaf outbound-unicast {
type yang:counter64;
description
"The total number of packets that higher-level
protocols requested be transmitted to a
subnetwork-unicast address, including those that
were discarded or not sent.";
}
leaf outbound-nunicast {
type yang:counter64;
description
"The total number of packets that higher-level
protocols requested be transmitted to a non-
unicast (i.e., a subnetwork-broadcast or
subnetwork-multicast) address, including those
that were discarded or not sent.";
}
leaf outbound-discards {
type yang:counter64;
description
"The number of outbound packets which were chosen
to be discarded even though no errors had been
detected to prevent their being transmitted. One
possible reason for discarding such a packet could
be to free up buffer space.";
}
leaf outbound-errors {
type yang:counter64;
description
"The number of outbound packets that contained
errors preventing them from being deliverable to a
higher-layer protocol.";
}
description
"Grouping for interface service telemetry.";
}
augment "/nw:networks/nw:network/nw:network-types" { }
description leaf inbound-errors {
"Defines the service topologies types"; type yang:counter64;
container service-type { description
presence "Indicates Network service topology"; "The number of inbound packets that contained
leaf service-type { errors preventing them from being deliverable to a
type identityref { higher-layer protocol.";
base vpn-common:service-type; }
} leaf inbound-unknown-protocol {
description type yang:counter64;
"The presence identifies the network service type, description
e.g., L3VPN, VPLS, etc."; "The number of packets received via the interface
} which were discarded because of an unknown or
description unsupported protocol.";
"Container for VPN service type."; }
} leaf outbound-octets {
} type yang:counter64;
description
"The total number of octets transmitted out of the
interface, including framing characters.";
}
leaf outbound-unicast {
type yang:counter64;
description
"The total number of packets that higher-level
protocols requested be transmitted to a
subnetwork-unicast address, including those that
were discarded or not sent.";
}
leaf outbound-nunicast {
type yang:counter64;
description
"The total number of packets that higher-level
protocols requested be transmitted to a non-
unicast (i.e., a subnetwork-broadcast or
subnetwork-multicast) address, including those
that were discarded or not sent.";
}
leaf outbound-discards {
type yang:counter64;
description
"The number of outbound packets which were chosen
to be discarded even though no errors had been
detected to prevent their being transmitted. One
possible reason for discarding such a packet could
be to free up buffer space.";
}
leaf outbound-errors {
type yang:counter64;
description
"The number of outbound packets that contained
errors preventing them from being deliverable to a
higher-layer protocol.";
}
description
"Grouping for interface service telemetry.";
}
augment "/nw:networks/nw:network" { augment "/nw:networks/nw:network/nw:network-types" {
when 'nw:network-types/nvp:service-type' { description
description "Defines the service topologies types.";
"Augment only for VPN Network topology."; container service-type {
} presence "Indicates network service topology.";
description leaf service-type {
"Augment the network with service topology attributes"; type identityref {
container vpn-pm-attributes { base vpn-common:service-type;
leaf vpn-id { }
type vpn-common:vpn-id; description
description "The presence identifies the network service type,
"VPN identifier."; e.g., L3VPN, VPLS, etc.";
} }
leaf vpn-service-topology { description
type identityref { "Container for VPN service type.";
base vpn-common:vpn-topology; }
} }
description
"VPN service topology, e.g., hub-spoke, any-to-any,
hub-spoke-disjoint";
}
description
"Container for vpn topology attributes.";
}
}
augment "/nw:networks/nw:network/nw:node" { augment "/nw:networks/nw:network" {
description when 'nw:network-types/nvp:service-type' {
"Augment the network node with other general attributes"; description
container pm-attributes { "Augments only for VPN Network topology.";
leaf node-type { }
type identityref { description
base node-type; "Augments the network with service topology attributes";
} container vpn-pm-attributes {
description leaf vpn-id {
"Node type, e.g., PE, P, ASBR."; type vpn-common:vpn-id;
} description
description "VPN identifier.";
"Container for node attributes."; }
} leaf vpn-service-topology {
} type identityref {
augment "/nw:networks/nw:network/nw:node/pm-attributes" { base vpn-common:vpn-topology;
when '../../nw:network-types/nvp:service-type' { }
description description
"Augment only for VPN node attributes."; "VPN service topology, e.g., hub-spoke, any-to-any,
} hub-spoke-disjoint.";
description
"Augment the network node with VPN specific attributes";
leaf role {
type identityref {
base vpn-common:role;
}
default "vpn-common:any-to-any-role";
description
"Role of the node in the VPN.";
}
uses vpn-summary-statistics;
}
augment "/nw:networks/nw:network/nt:link" { }
description description
"Augment the network topology link with performance monitoring "Container for VPN topology attributes.";
attributes"; }
container pm-attributes { }
description
"Container for PM attributes.";
leaf low-percentile {
type percentile;
default "10.00";
description
"Low percentile to report. Setting low-percentile
into 0.00 indicates the client is not interested in receiving
low percentile.";
}
leaf middle-percentile {
type percentile;
default "50.00";
description
"Middle percentile to report. Setting middle-percentile
into 0.00 indicates the client is not interested in receiving
middle percentile.";
}
leaf high-percentile {
type percentile;
default "90.00";
description
"High percentile to report. Setting high-percentile
into 0.00 indicates the client is not interested in receiving
high percentile";
} augment "/nw:networks/nw:network/nw:node" {
leaf pm-source { description
type string; "Augments the network node with other general attributes.";
config false; container pm-attributes {
description leaf node-type {
"The OAM tool used to collect the PM data."; type identityref {
} base node-type;
leaf reference-time { }
type yang:date-and-time; description
config false; "Node type, e.g., PE, P, ASBR.";
description }
"The time that the current Measurement Interval started."; description
} "Container for node attributes.";
leaf measurement-interval { }
type uint32; }
units "seconds";
default "60";
config false;
description
"Interval to calculate performance metric.";
}
container pm-statistics {
config false;
uses link-error-statistics;
uses link-delay-statistics;
uses link-jitter-statistics;
description
"Container for service telemetry attributes.";
}
}
}
augment "/nw:networks/nw:network/nt:link/pm-attributes" { augment "/nw:networks/nw:network/nw:node/pm-attributes" {
when '../../nw:network-types/nvp:service-type' { when '../../nw:network-types/nvp:service-type' {
description description
"Augment only for VPN Network topology."; "Augments only for VPN node attributes.";
} }
description description
"Augment the network topology link with service performance "Augments the network node with VPN specific attributes.";
monitoring attributes"; leaf role {
leaf protocol-type { type identityref {
type identityref { base vpn-common:role;
base vpn-common:protocol-type; }
} default "vpn-common:any-to-any-role";
config false; description
description "Role of the node in the VPN.";
"Underlay-transport type, e.g., GRE, LDP, etc."; }
} uses vpn-summary-statistics;
}
} augment "/nw:networks/nw:network/nt:link" {
description
"Augments the network topology link with performance monitoring
attributes.";
container pm-attributes {
description
"Container for PM attributes.";
leaf low-percentile {
type percentile;
default "10.00";
description
"Low percentile to report. Setting low-percentile
into 0.00 indicates the client is not interested in receiving
low percentile.";
}
leaf middle-percentile {
type percentile;
default "50.00";
description
"Middle percentile to report. Setting middle-percentile
into 0.00 indicates the client is not interested in receiving
middle percentile.";
}
leaf high-percentile {
type percentile;
default "95.00";
description
"High percentile to report. Setting high-percentile
into 0.00 indicates the client is not interested in receiving
high percentile.";
}
leaf measurement-interval {
type uint32;
units "seconds";
default "60";
description
"Indicates the time interval to perform PM measurement.";
}
leaf reference-time {
type yang:date-and-time;
config false;
description
"The time that the current measurement-interval started.";
}
leaf pm-source {
type identityref {
base pm-source-type;
}
config false;
description
"The OAM tool used to collect the PM data.";
}
container one-way-pm-statistics {
config false;
description
"Container for link telemetry attributes.";
augment "/nw:networks/nw:network/nw:node/nt:termination-point" { uses link-loss-statistics;
description uses link-delay-statistics;
"Augment the network topology termination point with uses link-jitter-statistics;
performance monitoring attributes"; }
container pm-statistics { }
config false; }
uses tp-svc-telemetry;
description
"Container for termination point PM attributes.";
}
}
}
<CODE ENDS> augment "/nw:networks/nw:network/nt:link/pm-attributes" {
when '../../nw:network-types/nvp:service-type' {
description
"Augments only for VPN Network topology.";
}
description
"Augments the network topology link with VPN service
performance monitoring attributes.";
leaf vpn-underlay-transport-type {
type identityref {
base vpn-common:protocol-type;
}
config false;
description
"The leaf indicates the underlay transport type of
a VPN service, e.g., GRE, LDP, etc.";
}
list vpn-one-way-pm-statistics {
key "class-id";
config false;
description
"The list of PM data based on class of service.";
leaf class-id {
type string;
description
"The class-id is used to identify the class of service.
This identifier is internal to the administration.";
}
uses link-loss-statistics;
uses link-delay-statistics;
uses link-jitter-statistics;
}
}
augment "/nw:networks/nw:network/nw:node/nt:termination-point" {
description
"Augments the network topology termination point with
performance monitoring attributes.";
container pm-statistics {
config false;
description
"Container for termination point PM attributes.";
uses tp-svc-telemetry;
}
}
augment "/nw:networks/nw:network/nw:node/nt:termination-point/pm-statistics" {
when '../../../nw:network-types/nvp:service-type' {
description
"Augments only for VPN Network topology.";
}
description
"Augments the network topology termination-point with
VPN service performance monitoring attributes";
list vpn-network-access {
key "network-access-id";
description
"The list of PM based on VPN network accesses.";
leaf network-access-id {
type vpn-common:vpn-id;
description
"References to an identifier for the VPN network
access, e.g. L3VPN or VPLS.";
}
uses tp-svc-telemetry;
}
}
}
<CODE ENDS>
6. Security Considerations 6. Security Considerations
The YANG modules defined in this document MAY be accessed via the The YANG modules defined in this document MAY be accessed via the
RESTCONF protocol [RFC8040] or NETCONF protocol [RFC6241]. The RESTCONF protocol [RFC8040] or NETCONF protocol [RFC6241]. The
lowest RESTCONF or NETCONF layer requires that the transport-layer lowest RESTCONF or NETCONF layer requires that the transport-layer
protocol provides both data integrity and confidentiality, see protocol provides both data integrity and confidentiality, see
Section 2 in [RFC8040] and [RFC6241]. The lowest NETCONF layer is Section 2 in [RFC8040] and [RFC6241]. The lowest NETCONF layer is
the secure transport layer, and the mandatory-to-implement secure the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH)[RFC6242] . The lowest RESTCONF layer transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC8446]. [RFC8446].
The NETCONF access control model [RFC8341] provides the means to The NETCONF access control model [RFC8341] provides the means to
restrict access for particular NETCONF or RESTCONF users to a restrict access for particular NETCONF or RESTCONF users to a
preconfigured subset of all available NETCONF or RESTCONF protocol preconfigured subset of all available NETCONF or RESTCONF protocol
operations and content. operations and content.
There are a number of data nodes defined in this YANG module that are There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes effect on network operations. These are the subtrees with the write
and their sensitivity/vulnerability: operation that can be exploited to impact the network monitoring:
o /nw:networks/nw:network/svc-topo:svc-telemetry-attributes * "/nw:networks/nw:network/nw:network-types"
o /nw:networks/nw:network/nw:node/svc-topo:node-attributes * "/nw:networks/nw:network/nvp:vpn-pm-attributes"
* "/nw:networks/nw:network/nw:node/nvp:pm-attributes"
* /nw:networks/nw:network/nt:link/nvp:pm-attributes"
Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. The nodes
reveals the quality of a service that is operated by an operator. It
is thus important to control read access (e.g., via get, get-config,
or notification) to these data nodes. These are the subtrees and
data nodes and their sensitivity/vulnerability:
* "/nw:networks/nw:network/nw:node/nvp:pm-attributes/nvp:vpn-
summary-statistics": Unauthorized access to this subtree can
disclose the operational state information of VPN instances.
* "/nw:networks/nw:network/nt:link/nvp:pm-attributes/nvp:one-way-pm-
statistics": Unauthorized access to this subtree can disclose the
operational state information of network links or VPN underlay
tunnels.
* "/nw:networks/nw:network/nw:node/nt:termination-point/nvp:pm-
statistics": Unauthorized access to this subtree can disclose the
operational state information of network termination points or VPN
network accesses.
7. IANA Considerations 7. IANA Considerations
This document requests IANA to register the following URI in the "ns" This document requests IANA to register the following URI in the "ns"
subregistry within the "IETF XML Registry" [RFC3688]: subregistry within the "IETF XML Registry" [RFC3688]:
URI: urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm URI: urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
This document requests IANA to register the following YANG module in This document requests IANA to register the following YANG module in
the "YANG Module Names" subregistry [RFC6020] within the "YANG the "YANG Module Names" subregistry [RFC6020] within the "YANG
Parameters" registry. Parameters" registry.
Name: ietf-network-vpn-pm Name: ietf-network-vpn-pm
Namespace: urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm Namespace: urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm
Maintained by IANA: N Maintained by IANA: N
Prefix: nvp Prefix: nvp
Reference: RFC XXXX Reference: RFC XXXX (RFC Ed.: replace XXXX with actual
RFC number and remove this note.)
8. Acknowledgements 8. Acknowledgements
Thanks to Joe Clarke, Adrian Farrel, Greg Mirsky, Roque Gagliano, Thanks to Joe Clarke, Adrian Farrel, Greg Mirsky, Roque Gagliano,
Erez Segev, and Dhruv Dhody for reviewing and providing important Erez Segev, and Dhruv Dhody for reviewing and providing important
input to this document. input to this document.
9. Contributors 9. Contributors
The following authors contributed significantly to this document:
Michale Wang Michale Wang
Huawei Huawei
Email:wangzitao@huawei.com Email:wangzitao@huawei.com
Roni Even Roni Even
Huawei Huawei
Email: ron.even.tlv@gmail.com Email: ron.even.tlv@gmail.com
Change Liu
China Unicom
Email: liuc131@chinaunicom.cn
Honglei Xu
China Telecom
Email: xuhl.bri@chinatelecom.cn
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.ietf-opsawg-vpn-common] [I-D.ietf-opsawg-vpn-common]
Barguil, S., Dios, O. G. D., Boucadair, M., and Q. Wu, "A Barguil, S., Dios, O. G. D., Boucadair, M., and Q. Wu, "A
Layer 2/3 VPN Common YANG Model", draft-ietf-opsawg-vpn- Layer 2/3 VPN Common YANG Model", Work in Progress,
common-07 (work in progress), April 2021. Internet-Draft, draft-ietf-opsawg-vpn-common-12, 29
September 2021, <https://www.ietf.org/archive/id/draft-
ietf-opsawg-vpn-common-12.txt>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation [RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation
Metric for IP Performance Metrics (IPPM)", RFC 3393, Metric for IP Performance Metrics (IPPM)", RFC 3393,
DOI 10.17487/RFC3393, November 2002, DOI 10.17487/RFC3393, November 2002,
<https://www.rfc-editor.org/info/rfc3393>. <https://www.rfc-editor.org/info/rfc3393>.
skipping to change at page 25, line 49 skipping to change at page 29, line 5
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>.
[RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., [RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N.,
Ananthakrishnan, H., and X. Liu, "A YANG Data Model for Ananthakrishnan, H., and X. Liu, "A YANG Data Model for
Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March
2018, <https://www.rfc-editor.org/info/rfc8345>. 2018, <https://www.rfc-editor.org/info/rfc8345>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
[RFC8532] Kumar, D., Wang, Z., Wu, Q., Ed., Rahman, R., and S. [RFC8532] Kumar, D., Wang, Z., Wu, Q., Ed., Rahman, R., and S.
skipping to change at page 26, line 22 skipping to change at page 29, line 32
Protocols That Use Connectionless Communications", Protocols That Use Connectionless Communications",
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>.
[RFC8641] Clemm, A. and E. Voit, "Subscription to YANG Notifications [RFC8641] Clemm, A. and E. Voit, "Subscription to YANG Notifications
for Datastore Updates", RFC 8641, DOI 10.17487/RFC8641, for Datastore Updates", RFC 8641, DOI 10.17487/RFC8641,
September 2019, <https://www.rfc-editor.org/info/rfc8641>. September 2019, <https://www.rfc-editor.org/info/rfc8641>.
10.2. Informative References 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", Work in Progress,
Internet-Draft, draft-ietf-netmod-node-tags-04, 11
November 2021, <https://www.ietf.org/archive/id/draft-
ietf-netmod-node-tags-04.txt>.
[I-D.ietf-opsawg-l2nm] [I-D.ietf-opsawg-l2nm]
Barguil, S., Dios, O. G. D., Boucadair, M., and L. A. Barguil, S., Dios, O. G. D., Boucadair, M., and L. A.
Munoz, "A Layer 2 VPN Network YANG Model", draft-ietf- Munoz, "A Layer 2 VPN Network YANG Model", Work in
opsawg-l2nm-02 (work in progress), April 2021. Progress, Internet-Draft, draft-ietf-opsawg-l2nm-12, 22
November 2021, <https://www.ietf.org/archive/id/draft-
ietf-opsawg-l2nm-12.txt>.
[I-D.ietf-opsawg-l3sm-l3nm] [I-D.ietf-opsawg-l3sm-l3nm]
Barguil, S., Dios, O. G. D., Boucadair, M., Munoz, L. A., Barguil, S., Dios, O. G. D., Boucadair, M., Munoz, L. A.,
and A. Aguado, "A Layer 3 VPN Network YANG Model", draft- and A. Aguado, "A Layer 3 VPN Network YANG Model", Work in
ietf-opsawg-l3sm-l3nm-08 (work in progress), April 2021. Progress, Internet-Draft, draft-ietf-opsawg-l3sm-l3nm-18,
8 October 2021, <https://www.ietf.org/archive/id/draft-
ietf-opsawg-l3sm-l3nm-18.txt>.
[RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J. [RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J.
Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)", Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)",
RFC 5357, DOI 10.17487/RFC5357, October 2008, RFC 5357, DOI 10.17487/RFC5357, October 2008,
<https://www.rfc-editor.org/info/rfc5357>. <https://www.rfc-editor.org/info/rfc5357>.
[RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S. [RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S.
Previdi, "OSPF Traffic Engineering (TE) Metric Previdi, "OSPF Traffic Engineering (TE) Metric
Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015, Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015,
<https://www.rfc-editor.org/info/rfc7471>. <https://www.rfc-editor.org/info/rfc7471>.
skipping to change at page 27, line 5 skipping to change at page 30, line 27
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8194] Schoenwaelder, J. and V. Bajpai, "A YANG Data Model for [RFC8194] Schoenwaelder, J. and V. Bajpai, "A YANG Data Model for
LMAP Measurement Agents", RFC 8194, DOI 10.17487/RFC8194, LMAP Measurement Agents", RFC 8194, DOI 10.17487/RFC8194,
August 2017, <https://www.rfc-editor.org/info/rfc8194>. August 2017, <https://www.rfc-editor.org/info/rfc8194>.
[RFC8309] Wu, Q., Liu, W., and A. Farrel, "Service Models [RFC8309] Wu, Q., Liu, W., and A. Farrel, "Service Models
Explained", RFC 8309, DOI 10.17487/RFC8309, January 2018, Explained", RFC 8309, DOI 10.17487/RFC8309, January 2018,
<https://www.rfc-editor.org/info/rfc8309>. <https://www.rfc-editor.org/info/rfc8309>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>.
[RFC8570] Ginsberg, L., Ed., Previdi, S., Ed., Giacalone, S., Ward, [RFC8570] Ginsberg, L., Ed., Previdi, S., Ed., Giacalone, S., Ward,
D., Drake, J., and Q. Wu, "IS-IS Traffic Engineering (TE) D., Drake, J., and Q. Wu, "IS-IS Traffic Engineering (TE)
Metric Extensions", RFC 8570, DOI 10.17487/RFC8570, March Metric Extensions", RFC 8570, DOI 10.17487/RFC8570, March
2019, <https://www.rfc-editor.org/info/rfc8570>. 2019, <https://www.rfc-editor.org/info/rfc8570>.
[RFC8571] Ginsberg, L., Ed., Previdi, S., Wu, Q., Tantsura, J., and [RFC8571] Ginsberg, L., Ed., Previdi, S., Wu, Q., Tantsura, J., and
C. Filsfils, "BGP - Link State (BGP-LS) Advertisement of C. Filsfils, "BGP - Link State (BGP-LS) Advertisement of
IGP Traffic Engineering Performance Metric Extensions", IGP Traffic Engineering Performance Metric Extensions",
RFC 8571, DOI 10.17487/RFC8571, March 2019, RFC 8571, DOI 10.17487/RFC8571, March 2019,
<https://www.rfc-editor.org/info/rfc8571>. <https://www.rfc-editor.org/info/rfc8571>.
skipping to change at page 27, line 46 skipping to change at page 31, line 16
xmlns:netconf="urn:ietf:params:xml:ns:netconf:base:1.0"> xmlns:netconf="urn:ietf:params:xml:ns:netconf:base:1.0">
<establish-subscription <establish-subscription
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"> xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
<stream-subtree-filter> <stream-subtree-filter>
<networks <networks
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topo"> xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topo">
<network> <network>
<network-id>l3-network</network-id> <network-id>l3-network</network-id>
<service-type <service-type
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm"> xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm">
L3VPN ietf-vpn-common:l3vpn
</service-type> </service-type>
<node> <node>
<node-id>A</node-id> <node-id>A</node-id>
<pm-attributes> <pm-attributes>
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm"> xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm">
<node-type>pe</node-type> <node-type>pe</node-type>
</pm-attributes> </pm-attributes>
<termination-point <termination-point
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topology"> xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topology">
<tp-id>1-0-1</tp-id> <tp-id>1-0-1</tp-id>
<pm-statistics <pm-statistics
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm"> xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm">
<inbound-octets>150</inbound-octets> <inbound-octets>150</inbound-octets>
<outbound-octets>100</outbound-octets> <outbound-octets>100</outbound-octets>
</pm-statistics> </pm-statistics>
</termination-point> </termination-point>
skipping to change at page 28, line 41 skipping to change at page 32, line 10
</node> </node>
<link <link
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topology"> xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topology">
<link-id>A-B</link-id> <link-id>A-B</link-id>
<source> <source>
<source-node>A</source-node> <source-node>A</source-node>
</source> </source>
<destination> <destination>
<dest-node>B</dest-node> <dest-node>B</dest-node>
</destination> </destination>
<protocol-type>mpls-te</protocol-type> <vpn-underlay-transport-type>mpls-te</vpn-underlay-transport-type>
<pm-attributes <pm-attributes
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm"> xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm">
<loss-statistics> <one-way-pm-statistics>
<packet-loss-count>100</packet-loss-count> <loss-statistics>
</loss-statistics> <packet-loss-count>100</packet-loss-count>
</loss-statistics>
</one-way-pm-statistics>
</pm-attributes> </pm-attributes>
</link> </link>
</network> </network>
</networks> </networks>
</stream-subtree-filter> </stream-subtree-filter>
<period <period
xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-push:1.0"> xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-push:1.0">
500 500
</period> </period>
</establish-subscription> </establish-subscription>
</rpc> </rpc>
Figure 7: Pub/Siub Retrieval Figure 7: Pub/Sub Retrieval
A.2. Example of RPC-based Retrieval A.2. Example of RPC-based Retrieval
This example, depicted in Figure 8, illustrates how a the client can This example, depicted in Figure 8, illustrates how a client can use
use the RPC model to fetch performance data on demand. For example, the RPC model to fetch performance data on demand. For example, the
the client requests "packet-loss-count" between 'source-node' A and client requests "packet-loss-count" between 'source-node' A and
'dest-node' B that belong to the same VPN ('VPN1'). 'dest-node' B that belong to the same VPN ('VPN1').
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
message-id="1"> message-id="1">
<report <report
xmlns="urn:ietf:params:xml:ns:yang:example-service-pm-report"> xmlns="urn:ietf:params:xml:ns:yang:example-service-pm-report">
<networks xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topo"> <networks xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topo">
<network> <network>
<network-id>vpn1</network-id> <network-id>vpn1</network-id>
<node> <node>
<node-id>A</node-id> <node-id>A</node-id>
<pm-attributes <pm-attributes
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm">
<node-type>pe</node-type>
</pm-attribtues>
<termination-point
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topology">
<tp-id>1-0-1</tp-id>
<pm-statistics
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm"> xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm">
<inbound-octets>100</inbound-octets> <node-type>pe</node-type>
<outbound-octets>150</outbound-octets>
</pm-statistics> </pm-attribtues>
</termination-point> <termination-point
</node> xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topology">
<node> <tp-id>1-0-1</tp-id>
<node-id>B</node-id> <pm-statistics
<pm-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm">
<inbound-octets>100</inbound-octets>
<outbound-octets>150</outbound-octets>
</pm-statistics>
</termination-point>
</node>
<node>
<node-id>B</node-id>
<pm-attributes
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm">
<node-type>pe</node-type>
</pm-attribtues>
<termination-point
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topology">
<tp-id>2-0-1</tp-id>
<pm-statistics
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm"> xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm">
<node-type>pe</node-type> <inbound-octets>150</inbound-octets>
</pm-attribtues> <outbound-octets>100</outbound-octets>
<termination-point </pm-statistics>
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topology"> </termination-point>
<tp-id>2-0-1</tp-id> </node>
<pm-statistics <link>
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-pm"> <link-id>A-B</link-id>
<inbound-octets>150</inbound-octets> <source>
<outbound-octets>100</outbound-octets> <source-node>A</source-node>
</pm-statistics> </source>
</termination-point> <destination>
</node> <dest-node>B</dest-node>
<link> </destination>
<link-id>A-B</link-id> <pm-attributes
<source> xmlns="urn:ietf:params:xml:ns:yang:ietf-network-pm">
<source-node>A</source-node> <one-way-pm-statistics>
</source> <loss-statistics>
<destination> <packet-loss-count>120</packet-loss-count>
<dest-node>B</dest-node> </loss-statistics>
</destination> </one-way-pm-statistics>
<-type>mpls-te</link-type>
<pm-attributes
xmlns="urn:ietf:params:xml:ns:yang:ietf-network-pm">
<loss-statistics>
<packet-loss-count>120</packet-loss-count>
</loss-statistics>
</pm-attributes> </pm-attributes>
</link> <vpn-underlay-transport-type>mpls-te</vpn-underlay-transport-type>
</network> </link>
</report> </network>
</rpc> </report>
</rpc>
Figure 8 Figure 8
A.3. Example of Percentile Monitoring A.3. Example of Percentile Monitoring
The following shows an example of a percentile measurement for a VPN The following shows an example of a percentile measurement for a VPN
link. link.
{ {
"ietf-network-topology:link":[ "ietf-network-topology:link":[
{ {
"link-id":"vpn1-link1", "link-id":"vpn1-link1",
"source":{ "source":{
"source-node":"vpn-node1" "source-node":"vpn-node1"
}, },
"destination":{ "destination":{
"dest-node":"vpn-node3" "dest-node":"vpn-node3"
}, },
"ietf-network-vpn-pm:protocol-type":"gre", "ietf-network-vpn-pm:pm-attributes":{
"ietf-network-vpn-pm:pm-attributes":{ "low-percentile":"20.00",
"low-percentile":"20.00", "middle-percentile":"50.00",
"middle-percentile":"50.00", "high-percentile":"90.00",
"high-percentile":"90.00", "one-way-pm-statistics:delay-statistics":{
"pm-statistics:delay-statistics":{ "unit-values":"lime:milliseconds",
"direction":"one-way", "min-delay-value":"43",
"unit-values":"milliseconds", "max-delay-value":"99",
"min-delay-value":"43", "low-delay-percentile":"64",
"max-delay-value":"99", "middle-delay-percentile":"77",
"low-delay-percentile":"64", "high-delay-percentile":"98"
"middle-delay-percentile":"77",
"high-delay-percentile":"98"
}
} }
} }
] "ietf-network-vpn-pm:vpn-underlay-transport-type":"ietf-vpn-common:gre",
} }
]
}
Authors' Addresses Authors' Addresses
Bo Wu (editor) Bo Wu (editor)
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing
Jiangsu, 210012
China China
Email: lana.wubo@huawei.com Email: lana.wubo@huawei.com
Qin Wu (editor) Qin Wu (editor)
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing
Jiangsu, 210012
China China
Email: bill.wu@huawei.com Email: bill.wu@huawei.com
Mohamed Boucadair (editor) Mohamed Boucadair (editor)
Orange Orange
Rennes 35000 Rennes 35000
France France
Email: mohamed.boucadair@orange.com Email: mohamed.boucadair@orange.com
Oscar Gonzalez de Dios Oscar Gonzalez de Dios
Telefonica Telefonica
Madrid Madrid
skipping to change at page 32, line 14 skipping to change at page 35, line 23
Mohamed Boucadair (editor) Mohamed Boucadair (editor)
Orange Orange
Rennes 35000 Rennes 35000
France France
Email: mohamed.boucadair@orange.com Email: mohamed.boucadair@orange.com
Oscar Gonzalez de Dios Oscar Gonzalez de Dios
Telefonica Telefonica
Madrid Madrid
ES Spain
Email: oscar.gonzalezdedios@telefonica.com Email: oscar.gonzalezdedios@telefonica.com
Bin Wen Bin Wen
Comcast Comcast
Email: bin_wen@comcast.com Email: bin_wen@comcast.com
Change Liu
China Unicom
Email: liuc131@chinaunicom.cn
Honglei Xu
China Telecom
Email: xuhl.bri@chinatelecom.cn
 End of changes. 114 change blocks. 
836 lines changed or deleted 1006 lines changed or added

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