rfc9070.original.xml   rfc9070.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version="1.0" encoding="UTF-8"?>
<!-- This template (draft-davies-template-bare-07.xml) is for creating an <!DOCTYPE rfc [
Internet Draft using xml2rfc, which is available here: <!ENTITY nbsp "&#160;">
http://xml.resource.org. --> <!ENTITY zwsp "&#8203;">
<!-- For vocabulary, refer https://tools.ietf.org/html/rfc7991 --> <!ENTITY nbhy "&#8209;">
<!-- $ Id: draft-ietf-mpls-ldp-yang-09.xml 2020-03-20 skraza $ --> <!ENTITY wj "&#8288;">
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent"> ]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
please see http://xml.resource.org/authoring/README.html. -->
<rfc
xmlns:xi="http://www.w3.org/2001/XInclude"
category="std"
docName="draft-ietf-mpls-ldp-yang-09"
ipr="trust200902"
obsoletes=""
updates=""
submissionType="IETF"
xml:lang="en"
tocInclude="true"
tocDepth="3"
symRefs="true"
sortRefs="true"
version="3">
<!-- xml2rfc v2v3 conversion 2.38.1 -->
<!-- category values: std, bcp, info, exp, and historic
ipr values: trust200902, noModificationTrust200902,
noDerivativesTrust200902,
or pre5378Trust200902
you can add the attributes updates="NNNN" and obsoletes="NNNN"
they will automatically be output with "(if approved)" -->
<!-- ***** FRONT MATTER ***** --> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-ietf-mpls-ldp-yan g-09" number="9070" ipr="trust200902" obsoletes="" updates="" submissionType="IE TF" category="std" consensus="true" xml:lang="en" tocInclude="true" tocDepth="3" symRefs="true" sortRefs="true" version="3">
<front> <front>
<!-- The abbreviated title is used in the page header - it is only <title>YANG Data Model for MPLS LDP</title>
necessary if the full title is longer than 39 characters -->
<title abbrev="YANG Data Model for MPLS LDP">
YANG Data Model for MPLS LDP</title>
<seriesInfo name="Internet-Draft" value="draft-ietf-mpls-ldp-yang-09"/>
<!-- add 'role="editor"' below for the editors if appropriate --> <seriesInfo name="RFC" value="9070"/>
<author fullname="Kamran Raza" initials="K." role="editor" surname="Raza"> <author fullname="Kamran Raza" initials="K." role="editor" surname="Raza">
<organization>Cisco Systems</organization> <organization>Cisco Systems</organization>
<address> <address>
<postal> <postal>
<street/> <country>Canada</country>
<!-- Reorder these if your country does things differently -->
<city/>
<region/>
<code/>
<country>CA</country>
</postal> </postal>
<phone/> <phone/>
<email>skraza@cisco.com</email> <email>skraza@cisco.com</email>
</address> </address>
</author> </author>
<author fullname="Rajiv Asati" initials="R." surname="Asati"> <author fullname="Rajiv Asati" initials="R." surname="Asati">
<organization>Cisco Systems</organization> <organization>Cisco Systems</organization>
<address> <address>
<postal> <postal>
<street/> <country>United States of America</country>
<!-- Reorder these if your country does things differently -->
<city/>
<region/>
<code/>
<country>USA</country>
</postal> </postal>
<email>rajiva@cisco.com</email> <email>rajiva@cisco.com</email>
</address> </address>
</author> </author>
<author fullname="Xufeng Liu" initials="X." surname="Liu"> <author fullname="Xufeng Liu" initials="X." surname="Liu">
<organization>Volta Networks</organization> <organization>IBM Corporation</organization>
<address> <address>
<postal> <postal>
<street/> <country>United States of America</country>
<!-- Reorder these if your country does things differently -->
<city/>
<region/>
<code/>
<country>USA</country>
</postal> </postal>
<email>xufeng.liu.ietf@gmail.com</email> <email>xufeng.liu.ietf@gmail.com</email>
</address> </address>
</author> </author>
<author fullname="Santosh Esale" initials="S." surname="Esale"> <author fullname="Santosh Easale" initials="S." surname="Easale">
<organization>Juniper Networks</organization> <organization>Juniper Networks</organization>
<address> <address>
<postal> <postal>
<street/> <country>United States of America</country>
<!-- Reorder these if your country does things differently -->
<city/>
<region/>
<code/>
<country>USA</country>
</postal> </postal>
<email>sesale@juniper.net</email> <email>santosh_easale@berkeley.edu</email>
</address> </address>
</author> </author>
<author fullname="Xia Chen" initials="X." surname="Chen"> <author fullname="Xia Chen" initials="X." surname="Chen">
<organization>Huawei Technologies</organization> <organization>Huawei Technologies</organization>
<address> <address>
<postal> <postal>
<street/>
<!-- Reorder these if your country does things differently -->
<city/>
<region/>
<code/>
<country>China</country> <country>China</country>
</postal> </postal>
<email>jescia.chenxia@huawei.com</email> <email>jescia.chenxia@huawei.com</email>
</address> </address>
</author> </author>
<author fullname="Himanshu Shah" initials="H." surname="Shah"> <author fullname="Himanshu Shah" initials="H." surname="Shah">
<organization>Ciena Corporation</organization> <organization>Ciena Corporation</organization>
<address> <address>
<postal> <postal>
<street/> <country>United States of America</country>
<!-- Reorder these if your country does things differently -->
<city/>
<region/>
<code/>
<country>USA</country>
</postal> </postal>
<email>hshah@ciena.com</email> <email>hshah@ciena.com</email>
</address> </address>
</author> </author>
<date day="20" month="March" year="2020"/> <date month="March" year="2022"/>
<!-- Meta-data Declarations -->
<area>Routing</area> <area>Routing</area>
<workgroup>MPLS Working Group</workgroup> <workgroup>MPLS</workgroup>
<keyword>MPLS</keyword> <keyword>MPLS</keyword>
<keyword>LDP</keyword> <keyword>LDP</keyword>
<keyword>YANG</keyword> <keyword>YANG</keyword>
<abstract> <abstract>
<t>This document describes a YANG data model for Multi-Protocol Label Switc hing (MPLS) <t>This document describes a YANG data model for the Multiprotocol Label Sw itching (MPLS)
Label Distribution Protocol (LDP). The model also serves as the base model Label Distribution Protocol (LDP). The model also serves as the base model
to define Multipoint LDP (mLDP) model. </t> to define the Multipoint LDP (mLDP) model. </t>
<t> The YANG modules in this document conform to the Network Management <t> The YANG modules in this document conform to the Network Management
Datastore Architecture (NMDA). Datastore Architecture (NMDA).
</t> </t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Introduction</name> <name>Introduction</name>
<t>The Network Configuration Protocol (NETCONF) <xref target="RFC6241"/> i <t>The Network Configuration Protocol (NETCONF) <xref target="RFC6241"/>
s one of the network is one of the network management protocols that defines mechanisms to
management protocols that defines mechanisms to manage network devices. YA manage network devices. YANG <xref target="RFC6020"/> <xref
NG target="RFC7950"/> is a modular language that represents data structures
<xref target="RFC6020"/> <xref target="RFC7950"/> is a modular language th in an XML tree format and is used as a data modeling language for
at represents data structures in an XML NETCONF.</t>
tree format, and is used as a data modelling language for the NETCONF.</t>
<t> This document introduces a YANG data model for MPLS Label Distribution <t> This document introduces a YANG data model for the MPLS Label
Protocol (LDP) Distribution Protocol (LDP) <xref target="RFC5036"/>. This model also
<xref target="RFC5036"/>. This model also covers LDP IPv6 <xref target="RF covers LDP IPv6 <xref target="RFC7552"/> and LDP capability <xref
C7552"/> and LDP capabilities target="RFC5561"/> specifications. </t>
<xref target="RFC5561"/> specifications. </t>
<t> The data model is defined for the following constructs that are used f or managing the protocol: </t> <t> The data model is defined for the following constructs that are used f or managing the protocol: </t>
<ul> <ul>
<li> Configuration </li> <li> Configuration </li>
<li> Operational State </li> <li> Operational State </li>
<li> Executables (Actions) </li> <li> Executables (Actions) </li>
<li> Notifications </li> <li> Notifications </li>
</ul> </ul>
<t> This document is organized to define the data model for each of the ab ove constructs <t> This document is organized to define the data model for each of the ab ove constructs
skipping to change at line 195 skipping to change at line 135
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Base and Extended</name> <name>Base and Extended</name>
<t> The configuration and state items are divided into the following two broad c ategories: </t> <t> The configuration and state items are divided into the following two broad c ategories: </t>
<ul> <ul>
<li> Base </li> <li> Base </li>
<li> Extended </li> <li> Extended </li>
</ul> </ul>
<t> The "base" category contains the basic and fundamental features that are cov <t> The "base" category contains the basic and fundamental features that are
ered in LDP base covered in LDP base specification <xref target="RFC5036"/> and constitute the
specification <xref target="RFC5036"/> and constitute the minimum requirements f minimum requirements for a typical base LDP deployment, whereas the "extended"
or a typical base LDP deployment. Whereas, the "extended" category contains othe category contains other non-base features. All the items in a base category
r non-base features. All the items in a base category are mandatory and hence no are mandatory and, hence, no "if-feature" is allowed under the "base" category.
"if-feature" is allowed under the "base" category. The base and extended categ The base and extended categories are defined in their own modules as described
ories are defined in their own modules as described later. </t> later. </t>
<t> The example of base feature includes the configuration of LDP lsr-id, enabli <t> The examples of a base feature include the configuration of LDP lsr-id,
ng LDP interfaces, setting password for LDP session etc., whereas the examples o enabling LDP interfaces, setting passwords for LDP sessions, etc., whereas the
f extended feature include inbound/outbound label policies, igp sync <xref targe examples of an extended feature include inbound/outbound label policies, IGP
t="RFC5443"/>, downstream-on-demand etc. It is worth highlighting that LDP IPv6 Sync <xref target="RFC5443"/>, downstream on demand, etc. It is worth
<xref target="RFC7552"/> is also categorized as an extended feature. </t> highlighting that LDP IPv6 <xref target="RFC7552"/> is also categorized as an
extended feature. </t>
<t> While "base" model support will suffice for small deployments, it is expecte d that large deployments will require both the "base" and "extended" models supp ort from the vendors. </t> <t> While "base" model support will suffice for small deployments, it is expecte d that large deployments will require both "base" and "extended" model support f rom the vendors. </t>
</section> </section>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Specification of Requirements</name> <name>Specification of Requirements</name>
<t> In this document, the word "IP" is used to refer to both IPv4 and IPv6 <t> In this document, the word "IP" is used to refer to both IPv4 and
, unless otherwise IPv6 unless otherwise explicitly stated. For example, "IP address
explicitly stated. For example, "IP address family" should be read as "IPv family" should be read as "IPv4 and/or IPv6 address family". </t>
4 and/or IPv6 address family". </t>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Overview</name> <name>Overview</name>
<t> This document defines two new modules for LDP YANG support: </t> <t> This document defines two new modules for LDP YANG support: </t>
<ul>
<li> "ietf-mpls-ldp" module that specifies the base LDP features and au
gments /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol defined
in <xref target="RFC8349"/>. We define new identity 'mpls-ldp' for LDP and the m
odel allows only a single instance of 'mpls-ldp'. </li>
<li> "ietf-mpls-ldp-extended" module that specifies the extended LDP fe
atures and augments the base LDP module.</li>
</ul>
<t> It is to be noted that mLDP YANG model <xref target="I-D.ietf-mpls-ml <dl newline="true">
dp-yang"/> augments
LDP base and extended modules to specify the mLDP specific base and exten <dt>"ietf-mpls-ldp"
ded features. </t> </dt>
<dd>A module that specifies the base LDP features and augments
/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol defined in
<xref target="RFC8349"/>. We define the new identity 'mpls-ldp' for LDP; the
model allows only a single instance of 'mpls-ldp'.
</dd>
<dt>"ietf-mpls-ldp-extended"
</dt>
<dd>A module that specifies the extended LDP features and augments the base
LDP module.
</dd>
</dl>
<t> It is to be noted that the mLDP YANG data model <xref
target="I-D.ietf-mpls-mldp-yang"/> augments LDP base and extended
modules to specify the mLDP-specific base and extended features. </t>
<t> <t>
There are four types of containers in our module(s): </t> There are four types of containers in our module(s): </t>
<ul> <ul>
<li> Read-Write parameters for configuration (<xref target="section_l dp_cfg"/>) </li> <li> Read-write parameters for configuration (<xref target="section_l dp_cfg"/>) </li>
<li> Read-only parameters for operational state (<xref target="sectio n_ldp_oper"/>) </li> <li> Read-only parameters for operational state (<xref target="sectio n_ldp_oper"/>) </li>
<li> Notifications for events (<xref target="section_ldp_notif"/>) </ li> <li> Notifications for events (<xref target="section_ldp_notif"/>) </ li>
<li> RPCs for executing commands to perform some action (<xref target <li> RPCs for executing commands to perform some action (<xref
="section_ldp_action"/>) </li> target="section_ldp_action"/>) </li>
</ul> </ul>
<t> <t>
The modules in this document conforms to the Network Management Datasto The modules in this document conform to the Network Management
re Datastore Architecture (NMDA) defined in <xref target="RFC8342"/>.
Architecture (NMDA) defined in <xref target="RFC8342"/>. The operational state data is combined with the associated
The operational state data is combined with the associated configuratio configuration data in the same hierarchy <xref target="RFC8407"/>.
n data in When protocol states are retrieved from the NMDA operational state
the same hierarchy <xref target="RFC8407"/>. datastore, the returned states cover all "config true" (rw) and
When protocol states are retrieved from the NMDA operational state data "config false" (ro) nodes defined in the schema.
store, the
returned states cover all "config true" (rw) and "config false" (ro) no
des defined
in the schema.
</t> </t>
<t> Following diagram depicts high level LDP YANG tree organization and h ierarchy: </t> <t>The following diagram depicts high-level LDP YANG tree organization an d hierarchy: </t>
<figure anchor="LDPYangTreeHL"> <figure anchor="LDPYangTreeHL">
<name>LDP YANG tree organization</name> <name>LDP YANG Tree Organization</name>
<artwork> <sourcecode type="yangtree">
+-- rw routing +-- rw routing
+-- rw control-plane-protocols +-- rw control-plane-protocols
+-- rw control-plane-protocol +-- rw control-plane-protocol
+-- rw mpls-ldp +-- rw mpls-ldp
+-- rw ... +-- rw ...
+-- rw ... // base +-- rw ... // base
| +-- rw ... | +-- rw ...
| +-- ro ... | +-- ro ...
| +-- | +--
+-- ro ... +-- ro ...
| +-- ro ... | +-- ro ...
| +-- ro ... | +-- ro ...
| +-- | +--
+-- rw ldp-ext: .... // extended +-- rw ldp-ext: .... // extended
| +-- rw ... | +-- rw ...
| +-- ro ... | +-- ro ...
| +-- | +--
+-- ro ... +-- ro ...
+-- ro ... +-- ro ...
+-- ro ... +-- ro ...
rpcs: rpcs:
+-- x mpls-ldp-some_action +-- x mpls-ldp-some_action
+-- x . . . . . +-- x . . . . .
notifications: notifications:
+--- n mpls-ldp-some_event +--- n mpls-ldp-some_event
+--- n ... +--- n ...
</sourcecode>
</artwork>
</figure> </figure>
<t> Before going into data model details, it is important to take note <t> Before going into data model details, it is important to take
of the following points: </t> note of the following points: </t>
<ul> <ul>
<li> This model aims to address only the core LDP parameters as per R <li> This model aims to address only the core LDP parameters as
FC specification, per RFC specification, as well as well-known and widely deployed
as well as well-known and widely deployed manageability controls (suc manageability controls (such as label filtering policies to apply
h as label filtering policies to apply filtering rules on the assignment, advert filtering rules on the assignment, advertisement, and acceptance
isement, and acceptance for label bindings). for label bindings). Any vendor-specific feature should be
Any vendor specific feature should be defined in a vendor-specific au defined in a vendor-specific augmentation of this model. </li>
gmentation of this model. </li>
<li> Multi-topology LDP <xref target="RFC7307"/> is beyond the scope of this document. </li> <li> Multi-topology LDP <xref target="RFC7307"/> is beyond the scope of this document. </li>
<li> This model does not cover any applications running on top of LDP <li> This model does not cover any applications running on top of
, nor does LDP, nor does it cover any Operations, Administration, and
it cover any OAM procedures for LDP. </li> Maintenance (OAM) procedures for LDP. </li>
<li> This model is a VPN Routing and Forwarding (VRF)-centric model. <li>This model is a VRF-centric model. It is important to note
It is important to note that <xref target="RFC4364"/> defines VRF tab that <xref target="RFC4364"/> defines VPN Routing and Forwarding
les and default forwarding tables as (VRF) tables and default forwarding tables as different; however,
different, however from a YANG modelling perspective this introduces from a YANG modeling perspective, this introduces unnecessary
unnecessary complications, hence we are complications; hence, we are treating the default forwarding table
treating the default forwarding table as just another VRF. </li> as just another VRF. </li>
<li> A "network-instance", as defined in <xref target="RFC8529"/>, re <li> A "network-instance", as defined in <xref target="RFC8529"/>,
fers to a VRF instance refers to a VRF instance (both default and non-default) within the
(both default and non-default) within the scope of this model. </li> scope of this model. </li>
<li> This model supports two address-families, namely "ipv4" and "ipv 6". </li> <li> This model supports two address families, namely, "ipv4" and "ip v6". </li>
<li> This model assumes platform-wide label space (i.e. label space I <li> This model assumes platform-wide label space (i.e., label
d of zero). However, when Upstream Label assignment space Id of zero). However, when upstream label assignment <xref
<xref target="RFC6389"/> is in use, an upstream assigned label is loo target="RFC6389"/> is in use, an upstream assigned label is looked
ked up in a Context-Specific label space up in a Context-Specific Label Space as defined in <xref
as defined in <xref target="RFC5331"/>. </li> target="RFC5331"/>. </li>
<li> The label and peer policies (including filters) are defined usin <li> The label and peer policies (including filters) are defined
g prefix-set and neighbor-set respectively as defined in routing-policy model <x using prefix-set and neighbor-set, respectively, as defined in the
ref target="I-D.ietf-rtgwg-policy-model"/>. </li> routing-policy model <xref target="RFC9067"/>. </li>
<li> <t> This model uses the terms LDP "neighbor"/"adjacency", "sessi <li> <t> This model uses the terms LDP "neighbor/adjacency",
on", and "peer" with the following semantics: </t> "session", and "peer" with the following semantics: </t>
<ul> <dl>
<li> Neighbor/Adjacency: An LDP enabled LSR that is discovered thro
ugh LDP discovery mechanisms. </li>
<li> Session: An LDP neighbor with whom a TCP connection has been e
stablished. </li>
<li> Peer: An LDP session which has successfully progressed beyond
its initialization phase and is
either already exchanging the bindings or is ready to do so. </li>
</ul>
<t>
It is to be noted that LDP Graceful Restart (GR) mechanisms defined
in <xref target="RFC3478"/> allow keeping the
exchanged bindings for some time after a session goes down with a pee
r. We call such a state belonging to a "stale" peer
-- i.e. keeping peer bindings from a peer with whom currently there i
s either no connection established or
connection is established but GR session is in recovery state.
When used in this document, the above terms will refer strictly to th <dt>Neighbor/Adjacency:
e semantics and definitions defined for them. </t></li> </dt>
<dd>An LDP-enabled Label Switching Router (LSR) that is discovered through LDP
discovery mechanisms.
</dd>
<dt>Session:
</dt>
<dd>An LDP neighbor with whom a TCP connection has been established.
</dd>
<dt>Peer:
</dt>
<dd>An LDP session that has successfully progressed beyond its initialization
phase and is either already exchanging the bindings or is ready to do so.
</dd>
</dl>
<t>
It is to be noted that LDP Graceful Restart (GR) mechanisms
defined in <xref target="RFC3478"/> allow keeping the exchanged
bindings for some time after a session goes down with a peer. We
refer to such a state as belonging to a "stale" peer, i.e., keeping
peer
bindings from a peer with whom currently there is either no
connection established or connection is established but the GR sessi
on
is in recovery state.
When used in this document, the above terms will refer strictly to
the semantics and definitions defined for them. </t></li>
</ul> </ul>
<t> <t>
A simplified graphical tree representation of base and extended LDP YAN A simplified graphical tree representation of base and extended LDP
G data YANG data models is presented in <xref target="ConsolidatedTree"/>.
model is presented in <xref target="ConsolidatedTree"/>. The meaning of the symbols in these tree diagrams is defined in
The meaning of the symbols in these tree diagrams is defined in <xref t <xref target="RFC8340"/>.
arget="RFC8340"/>.
</t> </t>
<t> <t>
The actual YANG specification for base and extended modules is captured The actual YANG specification for base and extended modules is
in <xref target="YANG"/>. captured in <xref target="YANG"/>.
</t> </t>
<t> <t>
While presenting the YANG tree view and actual specification, this do While presenting the YANG tree view and actual specification, this
cument assumes readers' document assumes readers are familiar with the concepts of YANG
familiarity with the concepts of YANG modeling, its presentation and modeling, its presentation, and its compilation.
its compilation.
</t> </t>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>The Complete Tree</name> <name>The Complete Tree</name>
<t> Following is a complete tree representation of configuration, state, <t>The following is a complete tree representation of configuration,
notification, state, notification, and RPC items under LDP base and extended
and RPC items under LDP base and extended modules. </t> modules. </t>
<figure anchor="ConsolidatedTree"> <figure anchor="ConsolidatedTree">
<name>Complete Tree</name> <name>Complete Tree</name>
<artwork> <sourcecode type="yangtree">
module: ietf-mpls-ldp module: ietf-mpls-ldp
augment /rt:routing/rt:control-plane-protocols augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol: /rt:control-plane-protocol:
+--rw mpls-ldp +--rw mpls-ldp
+--rw global +--rw global
| +--rw capability | +--rw capability
| | +--rw ldp-ext:end-of-lib {capability-end-of-lib}? | | +--rw ldp-ext:end-of-lib {capability-end-of-lib}?
| | | +--rw ldp-ext:enabled? boolean | | | +--rw ldp-ext:enabled? boolean
| | +--rw ldp-ext:typed-wildcard-fec | | +--rw ldp-ext:typed-wildcard-fec
| | | {capability-typed-wildcard-fec}? | | | {capability-typed-wildcard-fec}?
skipping to change at line 389 skipping to change at line 389
| | | +--ro bindings | | | +--ro bindings
| | | | +--ro address* [address] | | | | +--ro address* [address]
| | | | | +--ro address inet:ipv4-address | | | | | +--ro address inet:ipv4-address
| | | | | +--ro advertisement-type? advertised-received | | | | | +--ro advertisement-type? advertised-received
| | | | | +--ro peer | | | | | +--ro peer
| | | | | +--ro lsr-id? leafref | | | | | +--ro lsr-id? leafref
| | | | | +--ro label-space-id? leafref | | | | | +--ro label-space-id? leafref
| | | | +--ro fec-label* [fec] | | | | +--ro fec-label* [fec]
| | | | +--ro fec inet:ipv4-prefix | | | | +--ro fec inet:ipv4-prefix
| | | | +--ro peer* | | | | +--ro peer*
| | | | [lsr-id label-space-id advertisement-type] | | | | [lsr-id label-space-id advertisement-type]
| | | | +--ro lsr-id leafref | | | | +--ro lsr-id leafref
| | | | +--ro label-space-id leafref | | | | +--ro label-space-id leafref
| | | | +--ro advertisement-type | | | | +--ro advertisement-type
| | | | | advertised-received | | | | | advertised-received
| | | | +--ro label? | | | | +--ro label?
| | | | | rt-types:mpls-label | | | | | rt-types:mpls-label
| | | | +--ro used-in-forwarding? boolean | | | | +--ro used-in-forwarding? boolean
| | | +--rw ldp-ext:label-policy | | | +--rw ldp-ext:label-policy
| | | | +--rw ldp-ext:advertise | | | | +--rw ldp-ext:advertise
| | | | | +--rw ldp-ext:egress-explicit-null | | | | | +--rw ldp-ext:egress-explicit-null
skipping to change at line 450 skipping to change at line 450
| | | +--ro ldp-ext:address | | | +--ro ldp-ext:address
| | | | inet:ipv6-address | | | | inet:ipv6-address
| | | +--ro ldp-ext:advertisement-type? | | | +--ro ldp-ext:advertisement-type?
| | | | advertised-received | | | | advertised-received
| | | +--ro ldp-ext:peer | | | +--ro ldp-ext:peer
| | | +--ro ldp-ext:lsr-id? leafref | | | +--ro ldp-ext:lsr-id? leafref
| | | +--ro ldp-ext:label-space-id? leafref | | | +--ro ldp-ext:label-space-id? leafref
| | +--ro ldp-ext:fec-label* [fec] | | +--ro ldp-ext:fec-label* [fec]
| | +--ro ldp-ext:fec inet:ipv6-prefix | | +--ro ldp-ext:fec inet:ipv6-prefix
| | +--ro ldp-ext:peer* | | +--ro ldp-ext:peer*
| | [lsr-id label-space-id advertisement-type] | | [lsr-id label-space-id advertisement-type]
| | +--ro ldp-ext:lsr-id leafref | | +--ro ldp-ext:lsr-id leafref
| | +--ro ldp-ext:label-space-id leafref | | +--ro ldp-ext:label-space-id leafref
| | +--ro ldp-ext:advertisement-type | | +--ro ldp-ext:advertisement-type
| | | advertised-received | | | advertised-received
| | +--ro ldp-ext:label? | | +--ro ldp-ext:label?
| | | rt-types:mpls-label | | | rt-types:mpls-label
| | +--ro ldp-ext:used-in-forwarding? boolean | | +--ro ldp-ext:used-in-forwarding? boolean
| +--rw ldp-ext:forwarding-nexthop | +--rw ldp-ext:forwarding-nexthop
| | {forwarding-nexthop-config}? | | {forwarding-nexthop-config}?
| | +--rw ldp-ext:interfaces | | +--rw ldp-ext:interfaces
skipping to change at line 521 skipping to change at line 521
| | | | | +--ro ldp-ext:remaining? uint16 | | | | | +--ro ldp-ext:remaining? uint16
| | | | +--ro ldp-ext:next-hello? uint16 | | | | +--ro ldp-ext:next-hello? uint16
| | | | +--ro ldp-ext:statistics | | | | +--ro ldp-ext:statistics
| | | | | +--ro ldp-ext:discontinuity-time | | | | | +--ro ldp-ext:discontinuity-time
| | | | | | yang:date-and-time | | | | | | yang:date-and-time
| | | | | +--ro ldp-ext:hello-received? | | | | | +--ro ldp-ext:hello-received?
| | | | | | yang:counter64 | | | | | | yang:counter64
| | | | | +--ro ldp-ext:hello-dropped? | | | | | +--ro ldp-ext:hello-dropped?
| | | | | yang:counter64 | | | | | yang:counter64
| | | | +--ro ldp-ext:peer | | | | +--ro ldp-ext:peer
| | | | +--ro ldp-ext:lsr-id? leafref | | | | +--ro ldp-ext:lsr-id? leafref
| | | | +--ro ldp-ext:label-space-id? leafref | | | | +--ro ldp-ext:label-space-id? leafref
| | | +--rw ldp-ext:transport-address? union | | | +--rw ldp-ext:transport-address? union
| | +--rw ldp-ext:hello-holdtime? uint16 | | +--rw ldp-ext:hello-holdtime? uint16
| | | {per-interface-timer-config}? | | | {per-interface-timer-config}?
| | +--rw ldp-ext:hello-interval? uint16 | | +--rw ldp-ext:hello-interval? uint16
| | | {per-interface-timer-config}? | | | {per-interface-timer-config}?
| | +--rw ldp-ext:igp-synchronization-delay? uint16 | | +--rw ldp-ext:igp-synchronization-delay? uint16
| | {per-interface-timer-config}? | | {per-interface-timer-config}?
| +--rw targeted | +--rw targeted
| +--rw hello-holdtime? uint16 | +--rw hello-holdtime? uint16
| +--rw hello-interval? uint16 | +--rw hello-interval? uint16
skipping to change at line 754 skipping to change at line 754
| +--rw ldp-ext:enabled? boolean | +--rw ldp-ext:enabled? boolean
| +--rw ldp-ext:peer-list? peer-list-ref | +--rw ldp-ext:peer-list? peer-list-ref
+--rw ldp-ext:dual-stack-transport-preference +--rw ldp-ext:dual-stack-transport-preference
{peers-dual-stack-transport-preference}? {peers-dual-stack-transport-preference}?
+--rw ldp-ext:max-wait? uint16 +--rw ldp-ext:max-wait? uint16
+--rw ldp-ext:prefer-ipv4! +--rw ldp-ext:prefer-ipv4!
+--rw ldp-ext:peer-list? peer-list-ref +--rw ldp-ext:peer-list? peer-list-ref
rpcs: rpcs:
+---x mpls-ldp-clear-peer +---x mpls-ldp-clear-peer
| +---w input | +---w input
| +---w protocol-name? leafref | +---w protocol-name? leafref
| +---w lsr-id? leafref | +---w lsr-id? leafref
| +---w label-space-id? leafref | +---w label-space-id? leafref
+---x mpls-ldp-clear-hello-adjacency +---x mpls-ldp-clear-hello-adjacency
| +---w input | +---w input
| +---w hello-adjacency | +---w hello-adjacency
| +---w protocol-name? leafref | +---w protocol-name? leafref
| +---w (hello-adjacency-type)? | +---w (hello-adjacency-type)?
| +--:(targeted) | +--:(targeted)
| | +---w targeted! | | +---w targeted!
| | +---w target-address? inet:ip-address | | +---w target-address? inet:ip-address
| +--:(link) | +--:(link)
| +---w link! | +---w link!
| +---w next-hop-interface? leafref | +---w next-hop-interface? leafref
| +---w next-hop-address? inet:ip-address | +---w next-hop-address? inet:ip-address
+---x mpls-ldp-clear-peer-statistics +---x mpls-ldp-clear-peer-statistics
+---w input +---w input
+---w protocol-name? leafref +---w protocol-name? leafref
+---w lsr-id? leafref +---w lsr-id? leafref
+---w label-space-id? leafref +---w label-space-id? leafref
notifications: notifications:
+---n mpls-ldp-peer-event +---n mpls-ldp-peer-event
| +--ro event-type? oper-status-event-type | +--ro event-type? oper-status-event-type
| +--ro peer | +--ro peer
| +--ro protocol-name? leafref | +--ro protocol-name? leafref
| +--ro lsr-id? leafref | +--ro lsr-id? leafref
| +--ro label-space-id? leafref | +--ro label-space-id? leafref
+---n mpls-ldp-hello-adjacency-event +---n mpls-ldp-hello-adjacency-event
| +--ro event-type? oper-status-event-type | +--ro event-type? oper-status-event-type
| +--ro protocol-name? leafref | +--ro protocol-name? leafref
| +--ro (hello-adjacency-type)? | +--ro (hello-adjacency-type)?
| +--:(targeted) | +--:(targeted)
| | +--ro targeted | | +--ro targeted
| | +--ro target-address? inet:ip-address | | +--ro target-address? inet:ip-address
| +--:(link) | +--:(link)
| +--ro link | +--ro link
| +--ro next-hop-interface? if:interface-ref | +--ro next-hop-interface? if:interface-ref
| +--ro next-hop-address? inet:ip-address | +--ro next-hop-address? inet:ip-address
+---n mpls-ldp-fec-event +---n mpls-ldp-fec-event
+--ro event-type? oper-status-event-type +--ro event-type? oper-status-event-type
+--ro protocol-name? leafref +--ro protocol-name? leafref
+--ro fec? inet:ip-prefix +--ro fec? inet:ip-prefix
</sourcecode>
</artwork>
</figure> </figure>
</section> </section>
<section anchor="section_ldp_cfg" numbered="true" toc="default"> <section anchor="section_ldp_cfg" numbered="true" toc="default">
<name>Configuration</name> <name>Configuration</name>
<t> This specification defines the configuration parameters for base LDP <t> This specification defines the configuration parameters for base
as specified in <xref target="RFC5036"/> and LDP as specified in <xref target="RFC5036"/> and LDP IPv6 <xref
LDP IPv6 <xref target="RFC7552"/>. Moreover, it incorporates provisions t target="RFC7552"/>. Moreover, it incorporates provisions to enable LDP
o enable LDP Capabilities <xref target="RFC5561"/>, Capabilities <xref target="RFC5561"/> and defines some of the most
and defines some of the most significant and commonly used capabilities s significant and commonly used capabilities such as Typed Wildcard
uch as Typed Wildcard FEC <xref target="RFC5918"/>, End-of-LIB
FEC <xref target="RFC5918"/>, End-of-LIB <xref target="RFC5919"/>, and LD <xref target="RFC5919"/>, and LDP Upstream
P Upstream Label Assignment Label Assignment <xref target="RFC6389"/>. </t>
<xref target="RFC6389"/>. </t>
<t> This model augments /rt:routing/rt:control-plane-protocols/rt:control <t> This model augments
-plane-protocol that is defined in <xref target="RFC8349"/> and follows NMDA as /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol,
mentioned earlier. which is defined in <xref target="RFC8349"/> and follows NMDA as
mentioned earlier.
</t> </t>
<t> Following is the high-level configuration organization for base LDP m <t>The following is the high-level configuration organization for the
odule: </t> base LDP module: </t>
<figure anchor="LDPCfgOrgHL"> <figure anchor="LDPCfgOrgHL">
<name>Base Configuration organization</name> <name>Base Configuration Organization</name>
<artwork> <sourcecode type="yangtree">
augment /rt:routing/rt:control-plane-protocols: augment /rt:routing/rt:control-plane-protocols:
/rt:control-plane-protocol: /rt:control-plane-protocol:
+-- mpls-ldp +-- mpls-ldp
+-- global +-- global
| +-- ... | +-- ...
| +-- ... | +-- ...
| +-- address-families | +-- address-families
| | +-- ipv4 | | +-- ipv4
| | +-- . . . | | +-- . . .
| | +-- . . . | | +-- . . .
| +-- capability | +-- capability
| +-- ... | +-- ...
| +-- ... | +-- ...
+-- discovery +-- discovery
| +-- interfaces | +-- interfaces
| | +-- ... | | +-- ...
| | +-- ... | | +-- ...
| | +-- interface* [interface] | | +-- interface* [interface]
| | +-- ... | | +-- ...
| | +-- address-families | | +-- address-families
| | +-- ipv4 | | +-- ipv4
| | +-- ... | | +-- ...
| | +-- ... | | +-- ...
| +-- targeted | +-- targeted
| +-- ... | +-- ...
| +-- address-families | +-- address-families
| +-- ipv4 | +-- ipv4
| +- target* [adjacent-address] | +-- target* [adjacent-address]
| +- ... | +-- ...
| +- ... | +-- ...
+-- peers +-- peers
+-- ... +-- ...
+-- ... +-- ...
+-- peer* [lsr-id label-space-id] +-- peer* [lsr-id label-space-id]
+-- ... +-- ...
+-- ... +-- ...
</sourcecode>
</artwork>
</figure> </figure>
<t> Following is the high-level configuration organization for extended L <t>The following is the high-level configuration organization for the
DP: </t> extended LDP module: </t>
<figure anchor="LDPCfgExtOrgHL"> <figure anchor="LDPCfgExtOrgHL">
<name>Extended Configuration organization</name> <name>Extended Configuration Organization</name>
<artwork>
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol
+-- mpls-ldp
+-- global
| +-- ...
| +-- ...
| +-- address-families
| | +-- ipv4
| | | +-- . . .
| | | +-- . . .
| | | +-- label-policy
| | | +-- ...
| | | +-- ...
| | +-- ipv6
| | +-- . . .
| | +-- . . .
| | +-- label-policy
| | +-- ...
| | +-- ...
| +-- capability
| | +-- ...
| | +-- ...
| +-- discovery
| +-- interfaces
| | +-- ...
| | +-- ...
| | +-- interface* [interface]
| | +-- ...
| | +-- address-families
| | +-- ipv4
| | | +-- ...
| | | +-- ...
| | +-- ipv6
| | +-- ...
| | +-- ...
| +-- targeteted
| +-- ...
| +-- address-families
| +-- ipv6
| +- target* [adjacent-address]
| +- ...
| +- ...
+-- forwarding-nexthop
| +-- ...
| +-- ...
+-- peers
+-- ...
+-- ...
+-- peer*
+-- ...
+-- ...
+-- label-policy
| +-- ..
+-- address-families
+-- ipv4
| +-- ...
+-- ipv6
+-- ...
</artwork> <sourcecode type="yangtree">
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol
+-- mpls-ldp
+-- global
| +-- ...
| +-- ...
| +-- address-families
| | +-- ipv4
| | | +-- . . .
| | | +-- . . .
| | | +-- label-policy
| | | +-- ...
| | | +-- ...
| | +-- ipv6
| | +-- . . .
| | +-- . . .
| | +-- label-policy
| | +-- ...
| | +-- ...
| +-- capability
| | +-- ...
| | +-- ...
| +-- discovery
| +-- interfaces
| | +-- ...
| | +-- ...
| | +-- interface* [interface]
| | +-- ...
| | +-- address-families
| | +-- ipv4
| | | +-- ...
| | | +-- ...
| | +-- ipv6
| | +-- ...
| | +-- ...
| +-- targeted
| +-- ...
| +-- address-families
| +-- ipv6
| +- target* [adjacent-address]
| +- ...
| +- ...
+-- forwarding-nexthop
| +-- ...
| +-- ...
+-- peers
+-- ...
+-- ...
+-- peer*
+-- ...
+-- ...
+-- label-policy
| +-- ..
+-- address-families
+-- ipv4
| +-- ...
+-- ipv6
+-- ...
</sourcecode>
</figure> </figure>
<t> Given the configuration hierarchy, the model allows inheritance such <t>Given the configuration hierarchy, the model allows inheritance
that an item in a child tree such that an item in a child tree is able to derive value from a
is able to derive value from a similar or related item in one of the pare similar or related item in one of the parents. For instance, Hello
nts. For instance, hello holdtime holdtime can be configured per VRF or per VRF interface, thus allowing
can be configured per-VRF or per-VRF-interface, thus allowing inheritance inheritance as well flexibility to override with a different value at
as well any child level. </t>
flexibility to override with a different value at any child level. </t>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Configuration Hierarchy</name> <name>Configuration Hierarchy</name>
<t> LDP module resides under a network-instance and the scope of any LDP <t>The LDP module resides under a network-instance and the scope of
configuration defined under this tree is any LDP configuration defined under this tree is per network-instance
per network-instance (per-VRF). This configuration is further divided in (per-VRF). This configuration is further divided into sub categories
to sub categories as follows. </t> as follows:</t>
<ul> <ul>
<li>Global parameters</li> <li>Global parameters</li>
<li>Per-address-family parameters</li> <li>Per-address-family parameters</li>
<li>LDP Capabilities parameters</li> <li>LDP Capabilities parameters</li>
<li> <li>
<t>Hello Discovery parameters</t> <t>Hello Discovery parameters</t>
<ul> <ul>
<li> <li>
<t>interfaces</t> <t>interfaces</t>
<ul> <ul>
skipping to change at line 973 skipping to change at line 984
<t>Peer parameters</t> <t>Peer parameters</t>
<ul> <ul>
<li>Global</li> <li>Global</li>
<li>Per-peer: Global</li> <li>Per-peer: Global</li>
<li>Per-peer: Per-address-family</li> <li>Per-peer: Per-address-family</li>
</ul> </ul>
</li> </li>
<li>Forwarding parameters</li> <li>Forwarding parameters</li>
</ul> </ul>
<t> Following subsections briefly explain these configuration areas. </ t> <t>The following subsections briefly explain these configuration areas. </t>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Global parameters</name> <name>Global Parameters</name>
<t> There are configuration items that are available directly under <t> There are configuration items that are available directly
a VRF instance and do not fall under any under a VRF instance and do not fall under any other subtree. An
other sub tree. Example of such a parameter is LDP LSR Id that is t example of such a parameter is an LDP LSR Id that is typically
ypically configured per VRF. To keep legacy configured per VRF. To keep legacy LDP features and applications
LDP features and applications working in an LDP IPv4 networks with working in an LDP IPv4 network with this model, this document
this model, this document recommends an operator recommends an operator to pick a routable IPv4 unicast address
to pick a routable IPv4 unicast address (within a routing domain) a (within a routing domain) as an LSR Id. </t>
s an LSR Id. </t>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Capabilities parameters</name> <name>Capabilities Parameters</name>
<t> This container falls under the global tree and holds the LDP ca <t> This container falls under the global tree and holds the LDP
pabilities that are to be enabled for certain features. capabilities that are to be enabled for certain features. By
By default, an LDP capability is disabled unless explicitly enabled default, an LDP capability is disabled unless explicitly
. These capabilities are typically used to negotiate enabled. These capabilities are typically used to negotiate with
with LDP peer(s) the support/non-support related to a feature and i LDP peer(s) the support/non-support related to a feature and its
ts parameters. The scope of a capability enabled parameters. The scope of a capability enabled under this
under this container applies to all LDP peers in the given VRF inst container applies to all LDP peers in the given VRF
ance. There is also a peer level capability instance. There is also a peer-level capability container that
container that is provided to override a capability that is enabled is provided to override a capability that is enabled/specified
/specified at VRF level. </t> at VRF level. </t>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Per-Address-Family parameters</name> <name>Per-Address-Family Parameters</name>
<t> Any LDP configuration parameter related to IP address family (A <t> Any LDP configuration parameter related to an IP address
F) whose scope is VRF wide is configured under this family (AF) whose scope is VRF wide is configured under this
tree. The examples of per-AF parameters include enabling LDP for an tree. The examples of per-AF parameters include enabling LDP for
address family, prefix-list based label policies, and LDP an address family, prefix-list-based label policies, and LDP
transport address. </t> transport address. </t>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Hello Discovery parameters</name> <name>Hello Discovery Parameters</name>
<t> This container is used to hold LDP configuration related to Hel <t> This container is used to hold LDP configuration related to
lo and discovery process for both basic (link) the Hello and discovery process for both basic (link) and extended
and extended (targeted) discovery. </t> (targeted) discovery. </t>
<t> The "interfaces" is a container to configure parameters related <t> The "interfaces" container is used to configure parameters
to VRF interfaces. There are parameters that apply related to VRF interfaces. There are parameters that apply to
to all interfaces (such as hello timers), as well as parameters tha all interfaces (such as Hello timers) as well as parameters
t can be configured per-interface. Hence, an interface that can be configured per interface. Hence, an interface list
list is defined under "interfaces" container. The model defines par is defined under the "interfaces" container. The model defines
ameters to configure per-interface non AF related items, parameters to configure per-interface non-AF-related items as
as well as per-interface per-AF items. The example of the former is well as per-interface per-AF items. The example of the former is
interface hello timers, and example of the latter is enabling interface Hello timers, and an example of the latter is enabling
hellos for a given AF under an interface. </t> hellos for a given AF under an interface. </t>
<t> The "targeted" container under a VRF instance allows to configu <t> The "targeted" container under a VRF instance allows for the
re LDP targeted discovery related parameters. Within configuration of parameters related to LDP targeted
this container, the "target" list provides a means to configure mul discovery. Within this container, the "target" list provides a
tiple target addresses to perform extended discovery means to configure multiple target addresses to perform extended
to a specific destination target, as well as to fine-tune the per-t discovery to a specific destination target, as well as to
arget parameters. </t> fine tune the per-target parameters. </t>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Peer parameters</name> <name>Peer Parameters</name>
<t> This container is used to hold LDP configuration related to LDP
sessions and peers under a VRF instance. This container <t>
allows to configure parameters that either apply on VRF's all peers
or a subset (peer-list) of VRF peers. The example of This container is used to hold LDP configuration related to LDP sessions and
such parameters include authentication password, session KA timers peers under a VRF instance.
etc. Moreover, the model also allows per-peer parameter
tuning by specifying a "peer" list under the "peers" container. A p This container allows for the configuration of parameters that either apply to
eer is uniquely all or a subset (peer-list) of peers in a given VRF.
The example of such parameters includes authentication
passwords, session KeepAlive (KA) timers, etc. Moreover, the
model also allows per-peer parameter tuning by specifying a
"peer" list under the "peers" container. A peer is uniquely
identified by its LSR Id. </t> identified by its LSR Id. </t>
<t> Like per-interface parameters, some per-peer parameters are AF- <t> Like per-interface parameters, some per-peer parameters are
agnostic (i.e. either non AF related or apply to both AF agnostic (i.e., either non-AF related or apply to both IP
IP address families), and some that belong to an AF. The example of address families), and some belong to an AF. The example of
the former is per-peer session password configuration, the former is per-peer session password configuration, whereas
whereas the example of the latter is prefix-list based label polici the example of the latter is prefix-lis-based label policies
es (inbound and outbound) that apply to a given peer. </t> (inbound and outbound) that apply to a given peer. </t>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Forwarding parameters</name> <name>Forwarding Parameters</name>
<t> This container is used to hold configuration used to control LD
P forwarding behavior under a VRF instance. <t> This container is used to hold configuration used to control LDP
One example of a configuration under this container is when a user forwarding behavior under a VRF instance.
wishes to enable neighbor discovery on an interface
but wishes to disable use of the same interface as forwarding nexth One example of a configuration under this container is when a user wishes to
op. This example configuration makes sense only when enable LDP neighbor discovery on an interface but wishes to disable use of the
there are more than one LDP enabled interfaces towards the neighbor same interface for forwarding MPLS packets.
. </t>
This example configuration makes sense only when there are more
than one LDP-enabled interfaces towards a neighbor. </t>
</section> </section>
</section> </section>
</section> </section>
<section anchor="section_ldp_oper" numbered="true" toc="default"> <section anchor="section_ldp_oper" numbered="true" toc="default">
<name>Operational State</name> <name>Operational State</name>
<t> Operational state of LDP can be queried and obtained from read-only s <t>The operational state of LDP can be queried and obtained from
tate containers that fall under the same tree read-only state containers that fall under the same tree
(/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol) as the (/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol) as
configuration. </t> the configuration. </t>
<t> Following are main areas for which LDP operational state is defined : </t> <t>The following are main areas for which LDP operational state is defi ned: </t>
<ul> <ul>
<li> Neighbor Adjacencies </li> <li> Neighbor Adjacencies </li>
<li> Peer </li> <li> Peer </li>
<li> Bindings (FEC-label and address) </li> <li> Bindings (FEC-Label and address) </li>
<li> Capabilities </li> <li> Capabilities </li>
</ul> </ul>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Adjacency state</name> <name>Adjacency State</name>
<t> Neighbor adjacencies are per address-family hello adjacencies tha <t> Neighbor adjacencies are per-address-family Hello adjacencies
t are formed with neighbors as result of that are formed with neighbors as a result of LDP basic or
LDP basic or extended discovery. In terms of organization, there is a extended discovery. In terms of organization, there is a source of
source of discovery (e.g. interface or target discovery (e.g., interface or target address) along with its
address) along with its associated parameters and one or more discove associated parameters and one or more discovered neighbors along
red neighbors along with neighbor discovery related with neighbor-discovery-related parameters. For the basic
parameters. For the basic discovery, there could be more than one dis discovery, there could be more than one discovered neighbor for a
covered neighbor for a given source (interface), given source (interface), whereas there is at most one discovered
whereas there is at most one discovered neighbor for an extended disc neighbor for an extended discovery source (local-address and
overy source (local-address and target-address). target-address). It is also to be noted that the reason for a
It is also to be noted that the reason for a targeted neighbor adjace targeted neighbor adjacency could be either an active source
ncy could be either an active source (locally (locally configured targeted) or passive source (to allow any
configured targeted) or passive source (to allow any incoming extende incoming extended/targeted hellos). A neighbor/adjacency record
d/targeted hellos). A neighbor/adjacency record also contains session state that helps highlight whether a given
also contains session-state that helps highlight whether a given adja adjacency has progressed to the subsequent session level or
cency has progressed to subsequent session level eventual peer level. </t>
or to eventual peer level. </t>
<t> Following captures high level tree hierarchy for neighbor adjacen <t>The following captures high-level tree hierarchy for neighbor
cy state. The tree is shown for ipv4 address-family only; a similar tree exists adjacency state. The tree is shown for ipv4 address-family only; a
for ipv6 address-family as well. </t> similar tree exists for ipv6 address-family as well. </t>
<figure anchor="LDPAdjState">
<name>Adjacency state</name>
<artwork>
+--rw mpls-ldp! <figure anchor="LDPAdjState">
+--rw discovery
+--rw interfaces
| +--rw interface* [interface]
| +--rw address-families
| +--rw ipv4
| +--ro hello-adjacencies
| +--ro hello-adjacencies* [adjacent-address]
| +--ro adjacent-address
| . . . .
| . . . .
+--rw targeted
+--rw address-families
+--rw ipv4
+--ro hello-adjacencies
+--ro hello-adjacencies*
| [local-address adjacent-address]
+--ro local-address
+--ro adjacent-address
. . . .
. . . .
</artwork> <name>Adjacency State</name>
<sourcecode type="yangtree">
+--rw mpls-ldp!
+--rw discovery
+--rw interfaces
| +--rw interface* [interface]
| +--rw address-families
| +--rw ipv4
| +--ro hello-adjacencies
| +--ro hello-adjacencies* [adjacent-address]
| +--ro adjacent-address
| . . . .
| . . . .
+--rw targeted
+--rw address-families
+--rw ipv4
+--ro hello-adjacencies
+--ro hello-adjacencies*
| [local-address adjacent-address]
+--ro local-address
+--ro adjacent-address
. . . .
. . . .
</sourcecode>
</figure> </figure>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Peer state</name> <name>Peer State</name>
<t> Peer related state is presented under peers tree. This is one of
the core state that provides info on
the session related parameters (mode, authentication, KA timeout etc.
), TCP connection info, hello adjacencies for
the peer, statistics related to messages and bindings, and capabiliti
es exchange info. </t>
<t> Following captures high level tree hierarchy for peer state. The
peer's hello adjacencies tree is shown for ipv4 address-family only; a similar t
ree exists for ipv6 address-family as well.</t>
<figure anchor="LDPPeerState"> <t>Peer-related state is presented under a peers tree. This is one
<name>Peer state</name> of the core states that provides info on the session-related
<artwork> parameters (mode, authentication, KA timeout, etc.), TCP connection
info, Hello adjacencies for the peer, statistics related to
messages and bindings, and capabilities exchange info. </t>
+--rw mpls-ldp! <t>The following captures high-level tree hierarchy for peer
+--rw peers state. The peer's Hello adjacencies tree is shown for ipv4
+--rw peer* [lsr-id label-space-id] address-family only; a similar tree exists for ipv6 address-family
+--rw lsr-id as well.</t>
+--rw label-space-id
+--ro label-advertisement-mode
+--ro session-state
+--ro tcp-connection
+--ro session-holdtime?
+--ro up-time
+-- . . . .
+--ro address-families
| +--ro ipv4
| +--ro hello-adjacencies
| +--ro hello-adjacencies*
| [local-address adjacent-address]
| . . . .
| . . . .
+--ro received-peer-state
| +--ro . . . .
| +--ro capability
| +--ro . . . .
+--ro statistics
+-- . . . .
+-- received
| +-- ...
+-- sent
+-- ...
</artwork> <figure anchor="LDPPeerState">
<name>Peer State</name>
<sourcecode type="yangtree">
+--rw mpls-ldp!
+--rw peers
+--rw peer* [lsr-id label-space-id]
+--rw lsr-id
+--rw label-space-id
+--ro label-advertisement-mode
+--ro session-state
+--ro tcp-connection
+--ro session-holdtime?
+--ro up-time
+-- . . . .
+--ro address-families
| +--ro ipv4
| +--ro hello-adjacencies
| +--ro hello-adjacencies*
| [local-address adjacent-address]
| . . . .
| . . . .
+--ro received-peer-state
| +--ro . . . .
| +--ro capability
| +--ro . . . .
+--ro statistics
+-- . . . .
+-- received
| +-- ...
+-- sent
+-- ...
</sourcecode>
</figure> </figure>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Bindings state</name> <name>Bindings State</name>
<t> Binding state provides information on LDP FEC-label bindings as w <t> Bindings state provides information on LDP FEC-Label bindings
ell as address binding for both inbound (received) as well as address bindings for both inbound (received) as well as
as well as outbound (advertised) direction. FEC-label bindings are pr outbound (advertised) direction. FEC-Label bindings are presented
esented as a FEC-centric view, and address bindings are in a FEC-centric view, and address bindings are presented in an
presented as an address-centric view: </t> address-centric view: </t>
<figure anchor="ExampleBndg"> <figure anchor="ExampleBndg">
<name>Example Bindings</name> <name>Example Bindings</name>
<artwork> <sourcecode>
FEC-Label bindings: FEC-Label bindings:
FEC 203.0.113.1/32: FEC 203.0.113.1/32:
advertised: local-label 16000 advertised: local-label 16000
peer 192.0.2.1:0 peer 192.0.2.1:0
peer 192.0.2.2:0 peer 192.0.2.2:0
peer 192.0.2.3:0 peer 192.0.2.3:0
received: received:
peer 192.0.2.1:0, label 16002, used-in-forwarding=Yes peer 192.0.2.1:0, label 16002, used-in-forwarding=Yes
peer 192.0.2.2:0, label 17002, used-in-forwarding=No peer 192.0.2.2:0, label 17002, used-in-forwarding=No
FEC 203.0.113.2/32: FEC 203.0.113.2/32:
. . . . . . . .
FEC 198.51.100.0/24: FEC 198.51.100.0/24:
. . . . . . . .
FEC 2001:db8:0:2:: FEC 2001:db8:0:2::
. . . . . . . .
FEC 2001:db8:0:3:: FEC 2001:db8:0:3::
. . . . . . . .
Address bindings: Address bindings:
Addr 192.0.2.10: Addr 192.0.2.10:
advertised advertised
Addr 2001:db8:0:10:: Addr 2001:db8:0:10::
advertised advertised
Addr 192.0.2.1:
received, peer 192.0.2.1:0
Addr 192.0.2.2:
received, peer 192.0.2.2:0
Addr 192.0.2.3:
received, peer 192.0.2.3:0
Addr 2001:db8:0:2::
received, peer 192.0.2.2:0
Addr 2001:db8:0:3::
received, peer 192.0.2.3:0
</artwork> Addr 192.0.2.1:
received, peer 192.0.2.1:0
Addr 192.0.2.2:
received, peer 192.0.2.2:0
Addr 192.0.2.3:
received, peer 192.0.2.3:0
Addr 2001:db8:0:2::
received, peer 192.0.2.2:0
Addr 2001:db8:0:3::
received, peer 192.0.2.3:0
</sourcecode>
</figure> </figure>
<t> Note that all local addresses are advertised to all peers and hen <t> Note that all local addresses are advertised to all peers;
ce no need to provide per-peer information for hence, there is no need to provide per-peer information for local add
local address advertisement. Furthermore, note that it is easy to der ress
ive a peer-centric view for the bindings from advertisement. Furthermore, note that it is easy to derive a
the information already provided in this model. peer-centric view for the bindings from the information already
provided in this model.
</t> </t>
<t> Following captures high level tree hierarchy for bindings state. <t>The following captures high-level tree hierarchy for bindings
The tree shown below is for ipv4 address-family only; a similar tree exists for state. The tree shown below is for ipv4 address-family only; a
ipv6 address-family as well. </t> similar tree exists for ipv6 address-family as well. </t>
<figure anchor="LDPBndgState"> <figure anchor="LDPBndgState">
<name>Bindings state</name> <name>Bindings State</name>
<artwork> <sourcecode type="yangtree">
+--rw mpls-ldp!
+--rw mpls-ldp! +--rw global
+--rw global +--rw address-families
+--rw address-families +--rw ipv4
+--rw ipv4 +--ro bindings
+--ro bindings +--ro address* [address]
+--ro address* [address] | +--ro address (ipv4-address or ipv6-address)
| +--ro address (ipv4-address or ipv6-address) | +--ro advertisement-type? advertised-received
| +--ro advertisement-type? advertised-received | +--ro peer? leafref
| +--ro peer? leafref +--ro fec-label* [fec]
+--ro fec-label* [fec] +--ro fec (ipv4-prefix or ipv6-prefix)
+--ro fec (ipv4-prefix or ipv6-prefix) +--ro peer* [peer advertisement-type]
+--ro peer* [peer advertisement-type] +--ro peer leafref
+--ro peer leafref +--ro advertisement-type? advertised-received
+--ro advertisement-type? advertised-received +--ro label? mpls:mpls-label
+--ro label? mpls:mpls-label +--ro used-in-forwarding? boolean
+--ro used-in-forwarding? boolean </sourcecode>
</figure>
</artwork>
</figure>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Capabilities state</name> <name>Capabilities State</name>
<t> LDP capabilities state comprise two types of information - global <t> LDP capabilities state comprises two types of information:
information (such as timer etc.), and global information (such as timer, etc.) and per-peer
per-peer information. </t> information. </t>
<t> Following captures high level tree hierarchy for LDP capabilities state. </t> <t>The following captures high-level tree hierarchy for LDP capabilit ies state. </t>
<figure anchor="LDPCapState"> <figure anchor="LDPCapState">
<name>Capabilities state</name> <name>Capabilities State</name>
<artwork> <sourcecode type="yangtree">
+--rw mpls-ldp! +--rw mpls-ldp!
+--rw peers +--rw peers
+--rw peer* [lsr-id label-space-id] +--rw peer* [lsr-id label-space-id]
+--rw lsr-id yang:dotted-quad +--rw lsr-id yang:dotted-quad
+--rw label-space-id +--rw label-space-id
+--ro received-peer-state +--ro received-peer-state
+--ro capability +--ro capability
+--ro . . . . +--ro . . . .
+--ro . . . . +--ro . . . .
</sourcecode>
</artwork>
</figure> </figure>
</section> </section>
</section> </section>
<section anchor="section_ldp_notif" numbered="true" toc="default"> <section anchor="section_ldp_notif" numbered="true" toc="default">
<name>Notifications</name> <name>Notifications</name>
<t> This model defines a list of notifications to inform client of import <t> This model defines a list of notifications to inform the client of
ant events detected during the protocol operation. important events detected during the protocol operation. These events
These events include events related to changes in the operational state o include events related to changes in the operational state of an LDP
f an LDP peer, hello adjacency, and FEC etc. It is peer, Hello adjacency, and FEC, etc. It is to be noted that an LDP FEC
to be noted that an LDP FEC is treated as operational (up) as long as it is treated as operational (up) as long as it has at least one Next Hop
has at least 1 NHLFE (Next Hop Label Forwarding Entry) with outgoing label. </t> Label Forwarding Entry (NHLFE) with an outgoing label. </t>
<t> A simplified graphical representation of the data model for LDP notif ications is shown in <xref target="ConsolidatedTree"/>. </t> <t> A simplified graphical representation of the data model for LDP notif ications is shown in <xref target="ConsolidatedTree"/>. </t>
</section> </section>
<section anchor="section_ldp_action" numbered="true" toc="default"> <section anchor="section_ldp_action" numbered="true" toc="default">
<name>Action</name> <name>Action</name>
<t> This model defines a list of rpcs that allow performing an action or <t> This model defines a list of rpcs that allow performing an action
executing a command on the protocol. For example, or executing a command on the protocol. For example, it allows for the
it allows to clear (reset) LDP peers, hello-adjacencies, and statistics. clearing (resetting) of LDP peers, hello-adjacencies, and
The model makes an effort to provide different statistics. The model makes an effort to provide a different level of
level of control so that a user is able to either clear all, or clear all control so that a user is able to either clear all, clear all for a
for a given type, or clear a specific entity. </t> given type, or clear a specific entity. </t>
<t> A simplified graphical representation of the data model for LDP actio ns is shown in <xref target="ConsolidatedTree"/>. </t> <t> A simplified graphical representation of the data model for LDP actio ns is shown in <xref target="ConsolidatedTree"/>. </t>
</section> </section>
<section anchor="YANG" numbered="true" toc="default"> <section anchor="YANG" numbered="true" toc="default">
<name>YANG Specification</name> <name>YANG Specification</name>
<t> Following sections specify the actual YANG (module) specification <t>The following sections specify the actual YANG (module) specification
for LDP constructs defined earlier in the document. </t> for LDP constructs defined earlier in the document. </t>
<section anchor="base_yang" numbered="true" toc="default"> <section anchor="base_yang" numbered="true" toc="default">
<name>Base</name> <name>Base</name>
<t> <t>
This YANG module imports types defined in <xref target="RFC6991"/>, This YANG module imports types defined in <xref
<xref target="RFC8349"/>, <xref target="RFC8294"/>, target="RFC6991"/>, <xref target="RFC8177"/>, <xref
<xref target="RFC8343"/>, and <xref target="RFC8344"/>. target="RFC8294"/>, <xref target="RFC8343"/>, <xref
target="RFC8344"/>, <xref target="RFC8349"/>, and <xref
target="RFC9067"/>.
</t> </t>
<figure anchor="BASE-YANG-FILE"> <figure anchor="BASE-YANG-FILE">
<name>LDP base module</name> <name>LDP Base Module</name>
<artwork>
<![CDATA[
<CODE BEGINS> file "ietf-mpls-ldp@2020-02-25.yang"
// RFC Editor: replace the above date 2020-02-25 with the date of
// publication and remove this note.
<sourcecode name="ietf-mpls-ldp@2022-03-07.yang" type="yang" markers="t rue"><![CDATA[
module ietf-mpls-ldp { module ietf-mpls-ldp {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-ldp"; namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-ldp";
prefix "ldp"; prefix ldp;
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix inet;
reference "RFC 6991: Common YANG Data Types"; reference
"RFC 6991: Common YANG Data Types";
} }
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix yang;
reference "RFC 6991: Common YANG Data Types"; reference
"RFC 6991: Common YANG Data Types";
} }
import ietf-routing { import ietf-routing {
prefix "rt"; prefix rt;
reference reference
"RFC 8349: A YANG Data Model for Routing Management (NMDA "RFC 8349: A YANG Data Model for Routing Management (NMDA
version)"; version)";
} }
import ietf-routing-types { import ietf-routing-types {
prefix "rt-types"; prefix rt-types;
reference reference
"RFC 8294: Common YANG Data Types for the Routing Area"; "RFC 8294: Common YANG Data Types for the Routing Area";
} }
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix if;
reference "RFC 8343: A YANG Data Model for Interface Management"; reference
"RFC 8343: A YANG Data Model for Interface Management";
} }
import ietf-ip { import ietf-ip {
prefix "ip"; prefix ip;
reference "RFC 7277: A YANG Data Model for IP Management"; reference
"RFC 8344: A YANG Data Model for IP Management";
} }
import ietf-key-chain { import ietf-key-chain {
prefix "key-chain"; prefix key-chain;
reference "RFC 8177: YANG Data Model for Key Chains"; reference
"RFC 8177: YANG Data Model for Key Chains";
} }
organization organization
"IETF MPLS Working Group"; "IETF MPLS Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/mpls/> "WG Web: <https://datatracker.ietf.org/wg/mpls/>
WG List: <mailto:mpls@ietf.org> WG List: <mailto:mpls@ietf.org>
Editor: Kamran Raza Editor: Kamran Raza
<mailto:skraza@cisco.com> <mailto:skraza@cisco.com>
Editor: Rajiv Asati Author: Rajiv Asati
<mailto:rajiva@cisco.com> <mailto:rajiva@cisco.com>
Editor: Xufeng Liu Author: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com> <mailto:xufeng.liu.ietf@gmail.com>
Editor: Santosh Esale Author: Santosh Easale
<mailto:sesale@juniper.net> <mailto:santosh_easale@berkeley.edu>
Editor: Xia Chen Author: Xia Chen
<mailto:jescia.chenxia@huawei.com> <mailto:jescia.chenxia@huawei.com>
Editor: Himanshu Shah Author: Himanshu Shah
<mailto:hshah@ciena.com>"; <mailto:hshah@ciena.com>";
description description
"This YANG module defines the essential components for the "This YANG module defines the essential components for the
management of Multi-Protocol Label Switching (MPLS) Label management of Multiprotocol Label Switching (MPLS) Label
Distribution Protocol (LDP). It is also the base model to Distribution Protocol (LDP). It is also the base model to
be augmented for Multipoint LDP (mLDP). be augmented for Multipoint LDP (mLDP).
Copyright (c) 2020 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons 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 to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License 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
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC 9070; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
// RFC Editor: replace XXXX with actual RFC number and remove revision 2022-03-7 {
// this note
revision 2020-02-25 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: YANG Data Model for MPLS LDP."; "RFC 9070: YANG Data Model for MPLS LDP";
// RFC Editor: replace XXXX with actual RFC number and remove
// this note
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef advertised-received { typedef advertised-received {
type enumeration { type enumeration {
enum advertised { enum advertised {
description "Advertised information."; description
"Advertised information.";
} }
enum received { enum received {
description "Received information."; description
"Received information.";
} }
} }
description description
"Received or advertised."; "Received or advertised.";
} }
typedef downstream-upstream { typedef downstream-upstream {
type enumeration { type enumeration {
enum downstream { enum downstream {
description "Downstream information."; description
"Downstream information.";
} }
enum upstream { enum upstream {
description "Upstream information."; description
"Upstream information.";
} }
} }
description description
"Downstream or upstream."; "Downstream or upstream.";
} }
typedef label-adv-mode { typedef label-adv-mode {
type enumeration { type enumeration {
enum downstream-unsolicited { enum downstream-unsolicited {
description "Downstream Unsolicited."; description
"Downstream Unsolicited.";
} }
enum downstream-on-demand { enum downstream-on-demand {
description "Downstream on Demand."; description
"Downstream on Demand.";
} }
} }
description description
"Label Advertisement Mode."; "Label Advertisement Mode.";
} }
typedef oper-status-event-type { typedef oper-status-event-type {
type enumeration { type enumeration {
enum up { enum up {
value 1; value 1;
description description
"Operational status changed to up."; "Operational status changed to up.";
} }
enum down { enum down {
value 2; value 2;
description description
"Operational status changed to down."; "Operational status changed to down.";
} }
} }
description "Operational status event type for notifications."; description
"Operational status event type for notifications.";
} }
/* /*
* Identities * Identities
*/ */
identity mpls-ldp { identity mpls-ldp {
base rt:control-plane-protocol; base rt:control-plane-protocol;
description description
"LDP protocol."; "LDP protocol.";
reference reference
"RFC 5036: LDP Specification"; "RFC 5036: LDP Specification";
} }
identity adjacency-flag-base { identity adjacency-flag-base {
description "Base type for adjacency flags."; description
"Base type for adjacency flags.";
} }
identity adjacency-flag-active { identity adjacency-flag-active {
base adjacency-flag-base; base adjacency-flag-base;
description description
"This adjacency is configured and actively created."; "This adjacency is configured and actively created.";
} }
identity adjacency-flag-passive { identity adjacency-flag-passive {
base adjacency-flag-base; base adjacency-flag-base;
skipping to change at line 1487 skipping to change at line 1554
"This adjacency is not configured and passively accepted."; "This adjacency is not configured and passively accepted.";
} }
/* /*
* Groupings * Groupings
*/ */
grouping adjacency-state-attributes { grouping adjacency-state-attributes {
description description
"The operational state attributes of an LDP Hello adjacency, "The operational state attributes of an LDP Hello adjacency,
which can used for basic and extended discoveris, in IPv4 and which can used for basic and extended discoveries, in IPv4 and
IPv6 address families."; IPv6 address families.";
leaf-list flag { leaf-list flag {
type identityref { type identityref {
base adjacency-flag-base; base adjacency-flag-base;
} }
description description
"On or more flags to indicate whether the adjacency is "One or more flags to indicate whether the adjacency is
actively created, passively accepted, or both."; actively created, passively accepted, or both.";
} }
container hello-holdtime { container hello-holdtime {
description description
"Containing Hello holdtime state information."; "Containing Hello holdtime state information.";
leaf adjacent { leaf adjacent {
type uint16; type uint16;
units seconds; units "seconds";
description description
"The holdtime value learned from the adjacent LSR."; "The holdtime value learned from the adjacent LSR.";
} }
leaf negotiated { leaf negotiated {
type uint16; type uint16;
units seconds; units "seconds";
description description
"The holdtime negotiated between this LSR and the adjacent "The holdtime negotiated between this LSR and the adjacent
LSR."; LSR.";
} }
leaf remaining { leaf remaining {
type uint16; type uint16;
units seconds; units "seconds";
description description
"The time remaining until the holdtime timer expires."; "The time remaining until the holdtime timer expires.";
} }
} }
leaf next-hello { leaf next-hello {
type uint16; type uint16;
units seconds; units "seconds";
description description
"The time when the next Hello message will be sent."; "The time when the next Hello message will be sent.";
} }
container statistics { container statistics {
description description
"Statistics objects."; "Statistics objects.";
leaf discontinuity-time { leaf discontinuity-time {
type yang:date-and-time; type yang:date-and-time;
mandatory true; mandatory true;
description description
"The time on the most recent occasion at which any one or "The time on the most recent occasion at which any one or
more of this interface's counters suffered a more of this interface's counters suffered a
discontinuity. If no such discontinuities have occurred discontinuity. If no such discontinuities have occurred
since the last re-initialization of the local management since the last re-initialization of the local management
subsystem, then this node contains the time the local subsystem, then this node contains the time the local
management subsystem re-initialized itself."; management subsystem re-initialized itself.";
skipping to change at line 1562 skipping to change at line 1624
description description
"The number of Hello messages dropped."; "The number of Hello messages dropped.";
} }
} // statistics } // statistics
} // adjacency-state-attributes } // adjacency-state-attributes
grouping basic-discovery-timers { grouping basic-discovery-timers {
description description
"The timer attributes for basic discovery, used in the "The timer attributes for basic discovery, used in the
per-interface setting and in the all-interface setting."; per-interface setting and in the all-interface setting.";
leaf hello-holdtime { leaf hello-holdtime {
type uint16 { type uint16 {
range 15..3600; range "15..3600";
} }
units seconds; units "seconds";
description description
"The time interval for which a LDP link Hello adjacency "The time interval for which an LDP link Hello adjacency
is maintained in the absence of link Hello messages from is maintained in the absence of link Hello messages from
the LDP neighbor. the LDP neighbor.
This leaf may be configured at the per-interface level or This leaf may be configured at the per-interface level or
the global level, with precedence given to the value at the the global level, with precedence given to the value at the
per-interface level. If the leaf is not configured at per-interface level. If the leaf is not configured at
either level, the default value at the global level is either level, the default value at the global level is
used."; used.";
} }
leaf hello-interval { leaf hello-interval {
type uint16 { type uint16 {
range 5..1200; range "5..1200";
} }
units seconds; units "seconds";
description description
"The interval between consecutive LDP link Hello messages "The interval between consecutive LDP link Hello messages
used in basic LDP discovery. used in basic LDP discovery.
This leaf may be configured at the per-interface level or This leaf may be configured at the per-interface level or
the global level, with precedence given to the value at the the global level, with precedence given to the value at the
per-interface level. If the leaf is not configured at per-interface level. If the leaf is not configured at
either level, the default value at the global level is either level, the default value at the global level is
used."; used.";
} }
} // basic-discovery-timers } // basic-discovery-timers
skipping to change at line 1598 skipping to change at line 1659
per-interface level. If the leaf is not configured at per-interface level. If the leaf is not configured at
either level, the default value at the global level is either level, the default value at the global level is
used."; used.";
} }
} // basic-discovery-timers } // basic-discovery-timers
grouping binding-address-state-attributes { grouping binding-address-state-attributes {
description description
"Operational state attributes of an address binding, used in "Operational state attributes of an address binding, used in
IPv4 and IPv6 address families."; IPv4 and IPv6 address families.";
leaf advertisement-type { leaf advertisement-type {
type advertised-received; type advertised-received;
description description
"Received or advertised."; "Received or advertised.";
} }
container peer { container peer {
when "../advertisement-type = 'received'" { when "../advertisement-type = 'received'" {
description description
"Applicable for received address."; "Applicable for received address.";
} }
description description
"LDP peer from which this address is received."; "LDP peer from which this address is received.";
uses ldp-peer-ref-from-binding; uses ldp-peer-ref-from-binding;
} }
} // binding-address-state-attributes } // binding-address-state-attributes
grouping binding-label-state-attributes { grouping binding-label-state-attributes {
description description
"Operational state attributes for a FEC-label binding, used in "Operational state attributes for a FEC-Label binding, used in
IPv4 and IPv6 address families."; IPv4 and IPv6 address families.";
list peer { list peer {
key "lsr-id label-space-id advertisement-type"; key "lsr-id label-space-id advertisement-type";
description description
"List of advertised and received peers."; "List of advertised and received peers.";
uses ldp-peer-ref-from-binding { uses ldp-peer-ref-from-binding {
description description
"The LDP peer from which this binding is received, or to "The LDP peer from which this binding is received, or to
which this binding is advertised. which this binding is advertised.
The peer is identified by its LDP ID, which consists of The peer is identified by its LDP ID, which consists of
the LSR ID and the Label Space ID."; the LSR Id and the label space Id.";
} }
leaf advertisement-type { leaf advertisement-type {
type advertised-received; type advertised-received;
description description
"Received or advertised."; "Received or advertised.";
} }
leaf label { leaf label {
type rt-types:mpls-label; type rt-types:mpls-label;
description description
"Advertised (outbound) or received (inbound) "Advertised (outbound) or received (inbound)
skipping to change at line 1652 skipping to change at line 1711
leaf used-in-forwarding { leaf used-in-forwarding {
type boolean; type boolean;
description description
"'true' if the label is used in forwarding."; "'true' if the label is used in forwarding.";
} }
} // peer } // peer
} // binding-label-state-attributes } // binding-label-state-attributes
grouping graceful-restart-attributes-per-peer { grouping graceful-restart-attributes-per-peer {
description description
"Per peer graceful restart attributes. "Per-peer graceful restart attributes.
On the local side, these attributes are configuration and On the local side, these attributes are configuration and
operational state data. One the peer side, these attributes operational state data. On the peer side, these attributes
are operational state data received from the peer."; are operational state data received from the peer.";
container graceful-restart { container graceful-restart {
description description
"Attributes for graceful restart."; "Attributes for graceful restart.";
leaf enabled { leaf enabled {
type boolean; type boolean;
description description
"Enable or disable graceful restart. "Enable or disable graceful restart.
This leaf may be configured at the per-peer level or the This leaf may be configured at the per-peer level or the
global level, with precedence given to the value at the global level, with precedence given to the value at the
per-peer level. If the leaf is not configured at either per-peer level. If the leaf is not configured at either
level, the default value at the global level is used."; level, the default value at the global level is used.";
} }
leaf reconnect-time { leaf reconnect-time {
type uint16 { type uint16 {
range 10..1800; range "10..1800";
} }
units seconds; units "seconds";
description description
"Specifies the time interval that the remote LDP peer "Specifies the time interval that the remote LDP peer
must wait for the local LDP peer to reconnect after the must wait for the local LDP peer to reconnect after the
remote peer detects the LDP communication failure. remote peer detects the LDP communication failure.
This leaf may be configured at the per-peer level or the This leaf may be configured at the per-peer level or the
global level, with precedence given to the value at the global level, with precedence given to the value at the
per-peer level. If the leaf is not configured at either per-peer level. If the leaf is not configured at either
level, the default value at the global level is used."; level, the default value at the global level is used.";
} }
leaf recovery-time { leaf recovery-time {
type uint16 { type uint16 {
range 30..3600; range "30..3600";
} }
units seconds; units "seconds";
description description
"Specifies the time interval, in seconds, that the remote "Specifies the time interval, in seconds, that the remote
LDP peer preserves its MPLS forwarding state after LDP peer preserves its MPLS forwarding state after
receiving the Initialization message from the restarted receiving the Initialization message from the restarted
local LDP peer. local LDP peer.
This leaf may be configured at the per-peer level or the This leaf may be configured at the per-peer level or the
global level, with precedence given to the value at the global level, with precedence given to the value at the
per-peer level. If the leaf is not configured at either per-peer level. If the leaf is not configured at either
level, the default value at the global level is used."; level, the default value at the global level is used.";
} }
} // graceful-restart } // graceful-restart
} // graceful-restart-attributes-per-peer } // graceful-restart-attributes-per-peer
grouping ldp-interface-ref { grouping ldp-interface-ref {
description description
"Defining a reference to LDP interface."; "Defining a reference to an LDP interface.";
leaf name { leaf name {
type if:interface-ref; type if:interface-ref;
must "(/if:interfaces/if:interface[if:name=current()]/ip:ipv4)" must '(/if:interfaces/if:interface[if:name=current()]/ip:ipv4)'
+ " or " + ' or '
+ "(/if:interfaces/if:interface[if:name=current()]/ip:ipv6)" + '(/if:interfaces/if:interface[if:name=current()]/ip:ipv6)'
{ {
description "Interface is IPv4 or IPv6."; description
"Interface is IPv4 or IPv6.";
} }
description description
"The name of an LDP interface."; "The name of an LDP interface.";
} }
} }
grouping ldp-peer-ref-absolute { grouping ldp-peer-ref-absolute {
description description
"An absolute reference to an LDP peer, by the LDP ID, which "An absolute reference to an LDP peer, by the LDP ID, which
consists of the LSR ID and the Label Space ID."; consists of the LSR Id and the label space Id.";
leaf protocol-name { leaf protocol-name {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rt:name"; + "rt:control-plane-protocol/rt:name";
} }
description description
"The name of the LDP protocol instance."; "The name of the LDP protocol instance.";
} }
leaf lsr-id { leaf lsr-id {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol" + "rt:control-plane-protocol"
+ "[rt:name=current()/../protocol-name]/" + "[rt:name=current()/../protocol-name]/"
+ "ldp:mpls-ldp/ldp:peers/ldp:peer/ldp:lsr-id"; + "ldp:mpls-ldp/ldp:peers/ldp:peer/ldp:lsr-id";
} }
description description
"The LSR ID of the peer, as a portion of the peer LDP ID."; "The LSR Id of the peer, as a portion of the peer LDP ID.";
} }
leaf label-space-id { leaf label-space-id {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol" + "rt:control-plane-protocol"
+ "[rt:name=current()/../protocol-name]/" + "[rt:name=current()/../protocol-name]/"
+ "ldp:mpls-ldp/ldp:peers/" + "ldp:mpls-ldp/ldp:peers/"
+ "ldp:peer[ldp:lsr-id=current()/../lsr-id]/" + "ldp:peer[ldp:lsr-id=current()/../lsr-id]/"
+ "ldp:label-space-id"; + "ldp:label-space-id";
} }
description description
"The Label Space ID of the peer, as a portion of the peer "The label space Id of the peer, as a portion of the peer
LDP ID."; LDP ID.";
} }
} // ldp-peer-ref-absolute } // ldp-peer-ref-absolute
grouping ldp-peer-ref-from-binding { grouping ldp-peer-ref-from-binding {
description description
"A relative reference to an LDP peer, by the LDP ID, which "A relative reference to an LDP peer, by the LDP ID, which
consists of the LSR ID and the Label Space ID."; consists of the LSR Id and the label space Id.";
leaf lsr-id { leaf lsr-id {
type leafref { type leafref {
path "../../../../../../../ldp:peers/ldp:peer/ldp:lsr-id"; path "../../../../../../../ldp:peers/ldp:peer/ldp:lsr-id";
} }
description description
"The LSR ID of the peer, as a portion of the peer LDP ID."; "The LSR Id of the peer, as a portion of the peer LDP ID.";
} }
leaf label-space-id { leaf label-space-id {
type leafref { type leafref {
path "../../../../../../../ldp:peers/" path "../../../../../../../ldp:peers/"
+ "ldp:peer[ldp:lsr-id=current()/../lsr-id]/" + "ldp:peer[ldp:lsr-id=current()/../lsr-id]/"
+ "ldp:label-space-id"; + "ldp:label-space-id";
} }
description description
"The Label Space ID of the peer, as a portion of the peer "The label space Id of the peer, as a portion of the peer
LDP ID."; LDP ID.";
} }
} // ldp-peer-ref-from-binding } // ldp-peer-ref-from-binding
grouping ldp-peer-ref-from-interface { grouping ldp-peer-ref-from-interface {
description description
"A relative reference to an LDP peer, by the LDP ID, which "A relative reference to an LDP peer, by the LDP ID, which
consists of the LSR ID and the Label Space ID."; consists of the LSR Id and the label space Id.";
container peer { container peer {
description description
"Reference to an LDP peer, by the LDP ID, which consists of "Reference to an LDP peer, by the LDP ID, which consists of
the LSR ID and the Label Space ID."; the LSR Id and the label space Id.";
leaf lsr-id { leaf lsr-id {
type leafref { type leafref {
path "../../../../../../../../../ldp:peers/ldp:peer/" path "../../../../../../../../../ldp:peers/ldp:peer/"
+ "ldp:lsr-id"; + "ldp:lsr-id";
} }
description description
"The LSR ID of the peer, as a portion of the peer LDP ID."; "The LSR Id of the peer, as a portion of the peer LDP ID.";
} }
leaf label-space-id { leaf label-space-id {
type leafref { type leafref {
path "../../../../../../../../../ldp:peers/" path "../../../../../../../../../ldp:peers/"
+ "ldp:peer[ldp:lsr-id=current()/../lsr-id]/" + "ldp:peer[ldp:lsr-id=current()/../lsr-id]/"
+ "ldp:label-space-id"; + "ldp:label-space-id";
} }
description description
"The Label Space ID of the peer, as a portion of the peer "The label space Id of the peer, as a portion of the peer
LDP ID."; LDP ID.";
} }
} // peer } // peer
} // ldp-peer-ref-from-interface } // ldp-peer-ref-from-interface
grouping ldp-peer-ref-from-target { grouping ldp-peer-ref-from-target {
description description
"A relative reference to an LDP peer, by the LDP ID, which "A relative reference to an LDP peer, by the LDP ID, which
consists of the LSR ID and the Label Space ID."; consists of the LSR Id and the label space Id.";
container peer { container peer {
description description
"Reference to an LDP peer, by the LDP ID, which consists of "Reference to an LDP peer, by the LDP ID, which consists of
the LSR ID and the Label Space ID."; the LSR Id and the label space Id.";
leaf lsr-id { leaf lsr-id {
type leafref { type leafref {
path "../../../../../../../../ldp:peers/ldp:peer/" path "../../../../../../../../ldp:peers/ldp:peer/"
+ "ldp:lsr-id"; + "ldp:lsr-id";
} }
description description
"The LSR ID of the peer, as a portion of the peer LDP ID."; "The LSR Id of the peer, as a portion of the peer LDP ID.";
} }
leaf label-space-id { leaf label-space-id {
type leafref { type leafref {
path "../../../../../../../../ldp:peers/" path "../../../../../../../../ldp:peers/"
+ "ldp:peer[ldp:lsr-id=current()/../lsr-id]/" + "ldp:peer[ldp:lsr-id=current()/../lsr-id]/"
+ "ldp:label-space-id"; + "ldp:label-space-id";
} }
description description
"The Label Space ID of the peer, as a portion of the peer "The label space Id of the peer, as a portion of the peer
LDP ID."; LDP ID.";
} }
} // peer } // peer
} // ldp-peer-ref-from-target } // ldp-peer-ref-from-target
grouping peer-attributes { grouping peer-attributes {
description description
"Peer configuration attributes, used in the per-peer setting "Peer configuration attributes, used in the per-peer setting
can in the all-peer setting."; can in the all-peer setting.";
leaf session-ka-holdtime { leaf session-ka-holdtime {
type uint16 { type uint16 {
range 45..3600; range "45..3600";
} }
units seconds; units "seconds";
description description
"The time interval after which an inactive LDP session "The time interval after which an inactive LDP session
terminates and the corresponding TCP session closes. terminates and the corresponding TCP session closes.
Inactivity is defined as not receiving LDP packets from the Inactivity is defined as not receiving LDP packets from the
peer. peer.
This leaf may be configured at the per-peer level or the This leaf may be configured at the per-peer level or the
global level, with precedence given to the value at the global level, with precedence given to the value at the
per-peer level. If the leaf is not configured at either per-peer level. If the leaf is not configured at either
level, the default value at the global level is used."; level, the default value at the global level is used.";
} }
leaf session-ka-interval { leaf session-ka-interval {
type uint16 { type uint16 {
range 15..1200; range "15..1200";
} }
units seconds; units "seconds";
description description
"The interval between successive transmissions of keepalive "The interval between successive transmissions of KeepAlive
packets. Keepalive packets are only sent in the absence of packets. Keepalive packets are only sent in the absence of
other LDP packets transmitted over the LDP session. other LDP packets transmitted over the LDP session.
This leaf may be configured at the per-peer level or the This leaf may be configured at the per-peer level or the
global level, with precedence given to the value at the global level, with precedence given to the value at the
per-peer level. If the leaf is not configured at either per-peer level. If the leaf is not configured at either
level, the default value at the global level is used."; level, the default value at the global level is used.";
} }
} // peer-attributes } // peer-attributes
grouping peer-authentication { grouping peer-authentication {
description description
skipping to change at line 1880 skipping to change at line 1933
global level, with precedence given to the value at the global level, with precedence given to the value at the
per-peer level. If the leaf is not configured at either per-peer level. If the leaf is not configured at either
level, the default value at the global level is used."; level, the default value at the global level is used.";
} }
} // peer-attributes } // peer-attributes
grouping peer-authentication { grouping peer-authentication {
description description
"Peer authentication container, used in the per-peer setting "Peer authentication container, used in the per-peer setting
can in the all-peer setting."; can in the all-peer setting.";
container authentication { container authentication {
description description
"Containing authentication information."; "Containing authentication information.";
choice authentication-type { choice authentication-type {
description description
"Choice of authentication."; "Choice of authentication.";
case password { case password {
leaf key { leaf key {
type string; type string;
description description
"This leaf specifies the authentication key. The length "This leaf specifies the authentication key. The
of the key may be dependent on the cryptographic length of the key may be dependent on the
algorithm."; cryptographic algorithm.";
} }
leaf crypto-algorithm { leaf crypto-algorithm {
type identityref { type identityref {
base key-chain:crypto-algorithm; base key-chain:crypto-algorithm;
} }
description description
"Cryptographic algorithm associated with key."; "Cryptographic algorithm associated with key.";
} }
} }
} }
} }
} // peer-authentication } // peer-authentication
grouping peer-state-derived { grouping peer-state-derived {
description description
"The peer state information derived from the LDP protocol "The peer state information derived from the LDP protocol
operations."; operations.";
container label-advertisement-mode { container label-advertisement-mode {
config false; config false;
description "Label advertisement mode state."; description
"Label advertisement mode state.";
leaf local { leaf local {
type label-adv-mode; type label-adv-mode;
description description
"Local Label Advertisement Mode."; "Local Label Advertisement Mode.";
} }
leaf peer { leaf peer {
type label-adv-mode; type label-adv-mode;
description description
"Peer Label Advertisement Mode."; "Peer Label Advertisement Mode.";
} }
leaf negotiated { leaf negotiated {
type label-adv-mode; type label-adv-mode;
description description
"Negotiated Label Advertisement Mode."; "Negotiated Label Advertisement Mode.";
} }
} }
leaf next-keep-alive { leaf next-keep-alive {
type uint16; type uint16;
units seconds; units "seconds";
config false; config false;
description description
"Time duration from now until sending the next KeepAlive "Time duration from now until sending the next KeepAlive
message."; message.";
} }
container received-peer-state { container received-peer-state {
config false; config false;
description description
"Operational state information learned from the peer."; "Operational state information learned from the peer.";
uses graceful-restart-attributes-per-peer; uses graceful-restart-attributes-per-peer;
container capability { container capability {
description "Peer capability information."; description
"Peer capability information.";
container end-of-lib { container end-of-lib {
description description
"Peer's end-of-lib capability."; "Peer's end-of-lib capability.";
leaf enabled { leaf enabled {
type boolean; type boolean;
description description
"'true' if peer's end-of-lib capability is enabled."; "'true' if peer's end-of-lib capability is enabled.";
} }
} }
container typed-wildcard-fec { container typed-wildcard-fec {
skipping to change at line 1980 skipping to change at line 2030
"Peer's upstream label assignment capability."; "Peer's upstream label assignment capability.";
leaf enabled { leaf enabled {
type boolean; type boolean;
description description
"'true' if peer's upstream label assignment is "'true' if peer's upstream label assignment is
enabled."; enabled.";
} }
} }
} // capability } // capability
} // received-peer-state } // received-peer-state
container session-holdtime { container session-holdtime {
config false; config false;
description "Session holdtime state."; description
"Session holdtime state.";
leaf peer { leaf peer {
type uint16; type uint16;
units seconds; units "seconds";
description "Peer holdtime."; description
"Peer holdtime.";
} }
leaf negotiated { leaf negotiated {
type uint16; type uint16;
units seconds; units "seconds";
description "Negotiated holdtime."; description
"Negotiated holdtime.";
} }
leaf remaining { leaf remaining {
type uint16; type uint16;
units seconds; units "seconds";
description "Remaining holdtime."; description
"Remaining holdtime.";
} }
} // session-holdtime } // session-holdtime
leaf session-state { leaf session-state {
type enumeration { type enumeration {
enum non-existent { enum non-existent {
description "NON EXISTENT state. Transport disconnected."; description
"NON EXISTENT state. Transport disconnected.";
} }
enum initialized { enum initialized {
description "INITIALIZED state."; description
"INITIALIZED state.";
} }
enum openrec { enum openrec {
description "OPENREC state."; description
"OPENREC state.";
} }
enum opensent { enum opensent {
description "OPENSENT state."; description
"OPENSENT state.";
} }
enum operational { enum operational {
description "OPERATIONAL state."; description
"OPERATIONAL state.";
} }
} }
config false; config false;
description description
"Representing the operational status of the LDP session."; "Representing the operational status of the LDP session.";
reference reference
"RFC5036, Sec. 2.5.4."; "RFC 5036: LDP Specification, Sec. 2.5.4.";
} }
container tcp-connection { container tcp-connection {
config false; config false;
description "TCP connection state."; description
"TCP connection state.";
leaf local-address { leaf local-address {
type inet:ip-address; type inet:ip-address;
description "Local address."; description
"Local address.";
} }
leaf local-port { leaf local-port {
type inet:port-number; type inet:port-number;
description "Local port number."; description
"Local port number.";
} }
leaf remote-address { leaf remote-address {
type inet:ip-address; type inet:ip-address;
description "Remote address."; description
"Remote address.";
} }
leaf remote-port { leaf remote-port {
type inet:port-number; type inet:port-number;
description "Remote port number."; description
"Remote port number.";
} }
} // tcp-connection } // tcp-connection
leaf up-time { leaf up-time {
type rt-types:timeticks64; type rt-types:timeticks64;
config false; config false;
description description
"The number of time ticks (hundredths of a second) since the "The number of time ticks (hundredths of a second) since the
the state of the session with the peer changed to state of the session with the peer changed to
OPERATIONAL."; OPERATIONAL.";
} }
container statistics { container statistics {
config false; config false;
description description
"Statistics objects."; "Statistics objects.";
leaf discontinuity-time { leaf discontinuity-time {
type yang:date-and-time; type yang:date-and-time;
mandatory true; mandatory true;
description description
"The time on the most recent occasion at which any one or "The time on the most recent occasion at which any one or
more of this interface's counters suffered a more of this interface's counters suffered a
discontinuity. If no such discontinuities have occurred discontinuity. If no such discontinuities have occurred
since the last re-initialization of the local management since the last re-initialization of the local management
subsystem, then this node contains the time the local subsystem, then this node contains the time the local
management subsystem re-initialized itself."; management subsystem re-initialized itself.";
skipping to change at line 2072 skipping to change at line 2130
type yang:date-and-time; type yang:date-and-time;
mandatory true; mandatory true;
description description
"The time on the most recent occasion at which any one or "The time on the most recent occasion at which any one or
more of this interface's counters suffered a more of this interface's counters suffered a
discontinuity. If no such discontinuities have occurred discontinuity. If no such discontinuities have occurred
since the last re-initialization of the local management since the last re-initialization of the local management
subsystem, then this node contains the time the local subsystem, then this node contains the time the local
management subsystem re-initialized itself."; management subsystem re-initialized itself.";
} }
container received { container received {
description "Inbound statistics."; description
"Inbound statistics.";
uses statistics-peer-received-sent; uses statistics-peer-received-sent;
} }
container sent { container sent {
description "Outbound statistics."; description
"Outbound statistics.";
uses statistics-peer-received-sent; uses statistics-peer-received-sent;
} }
leaf total-addresses { leaf total-addresses {
type uint32; type uint32;
description description
"The number of learned addresses."; "The number of learned addresses.";
} }
leaf total-labels { leaf total-labels {
type uint32; type uint32;
description description
"The number of learned labels."; "The number of learned labels.";
} }
skipping to change at line 2116 skipping to change at line 2174
"The total number of octets sent or received."; "The total number of octets sent or received.";
} }
leaf total-messages { leaf total-messages {
type yang:counter64; type yang:counter64;
description description
"The number of messages sent or received."; "The number of messages sent or received.";
} }
leaf address { leaf address {
type yang:counter64; type yang:counter64;
description description
"The number of address messages sent or received."; "The number of Address messages sent or received.";
} }
leaf address-withdraw { leaf address-withdraw {
type yang:counter64; type yang:counter64;
description description
"The number of address-withdraw messages sent or received."; "The number of address-withdraw messages sent or received.";
} }
leaf initialization { leaf initialization {
type yang:counter64; type yang:counter64;
description description
"The number of initialization messages sent or received."; "The number of Initialization messages sent or received.";
} }
leaf keepalive { leaf keepalive {
type yang:counter64; type yang:counter64;
description description
"The number of keepalive messages sent or received."; "The number of KeepAlive messages sent or received.";
} }
leaf label-abort-request { leaf label-abort-request {
type yang:counter64; type yang:counter64;
description description
"The number of label-abort-request messages sent or "The number of label-abort-request messages sent or
received."; received.";
} }
leaf label-mapping { leaf label-mapping {
type yang:counter64; type yang:counter64;
description description
skipping to change at line 2174 skipping to change at line 2232
} // statistics-peer-received-sent } // statistics-peer-received-sent
/* /*
* Configuration data and operational state data nodes * Configuration data and operational state data nodes
*/ */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol" { + "rt:control-plane-protocol" {
when "derived-from-or-self(rt:type, 'ldp:mpls-ldp')" { when "derived-from-or-self(rt:type, 'ldp:mpls-ldp')" {
description description
"This augmentation is only valid for a control-plane "This augmentation is only valid for a control plane
protocol instance of LDP (type 'mpls-ldp')."; protocol instance of LDP (type 'mpls-ldp').";
} }
description description
"LDP augmentation to routing control-plane protocol "LDP augmentation to routing control plane protocol
configuration and state."; configuration and state.";
container mpls-ldp { container mpls-ldp {
must "not (../../rt:control-plane-protocol" must "not (../../rt:control-plane-protocol"
+ "[derived-from-or-self(rt:type, 'ldp:mpls-ldp')]" + "[derived-from-or-self(rt:type, 'ldp:mpls-ldp')]"
+ "[rt:name!=current()/../rt:name])" + "[rt:name!=current()/../rt:name])" {
{ description
description "Only one LDP instance is allowed."; "Only one LDP instance is allowed.";
} }
description description
"Containing configuration and operational data for the LDP "Containing configuration and operational data for the LDP
protocol."; protocol.";
container global { container global {
description description
"Global attributes for LDP."; "Global attributes for LDP.";
container capability { container capability {
description description
"Containing the LDP capability data. The container is "Containing the LDP capability data. The container is
used for augmentations."; used for augmentations.";
reference reference
"RFC5036: Sec. 1.5."; "RFC 5036: LDP Specification, Sec. 1.5.";
} }
container graceful-restart { container graceful-restart {
description description
"Attributes for graceful restart."; "Attributes for graceful restart.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default false; default "false";
description description
"Enable or disable graceful restart."; "Enable or disable graceful restart.";
} }
leaf reconnect-time { leaf reconnect-time {
type uint16 { type uint16 {
range 10..1800; range "10..1800";
} }
units seconds; units "seconds";
default 120; default "120";
description description
"Specifies the time interval that the remote LDP peer "Specifies the time interval that the remote LDP peer
must wait for the local LDP peer to reconnect after must wait for the local LDP peer to reconnect after
the remote peer detects the LDP communication the remote peer detects the LDP communication
failure."; failure.";
} }
leaf recovery-time { leaf recovery-time {
type uint16 { type uint16 {
range 30..3600; range "30..3600";
} }
units seconds; units "seconds";
default 120; default "120";
description description
"Specifies the time interval, in seconds, that the "Specifies the time interval, in seconds, that the
remote LDP peer preserves its MPLS forwarding state remote LDP peer preserves its MPLS forwarding state
after receiving the Initialization message from the after receiving the Initialization message from the
restarted local LDP peer."; restarted local LDP peer.";
} }
leaf forwarding-holdtime { leaf forwarding-holdtime {
type uint16 { type uint16 {
range 30..3600; range "30..3600";
} }
units seconds; units "seconds";
default 180; default "180";
description description
"Specifies the time interval, in seconds, before the "Specifies the time interval, in seconds, before the
termination of the recovery phase."; termination of the recovery phase.";
} }
} // graceful-restart } // graceful-restart
leaf lsr-id { leaf lsr-id {
type rt-types:router-id; type rt-types:router-id;
description description
"Specify the value to act as the LDP LSR ID. "Specifies the value to act as the LDP LSR Id.
If this attribute is not specified, LDP uses the router If this attribute is not specified, LDP uses the router
ID as determined by the system."; ID as determined by the system.";
} }
container address-families { container address-families {
description description
"Per address family confgiration and operational state. "Per-address-family configuration and operational state.
The address family can be either IPv4 or IPv6."; The address family can be either IPv4 or IPv6.";
container ipv4 { container ipv4 {
presence presence "Present if IPv4 is enabled, unless the
"Present if IPv4 is enabled, unless the 'enabled' 'enabled' leaf is set to 'false'.";
leaf is set to 'false'";
description description
"Containing data related to the IPv4 address family."; "Containing data related to the IPv4 address family.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default true; default "true";
description description
"'false' to disable the address family."; "'false' to disable the address family.";
} }
leaf label-distribution-control-mode { leaf label-distribution-control-mode {
type enumeration { type enumeration {
enum independent { enum independent {
description description
"Independent label distribution control."; "Independent label distribution control.";
} }
enum ordered { enum ordered {
description description
"Ordered label distribution control."; "Ordered label distribution control.";
} }
} }
config false; config false;
description description
"Label distribution control mode."; "Label distribution control mode.";
reference reference
"RFC5036: LDP Specification. Sec 2.6."; "RFC 5036: LDP Specification, Sec. 2.6.";
} }
// ipv4 bindings // ipv4 bindings
container bindings { container bindings {
config false; config false;
description description
"LDP address and label binding information."; "LDP address and label binding information.";
list address { list address {
key "address"; key "address";
description description
"List of address bindings learned by LDP."; "List of address bindings learned by LDP.";
leaf address { leaf address {
skipping to change at line 2311 skipping to change at line 2358
description description
"List of address bindings learned by LDP."; "List of address bindings learned by LDP.";
leaf address { leaf address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"The IPv4 address learned from an Address "The IPv4 address learned from an Address
message received from or advertised to a peer."; message received from or advertised to a peer.";
} }
uses binding-address-state-attributes; uses binding-address-state-attributes;
} }
list fec-label { list fec-label {
key "fec"; key "fec";
description description
"List of FEC-label bindings learned by LDP."; "List of FEC-label bindings learned by LDP.";
leaf fec { leaf fec {
type inet:ipv4-prefix; type inet:ipv4-prefix;
description description
"The prefix FEC value in the FEC-label binding, "The prefix FEC value in the FEC-Label binding,
learned in a Label Mapping message received from learned in a Label Mapping message received from
or advertised to a peer."; or advertised to a peer.";
} }
uses binding-label-state-attributes; uses binding-label-state-attributes;
} }
} // bindings } // bindings
} // ipv4 } // ipv4
} // address-families } // address-families
} // global } // global
container discovery { container discovery {
description description
"Neighbor discovery configuration and operational state."; "Neighbor-discovery configuration and operational state.";
container interfaces { container interfaces {
description description
"A list of interfaces for LDP Basic Discovery."; "A list of interfaces for LDP Basic Discovery.";
reference reference
"RFC5036: LDP Specification. Sec 2.4.1."; "RFC 5036: LDP Specification, Sec. 2.4.1.";
uses basic-discovery-timers { uses basic-discovery-timers {
refine "hello-holdtime" { refine "hello-holdtime" {
default 15; default "15";
} }
refine "hello-interval" { refine "hello-interval" {
default 5; default "5";
} }
} }
list interface { list interface {
key "name"; key "name";
description description
"List of LDP interfaces used for LDP Basic Discovery."; "List of LDP interfaces used for LDP Basic Discovery.";
uses ldp-interface-ref; uses ldp-interface-ref;
leaf next-hello { leaf next-hello {
type uint16; type uint16;
units seconds; units "seconds";
config false; config false;
description "Time to send the next Hello message."; description
"Time to send the next Hello message.";
} }
container address-families { container address-families {
description description
"Container for address families."; "Container for address families.";
container ipv4 { container ipv4 {
presence presence "Present if IPv4 is enabled, unless the
"Present if IPv4 is enabled, unless the 'enabled' 'enabled' leaf is set to 'false'.";
leaf is set to 'false'";
description description
"IPv4 address family."; "IPv4 address family.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default true; default "true";
description description
"Set to false to disable the address family on "Set to false to disable the address family on
the interface."; the interface.";
} }
container hello-adjacencies { container hello-adjacencies {
config false; config false;
description description
"Containing a list of Hello adjacencies."; "Containing a list of Hello adjacencies.";
list hello-adjacency { list hello-adjacency {
key "adjacent-address"; key "adjacent-address";
config false; config false;
description "List of Hello adjacencies."; description
"List of Hello adjacencies.";
leaf adjacent-address { leaf adjacent-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Neighbor address of the Hello adjacency."; "Neighbor address of the Hello adjacency.";
} }
uses adjacency-state-attributes; uses adjacency-state-attributes;
uses ldp-peer-ref-from-interface; uses ldp-peer-ref-from-interface;
} }
} }
} // ipv4 } // ipv4
} // address-families } // address-families
} // interface } // interface
} // interfaces } // interfaces
container targeted {
container targeted
{
description description
"A list of targeted neighbors for extended discovery."; "A list of targeted neighbors for extended discovery.";
leaf hello-holdtime { leaf hello-holdtime {
type uint16 { type uint16 {
range 15..3600; range "15..3600";
} }
units seconds; units "seconds";
default 45; default "45";
description description
"The time interval for which LDP targeted Hello "The time interval for which an LDP targeted Hello
adjacency is maintained in the absence of targeted adjacency is maintained in the absence of targeted
Hello messages from an LDP neighbor."; Hello messages from an LDP neighbor.";
} }
leaf hello-interval { leaf hello-interval {
type uint16 { type uint16 {
range 5..3600; range "5..3600";
} }
units seconds; units "seconds";
default 15; default "15";
description description
"The interval between consecutive LDP targeted Hello "The interval between consecutive LDP targeted Hello
messages used in extended LDP discovery."; messages used in extended LDP discovery.";
} }
container hello-accept { container hello-accept {
description description
"LDP policy to control the acceptance of extended "LDP policy to control the acceptance of extended
neighbor discovery Hello messages."; neighbor-discovery Hello messages.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default false; default "false";
description description
"'true' to accept; 'false' to deny."; "'true' to accept; 'false' to deny.";
} }
} }
container address-families { container address-families {
description description
"Container for address families."; "Container for address families.";
container ipv4 { container ipv4 {
presence presence "Present if IPv4 is enabled.";
"Present if IPv4 is enabled.";
description description
"IPv4 address family."; "IPv4 address family.";
container hello-adjacencies { container hello-adjacencies {
config false; config false;
description description
"Containing a list of Hello adjacencies."; "Containing a list of Hello adjacencies.";
list hello-adjacency { list hello-adjacency {
key "local-address adjacent-address"; key "local-address adjacent-address";
description "List of Hello adjacencies."; description
"List of Hello adjacencies.";
leaf local-address { leaf local-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Local address of the Hello adjacency."; "Local address of the Hello adjacency.";
} }
leaf adjacent-address { leaf adjacent-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Neighbor address of the Hello adjacency."; "Neighbor address of the Hello adjacency.";
} }
skipping to change at line 2472 skipping to change at line 2500
leaf local-address { leaf local-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Local address of the Hello adjacency."; "Local address of the Hello adjacency.";
} }
leaf adjacent-address { leaf adjacent-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Neighbor address of the Hello adjacency."; "Neighbor address of the Hello adjacency.";
} }
uses adjacency-state-attributes; uses adjacency-state-attributes;
uses ldp-peer-ref-from-target; uses ldp-peer-ref-from-target;
} }
} }
list target { list target {
key "adjacent-address"; key "adjacent-address";
description description
"Targeted discovery params."; "Targeted discovery params.";
leaf adjacent-address { leaf adjacent-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Configures a remote LDP neighbor for the "Configures a remote LDP neighbor for the
extended LDP discovery."; extended LDP discovery.";
} }
leaf enabled { leaf enabled {
type boolean; type boolean;
default true; default "true";
description description
"'true' to enable the target."; "'true' to enable the target.";
} }
leaf local-address { leaf local-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"The local address used as the source address to "The local address used as the source address to
send targeted Hello messages. send targeted Hello messages.
If the value is not specified, the If the value is not specified, the
transport-address is used as the source transport address is used as the source
address."; address.";
} }
} // target } // target
} // ipv4 } // ipv4
} // address-families } // address-families
} // targeted } // targeted
} // discovery } // discovery
container peers { container peers {
description description
"Peers configuration attributes."; "Peers configuration attributes.";
uses peer-authentication; uses peer-authentication;
uses peer-attributes { uses peer-attributes {
refine session-ka-holdtime { refine "session-ka-holdtime" {
default 180; default "180";
} }
refine session-ka-interval { refine "session-ka-interval" {
default 60; default "60";
} }
} }
list peer { list peer {
key "lsr-id label-space-id"; key "lsr-id label-space-id";
description description
"List of peers."; "List of peers.";
leaf lsr-id { leaf lsr-id {
type rt-types:router-id; type rt-types:router-id;
description description
"The LSR ID of the peer, to identify the globally "The LSR Id of the peer, used to identify the globally
unique LSR. This is the first four octets of the LDP unique LSR. This is the first four octets of the LDP
ID. This leaf is used together with the leaf ID. This leaf is used together with the leaf
'label-space-id' to form the LDP ID."; 'label-space-id' to form the LDP ID.";
reference reference
"RFC5036. Sec 2.2.2."; "RFC 5036: LDP Specification, Sec. 2.2.2.";
} }
leaf label-space-id { leaf label-space-id {
type uint16; type uint16;
description description
"The Label Space ID of the peer, to identify a specific "The label space Id of the peer, used to identify a
label space within the LSR. This is the last two specific label space within the LSR. This is the last
octets of the LDP ID. This leaf is used together with two octets of the LDP ID. This leaf is used together
the leaf 'lsr-id' to form the LDP ID."; with the leaf 'lsr-id' to form the LDP ID.";
reference reference
"RFC5036. Sec 2.2.2."; "RFC 5036: LDP Specification, Sec. 2.2.2.";
} }
uses peer-authentication; uses peer-authentication;
container address-families { container address-families {
description description
"Per-vrf per-af params."; "Per-vrf per-af params.";
container ipv4 { container ipv4 {
presence presence "Present if IPv4 is enabled.";
"Present if IPv4 is enabled.";
description description
"IPv4 address family."; "IPv4 address family.";
container hello-adjacencies { container hello-adjacencies {
config false; config false;
description description
"Containing a list of Hello adjacencies."; "Containing a list of Hello adjacencies.";
list hello-adjacency { list hello-adjacency {
key "local-address adjacent-address"; key "local-address adjacent-address";
description "List of Hello adjacencies."; description
"List of Hello adjacencies.";
leaf local-address { leaf local-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Local address of the Hello adjacency."; "Local address of the Hello adjacency.";
} }
leaf adjacent-address { leaf adjacent-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Neighbor address of the Hello adjacency."; "Neighbor address of the Hello adjacency.";
} }
skipping to change at line 2581 skipping to change at line 2596
leaf local-address { leaf local-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Local address of the Hello adjacency."; "Local address of the Hello adjacency.";
} }
leaf adjacent-address { leaf adjacent-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Neighbor address of the Hello adjacency."; "Neighbor address of the Hello adjacency.";
} }
uses adjacency-state-attributes; uses adjacency-state-attributes;
leaf interface { leaf interface {
type if:interface-ref; type if:interface-ref;
description "Interface for this adjacency."; description
"Interface for this adjacency.";
} }
} }
} }
} // ipv4 } // ipv4
} // address-families } // address-families
uses peer-state-derived; uses peer-state-derived;
} // list peer } // list peer
} // peers } // peers
} // container mpls-ldp } // container mpls-ldp
} }
/* /*
* RPCs * RPCs
*/ */
rpc mpls-ldp-clear-peer { rpc mpls-ldp-clear-peer {
description description
"Clears the session to the peer."; "Clears the session to the peer.";
input { input {
uses ldp-peer-ref-absolute { uses ldp-peer-ref-absolute {
description description
"The LDP peer to be cleared. If this is not provided "The LDP peer to be cleared. If this is not provided,
then all peers are cleared. then all peers are cleared.
The peer is identified by its LDP ID, which consists of The peer is identified by its LDP ID, which consists of
the LSR ID and the Label Space ID."; the LSR Id and the label space Id.";
} }
} }
} }
rpc mpls-ldp-clear-hello-adjacency { rpc mpls-ldp-clear-hello-adjacency {
description description
"Clears the hello adjacency"; "Clears the Hello adjacency.";
input { input {
container hello-adjacency { container hello-adjacency {
description description
"Link adjacency or targettted adjacency. If this is not "Link adjacency or targeted adjacency. If this is not
provided then all Hello adjacencies are cleared"; provided, then all Hello adjacencies are cleared.";
leaf protocol-name { leaf protocol-name {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rt:name"; + "rt:control-plane-protocol/rt:name";
} }
description description
"The name of the LDP protocol instance."; "The name of the LDP protocol instance.";
} }
choice hello-adjacency-type { choice hello-adjacency-type {
description "Adjacency type."; description
"Adjacency type.";
case targeted { case targeted {
container targeted { container targeted {
presence "Present to clear targeted adjacencies."; presence "Present to clear targeted adjacencies.";
description description
"Clear targeted adjacencies."; "Clear targeted adjacencies.";
leaf target-address { leaf target-address {
type inet:ip-address; type inet:ip-address;
description description
"The target address. If this is not provided then "The target address. If this is not provided, then
all targeted adjacencies are cleared"; all targeted adjacencies are cleared.";
} }
} }
} }
case link { case link {
container link { container link {
presence "Present to clear link adjacencies."; presence "Present to clear link adjacencies.";
description description
"Clear link adjacencies."; "Clear link adjacencies.";
leaf next-hop-interface { leaf next-hop-interface {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/mpls-ldp/discovery/" + "rt:control-plane-protocol/mpls-ldp/"
+ "interfaces/interface/name"; + "discovery/interfaces/interface/name";
} }
description description
"Interface connecting to next-hop. If this is not "Interface connecting to a next hop. If this is
provided then all link adjacencies are cleared."; not provided, then all link adjacencies are
cleared.";
} }
leaf next-hop-address { leaf next-hop-address {
type inet:ip-address; type inet:ip-address;
must "../next-hop-interface" { must '../next-hop-interface' {
description description
"Applicable when interface is specified."; "Applicable when an interface is specified.";
} }
description description
"IP address of next-hop. If this is not provided "IP address of a next hop. If this is not
then adjacencies to all next-hops on the given provided, then adjacencies to all next hops on the
interface are cleared."; given interface are cleared.";
} }
} }
} }
} // hello-adjacency-type } // hello-adjacency-type
} // hello-adjacency } // hello-adjacency
} // input } // input
} // mpls-ldp-clear-hello-adjacency } // mpls-ldp-clear-hello-adjacency
rpc mpls-ldp-clear-peer-statistics { rpc mpls-ldp-clear-peer-statistics {
description description
"Clears protocol statistics (e.g. sent and received "Clears protocol statistics (e.g., sent and received
counters)."; counters).";
input { input {
uses ldp-peer-ref-absolute { uses ldp-peer-ref-absolute {
description description
"The LDP peer whose statistics are to be cleared. "The LDP peer whose statistics are to be cleared.
If this is not provided then all peers' statistics are If this is not provided, then all peers' statistics are
cleared. cleared.
The peer is identified by its LDP ID, which consists of The peer is identified by its LDP ID, which consists of
the LSR ID and the Label Space ID."; the LSR Id and the label space Id.";
} }
} }
} }
/* /*
* Notifications * Notifications
*/ */
notification mpls-ldp-peer-event {
notification mpls-ldp-peer-event {
description description
"Notification event for a change of LDP peer operational "Notification event for a change of LDP peer operational
status."; status.";
leaf event-type { leaf event-type {
type oper-status-event-type; type oper-status-event-type;
description "Event type."; description
"Event type.";
} }
container peer { container peer {
description description
"Reference to an LDP peer, by the LDP ID, which consists of "Reference to an LDP peer, by the LDP ID, which consists of
the LSR ID and the Label Space ID."; the LSR Id and the label space Id.";
uses ldp-peer-ref-absolute; uses ldp-peer-ref-absolute;
} }
} }
notification mpls-ldp-hello-adjacency-event { notification mpls-ldp-hello-adjacency-event {
description description
"Notification event for a change of LDP adjacency operational "Notification event for a change of LDP adjacency operational
status."; status.";
leaf event-type { leaf event-type {
type oper-status-event-type; type oper-status-event-type;
description "Event type."; description
"Event type.";
} }
leaf protocol-name { leaf protocol-name {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rt:name"; + "rt:control-plane-protocol/rt:name";
} }
description description
"The name of the LDP protocol instance."; "The name of the LDP protocol instance.";
} }
choice hello-adjacency-type { choice hello-adjacency-type {
description description
"Interface or targeted adjacency."; "Interface or targeted adjacency.";
case targeted { case targeted {
container targeted { container targeted {
description description
"Targeted adjacency through LDP extended discovery."; "Targeted adjacency through LDP extended discovery.";
leaf target-address { leaf target-address {
type inet:ip-address; type inet:ip-address;
description description
"The target adjacent address learned."; "The target adjacent-address learned.";
} }
} }
} }
case link { case link {
container link { container link {
description description
"Link adjacency through LDP basic discovery."; "Link adjacency through LDP basic discovery.";
leaf next-hop-interface { leaf next-hop-interface {
type if:interface-ref; type if:interface-ref;
description description
"The interface connecting to the adjacent next hop."; "The interface connecting to the adjacent next hop.";
} }
leaf next-hop-address { leaf next-hop-address {
type inet:ip-address; type inet:ip-address;
must "../next-hop-interface" { must '../next-hop-interface' {
description description
"Applicable when interface is specified."; "Applicable when an interface is specified.";
} }
description description
"IP address of the next hop. This can be IPv4 or IPv6 "IP address of the next hop. This can be IPv4 or IPv6
address."; address.";
} }
} }
} }
} // hello-adjacency-type } // hello-adjacency-type
} // mpls-ldp-hello-adjacency-event } // mpls-ldp-hello-adjacency-event
notification mpls-ldp-fec-event { notification mpls-ldp-fec-event {
description description
"Notification event for a change of FEC status."; "Notification event for a change of FEC status.";
leaf event-type { leaf event-type {
type oper-status-event-type; type oper-status-event-type;
description "Event type."; description
"Event type.";
} }
leaf protocol-name { leaf protocol-name {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rt:name"; + "rt:control-plane-protocol/rt:name";
} }
description description
"The name of the LDP protocol instance."; "The name of the LDP protocol instance.";
} }
leaf fec { leaf fec {
type inet:ip-prefix; type inet:ip-prefix;
description description
"The address prefix element of the FEC whose status "The address prefix element of the FEC whose status
has changed."; has changed.";
} }
} }
} }
]]>
<CODE ENDS> </sourcecode>
]]>
</artwork>
</figure> </figure>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Extended</name> <name>Extended</name>
<t> <t>
This YANG module imports types defined in <xref target="RFC6991"/>, This YANG module imports types defined in <xref
<xref target="RFC8349"/>, <xref target="RFC8177"/>, and target="RFC5036"/>, <xref target="RFC6991"/>, <xref
<xref target="RFC8343"/>. target="RFC8349"/>, <xref target="RFC8177"/>, <xref
target="RFC8343"/>, and <xref target="RFC9067"/>.
</t> </t>
<figure anchor="EXT-YANG-FILE"> <figure anchor="EXT-YANG-FILE">
<name>LDP extended module</name> <name>LDP Extended Module</name>
<artwork> <sourcecode name="ietf-mpls-ldp-extended@2022-03-07.yang" type="yang" m
arkers="true"><![CDATA[
<![CDATA[
<CODE BEGINS> file "ietf-mpls-ldp-extended@2020-02-25.yang"
// RFC Editor: replace the above date 2020-02-25 with the date of
// publication and remove this note.
module ietf-mpls-ldp-extended { module ietf-mpls-ldp-extended {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-ldp-extended"; namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-ldp-extended";
prefix "ldp-ext"; prefix ldp-ext;
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix inet;
reference "RFC 6991: Common YANG Data Types"; reference
"RFC 6991: Common YANG Data Types";
} }
import ietf-routing { import ietf-routing {
prefix "rt"; prefix rt;
reference reference
"RFC 8349: A YANG Data Model for Routing Management (NMDA "RFC 8349: A YANG Data Model for Routing Management (NMDA
version)"; version)";
} }
import ietf-key-chain { import ietf-key-chain {
prefix "key-chain"; prefix key-chain;
reference "RFC 8177: YANG Data Model for Key Chains"; reference
"RFC 8177: YANG Data Model for Key Chains";
} }
import ietf-mpls-ldp { import ietf-mpls-ldp {
prefix "ldp"; prefix ldp;
reference "RFC XXXX: YANG Data Model for MPLS LDP"; reference
// RFC Editor: replace XXXX with actual RFC number and remove "RFC 9070: YANG Data Model for MPLS LDP";
// this note
} }
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix if;
reference "RFC 8343: A YANG Data Model for Interface Management"; reference
"RFC 8343: A YANG Data Model for Interface Management";
} }
import ietf-routing-policy { import ietf-routing-policy {
prefix rt-pol; prefix rt-pol;
reference reference
"I-D.ietf-rtgwg-policy-model: A YANG Data Model for Routing "RFC 9067: A YANG Data Model for Routing Policy";
Policy Management";
} }
organization organization
"IETF MPLS Working Group"; "IETF MPLS Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/mpls/> "WG Web: <https://datatracker.ietf.org/wg/mpls/>
WG List: <mailto:mpls@ietf.org> WG List: <mailto:mpls@ietf.org>
Editor: Kamran Raza Editor: Kamran Raza
<mailto:skraza@cisco.com> <mailto:skraza@cisco.com>
Editor: Rajiv Asati Author: Rajiv Asati
<mailto:rajiva@cisco.com> <mailto:rajiva@cisco.com>
Editor: Xufeng Liu Author: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com> <mailto:xufeng.liu.ietf@gmail.com>
Editor: Santosh Esale Author: Santosh Easale
<mailto:sesale@juniper.net> <mailto:santosh_easale@berkeley.edu>
Editor: Xia Chen Author: Xia Chen
<mailto:jescia.chenxia@huawei.com> <mailto:jescia.chenxia@huawei.com>
Editor: Himanshu Shah Author: Himanshu Shah
<mailto:hshah@ciena.com>"; <mailto:hshah@ciena.com>";
description description
"This YANG module defines the extended components for the "This YANG module defines the extended components for the
management of Multi-Protocol Label Switching (MPLS) Label management of Multiprotocol Label Switching (MPLS) Label
Distribution Protocol (LDP). It is also the model to Distribution Protocol (LDP). It is also the model to
be augmented for extended Multipoint LDP (mLDP). be augmented for extended Multipoint LDP (mLDP).
Copyright (c) 2020 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons 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 to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License 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
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC 9070; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
// RFC Editor: replace XXXX with actual RFC number and remove revision 2022-03-07 {
// this note
revision 2020-02-25 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: YANG Data Model for MPLS LDP."; "RFC 9070: YANG Data Model for MPLS LDP";
// RFC Editor: replace XXXX with actual RFC number and remove
// this note
} }
/* /*
* Features * Features
*/ */
feature capability-end-of-lib { feature capability-end-of-lib {
description description
"This feature indicates that the system allows to configure "This feature indicates that the system allows for the
LDP end-of-lib capability."; configuration of LDP end-of-lib capability.";
} }
feature capability-typed-wildcard-fec { feature capability-typed-wildcard-fec {
description description
"This feature indicates that the system allows to configure "This feature indicates that the system allows for the
LDP typed-wildcard-fec capability."; configuration of LDP typed-wildcard-fec capability.";
} }
feature capability-upstream-label-assignment { feature capability-upstream-label-assignment {
description description
"This feature indicates that the system allows to configure "This feature indicates that the system allows for the
LDP upstream label assignment capability."; configuration of LDP upstream label assignment capability.";
} }
feature forwarding-nexthop-config { feature forwarding-nexthop-config {
description description
"This feature indicates that the system allows to configure "This feature indicates that the system allows for controlling
forwarding nexthop on interfaces."; MPLS forwarding on an LDP interface.";
} }
feature graceful-restart-helper-mode { feature graceful-restart-helper-mode {
description description
"This feature indicates that the system supports graceful "This feature indicates that the system supports graceful
restart helper mode. We call an LSR to be operating in GR restart helper mode. We call an LSR to be operating in GR
helper mode when it advertises 0 as its FT Reconnect Timeout helper mode when it advertises 0 as its FT Reconnect Timeout
in the FT Session TLV. in the FT Session TLV.
Please refer RFC3478 section 2 for details."; Please refer to Section 2 of RFC 3478 for details.";
} }
feature key-chain { feature key-chain {
description description
"This feature indicates that the system supports keychain for "This feature indicates that the system supports key-chain for
authentication."; authentication.";
} }
feature peers-dual-stack-transport-preference { feature peers-dual-stack-transport-preference {
description description
"This feature indicates that the system allows to configure "This feature indicates that the system allows for the
the transport connection preference in a dual-stack setup configuration of the transport connection preference in a
for peers."; dual-stack setup for peers.";
} }
feature per-interface-timer-config { feature per-interface-timer-config {
description description
"This feature indicates that the system allows to configure "This feature indicates that the system allows for the
interface Hello timers at the per-interface level."; configuration of interface Hello timers at the per-interface
level.";
} }
feature per-peer-admin-down { feature per-peer-admin-down {
description description
"This feature indicates that the system allows to "This feature indicates that the system allows for the
administratively disable a peer."; administrative disabling of a peer.";
} }
feature per-peer-graceful-restart-config { feature per-peer-graceful-restart-config {
description description
"This feature indicates that the system allows to configure "This feature indicates that the system allows for the
graceful restart at the per-peer level."; configuration of graceful restart at the per-peer level.";
} }
feature per-peer-session-attributes-config { feature per-peer-session-attributes-config {
description description
"This feature indicates that the system allows to configure "This feature indicates that the system allows for the
session attributes at the per-peer level."; configuration of session attributes at the per-peer level.";
} }
feature policy-label-assignment-config { feature policy-label-assignment-config {
description description
"This feature indicates that the system allows to configure "This feature indicates that the system allows for the
policies to assign labels according to certain prefixes."; configuration of policies to assign labels according to
certain prefixes.";
} }
feature policy-ordered-label-config { feature policy-ordered-label-config {
description description
"This feature indicates that the system allows to configure "This feature indicates that the system allows for the
ordered label policies."; configuration of ordered label policies.";
} }
feature policy-targeted-discovery-config { feature policy-targeted-discovery-config {
description description
"This feature indicates that the system allows to configure "This feature indicates that the system allows for the
policies to control the acceptance of targeted neighbor configuration of policies to control the acceptance of
discovery Hello messages."; targeted neighbor-discovery Hello messages.";
} }
feature session-downstream-on-demand-config { feature session-downstream-on-demand-config {
description description
"This feature indicates that the system allows to configure "This feature indicates that the system allows for the
session downstream-on-demand"; configuration of session downstream on demand.";
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef neighbor-list-ref { typedef neighbor-list-ref {
type leafref { type leafref {
path "/rt-pol:routing-policy/rt-pol:defined-sets/" path "/rt-pol:routing-policy/rt-pol:defined-sets/"
+ "rt-pol:neighbor-sets/rt-pol:neighbor-set/rt-pol:name"; + "rt-pol:neighbor-sets/rt-pol:neighbor-set/rt-pol:name";
} }
description description
"A type for a reference to a neighbor address list. "A type for a reference to a neighbor address list.
The string value is the name identifier for uniquely The string value is the name identifier for uniquely
identifying the referenced address list, which contains a list identifying the referenced address list, which contains a list
of addresses that a routing policy can applied."; of addresses that a routing policy can applied.";
reference reference
"I-D.ietf-rtgwg-policy-model: A YANG Data Model for Routing "RFC 9067: A YANG Data Model for Routing Policy";
Policy Management";
} }
typedef prefix-list-ref { typedef prefix-list-ref {
type leafref { type leafref {
path "/rt-pol:routing-policy/rt-pol:defined-sets/" path "/rt-pol:routing-policy/rt-pol:defined-sets/"
+ "rt-pol:prefix-sets/rt-pol:prefix-set/rt-pol:name"; + "rt-pol:prefix-sets/rt-pol:prefix-set/rt-pol:name";
} }
description description
"A type for a reference to a prefix list. "A type for a reference to a prefix list.
The string value is the name identifier for uniquely The string value is the name identifier for uniquely
identifying the referenced prefix set, which contains a list identifying the referenced prefix set, which contains a list
of prefixes that a routing policy can applied."; of prefixes that a routing policy can applied.";
reference reference
"I-D.ietf-rtgwg-policy-model: A YANG Data Model for Routing "RFC 9067: A YANG Data Model for Routing Policy";
Policy Management";
} }
typedef peer-list-ref { typedef peer-list-ref {
type leafref { type leafref {
path "/rt-pol:routing-policy/rt-pol:defined-sets/" path "/rt-pol:routing-policy/rt-pol:defined-sets/"
+ "rt-pol:neighbor-sets/rt-pol:neighbor-set/rt-pol:name"; + "rt-pol:neighbor-sets/rt-pol:neighbor-set/rt-pol:name";
} }
description description
"A type for a reference to a peer address list. "A type for a reference to a peer address list.
The string value is the name identifier for uniquely The string value is the name identifier for uniquely
identifying the referenced address list, which contains a list identifying the referenced address list, which contains a list
of addresses that a routing policy can applied."; of addresses that a routing policy can applied.";
reference reference
"I-D.ietf-rtgwg-policy-model: A YANG Data Model for Routing "RFC 9067: A YANG Data Model for Routing Policy";
Policy Management";
} }
/* /*
* Identities * Identities
*/ */
/* /*
* Groupings * Groupings
*/ */
grouping address-family-ipv4-augment {
description "Augmentation to address family IPv4.";
grouping address-family-ipv4-augment {
description
"Augmentation to address family IPv4.";
uses policy-container; uses policy-container;
leaf transport-address { leaf transport-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"The transport address advertised in LDP Hello messages. "The transport address advertised in LDP Hello messages.
If this value is not specified, the LDP LSR ID is used as If this value is not specified, the LDP LSR Id is used as
the transport address."; the transport address.";
reference reference
"RFC5036. Sec. 3.5.2."; "RFC 5036: LDP Specification, Sec. 3.5.2.";
} }
} }
grouping authentication-keychain-augment { grouping authentication-keychain-augment {
description "Augmentation to authentication to add keychain."; description
"Augmentation to authentication to add key-chain.";
leaf key-chain { leaf key-chain {
type key-chain:key-chain-ref; type key-chain:key-chain-ref;
description description
"key-chain name. "key-chain name.
If not specified, no key chain is used."; If not specified, no key chain is used.";
} }
} }
grouping capability-augment { grouping capability-augment {
description "Augmentation to capability."; description
"Augmentation to capability.";
container end-of-lib { container end-of-lib {
if-feature capability-end-of-lib; if-feature "capability-end-of-lib";
description description
"Configure end-of-lib capability."; "Configure end-of-lib capability.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default false; default "false";
description description
"'true' to enable end-of-lib capability."; "'true' to enable end-of-lib capability.";
} }
} }
container typed-wildcard-fec { container typed-wildcard-fec {
if-feature capability-typed-wildcard-fec; if-feature "capability-typed-wildcard-fec";
description description
"Configure typed-wildcard-fec capability."; "Configure typed-wildcard-fec capability.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default false; default "false";
description description
"'true' to enable typed-wildcard-fec capability."; "'true' to enable typed-wildcard-fec capability.";
} }
} }
container upstream-label-assignment { container upstream-label-assignment {
if-feature capability-upstream-label-assignment; if-feature "capability-upstream-label-assignment";
description description
"Configure upstream label assignment capability."; "Configure upstream label assignment capability.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default false; default "false";
description description
"'true' to enable upstream label assignment."; "'true' to enable upstream label assignment.";
} }
} }
} // capability-augment } // capability-augment
grouping global-augment { grouping global-augment {
description "Augmentation to global attributes."; description
"Augmentation to global attributes.";
leaf igp-synchronization-delay { leaf igp-synchronization-delay {
type uint16 { type uint16 {
range "0 | 3..300"; range "0 | 3..300";
} }
units seconds; units "seconds";
default 0; default "0";
description description
"Sets the interval that the LDP waits before notifying the "Sets the interval that the LDP waits before notifying the
Interior Gateway Protocol (IGP) that label exchange is Interior Gateway Protocol (IGP) that label exchange is
completed so that IGP can start advertising the normal completed so that IGP can start advertising the normal
metric for the link. metric for the link.
If the value is not specified, there is no delay."; If the value is not specified, there is no delay.";
} }
} }
grouping global-forwarding-nexthop-augment { grouping global-forwarding-nexthop-augment {
description description
"Augmentation to global forwarding nexthop interfaces."; "Augmentation at the global level for controlling MPLS
forwarding on LDP interfaces.";
container forwarding-nexthop { container forwarding-nexthop {
if-feature forwarding-nexthop-config; if-feature "forwarding-nexthop-config";
description description
"Configuration for forwarding nexthop."; "Configuration for controlling MPLS forwarding on LDP
interfaces.";
container interfaces { container interfaces {
description description
"Containing a list of interfaces on which forwarding can be "Containing a list of interfaces on which forwarding can be
disabled."; disabled.";
list interface { list interface {
key "name"; key "name";
description description
"List of LDP interfaces on which forwarding can be "List of LDP interfaces on which forwarding can be
disabled."; disabled.";
uses ldp:ldp-interface-ref; uses ldp:ldp-interface-ref;
list address-family { list address-family {
key "afi"; key "afi";
description description
"Per-vrf per-af params."; "Per-vrf per-af params.";
leaf afi { leaf afi {
type identityref { type identityref {
base rt:address-family; base rt:address-family;
} }
description description
"Address family type value."; "Address family type value.";
} }
leaf ldp-disable { leaf ldp-disable {
type boolean; type boolean;
default false; default "false";
description description
"'true' to disable LDP forwarding on the interface."; "'true' to disable LDP forwarding on the interface.";
} }
} }
} // interface } // interface
} // interfaces } // interfaces
} // forwarding-nexthop } // forwarding-nexthop
} // global-forwarding-nexthop-augment } // global-forwarding-nexthop-augment
grouping graceful-restart-augment { grouping graceful-restart-augment {
description "Augmentation to graceful restart."; description
"Augmentation to graceful restart.";
leaf helper-enabled { leaf helper-enabled {
if-feature graceful-restart-helper-mode; if-feature "graceful-restart-helper-mode";
type boolean; type boolean;
default false; default "false";
description description
"Enable or disable graceful restart helper mode."; "Enable or disable graceful restart helper mode.";
} }
} }
grouping interface-address-family-ipv4-augment { grouping interface-address-family-ipv4-augment {
description "Augmentation to interface address family IPv4."; description
"Augmentation to interface address family IPv4.";
leaf transport-address { leaf transport-address {
type union { type union {
type enumeration { type enumeration {
enum "use-global-transport-address" { enum use-global-transport-address {
description description
"Use the transport address set at the global level "Use the transport address set at the global level
common for all interfaces for this address family."; common for all interfaces for this address family.";
} }
enum "use-interface-address" { enum use-interface-address {
description description
"Use interface address as the transport address."; "Use interface address as the transport address.";
} }
} }
type inet:ipv4-address; type inet:ipv4-address;
} }
default "use-global-transport-address"; default "use-global-transport-address";
description description
"IP address to be advertised as the LDP transport address."; "IP address to be advertised as the LDP transport address.";
} }
} }
grouping interface-address-family-ipv6-augment { grouping interface-address-family-ipv6-augment {
description "Augmentation to interface address family IPv6."; description
"Augmentation to interface address family IPv6.";
leaf transport-address { leaf transport-address {
type union { type union {
type enumeration { type enumeration {
enum "use-global-transport-address" { enum use-global-transport-address {
description description
"Use the transport address set at the global level "Use the transport address set at the global level
common for all interfaces for this address family."; common for all interfaces for this address family.";
} }
enum "use-interface-address" { enum use-interface-address {
description description
"Use interface address as the transport address."; "Use interface address as the transport address.";
} }
} }
type inet:ipv6-address; type inet:ipv6-address;
} }
default "use-global-transport-address"; default "use-global-transport-address";
description description
"IP address to be advertised as the LDP transport address."; "IP address to be advertised as the LDP transport address.";
} }
} }
grouping interface-augment { grouping interface-augment {
description "Augmentation to interface."; description
"Augmentation to interface.";
uses ldp:basic-discovery-timers { uses ldp:basic-discovery-timers {
if-feature per-interface-timer-config; if-feature "per-interface-timer-config";
} }
leaf igp-synchronization-delay { leaf igp-synchronization-delay {
if-feature per-interface-timer-config; if-feature "per-interface-timer-config";
type uint16 { type uint16 {
range "0 | 3..300"; range "0 | 3..300";
} }
units seconds; units "seconds";
description description
"Sets the interval that the LDP waits before notifying the "Sets the interval that the LDP waits before notifying the
Interior Gateway Protocol (IGP) that label exchange is Interior Gateway Protocol (IGP) that label exchange is
completed so that IGP can start advertising the normal completed so that IGP can start advertising the normal
metric for the link. metric for the link.
This leaf may be configured at the per-interface level or This leaf may be configured at the per-interface level or
the global level, with precedence given to the value at the the global level, with precedence given to the value at the
per-interface level. If the leaf is not configured at per-interface level. If the leaf is not configured at
either level, the default value at the global level is either level, the default value at the global level is
used."; used.";
} }
} }
grouping peer-af-policy-container { grouping peer-af-policy-container {
description description
"LDP policy attribute container under peer address-family."; "LDP policy attribute container under peer address family.";
container label-policy { container label-policy {
description description
"Label policy attributes."; "Label policy attributes.";
container advertise { container advertise {
description description
"Label advertising policies."; "Label advertising policies.";
leaf prefix-list { leaf prefix-list {
type prefix-list-ref; type prefix-list-ref;
description description
"Applies the prefix list to filter outgoing label "Applies the prefix list to filter outgoing label
advertisements. advertisements.
If the value is not specified, no prefix filter If the value is not specified, no prefix filter
is applied."; is applied.";
} }
} }
container accept { container accept {
description description
"Label advertisement acceptance policies."; "Label advertisement acceptance policies.";
leaf prefix-list { leaf prefix-list {
type prefix-list-ref; type prefix-list-ref;
description description
"Applies the prefix list to filer incoming label "Applies the prefix list to filer incoming label
advertisements. advertisements.
If the value is not specified, no prefix filter If the value is not specified, no prefix filter
is applied."; is applied.";
} }
} }
} }
} // peer-af-policy-container } // peer-af-policy-container
grouping peer-augment { grouping peer-augment {
description "Augmentation to each peer list entry."; description
"Augmentation to each peer list entry.";
leaf admin-down { leaf admin-down {
if-feature per-peer-admin-down; if-feature "per-peer-admin-down";
type boolean; type boolean;
default false; default "false";
description description
"'true' to disable the peer."; "'true' to disable the peer.";
} }
uses ldp:graceful-restart-attributes-per-peer { uses ldp:graceful-restart-attributes-per-peer {
if-feature per-peer-graceful-restart-config; if-feature "per-peer-graceful-restart-config";
} }
uses ldp:peer-attributes { uses ldp:peer-attributes {
if-feature per-peer-session-attributes-config; if-feature "per-peer-session-attributes-config";
} }
} }
grouping peers-augment { grouping peers-augment {
description "Augmentation to peers container."; description
"Augmentation to peers container.";
container session-downstream-on-demand { container session-downstream-on-demand {
if-feature session-downstream-on-demand-config; if-feature "session-downstream-on-demand-config";
description description
"Session downstream-on-demand attributes."; "Session downstream-on-demand attributes.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default false; default "false";
description description
"'true' if session downstream-on-demand is enabled."; "'true' if session downstream on demand is enabled.";
} }
leaf peer-list { leaf peer-list {
type peer-list-ref; type peer-list-ref;
description description
"The name of a peer ACL, to be applied to the "The name of a peer ACL, to be applied to the
downstream-on-demand sessions. downstream-on-demand sessions.
If this value is not specified, no filter is applied to If this value is not specified, no filter is applied to
any downstream-on-demand sessions."; any downstream-on-demand sessions.";
} }
} }
container dual-stack-transport-preference { container dual-stack-transport-preference {
if-feature peers-dual-stack-transport-preference; if-feature "peers-dual-stack-transport-preference";
description description
"The settings of peers to establish TCP connection in a "The settings of peers to establish TCP connection in a
dual-stack setup."; dual-stack setup.";
leaf max-wait { leaf max-wait {
type uint16 { type uint16 {
range "0..60"; range "0..60";
} }
default 30; default "30";
description description
"The maximum wait time in seconds for preferred transport "The maximum wait time in seconds for preferred transport
connection establishment. 0 indicates no preference."; connection establishment. 0 indicates no preference.";
} }
container prefer-ipv4 { container prefer-ipv4 {
presence presence "Present if IPv4 is preferred for transport
"Present if IPv4 is prefered for transport connection connection establishment, subject to the
establishment, subject to the 'peer-list' in this 'peer-list' in this container.";
container.";
description description
"Uses IPv4 as the prefered address family for transport "Uses IPv4 as the preferred address family for transport
connection establishment, subject to the 'peer-list' in connection establishment, subject to the 'peer-list' in
this container. this container.
If this container is not present, as a default, IPv6 is If this container is not present, as a default, IPv6 is
the prefered address family for transport connection the preferred address family for transport connection
establishment."; establishment.";
leaf peer-list { leaf peer-list {
type peer-list-ref; type peer-list-ref;
description description
"The name of a peer ACL, to be applied to the IPv4 "The name of a peer ACL, to be applied to the IPv4
transport connections. transport connections.
If this value is not specified, no filter is applied, If this value is not specified, no filter is applied,
and the IPv4 is prefered for all peers."; and the IPv4 is preferred for all peers.";
} }
} }
} }
} // peers-augment } // peers-augment
grouping policy-container { grouping policy-container {
description description
"LDP policy attributes."; "LDP policy attributes.";
container label-policy { container label-policy {
description description
skipping to change at line 3413 skipping to change at line 3406
description description
"Label advertising policies."; "Label advertising policies.";
container egress-explicit-null { container egress-explicit-null {
description description
"Enables an egress router to advertise an "Enables an egress router to advertise an
explicit null label (value 0) in place of an explicit null label (value 0) in place of an
implicit null label (value 3) to the implicit null label (value 3) to the
penultimate hop router."; penultimate hop router.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default false; default "false";
description description
"'true' to enable explicit null."; "'true' to enable explicit null.";
} }
} }
leaf prefix-list { leaf prefix-list {
type prefix-list-ref; type prefix-list-ref;
description description
"Applies the prefix list to filter outgoing label "Applies the prefix list to filter outgoing label
advertisements. advertisements.
If the value is not specified, no prefix filter If the value is not specified, no prefix filter
skipping to change at line 3440 skipping to change at line 3433
leaf prefix-list { leaf prefix-list {
type prefix-list-ref; type prefix-list-ref;
description description
"Applies the prefix list to filter incoming label "Applies the prefix list to filter incoming label
advertisements. advertisements.
If the value is not specified, no prefix filter If the value is not specified, no prefix filter
is applied."; is applied.";
} }
} }
container assign { container assign {
if-feature policy-label-assignment-config; if-feature "policy-label-assignment-config";
description description
"Label assignment policies"; "Label assignment policies.";
container independent-mode { container independent-mode {
description description
"Independent label policy attributes."; "Independent label policy attributes.";
leaf prefix-list { leaf prefix-list {
type prefix-list-ref; type prefix-list-ref;
description description
"Assign labels according to certain prefixes. "Assign labels according to certain prefixes.
If the value is not specified, no prefix filter If the value is not specified, no prefix filter
is applied (labels are assigned to all learned is applied (labels are assigned to all learned
routes)."; routes).";
skipping to change at line 3453 skipping to change at line 3446
container independent-mode { container independent-mode {
description description
"Independent label policy attributes."; "Independent label policy attributes.";
leaf prefix-list { leaf prefix-list {
type prefix-list-ref; type prefix-list-ref;
description description
"Assign labels according to certain prefixes. "Assign labels according to certain prefixes.
If the value is not specified, no prefix filter If the value is not specified, no prefix filter
is applied (labels are assigned to all learned is applied (labels are assigned to all learned
routes)."; routes).";
} }
} }
container ordered-mode { container ordered-mode {
if-feature policy-ordered-label-config; if-feature "policy-ordered-label-config";
description description
"Ordered label policy attributes."; "Ordered label policy attributes.";
leaf egress-prefix-list { leaf egress-prefix-list {
type prefix-list-ref; type prefix-list-ref;
description description
"Assign labels according to certain prefixes for "Assign labels according to certain prefixes for
egress LSR."; egress LSR.";
} }
} }
} // assign } // assign
skipping to change at line 3475 skipping to change at line 3467
} }
} }
} // assign } // assign
} // label-policy } // label-policy
} // policy-container } // policy-container
/* /*
* Configuration and state data nodes * Configuration and state data nodes
*/ */
// Forwarding nexthop augmentation to the global tree // Forwarding nexthop augmentation to the global tree
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global" { + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global" {
description "Forwarding nexthop augmentation."; description
"Forwarding nexthop augmentation.";
uses global-forwarding-nexthop-augment; uses global-forwarding-nexthop-augment;
} }
// global/address-families/ipv6 // global/address-families/ipv6
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/"
+ "ldp:address-families" {
description "Global IPv6 augmentation.";
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/"
+ "ldp:address-families" {
description
"Global IPv6 augmentation.";
container ipv6 { container ipv6 {
presence presence "Present if IPv6 is enabled, unless the 'enabled'
"Present if IPv6 is enabled, unless the 'enabled' leaf is set to 'false'.";
leaf is set to 'false'";
description description
"Containing data related to the IPv6 address family."; "Containing data related to the IPv6 address family.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default true; default "true";
description description
"'false' to disable the address family."; "'false' to disable the address family.";
} }
uses policy-container; uses policy-container;
leaf transport-address { leaf transport-address {
type inet:ipv6-address; type inet:ipv6-address;
mandatory true; mandatory true;
description description
"The transport address advertised in LDP Hello messages."; "The transport address advertised in LDP Hello messages.";
} }
leaf label-distribution-control-mode { leaf label-distribution-control-mode {
type enumeration { type enumeration {
enum independent { enum independent {
description description
"Independent label distribution control."; "Independent label distribution control.";
} }
enum ordered { enum ordered {
description description
"Ordered label distribution control."; "Ordered label distribution control.";
} }
} }
config false; config false;
description description
"Label distribution control mode."; "Label distribution control mode.";
reference reference
"RFC5036: LDP Specification. Sec 2.6."; "RFC 5036: LDP Specification, Sec. 2.6.";
} }
// ipv6 bindings // ipv6 bindings
container bindings { container bindings {
config false; config false;
description description
"LDP address and label binding information."; "LDP address and label binding information.";
list address { list address {
key "address"; key "address";
description description
"List of address bindings learned by LDP."; "List of address bindings learned by LDP.";
leaf address { leaf address {
skipping to change at line 3545 skipping to change at line 3534
description description
"List of address bindings learned by LDP."; "List of address bindings learned by LDP.";
leaf address { leaf address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"The IPv6 address learned from an Address "The IPv6 address learned from an Address
message received from or advertised to a peer."; message received from or advertised to a peer.";
} }
uses ldp:binding-address-state-attributes; uses ldp:binding-address-state-attributes;
} }
list fec-label { list fec-label {
key "fec"; key "fec";
description description
"List of FEC-label bindings learned by LDP."; "List of FEC-label bindings learned by LDP.";
leaf fec { leaf fec {
type inet:ipv6-prefix; type inet:ipv6-prefix;
description description
"The prefix FEC value in the FEC-label binding, "The prefix FEC value in the FEC-Label binding,
learned in a Label Mapping message received from learned in a Label Mapping message received from
or advertised to a peer."; or advertised to a peer.";
} }
uses ldp:binding-label-state-attributes; uses ldp:binding-label-state-attributes;
} }
} // bindings } // bindings
} // ipv6 } // ipv6
} }
// discovery/interfaces/interface/address-families/ipv6 // discovery/interfaces/interface/address-families/ipv6
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/"
+ "ldp:interfaces/ldp:interface/"
+ "ldp:address-families" {
description "Interface IPv6 augmentation.";
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/"
+ "ldp:interfaces/ldp:interface/"
+ "ldp:address-families" {
description
"Interface IPv6 augmentation.";
container ipv6 { container ipv6 {
presence presence "Present if IPv6 is enabled, unless the 'enabled'
"Present if IPv6 is enabled, unless the 'enabled' leaf is set to 'false'.";
leaf is set to 'false'";
description description
"IPv6 address family."; "IPv6 address family.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default true; default "true";
description description
"'false' to disable the address family on the interface."; "'false' to disable the address family on the interface.";
} }
container hello-adjacencies { container hello-adjacencies {
config false; config false;
description description
"Containing a list of Hello adjacencies."; "Containing a list of Hello adjacencies.";
list hello-adjacency { list hello-adjacency {
key "adjacent-address"; key "adjacent-address";
config false; config false;
description "List of Hello adjacencies."; description
"List of Hello adjacencies.";
leaf adjacent-address { leaf adjacent-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Neighbor address of the Hello adjacency."; "Neighbor address of the Hello adjacency.";
} }
uses ldp:adjacency-state-attributes; uses ldp:adjacency-state-attributes;
uses ldp:ldp-peer-ref-from-interface; uses ldp:ldp-peer-ref-from-interface;
} }
} }
} // ipv6 } // ipv6
} }
// discovery/targeted/address-families/ipv6 // discovery/targeted/address-families/ipv6
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/"
+ "ldp:targeted/ldp:address-families" {
description "Targeted discovery IPv6 augmentation.";
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/"
+ "ldp:targeted/ldp:address-families" {
description
"Targeted discovery IPv6 augmentation.";
container ipv6 { container ipv6 {
presence presence "Present if IPv6 is enabled.";
"Present if IPv6 is enabled.";
description description
"IPv6 address family."; "IPv6 address family.";
container hello-adjacencies { container hello-adjacencies {
config false; config false;
description description
"Containing a list of Hello adjacencies."; "Containing a list of Hello adjacencies.";
list hello-adjacency { list hello-adjacency {
key "local-address adjacent-address"; key "local-address adjacent-address";
config false; config false;
description "List of Hello adjacencies."; description
"List of Hello adjacencies.";
leaf local-address { leaf local-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Local address of the Hello adjacency."; "Local address of the Hello adjacency.";
} }
leaf adjacent-address { leaf adjacent-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Neighbor address of the Hello adjacency."; "Neighbor address of the Hello adjacency.";
} }
skipping to change at line 3639 skipping to change at line 3621
leaf local-address { leaf local-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Local address of the Hello adjacency."; "Local address of the Hello adjacency.";
} }
leaf adjacent-address { leaf adjacent-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Neighbor address of the Hello adjacency."; "Neighbor address of the Hello adjacency.";
} }
uses ldp:adjacency-state-attributes; uses ldp:adjacency-state-attributes;
uses ldp:ldp-peer-ref-from-target; uses ldp:ldp-peer-ref-from-target;
} }
} }
list target { list target {
key "adjacent-address"; key "adjacent-address";
description description
"Targeted discovery params."; "Targeted discovery params.";
leaf adjacent-address { leaf adjacent-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Configures a remote LDP neighbor for the "Configures a remote LDP neighbor for the
extended LDP discovery."; extended LDP discovery.";
} }
leaf enabled { leaf enabled {
type boolean; type boolean;
default true; default "true";
description description
"'true' to enable the target."; "'true' to enable the target.";
} }
leaf local-address { leaf local-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"The local address used as the source address to send "The local address used as the source address to send
targeted Hello messages. targeted Hello messages.
If the value is not specified, the transport-address If the value is not specified, the transport address
is used as the source address."; is used as the source address.";
} }
} // target } // target
} // ipv6 } // ipv6
} }
// /peers/peer/state/address-families/ipv6 // /peers/peer/state/address-families/ipv6
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/"
+ "ldp:peer/ldp:address-families" {
description "Peer state IPv6 augmentation.";
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/"
+ "ldp:peer/ldp:address-families" {
description
"Peer state IPv6 augmentation.";
container ipv6 { container ipv6 {
presence presence "Present if IPv6 is enabled.";
"Present if IPv6 is enabled.";
description description
"IPv6 address family."; "IPv6 address family.";
container hello-adjacencies { container hello-adjacencies {
config false; config false;
description description
"Containing a list of Hello adjacencies."; "Containing a list of Hello adjacencies.";
list hello-adjacency { list hello-adjacency {
key "local-address adjacent-address"; key "local-address adjacent-address";
description "List of Hello adjacencies."; description
"List of Hello adjacencies.";
leaf local-address { leaf local-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Local address of the Hello adjacency."; "Local address of the Hello adjacency.";
} }
leaf adjacent-address { leaf adjacent-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Neighbor address of the Hello adjacency."; "Neighbor address of the Hello adjacency.";
} }
skipping to change at line 3705 skipping to change at line 3682
leaf local-address { leaf local-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Local address of the Hello adjacency."; "Local address of the Hello adjacency.";
} }
leaf adjacent-address { leaf adjacent-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Neighbor address of the Hello adjacency."; "Neighbor address of the Hello adjacency.";
} }
uses ldp:adjacency-state-attributes; uses ldp:adjacency-state-attributes;
leaf interface { leaf interface {
type if:interface-ref; type if:interface-ref;
description "Interface for this adjacency."; description
"Interface for this adjacency.";
} }
} }
} }
} // ipv6 } // ipv6
} }
/* /*
* Configuration data and operational state data nodes * Configuration data and operational state data nodes
*/ */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global" { + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global" {
description "Graceful restart augmentation."; description
"Graceful restart augmentation.";
uses global-augment; uses global-augment;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/"
+ "ldp:capability" { + "ldp:capability" {
description "Capability augmentation."; description
"Capability augmentation.";
uses capability-augment; uses capability-augment;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/"
+ "ldp:graceful-restart" { + "ldp:graceful-restart" {
description "Graceful restart augmentation."; description
"Graceful restart augmentation.";
uses graceful-restart-augment; uses graceful-restart-augment;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/"
+ "ldp:address-families/ldp:ipv4" { + "ldp:address-families/ldp:ipv4" {
description "Address family IPv4 augmentation."; description
"Address family IPv4 augmentation.";
uses address-family-ipv4-augment; uses address-family-ipv4-augment;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/"
+ "ldp:interfaces/ldp:interface" { + "ldp:interfaces/ldp:interface" {
description "Interface augmentation."; description
"Interface augmentation.";
uses interface-augment; uses interface-augment;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/"
+ "ldp:interfaces/ldp:interface/ldp:address-families/" + "ldp:interfaces/ldp:interface/ldp:address-families/"
+ "ldp:ipv4" { + "ldp:ipv4" {
description "Interface address family IPv4 augmentation."; description
"Interface address family IPv4 augmentation.";
uses interface-address-family-ipv4-augment; uses interface-address-family-ipv4-augment;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/"
+ "ldp:interfaces/ldp:interface/ldp:address-families/" + "ldp:interfaces/ldp:interface/ldp:address-families/"
+ "ldp-ext:ipv6" { + "ldp-ext:ipv6" {
description "Interface address family IPv6 augmentation."; description
"Interface address family IPv6 augmentation.";
uses interface-address-family-ipv6-augment; uses interface-address-family-ipv6-augment;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/"
+ "ldp:targeted/ldp:hello-accept" { + "ldp:targeted/ldp:hello-accept" {
description "Targeted discovery augmentation."; description
"Targeted discovery augmentation.";
leaf neighbor-list { leaf neighbor-list {
if-feature policy-targeted-discovery-config; if-feature "policy-targeted-discovery-config";
type neighbor-list-ref; type neighbor-list-ref;
description description
"The name of a neighbor ACL, to accept Hello messages from "The name of a neighbor ACL, used to accept Hello messages
LDP peers as permitted by the neighbor-list policy. from LDP peers as permitted by the neighbor-list policy.
If this value is not specified, targeted Hello messages from If this value is not specified, targeted Hello messages
any source are accepted."; from any source are accepted.";
} }
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers" { + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers" {
description "Peers augmentation."; description
"Peers augmentation.";
uses peers-augment; uses peers-augment;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/"
+ "ldp:authentication/ldp:authentication-type" { + "ldp:authentication/ldp:authentication-type" {
if-feature key-chain; if-feature "key-chain";
description "Peers authentication augmentation."; description
"Peers authentication augmentation.";
case key-chain { case key-chain {
uses authentication-keychain-augment; uses authentication-keychain-augment;
} }
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/ldp:peer" { + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/"
description "Peer list entry augmentation."; + "ldp:peer" {
description
"Peer list entry augmentation.";
uses peer-augment; uses peer-augment;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/ldp:peer/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/"
+ "ldp:authentication/ldp:authentication-type" { + "ldp:peer/ldp:authentication/ldp:authentication-type" {
if-feature key-chain; if-feature "key-chain";
description "Peer list entry authentication augmentation."; description
"Peer list entry authentication augmentation.";
case key-chain { case key-chain {
uses authentication-keychain-augment; uses authentication-keychain-augment;
} }
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/ldp:peer/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/"
+ "ldp:address-families/ldp:ipv4" { + "ldp:peer/ldp:address-families/ldp:ipv4" {
description description
"Peer list entry IPv4 augmentation."; "Peer list entry IPv4 augmentation.";
uses peer-af-policy-container; uses peer-af-policy-container;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/ldp:peer/" + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/"
+ "ldp:address-families/ldp-ext:ipv6" { + "ldp:peer/ldp:address-families/ldp-ext:ipv6" {
description description
"Peer list entry IPv6 augmentation."; "Peer list entry IPv6 augmentation.";
uses peer-af-policy-container; uses peer-af-policy-container;
} }
} }
]]> </sourcecode>
</figure>
<CODE ENDS>
]]>
</artwork>
</figure>
</section> </section>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Security Considerations</name> <name>Security Considerations</name>
<t> This specification inherits the security <t> This specification inherits the security
considerations captured in <xref target="RFC5920"/> and the LDP protocol specification documents, namely base LDP considerations captured in <xref target="RFC5920"/> and the LDP protocol specification documents, namely base LDP
<xref target="RFC5036"/>, LDP IPv6 <xref target="RFC7552"/>, LDP Capabili ties <xref target="RFC5036"/>, LDP IPv6 <xref target="RFC7552"/>, LDP Capabili ties
<xref target="RFC5561"/>, Typed Wildcard FEC <xref target="RFC5918"/>, LD P End-of-LIB <xref target="RFC5561"/>, Typed Wildcard FEC <xref target="RFC5918"/>, LD P End-of-LIB
<xref target="RFC5919"/>, and LDP Upstream Label Assignment <xref target="RFC5919"/>, and LDP Upstream Label Assignment
<xref target="RFC6389"/>. <xref target="RFC6389"/>.
</t> </t>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>YANG model</name> <name>YANG Data Model</name>
<t> The YANG modules specified in this document defines a schema for data that i s designed to be accessed via network management protocols such as NETCONF <xref target="RFC6241"/> or RESTCONF <xref target="RFC8040"/>. The lowest NETCONF lay er is the secure transport layer, and the mandatory-to-implement secure transpor t is Secure Shell (SSH) <xref target="RFC6242"/>. The lowest RESTCONF layer is H TTPS, and the mandatory-to-implement secure transport is TLS <xref target="RFC84 46"/>. </t> <t> The YANG modules specified in this document define a schema for data that is designed to be accessed via network management protocols such as NETCONF <xref target="RFC6241"/> or RESTCONF <xref target="RFC8040"/>. The lowest NETCONF laye r is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) <xref target="RFC6242"/>. The lowest RESTCONF layer is HT TPS, and the mandatory-to-implement secure transport is TLS <xref target="RFC844 6"/>. </t>
<t> The Network Configuration Access Control Model (NACM) <xref target="RFC8341" /> provides the means to restrict access for particular NETCONF or RESTCONF user s to a preconfigured subset of all available NETCONF or RESTCONF protocol operat ions and content. </t> <t> The Network Configuration Access Control Model (NACM) <xref target="RFC8341" /> provides the means to restrict access for particular NETCONF or RESTCONF user s to a preconfigured subset of all available NETCONF or RESTCONF protocol operat ions and content. </t>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Writable nodes</name> <name>Writable Nodes</name>
<t> There are a number of data nodes defined in this YANG module that are writab <t> There are a number of data nodes defined in these YANG modules that are writ
le/creatable/deletable (i.e., config true, which is the default). These data nod able/creatable/deletable (i.e., config true, which is the default). These data n
es may be considered sensitive or vulnerable in some network environments. Write odes may be considered sensitive or vulnerable in some network environments. Wri
operations (e.g., edit-config) to these data nodes without proper protection ca te operations (e.g., edit-config) to these data nodes without proper protection
n have a negative effect on network operations. </t> can have a negative effect on network operations. </t>
<t> For LDP, the ability to modify MPLS LDP configuration may allow the entire M PLS LDP domain to be compromised including forming LDP adjacencies and/or peer s essions with unauthorized <t> For LDP, the ability to modify MPLS LDP configuration may allow the entire M PLS LDP domain to be compromised including forming LDP adjacencies and/or peer s essions with unauthorized
routers to mount a massive Denial-of-Service (DoS) attack. In particular, follin g are the subtrees and data nodes that are sensitivite and vulnerable: </t> routers to mount a massive Denial-of-Service (DoS) attack. In particular, the fo llowing are the subtrees and data nodes that are sensitive and vulnerable: </t>
<ul> <dl>
<li> /mpls-ldp/discovery/interfaces/interface: Adding LDP on any unprotected i <dt>/mpls-ldp/discovery/interfaces/interface:
nterface could allow an LDP hello adjacency to be formed with an unauthorized an </dt>
d malicious neighbor. Once an hello adjacency is formed, a peer session could pr <dd>Adding LDP on any unprotected interface could allow an LDP Hello adjacency
ogress with this neighbor. </li> to be formed with an unauthorized and malicious neighbor. Once a Hello
<li> /mpls-ldp/discovery/targeted/hello-accept: Allowing acceptance of targete adjacency is formed, a peer session could progress with this neighbor.
d-hellos could open LDP to DoS attacks related to incoming targeted hellos from </dd>
malicious sources. </li>
<li> /mpls-ldp/peers/authentication: Allowing a peer session establishement is <dt>/mpls-ldp/discovery/targeted/hello-accept:
typically controlled via LDP authentication where a proper and secure authentic </dt>
ation password/key management is warranted.</li> <dd> Allowing acceptance of targeted-hellos could open LDP to DoS attacks
<li> /mpls-ldp/peers/peer/authentication: Same as above. </li> related to incoming targeted hellos from malicious sources.
</ul> </dd>
<dt>/mpls-ldp/peers/authentication:
</dt>
<dd>Allowing a peer session establishment is typically controlled via LDP
authentication where a proper and secure authentication password/key
management is warranted.
</dd>
<dt>/mpls-ldp/peers/peer/authentication:
</dt>
<dd>Same as above.
</dd>
</dl>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Readable nodes</name> <name>Readable Nodes</name>
<t> Some of the readable data nodes in this YANG module may be considered sensit ive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. Th ese are the subtrees and data nodes and their sensitivity/vulnerability: </t> <t> Some of the readable data nodes in these YANG modules may be considered sens itive or vulnerable in some network environments. It is thus important to contro l read access (e.g., via get, get-config, or notification) to these data nodes. These are the subtrees and data nodes and their sensitivity/vulnerability: </t>
<t>The exposure of LDP databases (such as hello adjacencies, peers, address bind ings, and fec-label bindings) beyond the scope of the LDP admin domain may be un desirable. The relevant subtrees and data nodes are as follows: </t> <t>The exposure of LDP databases (such as Hello adjacencies, peers, address bind ings, and FEC-Label bindings) beyond the scope of the LDP admin domain may be un desirable. The relevant subtrees and data nodes are as follows: </t>
<ul> <ul>
<li> /mpls-ldp/global/address-families/ipv4/bindings/address </li> <li> /mpls-ldp/global/address-families/ipv4/bindings/address </li>
<li> /mpls-ldp/global/address-families/ipv6/bindings/address </li> <li> /mpls-ldp/global/address-families/ipv6/bindings/address </li>
<li> /mpls-ldp/global/address-families/ipv4/bindings/fec-label</li> <li> /mpls-ldp/global/address-families/ipv4/bindings/fec-label</li>
<li> /mpls-ldp/global/address-families/ipv6/bindings/fec-label</li> <li> /mpls-ldp/global/address-families/ipv6/bindings/fec-label</li>
<li> /mpls-ldp/discovery/interfaces/interface/address-families/ipv4/hello-ad jacencies </li> <li> /mpls-ldp/discovery/interfaces/interface/address-families/ipv4/hello-ad jacencies </li>
<li> /mpls-ldp/discovery/interfaces/interface/address-families/ipv6/hello-ad jacencies </li> <li> /mpls-ldp/discovery/interfaces/interface/address-families/ipv6/hello-ad jacencies </li>
<li> /mpls-ldp/discovery/targeted/address-families/ipv4/hello-adjacencies </ li> <li> /mpls-ldp/discovery/targeted/address-families/ipv4/hello-adjacencies </ li>
<li> /mpls-ldp/discovery/targeted/address-families/ipv6/hello-adjacencies </ li> <li> /mpls-ldp/discovery/targeted/address-families/ipv6/hello-adjacencies </ li>
<li> /mpls-ldp/peers</li> <li> /mpls-ldp/peers</li>
</ul> </ul>
<t> The configuration for LDP peer authentication is supported via the <t> The configuration for LDP peer authentication is supported via the
specification of key-chain <xref target="RFC8040"/>, or via direct key-chain specification <xref target="RFC8177"/> or via direct
specification of a key associated with a crypto algorithm (such as MD5). specification of a key associated with a crypto algorithm (such as MD5).
The relevant subtrees and data nodes are as follows: </t> The relevant subtrees and data nodes are as follows: </t>
<ul> <ul>
<li> /mpls-ldp/peers/authentication </li> <li> /mpls-ldp/peers/authentication </li>
<li> /mpls-ldp/peers/peer/authentication </li> <li> /mpls-ldp/peers/peer/authentication </li>
</ul> </ul>
<t> The actual authentication key data (whether locally specified or part of a k <t> The actual authentication key data (whether locally specified or part of a
ey-chain) is sensitive and needs to be kept secret from unauthorized parties. key-chain) is sensitive and needs to be kept secret from unauthorized parties.
For key-chain based authentication, this model inherits the security For key-chain-based authentication, this model inherits the security
considerations of <xref target="RFC8040"/> (that includes the considerations considerations of <xref target="RFC8040"/> (that includes the considerations
with with respect to the local storage and handling of authentication keys). A
respect to the local storage and handling of authentication keys). A similar similar procedure for storage and access to direct keys is warranted.
procedure for storage and access to direct key is warranted.
</t> </t>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>RPC operations</name> <name>RPC Operations</name>
<t>Some of the RPC operations in this YANG module may be considered sensitive or <t>Some of the RPC operations in these YANG modules may be considered sensitive
vulnerable in some network environments. It is thus important to control access or vulnerable in some network environments. It is thus important to control acce
to these operations otherwise control plane flaps, network outages, and DoS att ss to these operations; otherwise, control plane flaps, network outages, and DoS
acks are possible. The RPC operations are: </t> attacks are possible. The RPC operations are: </t>
<ul> <ul>
<li> mpls-ldp-clear-peer</li> <li> mpls-ldp-clear-peer</li>
<li> mpls-ldp-clear-hello-adjacency</li> <li> mpls-ldp-clear-hello-adjacency</li>
</ul> </ul>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Notifications</name> <name>Notifications</name>
skipping to change at line 3936 skipping to change at line 3946
significant notification load and possible side effects on the system stabilit y. significant notification load and possible side effects on the system stabilit y.
</t> </t>
</section> </section>
</section> </section>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>IANA Considerations</name> <name>IANA Considerations</name>
<t> This document requests the registration of the following URIs in the I <t>Per this document, the following URIs have been registered in the IETF
ETF "XML "XML
registry" <xref target="RFC3688"/>: </t> Registry" <xref target="RFC3688"/>: </t>
<table>
<name>URIs</name>
<thead>
<tr>
<th align="left">URI</th>
<th align="left">Registrant</th>
<th align="left">XML</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">urn:ietf:params:xml:ns:yang:ietf-mpls-ldp</td>
<td align="left">The IESG</td>
<td align="left">N/A</td>
</tr>
<tr>
<td align="left">urn:ietf:params:xml:ns:yang:ietf-mpls-ldp-extended</
td>
<td align="left">The IESG</td>
<td align="left">N/A</td>
</tr>
</tbody>
</table>
<t> This document requests the registration of the following YANG modules <dl spacing="compact">
in the <dt>URI:
"YANG Module Names" registry <xref target="RFC6020"/>: </t> </dt>
<dd>urn:ietf:params:xml:ns:yang:ietf-mpls-ldp
</dd>
<table> <dt>Registrant:
<name>YANG Modules</name> </dt>
<thead> <dd>The IESG
<tr> </dd>
<th align="left">Name</th>
<th align="left">Namespace</th>
<th align="left">Prefix</th>
<th align="left">Reference</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">ietf-mpls-ldp</td>
<td align="left">urn:ietf:params:xml:ns:yang:ietf-mpls-ldp</td>
<td align="left">ldp</td>
<td align="left">This document</td>
</tr>
<tr>
<td align="left">ietf-mpls-ldp-extended</td>
<td align="left">urn:ietf:params:xml:ns:yang:ietf-mpls-ldp-extended</
td>
<td align="left">ldp-ext</td>
<td align="left">This document</td>
</tr>
</tbody>
</table>
<t> -- RFC Editor: Replace "this document" with the document RFC number at <dt>XML:
time of publication, </dt>
and remove this note. <dd>N/A
</t> </dd>
</section> </dl>
<section numbered="true" toc="default"> <dl spacing="compact">
<name>Acknowledgments</name>
<t>The authors would like to acknowledge Eddie Chami, Nagendra Kumar, Man
nan Venkatesan, and
Pavan Beeram for their contribution to this document. </t>
<t> We also acknowledge Ladislav Lhotka, Jan Lindblad, Tom Petch, Yingzhe <dt>URI:
n Qu, and Benjamin Kaduk for their detailed review of the model during WG and IE </dt>
SG.</t> <dd>urn:ietf:params:xml:ns:yang:ietf-mpls-ldp-extended
</dd>
</section> <dt>Registrant:
</dt>
<dd>The IESG
</dd>
<section numbered="true" toc="default"> <dt>XML:
<name>Contributors</name> </dt>
<dd>N/A
</dd>
<artwork> </dl>
Danial Johari <t>Per this document, the following YANG modules have been registered in t
Cisco Systems he
Email: dajohari@cisco.com "YANG Module Names" registry <xref target="RFC6020"/>: </t>
Loa Andersson <dl spacing="compact">
Huawei Technologies
Email: loa@pi.nu
Jeff Tantsura <dt>Name:
Apstra </dt>
Email: jefftant.ietf@gmail.com <dd>ietf-mpls-ldp
</dd>
Matthew Bocci <dt>Namespace:
Nokia </dt>
Email: matthew.bocci@nokia.com <dd>urn:ietf:params:xml:ns:yang:ietf-mpls-ldp
</dd>
Reshad Rahman <dt>Prefix:
Cisco Systems </dt>
Email: rrahman@cisco.com <dd>ldp
</dd>
Stephane Litkowski <dt>Reference:
Cisco Systems </dt>
Email: slitkows@cisco.com <dd>RFC 9070
</dd>
</dl>
</artwork> <dl spacing="compact">
</section> <dt>Name:
</dt>
<dd>ietf-mpls-ldp-extended
</dd>
</middle> <dt>Namespace:
</dt>
<dd>urn:ietf:params:xml:ns:yang:ietf-mpls-ldp-extended
</dd>
<!-- *****BACK MATTER ***** --> <dt>Prefix:
</dt>
<dd>ldp-ext
</dd>
<back> <dt>Reference:
</dt>
<dd>RFC 9070
</dd>
<!-- References split into informative and normative --> </dl>
<!-- There are 2 ways to insert reference entries from the citation libraries </section>
:
1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (
as shown)
2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml
"?> here
(for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.x
ml")
Both are cited textually in the same manner: by using xref elements. </middle>
If you use the PI option, xml2rfc will, by default, try to find included fil
es in the same <back>
directory as the including file. You can also define the XML_LIBRARY environ
ment variable <displayreference target="I-D.ietf-mpls-mldp-yang" to="MPLS-MLDP-YANG"/>
with a value containing a set of directories to search. These can be either
in the local
filing system or remote ones accessed by http (http://domain/dir/... ).-->
<references title="Normative References"> <references title="Normative References">
<?rfc include="reference.RFC.3688.xml"?>
<?rfc include="reference.RFC.3478.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3688.
<?rfc include="reference.RFC.5036.xml"?> xml"/>
<?rfc include="reference.RFC.5331.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3478.
<?rfc include="reference.RFC.5443.xml"?> xml"/>
<?rfc include="reference.RFC.5561.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5036.
<?rfc include="reference.RFC.5918.xml"?> xml"/>
<?rfc include="reference.RFC.5919.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5331.
<?rfc include="reference.RFC.5920.xml"?> xml"/>
<?rfc include="reference.RFC.6020.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5443.
<?rfc include="reference.RFC.7950.xml"?> xml"/>
<?rfc include="reference.RFC.6241.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5561.
<?rfc include="reference.RFC.6242.xml"?> xml"/>
<?rfc include="reference.RFC.6389.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5918.
<?rfc include="reference.RFC.6991.xml"?> xml"/>
<?rfc include="reference.RFC.8344.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5919.
<?rfc include="reference.RFC.7277.xml"?> xml"/>
<?rfc include="reference.RFC.7552.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5920.
<?rfc include="reference.RFC.8040.xml"?> xml"/>
<?rfc include="reference.RFC.8177.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6020.
<?rfc include="reference.RFC.8446.xml"?> xml"/>
<?rfc include="reference.RFC.8294.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7950.
<?rfc include="reference.RFC.8341.xml"?> xml"/>
<?rfc include="reference.RFC.8342.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6241.
<?rfc include="reference.RFC.8343.xml"?> xml"/>
<?rfc include="reference.RFC.8349.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6242.
<?rfc include="reference.RFC.8407.xml"?> xml"/>
<?rfc include="reference.RFC.8529.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6389.
<?rfc include="reference.I-D.ietf-rtgwg-policy-model.xml"?> 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.8344.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7552.
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.8177.
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.8294.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8341.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8342.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8343.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8349.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8407.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8529.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9067.
xml"/>
</references> </references>
<references title="Informative References"> <references title="Informative References">
<?rfc include="reference.RFC.4364.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4364.
<?rfc include="reference.RFC.7307.xml"?> xml"/>
<?rfc include="reference.RFC.7951.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7307.
<?rfc include="reference.RFC.8340.xml"?> xml"/>
<?rfc include="reference.I-D.ietf-mpls-mldp-yang.xml"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7951.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8340.
xml"/>
<reference anchor='I-D.ietf-mpls-mldp-yang'>
<front>
<title>YANG Data Model for MPLS mLDP</title>
<author initials='K' surname='Raza' fullname='Kamran Raza' role="editor">
<organization />
</author>
<author initials='X' surname='Liu' fullname='Xufeng Liu'>
<organization />
</author>
<author initials='S' surname='Esale' fullname='Santosh Esale'>
<organization />
</author>
<author initials='L' surname='Andersson' fullname='Loa Andersson'>
<organization />
</author>
<author initials='J' surname='Tantsura' fullname='Jeff Tantsura'>
<organization />
</author>
<author initials='S' surname='Krishnaswamy' fullname='Sowmya Krishnaswamy'>
<organization />
</author>
<date year='2021' month='November' day='11' />
</front>
<seriesInfo name='Internet-Draft' value='draft-ietf-mpls-mldp-yang-10'/>
<format type='TXT' target='https://www.ietf.org/internet-drafts/draft-ietf-mpls-
mldp-yang-10.txt'/>
</reference>
</references> </references>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Data Tree Example</name> <name>Data Tree Example</name>
<t> <t>
This section contains an example of an instance data tree in the JSON This section contains an example of an instance data tree in the JSON
encoding <xref target="RFC7951"/>, containing both configuration and encoding <xref target="RFC7951"/>, containing both configuration and
state data. state data.
</t> </t>
<figure> <figure anchor="ex_top">
<name>Example topology</name> <name>Example Topology</name>
<artwork> <artwork>
+---------------------+ +---------------------+
| | | |
| Router 203.0.113.1 | | Router 203.0.113.1 |
| | | |
+----------+----------+ +----------+----------+
|eth1 |eth1
|2001:db8:0:1::1/64 |2001:db8:0:1::1/64
| |
| |
|2001:db8:0:1::2/64 |2001:db8:0:1::2/64
+----------+----------+ +----------+----------+
| | | | | |
| Another Router +---------| 2001:db8:0:2::/64 | Another Router +---------| 2001:db8:0:2::/64
| | | | | |
+---------------------+ +---------------------+
</artwork></figure> </artwork></figure>
<t> <t>
The configuration instance data tree for Router 203.0.113.1 in the The configuration instance data tree for Router 203.0.113.1 in <xref
above figure could be as follows: target="ex_top"/> could be as follows:
</t> </t>
<figure> <figure>
<name>Example Configuration data in JSON</name> <name>Example Configuration Data in JSON</name>
<artwork> <sourcecode type="json">
{ {
"ietf-interfaces:interfaces": { "ietf-interfaces:interfaces": {
"interface": [ "interface": [
{ {
"name": "eth1", "name": "eth1",
"description": "An interface with LDP enabled.", "description": "An interface with LDP enabled.",
"type": "iana-if-type:ethernetCsmacd", "type": "iana-if-type:ethernetCsmacd",
"ietf-ip:ipv6": { "ietf-ip:ipv6": {
"address": [ "address": [
skipping to change at line 4190 skipping to change at line 4205
] ]
} }
} }
} }
} }
] ]
} }
} }
} }
</artwork></figure> </sourcecode></figure>
<t> <t>
The corresponding operational state data for Router 203.0.113.1 The corresponding operational state data for Router 203.0.113.1
could be as follows: could be as follows:
</t> </t>
<figure> <figure>
<name>Example Operational data in JSON</name> <name>Example Operational Data in JSON</name>
<artwork> <sourcecode type="json">
{ {
"ietf-interfaces:interfaces": { "ietf-interfaces:interfaces": {
"interface": [ "interface": [
{ {
"name": "eth1", "name": "eth1",
"description": "An interface with LDP enabled.", "description": "An interface with LDP enabled.",
"type": "iana-if-type:ethernetCsmacd", "type": "iana-if-type:ethernetCsmacd",
"phys-address": "00:00:5e:00:53:01", "phys-address": "00:00:5e:00:53:01",
"oper-status": "up", "oper-status": "up",
"statistics": { "statistics": {
skipping to change at line 4344 skipping to change at line 4358
} }
} }
] ]
} }
} }
} }
] ]
} }
} }
} }
</sourcecode></figure>
</artwork></figure>
</section> </section>
<!-- Change Log <section numbered="false" toc="default">
v08 2020-02-27 KR IESG Review <name>Acknowledgments</name>
--> <t>The authors would like to acknowledge <contact
fullname="Eddie Chami"/>, <contact fullname="Nagendra
Kumar"/>, <contact fullname="Mannan Venkatesan"/>, and <contact
fullname="Pavan Beeram"/> for their contribution to this
document. </t>
<t> We also acknowledge <contact fullname="Ladislav Lhotka"/>,
<contact fullname="Jan Lindblad"/>, <contact fullname="Tom
Petch"/>, <contact fullname="Yingzhen Qu"/>, and <contact
fullname="Benjamin Kaduk"/> for their detailed review of the
model during WG and IESG processes.</t>
</section>
<section numbered="false" toc="default">
<name>Contributors</name>
<contact fullname="Danial Johari">
<organization>Cisco Systems</organization>
<address>
<email>dajohari@cisco.com</email>
</address>
</contact>
<contact fullname="Loa Andersson">
<organization>Huawei Technologies</organization>
<address>
<email>loa@pi.nu</email>
</address>
</contact>
<contact fullname="Jeff Tantsura">
<organization>Apstra</organization>
<address>
<email>jefftant.ietf@gmail.com</email>
</address>
</contact>
<contact fullname="Matthew Bocci">
<organization>Nokia</organization>
<address>
<email> matthew.bocci@nokia.com</email>
</address>
</contact>
<contact fullname="Reshad Rahman">
<address>
<email>reshad@yahoo.com</email>
</address>
</contact>
<contact fullname="Stephane Litkowski">
<organization>Cisco Systems</organization>
<address>
<email>slitkows@cisco.com</email>
</address>
</contact>
</section>
</back> </back>
</rfc> </rfc>
 End of changes. 576 change blocks. 
1466 lines changed or deleted 1427 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/