draft-ietf-opsawg-yang-vpn-service-pm-05.txt   draft-ietf-opsawg-yang-vpn-service-pm-06.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: 10 October 2022 M. Boucadair, Ed. Expires: 16 October 2022 M. Boucadair, Ed.
Orange Orange
O. Gonzalez de Dios O. Gonzalez de Dios
Telefonica Telefonica
B. Wen B. Wen
Comcast Comcast
8 April 2022 14 April 2022
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-05 draft-ietf-opsawg-yang-vpn-service-pm-06
Abstract Abstract
The data model for network topologies defined in RFC 8345 introduces The data model for network topologies defined in RFC 8345 introduces
vertical layering relationships between networks that can be vertical layering relationships between networks that can be
augmented to cover network and service topologies. This document augmented to cover network and service topologies. This document
defines a YANG module for performance monitoring (PM) of both defines a YANG module for performance monitoring (PM) of both
networks and VPN services that can be used to monitor and manage networks and VPN services that can be used to monitor and manage
network performance on the topology at higher layer or the service network performance on the topology at higher layer or the service
topology between VPN sites. topology between VPN sites.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 10 October 2022. This Internet-Draft will expire on 16 October 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 14, line 44 skipping to change at page 14, line 44
network access defined in [RFC9182] or [I-D.ietf-opsawg-l2nm]. network access defined in [RFC9182] or [I-D.ietf-opsawg-l2nm].
When multiple VPN network accesses are created using the same When multiple VPN network accesses are created using the same
physical port, finer-grained metrics can be monitored. If a TP is physical port, finer-grained metrics can be monitored. If a TP is
associated with only a single VPN, this list is not required. associated with only a single VPN, this list is not required.
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], [RFC8532], and [RFC9181]. [RFC6991], [RFC8532], and [RFC9181].
<CODE BEGINS> file "ietf-network-vpn-pm@2021-04-08.yang" <CODE BEGINS> file "ietf-network-vpn-pm@2022-04-08.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";
} }
skipping to change at page 33, line 35 skipping to change at page 33, line 35
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", Work in Munoz, "A Layer 2 VPN Network YANG Model", Work in
Progress, Internet-Draft, draft-ietf-opsawg-l2nm-12, 22 Progress, Internet-Draft, draft-ietf-opsawg-l2nm-12, 22
November 2021, <https://www.ietf.org/archive/id/draft- November 2021, <https://www.ietf.org/archive/id/draft-
ietf-opsawg-l2nm-12.txt>. ietf-opsawg-l2nm-12.txt>.
[I-D.ietf-opsawg-sap] [I-D.ietf-opsawg-sap]
Boucadair, M., Dios, O. G. D., Barguil, S., Wu, Q., and V. Boucadair, M., Dios, O. G. D., Barguil, S., Wu, Q., and V.
Lopez, "A Network YANG Model for Service Attachment Points Lopez, "A Network YANG Model for Service Attachment Points
(SAPs)", Work in Progress, Internet-Draft, draft-ietf- (SAPs)", Work in Progress, Internet-Draft, draft-ietf-
opsawg-sap-03, 21 March 2022, opsawg-sap-04, 11 April 2022,
<https://www.ietf.org/archive/id/draft-ietf-opsawg-sap- <https://www.ietf.org/archive/id/draft-ietf-opsawg-sap-
03.txt>. 04.txt>.
[RFC4026] Andersson, L. and T. Madsen, "Provider Provisioned Virtual [RFC4026] Andersson, L. and T. Madsen, "Provider Provisioned Virtual
Private Network (VPN) Terminology", RFC 4026, Private Network (VPN) Terminology", RFC 4026,
DOI 10.17487/RFC4026, March 2005, DOI 10.17487/RFC4026, March 2005,
<https://www.rfc-editor.org/info/rfc4026>. <https://www.rfc-editor.org/info/rfc4026>.
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
2006, <https://www.rfc-editor.org/info/rfc4364>. 2006, <https://www.rfc-editor.org/info/rfc4364>.
skipping to change at page 35, line 19 skipping to change at page 35, line 19
The example shown in Figure 8 illustrates how a client subscribes to The example shown in Figure 8 illustrates how a client subscribes to
the performance monitoring information between nodes ('node-id') A the performance monitoring information between nodes ('node-id') A
and B in the L3 network topology. The performance monitoring and B in the L3 network topology. The performance monitoring
parameter that the client is interested in is end-to-end loss. parameter that the client is interested in is end-to-end loss.
POST /restconf/operations POST /restconf/operations
/ietf-subscribed-notifications:establish-subscription /ietf-subscribed-notifications:establish-subscription
{ {
"ietf-subscribed-notifications:input":{ "ietf-subscribed-notifications:input":{
"stream-subtree-filter":{ "stream-subtree-filter":{
"ietf-network-topo:networks":{ "ietf-network:networks":{
"network":{ "network":{
"network-id":"l3-network", "network-id":"l3-network",
"ietf-network-vpn-pm:service-type":{ "ietf-network-vpn-pm:service-type":{
"ietf-vpn-common:l3vpn":{} "ietf-vpn-common:l3vpn":{}
}, },
"node":[ "node":[
{ {
"node-id":"A", "node-id":"A",
"ietf-network-vpn-pm:pm-attributes":{ "ietf-network-vpn-pm:pm-attributes":{
"node-type":"PE" "node-type":"PE"
skipping to change at page 35, line 45 skipping to change at page 35, line 45
{ {
"node-id":"B", "node-id":"B",
"ietf-network-vpn-pm:pm-attributes":{ "ietf-network-vpn-pm:pm-attributes":{
"node-type":"PE" "node-type":"PE"
}, },
"termination-point":{ "termination-point":{
"tp-id":"2-0-1" "tp-id":"2-0-1"
} }
} }
], ],
"link":{ "ietf-network-topology:link":{
"link-id":"A-B", "link-id":"A-B",
"source":{ "source":{
"source-node":"A" "source-node":"A"
}, },
"destination":{ "destination":{
"dest-node":"B" "dest-node":"B"
}, },
"ietf-network-vpn-pm:pm-attributes":{ "ietf-network-vpn-pm:pm-attributes":{
"one-way-pm-statistics":{ "one-way-pm-statistics":{
skipping to change at page 37, line 6 skipping to change at page 37, line 6
Figure 8: Pub/Sub Retrieval Figure 8: Pub/Sub Retrieval
A.2. Example of VPN Performance Snapshot A.2. Example of VPN Performance Snapshot
This example, depicted in Figure 9, illustrates an VPN PM instance This example, depicted in Figure 9, illustrates an VPN PM instance
example in which a client uses RESTCONF [RFC8040] to fetch the example in which a client uses RESTCONF [RFC8040] to fetch the
performance data of the link and TP belonged to "VPN1". performance data of the link and TP belonged to "VPN1".
{ {
"ietf-network-topo:networks": { "ietf-network:networks": {
"network": { "network": {
"network-id": "foo:vpn1", "network-id": "foo:vpn1",
"node": [ "node": [
{ {
"node-id": "A", "node-id": "A",
"ietf-network-vpn-pm:pm-attributes": { "ietf-network-vpn-pm:pm-attributes": {
"node-type": "PE" "node-type": "PE"
}, },
"termination-point": { "termination-point": {
"tp-id": "1-0-1", "tp-id": "1-0-1",
skipping to change at page 37, line 37 skipping to change at page 37, line 37
}, },
"termination-point": { "termination-point": {
"tp-id": "2-0-1", "tp-id": "2-0-1",
"ietf-network-vpn-pm:pm-statistics": { "ietf-network-vpn-pm:pm-statistics": {
"inbound-octets": "150", "inbound-octets": "150",
"outbound-octets": "100" "outbound-octets": "100"
} }
} }
} }
], ],
"link": { "ietf-network-topology:link": {
"link-id": "A-B", "link-id": "A-B",
"source": { "source-node": "A" }, "source": { "source-node": "A" },
"destination": { "dest-node": "B" }, "destination": { "dest-node": "B" },
"ietf-network-pm:pm-attributes": { "ietf-network-pm:pm-attributes": {
"one-way-pm-statistics": { "one-way-pm-statistics": {
"loss-statistics": { "packet-loss-count": "120" } "loss-statistics": { "packet-loss-count": "120" }
}, },
"vpn-underlay-transport-type": "ietf-vpn-common:gre" "vpn-underlay-transport-type": "ietf-vpn-common:gre"
} }
} }
skipping to change at page 38, line 22 skipping to change at page 38, line 22
{ {
"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:pm-attributes": { "ietf-network-vpn-pm:pm-attributes": {
"low-percentile": "20.00", "low-percentile": "20.00",
"middle-percentile": "50.00", "intermediate-percentile": "50.00",
"high-percentile": "90.00", "high-percentile": "90.00",
"one-way-pm-statistics": { "one-way-pm-statistics": {
"delay-statistics": { "delay-statistics": {
"unit-values": "lime:milliseconds", "unit-value": "lime:milliseconds",
"min-delay-value": "43", "min-delay-value": "43",
"max-delay-value": "99", "max-delay-value": "99",
"low-delay-percentile": "64", "low-delay-percentile": "64",
"intermediate-delay-percentile": "77", "intermediate-delay-percentile": "77",
"high-delay-percentile": "98" "high-delay-percentile": "98"
} }
}, },
"ietf-network-vpn-pm:inter-vpn-access-interface": [null] "inter-vpn-access-interface": [null]
} }
} }
] ]
} }
Authors' Addresses Authors' Addresses
Bo Wu (editor) Bo Wu (editor)
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
 End of changes. 14 change blocks. 
14 lines changed or deleted 14 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/