A YANG Model for VPN Service Performance Monitoring
draft-www-bess-yang-vpn-service-pm-01

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Yang Validation 0 errors, 0 warnings.
Additional URLs
- Yang catalog entry for ietf-vpn-svc-pm@2018-08-29.yang
- Yang impact analysis for draft-www-bess-yang-vpn-service-pm
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
BESS Working Group                                               M. Wang
Internet-Draft                                                     Q. Wu
Intended status: Standards Track                                 R. Even
Expires: April 25, 2019                                           Huawei
                                                                  B. Wen
                                                                 Comcast
                                                        October 22, 2018

          A YANG Model for VPN Service Performance Monitoring
                 draft-www-bess-yang-vpn-service-pm-01

Abstract

   As specified in [RFC8345], the data model defined in [RFC8345]
   introduces vertical layering relationships between networks that can
   be augmented to cover network/service topologies.  This document
   defines a YANG Model for VPN Service Performance Monitoring that can
   be used to monitor and manage network Performance between VPN sites
   and it is an augmentation to the I2RS network topology YANG data
   model.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 25, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Wang, et al.             Expires April 25, 2019                 [Page 1]
Internet-Draft              Service Topo YANG               October 2018

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  VPN Service Topology Overview . . . . . . . . . . . . . . . .   4
   4.  VPN service assurance model . . . . . . . . . . . . . . . . .   5
   5.  Model Usage Guideline . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Performance Monitoring Data Source  . . . . . . . . . . .   5
     5.2.  Retrieval via I2RS Pub/Sub  . . . . . . . . . . . . . . .   5
     5.3.  On demand Retrieval via RPC model . . . . . . . . . . . .   6
   6.  Design of the Data Model  . . . . . . . . . . . . . . . . . .   6
     6.1.  Network Level . . . . . . . . . . . . . . . . . . . . . .   6
     6.2.  Node Level  . . . . . . . . . . . . . . . . . . . . . . .   6
     6.3.  Link and Termination Point Level  . . . . . . . . . . . .   7
   7.  Example of I2RS Pub/Sub Retrieval . . . . . . . . . . . . . .   8
   8.  Example of RPC model based Retrieval  . . . . . . . . . . . .   9
   9.  VPN Service Assurance YANG Module . . . . . . . . . . . . . .   9
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  16
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   12. Normative References  . . . . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   [RFC8345] defines an abstract YANG data model for network/service
   topologies and inventories.  Service topology in [RFC8345] includes
   the a virtual topology for a service layer above the L1, L2, and L3
   layers.  This virtual topology has the generic topology elements of
   node,link, and terminating point.  One typical example of a service
   topology is described in figure 3 of [RFC8345],two VPN service
   topologies instantiated over a common L3 topology.  Each VPN service
   topology is mapped onto a subset of nodes from the common L3
   topology.

   In [RFC8299], the 3 types of VPN service topologies proposed for
   L3VPN service data model are any to any, hub and spoke, hub and spoke
   disjoint.  These VPN topology types can be used to describe how VPN
   sites are communicating with each other.

   This document defines a YANG Model for VPN Service Performance
   Monitoring that can be used to monitor and manage network Performance
Show full document text