<?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-07">
   <front>
      <title>A YANG Data Model for Traffic Engineering Tunnels 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>Jabil</organization>
      </author>
      <author initials="V. P." surname="Beeram" fullname="Vishnu Pavan Beeram">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="H." surname="Shah" fullname="Himanshu Shah">
         <organization>Ciena</organization>
      </author>
      <author initials="I." surname="Bryskin" fullname="Igor Bryskin">
         <organization>Huawei Technologies</organization>
      </author>
      <date month="June" day="29" year="2017" />
      <abstract>
	 <t>   This document defines a YANG data model for the configuration and
   management of Traffic Engineering (TE) interfaces, tunnels and Label
   Switched Paths (LSPs).  The model is divided into YANG modules that
   classify data into generic, device-specific, technology agnostic, and
   technology-specific elements.  The model also includes module(s) that
   contain reusable TE data types and data groupings.

   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-07" />
   
</reference>
