Yang Data Model for LSP-PING
draft-zheng-mpls-lsp-ping-yang-cfg-05

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05

draft-zheng-mpls-lsp-ping-yang-cfg-05.txt:
xym 0.3.2:
Extracting 'ietf-lspping@2015-07-02.yang'


ietf-lspping@2015-07-02.yang:
pyang 1.7.2: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.12.183: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model}:
No validation errors

Network Working Group                                           L. Zheng
Internet-Draft                                       Huawei Technologies
Intended status: Standards Track                               S. Aldrin
Expires: January 1, 2018                                          Google
                                                                G. Zheng
                                                     Huawei Technologies
                                                               G. Mirsky
                                                               ZTE Corp.
                                                               R. Rahman
                                                           Cisco Systems
                                                           June 30, 2017

                      Yang Data Model for LSP-PING
                 draft-zheng-mpls-lsp-ping-yang-cfg-05

Abstract

   When an LSP fails to deliver user traffic, the failure cannot always
   be detected by the MPLS control plane.  RFC4379 defines a mechanism
   that would enable users to detect such failure and to isolate faults.
   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 RFC[6241].  This document defines
   a YANG data model that can be used to configure and manage LSP-Ping.

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
   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.

Zheng, et al.            Expires January 1, 2018                [Page 1]
Internet-Draft                LSP-Ping Yang                    June 2017

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
     1.1.  Support of Long Running Command with NETCONF  . . . . . .   3
     1.2.  Contributors  . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Design of the Data Model  . . . . . . . . . . . . . . . . . .   4
     3.1.  Configuration of Control Information  . . . . . . . . . .   4
     3.2.  Configuration of Schedule Parameters  . . . . . . . . . .   5
     3.3.  Display of Result Information . . . . . . . . . . . . . .   6
   4.  Data Hierarchy  . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Interaction with other MPLS OAM Tools Models  . . . . . . . .  10
   6.  LSP-Ping Yang Module  . . . . . . . . . . . . . . . . . . . .  10
   7.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  20
     7.1.  Configuration of Control Information  . . . . . . . . . .  20
     7.2.  Configuration of Schedule Parameters  . . . . . . . . . .  21
     7.3.  Display of Result Information . . . . . . . . . . . . . .  22
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  24
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  24
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  24
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  24
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  25
     11.2.  Informative References . . . . . . . . . . . . . . . . .  25