YANG Data Model for LSP-Ping
draft-zheng-mpls-lsp-ping-yang-cfg-09

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

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08
• 09

draft-zheng-mpls-lsp-ping-yang-cfg-09.txt:
xym 0.4:
Extracting 'ietf-lspping@2018-03-01.yang'
   Removed 0 empty lines


ietf-lspping@2018-03-01.yang:
pyang 1.7.5: pyang --verbose --ietf -p {libs} {model}:
No validation errors

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

Network Working Group                                           L. Zheng
Internet-Draft                                                  G. Zheng
Intended status: Standards Track                     Huawei Technologies
Expires: April 17, 2019                                        G. Mirsky
                                                               ZTE Corp.
                                                               R. Rahman
                                                                F. Iqbal
                                                           Cisco Systems
                                                        October 14, 2018

                      YANG Data Model for LSP-Ping
                 draft-zheng-mpls-lsp-ping-yang-cfg-09

Abstract

   When an LSP fails to deliver user traffic, the failure cannot always
   be detected by the MPLS control plane.  RFC 8029 defines a mechanism
   that would enable users to detect such failure and to isolate faults.
   YANG, defined in RFC 6020 and RFC 7950, is a data modeling language
   used to specify the contents of a conceptual data stores that allows
   networked devices to be managed using NETCONF, as specified in RFC
   6241.  This document defines a YANG data model that can be used to
   configure and manage LSP-Ping.

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 17, 2019.

Copyright Notice

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

Zheng, et al.            Expires April 17, 2019                 [Page 1]
Internet-Draft                LSP-Ping YANG                 October 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Support of Long Running Command with NETCONF  . . . . . .   3
   2.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Design of the Data Model  . . . . . . . . . . . . . . . . . .   4
     3.1.  The Configuration of Control Information  . . . . . . . .   4
     3.2.  The 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.  The Configuration of Schedule Parameters  . . . . . . . .  21
     7.3.  Display of Result Information . . . . . . . . . . . . . .  22
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  24
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  25
   Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . .  25
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  25
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  25
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  25
     12.2.  Informative References . . . . . . . . . . . . . . . . .  26
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  27

1.  Introduction

   When an LSP fails to deliver user traffic, the failure cannot always
   be detected by the MPLS control plane.  [RFC8029] defines a mechanism
   that would enable users to detect such failure and to isolate faults.
   YANG, defined in [RFC6020] and [RFC7950], is a data modeling language
   that was introduced to define the contents of a conceptual data store
   that allows networked devices to be managed using NETCONF [RFC6241].