Generic YANG Data Model for Connection Oriented Operations, Administration, and Maintenance(OAM) protocols
draft-ietf-lime-yang-connection-oriented-oam-model-05

The information below is for an old version of the document
Document Type Active Internet-Draft (lime WG)
Last updated 2018-02-20 (latest revision 2018-02-08)
Replaces draft-ietf-lime-yang-oam-model
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Revised I-D Needed - Issue raised by WGLC
Document shepherd Ron Bonica
Shepherd write-up Show (last changed 2017-12-27)
IESG IESG state Waiting for Writeup
Consensus Boilerplate Yes
Telechat date
Needs a YES. Has enough positions to pass.
Responsible AD BenoƮt Claise
Send notices to rbonica@juniper.net
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Network Working Group                                           D. Kumar
Internet-Draft                                                     Cisco
Intended status: Standards Track                                   Q. Wu
Expires: August 10, 2018                                         M. Wang
                                                                  Huawei
                                                        February 6, 2018

      Generic YANG Data Model for Connection Oriented Operations,
             Administration, and Maintenance(OAM) protocols
         draft-ietf-lime-yang-connection-oriented-oam-model-05

Abstract

   This document presents a base YANG Data model for connection oriented
   OAM protocols.  It provides a technology-independent abstraction of
   key OAM constructs for such protocols.  The model presented here can
   be extended to include technology specific details.  This guarantees
   uniformity in the management of OAM protocols and provides support
   for nested OAM workflows (i.e., performing OAM functions at different
   levels through a unified interface).

   The YANG model in this document conforms to the Network Management
   Datastore Architecture defined in
   [I-D.ietf-netmod-revised-datastores].

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 August 10, 2018.

Copyright Notice

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

Kumar, et al.            Expires August 10, 2018                [Page 1]
Internet-Draft     Connection-Oriented OAM YANG model      February 2018

   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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions used in this document . . . . . . . . . . . . . .   4
     2.1.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Tree Diagrams . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Architecture of Generic YANG Model for OAM  . . . . . . . . .   6
   4.  Overview of the OAM Model . . . . . . . . . . . . . . . . . .   7
     4.1.  Maintenance Domain (MD) configuration . . . . . . . . . .   8
     4.2.  Maintenance Association (MA) configuration  . . . . . . .   9
     4.3.  Maintenance Endpoint (MEP) configuration  . . . . . . . .   9
     4.4.  RPC definitions . . . . . . . . . . . . . . . . . . . . .  10
     4.5.  Notifications . . . . . . . . . . . . . . . . . . . . . .  13
     4.6.  Monitor statistics  . . . . . . . . . . . . . . . . . . .  13
     4.7.  OAM data hierarchy  . . . . . . . . . . . . . . . . . . .  13
   5.  OAM YANG Module . . . . . . . . . . . . . . . . . . . . . . .  17
   6.  Base Mode . . . . . . . . . . . . . . . . . . . . . . . . . .  40
     6.1.  MEP Address . . . . . . . . . . . . . . . . . . . . . . .  40
     6.2.  MEP ID for Base Mode  . . . . . . . . . . . . . . . . . .  40
     6.3.  Maintenance Association . . . . . . . . . . . . . . . . .  41
   7.  Connection-oriented OAM YANG model applicability  . . . . . .  41
     7.1.  Generic YANG Model extension for TRILL OAM  . . . . . . .  41
       7.1.1.  MD Configuration Extension  . . . . . . . . . . . . .  42
       7.1.2.  MA Configuration Extension  . . . . . . . . . . . . .  42
       7.1.3.  MEP Configuration Extension . . . . . . . . . . . . .  43
       7.1.4.  RPC extension . . . . . . . . . . . . . . . . . . . .  43
     7.2.  Generic YANG Model extension for MPLS-TP OAM  . . . . . .  44
       7.2.1.  MD Configuration Extension  . . . . . . . . . . . . .  44
       7.2.2.  MA Configuration Extension  . . . . . . . . . . . . .  46
       7.2.3.  MEP Configuration Extension . . . . . . . . . . . . .  46
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  47
Show full document text