rfc8776xml2.original.xml   rfc8776.xml 
<?xml version="1.0" encoding="UTF-8"?> <?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.dtd" [
]>
<?rfc toc="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<rfc ipr="trust200902" docName="draft-ietf-teas-yang-te-types-14" category="std"
>
<!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="8776" category="std" obs
oletes=""
updates="" submissionType="IETF" consensus="true" xml:lang="en"
tocInclude="true" sortRefs="true" symRefs="true" version="3">
<!-- xml2rfc v2v3 conversion 2.40.1 -->
<front> <front>
<title abbrev="TE Common YANG Types">Traffic Engineering Common YANG Types</ title> <title abbrev="TE Common YANG Types">Common YANG Data Types for Traffic Engi neering</title>
<seriesInfo name="RFC" value="8776"/>
<author initials="T." surname="Saad" fullname="Tarek Saad"> <author initials="T." surname="Saad" fullname="Tarek Saad">
<organization>Juniper Networks</organization> <organization>Juniper Networks</organization>
<address> <address>
<email>tsaad@juniper.net</email> <email>tsaad@juniper.net</email>
</address> </address>
</author> </author>
<author initials="R." surname="Gandhi" fullname="Rakesh Gandhi"> <author initials="R." surname="Gandhi" fullname="Rakesh Gandhi">
<organization>Cisco Systems Inc</organization> <organization>Cisco Systems, Inc.</organization>
<address> <address>
<email>rgandhi@cisco.com</email> <email>rgandhi@cisco.com</email>
</address> </address>
</author> </author>
<author initials="X." surname="Liu" fullname="Xufeng Liu"> <author initials="X." surname="Liu" fullname="Xufeng Liu">
<organization>Volta Networks</organization> <organization>Volta Networks</organization>
<address> <address>
<email>xufeng.liu.ietf@gmail.com</email> <email>xufeng.liu.ietf@gmail.com</email>
</address> </address>
</author> </author>
<author initials="V.P." surname="Beeram" fullname="Vishnu Pavan Beeram"> <author initials="V." surname="Beeram" fullname="Vishnu Pavan Beeram">
<organization>Juniper Networks</organization> <organization>Juniper Networks</organization>
<address> <address>
<email>vbeeram@juniper.net</email> <email>vbeeram@juniper.net</email>
</address> </address>
</author> </author>
<author initials="I." surname="Bryskin" fullname="Igor Bryskin"> <author initials="I." surname="Bryskin" fullname="Igor Bryskin">
<organization>Individual</organization> <organization>Futurewei Technologies, Inc.</organization>
<address> <address>
<email>i_bryskin@yahoo.com</email> <email>i_bryskin@yahoo.com</email>
</address> </address>
</author> </author>
<date month="May" year="2020"/>
<date year="2019" month="December" day="10"/> <keyword>TE Tunnel</keyword>
<keyword>TE Model</keyword>
<workgroup>TEAS Working Group</workgroup> <keyword>TE Types</keyword>
<keyword>Internet-Draft</keyword> <keyword>TE YANG</keyword>
<keyword>TE Topology</keyword>
<keyword>TE Interfaces</keyword>
<keyword>TE LSP Model</keyword>
<abstract> <abstract>
<t>This document defines a collection of common data types and groupings i
<t>This document defines a collection of common data types and groupings in YANG n YANG data modeling language.
data modeling language.
These derived common types and groupings are intended to be imported by modules that model These derived common types and groupings are intended to be imported by modules that model
Traffic Engineering (TE) configuration and state capabilities.</t> Traffic Engineering (TE) configuration and state capabilities.</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section anchor="introduction" numbered="true" toc="default">
<section anchor="introduction" title="Introduction"> <name>Introduction</name>
<t>YANG <xref target="RFC6020" format="default"/> <xref target="RFC7950" f
<t>YANG <xref target="RFC6020"/> and <xref target="RFC7950"/> is a data modeling ormat="default"/> is a data modeling language used to model
language used to model
configuration data, state data, Remote Procedure Calls, and configuration data, state data, Remote Procedure Calls, and
notifications for network management protocols such as NETCONF <xref target="RFC notifications for network management protocols such as the Network
6241"/>. Configuration Protocol (NETCONF) <xref target="RFC6241" format="default"/>.
The YANG language supports a small set of built-in data types and provides mecha nisms The YANG language supports a small set of built-in data types and provides mecha nisms
to derive other types from the built-in types.</t> to derive other types from the built-in types.</t>
<t>This document introduces a collection of common data types derived
<t>This document introduces a collection of common data types derived
from the built-in YANG data types. The derived types and groupings 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 are designed to be the common types applicable for modeling Traffic Engineering (TE) features
in model(s) defined outside of this document.</t> in model(s) defined outside of this document.</t>
<section anchor="terminology" numbered="true" toc="default">
<section anchor="terminology" title="Terminology"> <name>Terminology</name>
<t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
<t>The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>",
“SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, and “OPTIONAL” in this "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>",
document are to be interpreted as described in BCP 14 <xref target="RFC2119"/> < "<bcp14>SHOULD NOT</bcp14>",
xref target="RFC8174"/> "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
when, and only when, they appear in all capitals, as shown here.</t> "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document
are to be interpreted as described in BCP&nbsp;14
<t>The terminology for describing YANG data models is found in <xref target="RFC <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only
7950"/>.</t> when, they appear in all capitals, as shown here.</t>
<t>The terminology for describing YANG data models is found in <xref tar
</section> get="RFC7950" format="default"/>.</t>
<section anchor="prefixes-in-data-node-names" title="Prefixes in Data Node Names </section>
"> <section anchor="prefixes-in-data-node-names" numbered="true" toc="default
">
<t>In this document, names of data nodes and other data model objects <name>Prefixes in Data Node Names</name>
<t>In this document, names of data nodes and other data model objects
are prefixed using the standard prefix associated with the are prefixed using the standard prefix associated with the
corresponding YANG imported modules, as shown in Table 1.</t> corresponding YANG imported modules, as shown in <xref target="prefixes-modules-
table"/>.</t>
<figure><artwork><![CDATA[
+-----------------+----------------------+---------------+
| Prefix | YANG module | Reference |
+-----------------+----------------------+---------------+
| yang | ietf-yang-types | [RFC6991] |
| inet | ietf-inet-types | [RFC6991] |
| rt-types | ietf-routing-types | [RFC8294] |
| te-types | ietf-te-types | this document |
| te-packet-types | ietf-te-packet-types | this document |
+-----------------+----------------------+---------------+
Table 1: Prefixes and corresponding YANG modules
]]></artwork></figure>
</section>
</section>
<section anchor="acronyms-and-abbreviations" title="Acronyms and Abbreviations">
<t><list style='empty'>
<t>GMPLS: Generalized Multiprotocol Label Switching</t>
</list></t>
<t><list style='empty'>
<t>LSP: Label Switched Path</t>
</list></t>
<t><list style='empty'>
<t>LSR: Label Switching Router</t>
</list></t>
<t><list style='empty'>
<t>LER: Label Edge Router</t>
</list></t>
<t><list style='empty'>
<t>MPLS: Multiprotocol Label Switching</t>
</list></t>
<t><list style='empty'>
<t>RSVP: Resource Reservation Protocol</t>
</list></t>
<t><list style='empty'>
<t>TE: Traffic Engineering</t>
</list></t>
<t><list style='empty'>
<t>DS-TE: Differentiated Services Traffic Engineering</t>
</list></t>
<t><list style='empty'>
<t>SRLG: Shared Link Risk Group</t>
</list></t>
<t><list style='empty'>
<t>NBMA: Non-Broadcast Multiple-access Network</t>
</list></t>
<t><list style='empty'>
<t>APS: Automatic Protection Switching</t>
</list></t>
<t><list style='empty'>
<t>SD: Signal Degrade</t>
</list></t>
<t><list style='empty'>
<t>SF: Signal Fail</t>
</list></t>
<t><list style='empty'>
<t>WTR: Wait to Restore</t>
</list></t>
<t><list style='empty'>
<t>PM: Performance Metrics</t>
</list></t>
</section>
<section anchor="overview" title="Overview">
<t>This document defines two YANG modules for common TE types: <table anchor="prefixes-modules-table">
ietf-te-types for TE generic types and ietf-te-packet-types for <name>Prefixes and Corresponding YANG Modules</name>
<thead>
<tr>
<th>Prefix</th>
<th>YANG Module</th>
<th>Reference</th>
</tr>
</thead>
<tbody>
<tr>
<td>yang</td>
<td>ietf-yang-types</td>
<td><xref target="RFC6991"/></td>
</tr>
<tr>
<td>inet</td>
<td>ietf-inet-types</td>
<td><xref target="RFC6991"/></td>
</tr>
<tr>
<td>rt-types</td>
<td>ietf-routing-types</td>
<td><xref target="RFC8294"/></td>
</tr>
<tr>
<td>te-types</td>
<td>ietf-te-types</td>
<td>This document</td>
</tr>
<tr>
<td>te-packet-types</td>
<td>ietf-te-packet-types</td>
<td>This document</td>
</tr>
</tbody>
</table>
</section>
</section>
<section anchor="acronyms-and-abbreviations" numbered="true" toc="default">
<name>Acronyms and Abbreviations</name>
<dl newline="false" spacing="normal" indent="10">
<dt>GMPLS:</dt><dd>Generalized Multiprotocol Label Switching</dd>
<dt>LSP:</dt><dd>Label Switched Path</dd>
<dt>LSR:</dt><dd>Label Switching Router</dd>
<dt>LER:</dt><dd>Label Edge Router</dd>
<dt>MPLS:</dt><dd>Multiprotocol Label Switching</dd>
<dt>RSVP:</dt><dd>Resource Reservation Protocol</dd>
<dt>TE:</dt><dd>Traffic Engineering</dd>
<dt>DS-TE:</dt><dd>Differentiated Services Traffic Engineering</dd>
<dt>SRLG:</dt><dd>Shared Risk Link Group</dd>
<dt>NBMA:</dt><dd> Non-Broadcast Multi-Access</dd>
<dt>APS:</dt><dd>Automatic Protection Switching</dd>
<dt>SD:</dt><dd>Signal Degrade</dd>
<dt>SF:</dt><dd>Signal Fail</dd>
<dt>WTR:</dt><dd>Wait-to-Restore</dd>
<dt>PM:</dt><dd>Performance Metrics</dd>
</dl>
</section>
<section anchor="overview" numbered="true" toc="default">
<name>Overview</name>
<t>This document defines two YANG modules for common TE types:
"ietf&nbhy;te&nbhy;types" for TE generic types and "ietf-te-packet-types" for
packet-specific types. Other technology-specific TE types are outside the packet-specific types. Other technology-specific TE types are outside the
scope of this document.</t> scope of this document.</t>
<section anchor="te-types-contents" numbered="true" toc="default">
<section anchor="te-types-contents" title="TE Types Module Contents"> <name>TE Types Module Contents</name>
<t>The "ietf-te-types" module (<xref target="te-types-yang-module"/>) co
<t>The ietf-te-types module contains common TE types that are independent and ntains common TE types that are independent and
agnostic of any specific technology or control plane instance.</t> agnostic of any specific technology or control-plane instance.</t>
<t>The "ietf-te-types" module contains the following YANG reusable types
<t>The ietf-te-types module contains the following YANG reusable types and group and groupings:</t>
ings:</t> <dl newline="true" spacing="normal">
<dt>te-bandwidth:</dt>
<t>te-bandwidth:</t> <dd>A YANG grouping that defines the generic TE bandwidth.
<t><list style='empty'>
<t>A YANG grouping that defines the generic TE bandwidth.
The modeling structure allows augmentation for each technology. The modeling structure allows augmentation for each technology.
For un-specified technologies, the string encoded te-bandwidth For unspecified technologies, the string-encoded "te-bandwidth"
type is used.</t> type is used.</dd>
</list></t> <dt>te-label:</dt>
<dd>A YANG grouping that defines the generic TE label.
<t>te-label:</t>
<t><list style='empty'>
<t>A YANG grouping that defines the generic TE label.
The modeling structure allows augmentation for each technology. The modeling structure allows augmentation for each technology.
For un-specified technologies, rt-types:generalized-label For unspecified technologies, "rt-types:generalized-label"
is used.</t> is used.</dd>
</list></t> <dt>performance-metrics-attributes:</dt>
<dd>A YANG grouping that defines one-way and two-way measured
<t>performance-metrics-attributes:</t> Performance Metrics (PM) and indications of anomalies on link(s) or
the path as defined in <xref target="RFC7471" format="default"/>,
<t><list style='empty'> <xref target="RFC8570" format="default"/>, and <xref target="RFC7823"
<t>A YANG grouping that defines one-way and two-way measured performance metri format="default"/>.</dd>
cs and anomalous indication on link(s) or the path as defined in <xref target="R <dt>performance-metrics-throttle-container:</dt>
FC7471"/>, <xref target="RFC8570"/>, and <xref target="RFC7823"/>.</t> <dd>A YANG grouping that defines configurable thresholds for advertise
</list></t> ment suppression and measurement intervals.</dd>
<dt>te-ds-class:</dt>
<t>performance-metrics-throttle-container:</t> <dd>A type representing the Differentiated Services (DS) Class-Type of
traffic as defined in <xref target="RFC4124" format="default"/>.</dd>
<t><list style='empty'> <dt>te-label-direction:</dt>
<t>A YANG grouping that defines configurable thresholds for advertisement supp <dd>An enumerated type for specifying the forward or reverse direction
ression and measurement intervals.</t> of a label.</dd>
</list></t> <dt>te-hop-type:</dt>
<dd>An enumerated type for specifying that a hop is loose or strict.</
<t>te-ds-class:</t> dd>
<dt>te-global-id:</dt>
<t><list style='empty'> <dd>A type representing the identifier that uniquely identifies an ope
<t>A type representing the Differentiated-Services (DS) Class-Type of traffic rator, which can be
as defined in <xref target="RFC4124"/>.</t>
</list></t>
<t>te-label-direction:</t>
<t><list style='empty'>
<t>An enumerated type for specifying the forward or reverse direction
of a label.</t>
</list></t>
<t>te-hop-type:</t>
<t><list style='empty'>
<t>An enumerated type for specifying hop as loose or strict.</t>
</list></t>
<t>te-global-id:</t>
<t><list style='empty'>
<t>A type representing the identifier that uniquely identify an operator, whic
h can be
either a provider or a client. either a provider or a client.
The definition of this type is taken from <xref target="RFC6370"/> and <xref t The
arget="RFC5003"/>. definition of this type is taken from <xref target="RFC6370"/> and <xref
target="RFC5003"/>.
This attribute type is used solely to provide a globally This attribute type is used solely to provide a globally
unique context for TE topologies.</t> unique context for TE topologies.</dd>
</list></t> <dt>te-node-id:</dt>
<dd>A type representing the identifier for a node in a TE topology.
<t>te-node-id:</t>
<t><list style='empty'>
<t>A type representing the identifier for a node in a TE topology.
The identifier is represented as 4 octets in dotted-quad notation. The identifier is represented as 4 octets in dotted-quad notation.
This attribute MAY be mapped to the Router Address described This attribute <bcp14>MAY</bcp14> be mapped to the Router Address TLV describe
in Section 2.4.1 of <xref target="RFC3630"/>, the TE Router ID described in d
Section 3 of <xref target="RFC6827"/>, the Traffic Engineering Router ID in <xref target="RFC3630" sectionFormat="of" section="2.4.1"/>, the TE
described in Section 4.3 of <xref target="RFC5305"/>, or the TE Router ID Router ID described in
described in Section 3.2.1 of <xref target="RFC6119"/>. <xref target="RFC6827" sectionFormat="of" section="3"/>, the Traffic
The reachability of such a TE node MAY be achieved by a Engineering Router ID TLV
mechanism such as Section 6.2 of <xref target="RFC6827"/>.</t> described in <xref target="RFC5305" sectionFormat="of" section="4.3"/>, or
</list></t> the TE Router ID TLV
described in <xref target="RFC6119" sectionFormat="of" section="3.2.1"/>.
<t>te-topology-id:</t> The reachability of such a TE node <bcp14>MAY</bcp14> be achieved by a
mechanism such as that described in <xref target="RFC6827" sectionFormat="of" se
<t><list style='empty'> ction="6.2"/>.</dd>
<t>A type representing the identifier for a topology. <dt>te-topology-id:</dt>
<dd>A type representing the identifier for a topology.
It is optional to have one or more prefixes at the beginning, It is optional to have one or more prefixes at the beginning,
separated by colons. The prefixes can be the network-types, separated by colons. The prefixes can be "network-types"
defined in ietf-network <xref target="RFC8345"/>, to help user to understand t as defined in the "ietf-network" module in <xref target="RFC8345" format="defa
he ult"/>, to
topology better before further inquiry.</t> help the user better understand the topology before further inquiry is made.</
</list></t> dd>
<dt>te-tp-id:</dt>
<t>te-tp-id:</t> <dd>A type representing the identifier of a TE interface Link
Termination Point (LTP) on a specific TE node where the TE link
<t><list style='empty'> connects. This attribute is mapped to a local or remote link identifie
<t>A type representing the identifier of a TE interface link termination endpo r <xref target="RFC3630" format="default"/> <xref target="RFC5305" format="defau
int (TP) on a specific TE node where the TE link connects. This attribute is ma lt"/>.</dd>
pped to local or remote link identifier in <xref target="RFC3630"/> and <xref ta <dt>te-path-disjointness:</dt>
rget="RFC5305"/>.</t> <dd>A type representing the different resource disjointness options fo
</list></t> r a TE tunnel path as defined in <xref target="RFC4872" format="default"/>.</dd>
<dt>admin-groups:</dt>
<t>te-path-disjointness:</t> <dd>A union type for a TE link's classic or extended administrative gr
oups as defined in
<t><list style='empty'> <xref target="RFC3630" format="default"/>, <xref target="RFC5305"
<t>A type representing the different resource disjointness options for a TE tu format="default"/>, and <xref target="RFC7308"/>.
nnel path as defined in <xref target="RFC4872"/>.</t> </dd>
</list></t> <dt>srlg:</dt>
<dd>A type representing the Shared Risk Link Group (SRLG) as defined i
<t>admin-groups:</t> n <xref target="RFC4203" format="default"/> and <xref target="RFC5307" format="d
efault"/>.</dd>
<t><list style='empty'> <dt>te-metric:</dt>
<t>A union type for TE link’s classic or extended administrative groups as def <dd>A type representing the TE metric as defined in <xref target="RFC3
ined in 785" format="default"/>.</dd>
<xref target="RFC3630"/> and <xref target="RFC5305"/>.</t> <dt>te-recovery-status:</dt>
</list></t> <dd>An enumerated type for the different statuses of a recovery action
as defined in <xref target="RFC4427" format="default"/> and <xref target="RFC63
<t>srlg:</t> 78" format="default"/>.</dd>
<dt>path-attribute-flags:</dt>
<t><list style='empty'> <dd>A base YANG identity for supported LSP path flags as defined in <x
<t>A type representing the Shared Risk Link Group (SRLG) as defined in <xref t ref target="RFC3209" format="default"/>, <xref target="RFC4090" format="default"
arget="RFC4203"/> and <xref target="RFC5307"/>.</t> />, <xref target="RFC4736" format="default"/>, <xref target="RFC5712" format="de
</list></t> fault"/>, <xref target="RFC4920" format="default"/>, <xref target="RFC5420" form
at="default"/>, <xref target="RFC7570" format="default"/>, <xref target="RFC4875
<t>te-metric:</t> " format="default"/>, <xref target="RFC5151" format="default"/>, <xref target="R
FC5150" format="default"/>, <xref target="RFC6001" format="default"/>, <xref tar
<t><list style='empty'> get="RFC6790" format="default"/>, <xref target="RFC7260" format="default"/>, <xr
<t>A type representing the TE metric as defined in <xref target="RFC3785"/>.</ ef target="RFC8001" format="default"/>, <xref target="RFC8149" format="default"/
t> >, and <xref target="RFC8169" format="default"/>.</dd>
</list></t> <dt>link-protection-type:</dt>
<dd>A base YANG identity for supported link protection types as
<t>te-recovery-status:</t> defined in <xref target="RFC4872" format="default"/> and <xref target="
RFC4427" format="default"/>.</dd>
<t><list style='empty'> <dt>restoration-scheme-type:</dt>
<t>An enumerated type for the different status of a recovery action as defined <dd>A base YANG identity for supported LSP restoration schemes as defi
in <xref target="RFC4427"/> and <xref target="RFC6378"/>.</t> ned in <xref target="RFC4872" format="default"/>.</dd>
</list></t> <dt>protection-external-commands:</dt>
<dd>A base YANG identity for supported protection-related external
<t>path-attribute-flags:</t> commands used for troubleshooting purposes, as defined in <xref target=
"RFC4427" format="default"/>.</dd>
<t><list style='empty'> <dt>association-type:</dt>
<t>A base YANG identity for supported LSP path flags as defined in <xref targe <dd>A base YANG identity for supported LSP association types as define
t="RFC3209"/>, <xref target="RFC4090"/>, <xref target="RFC4736"/>, <xref target= d
"RFC5712"/>, <xref target="RFC4920"/>, <xref target="RFC5420"/>, <xref target="R in <xref target="RFC6780" format="default"/>, <xref target="RFC4872"
FC7570"/>, <xref target="RFC4875"/>, <xref target="RFC5151"/>, <xref target="RFC format="default"/>, and <xref target="RFC4873" format="default"/>.</dd>
5150"/>, <xref target="RFC6001"/>, <xref target="RFC6790"/>, <xref target="RFC72 <dt>objective-function-type:</dt>
60"/>, <xref target="RFC8001"/>, <xref target="RFC8149"/>, and <xref target="RFC <dd>A base YANG identity for supported path computation objective func
8169"/>.</t> tions as defined in
</list></t> <xref target="RFC5541" format="default"/>.</dd>
<dt>te-tunnel-type:</dt>
<t>link-protection-type:</t> <dd>A base YANG identity for supported TE tunnel types as defined in <
xref target="RFC3209" format="default"/> and <xref target="RFC4875" format="defa
<t><list style='empty'> ult"/>.</dd>
<t>A base YANG identity for supported link protection types as defined in <xre <dt>lsp-encoding-types:</dt>
f target="RFC4872"/>, <xref target="RFC4427"/></t> <dd>A base YANG identity for supported LSP encoding types as defined i
</list></t> n <xref target="RFC3471" format="default"/>.</dd>
<dt>lsp-protection-type:</dt>
<t>restoration-scheme-type:</t> <dd>A base YANG identity for supported LSP protection types as defined
in <xref target="RFC4872" format="default"/> and <xref target="RFC4873" format=
<t><list style='empty'> "default"/>.</dd>
<t>A base YANG identity for supported LSP restoration schemes as defined in <x <dt>switching-capabilities:</dt>
ref target="RFC4872"/>.</t> <dd>A base YANG identity for supported interface switching capabilitie
</list></t> s as defined in <xref target="RFC3471" format="default"/>.</dd>
<dt>resource-affinities-type:</dt>
<t>protection-external-commands:</t> <dd>A base YANG identity for supported attribute filters associated wi
th a tunnel that must be satisfied for a link to be acceptable as defined in <xr
<t><list style='empty'> ef target="RFC2702" format="default"/> and <xref target="RFC3209" format="defaul
<t>A base YANG identity for supported protection external commands for trouble t"/>.</dd>
shooting purposes as defined in <xref target="RFC4427"/>.</t> <dt>path-metric-type:</dt>
</list></t> <dd>A base YANG identity for supported path metric types as defined in
<xref target="RFC3785" format="default"/> and <xref target="RFC7471" format="de
<t>association-type:</t> fault"/>.</dd>
<dt>explicit-route-hop:</dt>
<t><list style='empty'> <dd>A YANG grouping that defines supported explicit routes as defined
<t>A base YANG identity for supported Label Switched Path (LSP) association ty in <xref target="RFC3209" format="default"/> and <xref target="RFC3477" format="
pes as defined default"/>.</dd>
in <xref target="RFC6780"/>, <xref target="RFC4872"/>, <xref target="RFC4873"/ <dt>te-link-access-type:</dt>
>.</t> <dd>An enumerated type for the different TE link access types as
</list></t> defined in <xref target="RFC3630" format="default"/>.</dd>
</dl>
<t>objective-function-type:</t> </section>
<section anchor="packet-te-types-module-contents" numbered="true" toc="def
<t><list style='empty'> ault">
<t>A base YANG identity for supported path computation objective functions as <name>Packet TE Types Module Contents</name>
defined in <t>The "ietf-te-packet-types" module (<xref target="packet-te-types-yang
<xref target="RFC5541"/>.</t> -module"/>) covers the common types and groupings that are specific to packet te
</list></t> chnology.</t>
<t>The "ietf-te-packet-types" module contains the following YANG reusabl
<t>te-tunnel-type:</t> e types and groupings:</t>
<t><list style='empty'>
<t>A base YANG identity for supported TE tunnel types as defined in <xref targ
et="RFC3209"/> and <xref target="RFC4875"/>.</t>
</list></t>
<t>lsp-encoding-types:</t>
<t><list style='empty'>
<t>base YANG identity for supported LSP encoding types as defined in <xref tar
get="RFC3471"/>.</t>
</list></t>
<t>lsp-protection-type:</t>
<t><list style='empty'>
<t>A base YANG identity for supported LSP protection types as defined in <xref
target="RFC4872"/> and <xref target="RFC4873"/>.</t>
</list></t>
<t>switching-capabilities:</t>
<t><list style='empty'>
<t>A base YANG identity for supported interface switching capabilities as defi
ned in <xref target="RFC3471"/>.</t>
</list></t>
<t>resource-affinities-type:</t>
<t><list style='empty'>
<t>A base YANG identity for supported attribute filters associated with a tunn
el that must be satisfied for a link to be acceptable as defined in <xref target
="RFC2702"/> and <xref target="RFC3209"/>.</t>
</list></t>
<t>path-metric-type:</t>
<t><list style='empty'>
<t>A base YANG identity for supported path metric types as defined in <xref ta
rget="RFC3785"/> and <xref target="RFC7471"/>.</t>
</list></t>
<t>explicit-route-hop:</t>
<t><list style='empty'>
<t>A YANG grouping that defines supported explicit routes as defined in <xref
target="RFC3209"/> and <xref target="RFC3477"/>.</t>
</list></t>
<t>te-link-access-type:</t>
<t><list style='empty'>
<t>An enumerated type for the different TE link access types as defined in <xr
ef target="RFC3630"/>.</t>
</list></t>
</section>
<section anchor="packet-te-types-module-contents" title="Packet TE Types Module
Contents">
<t>The ietf-te-packet-types module covers the common types and groupings that ar
e specific to packet technology.</t>
<t>The ietf-te-packet-types module contains the following YANG reusable types an
d groupings:</t>
<t>backup-protection-type:</t>
<t><list style='empty'>
<t>A base YANG identity for supported protection types that a backup or bypass
tunnel can provide as defined in <xref target="RFC4090"/>.</t>
</list></t>
<t>te-class-type:</t>
<t><list style='empty'>
<t>A type that represents the Diffserv-TE class-type as defined in <xref targe
t="RFC4124"/>.</t>
</list></t>
<t>bc-type:</t>
<t><list style='empty'>
<t>A type that represents the Diffserv-TE Bandwidth Constraint (BC) as defined
in <xref target="RFC4124"/>.</t>
</list></t>
<t>bc-model-type:</t>
<t><list style='empty'>
<t>A base YANG identity for supported Diffserv-TE bandwidth constraint models
as defined in <xref target="RFC4125"/>, <xref target="RFC4126"/> and <xref targe
t="RFC4127"/>.</t>
</list></t>
<t>te-bandwidth-requested-type:</t>
<t><list style='empty'>
<t>An enumerated type for the different options to request bandwidth for a spe
cific tunnel.</t>
</list></t>
<t>performance-metrics-attributes-packet:</t>
<t><list style='empty'>
<t>A YANG grouping that contains the generic performance metrics and additiona
l packet specific metrics.</t>
</list></t>
</section>
</section>
<section anchor="te-types-yang-module" title="TE Types YANG Module">
<t>The ietf-te-types module imports from the following modules:</t>
<t><list style="symbols">
<t>ietf-yang-types and ietf-inet-types defined in <xref target="RFC6991"/></t>
<t>ietf-routing-types defined in <xref target="RFC8294"/></t>
</list></t>
<t>In addition to the references cross-referenced in <xref target="te-types-cont <dl newline="true" spacing="normal">
ents"> </xref>, this model also references the following RFCs in defining the ty <dt>backup-protection-type:</dt>
pes and YANG grouping of the YANG module: <dd>A base YANG identity for supported protection types that a backup
<xref target="RFC3272"/>, or bypass tunnel can provide as defined in <xref target="RFC4090" format="defaul
<xref target="RFC4202"/>, t"/>.</dd>
<xref target="RFC4328"/>, <dt>te-class-type:</dt>
<xref target="RFC4657"/>, <dd>A type that represents the Diffserv-TE Class-Type as defined in <x
<xref target="RFC5817"/>, ref target="RFC4124" format="default"/>.</dd>
<xref target="RFC6004"/>, <dt>bc-type:</dt>
<xref target="RFC6511"/>, <dd>A type that represents Diffserv-TE Bandwidth Constraints (BCs) as
<xref target="RFC6205"/>, defined in <xref target="RFC4124" format="default"/>.</dd>
<xref target="RFC7139"/>, <dt>bc-model-type:</dt>
<xref target="RFC7308"/>, <dd>A base YANG identity for supported Diffserv-TE Bandwidth Constrain
<xref target="RFC7551"/>, ts Models as defined in <xref target="RFC4125" format="default"/>, <xref target=
<xref target="RFC7571"/>, "RFC4126" format="default"/>, and <xref target="RFC4127" format="default"/>.</dd
<xref target="RFC7579"/>, <xref target="RFC4090"/>, <xref target="RFC4561"/> and >
<xref target="RFC7951"/>, <xref target="G709"/>.</t> <dt>te-bandwidth-requested-type:</dt>
<dd>An enumerated type for the different options to request bandwidth
for a specific tunnel.</dd>
<dt>performance-metrics-attributes-packet:</dt>
<dd>A YANG grouping that contains the generic performance metrics and
additional packet-specific metrics.</dd>
</dl>
</section>
</section>
<section anchor="te-types-yang-module" numbered="true" toc="default">
<name>TE Types YANG Module</name>
<t>The "ietf-te-types" module imports from the following modules:</t>
<ul spacing="normal">
<li>"ietf-yang-types" and "ietf-inet-types" as defined in <xref target="
RFC6991" format="default"/></li>
<li>"ietf-routing-types" as defined in <xref target="RFC8294"
format="default"/></li>
</ul>
<t>In addition to <xref target="RFC6991"/> and
<xref target="RFC8294"/>, this module references the following documents in
defining the types and YANG groupings:
<xref target="RFC3272" format="default"/>,
<xref target="RFC4090" format="default"/>,
<xref target="RFC4202" format="default"/>,
<xref target="RFC4328" format="default"/>,
<xref target="RFC4561" format="default"/>,
<xref target="RFC4657" format="default"/>,
<xref target="RFC5817" format="default"/>,
<xref target="RFC6004" format="default"/>,
<xref target="RFC6511" format="default"/>,
<xref target="RFC7139" format="default"/>,
<xref target="RFC7308" format="default"/>,
<xref target="RFC7551" format="default"/>,
<xref target="RFC7571" format="default"/>,
<xref target="RFC7579" format="default"/>,
and <xref target="G.709" format="default"/>.</t>
<figure title="TE basic types YANG module" anchor="fig-basic-types"><artwork><![ <sourcecode name="ietf-te-types@2020-04-06.yang" type="yang" markers="tr
CDATA[ ue"><![CDATA[
<CODE BEGINS> file "ietf-te-types@2019-11-18.yang"
module ietf-te-types { module ietf-te-types {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-te-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-te-types";
prefix te-types;
/* Replace with IANA when assigned */
prefix "te-types";
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference "RFC6991: Common YANG Data Types"; reference
"RFC 6991: Common YANG Data Types";
} }
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix yang;
reference "RFC6991: Common YANG Data Types"; reference
"RFC 6991: Common YANG Data Types";
} }
import ietf-routing-types { import ietf-routing-types {
prefix "rt-types"; prefix rt-types;
reference "RFC8294: Common YANG Data Types for the Routing Area"; reference
"RFC 8294: Common YANG Data Types for the Routing Area";
} }
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <https://datatracker.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
Editor: Tarek Saad Editor: Tarek Saad
<mailto:tsaad@juniper.net> <mailto:tsaad@juniper.net>
Editor: Rakesh Gandhi Editor: Rakesh Gandhi
<mailto:rgandhi@cisco.com> <mailto:rgandhi@cisco.com>
Editor: Vishnu Pavan Beeram Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net> <mailto:vbeeram@juniper.net>
Editor: Himanshu Shah
<mailto:hshah@ciena.com>
Editor: Xufeng Liu Editor: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com> <mailto:xufeng.liu.ietf@gmail.com>
Editor: Igor Bryskin Editor: Igor Bryskin
<mailto:i_bryskin@yahoo.com> <mailto:i_bryskin@yahoo.com>";
Editor: Young Lee
<mailto:leeyoung@huawei.com>";
description description
"This module contains a collection of generally useful TE "This YANG module contains a collection of generally useful
specific YANG data type definitions. The model fully conforms YANG data type definitions specific to TE. The model fully
to the Network Management Datastore Architecture (NMDA). conforms to the Network Management Datastore Architecture
(NMDA).
Copyright (c) 2018 IETF Trust and the persons The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
identified as authors of the code. All rights reserved. NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here.
Copyright (c) 2020 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject to
to the license terms contained in, the Simplified BSD License the license terms contained in, the Simplified BSD License set
set forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this This version of this YANG module is part of RFC 8776; see the
// note. RFC itself for full legal notices.";
// RFC Ed.: update the date below with the date of RFC publication
// and remove this note.
revision "2019-11-18" { revision 2020-04-06 {
description "Latest revision of TE types"; description
"Latest revision of TE types.";
reference reference
"RFC XXXX: A YANG Data Model for Common Traffic Engineering "RFC 8776: Common YANG Data Types for Traffic Engineering";
Types";
} }
/** /**
* Typedefs * Typedefs
*/ */
typedef admin-group { typedef admin-group {
type yang:hex-string { type yang:hex-string {
/* 01:02:03:04 */ /* 01:02:03:04 */
length "1..11"; length "1..11";
} }
description description
"Administrative group/Resource class/Color representation in "Administrative group / resource class / color representation
hex-string type. in 'hex-string' type.
The Most Significant Byte (MSB) is the farthest to the left The most significant byte in the hex-string is the farthest
in the byte sequence. Leading zero bytes in the configured to the left in the byte sequence. Leading zero bytes in the
value may be omitted for brevity."; configured value may be omitted for brevity.";
reference
reference "RFC3630 and RFC5305"; "RFC 3630: Traffic Engineering (TE) Extensions to OSPF
Version 2
RFC 5305: IS-IS Extensions for Traffic Engineering
RFC 7308: Extended Administrative Groups in MPLS Traffic
Engineering (MPLS-TE)";
} }
typedef admin-groups { typedef admin-groups {
type union { type union {
type admin-group; type admin-group;
type extended-admin-group; type extended-admin-group;
} }
description "TE administrative group derived type"; description
"Derived types for TE administrative groups.";
} }
typedef extended-admin-group { typedef extended-admin-group {
type yang:hex-string; type yang:hex-string;
description description
"Extended administrative group/Resource class/Color "Extended administrative group / resource class / color
representation in hex-string type. representation in 'hex-string' type.
The MSB is the farthest to the left in the byte sequence. The most significant byte in the hex-string is the farthest
Leading zero bytes in the configured value may be omitted to the left in the byte sequence. Leading zero bytes in the
for brevity."; configured value may be omitted for brevity.";
reference "RFC7308"; reference
"RFC 7308: Extended Administrative Groups in MPLS Traffic
Engineering (MPLS-TE)";
} }
typedef path-attribute-flags { typedef path-attribute-flags {
type union { type union {
type identityref { type identityref {
base session-attributes-flags; base session-attributes-flags;
} }
type identityref { type identityref {
base lsp-attributes-flags; base lsp-attributes-flags;
} }
} }
description "Path attributes flags type"; description
"Path attributes flags type.";
} }
typedef performance-metrics-normality { typedef performance-metrics-normality {
type enumeration { type enumeration {
enum "unknown" { enum unknown {
value 0; value 0;
description description
"Unknown."; "Unknown.";
} }
enum "normal" { enum normal {
value 1; value 1;
description description
"Normal. Indicates anomalous bit is not set"; "Normal. Indicates that the anomalous bit is not set.";
} }
enum "abnormal" { enum abnormal {
value 2; value 2;
description description
"Abnormal. Indicate that the anomalous bit is set."; "Abnormal. Indicates that the anomalous bit is set.";
} }
} }
description description
"Indicates whether a performance metric is normal (anomalous "Indicates whether a performance metric is normal (anomalous
bit not set, abnormal (anomalous bit set), or unknown."; bit not set), abnormal (anomalous bit set), or unknown.";
reference reference
"RFC7471: OSPF Traffic Engineering (TE) Metric Extensions. "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions
RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions. RFC 7823: Performance-Based Path Selection for Explicitly
RFC7823: Performance-Based Path Selection for Explicitly
Routed Label Switched Paths (LSPs) Using TE Metric Routed Label Switched Paths (LSPs) Using TE Metric
Extensions"; Extensions
RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions";
} }
typedef srlg { typedef srlg {
type uint32; type uint32;
description "SRLG type"; description
reference "RFC4203 and RFC5307"; "SRLG type.";
reference
"RFC 4203: OSPF Extensions in Support of Generalized
Multi-Protocol Label Switching (GMPLS)
RFC 5307: IS-IS Extensions in Support of Generalized
Multi-Protocol Label Switching (GMPLS)";
} }
typedef te-common-status { typedef te-common-status {
type enumeration { type enumeration {
enum up { enum up {
description description
"Enabled."; "Enabled.";
} }
enum down { enum down {
description description
"Disabled."; "Disabled.";
} }
enum testing { enum testing {
description description
"In some test mode."; "In some test mode.";
} }
enum preparing-maintenance { enum preparing-maintenance {
description description
"Resource is disabled in the control plane to prepare for "The resource is disabled in the control plane to prepare
graceful shutdown for maintenance purposes."; for a graceful shutdown for maintenance purposes.";
reference reference
"RFC5817: Graceful Shutdown in MPLS and Generalized MPLS "RFC 5817: Graceful Shutdown in MPLS and Generalized MPLS
Traffic Engineering Networks"; Traffic Engineering Networks";
} }
enum maintenance { enum maintenance {
description description
"Resource is disabled in the data plane for maintenance "The resource is disabled in the data plane for maintenance
purposes."; purposes.";
} }
enum unknown { enum unknown {
description description
"Status is unknown"; "Status is unknown.";
} }
} }
description description
"Defines a type representing the common states of a TE "Defines a type representing the common states of a TE
resource."; resource.";
} }
typedef te-bandwidth { typedef te-bandwidth {
type string { type string {
pattern pattern '0[xX](0((\.0?)?[pP](\+)?0?|(\.0?))|'
'0[xX](0((\.0?)?[pP](\+)?0?|(\.0?))|' + '1(\.([\da-fA-F]{0,5}[02468aAcCeE]?)?)?[pP](\+)?(12[0-7]|'
+ '1(\.([\da-fA-F]{0,5}[02468aAcCeE]?)?)?[pP](\+)?(12[0-7]|' + '1[01]\d|0?\d?\d)?)|0[xX][\da-fA-F]{1,8}|\d+'
+ '1[01]\d|0?\d?\d)?)|0[xX][\da-fA-F]{1,8}|\d+' + '(,(0[xX](0((\.0?)?[pP](\+)?0?|(\.0?))|'
+ '(,(0[xX](0((\.0?)?[pP](\+)?0?|(\.0?))|' + '1(\.([\da-fA-F]{0,5}[02468aAcCeE]?)?)?[pP](\+)?(12[0-7]|'
+ '1(\.([\da-fA-F]{0,5}[02468aAcCeE]?)?)?[pP](\+)?(12[0-7]|' + '1[01]\d|0?\d?\d)?)|0[xX][\da-fA-F]{1,8}|\d+))*';
+ '1[01]\d|0?\d?\d)?)|0[xX][\da-fA-F]{1,8}|\d+))*';
} }
description description
"This is the generic bandwidth type that is a string containing "This is the generic bandwidth type. It is a string containing
a list of numbers separated by commas, with each of these a list of numbers separated by commas, where each of these
number can be non-negative decimal, hex integer, or hex float: numbers can be non-negative decimal, hex integer, or
hex float:
(dec | hex | float)[*(','(dec | hex | float))] (dec | hex | float)[*(','(dec | hex | float))]
For packet switching type, the string encoding follows the For the packet-switching type, the string encoding follows
type bandwidth-ieee-float32 defined in RFC 8294 (e.g. 0x1p10), the type 'bandwidth-ieee-float32' as defined in RFC 8294
where the units are in bytes per second. (e.g., 0x1p10), where the units are in bytes per second.
For OTN switching type, a list of integers can be used, such For the Optical Transport Network (OTN) switching type,
as '0,2,3,1', indicating 2 odu0's and 1 odu3. a list of integers can be used, such as '0,2,3,1', indicating
For DWDM, a list of pairs of slot number and width can be two ODU0s and one ODU3. ('ODU' stands for 'Optical Data
used, such as '0,2,3,3', indicating a frequency slot 0 with Unit'.) For Dense Wavelength Division Multiplexing (DWDM),
a list of pairs of slot numbers and widths can be used,
such as '0,2,3,3', indicating a frequency slot 0 with
slot width 2 and a frequency slot 3 with slot width 3. slot width 2 and a frequency slot 3 with slot width 3.
Canonically, the string is represented as all lowercase and in Canonically, the string is represented as all lowercase and in
hex where the prefix '0x' precedes the hex number"; hex, where the prefix '0x' precedes the hex number.";
reference "RFC 8294, G709"; reference
} // te-bandwidth "RFC 8294: Common YANG Data Types for the Routing Area
ITU-T Recommendation G.709: Interfaces for the
optical transport network";
}
typedef te-ds-class { typedef te-ds-class {
type uint8 { type uint8 {
range '0..7'; range "0..7";
} }
description description
"The Differentiated Class-Type of traffic."; "The Differentiated Services Class-Type of traffic.";
reference "RFC4124: section-4.3.1"; reference
"RFC 4124: Protocol Extensions for Support of Diffserv-aware
MPLS Traffic Engineering, Section 4.3.1";
} }
typedef te-global-id { typedef te-global-id {
type uint32; type uint32;
description description
"An identifier to uniquely identify an operator, which can be "An identifier to uniquely identify an operator, which can be
either a provider or a client. either a provider or a client.
The definition of this type is taken from RFC6370 and RFC5003. The definition of this type is taken from RFCs 6370 and 5003.
This attribute type is used solely to provide a globally This attribute type is used solely to provide a globally
unique context for TE topologies."; unique context for TE topologies.";
reference
"RFC 5003: Attachment Individual Identifier (AII) Types for
Aggregation
RFC 6370: MPLS Transport Profile (MPLS-TP) Identifiers";
} }
typedef te-hop-type { typedef te-hop-type {
type enumeration { type enumeration {
enum loose { enum loose {
description description
"loose hop in an explicit path"; "A loose hop in an explicit path.";
} }
enum strict { enum strict {
description description
"strict hop in an explicit path"; "A strict hop in an explicit path.";
} }
} }
description description
"enumerated type for specifying loose or strict "Enumerated type for specifying loose or strict paths.";
paths"; reference
reference "RFC3209: section-4.3.2"; "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels,
Section 4.3.3";
} }
typedef te-link-access-type { typedef te-link-access-type {
type enumeration { type enumeration {
enum point-to-point { enum point-to-point {
description description
"The link is point-to-point."; "The link is point-to-point.";
} }
enum multi-access { enum multi-access {
description description
"The link is multi-access, including broadcast and NBMA."; "The link is multi-access, including broadcast and NBMA.";
} }
} }
description description
"Defines a type representing the access type of a TE link."; "Defines a type representing the access type of a TE link.";
reference reference
"RFC3630: Traffic Engineering (TE) Extensions to OSPF "RFC 3630: Traffic Engineering (TE) Extensions to OSPF
Version 2."; Version 2";
} }
typedef te-label-direction { typedef te-label-direction {
type enumeration { type enumeration {
enum forward { enum forward {
description description
"Label allocated for the forward LSP direction"; "Label allocated for the forward LSP direction.";
} }
enum reverse { enum reverse {
description description
"Label allocated for the reverse LSP direction"; "Label allocated for the reverse LSP direction.";
} }
} }
description description
"enumerated type for specifying the forward or reverse "Enumerated type for specifying the forward or reverse
label"; label.";
} }
typedef te-link-direction { typedef te-link-direction {
type enumeration { type enumeration {
enum incoming { enum incoming {
description description
"explicit route represents an incoming link on a node"; "The explicit route represents an incoming link on
a node.";
} }
enum outgoing { enum outgoing {
description description
"explicit route represents an outgoing link on a node"; "The explicit route represents an outgoing link on
a node.";
} }
} }
description description
"enumerated type for specifying direction of link on a node"; "Enumerated type for specifying the direction of a link on
a node.";
} }
typedef te-metric { typedef te-metric {
type uint32; type uint32;
description "TE metric"; description
reference "RFC3785"; "TE metric.";
reference
"RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a
second MPLS Traffic Engineering (TE) Metric";
} }
typedef te-node-id { typedef te-node-id {
type yang:dotted-quad; type yang:dotted-quad;
description description
"A type representing the identifier for a node in a TE "A type representing the identifier for a node in a TE
topology. topology.
The identifier is represented as 4 octets in dotted-quad The identifier is represented as 4 octets in dotted-quad
notation. notation.
This attribute MAY be mapped to the Router Address described This attribute MAY be mapped to the Router Address TLV
in Section 2.4.1 of [RFC3630], the TE Router ID described in described in Section 2.4.1 of RFC 3630, the TE Router ID
Section 3 of [RFC6827], the Traffic Engineering Router ID described in Section 3 of RFC 6827, the Traffic Engineering
described in Section 4.3 of [RFC5305], or the TE Router ID Router ID TLV described in Section 4.3 of RFC 5305, or the
described in Section 3.2.1 of [RFC6119]. TE Router ID TLV described in Section 3.2.1 of RFC 6119.
The reachability of such a TE node MAY be achieved by a The reachability of such a TE node MAY be achieved by a
mechanism such as Section 6.2 of [RFC6827]."; mechanism such as that described in Section 6.2 of RFC 6827.";
reference
"RFC 3630: Traffic Engineering (TE) Extensions to OSPF
Version 2, Section 2.4.1
RFC 5305: IS-IS Extensions for Traffic Engineering,
Section 4.3
RFC 6119: IPv6 Traffic Engineering in IS-IS, Section 3.2.1
RFC 6827: Automatically Switched Optical Network (ASON)
Routing for OSPFv2 Protocols, Section 3";
} }
typedef te-oper-status { typedef te-oper-status {
type te-common-status; type te-common-status;
description description
"Defines a type representing the operational status of "Defines a type representing the operational status of
a TE resource."; a TE resource.";
} }
typedef te-admin-status { typedef te-admin-status {
type te-common-status; type te-common-status;
description description
"Defines a type representing the administrative status of "Defines a type representing the administrative status of
a TE resource."; a TE resource.";
} }
typedef te-path-disjointness { typedef te-path-disjointness {
type bits { type bits {
bit node { bit node {
skipping to change at line 821 skipping to change at line 709
type te-common-status; type te-common-status;
description description
"Defines a type representing the administrative status of "Defines a type representing the administrative status of
a TE resource."; a TE resource.";
} }
typedef te-path-disjointness { typedef te-path-disjointness {
type bits { type bits {
bit node { bit node {
position 0; position 0;
description "Node disjoint."; description
"Node disjoint.";
} }
bit link { bit link {
position 1; position 1;
description "Link disjoint."; description
"Link disjoint.";
} }
bit srlg { bit srlg {
position 2; position 2;
description "SRLG (Shared Risk Link Group) disjoint."; description
"SRLG (Shared Risk Link Group) disjoint.";
} }
} }
description description
"Type of the resource disjointness for a TE tunnel path."; "Type of the resource disjointness for a TE tunnel path.";
reference reference
"RFC4872: RSVP-TE Extensions in Support of End-to-End "RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Generalized Multi-Protocol Label Switching (GMPLS) Recovery";
Recovery"; }
} // te-path-disjointness
typedef te-recovery-status { typedef te-recovery-status {
type enumeration { type enumeration {
enum normal { enum normal {
description description
"Both the recovery and working spans are fully "Both the recovery span and the working span are fully
allocated and active, data traffic is being allocated and active, data traffic is being
transported over (or selected from) the working transported over (or selected from) the working
span, and no trigger events are reported."; span, and no trigger events are reported.";
} }
enum recovery-started { enum recovery-started {
description description
"The recovery action has been started, but not completed."; "The recovery action has been started but not completed.";
} }
enum recovery-succeeded { enum recovery-succeeded {
description description
"The recovery action has succeeded. The working span has "The recovery action has succeeded. The working span has
reported a failure/degrade condition and the user traffic reported a failure/degrade condition, and the user traffic
is being transported (or selected) on the recovery span."; is being transported (or selected) on the recovery span.";
} }
enum recovery-failed { enum recovery-failed {
description description
"The recovery action has failed."; "The recovery action has failed.";
} }
enum reversion-started { enum reversion-started {
description description
"The reversion has started."; "The reversion has started.";
} }
enum reversion-succeeded { enum reversion-succeeded {
description description
"The reversion action has succeeded."; "The reversion action has succeeded.";
} }
enum reversion-failed { enum reversion-failed {
description description
"The reversion has failed."; "The reversion has failed.";
} }
enum recovery-unavailable { enum recovery-unavailable {
description description
"The recovery is unavailable -- either as a result of an "The recovery is unavailable, as a result of either an
operator Lockout command or a failure condition detected operator's lockout command or a failure condition
on the recovery span."; detected on the recovery span.";
} }
enum recovery-admin { enum recovery-admin {
description description
"The operator has issued a command switching the user "The operator has issued a command to switch the user
traffic to the recovery span."; traffic to the recovery span.";
} }
enum wait-to-restore { enum wait-to-restore {
description description
"The recovery domain is recovering from a failure/degrade "The recovery domain is recovering from a failure/degrade
condition on the working span that is being controlled by condition on the working span that is being controlled by
the Wait-to-Restore (WTR) timer."; the Wait-to-Restore (WTR) timer.";
} }
} }
description description
"Defines the status of a recovery action."; "Defines the status of a recovery action.";
reference reference
"RFC4427: Recovery (Protection and Restoration) Terminology "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS). for Generalized Multi-Protocol Label Switching (GMPLS)
RFC6378: MPLS Transport Profile (MPLS-TP) Linear Protection"; RFC 6378: MPLS Transport Profile (MPLS-TP) Linear Protection";
} }
typedef te-template-name { typedef te-template-name {
type string { type string {
pattern '/?([a-zA-Z0-9\-_.]+)(/[a-zA-Z0-9\-_.]+)*'; pattern '/?([a-zA-Z0-9\-_.]+)(/[a-zA-Z0-9\-_.]+)*';
} }
description description
"A type for the name of a TE node template or TE link "A type for the name of a TE node template or TE link
template."; template.";
} }
typedef te-topology-event-type { typedef te-topology-event-type {
type enumeration { type enumeration {
enum "add" { enum add {
value 0; value 0;
description description
"A TE node or te-link has been added."; "A TE node or TE link has been added.";
} }
enum "remove" { enum remove {
value 1; value 1;
description description
"A TE node or te-link has been removed."; "A TE node or TE link has been removed.";
} }
enum "update" { enum update {
value 2; value 2;
description description
"A TE node or te-link has been updated."; "A TE node or TE link has been updated.";
} }
} }
description "TE Event type for notifications"; description
} // te-topology-event-type "TE event type for notifications.";
}
typedef te-topology-id { typedef te-topology-id {
type union { type union {
type string { type string {
length 0; // empty string length "0";
} // empty string
type string { }
pattern type string {
'([a-zA-Z0-9\-_.]+:)*' pattern '([a-zA-Z0-9\-_.]+:)*'
+ '/?([a-zA-Z0-9\-_.]+)(/[a-zA-Z0-9\-_.]+)*'; + '/?([a-zA-Z0-9\-_.]+)(/[a-zA-Z0-9\-_.]+)*';
} }
} }
description description
"An identifier for a topology. "An identifier for a topology.
It is optional to have one or more prefixes at the beginning, It is optional to have one or more prefixes at the beginning,
separated by colons. The prefixes can be the network-types, separated by colons. The prefixes can be 'network-types' as
defined in ietf-network.yang, to help user to understand the defined in the 'ietf-network' module in RFC 8345, to help the
topology better before further inquiry."; user better understand the topology before further inquiry
reference "RFC8345"; is made.";
reference
"RFC 8345: A YANG Data Model for Network Topologies";
} }
typedef te-tp-id { typedef te-tp-id {
type union { type union {
type uint32; // Unnumbered type uint32;
type inet:ip-address; // IPv4 or IPv6 address // Unnumbered
type inet:ip-address;
// IPv4 or IPv6 address
} }
description description
"An identifier for a TE link endpoint on a node. "An identifier for a TE link endpoint on a node.
This attribute is mapped to local or remote link identifier in This attribute is mapped to a local or remote link identifier
RFC3630 and RFC5305."; as defined in RFCs 3630 and 5305.";
reference
"RFC 3630: Traffic Engineering (TE) Extensions to OSPF
Version 2
RFC 5305: IS-IS Extensions for Traffic Engineering";
} }
/* TE features */ /* TE features */
feature p2mp-te { feature p2mp-te {
description description
"Indicates support for P2MP-TE"; "Indicates support for Point-to-Multipoint TE (P2MP-TE).";
reference "RFC4875"; reference
"RFC 4875: Extensions to Resource Reservation Protocol -
Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
Label Switched Paths (LSPs)";
} }
feature frr-te { feature frr-te {
description description
"Indicates support for TE FastReroute (FRR)"; "Indicates support for TE Fast Reroute (FRR).";
reference "RFC4090"; reference
"RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP Tunnels";
} }
feature extended-admin-groups { feature extended-admin-groups {
description description
"Indicates support for TE link extended admin "Indicates support for TE link extended administrative
groups."; groups.";
reference "RFC7308"; reference
"RFC 7308: Extended Administrative Groups in MPLS Traffic
Engineering (MPLS-TE)";
} }
feature named-path-affinities { feature named-path-affinities {
description description
"Indicates support for named path affinities"; "Indicates support for named path affinities.";
} }
feature named-extended-admin-groups { feature named-extended-admin-groups {
description description
"Indicates support for named extended admin groups"; "Indicates support for named extended administrative groups.";
} }
feature named-srlg-groups { feature named-srlg-groups {
description description
"Indicates support for named SRLG groups"; "Indicates support for named SRLG groups.";
} }
feature named-path-constraints { feature named-path-constraints {
description description
"Indicates support for named path constraints"; "Indicates support for named path constraints.";
} }
feature path-optimization-metric { feature path-optimization-metric {
description description
"Indicates support for path optimization metric"; "Indicates support for path optimization metrics.";
} }
feature path-optimization-objective-function { feature path-optimization-objective-function {
description description
"Indicates support for path optimization objective function"; "Indicates support for path optimization objective functions.";
} }
/* /*
* Identities * Identities
*/ */
identity session-attributes-flags { identity session-attributes-flags {
description description
"Base identity for the RSVP-TE session attributes flags"; "Base identity for the RSVP-TE session attributes flags.";
} }
identity local-protection-desired { identity local-protection-desired {
base session-attributes-flags; base session-attributes-flags;
description "Fastreroute local protection is desired."; description
reference "RFC3209"; "Local protection is desired.";
reference
"RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels,
Section 4.7.1";
} }
identity se-style-desired { identity se-style-desired {
base session-attributes-flags; base session-attributes-flags;
description description
"Shared explicit style to allow the LSP to be "Shared explicit style, to allow the LSP to be established
established sharing resources with the old LSP."; and share resources with the old LSP.";
reference "RFC3209"; reference
"RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
} }
identity local-recording-desired { identity local-recording-desired {
base session-attributes-flags; base session-attributes-flags;
description "Local recording desired"; description
reference "RFC3209"; "Label recording is desired.";
reference
"RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels,
Section 4.7.1";
} }
identity bandwidth-protection-desired { identity bandwidth-protection-desired {
base session-attributes-flags; base session-attributes-flags;
description description
"Request FRR bandwidth protection on LSRs if "Requests FRR bandwidth protection on LSRs, if present.";
present."; reference
reference "RFC4090"; "RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP Tunnels";
} }
identity node-protection-desired { identity node-protection-desired {
base session-attributes-flags; base session-attributes-flags;
description description
"Request FRR node protection on LSRs if "Requests FRR node protection on LSRs, if present.";
present."; reference
reference "RFC4090"; "RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP Tunnels";
} }
identity path-reevaluation-request { identity path-reevaluation-request {
base session-attributes-flags; base session-attributes-flags;
description description
"This flag indicates that a path re-evaluation (of the "This flag indicates that a path re-evaluation (of the
current path in use) is requested. Note that this does current path in use) is requested. Note that this does
not trigger any LSP Reroute but instead just signals a not trigger any LSP reroutes but instead just signals a
request to evaluate whether a preferable path exists."; request to evaluate whether a preferable path exists.";
reference "RFC4736"; reference
"RFC 4736: Reoptimization of Multiprotocol Label Switching
(MPLS) Traffic Engineering (TE) Loosely Routed Label Switched
Path (LSP)";
} }
identity soft-preemption-desired { identity soft-preemption-desired {
base session-attributes-flags; base session-attributes-flags;
description description
"Soft-preemption of LSP resources is desired"; "Soft preemption of LSP resources is desired.";
reference "RFC5712"; reference
"RFC 5712: MPLS Traffic Engineering Soft Preemption";
} }
identity lsp-attributes-flags { identity lsp-attributes-flags {
description "Base identity for per hop attribute flags"; description
"Base identity for LSP attributes flags.";
} }
identity end-to-end-rerouting-desired { identity end-to-end-rerouting-desired {
base lsp-attributes-flags; base lsp-attributes-flags;
description description
"Indicates end-to-end re-routing behavior for an "Indicates end-to-end rerouting behavior for an LSP
LSP under establishment. This MAY also be used for undergoing establishment. This MAY also be used to
specifying the behavior of end-to-end LSP recovery for specify the behavior of end-to-end LSP recovery for
established LSPs."; established LSPs.";
reference "RFC4920, RFC5420, RFC7570"; reference
"RFC 4920: Crankback Signaling Extensions for MPLS and GMPLS
RSVP-TE
RFC 5420: Encoding of Attributes for MPLS LSP Establishment
Using Resource Reservation Protocol Traffic Engineering
(RSVP-TE)
RFC 7570: Label Switched Path (LSP) Attribute in the Explicit
Route Object (ERO)";
} }
identity boundary-rerouting-desired { identity boundary-rerouting-desired {
base lsp-attributes-flags; base lsp-attributes-flags;
description description
"Indicates boundary re-routing behavior for an LSP under "Indicates boundary rerouting behavior for an LSP undergoing
establishment. This MAY also be used for specifying the establishment. This MAY also be used to specify
segment-based LSP recovery through nested crankback for segment-based LSP recovery through nested crankback for
established LSPs. The boundary ABR/ASBR can either decide established LSPs. The boundary Area Border Router (ABR) /
to forward the PathErr message upstream to an upstream boundary Autonomous System Border Router (ASBR) can decide to forward
ABR/ASBR or to the ingress LSR. the PathErr message upstream to either an upstream boundary
Alternatively, it can try to select another egress boundary ABR/ASBR or the ingress LSR. Alternatively, it can try to
LSR."; select another egress boundary LSR.";
reference "RFC4920, RFC5420, RFC7570"; reference
"RFC 4920: Crankback Signaling Extensions for MPLS and GMPLS
RSVP-TE
RFC 5420: Encoding of Attributes for MPLS LSP Establishment
Using Resource Reservation Protocol Traffic Engineering
(RSVP-TE)
RFC 7570: Label Switched Path (LSP) Attribute in the Explicit
Route Object (ERO)";
} }
identity segment-based-rerouting-desired { identity segment-based-rerouting-desired {
base lsp-attributes-flags; base lsp-attributes-flags;
description description
"Indicates segment-based re-routing behavior for an LSP under "Indicates segment-based rerouting behavior for an LSP
establishment. This MAY also be used to specify the segment- undergoing establishment. This MAY also be used to specify
based LSP recovery for established LSPs."; segment-based LSP recovery for established LSPs.";
reference "RFC4920, RFC5420, RFC7570"; reference
"RFC 4920: Crankback Signaling Extensions for MPLS and GMPLS
RSVP-TE
RFC 5420: Encoding of Attributes for MPLS LSP Establishment
Using Resource Reservation Protocol Traffic Engineering
(RSVP-TE)
RFC 7570: Label Switched Path (LSP) Attribute in the Explicit
Route Object (ERO)";
} }
identity lsp-integrity-required { identity lsp-integrity-required {
base lsp-attributes-flags; base lsp-attributes-flags;
description "Indicates LSP integrity is required"; description
reference "RFC4875, RFC7570"; "Indicates that LSP integrity is required.";
reference
"RFC 4875: Extensions to Resource Reservation Protocol -
Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
Label Switched Paths (LSPs)
RFC 7570: Label Switched Path (LSP) Attribute in the Explicit
Route Object (ERO)";
} }
identity contiguous-lsp-desired { identity contiguous-lsp-desired {
base lsp-attributes-flags; base lsp-attributes-flags;
description "Indicates contiguous LSP is desired"; description
reference "RFC5151, RFC7570"; "Indicates that a contiguous LSP is desired.";
reference
"RFC 5151: Inter-Domain MPLS and GMPLS Traffic Engineering --
Resource Reservation Protocol-Traffic Engineering (RSVP-TE)
Extensions
RFC 7570: Label Switched Path (LSP) Attribute in the Explicit
Route Object (ERO)";
} }
identity lsp-stitching-desired { identity lsp-stitching-desired {
base lsp-attributes-flags; base lsp-attributes-flags;
description "Indicates LSP stitching is desired"; description
reference "RFC5150, RFC7570"; "Indicates that LSP stitching is desired.";
reference
"RFC 5150: Label Switched Path Stitching with Generalized
Multiprotocol Label Switching Traffic Engineering (GMPLS TE)
RFC 7570: Label Switched Path (LSP) Attribute in the Explicit
Route Object (ERO)";
} }
identity pre-planned-lsp-flag { identity pre-planned-lsp-flag {
base lsp-attributes-flags; base lsp-attributes-flags;
description description
"Indicates the LSP MUST be provisioned in the "Indicates that the LSP MUST be provisioned in the
control plane only."; control plane only.";
reference "RFC6001, RFC7570"; reference
"RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions for
Multi-Layer and Multi-Region Networks (MLN/MRN)
RFC 7570: Label Switched Path (LSP) Attribute in the Explicit
Route Object (ERO)";
} }
identity non-php-behavior-flag { identity non-php-behavior-flag {
base lsp-attributes-flags; base lsp-attributes-flags;
description description
"Indicates non-php behavior for the LSP is desired"; "Indicates that non-PHP (non-Penultimate Hop Popping) behavior
reference "RFC6511, RFC7570"; for the LSP is desired.";
reference
"RFC 6511: Non-Penultimate Hop Popping Behavior and Out-of-Band
Mapping for RSVP-TE Label Switched Paths
RFC 7570: Label Switched Path (LSP) Attribute in the Explicit
Route Object (ERO)";
} }
identity oob-mapping-flag { identity oob-mapping-flag {
base lsp-attributes-flags; base lsp-attributes-flags;
description description
"Indicates signaling of the egress binding information "Indicates that signaling of the egress binding information is
is out-of-band , (e.g., via Border Gateway Protocol (BGP))"; out of band (e.g., via the Border Gateway Protocol (BGP)).";
reference "RFC6511, RFC7570"; reference
"RFC 6511: Non-Penultimate Hop Popping Behavior and Out-of-Band
Mapping for RSVP-TE Label Switched Paths
RFC 7570: Label Switched Path (LSP) Attribute in the Explicit
Route Object (ERO)";
} }
identity entropy-label-capability { identity entropy-label-capability {
base lsp-attributes-flags; base lsp-attributes-flags;
description "Indicates entropy label capability"; description
reference "RFC6790, RFC7570"; "Indicates entropy label capability.";
reference
"RFC 6790: The Use of Entropy Labels in MPLS Forwarding
RFC 7570: Label Switched Path (LSP) Attribute in the Explicit
Route Object (ERO)";
} }
identity oam-mep-entity-desired { identity oam-mep-entity-desired {
base lsp-attributes-flags; base lsp-attributes-flags;
description description
"OAM Maintenance Entity Group End Point (MEP) entities desired"; "OAM Maintenance Entity Group End Point (MEP) entities
reference "RFC7260"; desired.";
reference
"RFC 7260: GMPLS RSVP-TE Extensions for Operations,
Administration, and Maintenance (OAM) Configuration";
} }
identity oam-mip-entity-desired { identity oam-mip-entity-desired {
base lsp-attributes-flags; base lsp-attributes-flags;
description description
"OAM Maintenance Entity Group Intermediate Points (MIP) "OAM Maintenance Entity Group Intermediate Points (MIP)
entities desired"; entities desired.";
reference "RFC7260"; reference
"RFC 7260: GMPLS RSVP-TE Extensions for Operations,
Administration, and Maintenance (OAM) Configuration";
} }
identity srlg-collection-desired { identity srlg-collection-desired {
base lsp-attributes-flags; base lsp-attributes-flags;
description "SRLG collection desired"; description
reference "RFC8001, RFC7570"; "SRLG collection desired.";
reference
"RFC 7570: Label Switched Path (LSP) Attribute in the Explicit
Route Object (ERO)
RFC 8001: RSVP-TE Extensions for Collecting Shared Risk
Link Group (SRLG) Information";
} }
identity loopback-desired { identity loopback-desired {
base lsp-attributes-flags; base lsp-attributes-flags;
description description
"This flag indicates a particular node on the LSP is "This flag indicates that a particular node on the LSP is
required to enter loopback mode. This can also be required to enter loopback mode. This can also be
used for specifying the loopback state of the node."; used to specify the loopback state of the node.";
reference "RFC7571"; reference
"RFC 7571: GMPLS RSVP-TE Extensions for Lock Instruct and
Loopback";
} }
identity p2mp-te-tree-eval-request { identity p2mp-te-tree-eval-request {
base lsp-attributes-flags; base lsp-attributes-flags;
description "P2MP-TE tree re-evaluation request"; description
reference "RFC8149"; "P2MP-TE tree re-evaluation request.";
reference
"RFC 8149: RSVP Extensions for Reoptimization of Loosely Routed
Point-to-Multipoint Traffic Engineering Label Switched Paths
(LSPs)";
} }
identity rtm-set-desired { identity rtm-set-desired {
base lsp-attributes-flags; base lsp-attributes-flags;
description description
"Residence Time Measurement (RTM) attribute flag requested"; "Residence Time Measurement (RTM) attribute flag requested.";
reference "RFC8169"; reference
"RFC 8169: Residence Time Measurement in MPLS Networks";
} }
identity link-protection-type { identity link-protection-type {
description "Base identity for link protection type."; description
"Base identity for the link protection type.";
} }
identity link-protection-unprotected { identity link-protection-unprotected {
base link-protection-type; base link-protection-type;
description "Unprotected link type"; description
reference "RFC4872"; "Unprotected link type.";
reference
"RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Recovery";
} }
identity link-protection-extra-traffic { identity link-protection-extra-traffic {
base link-protection-type; base link-protection-type;
description "Extra-traffic protected link type"; description
reference "RFC4427."; "Extra-Traffic protected link type.";
reference
"RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity link-protection-shared { identity link-protection-shared {
base link-protection-type; base link-protection-type;
description "Shared protected link type"; description
reference "RFC4872"; "Shared protected link type.";
reference
"RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Recovery";
} }
identity link-protection-1-for-1 { identity link-protection-1-for-1 {
base link-protection-type; base link-protection-type;
description "One for one protected link type"; description
reference "RFC4872"; "One-for-one (1:1) protected link type.";
reference
"RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Recovery";
} }
identity link-protection-1-plus-1 { identity link-protection-1-plus-1 {
base link-protection-type; base link-protection-type;
description "One plus one protected link type"; description
reference "RFC4872"; "One-plus-one (1+1) protected link type.";
reference
"RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Recovery";
} }
identity link-protection-enhanced { identity link-protection-enhanced {
base link-protection-type; base link-protection-type;
description "Enhanced protection protected link type"; description
reference "RFC4872"; "A compound link protection type derived from the underlay
TE tunnel protection configuration supporting the TE link.";
} }
identity association-type { identity association-type {
description "Base identity for tunnel association"; description
"Base identity for the tunnel association.";
} }
identity association-type-recovery { identity association-type-recovery {
base association-type; base association-type;
description description
"Association Type Recovery used to associate LSPs of "Association type for recovery, used to associate LSPs of the
same tunnel for recovery"; same tunnel for recovery.";
reference "RFC6780, RFC4872"; reference
"RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Recovery
RFC 6780: RSVP ASSOCIATION Object Extensions";
} }
identity association-type-resource-sharing { identity association-type-resource-sharing {
base association-type; base association-type;
description description
"Association Type Resource Sharing used to enable resource "Association type for resource sharing, used to enable
sharing during make-before-break."; resource sharing during make-before-break.";
reference "RFC6780, RFC4873"; reference
"RFC 4873: GMPLS Segment Recovery
RFC 6780: RSVP ASSOCIATION Object Extensions";
} }
identity association-type-double-sided-bidir { identity association-type-double-sided-bidir {
base association-type; base association-type;
description description
"Association Type Double Sided bidirectional used to associate "Association type for double-sided bidirectional LSPs,
two LSPs of two tunnels that are independently configured on used to associate two LSPs of two tunnels that are
either endpoint"; independently configured on either endpoint.";
reference "RFC7551"; reference
"RFC 7551: RSVP-TE Extensions for Associated Bidirectional
Label Switched Paths (LSPs)";
} }
identity association-type-single-sided-bidir { identity association-type-single-sided-bidir {
base association-type; base association-type;
description description
"Association Type Single Sided bidirectional used to associate "Association type for single-sided bidirectional LSPs,
two LSPs of two tunnels, where a tunnel is configured on one used to associate two LSPs of two tunnels, where one
side/endpoint, and the other tunnel is dynamically created on tunnel is configured on one side/endpoint and the other
the other endpoint"; tunnel is dynamically created on the other endpoint.";
reference "RFC6780,RFC7551"; reference
"RFC 6780: RSVP ASSOCIATION Object Extensions
RFC 7551: RSVP-TE Extensions for Associated Bidirectional
Label Switched Paths (LSPs)";
} }
identity objective-function-type { identity objective-function-type {
description "Base objective function type"; description
"Base objective function type.";
} }
identity of-minimize-cost-path { identity of-minimize-cost-path {
base objective-function-type; base objective-function-type;
description description
"Minimize cost of path objective function"; "Objective function for minimizing path cost.";
reference "RFC5541"; reference
"RFC 5541: Encoding of Objective Functions in the Path
Computation Element Communication Protocol (PCEP)";
} }
identity of-minimize-load-path { identity of-minimize-load-path {
base objective-function-type; base objective-function-type;
description description
"Minimize the load on path(s) objective "Objective function for minimizing the load on one or more
function"; paths.";
reference "RFC5541"; reference
"RFC 5541: Encoding of Objective Functions in the Path
Computation Element Communication Protocol (PCEP)";
} }
identity of-maximize-residual-bandwidth { identity of-maximize-residual-bandwidth {
base objective-function-type; base objective-function-type;
description description
"Maximize the residual bandwidth objective "Objective function for maximizing residual bandwidth.";
function"; reference
reference "RFC5541"; "RFC 5541: Encoding of Objective Functions in the Path
Computation Element Communication Protocol (PCEP)";
} }
identity of-minimize-agg-bandwidth-consumption { identity of-minimize-agg-bandwidth-consumption {
base objective-function-type; base objective-function-type;
description description
"minimize the aggregate bandwidth consumption "Objective function for minimizing aggregate bandwidth
objective function"; consumption.";
reference "RFC5541"; reference
"RFC 5541: Encoding of Objective Functions in the Path
Computation Element Communication Protocol (PCEP)";
} }
identity of-minimize-load-most-loaded-link { identity of-minimize-load-most-loaded-link {
base objective-function-type; base objective-function-type;
description description
"Minimize the load on the most loaded link "Objective function for minimizing the load on the link that
objective function"; is carrying the highest load.";
reference "RFC5541"; reference
"RFC 5541: Encoding of Objective Functions in the Path
Computation Element Communication Protocol (PCEP)";
} }
identity of-minimize-cost-path-set { identity of-minimize-cost-path-set {
base objective-function-type; base objective-function-type;
description description
"Minimize the cost on a path set objective "Objective function for minimizing the cost on a path set.";
function"; reference
reference "RFC5541"; "RFC 5541: Encoding of Objective Functions in the Path
Computation Element Communication Protocol (PCEP)";
} }
identity path-computation-method { identity path-computation-method {
description description
"base identity for supported path computation "Base identity for supported path computation mechanisms.";
mechanisms";
} }
identity path-locally-computed { identity path-locally-computed {
base path-computation-method; base path-computation-method;
description description
"indicates a constrained-path LSP in which the "Indicates a constrained-path LSP in which the
path is computed by the local LER"; path is computed by the local LER.";
reference "RFC3272 section 5.4"; reference
"RFC 3272: Overview and Principles of Internet Traffic
Engineering, Section 5.4";
} }
identity path-externally-queried { identity path-externally-queried {
base path-computation-method; base path-computation-method;
description description
"Constrained-path LSP in which the path is "Constrained-path LSP in which the path is obtained by
obtained by querying an external source, such as a PCE server. querying an external source, such as a PCE server.
In the case that an LSP is defined to be externally queried, it In the case that an LSP is defined to be externally queried,
may also have associated explicit definitions (provided it may also have associated explicit definitions (provided
to the external source to aid computation). The path that is to the external source to aid computation). The path that is
returned by the external source may require further local returned by the external source may require further local
computation on the device."; computation on the device.";
reference "RFC4657, RFC3272"; reference
"RFC 3272: Overview and Principles of Internet Traffic
Engineering
RFC 4657: Path Computation Element (PCE) Communication
Protocol Generic Requirements";
} }
identity path-explicitly-defined { identity path-explicitly-defined {
base path-computation-method; base path-computation-method;
description description
"constrained-path LSP in which the path is "Constrained-path LSP in which the path is
explicitly specified as a collection of strict or/and loose explicitly specified as a collection of strict and/or loose
hops"; hops.";
reference "RFC3209 and RFC3272"; reference
"RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
RFC 3272: Overview and Principles of Internet Traffic
Engineering";
} }
identity lsp-metric-type { identity lsp-metric-type {
description description
"Base identity for types of LSP metric specification"; "Base identity for the LSP metric specification types.";
} }
identity lsp-metric-relative { identity lsp-metric-relative {
base lsp-metric-type; base lsp-metric-type;
description description
"The metric specified for the LSPs to which this identity refers "The metric specified for the LSPs to which this identity
is specified as a relative value to the IGP metric cost to the refers is specified as a value relative to the IGP metric
LSP's tail-end."; cost to the LSP's tail end.";
reference "RFC4657"; reference
"RFC 4657: Path Computation Element (PCE) Communication
Protocol Generic Requirements";
} }
identity lsp-metric-absolute { identity lsp-metric-absolute {
base lsp-metric-type; base lsp-metric-type;
description description
"The metric specified for the LSPs to which this identity refers "The metric specified for the LSPs to which this identity
is specified as an absolute value"; refers is specified as an absolute value.";
reference "RFC4657"; reference
"RFC 4657: Path Computation Element (PCE) Communication
Protocol Generic Requirements";
} }
identity lsp-metric-inherited { identity lsp-metric-inherited {
base lsp-metric-type; base lsp-metric-type;
description description
"The metric for the LSPs to which this identity refers is "The metric for the LSPs to which this identity refers is
not specified explicitly - but rather inherited from the IGP not specified explicitly; rather, it is directly inherited
cost directly"; from the IGP cost.";
reference "RFC4657"; reference
"RFC 4657: Path Computation Element (PCE) Communication
Protocol Generic Requirements";
} }
identity te-tunnel-type { identity te-tunnel-type {
description description
"Base identity from which specific tunnel types are "Base identity from which specific tunnel types are derived.";
derived.";
} }
identity te-tunnel-p2p { identity te-tunnel-p2p {
base te-tunnel-type; base te-tunnel-type;
description description
"TE point-to-point tunnel type."; "TE Point-to-Point (P2P) tunnel type.";
reference "RFC3209"; reference
"RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
} }
identity te-tunnel-p2mp { identity te-tunnel-p2mp {
base te-tunnel-type; base te-tunnel-type;
description description
"TE point-to-multipoint tunnel type."; "TE P2MP tunnel type.";
reference "RFC4875"; reference
"RFC 4875: Extensions to Resource Reservation Protocol -
Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
Label Switched Paths (LSPs)";
} }
identity tunnel-action-type { identity tunnel-action-type {
description description
"Base identity from which specific tunnel action types "Base identity from which specific tunnel action types
are derived."; are derived.";
} }
identity tunnel-action-resetup { identity tunnel-action-resetup {
base tunnel-action-type; base tunnel-action-type;
description description
"TE tunnel action resetup. Tears the "TE tunnel action that tears down the tunnel's current LSP
tunnel's current LSP (if any) and (if any) and attempts to re-establish a new LSP.";
attempts to re-establish a new LSP";
} }
identity tunnel-action-reoptimize { identity tunnel-action-reoptimize {
base tunnel-action-type; base tunnel-action-type;
description description
"TE tunnel action reoptimize. "TE tunnel action that reoptimizes the placement of the
Reoptimizes placement of the tunnel LSP(s)"; tunnel LSP(s).";
} }
identity tunnel-action-switchpath { identity tunnel-action-switchpath {
base tunnel-action-type; base tunnel-action-type;
description description
"TE tunnel action switchpath "TE tunnel action that switches the tunnel's LSP to use the
Switches the tunnel's LSP to use the specified path"; specified path.";
} }
identity te-action-result { identity te-action-result {
description description
"Base identity from which specific TE action results "Base identity from which specific TE action results
are derived."; are derived.";
} }
identity te-action-success { identity te-action-success {
base te-action-result; base te-action-result;
description "TE action successful."; description
"TE action was successful.";
} }
identity te-action-fail { identity te-action-fail {
base te-action-result; base te-action-result;
description "TE action failed."; description
"TE action failed.";
} }
identity tunnel-action-inprogress { identity tunnel-action-inprogress {
base te-action-result; base te-action-result;
description "TE action inprogress."; description
"TE action is in progress.";
} }
identity tunnel-admin-state-type { identity tunnel-admin-state-type {
description description
"Base identity for TE tunnel admin states"; "Base identity for TE tunnel administrative states.";
} }
identity tunnel-admin-state-up { identity tunnel-admin-state-up {
base tunnel-admin-state-type; base tunnel-admin-state-type;
description "Tunnel administratively state up"; description
"Tunnel's administrative state is up.";
} }
identity tunnel-admin-state-down { identity tunnel-admin-state-down {
base tunnel-admin-state-type; base tunnel-admin-state-type;
description "Tunnel administratively state down"; description
"Tunnel's administrative state is down.";
} }
identity tunnel-state-type { identity tunnel-state-type {
description description
"Base identity for TE tunnel states"; "Base identity for TE tunnel states.";
} }
identity tunnel-state-up { identity tunnel-state-up {
base tunnel-state-type; base tunnel-state-type;
description "Tunnel state up"; description
"Tunnel's state is up.";
} }
identity tunnel-state-down { identity tunnel-state-down {
base tunnel-state-type; base tunnel-state-type;
description "Tunnel state down"; description
"Tunnel's state is down.";
} }
identity lsp-state-type { identity lsp-state-type {
description description
"Base identity for TE LSP states"; "Base identity for TE LSP states.";
} }
identity lsp-path-computing { identity lsp-path-computing {
base lsp-state-type; base lsp-state-type;
description description
"State path compute in progress"; "State path computation is in progress.";
} }
identity lsp-path-computation-ok { identity lsp-path-computation-ok {
base lsp-state-type; base lsp-state-type;
description description
"State path compute successful"; "State path computation was successful.";
} }
identity lsp-path-computation-failed { identity lsp-path-computation-failed {
base lsp-state-type; base lsp-state-type;
description description
"State path compute failed"; "State path computation failed.";
} }
identity lsp-state-setting-up { identity lsp-state-setting-up {
base lsp-state-type; base lsp-state-type;
description description
"State setting up"; "State is being set up.";
} }
identity lsp-state-setup-ok { identity lsp-state-setup-ok {
base lsp-state-type; base lsp-state-type;
description description
"State setup successful"; "State setup was successful.";
} }
identity lsp-state-setup-failed { identity lsp-state-setup-failed {
base lsp-state-type; base lsp-state-type;
description description
"State setup failed"; "State setup failed.";
} }
identity lsp-state-up { identity lsp-state-up {
base lsp-state-type; base lsp-state-type;
description "State up"; description
"State is up.";
} }
identity lsp-state-tearing-down { identity lsp-state-tearing-down {
base lsp-state-type; base lsp-state-type;
description description
"State tearing down"; "State is being torn down.";
} }
identity lsp-state-down { identity lsp-state-down {
base lsp-state-type; base lsp-state-type;
description "State down"; description
"State is down.";
} }
identity path-invalidation-action-type { identity path-invalidation-action-type {
description description
"Base identity for TE path invalidation action types"; "Base identity for TE path invalidation action types.";
} }
identity path-invalidation-action-drop { identity path-invalidation-action-drop {
base path-invalidation-action-type; base path-invalidation-action-type;
description description
"TE path invalidation action to drop"; "Upon invalidation of the TE tunnel path, the tunnel remains
reference "RFC3209 section 2.5"; valid, but any packet mapped over the tunnel is dropped.";
reference
"RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels,
Section 2.5";
} }
identity path-invalidation-action-teardown { identity path-invalidation-action-teardown {
base path-invalidation-action-type; base path-invalidation-action-type;
description description
"TE path invalidation action teardown"; "TE path invalidation action teardown.";
reference "RFC3209 section 2.5"; reference
"RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels,
Section 2.5";
} }
identity lsp-restoration-type { identity lsp-restoration-type {
description description
"Base identity from which LSP restoration types are "Base identity from which LSP restoration types are derived.";
derived.";
} }
identity lsp-restoration-restore-any { identity lsp-restoration-restore-any {
base lsp-restoration-type; base lsp-restoration-type;
description description
"Restores when any of the LSPs is affected by a failure"; "Any LSP affected by a failure is restored.";
} }
identity lsp-restoration-restore-all { identity lsp-restoration-restore-all {
base lsp-restoration-type; base lsp-restoration-type;
description description
"Restores when all the tunnel LSPs are affected by failure"; "Affected LSPs are restored after all LSPs of the tunnel are
broken.";
} }
identity restoration-scheme-type { identity restoration-scheme-type {
description description
"Base identity for LSP restoration schemes"; "Base identity for LSP restoration schemes.";
} }
identity restoration-scheme-preconfigured { identity restoration-scheme-preconfigured {
base restoration-scheme-type; base restoration-scheme-type;
description description
"Restoration LSP is preconfigured prior to the failure"; "Restoration LSP is preconfigured prior to the failure.";
reference "RFC4427"; reference
"RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity restoration-scheme-precomputed { identity restoration-scheme-precomputed {
base restoration-scheme-type; base restoration-scheme-type;
description description
"Restoration LSP is precomputed prior to the failure"; "Restoration LSP is precomputed prior to the failure.";
reference "RFC4427"; reference
"RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity restoration-scheme-presignaled { identity restoration-scheme-presignaled {
base restoration-scheme-type; base restoration-scheme-type;
description description
"Restoration LSP is presignaled prior to the failure"; "Restoration LSP is presignaled prior to the failure.";
reference "RFC4427"; reference
"RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity lsp-protection-type { identity lsp-protection-type {
description description
"Base identity from which LSP protection types are "Base identity from which LSP protection types are derived.";
derived."; reference
reference "RFC4872"; "RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Recovery";
} }
identity lsp-protection-unprotected { identity lsp-protection-unprotected {
base lsp-protection-type; base lsp-protection-type;
description description
"LSP protection 'Unprotected'"; "'Unprotected' LSP protection type.";
reference "RFC4872"; reference
"RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Recovery";
} }
identity lsp-protection-reroute-extra { identity lsp-protection-reroute-extra {
base lsp-protection-type; base lsp-protection-type;
description description
"LSP protection '(Full) Rerouting'"; "'(Full) Rerouting' LSP protection type.";
reference "RFC4872"; reference
"RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Recovery";
} }
identity lsp-protection-reroute { identity lsp-protection-reroute {
base lsp-protection-type; base lsp-protection-type;
description description
"LSP protection 'Rerouting without Extra-Traffic'"; "'Rerouting without Extra-Traffic' LSP protection type.";
reference "RFC4872"; reference
"RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Recovery";
} }
identity lsp-protection-1-for-n { identity lsp-protection-1-for-n {
base lsp-protection-type; base lsp-protection-type;
description description
"LSP protection '1:N Protection with Extra-Traffic'"; "'1:N Protection with Extra-Traffic' LSP protection type.";
reference "RFC4872"; reference
} "RFC 4872: RSVP-TE Extensions in Support of End-to-End
identity lsp-protection-unidir-1-for-1 { Generalized Multi-Protocol Label Switching (GMPLS) Recovery";
base lsp-protection-type;
description
"LSP protection '1:1 Unidirectional Protection'";
reference "RFC4872";
} }
identity lsp-protection-bidir-1-for-1 {
identity lsp-protection-1-for-1 {
base lsp-protection-type; base lsp-protection-type;
description description
"LSP protection '1:1 Bidirectional Protection'"; "LSP protection '1:1 Protection Type'.";
reference "RFC4872"; reference
"RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Recovery";
} }
identity lsp-protection-unidir-1-plus-1 { identity lsp-protection-unidir-1-plus-1 {
base lsp-protection-type; base lsp-protection-type;
description description
"LSP protection '1+1 Unidirectional Protection'"; "'1+1 Unidirectional Protection' LSP protection type.";
reference "RFC4872"; reference
"RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Recovery";
} }
identity lsp-protection-bidir-1-plus-1 { identity lsp-protection-bidir-1-plus-1 {
base lsp-protection-type; base lsp-protection-type;
description description
"LSP protection '1+1 Bidirectional Protection'"; "'1+1 Bidirectional Protection' LSP protection type.";
reference "RFC4872"; reference
"RFC 4872: RSVP-TE Extensions in Support of End-to-End
Generalized Multi-Protocol Label Switching (GMPLS) Recovery";
} }
identity lsp-protection-extra-traffic { identity lsp-protection-extra-traffic {
base lsp-protection-type; base lsp-protection-type;
description description
"LSP protection 'Extra-Traffic'"; "Extra-Traffic LSP protection type.";
reference reference
"RFC4427."; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity lsp-protection-state { identity lsp-protection-state {
description description
"Base identity of protection states for reporting "Base identity of protection states for reporting purposes.";
purposes.";
} }
identity normal { identity normal {
base lsp-protection-state; base lsp-protection-state;
description "Normal state."; description
"Normal state.";
} }
identity signal-fail-of-protection { identity signal-fail-of-protection {
base lsp-protection-state; base lsp-protection-state;
description description
"There is a signal fail condition on the protection "The protection transport entity has a signal fail condition
transport entity which has higher priority than the that is of higher priority than the forced switchover
forced switch command."; command.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity lockout-of-protection { identity lockout-of-protection {
base lsp-protection-state; base lsp-protection-state;
description description
"A Loss of Protection (LoP) command is active."; "A Loss of Protection (LoP) command is active.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity forced-switch { identity forced-switch {
base lsp-protection-state; base lsp-protection-state;
description description
"A forced switch command is active."; "A forced switchover command is active.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity signal-fail { identity signal-fail {
base lsp-protection-state; base lsp-protection-state;
description description
"There is a signal fail condition on either the working "There is a signal fail condition on either the working path
or the protection path."; or the protection path.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity signal-degrade { identity signal-degrade {
base lsp-protection-state; base lsp-protection-state;
description description
"There is an signal degrade condition on either the working "There is a signal degrade condition on either the working
or the protection path."; path or the protection path.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity manual-switch { identity manual-switch {
base lsp-protection-state; base lsp-protection-state;
description description
"A manual switch command is active."; "A manual switchover command is active.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity wait-to-restore { identity wait-to-restore {
base lsp-protection-state; base lsp-protection-state;
description description
"A wait time to restore (WTR) is running."; "A WTR timer is running.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity do-not-revert { identity do-not-revert {
base lsp-protection-state; base lsp-protection-state;
description description
"A DNR condition is active because of a non-revertive "A Do Not Revert (DNR) condition is active because of
behavior."; non-revertive behavior.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity failure-of-protocol { identity failure-of-protocol {
base lsp-protection-state; base lsp-protection-state;
description description
"The protection is not working because of a failure of "LSP protection is not working because of a protocol failure
protocol condition."; condition.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity protection-external-commands { identity protection-external-commands {
description description
"Base identity from which protection external commands "Base identity from which protection-related external commands
for trouble shooting purposes are derived."; used for troubleshooting purposes are derived.";
} }
identity action-freeze { identity action-freeze {
base protection-external-commands; base protection-external-commands;
description description
"A temporary configuration action initiated by an operator "A temporary configuration action initiated by an operator
command to prevent any switch action to be taken and as such command that prevents any switchover action from being taken
freezes the current state."; and, as such, freezes the current state.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity clear-freeze { identity clear-freeze {
base protection-external-commands; base protection-external-commands;
description description
"An action that clears the active freeze state."; "An action that clears the active freeze state.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity action-lockout-of-normal { identity action-lockout-of-normal {
base protection-external-commands; base protection-external-commands;
description description
"A temporary configuration action initiated by an operator "A temporary configuration action initiated by an operator
command to ensure that the normal traffic is not allowed command to ensure that the normal traffic is not allowed
to use the protection transport entity."; to use the protection transport entity.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity clear-lockout-of-normal { identity clear-lockout-of-normal {
base protection-external-commands; base protection-external-commands;
description description
"An action that clears the active lockout of normal state."; "An action that clears the active lockout of the
normal state.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity action-lockout-of-protection { identity action-lockout-of-protection {
base protection-external-commands; base protection-external-commands;
description description
"A temporary configuration action initiated by an operator "A temporary configuration action initiated by an operator
command to ensure that the protection transport entity is command to ensure that the protection transport entity is
temporarily not available to transport a traffic signal temporarily not available to transport a traffic signal
(either normal or extra traffic)."; (either normal or Extra-Traffic).";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity action-forced-switch { identity action-forced-switch {
base protection-external-commands; base protection-external-commands;
description description
"A switch action initiated by an operator command to switch "A switchover action initiated by an operator command to switch
the extra traffic signal, the normal traffic signal, or the the Extra-Traffic signal, the normal traffic signal, or the
null signal to the protection transport entity, unless an null signal to the protection transport entity, unless a
equal or higher priority switch command is in effect."; switchover command of equal or higher priority is in effect.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity action-manual-switch { identity action-manual-switch {
base protection-external-commands; base protection-external-commands;
description description
"A switch action initiated by an operator command to switch "A switchover action initiated by an operator command to switch
the extra traffic signal, the normal traffic signal, or the Extra-Traffic signal, the normal traffic signal, or
the null signal to the protection transport entity, unless the null signal to the protection transport entity, unless
a fault condition exists on other transport entities or an a fault condition exists on other transport entities or a
equal or higher priority switch command is in effect."; switchover command of equal or higher priority is in effect.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity action-exercise { identity action-exercise {
base protection-external-commands; base protection-external-commands;
description description
"An action to start testing if the APS communication is "An action that starts testing whether or not APS communication
operating correctly. It is lower priority than any other is operating correctly. It is of lower priority than any
state or command."; other state or command.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity clear { identity clear {
base protection-external-commands; base protection-external-commands;
description description
"An action that clears the active near-end lockout of "An action that clears the active near-end lockout of a
protection, forced switch, manual switch, WTR state, protection, forced switchover, manual switchover, WTR state,
or exercise command."; or exercise command.";
reference reference
"RFC4427"; "RFC 4427: Recovery (Protection and Restoration) Terminology
for Generalized Multi-Protocol Label Switching (GMPLS)";
} }
identity switching-capabilities { identity switching-capabilities {
description description
"Base identity for interface switching capabilities"; "Base identity for interface switching capabilities.";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity switching-psc1 { identity switching-psc1 {
base switching-capabilities; base switching-capabilities;
description description
"Packet-Switch Capable-1 (PSC-1)"; "Packet-Switch Capable-1 (PSC-1).";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity switching-evpl { identity switching-evpl {
base switching-capabilities; base switching-capabilities;
description description
"Ethernet Virtual Private Line (EVPL)"; "Ethernet Virtual Private Line (EVPL).";
reference "RFC6004"; reference
"RFC 6004: Generalized MPLS (GMPLS) Support for Metro Ethernet
Forum and G.8011 Ethernet Service Switching";
} }
identity switching-l2sc { identity switching-l2sc {
base switching-capabilities; base switching-capabilities;
description description
"Layer-2 Switch Capable (L2SC)"; "Layer-2 Switch Capable (L2SC).";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity switching-tdm { identity switching-tdm {
base switching-capabilities; base switching-capabilities;
description description
"Time-Division-Multiplex Capable (TDM)"; "Time-Division-Multiplex Capable (TDM).";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity switching-otn { identity switching-otn {
base switching-capabilities; base switching-capabilities;
description description
"OTN-TDM capable"; "OTN-TDM capable.";
reference "RFC7138"; reference
"RFC 7138: Traffic Engineering Extensions to OSPF for GMPLS
Control of Evolving G.709 Optical Transport Networks";
} }
identity switching-dcsc { identity switching-dcsc {
base switching-capabilities; base switching-capabilities;
description description
"Data Channel Switching Capable (DCSC)"; "Data Channel Switching Capable (DCSC).";
reference "RFC6002"; reference
"RFC 6002: Generalized MPLS (GMPLS) Data Channel
Switching Capable (DCSC) and Channel Set Label Extensions";
} }
identity switching-lsc { identity switching-lsc {
base switching-capabilities; base switching-capabilities;
description description
"Lambda-Switch Capable (LSC)"; "Lambda-Switch Capable (LSC).";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity switching-fsc { identity switching-fsc {
base switching-capabilities; base switching-capabilities;
description description
"Fiber-Switch Capable (FSC)"; "Fiber-Switch Capable (FSC).";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity lsp-encoding-types { identity lsp-encoding-types {
description description
"Base identity for encoding types"; "Base identity for encoding types.";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity lsp-encoding-packet { identity lsp-encoding-packet {
base lsp-encoding-types; base lsp-encoding-types;
description description
"Packet LSP encoding"; "Packet LSP encoding.";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity lsp-encoding-ethernet { identity lsp-encoding-ethernet {
base lsp-encoding-types; base lsp-encoding-types;
description description
"Ethernet LSP encoding"; "Ethernet LSP encoding.";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity lsp-encoding-pdh { identity lsp-encoding-pdh {
base lsp-encoding-types; base lsp-encoding-types;
description description
"ANSI/ETSI LSP encoding"; "ANSI/ETSI PDH LSP encoding.";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity lsp-encoding-sdh { identity lsp-encoding-sdh {
base lsp-encoding-types; base lsp-encoding-types;
description description
"SDH ITU-T G.707 / SONET ANSI T1.105 LSP encoding"; "SDH ITU-T G.707 / SONET ANSI T1.105 LSP encoding.";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity lsp-encoding-digital-wrapper { identity lsp-encoding-digital-wrapper {
base lsp-encoding-types; base lsp-encoding-types;
description description
"Digital Wrapper LSP encoding"; "Digital Wrapper LSP encoding.";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity lsp-encoding-lambda { identity lsp-encoding-lambda {
base lsp-encoding-types; base lsp-encoding-types;
description description
"Lambda (photonic) LSP encoding"; "Lambda (photonic) LSP encoding.";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity lsp-encoding-fiber { identity lsp-encoding-fiber {
base lsp-encoding-types; base lsp-encoding-types;
description description
"Fiber LSP encoding"; "Fiber LSP encoding.";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity lsp-encoding-fiber-channel { identity lsp-encoding-fiber-channel {
base lsp-encoding-types; base lsp-encoding-types;
description description
"Fiber Channel LSP encoding"; "FiberChannel LSP encoding.";
reference "RFC3471"; reference
"RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description";
} }
identity lsp-encoding-oduk { identity lsp-encoding-oduk {
base lsp-encoding-types; base lsp-encoding-types;
description description
"G.709 ODUk (Digital Path) LSP encoding"; "G.709 ODUk (Digital Path) LSP encoding.";
reference "RFC4328"; reference
"RFC 4328: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Extensions for G.709 Optical Transport Networks
Control";
} }
identity lsp-encoding-optical-channel { identity lsp-encoding-optical-channel {
base lsp-encoding-types; base lsp-encoding-types;
description description
"G.709 Optical Channel LSP encoding"; "G.709 Optical Channel LSP encoding.";
reference "RFC4328"; reference
"RFC 4328: Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Extensions for G.709 Optical Transport Networks
Control";
} }
identity lsp-encoding-line { identity lsp-encoding-line {
base lsp-encoding-types; base lsp-encoding-types;
description description
"Line (e.g., 8B/10B) LSP encoding"; "Line (e.g., 8B/10B) LSP encoding.";
reference "RFC6004"; reference
"RFC 6004: Generalized MPLS (GMPLS) Support for Metro
Ethernet Forum and G.8011 Ethernet Service Switching";
} }
identity path-signaling-type { identity path-signaling-type {
description description
"base identity from which specific LSPs path "Base identity from which specific LSP path setup types
setup types are derived"; are derived.";
} }
identity path-setup-static { identity path-setup-static {
base path-signaling-type; base path-signaling-type;
description description
"Static LSP provisioning path setup"; "Static LSP provisioning path setup.";
} }
identity path-setup-rsvp { identity path-setup-rsvp {
base path-signaling-type; base path-signaling-type;
description description
"RSVP-TE signaling path setup"; "RSVP-TE signaling path setup.";
reference "RFC3209"; reference
"RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
} }
identity path-setup-sr { identity path-setup-sr {
base path-signaling-type; base path-signaling-type;
description description
"Segment-routing path setup"; "Segment-routing path setup.";
} }
identity path-scope-type { identity path-scope-type {
description description
"base identity from which specific path "Base identity from which specific path scope types are
scope types are derived"; derived.";
} }
identity path-scope-segment { identity path-scope-segment {
base path-scope-type; base path-scope-type;
description description
"Path scope segment"; "Path scope segment.";
reference "RFC4873"; reference
"RFC 4873: GMPLS Segment Recovery";
} }
identity path-scope-end-to-end { identity path-scope-end-to-end {
base path-scope-type; base path-scope-type;
description description
"Path scope end to end"; "Path scope end to end.";
reference "RFC4873"; reference
"RFC 4873: GMPLS Segment Recovery";
} }
identity route-usage-type { identity route-usage-type {
description description
"Base identity for route usage"; "Base identity for route usage.";
} }
identity route-include-object { identity route-include-object {
base route-usage-type; base route-usage-type;
description description
"Include route object"; "'Include route' object.";
} }
identity route-exclude-object { identity route-exclude-object {
base route-usage-type; base route-usage-type;
description description
"Exclude route object"; "'Exclude route' object.";
reference "RFC4874"; reference
"RFC 4874: Exclude Routes - Extension to Resource ReserVation
Protocol-Traffic Engineering (RSVP-TE)";
} }
identity route-exclude-srlg { identity route-exclude-srlg {
base route-usage-type; base route-usage-type;
description "Exclude SRLG"; description
reference "RFC4874"; "Excludes SRLGs.";
reference
"RFC 4874: Exclude Routes - Extension to Resource ReserVation
Protocol-Traffic Engineering (RSVP-TE)";
} }
identity path-metric-type { identity path-metric-type {
description description
"Base identity for path metric type"; "Base identity for the path metric type.";
} }
identity path-metric-te { identity path-metric-te {
base path-metric-type; base path-metric-type;
description description
"TE path metric"; "TE path metric.";
reference "RFC3785"; reference
"RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a
second MPLS Traffic Engineering (TE) Metric";
} }
identity path-metric-igp { identity path-metric-igp {
base path-metric-type; base path-metric-type;
description description
"IGP path metric"; "IGP path metric.";
reference "RFC3785"; reference
"RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a
second MPLS Traffic Engineering (TE) Metric";
} }
identity path-metric-hop { identity path-metric-hop {
base path-metric-type; base path-metric-type;
description description
"Hop path metric"; "Hop path metric.";
} }
identity path-metric-delay-average { identity path-metric-delay-average {
base path-metric-type; base path-metric-type;
description description
"Unidirectional average link delay"; "Average unidirectional link delay.";
reference "RFC7471"; reference
"RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions";
} }
identity path-metric-delay-minimum { identity path-metric-delay-minimum {
base path-metric-type; base path-metric-type;
description description
"Unidirectional minimum link delay"; "Minimum unidirectional link delay.";
reference "RFC7471"; reference
"RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions";
} }
identity path-metric-residual-bandwidth { identity path-metric-residual-bandwidth {
base path-metric-type; base path-metric-type;
description description
"Unidirectional Residual Bandwidth, which is defined to be "Unidirectional Residual Bandwidth, which is defined to be
Maximum Bandwidth [RFC3630] minus the bandwidth currently Maximum Bandwidth (RFC 3630) minus the bandwidth currently
allocated to LSPs."; allocated to LSPs.";
reference "RFC7471"; reference
"RFC 3630: Traffic Engineering (TE) Extensions to OSPF
Version 2
RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions";
} }
identity path-metric-optimize-includes { identity path-metric-optimize-includes {
base path-metric-type; base path-metric-type;
description description
"A metric that optimizes the number of included resources "A metric that optimizes the number of included resources
specified in a set"; specified in a set.";
} }
identity path-metric-optimize-excludes { identity path-metric-optimize-excludes {
base path-metric-type; base path-metric-type;
description description
"A metric that optimizes to a maximum the number of excluded "A metric that optimizes to a maximum the number of excluded
resources specified in a set"; resources specified in a set.";
} }
identity path-tiebreaker-type { identity path-tiebreaker-type {
description description
"Base identity for path tie-breaker type"; "Base identity for the path tiebreaker type.";
} }
identity path-tiebreaker-minfill { identity path-tiebreaker-minfill {
base path-tiebreaker-type; base path-tiebreaker-type;
description description
"Min-Fill LSP path placement"; "Min-Fill LSP path placement.";
} }
identity path-tiebreaker-maxfill { identity path-tiebreaker-maxfill {
base path-tiebreaker-type; base path-tiebreaker-type;
description description
"Max-Fill LSP path placement"; "Max-Fill LSP path placement.";
} }
identity path-tiebreaker-random { identity path-tiebreaker-random {
base path-tiebreaker-type; base path-tiebreaker-type;
description description
"Random LSP path placement"; "Random LSP path placement.";
} }
identity resource-affinities-type { identity resource-affinities-type {
description description
"Base identity for resource affinities"; "Base identity for resource class affinities.";
reference "RFC2702"; reference
"RFC 2702: Requirements for Traffic Engineering Over MPLS";
} }
identity resource-aff-include-all { identity resource-aff-include-all {
base resource-affinities-type; base resource-affinities-type;
description description
"The set of attribute filters associated with a "The set of attribute filters associated with a
tunnel all of which must be present for a link tunnel, all of which must be present for a link
to be acceptable"; to be acceptable.";
reference "RFC2702 and RFC3209"; reference
"RFC 2702: Requirements for Traffic Engineering Over MPLS
RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
} }
identity resource-aff-include-any { identity resource-aff-include-any {
base resource-affinities-type; base resource-affinities-type;
description description
"The set of attribute filters associated with a "The set of attribute filters associated with a
tunnel any of which must be present for a link tunnel, any of which must be present for a link
to be acceptable"; to be acceptable.";
reference "RFC2702 and RFC3209"; reference
"RFC 2702: Requirements for Traffic Engineering Over MPLS
RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
} }
identity resource-aff-exclude-any { identity resource-aff-exclude-any {
base resource-affinities-type; base resource-affinities-type;
description description
"The set of attribute filters associated with a "The set of attribute filters associated with a
tunnel any of which renders a link unacceptable"; tunnel, any of which renders a link unacceptable.";
reference "RFC2702 and RFC3209"; reference
"RFC 2702: Requirements for Traffic Engineering Over MPLS
RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
} }
identity te-optimization-criterion { identity te-optimization-criterion {
description description
"Base identity for TE optimization criterion."; "Base identity for the TE optimization criteria.";
reference reference
"RFC3272: Overview and Principles of Internet Traffic "RFC 3272: Overview and Principles of Internet Traffic
Engineering."; Engineering";
} }
identity not-optimized { identity not-optimized {
base te-optimization-criterion; base te-optimization-criterion;
description "Optimization is not applied."; description
"Optimization is not applied.";
} }
identity cost { identity cost {
base te-optimization-criterion; base te-optimization-criterion;
description "Optimized on cost."; description
reference "RFC5541"; "Optimized on cost.";
reference
"RFC 5541: Encoding of Objective Functions in the Path
Computation Element Communication Protocol (PCEP)";
} }
identity delay { identity delay {
base te-optimization-criterion; base te-optimization-criterion;
description "Optimized on delay."; description
reference "RFC5541"; "Optimized on delay.";
reference
"RFC 5541: Encoding of Objective Functions in the Path
Computation Element Communication Protocol (PCEP)";
} }
identity path-computation-srlg-type { identity path-computation-srlg-type {
description description
"Base identity for SRLG path computation"; "Base identity for SRLG path computation.";
} }
identity srlg-ignore { identity srlg-ignore {
base path-computation-srlg-type; base path-computation-srlg-type;
description description
"Ignores SRLGs in path computation"; "Ignores SRLGs in the path computation.";
} }
identity srlg-strict { identity srlg-strict {
base path-computation-srlg-type; base path-computation-srlg-type;
description description
"Include strict SRLG check in path computation"; "Includes a strict SRLG check in the path computation.";
} }
identity srlg-preferred { identity srlg-preferred {
base path-computation-srlg-type; base path-computation-srlg-type;
description description
"Include preferred SRLG check in path computation"; "Includes a preferred SRLG check in the path computation.";
} }
identity srlg-weighted { identity srlg-weighted {
base path-computation-srlg-type; base path-computation-srlg-type;
description description
"Include weighted SRLG check in path computation"; "Includes a weighted SRLG check in the path computation.";
} }
/** /**
* TE bandwidth groupings * TE bandwidth groupings
**/ **/
grouping te-bandwidth { grouping te-bandwidth {
description description
"This grouping defines the generic TE bandwidth. "This grouping defines the generic TE bandwidth.
For some known data plane technologies, specific modeling For some known data-plane technologies, specific modeling
structures are specified. The string encoded te-bandwidth structures are specified. The string-encoded 'te-bandwidth'
type is used for un-specified technologies. type is used for unspecified technologies.
The modeling structure can be augmented later for other The modeling structure can be augmented later for other
technologies."; technologies.";
container te-bandwidth { container te-bandwidth {
description description
"Container that specifies TE bandwidth. The choices "Container that specifies TE bandwidth. The choices
can be augmented for specific dataplane technologies."; can be augmented for specific data-plane technologies.";
choice technology { choice technology {
default generic; default "generic";
description description
"Data plane technology type."; "Data-plane technology type.";
case generic { case generic {
leaf generic { leaf generic {
type te-bandwidth; type te-bandwidth;
description description
"Bandwidth specified in a generic format."; "Bandwidth specified in a generic format.";
} }
} }
} }
} }
} }
skipping to change at line 2142 skipping to change at line 2460
"Bandwidth specified in a generic format."; "Bandwidth specified in a generic format.";
} }
} }
} }
} }
} }
/** /**
* TE label groupings * TE label groupings
**/ **/
grouping te-label { grouping te-label {
description description
"This grouping defines the generic TE label. "This grouping defines the generic TE label.
The modeling structure can be augmented for each technology. The modeling structure can be augmented for each technology.
For un-specified technologies, rt-types:generalized-label For unspecified technologies, 'rt-types:generalized-label'
is used."; is used.";
container te-label { container te-label {
description description
"Container that specifies TE label. The choices can "Container that specifies the TE label. The choices can
be augmented for specific dataplane technologies."; be augmented for specific data-plane technologies.";
choice technology { choice technology {
default generic; default "generic";
description description
"Data plane technology type."; "Data-plane technology type.";
case generic { case generic {
leaf generic { leaf generic {
type rt-types:generalized-label; type rt-types:generalized-label;
description description
"TE label specified in a generic format."; "TE label specified in a generic format.";
} }
} }
} }
leaf direction { leaf direction {
type te-label-direction; type te-label-direction;
default 'forward'; default "forward";
description "Label direction"; description
"Label direction.";
} }
} }
} }
grouping te-topology-identifier { grouping te-topology-identifier {
description description
"Augmentation for TE topology."; "Augmentation for a TE topology.";
container te-topology-identifier { container te-topology-identifier {
description "TE topology identifier container"; description
"TE topology identifier container.";
leaf provider-id { leaf provider-id {
type te-global-id; type te-global-id;
default 0; default "0";
description description
"An identifier to uniquely identify a provider. If omitted, "An identifier to uniquely identify a provider.
it assumes the default topology provider ID=0"; If omitted, it assumes that the topology provider ID
value = 0 (the default).";
} }
leaf client-id { leaf client-id {
type te-global-id; type te-global-id;
default 0; default "0";
description description
"An identifier to uniquely identify a client. If omitted, "An identifier to uniquely identify a client.
it assumes the default topology client ID=0"; If omitted, it assumes that the topology client ID
value = 0 (the default).";
} }
leaf topology-id { leaf topology-id {
type te-topology-id; type te-topology-id;
default ''; default "";
description description
"When the datastore contains several topologies, the "When the datastore contains several topologies,
topology-id distinguishes between them. If omitted, the 'topology-id' distinguishes between them. If omitted,
default empty string topology-id is assumed"; the default (empty) string for this leaf is assumed.";
} }
} }
} }
/** /**
* TE performance metric groupings * TE performance metrics groupings
**/ **/
grouping performance-metrics-one-way-delay-loss { grouping performance-metrics-one-way-delay-loss {
description description
"Performance Metric (PM) information in real time that can "Performance Metrics (PM) information in real time that can
be applicable to links or connections. PM defined be applicable to links or connections. PM defined in this
in this grouping is applicable to generic TE performance grouping are applicable to generic TE PM as well as packet TE
metrics as well as packet TE performance metrics."; PM.";
reference reference
"RFC7471: OSPF Traffic Engineering (TE) Metric Extensions. "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions
RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions. RFC 7823: Performance-Based Path Selection for Explicitly
RFC7823: Performance-Based Path Selection for Explicitly Routed Label Switched Paths (LSPs) Using TE Metric
Routed Label Switched Paths (LSPs) Using TE Metric Extensions
Extensions"; RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions";
leaf one-way-delay { leaf one-way-delay {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
description "One-way delay or latency in micro seconds."; description
"One-way delay or latency in microseconds.";
} }
leaf one-way-delay-normality { leaf one-way-delay-normality {
type te-types:performance-metrics-normality; type te-types:performance-metrics-normality;
description "One-way delay normality."; description
"One-way delay normality.";
} }
} }
grouping performance-metrics-two-way-delay-loss { grouping performance-metrics-two-way-delay-loss {
description description
"Performance metric information in real time that can "PM information in real time that can be applicable to links or
be applicable to links or connections. PM defined connections. PM defined in this grouping are applicable to
in this grouping is applicable to generic TE performance generic TE PM as well as packet TE PM.";
metrics as well as packet TE performance metrics.";
reference reference
"RFC7471: OSPF Traffic Engineering (TE) Metric Extensions. "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions
RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions. RFC 7823: Performance-Based Path Selection for Explicitly
RFC7823: Performance-Based Path Selection for Explicitly Routed Label Switched Paths (LSPs) Using TE Metric
Routed Label Switched Paths (LSPs) Using TE Metric Extensions
Extensions"; RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions";
leaf two-way-delay { leaf two-way-delay {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
description "Two-way delay or latency in micro seconds."; description
"Two-way delay or latency in microseconds.";
} }
leaf two-way-delay-normality { leaf two-way-delay-normality {
type te-types:performance-metrics-normality; type te-types:performance-metrics-normality;
description "Two-way delay normality."; description
"Two-way delay normality.";
} }
} }
grouping performance-metrics-one-way-bandwidth { grouping performance-metrics-one-way-bandwidth {
description description
"Performance metric information in real time that can "PM information in real time that can be applicable to links.
be applicable to links. PM defined PM defined in this grouping are applicable to generic TE PM
in this grouping is applicable to generic TE performance as well as packet TE PM.";
metrics as well as packet TE performance metrics.";
reference reference
"RFC7471: OSPF Traffic Engineering (TE) Metric Extensions. "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions
RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions. RFC 7823: Performance-Based Path Selection for Explicitly
RFC7823: Performance-Based Path Selection for Explicitly Routed Label Switched Paths (LSPs) Using TE Metric
Routed Label Switched Paths (LSPs) Using TE Metric Extensions
Extensions"; RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions";
leaf one-way-residual-bandwidth { leaf one-way-residual-bandwidth {
type rt-types:bandwidth-ieee-float32; type rt-types:bandwidth-ieee-float32;
units 'bytes per second'; units "bytes per second";
default '0x0p0'; default "0x0p0";
description description
"Residual bandwidth that subtracts tunnel "Residual bandwidth that subtracts tunnel reservations from
reservations from Maximum Bandwidth (or link capacity) Maximum Bandwidth (or link capacity) (RFC 3630) and
[RFC3630] and provides an aggregated remainder across QoS provides an aggregated remainder across QoS classes.";
classes."; reference
"RFC 3630: Traffic Engineering (TE) Extensions to OSPF
Version 2";
} }
leaf one-way-residual-bandwidth-normality { leaf one-way-residual-bandwidth-normality {
type te-types:performance-metrics-normality; type te-types:performance-metrics-normality;
default 'normal'; default "normal";
description "Residual bandwidth normality."; description
"Residual bandwidth normality.";
} }
leaf one-way-available-bandwidth { leaf one-way-available-bandwidth {
type rt-types:bandwidth-ieee-float32; type rt-types:bandwidth-ieee-float32;
units 'bytes per second'; units "bytes per second";
default '0x0p0'; default "0x0p0";
description description
"Available bandwidth that is defined to be residual "Available bandwidth that is defined to be residual
bandwidth minus the measured bandwidth used for the bandwidth minus the measured bandwidth used for the
actual forwarding of non-RSVP-TE LSP packets. For a actual forwarding of non-RSVP-TE LSP packets. For a
bundled link, available bandwidth is defined to be the bundled link, available bandwidth is defined to be the
sum of the component link available bandwidths."; sum of the component link available bandwidths.";
} }
leaf one-way-available-bandwidth-normality { leaf one-way-available-bandwidth-normality {
type te-types:performance-metrics-normality; type te-types:performance-metrics-normality;
default 'normal'; default "normal";
description "Available bandwidth normality."; description
"Available bandwidth normality.";
} }
leaf one-way-utilized-bandwidth { leaf one-way-utilized-bandwidth {
type rt-types:bandwidth-ieee-float32; type rt-types:bandwidth-ieee-float32;
units 'bytes per second'; units "bytes per second";
default '0x0p0'; default "0x0p0";
description description
"Bandwidth utilization that represents the actual "Bandwidth utilization that represents the actual
utilization of the link (i.e. as measured in the router). utilization of the link (i.e., as measured in the router).
For a bundled link, bandwidth utilization is defined to For a bundled link, bandwidth utilization is defined to
be the sum of the component link bandwidth be the sum of the component link bandwidth utilizations.";
utilizations.";
} }
leaf one-way-utilized-bandwidth-normality { leaf one-way-utilized-bandwidth-normality {
type te-types:performance-metrics-normality; type te-types:performance-metrics-normality;
default 'normal'; default "normal";
description "Bandwidth utilization normality."; description
"Bandwidth utilization normality.";
} }
} }
grouping one-way-performance-metrics { grouping one-way-performance-metrics {
description description
"One-way performance metrics throttle grouping."; "One-way PM throttle grouping.";
leaf one-way-delay { leaf one-way-delay {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
default 0; default "0";
description "One-way delay or latency in micro seconds."; description
"One-way delay or latency in microseconds.";
} }
leaf one-way-residual-bandwidth { leaf one-way-residual-bandwidth {
type rt-types:bandwidth-ieee-float32; type rt-types:bandwidth-ieee-float32;
units 'bytes per second'; units "bytes per second";
default '0x0p0'; default "0x0p0";
description description
"Residual bandwidth that subtracts tunnel "Residual bandwidth that subtracts tunnel reservations from
reservations from Maximum Bandwidth (or link capacity) Maximum Bandwidth (or link capacity) (RFC 3630) and
[RFC3630] and provides an aggregated remainder across QoS provides an aggregated remainder across QoS classes.";
classes."; reference
"RFC 3630: Traffic Engineering (TE) Extensions to OSPF
Version 2";
} }
leaf one-way-available-bandwidth { leaf one-way-available-bandwidth {
type rt-types:bandwidth-ieee-float32; type rt-types:bandwidth-ieee-float32;
units 'bytes per second'; units "bytes per second";
default '0x0p0'; default "0x0p0";
description description
"Available bandwidth that is defined to be residual "Available bandwidth that is defined to be residual
bandwidth minus the measured bandwidth used for the bandwidth minus the measured bandwidth used for the
actual forwarding of non-RSVP-TE LSP packets. For a actual forwarding of non-RSVP-TE LSP packets. For a
bundled link, available bandwidth is defined to be the bundled link, available bandwidth is defined to be the
sum of the component link available bandwidths."; sum of the component link available bandwidths.";
} }
leaf one-way-utilized-bandwidth { leaf one-way-utilized-bandwidth {
type rt-types:bandwidth-ieee-float32; type rt-types:bandwidth-ieee-float32;
units 'bytes per second'; units "bytes per second";
default '0x0p0'; default "0x0p0";
description description
"Bandwidth utilization that represents the actual "Bandwidth utilization that represents the actual
utilization of the link (i.e. as measured in the router). utilization of the link (i.e., as measured in the router).
For a bundled link, bandwidth utilization is defined to For a bundled link, bandwidth utilization is defined to
be the sum of the component link bandwidth be the sum of the component link bandwidth utilizations.";
utilizations.";
} }
} }
grouping two-way-performance-metrics { grouping two-way-performance-metrics {
description description
"Two-way performance metrics throttle grouping."; "Two-way PM throttle grouping.";
leaf two-way-delay { leaf two-way-delay {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
default 0; default "0";
description "Two-way delay or latency in micro seconds."; description
"Two-way delay or latency in microseconds.";
} }
} }
grouping performance-metrics-thresholds { grouping performance-metrics-thresholds {
description description
"Grouping for configurable thresholds for measured attributes"; "Grouping for configurable thresholds for measured
attributes.";
uses one-way-performance-metrics; uses one-way-performance-metrics;
uses two-way-performance-metrics; uses two-way-performance-metrics;
} }
grouping performance-metrics-attributes { grouping performance-metrics-attributes {
description description
"A container containing performance metric attributes."; "Contains PM attributes.";
container performance-metrics-one-way { container performance-metrics-one-way {
description description
"One-way link performance information in real time."; "One-way link performance information in real time.";
reference reference
"RFC7471: OSPF Traffic Engineering (TE) Metric Extensions. "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions
RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions. RFC 7823: Performance-Based Path Selection for Explicitly
RFC7823: Performance-Based Path Selection for Explicitly
Routed Label Switched Paths (LSPs) Using TE Metric Routed Label Switched Paths (LSPs) Using TE Metric
Extensions"; Extensions
RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions";
uses performance-metrics-one-way-delay-loss; uses performance-metrics-one-way-delay-loss;
uses performance-metrics-one-way-bandwidth; uses performance-metrics-one-way-bandwidth;
} }
container performance-metrics-two-way { container performance-metrics-two-way {
description description
"Two-way link performance information in real time."; "Two-way link performance information in real time.";
reference reference
"RFC7471: OSPF Traffic Engineering (TE) Metric Extensions. "RFC 6374: Packet Loss and Delay Measurement for MPLS
RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions. Networks";
RFC7823: Performance-Based Path Selection for Explicitly
Routed Label Switched Paths (LSPs) Using TE Metric
Extensions";
uses performance-metrics-two-way-delay-loss; uses performance-metrics-two-way-delay-loss;
} }
} }
grouping performance-metrics-throttle-container { grouping performance-metrics-throttle-container {
description description
"A container controlling performance metric throttle."; "Controls PM throttling.";
container throttle { container throttle {
must "suppression-interval >= measure-interval" { must 'suppression-interval >= measure-interval' {
error-message error-message
"suppression-interval cannot be less then "'suppression-interval' cannot be less than "
measure-interval."; + "'measure-interval'.";
description description
"Constraint on suppression-interval and "Constraint on 'suppression-interval' and
measure-interval."; 'measure-interval'.";
} }
description description
"Link performance information in real time."; "Link performance information in real time.";
reference reference
"RFC7471: OSPF Traffic Engineering (TE) Metric Extensions. "RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions
RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions. RFC 7823: Performance-Based Path Selection for Explicitly
RFC7823: Performance-Based Path Selection for Explicitly
Routed Label Switched Paths (LSPs) Using TE Metric Routed Label Switched Paths (LSPs) Using TE Metric
Extensions"; Extensions
RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions";
leaf one-way-delay-offset { leaf one-way-delay-offset {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
default 0; default "0";
description description
"Offset value to be added to the measured delay value."; "Offset value to be added to the measured delay value.";
} }
leaf measure-interval { leaf measure-interval {
type uint32; type uint32;
default 30; default "30";
description description
"Interval in seconds to measure the extended metric "Interval, in seconds, to measure the extended metric
values."; values.";
} }
leaf advertisement-interval { leaf advertisement-interval {
type uint32; type uint32;
default 0; default "0";
description description
"Interval in seconds to advertise the extended metric "Interval, in seconds, to advertise the extended metric
values."; values.";
} }
leaf suppression-interval { leaf suppression-interval {
type uint32 { type uint32 {
range '1 .. max'; range "1..max";
} }
default 120; default "120";
description description
"Interval in seconds to suppress advertising the extended "Interval, in seconds, to suppress advertisement of the
metric values."; extended metric values.";
reference "RFC 7810, Section-6"; reference
"RFC 8570: IS-IS Traffic Engineering (TE) Metric
Extensions, Section 6";
} }
container threshold-out { container threshold-out {
uses performance-metrics-thresholds; uses performance-metrics-thresholds;
description description
"If the measured parameter falls outside an upper bound "If the measured parameter falls outside an upper bound
for all but the min delay metric (or lower bound for for all but the minimum-delay metric (or a lower bound
min-delay metric only) and the advertised value is not for the minimum-delay metric only) and the advertised
already outside that bound, anomalous announcement will be value is not already outside that bound, an 'anomalous'
triggered."; announcement (anomalous bit set) will be triggered.";
} }
container threshold-in { container threshold-in {
uses performance-metrics-thresholds; uses performance-metrics-thresholds;
description description
"If the measured parameter falls inside an upper bound "If the measured parameter falls inside an upper bound
for all but the min delay metric (or lower bound for for all but the minimum-delay metric (or a lower bound
min-delay metric only) and the advertised value is not for the minimum-delay metric only) and the advertised
already inside that bound, normal (anomalous-flag cleared) value is not already inside that bound, a 'normal'
announcement will be triggered."; announcement (anomalous bit cleared) will be triggered.";
} }
container threshold-accelerated-advertisement { container threshold-accelerated-advertisement {
description description
"When the difference between the last advertised value and "When the difference between the last advertised value and
current measured value exceed this threshold, anomalous the current measured value exceeds this threshold, an
announcement will be triggered."; 'anomalous' announcement (anomalous bit set) will be
triggered.";
uses performance-metrics-thresholds; uses performance-metrics-thresholds;
} }
} }
} // performance-metrics-throttle-container }
/** /**
* TE tunnel generic groupings * TE tunnel generic groupings
**/ **/
grouping explicit-route-hop { grouping explicit-route-hop {
description description
"The explicit route entry grouping"; "The explicit route entry grouping.";
choice type { choice type {
description description
"The explicit route entry type"; "The explicit route entry type.";
case numbered-node-hop { case numbered-node-hop {
container numbered-node-hop { container numbered-node-hop {
leaf node-id { leaf node-id {
type te-node-id; type te-node-id;
mandatory true; mandatory true;
description description
"The identifier of a node in the TE topology."; "The identifier of a node in the TE topology.";
} }
leaf hop-type { leaf hop-type {
type te-hop-type; type te-hop-type;
default 'strict'; default "strict";
description "strict or loose hop"; description
"Strict or loose hop.";
} }
description "Numbered node route hop"; description
"Numbered node route hop.";
reference reference
"RFC3209: section 4.3 for EXPLICIT_ROUTE in RSVP-TE "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels,
RFC3477: Signalling Unnumbered Links in RSVP-TE"; Section 4.3, EXPLICIT_ROUTE in RSVP-TE
RFC 3477: Signalling Unnumbered Links in Resource
ReSerVation Protocol - Traffic Engineering (RSVP-TE)";
} }
} }
case numbered-link-hop { case numbered-link-hop {
container numbered-link-hop { container numbered-link-hop {
leaf link-tp-id { leaf link-tp-id {
type te-tp-id; type te-tp-id;
mandatory true; mandatory true;
description description
"TE link termination point identifier."; "TE Link Termination Point (LTP) identifier.";
} }
leaf hop-type { leaf hop-type {
type te-hop-type; type te-hop-type;
default 'strict'; default "strict";
description "strict or loose hop"; description
"Strict or loose hop.";
} }
leaf direction { leaf direction {
type te-link-direction; type te-link-direction;
default 'outgoing'; default "outgoing";
description "Link route object direction"; description
"Link route object direction.";
} }
description description
"Numbered link explicit route hop"; "Numbered link explicit route hop.";
reference reference
"RFC3209: section 4.3 for EXPLICIT_ROUTE in RSVP-TE "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels,
RFC3477: Signalling Unnumbered Links in RSVP-TE"; Section 4.3, EXPLICIT_ROUTE in RSVP-TE
RFC 3477: Signalling Unnumbered Links in Resource
ReSerVation Protocol - Traffic Engineering (RSVP-TE)";
} }
} }
case unnumbered-link-hop { case unnumbered-link-hop {
container unnumbered-link-hop { container unnumbered-link-hop {
leaf link-tp-id { leaf link-tp-id {
type te-tp-id; type te-tp-id;
mandatory true; mandatory true;
description description
"TE link termination point identifier. The combination "TE LTP identifier. The combination of the TE link ID
of TE link ID and the TE node ID is used to identify an and the TE node ID is used to identify an unnumbered
unnumbered TE link."; TE link.";
} }
leaf node-id { leaf node-id {
type te-node-id; type te-node-id;
mandatory true; mandatory true;
description description
"The identifier of a node in the TE topology."; "The identifier of a node in the TE topology.";
} }
leaf hop-type { leaf hop-type {
type te-hop-type; type te-hop-type;
default 'strict'; default "strict";
description "strict or loose hop"; description
"Strict or loose hop.";
} }
leaf direction { leaf direction {
type te-link-direction; type te-link-direction;
default 'outgoing'; default "outgoing";
description "Link route object direction"; description
"Link route object direction.";
} }
description description
"Unnumbered link explicit route hop"; "Unnumbered link explicit route hop.";
reference reference
"RFC3209: section 4.3 for EXPLICIT_ROUTE in RSVP-TE "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels,
RFC3477: Signalling Unnumbered Links in RSVP-TE"; Section 4.3, EXPLICIT_ROUTE in RSVP-TE
RFC 3477: Signalling Unnumbered Links in Resource
ReSerVation Protocol - Traffic Engineering (RSVP-TE)";
} }
} }
case as-number { case as-number {
container as-number-hop { container as-number-hop {
leaf as-number { leaf as-number {
type inet:as-number; type inet:as-number;
mandatory true; mandatory true;
description "The AS number"; description
"The Autonomous System (AS) number.";
} }
leaf hop-type { leaf hop-type {
type te-hop-type; type te-hop-type;
default 'strict'; default "strict";
description "strict or loose hop"; description
"Strict or loose hop.";
} }
description description
"Autonomous System explicit route hop"; "AS explicit route hop.";
} }
} }
case label { case label {
container label-hop { container label-hop {
description "Label hop type"; description
"Label hop type.";
uses te-label; uses te-label;
} }
description description
"The label explicit route hop type"; "The label explicit route hop type.";
} }
} }
} }
grouping record-route-state { grouping record-route-state {
description description
"The record route grouping"; "The Record Route grouping.";
leaf index { leaf index {
type uint32; type uint32;
description description
"Record route hop index. The index is used to "Record Route hop index. The index is used to
identify an entry in the list. The order of entries identify an entry in the list. The order of entries
is defined by the user without relying on key values"; is defined by the user without relying on key values.";
} }
choice type { choice type {
description description
"The record route entry type"; "The Record Route entry type.";
case numbered-node-hop { case numbered-node-hop {
container numbered-node-hop { container numbered-node-hop {
description "Numbered node route hop container"; description
"Numbered node route hop container.";
leaf node-id { leaf node-id {
type te-node-id; type te-node-id;
mandatory true; mandatory true;
description description
"The identifier of a node in the TE topology."; "The identifier of a node in the TE topology.";
} }
leaf-list flags { leaf-list flags {
type path-attribute-flags; type path-attribute-flags;
description "Record route per hop flags"; description
reference "RFC3209, RFC4090, RFC4561"; "Path attributes flags.";
reference
"RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP
Tunnels
RFC 4561: Definition of a Record Route Object (RRO)
Node-Id Sub-Object";
} }
} }
description "Numbered node route hop"; description
"Numbered node route hop.";
} }
case numbered-link-hop { case numbered-link-hop {
container numbered-link-hop { container numbered-link-hop {
description "Numbered link route hop container"; description
"Numbered link route hop container.";
leaf link-tp-id { leaf link-tp-id {
type te-tp-id; type te-tp-id;
mandatory true; mandatory true;
description description
"Numbered TE link termination point identifier."; "Numbered TE LTP identifier.";
} }
leaf-list flags { leaf-list flags {
type path-attribute-flags; type path-attribute-flags;
description "Record route per hop flags"; description
reference "RFC3209, RFC4090, RFC4561"; "Path attributes flags.";
reference
"RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP
Tunnels
RFC 4561: Definition of a Record Route Object (RRO)
Node-Id Sub-Object";
} }
} }
description "Numbered link route hop"; description
"Numbered link route hop.";
} }
case unnumbered-link-hop { case unnumbered-link-hop {
container unnumbered-link-hop { container unnumbered-link-hop {
leaf link-tp-id { leaf link-tp-id {
type te-tp-id; type te-tp-id;
mandatory true; mandatory true;
description description
"TE link termination point identifier. The combination "TE LTP identifier. The combination of the TE link ID
of TE link ID and the TE node ID is used to identify an and the TE node ID is used to identify an unnumbered
unnumbered TE link."; TE link.";
} }
leaf node-id { leaf node-id {
type te-node-id; type te-node-id;
description description
"The identifier of a node in the TE topology."; "The identifier of a node in the TE topology.";
} }
leaf-list flags { leaf-list flags {
type path-attribute-flags; type path-attribute-flags;
description "Record route per hop flags"; description
reference "RFC3209, RFC4090, RFC4561"; "Path attributes flags.";
reference
"RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP
Tunnels
RFC 4561: Definition of a Record Route Object (RRO)
Node-Id Sub-Object";
} }
description description
"Unnumbered link record route hop"; "Unnumbered link Record Route hop.";
reference reference
"RFC3477: Signalling Unnumbered Links in "RFC 3477: Signalling Unnumbered Links in Resource
RSVP-TE"; ReSerVation Protocol - Traffic Engineering (RSVP-TE)";
} }
description "Unnumbered link route hop"; description
"Unnumbered link route hop.";
} }
case label { case label {
container label-hop { container label-hop {
description "Label route hop type"; description
"Label route hop type.";
uses te-label; uses te-label;
leaf-list flags { leaf-list flags {
type path-attribute-flags; type path-attribute-flags;
description "Record route per hop flags"; description
reference "RFC3209, RFC4090, RFC4561"; "Path attributes flags.";
reference
"RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP
Tunnels
RFC 4561: Definition of a Record Route Object (RRO)
Node-Id Sub-Object";
} }
} }
description description
"The Label record route entry types"; "The label Record Route entry types.";
} }
} }
} }
grouping label-restriction-info { grouping label-restriction-info {
description "Label set item info"; description
"Label set item information.";
leaf restriction { leaf restriction {
type enumeration { type enumeration {
enum inclusive { enum inclusive {
description "The label or label range is inclusive."; description
"The label or label range is inclusive.";
} }
enum exclusive { enum exclusive {
description "The label or label range is exclusive."; description
"The label or label range is exclusive.";
} }
} }
default 'inclusive'; default "inclusive";
description description
"Whether the list item is inclusive or exclusive."; "Indicates whether the list item is inclusive or exclusive.";
} }
leaf index { leaf index {
type uint32; type uint32;
description description
"The index of the label restriction list entry."; "The index of the label restriction list entry.";
} }
container label-start { container label-start {
must "(not(../label-end/te-label/direction) and" + must "(not(../label-end/te-label/direction) and"
" not(te-label/direction))" + " not(te-label/direction))"
+ " or " + " or "
+ "(../label-end/te-label/direction = te-label/direction)" + "(../label-end/te-label/direction = te-label/direction)"
+ " or " + " or "
+ "(not(te-label/direction) and" + + "(not(te-label/direction) and"
" (../label-end/te-label/direction = 'forward'))" + " (../label-end/te-label/direction = 'forward'))"
+ " or " + " or "
+ "(not(../label-end/te-label/direction) and" + + "(not(../label-end/te-label/direction) and"
" (te-label/direction = 'forward'))" { + " (te-label/direction = 'forward'))" {
error-message error-message
"label-start and label-end must have the same direction."; "'label-start' and 'label-end' must have the same "
+ "direction.";
} }
description description
"This is the starting label if a label range is specified. "This is the starting label if a label range is specified.
This is the label value if a single label is specified, This is the label value if a single label is specified,
in which case, attribute 'label-end' is not set."; in which case the 'label-end' attribute is not set.";
uses te-label; uses te-label;
} }
container label-end { container label-end {
must "(not(../label-start/te-label/direction) and" + must "(not(../label-start/te-label/direction) and"
" not(te-label/direction))" + " not(te-label/direction))"
+ " or " + " or "
+ "(../label-start/te-label/direction = te-label/direction)" + "(../label-start/te-label/direction = te-label/direction)"
+ " or " + " or "
+ "(not(te-label/direction) and" + + "(not(te-label/direction) and"
" (../label-start/te-label/direction = 'forward'))" + " (../label-start/te-label/direction = 'forward'))"
+ " or " + " or "
+ "(not(../label-start/te-label/direction) and" + + "(not(../label-start/te-label/direction) and"
" (te-label/direction = 'forward'))" { + " (te-label/direction = 'forward'))" {
error-message error-message
"label-start and label-end must have the same direction."; "'label-start' and 'label-end' must have the same "
+ "direction.";
} }
description description
"The ending label if a label range is specified; "This is the ending label if a label range is specified.
This attribute is not set, If a single label is This attribute is not set if a single label is specified.";
specified.";
uses te-label; uses te-label;
} }
container label-step { container label-step {
description description
"The step increment between labels in the label range. "The step increment between labels in the label range.
The label start/end values will have to be consistent The label start/end values will have to be consistent
with the sign of label step. For example, with the sign of label step. For example,
label-start < label-end enforces label-step > 0 'label-start' < 'label-end' enforces 'label-step' > 0
label-start > label-end enforces label-step < 0"; 'label-start' > 'label-end' enforces 'label-step' < 0.";
choice technology { choice technology {
default generic; default "generic";
description description
"Data plane technology type."; "Data-plane technology type.";
case generic { case generic {
leaf generic { leaf generic {
type int32; type int32;
default 1; default "1";
description "Label range step"; description
"Label range step.";
} }
} }
} }
} }
leaf range-bitmap { leaf range-bitmap {
type yang:hex-string; type yang:hex-string;
description description
"When there are gaps between label-start and label-end, "When there are gaps between 'label-start' and 'label-end',
this attribute is used to specify the positions this attribute is used to specify the positions
of the used labels. This is represented in big-endian as of the used labels. This is represented in big endian as
hex-string. 'hex-string'.
The MSB is the farthest to the left in the byte sequence. The most significant byte in the hex-string is the farthest
Leading zero bytes in the configured value may be omitted to the left in the byte sequence. Leading zero bytes in the
for brevity. configured value may be omitted for brevity.
Each bit-position in the range-bitmap hex-string maps to a Each bit position in the 'range-bitmap' 'hex-string' maps
label in the range derived from the label-start. to a label in the range derived from 'label-start'.
For example, assuming label-start=16000 and For example, assuming that 'label-start' = 16000 and
range-bitmap=0x01000001, then: 'range-bitmap' = 0x01000001, then:
- bit-position(0) is set, and the corresponding mapped label
from the range is: 16000 + (0 * label-step) or - bit position (0) is set, and the corresponding mapped
16000 for default label-step=1. label from the range is 16000 + (0 * 'label-step') or
- bit-position(24) is set, and the corresponding mapped label 16000 for default 'label-step' = 1.
from the range is: 16000 + (24 * label-step) or - bit position (24) is set, and the corresponding mapped
16024 for default label-step=1"; label from the range is 16000 + (24 * 'label-step') or
16024 for default 'label-step' = 1.";
} }
} }
grouping label-set-info { grouping label-set-info {
description description
"Grouping for List of label restrictions specifying what labels "Grouping for the list of label restrictions specifying what
may or may not be used on a link connectivity."; labels may or may not be used.";
container label-restrictions { container label-restrictions {
description description
"The label restrictions container"; "The label restrictions container.";
list label-restriction { list label-restriction {
key "index"; key "index";
description description
"The absence of label-set implies that all labels are "The absence of the label restrictions container implies
acceptable; otherwise only restricted labels are that all labels are acceptable; otherwise, only restricted
available."; labels are available.";
reference reference
"RFC7579: General Network Element Constraint Encoding "RFC 7579: General Network Element Constraint Encoding
for GMPLS-Controlled Networks"; for GMPLS-Controlled Networks";
uses label-restriction-info; uses label-restriction-info;
} }
} }
} }
grouping optimization-metric-entry { grouping optimization-metric-entry {
description "Optimization metrics configuration grouping"; description
"Optimization metrics configuration grouping.";
leaf metric-type { leaf metric-type {
type identityref { type identityref {
base path-metric-type; base path-metric-type;
} }
description description
"Identifies an entry in the list of metric-types to "Identifies the 'metric-type' that the path computation
optimize the TE path for."; process uses for optimization.";
} }
leaf weight { leaf weight {
type uint8; type uint8;
default 1; default "1";
description "TE path metric normalization weight"; description
"TE path metric normalization weight.";
} }
container explicit-route-exclude-objects { container explicit-route-exclude-objects {
when "../metric-type = " + when "../metric-type = "
"'te-types:path-metric-optimize-excludes'"; + "'te-types:path-metric-optimize-excludes'";
description description
"Container for the exclude route object list"; "Container for the 'exclude route' object list.";
uses path-route-exclude-objects; uses path-route-exclude-objects;
} }
container explicit-route-include-objects { container explicit-route-include-objects {
when "../metric-type = " + when "../metric-type = "
"'te-types:path-metric-optimize-includes'"; + "'te-types:path-metric-optimize-includes'";
description description
"Container for the include route object list"; "Container for the 'include route' object list.";
uses path-route-include-objects; uses path-route-include-objects;
} }
} }
grouping common-constraints { grouping common-constraints {
description description
"Common constraints grouping that can be set on "Common constraints grouping that can be set on
a constraint set or directly on the tunnel"; a constraint set or directly on the tunnel.";
uses te-bandwidth { uses te-bandwidth {
description description
"A requested bandwidth to use for path computation"; "A requested bandwidth to use for path computation.";
} }
leaf link-protection { leaf link-protection {
type identityref { type identityref {
base link-protection-type; base link-protection-type;
} }
default te-types:link-protection-unprotected; default "te-types:link-protection-unprotected";
description description
"Link protection type required for the links included "Link protection type required for the links included
in the computed path"; in the computed path.";
reference reference
"RFC4202: Routing Extensions in Support of "RFC 4202: Routing Extensions in Support of
Generalized Multi-Protocol Label Switching (GMPLS)."; Generalized Multi-Protocol Label Switching (GMPLS)";
} }
leaf setup-priority { leaf setup-priority {
type uint8 { type uint8 {
range '0..7'; range "0..7";
} }
default 7; default "7";
description description
"TE LSP requested setup priority"; "TE LSP requested setup priority.";
reference "RFC3209"; reference
"RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
} }
leaf hold-priority { leaf hold-priority {
type uint8 { type uint8 {
range '0..7'; range "0..7";
} }
default 7; default "7";
description description
"TE LSP requested hold priority"; "TE LSP requested hold priority.";
reference "RFC3209"; reference
"RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
} }
leaf signaling-type { leaf signaling-type {
type identityref { type identityref {
base path-signaling-type; base path-signaling-type;
} }
default te-types:path-setup-rsvp; default "te-types:path-setup-rsvp";
description "TE tunnel path signaling type"; description
"TE tunnel path signaling type.";
} }
} }
grouping tunnel-constraints { grouping tunnel-constraints {
description description
"Tunnel constraints grouping that can be set on "Tunnel constraints grouping that can be set on
a constraint set or directly on the tunnel"; a constraint set or directly on the tunnel.";
uses te-topology-identifier; uses te-topology-identifier;
uses common-constraints; uses common-constraints;
} }
grouping path-constraints-route-objects { grouping path-constraints-route-objects {
description description
"List of route entries to be included or excluded when performing "List of route entries to be included or excluded when
path computation."; performing the path computation.";
container explicit-route-objects-always { container explicit-route-objects-always {
description description
"Container for the exclude route object list"; "Container for the 'exclude route' object list.";
list route-object-exclude-always { list route-object-exclude-always {
key index; key "index";
ordered-by user; ordered-by user;
description description
"List of route objects to always exclude "List of route objects to always exclude from the path
from path computation"; computation.";
leaf index { leaf index {
type uint32; type uint32;
description description
"Explicit route object index. The index is used to "Explicit Route Object index. The index is used to
identify an entry in the list. The order of entries identify an entry in the list. The order of entries
is defined by the user without relying on key values"; is defined by the user without relying on key values.";
} }
uses explicit-route-hop; uses explicit-route-hop;
} }
list route-object-include-exclude { list route-object-include-exclude {
key index; key "index";
ordered-by user; ordered-by user;
description description
"List of route objects to include or exclude in path "List of route objects to include or exclude in the path
computation"; computation.";
leaf explicit-route-usage { leaf explicit-route-usage {
type identityref { type identityref {
base route-usage-type; base route-usage-type;
} }
default te-types:route-include-object; default "te-types:route-include-object";
description description
"Include or exclude usage. Default is to include"; "Indicates whether to include or exclude the
route object. The default is to include it.";
} }
leaf index { leaf index {
type uint32; type uint32;
description description
"Route object include-exclude index. The index is used to "Route object include-exclude index. The index is used
identify an entry in the list. The order of entries to identify an entry in the list. The order of entries
is defined by the user without relying on key values"; is defined by the user without relying on key values.";
} }
uses explicit-route-hop { uses explicit-route-hop {
augment "type" { augment "type" {
case srlg { case srlg {
container srlg { container srlg {
description "SRLG container"; description
"SRLG container.";
leaf srlg { leaf srlg {
type uint32; type uint32;
description "SRLG value"; description
"SRLG value.";
} }
} }
description "An SRLG value to be included or excluded"; description
"An SRLG value to be included or excluded.";
} }
description description
"Augmentation to generic explicit route for SRLG "Augmentation for a generic explicit route for SRLG
exclusion"; exclusion.";
} }
} }
} }
} }
} }
grouping path-route-include-objects { grouping path-route-include-objects {
description description
"List of route object(s) to be included when performing "List of route objects to be included when performing
the path computation."; the path computation.";
list route-object-include-object { list route-object-include-object {
key index; key "index";
ordered-by user; ordered-by user;
description description
"List of explicit route objects to be included "List of Explicit Route Objects to be included in the
in path computation"; path computation.";
leaf index { leaf index {
type uint32; type uint32;
description description
"Route object entry index. The index is used to "Route object entry index. The index is used to
identify an entry in the list. The order of entries identify an entry in the list. The order of entries
is defined by the user without relying on key values"; is defined by the user without relying on key values.";
} }
uses explicit-route-hop; uses explicit-route-hop;
} }
} }
grouping path-route-exclude-objects { grouping path-route-exclude-objects {
description description
"List of route object(s) to be excluded when performing "List of route objects to be excluded when performing
the path computation."; the path computation.";
list route-object-exclude-object { list route-object-exclude-object {
key index; key "index";
ordered-by user; ordered-by user;
description description
"List of explicit route objects to be excluded "List of Explicit Route Objects to be excluded in the
in path computation"; path computation.";
leaf index { leaf index {
type uint32; type uint32;
description description
"Route object entry index. The index is used to "Route object entry index. The index is used to
identify an entry in the list. The order of entries identify an entry in the list. The order of entries
is defined by the user without relying on key values"; is defined by the user without relying on key values.";
} }
uses explicit-route-hop { uses explicit-route-hop {
augment "type" { augment "type" {
case srlg { case srlg {
container srlg { container srlg {
description "SRLG container"; description
"SRLG container.";
leaf srlg { leaf srlg {
type uint32; type uint32;
description "SRLG value"; description
"SRLG value.";
} }
} }
description "An SRLG value to be included or excluded"; description
"An SRLG value to be included or excluded.";
} }
description description
"Augmentation to generic explicit route for SRLG exclusion"; "Augmentation for a generic explicit route for SRLG
exclusion.";
} }
} }
} }
} }
grouping generic-path-metric-bounds { grouping generic-path-metric-bounds {
description "TE path metric bounds grouping"; description
"TE path metric bounds grouping.";
container path-metric-bounds { container path-metric-bounds {
description "TE path metric bounds container"; description
"TE path metric bounds container.";
list path-metric-bound { list path-metric-bound {
key metric-type; key "metric-type";
description "List of TE path metric bounds"; description
"List of TE path metric bounds.";
leaf metric-type { leaf metric-type {
type identityref { type identityref {
base path-metric-type; base path-metric-type;
} }
description description
"Identifies an entry in the list of metric-types "Identifies an entry in the list of 'metric-type' items
bound for the TE path."; bound for the TE path.";
} }
leaf upper-bound { leaf upper-bound {
type uint64; type uint64;
default 0; default "0";
description description
"Upper bound on end-to-end TE path metric. A zero indicate "Upper bound on the end-to-end TE path metric. A zero
an unbounded upper limit for the specific metric-type"; indicates an unbounded upper limit for the specific
'metric-type'.";
} }
} }
} }
} }
grouping generic-path-optimization { grouping generic-path-optimization {
description "TE generic path optimization grouping"; description
"TE generic path optimization grouping.";
container optimizations { container optimizations {
description description
"The objective function container that includes "The objective function container that includes
attributes to impose when computing a TE path"; attributes to impose when computing a TE path.";
choice algorithm { choice algorithm {
description "Optimizations algorithm."; description
"Optimizations algorithm.";
case metric { case metric {
if-feature path-optimization-metric; if-feature "path-optimization-metric";
/* Optimize by metric */ /* Optimize by metric */
list optimization-metric { list optimization-metric {
key "metric-type"; key "metric-type";
description "TE path metric type"; description
"TE path metric type.";
uses optimization-metric-entry; uses optimization-metric-entry;
} }
/* Tiebreakers */ /* Tiebreakers */
container tiebreakers { container tiebreakers {
description description
"Container for the list of tiebreaker(s)"; "Container for the list of tiebreakers.";
list tiebreaker { list tiebreaker {
key "tiebreaker-type"; key "tiebreaker-type";
description description
"The list of tiebreaker criterion to apply "The list of tiebreaker criteria to apply on an
on an equally favored set of paths to pick best"; equally favored set of paths, in order to pick
the best.";
leaf tiebreaker-type { leaf tiebreaker-type {
type identityref { type identityref {
base path-metric-type; base path-metric-type;
} }
description description
"Identifies an entry in the list of tiebreakers."; "Identifies an entry in the list of tiebreakers.";
} }
} }
} }
} }
case objective-function { case objective-function {
if-feature path-optimization-objective-function; if-feature "path-optimization-objective-function";
/* Objective functions */ /* Objective functions */
container objective-function { container objective-function {
description description
"The objective function container that includes "The objective function container that includes
attributes to impose when computing a TE path"; attributes to impose when computing a TE path.";
leaf objective-function-type { leaf objective-function-type {
type identityref { type identityref {
base objective-function-type; base objective-function-type;
} }
default te-types:of-minimize-cost-path; default "te-types:of-minimize-cost-path";
description "Objective function entry"; description
"Objective function entry.";
} }
} }
} }
} }
} }
} }
grouping generic-path-affinities { grouping generic-path-affinities {
description description
"Path affinities grouping"; "Path affinities grouping.";
container path-affinities-values { container path-affinities-values {
description description
"Path affinities values representation"; "Path affinities represented as values.";
list path-affinities-value { list path-affinities-value {
key "usage"; key "usage";
description description
"List of named affinity constraints"; "List of named affinity constraints.";
leaf usage { leaf usage {
type identityref { type identityref {
base resource-affinities-type; base resource-affinities-type;
} }
description description
"Identifies an entry in the list of value affinities "Identifies an entry in the list of value affinity
constraints"; constraints.";
} }
leaf value { leaf value {
type admin-groups; type admin-groups;
default ''; default "";
description "The affinity value. The default is empty."; description
"The affinity value. The default is empty.";
} }
} }
} }
container path-affinity-names { container path-affinity-names {
description description
"Path affinities named representation style"; "Path affinities represented as names.";
list path-affinity-name { list path-affinity-name {
key "usage"; key "usage";
description "List of named affinity constraints"; description
"List of named affinity constraints.";
leaf usage { leaf usage {
type identityref { type identityref {
base resource-affinities-type; base resource-affinities-type;
} }
description description
"Identifies an entry in the list of named affinities "Identifies an entry in the list of named affinity
constraints"; constraints.";
} }
list affinity-name { list affinity-name {
key "name"; key "name";
leaf name { leaf name {
type string; type string;
description "Identify a named affinity entry."; description
"Identifies a named affinity entry.";
} }
description "List of named affinities"; description
"List of named affinities.";
} }
} }
} }
} }
grouping generic-path-srlgs { grouping generic-path-srlgs {
description description
"Path SRLG grouping"; "Path SRLG grouping.";
container path-srlgs-lists { container path-srlgs-lists {
description description
"Path SRLG properties container"; "Path SRLG properties container.";
list path-srlgs-list { list path-srlgs-list {
key "usage"; key "usage";
description description
"List entries of value SRLGs to be included or excluded"; "List of SRLG values to be included or excluded.";
leaf usage { leaf usage {
type identityref { type identityref {
base route-usage-type; base route-usage-type;
} }
description description
"Identifies an entry of list of SRLGs to either include "Identifies an entry in a list of SRLGs to either
or exclude"; include or exclude.";
} }
leaf-list values { leaf-list values {
type srlg; type srlg;
description "List of SRLG values"; description
"List of SRLG values.";
} }
} }
} }
container path-srlgs-names { container path-srlgs-names {
description "Container for named SRLG list"; description
"Container for the list of named SRLGs.";
list path-srlgs-name { list path-srlgs-name {
key "usage"; key "usage";
description description
"List entries of named SRLGs to be included or excluded"; "List of named SRLGs to be included or excluded.";
leaf usage { leaf usage {
type identityref { type identityref {
base route-usage-type; base route-usage-type;
} }
description description
"Identifies an entry of list of named SRLGs to either "Identifies an entry in a list of named SRLGs to either
include or exclude"; include or exclude.";
} }
leaf-list names { leaf-list names {
type string; type string;
description "List of named SRLGs"; description
"List of named SRLGs.";
} }
} }
} }
} }
grouping generic-path-disjointness { grouping generic-path-disjointness {
description "Path disjointness grouping"; description
"Path disjointness grouping.";
leaf disjointness { leaf disjointness {
type te-path-disjointness; type te-path-disjointness;
description description
"The type of resource disjointness. "The type of resource disjointness.
When configured for a primary path, the disjointness level When configured for a primary path, the disjointness level
applies to all secondary LSPs. When configured for a secondary applies to all secondary LSPs. When configured for a
path, disjointness level overrides the one configured for the secondary path, the disjointness level overrides the level
primary path"; configured for the primary path.";
} }
} }
grouping common-path-constraints-attributes { grouping common-path-constraints-attributes {
description description
"Common path constraints configuration grouping"; "Common path constraints configuration grouping.";
uses common-constraints; uses common-constraints;
uses generic-path-metric-bounds; uses generic-path-metric-bounds;
uses generic-path-affinities; uses generic-path-affinities;
uses generic-path-srlgs; uses generic-path-srlgs;
} }
grouping generic-path-constraints { grouping generic-path-constraints {
description description
"Global named path constraints configuration "Global named path constraints configuration grouping.";
grouping";
container path-constraints { container path-constraints {
description "TE named path constraints container"; description
"TE named path constraints container.";
uses common-path-constraints-attributes; uses common-path-constraints-attributes;
uses generic-path-disjointness; uses generic-path-disjointness;
} }
} }
grouping generic-path-properties { grouping generic-path-properties {
description "TE generic path properties grouping"; description
"TE generic path properties grouping.";
container path-properties { container path-properties {
config false; config false;
description "The TE path properties"; description
"The TE path properties.";
list path-metric { list path-metric {
key metric-type; key "metric-type";
description "TE path metric type"; description
"TE path metric type.";
leaf metric-type { leaf metric-type {
type identityref { type identityref {
base path-metric-type; base path-metric-type;
} }
description "TE path metric type"; description
"TE path metric type.";
} }
leaf accumulative-value { leaf accumulative-value {
type uint64; type uint64;
description "TE path metric accumulative value"; description
"TE path metric accumulative value.";
} }
} }
uses generic-path-affinities; uses generic-path-affinities;
uses generic-path-srlgs; uses generic-path-srlgs;
container path-route-objects { container path-route-objects {
description description
"Container for the list of route objects either returned by "Container for the list of route objects either returned by
the computation engine or actually used by an LSP"; the computation engine or actually used by an LSP.";
list path-route-object { list path-route-object {
key index; key "index";
ordered-by user; ordered-by user;
description description
"List of route objects either returned by the computation "List of route objects either returned by the computation
engine or actually used by an LSP"; engine or actually used by an LSP.";
leaf index { leaf index {
type uint32; type uint32;
description description
"Route object entry index. The index is used to "Route object entry index. The index is used to
identify an entry in the list. The order of entries identify an entry in the list. The order of entries
is defined by the user without relying on key values"; is defined by the user without relying on key
values.";
} }
uses explicit-route-hop; uses explicit-route-hop;
} }
} }
} }
} }
} }
<CODE ENDS> ]]></sourcecode>
]]></artwork></figure> </section>
<section anchor="packet-te-types-yang-module" numbered="true" toc="default">
</section> <name>Packet TE Types YANG Module</name>
<section anchor="packet-te-types-yang-module" title="Packet TE Types YANG Module <t>The "ietf-te-packet-types" module imports from the "ietf-te-types"
"> module defined in <xref target="te-types-yang-module"/> of this
document.</t>
<t>The ietf-te-packet-types module imports from the following modules:</t>
<t><list style="symbols">
<t>ietf-te-types defined in this document.</t>
</list></t>
<figure title="TE packet types YANG module" anchor="fig-mpls-te-types"><artwork> <sourcecode name="ietf-te-packet-types@2020-04-06.yang" type="yang" mark
<![CDATA[ ers="true"><![CDATA[
<CODE BEGINS> file "ietf-te-packet-types@2019-11-18.yang"
module ietf-te-packet-types { module ietf-te-packet-types {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-te-packet-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-te-packet-types";
prefix te-packet-types;
/* Replace with IANA when assigned */
prefix "te-packet-types";
/* Import TE generic types */ /* Import TE generic types */
import ietf-te-types { import ietf-te-types {
prefix te-types; prefix te-types;
reference reference
"RFC XXXX: A YANG Data Model for Common Traffic Engineering "RFC 8776: Common YANG Data Types for Traffic Engineering";
Types";
} }
organization organization
"IETF TEAS Working Group"; "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <https://datatracker.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
Editor: Tarek Saad Editor: Tarek Saad
<mailto:tsaad@juniper.net> <mailto:tsaad@juniper.net>
Editor: Rakesh Gandhi Editor: Rakesh Gandhi
<mailto:rgandhi@cisco.com> <mailto:rgandhi@cisco.com>
Editor: Vishnu Pavan Beeram Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net> <mailto:vbeeram@juniper.net>
Editor: Himanshu Shah
<mailto:hshah@ciena.com>
Editor: Xufeng Liu Editor: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com> <mailto:xufeng.liu.ietf@gmail.com>
Editor: Igor Bryskin Editor: Igor Bryskin
<mailto:i_bryskin@yahoo.com> <mailto:i_bryskin@yahoo.com>";
Editor: Young Lee
<mailto:leeyoung@huawei.com>";
description description
"This module contains a collection of generally useful MPLS TE "This YANG module contains a collection of generally useful YANG
specific YANG data type definitions. The model fully conforms data type definitions specific to MPLS TE. The model fully
to the Network Management Datastore Architecture (NMDA). conforms to the Network Management Datastore Architecture
(NMDA).
Copyright (c) 2018 IETF Trust and the persons Copyright (c) 2020 IETF Trust and the persons identified as
identified as authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject to
to the license terms contained in, the Simplified BSD License the license terms contained in, the Simplified BSD License set
set forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this
// note.
// RFC Ed.: update the date below with the date of RFC publication This version of this YANG module is part of RFC 8776; see the
// and remove this note. RFC itself for full legal notices.";
revision "2019-11-18" { revision 2020-04-06 {
description "Latest revision of TE MPLS types"; description
"Latest revision of TE MPLS types.";
reference reference
"RFC XXXX: A YANG Data Model for Common Traffic Engineering "RFC 8776: Common YANG Data Types for Traffic Engineering";
Types";
} }
/** /**
* Typedefs * Typedefs
*/ */
typedef te-bandwidth-requested-type { typedef te-bandwidth-requested-type {
type enumeration { type enumeration {
enum specified { enum specified {
description description
"Bandwidth is explicitly specified"; "Bandwidth is explicitly specified.";
} }
enum auto { enum auto {
description description
"Bandwidth is automatically computed"; "Bandwidth is automatically computed.";
} }
} }
description description
"enumerated type for specifying whether bandwidth is "Enumerated type for specifying whether bandwidth is
explicitly specified or automatically computed"; explicitly specified or automatically computed.";
} }
typedef te-class-type { typedef te-class-type {
type uint8; type uint8;
description description
"Diffserv-TE class-type that defines a set of Traffic "Diffserv-TE Class-Type. Defines a set of Traffic Trunks
Trunks crossing a link that is governed by a specific crossing a link that is governed by a specific set of
set of bandwidth constraints. CT is used for the bandwidth constraints. Class-Type is used for the purposes
purposes of link bandwidth allocation, constraint- of link bandwidth allocation, constraint-based routing, and
based routing and admission control."; admission control.";
reference "RFC4124: Protocols for Diffserv-aware TE"; reference
"RFC 4124: Protocol Extensions for Support of Diffserv-aware
MPLS Traffic Engineering";
} }
typedef bc-type { typedef bc-type {
type uint8 { type uint8 {
range '0..7'; range "0..7";
} }
description description
"Diffserv-TE bandwidth constraint as defined in RFC4124"; "Diffserv-TE bandwidth constraints as defined in RFC 4124.";
reference "RFC4124: Protocols for Diffserv-aware TE"; reference
"RFC 4124: Protocol Extensions for Support of Diffserv-aware
MPLS Traffic Engineering";
} }
typedef bandwidth-kbps { typedef bandwidth-kbps {
type uint64; type uint64;
units "Kbps"; units "Kbps";
description description
"Bandwidth values expressed in kilobits per second"; "Bandwidth values, expressed in kilobits per second.";
} }
typedef bandwidth-mbps { typedef bandwidth-mbps {
type uint64; type uint64;
units "Mbps"; units "Mbps";
description description
"Bandwidth values expressed in megabits per second"; "Bandwidth values, expressed in megabits per second.";
} }
typedef bandwidth-gbps { typedef bandwidth-gbps {
type uint64; type uint64;
units "Gbps"; units "Gbps";
description description
"Bandwidth values expressed in gigabits per second"; "Bandwidth values, expressed in gigabits per second.";
} }
identity backup-protection-type { identity backup-protection-type {
description description
"Base identity for backup protection type"; "Base identity for the backup protection type.";
} }
identity backup-protection-link { identity backup-protection-link {
base backup-protection-type; base backup-protection-type;
description description
"backup provides link protection only"; "Backup provides link protection only.";
} }
identity backup-protection-node-link { identity backup-protection-node-link {
base backup-protection-type; base backup-protection-type;
description description
"backup offers node (preferred) or link protection"; "Backup offers node (preferred) or link protection.";
} }
identity bc-model-type { identity bc-model-type {
description description
"Base identity for Diffserv-TE bandwidth constraint "Base identity for the Diffserv-TE Bandwidth Constraints
model type"; Model type.";
reference "RFC4124: Protocols for Diffserv-aware TE"; reference
"RFC 4124: Protocol Extensions for Support of Diffserv-aware
MPLS Traffic Engineering";
} }
identity bc-model-rdm { identity bc-model-rdm {
base bc-model-type; base bc-model-type;
description description
"Russian Doll bandwidth constraint model type."; "Russian Dolls Bandwidth Constraints Model type.";
reference "RFC4127: Russian Dolls Model for DS-TE"; reference
"RFC 4127: Russian Dolls Bandwidth Constraints Model for
Diffserv-aware MPLS Traffic Engineering";
} }
identity bc-model-mam { identity bc-model-mam {
base bc-model-type; base bc-model-type;
description description
"Maximum Allocation bandwidth constraint "Maximum Allocation Bandwidth Constraints Model type.";
model type."; reference
reference "RFC4125: Maximum Allocation Model for DS-TE"; "RFC 4125: Maximum Allocation Bandwidth Constraints Model for
Diffserv-aware MPLS Traffic Engineering";
} }
identity bc-model-mar { identity bc-model-mar {
base bc-model-type; base bc-model-type;
description description
"Maximum Allocation with Reservation "Maximum Allocation with Reservation Bandwidth Constraints
bandwidth constraint model type."; Model type.";
reference "RFC4126: MAR Bandwidth Constraints Model for DS-TE"; reference
"RFC 4126: Max Allocation with Reservation Bandwidth
Constraints Model for Diffserv-aware MPLS Traffic Engineering
& Performance Comparisons";
} }
grouping performance-metrics-attributes-packet { grouping performance-metrics-attributes-packet {
description description
"A container containing performance metric attributes."; "Contains PM attributes.";
uses te-types:performance-metrics-attributes { uses te-types:performance-metrics-attributes {
augment performance-metrics-one-way { augment "performance-metrics-one-way" {
leaf one-way-min-delay { leaf one-way-min-delay {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
description description
"One-way minimum delay or latency in micro seconds."; "One-way minimum delay or latency in microseconds.";
} }
leaf one-way-min-delay-normality { leaf one-way-min-delay-normality {
type te-types:performance-metrics-normality; type te-types:performance-metrics-normality;
default "normal"; default "normal";
description "One-way minimum delay or latency normality."; description
"One-way minimum delay or latency normality.";
} }
leaf one-way-max-delay { leaf one-way-max-delay {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
description description
"One-way maximum delay or latency in micro seconds."; "One-way maximum delay or latency in microseconds.";
} }
leaf one-way-max-delay-normality { leaf one-way-max-delay-normality {
type te-types:performance-metrics-normality; type te-types:performance-metrics-normality;
default "normal"; default "normal";
description "One-way maximum delay or latency normality."; description
"One-way maximum delay or latency normality.";
} }
leaf one-way-delay-variation { leaf one-way-delay-variation {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
description "One-way delay variation in micro seconds."; description
reference "RFC5481, section 4.2"; "One-way delay variation in microseconds.";
reference
"RFC 5481: Packet Delay Variation Applicability
Statement, Section 4.2";
} }
leaf one-way-delay-variation-normality { leaf one-way-delay-variation-normality {
type te-types:performance-metrics-normality; type te-types:performance-metrics-normality;
default "normal"; default "normal";
description "One-way delay variation normality."; description
reference "RFC7471, RFC8570, and RFC7823"; "One-way delay variation normality.";
reference
"RFC 7471: OSPF Traffic Engineering (TE) Metric
Extensions
RFC 7823: Performance-Based Path Selection for
Explicitly Routed Label Switched Paths (LSPs) Using
TE Metric Extensions
RFC 8570: IS-IS Traffic Engineering (TE) Metric
Extensions";
} }
leaf one-way-packet-loss { leaf one-way-packet-loss {
type decimal64 { type decimal64 {
fraction-digits 6; fraction-digits 6;
range '0 .. 50.331642'; range "0..50.331642";
} }
description description
"One-way packet loss as a percentage of the total traffic "One-way packet loss as a percentage of the total traffic
sent over a configurable interval. The finest precision is sent over a configurable interval. The finest precision
0.000003%. where the maximum 50.331642%."; is 0.000003%, where the maximum is 50.331642%.";
reference "RFC 7810, section-4.4"; reference
"RFC 8570: IS-IS Traffic Engineering (TE) Metric
Extensions, Section 4.4";
} }
leaf one-way-packet-loss-normality { leaf one-way-packet-loss-normality {
type te-types:performance-metrics-normality; type te-types:performance-metrics-normality;
default "normal"; default "normal";
description "Packet loss normality."; description
reference "RFC7471, RFC8570, and RFC7823"; "Packet loss normality.";
reference
"RFC 7471: OSPF Traffic Engineering (TE) Metric
Extensions
RFC 7823: Performance-Based Path Selection for
Explicitly Routed Label Switched Paths (LSPs) Using
TE Metric Extensions
RFC 8570: IS-IS Traffic Engineering (TE) Metric
Extensions";
} }
description description
"PM one-way packet specific augmentation to generic PM "PM one-way packet-specific augmentation for a generic PM
grouping"; grouping.";
} }
augment performance-metrics-two-way { augment "performance-metrics-two-way" {
leaf two-way-min-delay { leaf two-way-min-delay {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
default 0; default "0";
description description
"Two-way minimum delay or latency in micro seconds."; "Two-way minimum delay or latency in microseconds.";
} }
leaf two-way-min-delay-normality { leaf two-way-min-delay-normality {
type te-types:performance-metrics-normality; type te-types:performance-metrics-normality;
default "normal"; default "normal";
description "Two-way minimum delay or latency normality."; description
reference "RFC7471, RFC8570, and RFC7823"; "Two-way minimum delay or latency normality.";
reference
"RFC 7471: OSPF Traffic Engineering (TE) Metric
Extensions
RFC 7823: Performance-Based Path Selection for
Explicitly Routed Label Switched Paths (LSPs) Using
TE Metric Extensions
RFC 8570: IS-IS Traffic Engineering (TE) Metric
Extensions";
} }
leaf two-way-max-delay { leaf two-way-max-delay {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
default 0; default "0";
description description
"Two-way maximum delay or latency in micro seconds."; "Two-way maximum delay or latency in microseconds.";
} }
leaf two-way-max-delay-normality { leaf two-way-max-delay-normality {
type te-types:performance-metrics-normality; type te-types:performance-metrics-normality;
default "normal"; default "normal";
description "Two-way maximum delay or latency normality."; description
reference "RFC7471, RFC8570, and RFC7823"; "Two-way maximum delay or latency normality.";
reference
"RFC 7471: OSPF Traffic Engineering (TE) Metric
Extensions
RFC 7823: Performance-Based Path Selection for
Explicitly Routed Label Switched Paths (LSPs) Using
TE Metric Extensions
RFC 8570: IS-IS Traffic Engineering (TE) Metric
Extensions";
} }
leaf two-way-delay-variation { leaf two-way-delay-variation {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
default 0; default "0";
description "Two-way delay variation in micro seconds."; description
reference "RFC5481, section 4.2"; "Two-way delay variation in microseconds.";
reference
"RFC 5481: Packet Delay Variation Applicability
Statement, Section 4.2";
} }
leaf two-way-delay-variation-normality { leaf two-way-delay-variation-normality {
type te-types:performance-metrics-normality; type te-types:performance-metrics-normality;
default "normal"; default "normal";
description "Two-way delay variation normality."; description
reference "RFC7471, RFC8570, and RFC7823"; "Two-way delay variation normality.";
reference
"RFC 7471: OSPF Traffic Engineering (TE) Metric
Extensions
RFC 7823: Performance-Based Path Selection for
Explicitly Routed Label Switched Paths (LSPs) Using
TE Metric Extensions
RFC 8570: IS-IS Traffic Engineering (TE) Metric
Extensions";
} }
leaf two-way-packet-loss { leaf two-way-packet-loss {
type decimal64 { type decimal64 {
fraction-digits 6; fraction-digits 6;
range '0 .. 50.331642'; range "0..50.331642";
} }
default 0; default "0";
description description
"Two-way packet loss as a percentage of the total traffic "Two-way packet loss as a percentage of the total traffic
sent over a configurable interval. The finest precision is sent over a configurable interval. The finest precision
0.000003%."; is 0.000003%.";
} }
leaf two-way-packet-loss-normality { leaf two-way-packet-loss-normality {
type te-types:performance-metrics-normality; type te-types:performance-metrics-normality;
default "normal"; default "normal";
description "Two-way packet loss normality."; description
"Two-way packet loss normality.";
} }
description description
"PM two-way packet specific augmentation to generic PM "PM two-way packet-specific augmentation for a generic PM
grouping"; grouping.";
reference "RFC7471, RFC8570, and RFC7823"; reference
"RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions
RFC 7823: Performance-Based Path Selection for
Explicitly Routed Label Switched Paths (LSPs) Using
TE Metric Extensions
RFC 8570: IS-IS Traffic Engineering (TE) Metric
Extensions";
} }
} }
} }
grouping one-way-performance-metrics-packet { grouping one-way-performance-metrics-packet {
description description
"One-way packet performance metrics throttle grouping."; "One-way packet PM throttle grouping.";
leaf one-way-min-delay { leaf one-way-min-delay {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
default 0; default "0";
description "One-way minimum delay or latency in micro seconds."; description
"One-way minimum delay or latency in microseconds.";
} }
leaf one-way-max-delay { leaf one-way-max-delay {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
default 0; default "0";
description "One-way maximum delay or latency in micro seconds."; description
"One-way maximum delay or latency in microseconds.";
} }
leaf one-way-delay-variation { leaf one-way-delay-variation {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
default 0; default "0";
description "One-way delay variation in micro seconds."; description
"One-way delay variation in microseconds.";
} }
leaf one-way-packet-loss { leaf one-way-packet-loss {
type decimal64 { type decimal64 {
fraction-digits 6; fraction-digits 6;
range '0 .. 50.331642'; range "0..50.331642";
} }
default 0; default "0";
description description
"One-way packet loss as a percentage of the total traffic sent "One-way packet loss as a percentage of the total traffic
over a configurable interval. The finest precision is sent over a configurable interval. The finest precision is
0.000003%."; 0.000003%.";
} }
} }
grouping two-way-performance-metrics-packet { grouping two-way-performance-metrics-packet {
description description
"Two-way packet performance metrics throttle grouping."; "Two-way packet PM throttle grouping.";
leaf two-way-min-delay { leaf two-way-min-delay {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
default 0; default "0";
description "Two-way minimum delay or latency in micro seconds."; description
"Two-way minimum delay or latency in microseconds.";
} }
leaf two-way-max-delay { leaf two-way-max-delay {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
default 0; default "0";
description "Two-way maximum delay or latency in micro seconds."; description
"Two-way maximum delay or latency in microseconds.";
} }
leaf two-way-delay-variation { leaf two-way-delay-variation {
type uint32 { type uint32 {
range '0..16777215'; range "0..16777215";
} }
default 0; default "0";
description "Two-way delay variation in micro seconds."; description
"Two-way delay variation in microseconds.";
} }
leaf two-way-packet-loss { leaf two-way-packet-loss {
type decimal64 { type decimal64 {
fraction-digits 6; fraction-digits 6;
range '0 .. 50.331642'; range "0..50.331642";
} }
default 0; default "0";
description description
"Two-way packet loss as a percentage of the total traffic sent "Two-way packet loss as a percentage of the total traffic
over a configurable interval. The finest precision is sent over a configurable interval. The finest precision is
0.000003%."; 0.000003%.";
} }
} }
grouping performance-metrics-throttle-container-packet { grouping performance-metrics-throttle-container-packet {
description description
"Packet performance metrics threshold grouping"; "Packet PM threshold grouping.";
uses te-types:performance-metrics-throttle-container { uses te-types:performance-metrics-throttle-container {
augment "throttle/threshold-out" { augment "throttle/threshold-out" {
uses one-way-performance-metrics-packet; uses one-way-performance-metrics-packet;
uses two-way-performance-metrics-packet; uses two-way-performance-metrics-packet;
description description
"PM threshold-out packet augmentation to "PM threshold-out packet augmentation for a
generic grouping"; generic grouping.";
} }
augment "throttle/threshold-in" { augment "throttle/threshold-in" {
uses one-way-performance-metrics-packet; uses one-way-performance-metrics-packet;
uses two-way-performance-metrics-packet; uses two-way-performance-metrics-packet;
description description
"PM threshold-in packet augmentation to "PM threshold-in packet augmentation for a
generic grouping"; generic grouping.";
} }
augment "throttle/threshold-accelerated-advertisement" { augment "throttle/threshold-accelerated-advertisement" {
uses one-way-performance-metrics-packet; uses one-way-performance-metrics-packet;
uses two-way-performance-metrics-packet; uses two-way-performance-metrics-packet;
description description
"PM accelerated advertisement packet augmentation to "PM accelerated advertisement packet augmentation for a
generic grouping"; generic grouping.";
} }
} }
} }
} }
<CODE ENDS> ]]></sourcecode>
]]></artwork></figure> </section>
<section anchor="iana-considerations" numbered="true" toc="default">
</section> <name>IANA Considerations</name>
<section anchor="iana-considerations" title="IANA Considerations"> <t>This document registers the following URIs in the "ns" subregistry
within the "IETF XML Registry" <xref target="RFC3688"
<t>This document registers the following URIs in the IETF XML registry format="default"/>.</t>
<xref target="RFC3688"/>.
Following the format in <xref target="RFC3688"/>, the following registration is
requested to be made.</t>
<figure><artwork><![CDATA[
URI: urn:ietf:params:xml:ns:yang:ietf-te-types
XML: N/A, the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-te-packet-types
XML: N/A, the requested URI is an XML namespace.
]]></artwork></figure>
<t>This document registers two YANG modules in the YANG Module Names <ul empty="true"><li>
registry <xref target="RFC6020"/>.</t> <dl newline="false" spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-te-types</dd>
<dt>Registrant Contact:</dt><dd>The IESG.</dd>
<dt>XML:</dt><dd>N/A; the requested URI is an XML namespace.</dd>
</dl></li></ul>
<figure><artwork><![CDATA[ <ul empty="true"><li>
name: ietf-te-types <dl newline="false" spacing="compact">
namespace: urn:ietf:params:xml:ns:yang:ietf-te-types <dt>URI:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-te-packet-types</dd>
prefix: te-types <dt>Registrant Contact:</dt><dd>The IESG.</dd>
reference: RFCXXXX <dt>XML:</dt><dd>N/A; the requested URI is an XML namespace.</dd>
</dl></li></ul>
name: ietf-te-packet-types <t>This document registers two YANG modules in the "YANG Module Names"
namespace: urn:ietf:params:xml:ns:yang:ietf-te-packet-types registry <xref target="RFC6020" format="default"/>.</t>
prefix: te-packet-types
reference: RFCXXXX
]]></artwork></figure>
</section> <ul empty="true"><li>
<section anchor="security-considerations" title="Security Considerations"> <dl newline="false" spacing="compact">
<dt>Name:</dt><dd>ietf-te-types</dd>
<dt>Namespace:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-te-types</dd>
<dt>Prefix:</dt><dd>te-types</dd>
<dt>Reference:</dt><dd>RFC 8776</dd>
</dl></li></ul>
<t>The YANG module specified in this document defines a schema for data that is <ul empty="true"><li>
<dl newline="false" spacing="compact">
<dt>Name:</dt><dd>ietf-te-packet-types</dd>
<dt>Namespace:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-te-packet-types</dd>
<dt>Prefix:</dt><dd>te-packet-types</dd>
<dt>Reference:</dt><dd>RFC 8776</dd>
</dl></li></ul>
</section>
<section anchor="security-considerations" numbered="true" toc="default">
<name>Security Considerations</name>
<t>The YANG module specified in this document defines a schema for data th
at is
designed to be accessed via network management protocols such as NETCONF designed to be accessed via network management protocols such as NETCONF
<xref target="RFC6241"/> or RESTCONF <xref target="RFC8040"/>. The lowest NETCON F layer is the secure <xref target="RFC6241" format="default"/> or RESTCONF <xref target="RFC8040" for mat="default"/>. The lowest NETCONF layer is the secure
transport layer, and the mandatory-to-implement secure transport is Secure transport layer, and the mandatory-to-implement secure transport is Secure
Shell (SSH) <xref target="RFC6242"/>. The lowest RESTCONF layer is HTTPS, and t Shell (SSH) <xref target="RFC6242" format="default"/>. The lowest RESTCONF laye
he r is HTTPS, and the
mandatory-to-implement secure transport is TLS <xref target="RFC8446"/>.</t> mandatory-to-implement secure transport is TLS <xref target="RFC8446" format="de
fault"/>.</t>
<t>The Network Configuration Access Control Model (NACM) <xref target="RFC8341"/ <t>The Network Configuration Access Control Model (NACM) <xref target="RFC
> provides the 8341" format="default"/> provides the
means to restrict access for particular NETCONF or RESTCONF users to a means to restrict access for particular NETCONF or RESTCONF users to a
preconfigured subset of all available NETCONF or RESTCONF protocol operations preconfigured subset of all available NETCONF or RESTCONF protocol operations
and content.</t> and content.</t>
<t>The YANG module in this document defines common TE type definitions
<t>The YANG module in this document defines common TE type definitions (e.g., typedef, identity, and grouping statements) in YANG data modeling
(i.e., typedef, identity and grouping statements) in YANG data modeling
language to be imported and used by other TE modules. When imported language to be imported and used by other TE modules. When imported
and used, the resultant schema will have data nodes that can be writable, or and used, the resultant schema will have data nodes that can be writable or
readable. The access to such data nodes may be considered sensitive or readable. Access to such data nodes may be considered sensitive or
vulnerable in some network environments. Write operations (e.g., edit-config) vulnerable in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative effect on to these data nodes without proper protection can have a negative effect on
network operations.</t> network operations.</t>
<t>The security considerations spelled out in the YANG 1.1 specification
<xref target="RFC7950" format="default"/> apply for this document as well.</t>
<t>The security considerations spelled out in the YANG 1.1 specification </section>
<xref target="RFC7950"/> apply for this document as well.</t>
</section>
<section anchor="acknowledgement" title="Acknowledgement">
<t>The authors would like to thank the members of the multi-vendor YANG design
team
who are involved in the definition of these data types.</t>
<t>The authors would also like to thank Tom Petch, Jan Lindblad, Sergio Belotti,
Italo Busi,
Carlo Perocchio, Francesco Lazzeri, and Aihua Guo for their review
comments and for providing valuable feedback on this document.</t>
</section>
<section anchor="contributors" title="Contributors">
<figure><artwork><![CDATA[
Himanshu Shah
Ciena
Email: hshah@ciena.com
Young Lee
Huawei Technologies
Email: leeyoung@huawei.com
]]></artwork></figure>
</section>
</middle> </middle>
<back> <back>
<references>
<name>References</name>
<references>
<name>Normative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6020.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6241.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8294.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6991.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7950.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8345.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3688.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8040.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6242.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8446.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8341.
xml"/>
</references>
<references>
<name>Informative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3209.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7308.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6511.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5541.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3272.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4657.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5817.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4328.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6004.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7139.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7551.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7571.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7579.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3471.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3477.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3785.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4124.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4202.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7471.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8570.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7823.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6370.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5003.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3630.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6827.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5305.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6119.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4203.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5307.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6378.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4427.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4090.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4561.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4736.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5712.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4920.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5420.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7570.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4875.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5151.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5150.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6001.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6790.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7260.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8001.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8149.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8169.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6780.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4872.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4873.
xml"/>
<references title='Normative References'> <reference anchor="G.709" target="https://www.itu.int/rec/T-REC-G.709/">
<front>
<reference anchor="RFC2119" target='https://www.rfc-editor.org/info/rfc2119'> <title>Interfaces for the optical transport network</title>
<front> <seriesInfo name="ITU-T" value="Recommendation G.709"/>
<title>Key words for use in RFCs to Indicate Requirement Levels</title> <author>
<author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></ <organization>ITU-T</organization>
author> </author>
<date year='1997' month='March' /> <date month="June" year="2016"/>
<abstract><t>In many standards track documents several words are used to signify </front>
the requirements in the specification. These words are often capitalized. This </reference>
document defines these words as they should be interpreted in IETF documents.
This document specifies an Internet Best Current Practices for the Internet Comm
unity, and requests discussion and suggestions for improvements.</t></abstract>
</front>
<seriesInfo name='BCP' value='14'/>
<seriesInfo name='RFC' value='2119'/>
<seriesInfo name='DOI' value='10.17487/RFC2119'/>
</reference>
<reference anchor="RFC8174" target='https://www.rfc-editor.org/info/rfc8174'>
<front>
<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
<author initials='B.' surname='Leiba' fullname='B. Leiba'><organization /></auth
or>
<date year='2017' month='May' />
<abstract><t>RFC 2119 specifies common key words that may be used in protocol s
pecifications. This document aims to reduce the ambiguity by clarifying that on
ly UPPERCASE usage of the key words have the defined special meanings.</t></abs
tract>
</front>
<seriesInfo name='BCP' value='14'/>
<seriesInfo name='RFC' value='8174'/>
<seriesInfo name='DOI' value='10.17487/RFC8174'/>
</reference>
<reference anchor="RFC6020" target='https://www.rfc-editor.org/info/rfc6020'>
<front>
<title>YANG - A Data Modeling Language for the Network Configuration Protocol (N
ETCONF)</title>
<author initials='M.' surname='Bjorklund' fullname='M. Bjorklund' role='editor'>
<organization /></author>
<date year='2010' month='October' />
<abstract><t>YANG is a data modeling language used to model configuration and st
ate data manipulated by the Network Configuration Protocol (NETCONF), NETCONF re
mote procedure calls, and NETCONF notifications. [STANDARDS-TRACK]</t></abstract
>
</front>
<seriesInfo name='RFC' value='6020'/>
<seriesInfo name='DOI' value='10.17487/RFC6020'/>
</reference>
<reference anchor="RFC6241" target='https://www.rfc-editor.org/info/rfc6241'>
<front>
<title>Network Configuration Protocol (NETCONF)</title>
<author initials='R.' surname='Enns' fullname='R. Enns' role='editor'><organizat
ion /></author>
<author initials='M.' surname='Bjorklund' fullname='M. Bjorklund' role='editor'>
<organization /></author>
<author initials='J.' surname='Schoenwaelder' fullname='J. Schoenwaelder' role='
editor'><organization /></author>
<author initials='A.' surname='Bierman' fullname='A. Bierman' role='editor'><org
anization /></author>
<date year='2011' month='June' />
<abstract><t>The Network Configuration Protocol (NETCONF) defined in this docume
nt provides mechanisms to install, manipulate, and delete the configuration of n
etwork devices. It uses an Extensible Markup Language (XML)-based data encoding
for the configuration data as well as the protocol messages. The NETCONF proto
col operations are realized as remote procedure calls (RPCs). This document obs
oletes RFC 4741. [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='6241'/>
<seriesInfo name='DOI' value='10.17487/RFC6241'/>
</reference>
<reference anchor="RFC8294" target='https://www.rfc-editor.org/info/rfc8294'>
<front>
<title>Common YANG Data Types for the Routing Area</title>
<author initials='X.' surname='Liu' fullname='X. Liu'><organization /></author>
<author initials='Y.' surname='Qu' fullname='Y. Qu'><organization /></author>
<author initials='A.' surname='Lindem' fullname='A. Lindem'><organization /></au
thor>
<author initials='C.' surname='Hopps' fullname='C. Hopps'><organization /></auth
or>
<author initials='L.' surname='Berger' fullname='L. Berger'><organization /></au
thor>
<date year='2017' month='December' />
<abstract><t>This document defines a collection of common data types using the Y
ANG data modeling language. These derived common types are designed to be impor
ted by other modules defined in the routing area.</t></abstract>
</front>
<seriesInfo name='RFC' value='8294'/>
<seriesInfo name='DOI' value='10.17487/RFC8294'/>
</reference>
<reference anchor="RFC6991" target='https://www.rfc-editor.org/info/rfc6991'>
<front>
<title>Common YANG Data Types</title>
<author initials='J.' surname='Schoenwaelder' fullname='J. Schoenwaelder' role='
editor'><organization /></author>
<date year='2013' month='July' />
<abstract><t>This document introduces a collection of common data types to be us
ed with the YANG data modeling language. This document obsoletes RFC 6021.</t><
/abstract>
</front>
<seriesInfo name='RFC' value='6991'/>
<seriesInfo name='DOI' value='10.17487/RFC6991'/>
</reference>
<reference anchor="RFC7951" target='https://www.rfc-editor.org/info/rfc7951'>
<front>
<title>JSON Encoding of Data Modeled with YANG</title>
<author initials='L.' surname='Lhotka' fullname='L. Lhotka'><organization /></au
thor>
<date year='2016' month='August' />
<abstract><t>This document defines encoding rules for representing configuration
data, state data, parameters of Remote Procedure Call (RPC) operations or actio
ns, and notifications defined using YANG as JavaScript Object Notation (JSON) te
xt.</t></abstract>
</front>
<seriesInfo name='RFC' value='7951'/>
<seriesInfo name='DOI' value='10.17487/RFC7951'/>
</reference>
<reference anchor="RFC7950" target='https://www.rfc-editor.org/info/rfc7950'>
<front>
<title>The YANG 1.1 Data Modeling Language</title>
<author initials='M.' surname='Bjorklund' fullname='M. Bjorklund' role='editor'>
<organization /></author>
<date year='2016' month='August' />
<abstract><t>YANG is a data modeling language used to model configuration data,
state data, Remote Procedure Calls, and notifications for network management pro
tocols. This document describes the syntax and semantics of version 1.1 of the
YANG language. YANG version 1.1 is a maintenance release of the YANG language,
addressing ambiguities and defects in the original specification. There are a s
mall number of backward incompatibilities from YANG version 1. This document al
so specifies the YANG mappings to the Network Configuration Protocol (NETCONF).<
/t></abstract>
</front>
<seriesInfo name='RFC' value='7950'/>
<seriesInfo name='DOI' value='10.17487/RFC7950'/>
</reference>
<reference anchor="RFC8345" target='https://www.rfc-editor.org/info/rfc8345'>
<front>
<title>A YANG Data Model for Network Topologies</title>
<author initials='A.' surname='Clemm' fullname='A. Clemm'><organization /></auth
or>
<author initials='J.' surname='Medved' fullname='J. Medved'><organization /></au
thor>
<author initials='R.' surname='Varga' fullname='R. Varga'><organization /></auth
or>
<author initials='N.' surname='Bahadur' fullname='N. Bahadur'><organization /></
author>
<author initials='H.' surname='Ananthakrishnan' fullname='H. Ananthakrishnan'><o
rganization /></author>
<author initials='X.' surname='Liu' fullname='X. Liu'><organization /></author>
<date year='2018' month='March' />
<abstract><t>This document defines an abstract (generic, or base) YANG data mode
l for network/service topologies and inventories. The data model serves as a ba
se model that is augmented with technology-specific details in other, more speci
fic topology and inventory data models.</t></abstract>
</front>
<seriesInfo name='RFC' value='8345'/>
<seriesInfo name='DOI' value='10.17487/RFC8345'/>
</reference>
<reference anchor="RFC3688" target='https://www.rfc-editor.org/info/rfc3688'>
<front>
<title>The IETF XML Registry</title>
<author initials='M.' surname='Mealling' fullname='M. Mealling'><organization />
</author>
<date year='2004' month='January' />
<abstract><t>This document describes an IANA maintained registry for IETF standa
rds which use Extensible Markup Language (XML) related items such as Namespaces,
Document Type Declarations (DTDs), Schemas, and Resource Description Framework
(RDF) Schemas.</t></abstract>
</front>
<seriesInfo name='BCP' value='81'/>
<seriesInfo name='RFC' value='3688'/>
<seriesInfo name='DOI' value='10.17487/RFC3688'/>
</reference>
<reference anchor="RFC8040" target='https://www.rfc-editor.org/info/rfc8040'>
<front>
<title>RESTCONF Protocol</title>
<author initials='A.' surname='Bierman' fullname='A. Bierman'><organization /></
author>
<author initials='M.' surname='Bjorklund' fullname='M. Bjorklund'><organization
/></author>
<author initials='K.' surname='Watsen' fullname='K. Watsen'><organization /></au
thor>
<date year='2017' month='January' />
<abstract><t>This document describes an HTTP-based protocol that provides a prog
rammatic interface for accessing data defined in YANG, using the datastore conce
pts defined in the Network Configuration Protocol (NETCONF).</t></abstract>
</front>
<seriesInfo name='RFC' value='8040'/>
<seriesInfo name='DOI' value='10.17487/RFC8040'/>
</reference>
<reference anchor="RFC6242" target='https://www.rfc-editor.org/info/rfc6242'>
<front>
<title>Using the NETCONF Protocol over Secure Shell (SSH)</title>
<author initials='M.' surname='Wasserman' fullname='M. Wasserman'><organization
/></author>
<date year='2011' month='June' />
<abstract><t>This document describes a method for invoking and running the Netwo
rk Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SS
H subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK]</t></abstract
>
</front>
<seriesInfo name='RFC' value='6242'/>
<seriesInfo name='DOI' value='10.17487/RFC6242'/>
</reference>
<reference anchor="RFC8446" target='https://www.rfc-editor.org/info/rfc8446'>
<front>
<title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
<author initials='E.' surname='Rescorla' fullname='E. Rescorla'><organization />
</author>
<date year='2018' month='August' />
<abstract><t>This document specifies version 1.3 of the Transport Layer Security
(TLS) protocol. TLS allows client/server applications to communicate over the
Internet in a way that is designed to prevent eavesdropping, tampering, and mess
age forgery.</t><t>This document updates RFCs 5705 and 6066, and obsoletes RFCs
5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2
implementations.</t></abstract>
</front>
<seriesInfo name='RFC' value='8446'/>
<seriesInfo name='DOI' value='10.17487/RFC8446'/>
</reference>
<reference anchor="RFC8341" target='https://www.rfc-editor.org/info/rfc8341'>
<front>
<title>Network Configuration Access Control Model</title>
<author initials='A.' surname='Bierman' fullname='A. Bierman'><organization /></
author>
<author initials='M.' surname='Bjorklund' fullname='M. Bjorklund'><organization
/></author>
<date year='2018' month='March' />
<abstract><t>The standardization of network configuration interfaces for use wit
h the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires
a structured and secure operating environment that promotes human usability and
multi-vendor interoperability. There is a need for standard mechanisms to rest
rict NETCONF or RESTCONF protocol access for particular users to a preconfigured
subset of all available NETCONF or RESTCONF protocol operations and content. T
his document defines such an access control model.</t><t>This document obsoletes