<?xml version='1.0' encoding='utf-8'?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.2.12 -->
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902"
     docName="draft-ietf-teas-yang-te-types-13" number="0000" category="std" obsoletes=""
     updates="" submissionType="IETF" consensus="true" xml:lang="en" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 2.40.1 -->
  <front>
    <title abbrev="TE Common YANG Types">Traffic Engineering Common YANG Types</title>

    <seriesInfo name="RFC" value="0000"/>
    <author initials="T." surname="Saad" fullname="Tarek Saad">
      <organization>Juniper Networks</organization>
      <address>
        <email>tsaad@juniper.net</email>
      </address>
    </author>
    <author initials="R." surname="Gandhi" fullname="Rakesh Gandhi">
      <organization>Cisco Systems, Inc.</organization>
      <address>
        <email>rgandhi@cisco.com</email>
      </address>
    </author>
    <author initials="X." surname="Liu" fullname="Xufeng Liu">
      <organization>Volta Networks</organization>
      <address>
        <email>xufeng.liu.ietf@gmail.com</email>
      </address>
    </author>
    <author initials="V." surname="Beeram" fullname="Vishnu Pavan Beeram">
      <organization>Juniper Networks</organization>
      <address>
        <email>vbeeram@juniper.net</email>
      </address>
    </author>
    <author initials="I." surname="Bryskin" fullname="Igor Bryskin">
      <organization>Individual</organization>
      <address>
        <email>i_bryskin@yahoo.com</email>
      </address>
    </author>
    <date month="March" year="2020"/>

    <abstract>
      <t>This document defines a collection of common data types and groupings in YANG data modeling language.
These derived common types and groupings are intended to be imported by modules that model
Traffic Engineering (TE) configuration and state capabilities.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" toc="default">
      <name>Introduction</name>
      <t>YANG configuration data, state data, Remote Procedure Calls, and
notifications for network management protocols such as the Network
Configuration Protocol (NETCONF).
The YANG language supports a small set of built-in data types and provides mechanisms
to derive other types from the built-in types.</t>
      <t>This document introduces a collection of common data types derived
from the built-in YANG data types.  The derived types and groupings 
are designed to be the common types applicable for modeling Traffic Engineering (TE) features
in model(s) defined outside of this document.</t>
    </section>
    </middle>
<back>
  </back>

</rfc>
