YANG Data Model for MPLS-TP Operations, Administration, and Maintenance (OAM)
draft-zhang-mpls-tp-yang-oam-04

Document Type Active Internet-Draft (individual)
Last updated 2017-06-29
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Yang Validation 0 errors, 0 warnings.
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)
Network Working Group                                           L. Zhang
Internet-Draft                                                  L. Zheng
Intended status: Standards Track                     Huawei Technologies
Expires: January 1, 2018                                       S. Aldrin
                                                                  Google
                                                               G. Mirsky
                                                               ZTE Corp.
                                                           June 30, 2017

YANG Data Model for MPLS-TP Operations, Administration, and Maintenance
                                 (OAM)
                    draft-zhang-mpls-tp-yang-oam-04

Abstract

   The Transport Profile of Multiprotocol Label Switching (MPLS-TP)
   [RFC5921]is a packet-based transport technology based on the MPLS
   Traffic Engineering (MPLS-TE) and pseudowire (PW) data-plane
   architectures.  A comprehensive set of Operations, Administration,
   and Maintenance (OAM) procedures that fulfill the MPLS-TP OAM
   requirements for fault, performance, and protection-switching
   management had been defined.  YANG [RFC6020]is a data definition
   language that was introduced to define the contents of a conceptual
   data store that allows networked devices to be managed using NETCONF
   [RFC6241].  This document presents the YANG Data model for MPLS-TP
   OAM, including the basic functions of Fault Management and
   Performance Monitoring.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 http://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

Zhang, et al.            Expires January 1, 2018                [Page 1]
Internet-Draft              MPLS-TP OAM Yang                   June 2017

   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 January 1, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights 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.  Design of the Data Model  . . . . . . . . . . . . . . . . . .   4
     3.1.  Maintenance Entity Group (MEG) Configuration  . . . . . .   4
     3.2.  Maintenance Entities (MEs) Configuration  . . . . . . . .   4
     3.3.  MPLS-TP OAM Fault Management And Performance Moinitoring
           Configuration . . . . . . . . . . . . . . . . . . . . . .   6
     3.4.  Display of ME Status  . . . . . . . . . . . . . . . . . .   7
     3.5.  Display of Detect Result  . . . . . . . . . . . . . . . .  10
   4.  MPLS-TP OAM Data Hierarchy  . . . . . . . . . . . . . . . . .  12
   5.  Interaction with other MPLS OAM Tools Models  . . . . . . . .  17
   6.  MPLS-TP OAM YANG module . . . . . . . . . . . . . . . . . . .  17
   7.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  47
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  47
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  48
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  48
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  48
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  48
     11.2.  Infomative References  . . . . . . . . . . . . . . . . .  49
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  49
Show full document text