<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.zheng-mpls-lsp-ping-yang-cfg" target="https://datatracker.ietf.org/doc/html/draft-zheng-mpls-lsp-ping-yang-cfg-10">
   <front>
      <title>YANG Data Model for LSP-Ping</title>
      <author initials="L." surname="Zheng" fullname="Lianshu Zheng">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="G." surname="Zheng" fullname="Guangying Zheng">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="G." surname="Mirsky" fullname="Greg Mirsky">
         <organization>ZTE Corp.</organization>
      </author>
      <author initials="R." surname="Rahman" fullname="Reshad Rahman">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="" surname="faiqbal@cisco.com" fullname="faiqbal@cisco.com">
         <organization>Cisco Systems</organization>
      </author>
      <date month="January" day="9" year="2019" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-zheng-mpls-lsp-ping-yang-cfg-10" />
   
</reference>
