<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-teas-yang-te" target="https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-te-42">
   <front>
      <title>A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths, and Interfaces</title>
      <author initials="T." surname="Saad" fullname="Tarek Saad">
         <organization>Cisco Systems Inc</organization>
      </author>
      <author initials="R." surname="Gandhi" fullname="Rakesh Gandhi">
         <organization>Cisco Systems Inc</organization>
      </author>
      <author initials="X." surname="Liu" fullname="Xufeng Liu">
         <organization>Alef Edge</organization>
      </author>
      <author initials="V. P." surname="Beeram" fullname="Vishnu Pavan Beeram">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="I." surname="Bryskin" fullname="Igor Bryskin">
         <organization>Individual</organization>
      </author>
      <date month="February" day="24" year="2026" />
      <abstract>
	 <t>   This document defines a YANG data model for the provisioning and
   management of Traffic Engineering (TE) tunnels, Label Switched Paths
   (LSPs), and interfaces.  The model covers data that is independent of
   any technology or dataplane encapsulation and is divided into two
   YANG modules that cover device-specific, and device independent data.

   This model covers data for configuration, operational state, remote
   procedural calls, and event notifications.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-teas-yang-te-42" />
   
</reference>
