< draft-www-bess-yang-vpn-service-pm-02.txt   draft-www-bess-yang-vpn-service-pm-03.txt >
BESS Working Group M. Wang BESS Working Group M. Wang
Internet-Draft Q. Wu Internet-Draft Q. Wu
Intended status: Standards Track R. Even Intended status: Standards Track R. Even
Expires: September 9, 2019 Huawei Expires: January 6, 2020 Huawei
B. Wen B. Wen
Comcast Comcast
C. Liu C. Liu
China Unicom China Unicom
March 8, 2019 July 5, 2019
A YANG Model for Network and VPN Service Performance Monitoring A YANG Model for Network and VPN Service Performance Monitoring
draft-www-bess-yang-vpn-service-pm-02 draft-www-bess-yang-vpn-service-pm-03
Abstract Abstract
The data model defined in [RFC8345] introduces vertical layering The data model defined in [RFC8345] introduces vertical layering
relationships between networks that can be augmented to cover relationships between networks that can be augmented to cover
network/service topologies. This document defines a YANG model for network/service topologies. This document defines a YANG model for
Network and VPN Service Performance Monitoring that can be used to Network and VPN Service Performance Monitoring that can be used to
monitor and manage network performance on the topology at different monitor and manage network performance on the topology at different
layer or the overlay topology between VPN sites. This model is an layer or the overlay topology between VPN sites. This model is an
augmentation to the network topology YANG data model defined in augmentation to the network topology YANG data model defined in
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 September 9, 2019. This Internet-Draft will expire on January 6, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 32 skipping to change at page 2, line 32
topology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 topology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Model Usage Guideline . . . . . . . . . . . . . . . . . . . . 5 5. Model Usage Guideline . . . . . . . . . . . . . . . . . . . . 5
5.1. Performance Monitoring Data Source . . . . . . . . . . . 5 5.1. Performance Monitoring Data Source . . . . . . . . . . . 5
5.2. Retrieval via I2RS Pub/Sub [RFC7923] . . . . . . . . . . 5 5.2. Retrieval via I2RS Pub/Sub [RFC7923] . . . . . . . . . . 5
5.3. On demand Retrieval via RPC model . . . . . . . . . . . . 6 5.3. On demand Retrieval via RPC model . . . . . . . . . . . . 6
6. Design of the Data Model . . . . . . . . . . . . . . . . . . 6 6. Design of the Data Model . . . . . . . . . . . . . . . . . . 6
6.1. Network Level . . . . . . . . . . . . . . . . . . . . . . 6 6.1. Network Level . . . . . . . . . . . . . . . . . . . . . . 6
6.2. Node Level . . . . . . . . . . . . . . . . . . . . . . . 6 6.2. Node Level . . . . . . . . . . . . . . . . . . . . . . . 6
6.3. Link and Termination Point Level . . . . . . . . . . . . 7 6.3. Link and Termination Point Level . . . . . . . . . . . . 7
7. Example of I2RS Pub/Sub Retrieval [RFC7923] . . . . . . . . . 9 7. Example of I2RS Pub/Sub Retrieval [RFC7923] . . . . . . . . . 9
8. Example of RPC model based Retrieval . . . . . . . . . . . . 11 8. Example of RPC model based Retrieval . . . . . . . . . . . . 10
9. Network and VPN Service Assurance YANG Module . . . . . . . . 11 9. Network and VPN Service Assurance YANG Module . . . . . . . . 12
10. Security Considerations . . . . . . . . . . . . . . . . . . . 20 10. Security Considerations . . . . . . . . . . . . . . . . . . . 20
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
12. Normative References . . . . . . . . . . . . . . . . . . . . 21 12. Normative References . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
[RFC8345] defines an abstract YANG data model for network/service [RFC8345] defines an abstract YANG data model for network/service
topologies and inventories. Service topology in [RFC8345] includes topologies and inventories. Service topology in [RFC8345] includes
the a virtual topology for a service layer above the L1, L2, and L3 the a virtual topology for a service layer above the L1, L2, and L3
layers. This virtual topology has the generic topology elements of layers. This virtual topology has the generic topology elements of
node, link, and terminating point. One typical example of a service node, link, and terminating point. One typical example of a service
topology is described in figure 3 of [RFC8345], two VPN service topology is described in figure 3 of [RFC8345], two VPN service
skipping to change at page 6, line 33 skipping to change at page 6, line 33
module: ietf-network-vpn-svc-pm module: ietf-network-vpn-svc-pm
augment /nw:networks/nw:network/nw:network-types: augment /nw:networks/nw:network/nw:network-types:
+--rw svc-topo-type? identityref +--rw svc-topo-type? identityref
augment /nw:networks/nw:network: augment /nw:networks/nw:network:
+--rw svc-topo-attributes +--rw svc-topo-attributes
+--rw vpn-topo? identityref +--rw vpn-topo? identityref
Network Level View of the hierarchies Network Level View of the hierarchies
The Network and VPN service performance monitoring model defines only For VPN service performance monitoring, this model defines only the
the following minimal set of Network level service topology following minimal set of Network level service topology attributes:
attributes:
o svc-topo-type: Indicate the network type is service topology type o svc-topo-type: Indicate the network type is service topology type
such as L3VPN service topology, L2VPN service topology. such as L3VPN service topology, L2VPN service topology.
o vpn-topo: The type of VPN service topology, this model supports o vpn-topo: The type of VPN service topology, this model supports
any-to-any, Hub and Spoke (where Hubs can exchange traffic), and any-to-any, Hub and Spoke (where Hubs can exchange traffic), and
"Hub and Spoke disjoint" (where Hubs cannot exchange traffic). "Hub and Spoke disjoint" (where Hubs cannot exchange traffic).
For network performance monitoring, the attributes of "Network Level"
that defined in [RFC8345] do not need to be extended.
6.2. Node Level 6.2. Node Level
augment /nw:networks/nw:network/nw:node: augment /nw:networks/nw:network/nw:node:
+--rw node-attributes +--rw node-attributes
+--rw node-type? identityref +--rw node-type? identityref
+--rw site-id? string +--rw site-id? string
+--rw site-role? Identityref +--rw site-role? Identityref
Node Level View of the hierarchies Node Level View of the hierarchies
The Network and VPN service performance monitoring model defines only The Network and VPN service performance monitoring model defines only
skipping to change at page 10, line 18 skipping to change at page 9, line 44
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 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>l3-network</network-id> <network-id>l3-network</network-id>
<node> <node>
<node-id>A</node-id> <node-id>A</node-id>
<node-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-svc-pm"> <node-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-svc-pm">
<node-type>pe</node-type> <node-type>pe</node-type>
</node-attribtues> </node-attribtues>
<termination-point xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topology">
<tp-id>1-0-1</tp-id>
<tp-telemetry-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-svc-pm">
<in-octets>100</in-octets>
<out-octets>150</out-octets>
</tp-telemetry-attributes>
</termination-point>
</node> </node>
<node> <node>
<node-id>B</node-id> <node-id>B</node-id>
<node-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-svc-pm"> <node-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-svc-pm">
<node-type>pe</node-type> <node-type>pe</node-type>
</node-attribtues> </node-attribtues>
<termination-point xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topology">
<tp-id>2-0-1</tp-id>
<tp-telemetry-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-svc-pm">
<in-octets>150</in-octets>
<out-octets>100</out-octets>
</tp-telemetry-attributes>
</termination-point>
</node> </node>
<link xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topology"> <link 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>
<svc-telemetry-attributes <svc-telemetry-attributes
skipping to change at page 11, line 22 skipping to change at page 11, line 16
message-id="1"> message-id="1">
<report xmlns="urn:ietf:params:xml:ns:yang:example-service-pm-report"> <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>
<node-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-svc-pm"> <node-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-svc-pm">
<node-type>pe</node-type> <node-type>pe</node-type>
</node-attribtues> </node-attribtues>
<termination-point xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topology">
<tp-id>1-0-1</tp-id>
<tp-telemetry-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-svc-pm">
<in-octets>100</in-octets>
<out-octets>150</out-octets>
</tp-telemetry-attributes>
</termination-point>
</node> </node>
<node> <node>
<node-id>B</node-id> <node-id>B</node-id>
<node-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-svc-pm"> <node-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-svc-pm">
<node-type>pe</node-type> <node-type>pe</node-type>
</node-attribtues> </node-attribtues>
<termination-point xmlns="urn:ietf:params:xml:ns:yang:ietf-network-topology">
<tp-id>2-0-1</tp-id>
<tp-telemetry-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-svc-pm">
<in-octets>150</in-octets>
<out-octets>100</out-octets>
</tp-telemetry-attributes>
</termination-point>
</node> </node>
<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>
<svc-telemetry-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-svc-pm"> <svc-telemetry-attributes xmlns="urn:ietf:params:xml:ns:yang:ietf-network-vpn-svc-pm">
<loss-statistics> <loss-statistics>
 End of changes. 12 change blocks. 
10 lines changed or deleted 40 lines changed or added

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