IS-IS Working Group S. Litkowski
Internet-Draft Orange
Intended status: Standards Track D. Yeung
Expires: March 24, 2017 A. Lindem
Cisco Systems
J. Zhang
Juniper Networks
L. Lhotka
CZ.NIC
September 20, 2016
YANG Data Model for IS-IS protocol
draft-ietf-isis-yang-isis-cfg-09
Abstract
This document defines a YANG data model that can be used to configure
and manage IS-IS protocol on network elements. It also defined an
extension module for segment routing configuration and operation.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 24, 2017.
Litkowski, et al. Expires March 24, 2017 [Page 1]
Internet-Draft isis-cfg September 2016
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 3
2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3
2.1. IS-IS Configuration . . . . . . . . . . . . . . . . . . . 9
2.2. Multitopology Parameters . . . . . . . . . . . . . . . . 10
2.3. Per-Level Parameters . . . . . . . . . . . . . . . . . . 10
2.4. Per-Interface Parameters . . . . . . . . . . . . . . . . 12
2.5. ISO parameters . . . . . . . . . . . . . . . . . . . . . 12
2.6. IP FRR . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.7. Operational State . . . . . . . . . . . . . . . . . . . . 13
3. RPC Operations . . . . . . . . . . . . . . . . . . . . . . . 13
4. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 14
5. Segment Routing . . . . . . . . . . . . . . . . . . . . . . . 18
5.1. Segment Routing activation . . . . . . . . . . . . . . . 20
5.2. Advertising mapping server policy . . . . . . . . . . . . 20
5.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 20
6. Interaction with Other YANG Modules . . . . . . . . . . . . . 21
7. IS-IS YANG Module . . . . . . . . . . . . . . . . . . . . . . 21
8. IS-IS Segment Routing YANG Module . . . . . . . . . . . . . . 100
9. Security Considerations . . . . . . . . . . . . . . . . . . . 114
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 115
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 115
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 115
13. Normative References . . . . . . . . . . . . . . . . . . . . 116
Appendix A. Example: NETCONF <get> Reply . . . . . . . . . . . . 117
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 120
Litkowski, et al. Expires March 24, 2017 [Page 2]
Internet-Draft isis-cfg September 2016
1. Introduction
This document defines a YANG data model for IS-IS routing protocol.
The data model covers configuration of an IS-IS routing protocol
instance as well as operational states.
1.1. Tree diagram
A simplified graphical representation of the data model is presented
in Section 2.
The meaning of the symbols in these diagrams is as follows:
o Brackets "[" and "]" enclose list keys.
o Curly braces "{" and "}" contain names of optional features that
make the corresponding node conditional.
o Abbreviations before data node names: "rw" means configuration
(read-write), and "ro" state data (read-only).
o Symbols after data node names: "?" means an optional node and "*"
denotes a "list" or "leaf-list".
o Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not
shown.
2. Design of the Data Model
The IS-IS YANG module is divided in two main "isis" containers that
are augmenting the "routing-protocol" lists in ietf-routing module
with specific IS-IS parameters.
One container contains the writable parameters, while the other
contains the operational states.
The figure below describe the overall structure of the isis YANG
module:
module: ietf-isis
augment /rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route:
+--ro metric? uint32
+--ro tag* uint64
+--ro route-type? enumeration
Litkowski, et al. Expires March 24, 2017 [Page 3]
Internet-Draft isis-cfg September 2016
augment /if:interfaces/if:interface:
+--rw clns-mtu? uint16
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol:
+--rw isis
+--rw enable? boolean {admin-control}?
+--rw level-type? level
+--rw system-id? system-id
+--rw maximum-area-addresses? uint8 {maximum-area-addresses}?
+--rw area-address* area-address
+--rw mpls
| +--rw ipv4-router-id? inet:ipv4-address {ipv4-router-id}?
| +--rw ipv6-router-id? inet:ipv6-address {ipv6-router-id}?
| +--rw igp-ldp-sync {igp-ldp-sync}?
+--rw reference-bandwidth? uint32 {reference-bandwidth}?
+--rw lsp-mtu? uint16
+--rw lsp-lifetime? uint16
+--rw lsp-refresh? uint16 {lsp-refresh}?
+--rw graceful-restart {graceful-restart}?
| +--rw enable? boolean
+--rw node-tag {node-tag}?
| +--rw node-tag* [tag]
| ...
+--rw authentication
| +--rw (authentication-type)?
| | ...
| +--rw level-1
| | ...
| +--rw level-2
| ...
+--rw metric-type
| +--rw value? enumeration
| +--rw level-1
| | ...
| +--rw level-2
| ...
+--rw default-metric
| +--rw value? wide-metric
| +--rw level-1
| | ...
| +--rw level-2
| ...
+--rw afs
| +--rw af* [af] {nlpid-control}?
| ...
+--rw preference
| +--rw (granularity)?
| ...
+--rw overload
Litkowski, et al. Expires March 24, 2017 [Page 4]
Internet-Draft isis-cfg September 2016
| +--rw status? boolean
+--rw overload-max-metric {overload-max-metric}?
| +--rw timeout? uint16
+--rw fast-reroute {fast-reroute}?
| +--rw lfa {lfa}?
+--rw multi-topology {multi-topology}?
| +--rw topology* [name]
| ...
+--rw interfaces
+--rw interface* [name]
...
augment /rt:routing-state/rt:control-plane-protocols/rt:control-plane-protocol:
+--ro isis
+--ro enable? boolean {admin-control}?
+--ro level-type? level
+--ro system-id? system-id
+--ro maximum-area-addresses? uint8 {maximum-area-addresses}?
+--ro area-address* area-address
+--ro mpls
| +--ro ipv4-router-id? inet:ipv4-address {ipv4-router-id}?
| +--ro ipv6-router-id? inet:ipv6-address {ipv6-router-id}?
| +--ro igp-ldp-sync {igp-ldp-sync}?
+--ro reference-bandwidth? uint32 {reference-bandwidth}?
+--ro lsp-mtu? uint16
+--ro lsp-lifetime? uint16
+--ro lsp-refresh? uint16 {lsp-refresh}?
+--ro graceful-restart {graceful-restart}?
| +--ro enable? boolean
+--ro node-tag {node-tag}?
| +--ro node-tag* [tag]
| ...
+--ro authentication
| +--ro (authentication-type)?
| | ...
| +--ro level-1
| | ...
| +--ro level-2
| ...
+--ro metric-type
| +--ro value? enumeration
| +--ro level-1
| | ...
| +--ro level-2
| ...
+--ro default-metric
| +--ro value? wide-metric
| +--ro level-1
| | ...
Litkowski, et al. Expires March 24, 2017 [Page 5]
Internet-Draft isis-cfg September 2016
| +--ro level-2
| ...
+--ro afs
| +--ro af* [af] {nlpid-control}?
| ...
+--ro preference
| +--ro (granularity)?
| ...
+--ro overload
| +--ro status? boolean
+--ro overload-max-metric {overload-max-metric}?
| +--ro timeout? uint16
+--ro fast-reroute {fast-reroute}?
| +--ro lfa {lfa}?
| +--ro protected-routes
| | ...
| +--ro nonprotected-routes
| | ...
| +--ro protection-statistics* [frr-protection-method]
| ...
+--ro topologies* [name]
| +--ro name leafref
| +--ro fast-route {fast-reroute}?
| ...
+--ro system-counters
| +--ro level* [level]
| ...
+--ro interfaces
| +--ro interface* [interface]
| ...
+--ro spf-log
| +--ro event* [id]
| ...
+--ro lsp-log
| +--ro event* [id]
| ...
+--ro database
| +--ro level-db* [level]
| ...
+--ro hostnames
+--ro hostname* [system-id]
...
rpcs:
+---x clear-adjacency
| +--ro input
| +--ro routing-protocol-instance-name instance-state-ref
| +--ro level? level
| +--ro interface? string
Litkowski, et al. Expires March 24, 2017 [Page 6]
Internet-Draft isis-cfg September 2016
+---x clear-database
+--ro input
+--ro routing-protocol-instance-name instance-state-ref
+--ro level? level
notifications:
+---n database-overload
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro overload? enumeration
+---n lsp-too-large
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro pdu-size? uint32
| +--ro lsp-id? lsp-id
+---n corrupted-lsp-detected
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro lsp-id? lsp-id
+---n attempt-to-exceed-max-sequence
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro lsp-id? lsp-id
+---n id-len-mismatch
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro pdu-field-len? uint8
| +--ro raw-pdu? binary
+---n max-area-addresses-mismatch
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro max-area-addresses? uint8
| +--ro raw-pdu? binary
+---n own-lsp-purge
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro lsp-id? lsp-id
Litkowski, et al. Expires March 24, 2017 [Page 7]
Internet-Draft isis-cfg September 2016
+---n sequence-number-skipped
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro lsp-id? lsp-id
+---n authentication-type-failure
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro raw-pdu? binary
+---n authentication-failure
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro raw-pdu? binary
+---n version-skew
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro protocol-version? uint8
| +--ro raw-pdu? binary
+---n area-mismatch
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro raw-pdu? binary
+---n rejected-adjacency
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro raw-pdu? binary
| +--ro reason? string
+---n protocols-supported-mismatch
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
Litkowski, et al. Expires March 24, 2017 [Page 8]
Internet-Draft isis-cfg September 2016
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro raw-pdu? binary
| +--ro protocols* uint8
+---n lsp-error-detected
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro lsp-id? lsp-id
| +--ro raw-pdu? binary
| +--ro error-offset? uint32
| +--ro tlv-type? uint8
+---n adjacency-change
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro neighbor? string
| +--ro neighbor-system-id? system-id
| +--ro level? level
| +--ro state? enumeration
| +--ro reason? string
+---n lsp-received
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro lsp-id? lsp-id
| +--ro sequence? uint32
| +--ro received-timestamp? yang:timestamp
| +--ro neighbor-system-id? system-id
+---n lsp-generation
+--ro instance-name? string
+--ro instance-level? level
+--ro lsp-id? lsp-id
+--ro sequence? uint32
+--ro send-timestamp? yang:timestamp
2.1. IS-IS Configuration
The IS-IS configuration container is divided in:
o Global parameters.
Litkowski, et al. Expires March 24, 2017 [Page 9]
Internet-Draft isis-cfg September 2016
o Per interface configuration (see Section 2.4).
It would to up to extension modules to augment this model to support
vendor specific parameters.
2.2. Multitopology Parameters
The "topologies" list is used to enable support of MT extensions for
specific address families.
Each topology should refer to an existing RIB.
Some specific parameters could be defined for a specific topology at
global level and also at interface level.
2.3. Per-Level Parameters
Some parameters support per level configuration. In this case, the
parameter is built as a container with three levels of configuration
:
o top level : corresponds to level-1-2, so the configuration applies
to both levels.
o level-1 : corresponds to level-1 specific parameter.
o level-2 : corresponds to level-2 specific parameter.
+--rw priority
| +--rw value? uint8
| +--rw level-1
| | +--rw value? uint8
| +--rw level-2
| +--rw value? uint8
Example :
<priority>
<value>250</value>
<level-1>
<value>100</value>
</level-1>
<level-2>
<value>200</value>
</level-2>
</priority>
Litkowski, et al. Expires March 24, 2017 [Page 10]
Internet-Draft isis-cfg September 2016
An implementation SHOULD prefer a level specific parameter over
level-all parameter. As example, if priority is 100 for level-1, 200
for level-2 and 250 for top level configuration, the implementation
should use 100 for level-1 and 200 for level-2.
Some parameters like overload bit and route preference are not
modelled for per level configuration. If an implementation supports
per level configuration for such parameter, the implementation SHOULD
augment the current model by adding level-1 and level-2 containers
and reusing existing configuration groupings.
Example of augmentation :
augment "/rt:routing/" +
"rt:routing-protocols/rt:routing-protocol"+
"/isis:isis/isis:overload" {
when "rt:type = 'isis:isis'" {
description
"This augment IS-IS routing protocol when used";
}
description
"This augments IS-IS overload configuration
with per level configuration.";
container level-1 {
uses isis:overload-global-cfg;
description
"Level 1 configuration.";
}
container level-2 {
uses isis:overload-global-cfg;
description
"Level 2 configuration.";
}
}
Moreover, if an implementation does not support per level
configuration for a parameter, like priority, which has per level
configuration, the implementation SHOULD advertise a deviation to
announce the non support of the level-1 and level-2 containers.
Finally, if an implementation supports per level configuration but
does not support the level-1-2 configuration, it SHOULD also
advertise a deviation.
Litkowski, et al. Expires March 24, 2017 [Page 11]
Internet-Draft isis-cfg September 2016
2.4. Per-Interface Parameters
The per-interface section of the IS-IS instance describes the
interface specific parameters.
The interface is a reference to an interface in the Interface YANG
model.
Each interface has interface-specific parameters that may have a
different value per level as described in previous section. An
interface-specific parameter always override an IS-IS global
parameter .
Some parameters like hello-padding are defined as containers to
permit easy extension by vendor specific modules.
TODO : interfaces.tree
2.5. ISO parameters
Some ISO parameters may be required.
This module augments interface configuration model to support ISO
configuration parameters.
The clns-mtu can be defined under the interface.
2.6. IP FRR
This YANG model supports LFA and remote LFA as IP FRR techniques.
The "fast-reroute" container may be augmented by other models to
support other IPFRR flavors (MRT ...).
The current version of the model supports activation of LFA and
remote LFA at interface only. The global "lfa" container is present
but kept empty to permit augmentation with vendor specific properties
like policies.
Remote LFA is considered as a child of LFA. Remote LFA cannot be
enabled if LFA is not enabled.
The "candidate-disabled" permit to mark an interface to not be used
as a backup.
Litkowski, et al. Expires March 24, 2017 [Page 12]
Internet-Draft isis-cfg September 2016
2.7. Operational State
"isis" container provides operational states for IS-IS. This
container is divided in multiple components:
o system-counters : provides statistical informations about the
global system.
o interface : provides configuration state information for each
interface.
o adjacencies: provides state information about current IS-IS
adjacencies.
o spf-log: provides information about SPF events on the node.
o lsp-log: provides information about LSP events on the node
(reception of an LSP or modification of local LSP).
o database: provides details on current LSDB.
o hostnames: provides information about system-id to hostname
mappings.
o fast-reroute: provides information about IP FRR.
3. RPC Operations
The "ietf-isis" module defines two RPC operations:
o clear-isis-database: reset the content of a particular IS-IS
database and restart database synchronization with the neighbors.
o clear-isis-adjacency: restart a particular set of IS-IS
adjacencies.
rpcs:
+---x clear-adjacency
| +--ro input
| +--ro routing-protocol-instance-name instance-state-ref
| +--ro level? level
| +--ro interface? string
+---x clear-database
+--ro input
+--ro routing-protocol-instance-name instance-state-ref
+--ro level? level
Litkowski, et al. Expires March 24, 2017 [Page 13]
Internet-Draft isis-cfg September 2016
4. Notifications
The "ietf-isis" module introduces some notifications :
database-overload : raised when overload condition is changed.
lsp-too-large : raised when the system tries to propagate a too
large PDU.
corrupted-lsp-detected : raised when the system find that an LSP
that was stored in memory has become corrupted.
attempt-to-exceed-max-sequence : This notification is sent when
the system wraps the 32-bit sequence counter of an LSP.
id-len-mismatch : This notification is sent when we receive a PDU
with a different value for the System ID length.
max-area-addresses-mismatch : This notification is sent when we
receive a PDU with a different value for the Maximum Area
Addresses.
own-lsp-purge : This notification is sent when the system receives
a PDU with its own system ID and zero age.
sequence-number-skipped : This notification is sent when the
system receives a PDU with its own system ID and different
contents. The system has to reissue the LSP with a higher
sequence number.
authentication-type-failure : This notification is sent when the
system receives a PDU with the wrong authentication type field.
authentication-failure : This notification is sent when the system
receives a PDU with the wrong authentication information.
version-skew : This notification is sent when the system receives
a PDU with a different protocol version number.
area-mismatch : This notification is sent when the system receives
a Hello PDU from an IS that does not share any area address.
rejected-adjacency : This notification is sent when the system
receives a Hello PDU from an IS but does not establish an
adjacency for some reason.
Litkowski, et al. Expires March 24, 2017 [Page 14]
Internet-Draft isis-cfg September 2016
protocols-supported-mismatch : This notification is sent when the
system receives a non pseudonode LSP that has no matching protocol
supported.
lsp-error-detected : This notification is sent when the system
receives a LSP with a parse error.
adjacency-change : This notification is sent when an IS-IS
adjacency moves to Up state or to Down state.
lsp-received : This notification is sent when a LSP is received.
lsp-generation : This notification is sent when a LSP is
regenerated.
notifications:
+---n database-overload
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro overload? enumeration
+---n lsp-too-large
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro pdu-size? uint32
| +--ro lsp-id? lsp-id
+---n corrupted-lsp-detected
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro lsp-id? lsp-id
+---n attempt-to-exceed-max-sequence
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro lsp-id? lsp-id
+---n id-len-mismatch
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro pdu-field-len? uint8
| +--ro raw-pdu? binary
+---n max-area-addresses-mismatch
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
Litkowski, et al. Expires March 24, 2017 [Page 15]
Internet-Draft isis-cfg September 2016
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro max-area-addresses? uint8
| +--ro raw-pdu? binary
+---n own-lsp-purge
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro lsp-id? lsp-id
+---n sequence-number-skipped
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro lsp-id? lsp-id
+---n authentication-type-failure
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro raw-pdu? binary
+---n authentication-failure
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro raw-pdu? binary
+---n version-skew
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro protocol-version? uint8
| +--ro raw-pdu? binary
+---n area-mismatch
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro raw-pdu? binary
+---n rejected-adjacency
Litkowski, et al. Expires March 24, 2017 [Page 16]
Internet-Draft isis-cfg September 2016
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro raw-pdu? binary
| +--ro reason? string
+---n protocols-supported-mismatch
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro raw-pdu? binary
| +--ro protocols* uint8
+---n lsp-error-detected
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro lsp-id? lsp-id
| +--ro raw-pdu? binary
| +--ro error-offset? uint32
| +--ro tlv-type? uint8
+---n adjacency-change
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro neighbor? string
| +--ro neighbor-system-id? system-id
| +--ro level? level
| +--ro state? enumeration
| +--ro reason? string
+---n lsp-received
| +--ro instance-name? string
| +--ro instance-level? level
| +--ro interface-name? string
| +--ro interface-level? level
| +--ro extended-circuit-id? extended-circuit-id
| +--ro lsp-id? lsp-id
| +--ro sequence? uint32
| +--ro received-timestamp? yang:timestamp
| +--ro neighbor-system-id? system-id
+---n lsp-generation
+--ro instance-name? string
Litkowski, et al. Expires March 24, 2017 [Page 17]
Internet-Draft isis-cfg September 2016
+--ro instance-level? level
+--ro lsp-id? lsp-id
+--ro sequence? uint32
+--ro send-timestamp? yang:timestamp
5. Segment Routing
The IS-IS SR YANG module is augmenting IS-IS module for both
configuration and operational states.
The IS-IS SR YANG module requires the base segment routing module
([I-D.ietf-spring-sr-yang]) to be supported as there is a strong
relationship between those modules.
The figure below describe the overall structure of the isis-sr YANG
module:
module: ietf-isis-sr
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/isis:isis:
+--rw segment-routing
| +--rw enabled? boolean
| +--rw bindings
| +--rw advertise
| | +--rw policies* string
| +--rw receive? boolean
+--rw protocol-srgb {sr:protocol-srgb}?
+--rw srgb* [lower-bound upper-bound]
+--rw lower-bound uint32
+--rw upper-bound uint32
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/isis:isis/
isis:interfaces/isis:interface:
+--rw segment-routing
+--rw adjacency-sid
+--rw advertise-adj-group-sid* [group-id]
| +--rw group-id uint32
+--rw advertise-protection? enumeration
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/isis:isis/
isis:interfaces/isis:interface/isis:fast-reroute:
+--rw ti-lfa {ti-lfa}?
+--rw enable? boolean
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/isis:isis/
isis:interfaces/isis:interface/isis:fast-reroute/isis:lfa/isis:remote-lfa:
+--rw use-segment-routing-path? boolean {remote-lfa-sr}?
augment /rt:routing-state/rt:control-plane-protocols/
rt:control-plane-protocol/isis:isis:
+--ro segment-routing
| +--ro enabled? boolean
| +--ro bindings
| +--ro advertise
| | +--ro policies* string
| +--ro receive? boolean
+--ro protocol-srgb {sr:protocol-srgb}?
Litkowski, et al. Expires March 24, 2017 [Page 18]
Internet-Draft isis-cfg September 2016
+--ro srgb* [lower-bound upper-bound]
+--ro lower-bound uint32
+--ro upper-bound uint32
augment /rt:routing-state/rt:control-plane-protocols/
rt:control-plane-protocol/isis:isis/
isis:interfaces/isis:interface:
+--ro segment-routing
+--ro adjacency-sid
+--ro advertise-adj-group-sid* [group-id]
| +--ro group-id uint32
+--ro advertise-protection? enumeration
augment /rt:routing-state/rt:control-plane-protocols/
rt:control-plane-protocol/isis:isis/
isis:interfaces/isis:interface/isis:adjacencies/isis:adjacency:
+--ro adjacency-sid* [value]
+--ro af? identityref
+--ro value uint32
+--ro weight? uint8
+--ro protection-requested? boolean
augment /rt:routing-state/rt:control-plane-protocols/
rt:control-plane-protocol/isis:isis/
isis:database/isis:level-db/isis:lsp/isis:extended-is-neighbor/
isis:neighbor:
+--ro sid-list* [value]
+--ro flags? bits
+--ro weight? uint8
+--ro neighbor-id? isis:system-id
+--ro value uint32
augment /rt:routing-state/rt:control-plane-protocols/
rt:control-plane-protocol/isis:isis/
isis:database/isis:level-db/isis:lsp/isis:mt-is-neighbor/
isis:neighbor:
+--ro sid-list* [value]
+--ro flags? bits
+--ro weight? uint8
+--ro neighbor-id? isis:system-id
+--ro value uint32
augment /rt:routing-state/rt:control-plane-protocols/
rt:control-plane-protocol/isis:isis/isis:database/
isis:level-db/isis:lsp/isis:extended-ipv4-reachability/
isis:prefixes:
+--ro sid-list* [value]
+--ro flags? bits
+--ro algorithm? uint8
+--ro value uint32
augment /rt:routing-state/rt:control-plane-protocols/
rt:control-plane-protocol/isis:isis/
isis:database/isis:level-db/isis:lsp/
isis:mt-extended-ipv4-reachability/isis:prefixes:
+--ro sid-list* [value]
+--ro flags? bits
+--ro algorithm? uint8
+--ro value uint32
augment /rt:routing-state/rt:control-plane-protocols/
rt:control-plane-protocol/isis:isis/
isis:database/isis:level-db/isis:lsp/
isis:ipv6-reachability/isis:prefixes:
+--ro sid-list* [value]
+--ro flags? bits
+--ro algorithm? uint8
+--ro value uint32
augment /rt:routing-state/rt:control-plane-protocols/
rt:control-plane-protocol/isis:isis/
isis:database/isis:level-db/isis:lsp/isis:mt-ipv6-reachability/
isis:prefixes:
+--ro sid-list* [value]
+--ro flags? bits
+--ro algorithm? uint8
+--ro value uint32
augment /rt:routing-state/rt:control-plane-protocols/
rt:control-plane-protocol/isis:isis/
isis:database/isis:level-db/isis:lsp:
Litkowski, et al. Expires March 24, 2017 [Page 19]
Internet-Draft isis-cfg September 2016
+--ro segment-routing-bindings* [fec range]
+--ro fec string
+--ro range uint16
+--ro flags? bits
+--ro weight? uint8
+--ro binding
+--ro prefix-sid
| +--ro sid-list* [value]
| +--ro flags? bits
| +--ro algorithm? uint8
| +--ro value uint32
+--ro ero-metric? uint32
+--ro ero
| +--ro address-family? identityref
| +--ro loose? boolean
| +--ro address? string
+--ro backup-ero
| +--ro address-family? identityref
| +--ro loose? boolean
| +--ro address? string
+--ro unnumbered-interface-id-ero
| +--ro router-id? string
| +--ro interface-id? uint32
+--ro backup-unnumbered-interface-id-ero
+--ro router-id? string
+--ro interface-id? uint32
5.1. Segment Routing activation
Activation of segment-routing IS-IS is done by setting the "enabled"
leaf to true. This triggers advertisement of segment-routing
extensions based on the configuration parameters that have been setup
using the base segment routing module.
5.2. Advertising mapping server policy
The base segment routing module defines mapping server policies. By
default, IS-IS will not advertise nor receive any mapping server
entry. The IS-IS segment-routing module permits to advertise one or
multiple mapping server policies through the "bindings/advertise/
policies" leaf-list. The "bindings/receive" leaf permits to enable
the reception of mapping server entries.
5.3. IP Fast reroute
IS-IS SR model augments the fast-reroute container under interface.
It brings the ability to activate TI-LFA (topology independent LFA)
Litkowski, et al. Expires March 24, 2017 [Page 20]
Internet-Draft isis-cfg September 2016
and also enhances remote LFA to use segment-routing tunneling instead
of LDP.
6. Interaction with Other YANG Modules
The "isis" configuration container augments the "/rt:routing/
rt:control-plane-protocols/control-plane-protocol" container of the
ietf-routing [I-D.ietf-netmod-routing-cfg] module by defining IS-IS
specific parameters.
The "isis" module augments "/if:interfaces/if:interface" with ISO
specific parameters.
The "isis" operational state container augments the "/rt:routing-
state/rt:control-plane-protocols/control-plane-protocol" container of
the ietf-routing module by defining IS-IS specific operational
states.
Some IS-IS specific routes attributes are added to route objects of
the ietf-routing module by augmenting "/rt:routing-
state/rt:ribs/rt:rib/rt:routes/rt:route".
The modules defined in this document use some groupings from ietf-
keychain [I-D.ietf-rtgwg-yang-key-chain] and ietf-segment routing
[I-D.ietf-spring-sr-yang].
7. IS-IS YANG Module
<CODE BEGINS> file "ietf-isis@2016-09-20.yang"
module ietf-isis {
namespace "urn:ietf:params:xml:ns:yang:ietf-isis";
prefix isis;
import ietf-routing {
prefix "rt";
}
import ietf-inet-types {
prefix inet;
}
import ietf-yang-types {
prefix yang;
}
import ietf-interfaces {
Litkowski, et al. Expires March 24, 2017 [Page 21]
Internet-Draft isis-cfg September 2016
prefix "if";
}
import ietf-key-chain {
prefix "key-chain";
}
organization
"IETF ISIS Working Group";
contact
"WG List: <mailto:isis-wg@ietf.org>
Editor: Stephane Litkowski
<mailto:stephane.litkowski@orange.com>
Derek Yeung
<mailto:myeung@cisco.com>
Acee Lindem
<mailto:acee@cisco.com>
Jeffrey Zhang
<mailto:zzhang@juniper.net>
Ladislav Lhotka
<mailto:llhotka@nic.cz>
Yi Yang
<mailto:yiya@cisco.com>
Dean Bogdanovic
<mailto:deanb@juniper.net>
Kiran Agrahara Sreenivasa
<mailto:kkoushik@brocade.com>
Yingzhen Qu
<mailto:yiqu@cisco.com>
Jeff Tantsura
<mailto:jeff.tantsura@ericsson.com>
";
description
"The YANG module defines a generic configuration model for
ISIS common across all of the vendor implementations.";
revision 2016-09-20 {
description
"
Align to draft-ietf-netmod-routing-cfg-23.
";
reference "draft-ietf-isis-yang-isis-cfg-09";
}
Litkowski, et al. Expires March 24, 2017 [Page 22]
Internet-Draft isis-cfg September 2016
revision 2016-05-30 {
description
"
Added container before af list
Added container before topology list
Aligned LFA if per level cfg
";
reference "";
}
revision 2016-03-21 {
description
"
- remove routing-instance as per core routing model v21
- added BFD leaf (no more BFD protocol model)
- changed keychain module reference
";
reference "draft-ietf-isis-yang-isis-cfg-08";
}
revision 2015-12-17 {
description
"Moved lists to containers+groupings for per level
configuration.";
reference "";
}
revision 2015-11-25 {
description
"
* Remove selector from system-id type
* Added some defaults
";
reference "";
}
revision 2015-11-18 {
description
"
* Move Overload config from list to container
* Move Overload-max-metric config from list to container
* Move preference config from list to container
* Add Node flag in config
* Removed BFD config => moved to isis-bfd module
* Remove call to routing policy model
(waiting stabilization to add it)
";
reference "draft-ietf-isis-yang-isis-cfg-07";
}
revision 2015-09-10 {
description
Litkowski, et al. Expires March 24, 2017 [Page 23]
Internet-Draft isis-cfg September 2016
" * Correct invalid references to previous
versions core routing model.
* Moved BFD config to usage of ietf-bfd yang grouping
* Adding routing-policy support through routing-policy model
";
reference "draft-ietf-isis-yang-isis-05";
}
revision 2015-06-22 {
description
" * Segment routing is part os a separate module.";
reference "draft-ietf-isis-yang-isis-03";
}
revision 2015-03-03 {
description
" * Reviewed config and op state groupings.
* Add default value to lfa candidate-disabled
* Add enable leaf to isis container to reflect admin state
* Move to VRF centric only
";
reference "";
}
revision 2015-03-03 {
description
"
* Defining hierarchy for operational states
* Adding CLNS MTU
* Adding Keychain
";
reference "draft-ietf-isis-yang-isis-02";
}
revision 2015-02-20 {
description
"
* Removing igp-ldp-sync timer in IS-IS
";
reference "";
}
revision 2014-12-15 {
description
"
* Adding IPFRR
* Adding igp-ldp sync
* Adding segment routing
* Adding instance reference to operational states.
* Move AF type from string to identity
* Updated router-capability in LSDB description.
* packet counters moved to interface-packet-counters.
Litkowski, et al. Expires March 24, 2017 [Page 24]
Internet-Draft isis-cfg September 2016
* Added modification information in lsp-log
";
reference "";
}
revision 2014-10-24 {
description
"
* Change hello-padding to container
* Change bfd to container
* Make BFD a feature
* Creates mpls-te container and put router-id
inside
* Remove GR helper disable and timers
";
reference "draft-ietf-isis-yang-isis-cfg-01";
}
revision 2014-10-21 {
description
"
* Interface metric move from af container to interface
container
* Hello-padding on interface moved to hello-padding-disable
with empty type
* three-way-handshake removed
* route preference changed to a choice
* csnp-authentication/psnp-authentication merged
to authentication container
* lsp-gen-interval-exp-delay removed
* Added overload-max-metric feature
* overload-max-metric is in a separate container
";
reference "";
}
revision 2014-10-07 {
description
"
* Removed spf parameters (should be part of
vendor specific extensions.
* Removed hello parameters at global level.
* Interface configuration uses a string rather
than a reference. This permits to map to some
vendor specific configuration.
";
reference "draft-ietf-isis-yang-isis-00";
}
revision 2014-09-26 {
description
Litkowski, et al. Expires March 24, 2017 [Page 25]
Internet-Draft isis-cfg September 2016
"
* Add BFD support
* remove max-elements to max-area-addresses
";
reference "";
}
revision 2014-09-11 {
description
"
* Add level parameter to ispf and spf delay
* Add LSP generation as a feature
* Make lsp-refresh a feature
* Change parameter container to list
";
reference "";
}
revision 2014-09-05 {
description
" Rewrite of the global hierarchy.";
reference "";
}
revision 2014-08-06 {
description
"
* isis-state renamed to isis.
* Add GR support
* Add meshgroup support
* Add CLNS support
* Add 64bits tags
* Add notifications to be aligned with MIB4444
* Add packet-counters, interface-counters, system-counters
states
* Add 3-way handshake support
* Rename isis-adjacency-updown to adjacency-change
* Add notification for LSP reception
* Use feature for reference BW
* Add lsp-retransmit-interval on interfaces
* Rename lsp-interval to lsp-pacing-interval
* Add ispf support as feature
* Add spf delay support as feature (2step & exp backoff)
* Add maximum-area-addresses
* Add default-metric
";
reference "RFC XXXX: YANG Data Model for ISIS Protocol";
}
revision 2014-06-25 {
description "
* isis-cfg renamed to isis.
Litkowski, et al. Expires March 24, 2017 [Page 26]
Internet-Draft isis-cfg September 2016
* Add precisions on authentication-keys in description
";
reference "draft-litkowski-isis-yang-isis-01";
}
revision 2014-06-20 {
description "
* isis-op renamed to isis-state.
* Multiple instances under ISIS are removed.
* interface-cfg grouping removed and content
is directly included in container isis.
* TLVxx renamed with human-readable name in isis-database.
TLV reference are putted in description.
* Reference to core routing module were fixed.
* Namespace fixed.
* Add simple-iso-address type.
* area-id and system-id in ISIS container are merged to
nsap-address.
* Add isis-system-id type.
* Add isis-lsp-id type.
* Add remaining-lifetime leaf in isis-database.
* Add TLV2 (is-neighbor) in isis-database.
* Renamed some container name for consistency
reason ('isis-' prefixed).
* Add new identities isis-cfg and isis-state.
* Add descriptions.
* Add notification isis-adjacency-updown.
* Add RPC clear-isis-adjacency and clear-isis-database.
";
reference "draft-litkowski-isis-yang-isis-00";
}
revision 2014-06-11 {
description "Initial revision.";
reference "draft-litkowski-netmod-isis-cfg-00";
}
identity isis {
base rt:routing-protocol;
description "Identity for the ISIS routing protocol.";
}
identity isis-adjacency-change {
description "Identity for the ISIS routing protocol
adjacency state.";
}
identity clear-isis-database {
description "Identity for the ISIS routing protocol
Litkowski, et al. Expires March 24, 2017 [Page 27]
Internet-Draft isis-cfg September 2016
database reset action.";
}
identity clear-isis-adjacency {
description "Identity for the ISIS routing protocol
adjacency reset action.";
}
/* Feature definitions */
feature bfd {
description
"Support of BFD for IS-IS links.";
}
feature key-chain {
description
"Support of keychain for authentication.";
}
feature segment-routing {
description
"Support of segment-routing.";
}
feature node-flag {
description
"Support of node-flag advertisement
as prefix attribute";
}
feature node-tag {
description
"Support of node tag.";
}
feature igp-ldp-sync {
description
"Support of RFC5443.";
}
feature fast-reroute {
description
"Support of IPFRR.";
}
feature lfa {
description
"Support of Loop Free Alternates.";
}
feature remote-lfa {
description
"Support of remote Loop Free Alternates.";
}
Litkowski, et al. Expires March 24, 2017 [Page 28]
Internet-Draft isis-cfg September 2016
feature overload-max-metric {
description
"Support of overload by setting
all links to max metric.";
}
feature prefix-tag {
description
"Add 32bit tag to prefixes";
}
feature prefix-tag64 {
description
"Add 64bit tag to prefixes";
}
feature reference-bandwidth {
description
"Use a reference bandwidth to compute metric.";
}
feature ipv4-router-id {
description
"Support of IPv4 router ID configuration under ISIS.";
}
feature ipv6-router-id {
description
"Support of IPv6 router ID configuration under ISIS.";
}
feature multi-topology {
description
"Multitopology routing support.";
}
feature nlpid-control {
description
"This feature controls the advertisement
of support NLPID within ISIS configuration.";
}
feature graceful-restart {
description
"Graceful restart support as per RFC5306.";
}
feature lsp-refresh {
description
"Configuration of LSP refresh interval.";
}
feature maximum-area-addresses {
Litkowski, et al. Expires March 24, 2017 [Page 29]
Internet-Draft isis-cfg September 2016
description
"Support of maximum-area-addresses config.";
}
feature admin-control {
description
"Control administrative state of ISIS.";
}
/* Type definitions */
typedef instance-state-ref {
type leafref {
path "/rt:routing-state/"
+"rt:control-plane-protocols/rt:control-plane-protocol/rt:name";
}
description
"This type is used for leaves that reference state data of
an ISIS protocol instance.";
}
typedef admin-state {
type enumeration {
enum "up" {
description
"Up state";
}
enum "down" {
description
"Down state";
}
}
description
"Administrative state of a component.";
}
typedef oper-state {
type enumeration {
enum "up" {
description
"Up state";
}
enum "down" {
description
"Down state";
}
}
description
Litkowski, et al. Expires March 24, 2017 [Page 30]
Internet-Draft isis-cfg September 2016
"Operational state of a component.";
}
typedef circuit-id {
type uint8;
description
"This type defines the circuit ID
associated with an interface.";
}
typedef extended-circuit-id {
type uint32;
description
"This type defines the extended circuit ID
associated with an interface.";
}
typedef interface-type {
type enumeration {
enum broadcast {
description "Broadcast interface type.
Would result in DIS election.";
}
enum point-to-point {
description
"Point to point interface type.";
}
}
description
"This type defines the type of adjacency
to be established on the interface.
This is affecting the type of hello
message that would be used.";
}
typedef level {
type enumeration {
enum "level-1" {
description
"This enum describes L1 only capability.";
}
enum "level-2" {
description
"This enum describes L2 only capability.";
}
enum "level-all" {
description
"This enum describes both levels capability.";
Litkowski, et al. Expires March 24, 2017 [Page 31]
Internet-Draft isis-cfg September 2016
}
}
default "level-all";
description
"This type defines ISIS level of an object.";
}
typedef level-number {
type uint8 {
range "1 .. 2";
}
description
"This type defines a current ISIS level.";
}
typedef lsp-id {
type string {
pattern
'[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}\.[0-9A-Fa-f]'
+'{4}\.[0-9][0-9]-[0-9][0-9]';
}
description
"This type defines ISIS LSP ID using pattern,
system id looks like : 0143.0438.AeF0.02-01";
}
typedef area-address {
type string {
pattern '[0-9A-Fa-f]{2}\.([0-9A-Fa-f]{4}\.){0,3}';
}
description
"This type defines the area address.";
}
typedef snpa {
type string {
length "0 .. 20";
}
description
"This type defines Subnetwork Point of Attachement format.";
}
typedef system-id {
type string {
pattern
Litkowski, et al. Expires March 24, 2017 [Page 32]
Internet-Draft isis-cfg September 2016
'[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}';
}
description
"This type defines ISIS system id using pattern,
system id looks like : 0143.0438.AeF0";
}
typedef wide-metric {
type uint32 {
range "0 .. 16777215";
}
description
"This type defines wide style format
of ISIS metric.";
}
typedef std-metric {
type uint8 {
range "0 .. 63";
}
description
"This type defines old style format
of ISIS metric.";
}
typedef mesh-group-state {
type enumeration {
enum "meshInactive" {
description
"Interface is not part of a mesh group.";
}
enum "meshSet" {
description
"Interface is part of a mesh group.";
}
enum "meshBlocked" {
description
"LSPs must not be flooded over that interface.";
}
}
description
"This type describes meshgroup state of an interface";
}
/* Grouping definitions */
Litkowski, et al. Expires March 24, 2017 [Page 33]
Internet-Draft isis-cfg September 2016
grouping admin-control {
leaf enable {
if-feature admin-control;
type boolean;
default true;
description
"Control the administrative
state.";
}
description
"Grouping for admin control.";
}
grouping adjacency-state {
container adjacencies {
list adjacency {
leaf neighbor-systype {
type level;
description
"Type of neighboring system";
}
leaf neighbor-sysid {
type system-id;
description
"The system-id of the neighbor";
}
leaf neighbor-extended-circuit-id {
type extended-circuit-id;
description
"Circuit ID of the neighbor";
}
leaf neighbor-snpa {
type snpa;
description
"SNPA of the neighbor";
}
leaf usage {
type level;
description
"How is the adjacency used ?
On a p2p link this might be level 1 and 2,
but on a LAN, the usage will be level 1
between peers at L1 or level 2 between
Litkowski, et al. Expires March 24, 2017 [Page 34]
Internet-Draft isis-cfg September 2016
peers at L2.";
}
leaf hold-timer {
type uint16;
description
"The holding time in seconds for this
adjacency. This value is based on
received hello PDUs and the elapsed
time since receipt.";
}
leaf neighbor-priority {
type uint8 {
range "0 .. 127";
}
description
"Priority of the neighboring IS for becoming
the DIS.";
}
leaf lastuptime {
type yang:timestamp;
description
"When the adjacency most recently entered
state 'up', measured in hundredths of a
second since the last reinitialization of
the network management subsystem.
The value is 0 if the adjacency has never
been in state 'up'.";
}
leaf state {
type enumeration {
enum "Up" {
description
"This state describes that
adjacency is established.";
}
enum "Down" {
description
"This state describes that
adjacency is NOT established.";
}
enum "Init" {
description
"This state describes that
adjacency is establishing.";
}
enum "Failed" {
description
Litkowski, et al. Expires March 24, 2017 [Page 35]
Internet-Draft isis-cfg September 2016
"This state describes that
adjacency is failed.";
}
}
description
"This leaf describes the state of the
interface.";
}
description
"List of operational adjacencies.";
}
description
"This container lists the adjacencies of
the local node.";
}
description
"Adjacency state";
}
grouping fast-reroute-global-state {
container protected-routes {
list af-stats {
key "af prefix alternate";
leaf af {
type identityref {
base rt:address-family;
}
description
"Address-family";
}
leaf prefix {
type string;
description
"Protected prefix.";
}
leaf alternate {
type string;
description
"Alternate nexthop for the prefix.";
}
leaf alternate-type {
type enumeration {
enum equalcost {
description
Litkowski, et al. Expires March 24, 2017 [Page 36]
Internet-Draft isis-cfg September 2016
"ECMP alternate.";
}
enum lfa {
description
"LFA alternate.";
}
enum remote-lfa {
description
"Remote LFA alternate.";
}
enum tunnel {
description
"Tunnel based alternate
(like RSVP-TE or GRE).";
}
enum ti-lfa {
description
"TI LFA alternate.";
}
enum mrt {
description
"MRT alternate.";
}
enum other {
description
"Unknown alternate type.";
}
}
description
"Type of alternate.";
}
leaf best {
type boolean;
description
"describes if the alternate is the best one.";
}
leaf non-best-reason {
type string;
description
"Information field to describe why the alternate
is not best.";
}
leaf protection-available {
type bits {
bit nodeprotect {
position 0;
description
"Node protection available.";
Litkowski, et al. Expires March 24, 2017 [Page 37]
Internet-Draft isis-cfg September 2016
}
bit linkprotect {
position 1;
description
"Link protection available.";
}
bit srlgprotect {
position 2;
description
"SRLG protection available.";
}
bit downstreamprotect {
position 3;
description
"Downstream protection available.";
}
bit other {
position 4;
description
"Other protection available.";
}
}
description
"Describes protection provided by the alternate.";
}
leaf alternate-metric1 {
type uint32;
description
"Metric from PLR to destination
through the alternate path.";
}
leaf alternate-metric2 {
type uint32;
description
"Metric from PLR to the alternate node";
}
leaf alternate-metric3 {
type uint32;
description
"Metric from alternate node to the destination";
}
description
"Per AF statistics.";
}
description
"List of prefixes that are protected.";
}
Litkowski, et al. Expires March 24, 2017 [Page 38]
Internet-Draft isis-cfg September 2016
container nonprotected-routes {
list af-stats {
key "af prefix";
leaf af {
type identityref {
base rt:address-family;
}
description
"Address-family";
}
leaf prefix {
type string;
description
"Protected prefix.";
}
description
"Per AF statistics.";
}
description
"List of prefixes that are not protected.";
}
list protection-statistics {
key frr-protection-method;
leaf frr-protection-method {
type string;
description
"Protection method used.";
}
list af-stats {
key af;
leaf af {
type identityref {
base rt:address-family;
}
description
"Address-family";
}
leaf total-routes {
type uint32;
description
"Total prefixes.";
}
leaf unprotected-routes {
type uint32;
Litkowski, et al. Expires March 24, 2017 [Page 39]
Internet-Draft isis-cfg September 2016
description
"Total of prefixes who are
not protected.";
}
leaf protected-routes {
type uint32;
description
"Total of prefixes who are
protected.";
}
leaf linkprotected-routes {
type uint32;
description
"Total of prefixes who are
link protected.";
}
leaf nodeprotected-routes {
type uint32;
description
"Total of prefixes who are
node protected.";
}
description
"Per AF statistics.";
}
description
"Global protection statistics.";
}
description
"IPFRR states.";
}
grouping notification-instance-hdr {
description
"This group describes common instance specific
data for notifications.";
leaf instance-name {
type string;
description
"Describes the name of the ISIS instance.";
}
leaf instance-level {
type level;
description
"Describes the ISIS level of the instance.";
}
}
Litkowski, et al. Expires March 24, 2017 [Page 40]
Internet-Draft isis-cfg September 2016
grouping notification-interface-hdr {
description
"This group describes common interface specific
data for notifications.";
leaf interface-name {
type string;
description
"Describes the name of the ISIS interface.";
}
leaf interface-level {
type level;
description
"Describes the ISIS level of the interface.";
}
leaf extended-circuit-id {
type extended-circuit-id;
description
"Describes the extended circuit-id of the interface.";
}
}
grouping route-content {
description
"This group add isis-specific route properties.";
leaf metric {
type uint32;
description
"This leaf describes ISIS metric of a route.";
}
leaf-list tag {
type uint64;
description
"This leaf describes list of tags associated
with the route. The leaf describes both
32bits and 64bits tags.";
}
leaf route-type {
type enumeration {
enum l2-up-internal {
description "Level 2 internal route
and not leaked to a lower level";
}
enum l1-up-internal {
description "Level 1 internal route
and not leaked to a lower level";
}
enum l2-up-external {
description "Level 2 external route
Litkowski, et al. Expires March 24, 2017 [Page 41]
Internet-Draft isis-cfg September 2016
and not leaked to a lower level";
}
enum l1-up-external {
description "Level 1 external route
and not leaked to a lower level";
}
enum l2-down-internal {
description "Level 2 internal route
and leaked to a lower level";
}
enum l1-down-internal {
description "Level 1 internal route
and leaked to a lower level";
}
enum l2-down-external {
description "Level 2 external route
and leaked to a lower level";
}
enum l1-down-external {
description "Level 1 external route
and leaked to a lower level";
}
}
description
"This leaf describes the type of ISIS route.";
}
}
grouping fast-reroute-global-cfg {
description
"This group defines global
configuration of IPFRR.";
container lfa {
if-feature lfa;
description
"This container may be
augmented with global parameters
for LFA.
Creating the container has no effect on
LFA activation.";
}
}
grouping fast-reroute-if-cfg {
description
Litkowski, et al. Expires March 24, 2017 [Page 42]
Internet-Draft isis-cfg September 2016
"This group defines interface
configuration of IPFRR.";
container lfa {
if-feature lfa;
uses lfa-if-cfg;
container level-1 {
uses lfa-if-cfg;
description
"LFA level 21 config";
}
container level-2 {
uses lfa-if-cfg;
description
"LFA level 2 config";
}
description
"LFA config";
}
}
grouping prefix-reachability-attributes {
description
"This group defines extended reachability attributes of an
IPv4 or IPv6 prefix.";
leaf external-prefix-flag {
type boolean;
description
"External prefix flag.";
}
leaf readvertisement-flag {
type boolean;
description
"Readvertisement flag.";
}
leaf node-flag {
type boolean;
description
"Node flag.";
}
}
grouping prefix-ipv4-source-router-id {
Litkowski, et al. Expires March 24, 2017 [Page 43]
Internet-Draft isis-cfg September 2016
description
"This group defines the IPv4 source router ID of
a prefix advertisement.";
leaf ipv4-source-router-id {
type inet:ipv4-address;
description
"IPv4 Source router ID address.";
}
}
grouping prefix-ipv6-source-router-id {
description
"This group defines the IPv6 source router ID of
a prefix advertisement.";
leaf ipv6-source-router-id {
type inet:ipv6-address;
description
"IPv6 Source router ID address.";
}
}
grouping prefix-attributes-extension {
description
"Prefix extended attributes.";
uses prefix-reachability-attributes;
uses prefix-ipv4-source-router-id;
uses prefix-ipv6-source-router-id;
}
grouping prefix-ipv4-std {
description
"This group defines attributes of an
IPv4 standard prefix.";
leaf up-down {
type boolean;
description
"This leaf expresses the value of up/down bit.";
}
leaf i-e {
type boolean;
description
"This leaf expresses the value of I/E bit.";
}
leaf ip-prefix {
Litkowski, et al. Expires March 24, 2017 [Page 44]
Internet-Draft isis-cfg September 2016
type inet:ipv4-address;
description
"This leaf describes the IPv4 prefix";
}
leaf prefix-len {
type uint8;
description
"This leaf describes the IPv4 prefix len in bits";
}
leaf default-metric {
type std-metric;
description
"This leaf describes the ISIS default metric value";
}
container delay-metric {
leaf metric {
type std-metric;
description
"This leaf describes the ISIS delay metric value";
}
leaf supported {
type boolean;
default "false";
description
"This leaf describes if the metric is supported.";
}
description
"This container defines the ISIS delay metric.";
}
container expense-metric {
leaf metric {
type std-metric;
description
"This leaf describes the ISIS expense metric value";
}
leaf supported {
type boolean;
default "false";
description
"This leaf describes if the metric is supported.";
}
description
"This container defines the ISIS expense metric.";
}
container error-metric {
leaf metric {
type std-metric;
Litkowski, et al. Expires March 24, 2017 [Page 45]
Internet-Draft isis-cfg September 2016
description
"This leaf describes the ISIS error metric value";
}
leaf supported {
type boolean;
default "false";
description
"This leaf describes if the metric is supported.";
}
description
"This container defines the ISIS error metric.";
}
}
grouping prefix-ipv4-extended {
description
"This group defines attributes of an
IPv4 extended prefix.";
leaf up-down {
type boolean;
description
"This leaf expresses the value of up/down bit.";
}
leaf ip-prefix {
type inet:ipv4-address;
description
"This leaf describes the IPv4 prefix";
}
leaf prefix-len {
type uint8;
description
"This leaf describes the IPv4 prefix len in bits";
}
leaf metric {
type wide-metric;
description
"This leaf describes the ISIS metric value";
}
leaf-list tag {
type uint32;
description
"This leaf describes a list of tags associated with
the prefix.";
}
leaf-list tag64 {
type uint64;
Litkowski, et al. Expires March 24, 2017 [Page 46]
Internet-Draft isis-cfg September 2016
description
"This leaf describes a list of 64-bit tags associated with
the prefix.";
}
uses prefix-attributes-extension;
}
grouping prefix-ipv6-extended {
description
"This group defines attributes of an
IPv6 prefix.";
leaf up-down {
type boolean;
description
"This leaf expresses the value of up/down bit.";
}
leaf ip-prefix {
type inet:ipv6-address;
description
"This leaf describes the IPv6 prefix";
}
leaf prefix-len {
type uint8;
description
"This leaf describes the IPv4 prefix len in bits";
}
leaf metric {
type wide-metric;
description
"This leaf describes the ISIS metric value";
}
leaf-list tag {
type uint32;
description
"This leaf describes a list of tags associated with
the prefix.";
}
leaf-list tag64 {
type uint64;
description
"This leaf describes a list of 64-bit tags associated with
the prefix.";
}
uses prefix-attributes-extension;
Litkowski, et al. Expires March 24, 2017 [Page 47]
Internet-Draft isis-cfg September 2016
}
grouping neighbor-extended {
description
"This group defines attributes of an
ISIS extended neighbor.";
leaf neighbor-id {
type system-id;
description
"This leaf describes the system-id of the neighbor.";
}
leaf metric {
type wide-metric;
description
"This leaf describes the ISIS metric value";
}
}
grouping neighbor {
description
"This group defines attributes of an
ISIS standard neighbor.";
leaf neighbor-id {
type system-id;
description
"This leaf describes the system-id of the neighbor.";
}
leaf i-e {
type boolean;
description
"This leaf expresses the value of I/E bit.";
}
leaf default-metric {
type std-metric;
description
"This leaf describes the ISIS default metric value";
}
container delay-metric {
leaf metric {
type std-metric;
description
"This leaf describes the ISIS delay metric value";
}
leaf supported {
type boolean;
Litkowski, et al. Expires March 24, 2017 [Page 48]
Internet-Draft isis-cfg September 2016
default "false";
description
"This leaf describes if the metric is supported.";
}
description
"This container defines the ISIS delay metric.";
}
container expense-metric {
leaf metric {
type std-metric;
description
"This leaf describes the ISIS delay expense value";
}
leaf supported {
type boolean;
default "false";
description
"This leaf describes if the metric is supported.";
}
description
"This container defines the ISIS expense metric.";
}
container error-metric {
leaf metric {
type std-metric;
description
"This leaf describes the ISIS error metric value";
}
leaf supported {
type boolean;
default "false";
description
"This leaf describes if the metric is supported.";
}
description
"This container defines the ISIS error metric.";
}
}
grouping database {
description
"This group defines attributes of an
ISIS database (Link State DB).";
leaf lsp-id {
type lsp-id;
description
"This leaf describes the LSP ID of the LSP.";
}
Litkowski, et al. Expires March 24, 2017 [Page 49]
Internet-Draft isis-cfg September 2016
leaf checksum {
type uint16;
description
"This leaf describes the checksum of the LSP.";
}
leaf remaining-lifetime {
type uint16;
units "seconds";
description
"This leaf describes the remaining lifetime
in seconds before the LSP expiration.";
}
leaf sequence {
type uint32;
description
"This leaf describes the sequence number of the LSP.";
}
leaf attributes {
type bits {
bit PARTITIONNED {
description
"If set, the originator supports partition
repair.";
}
bit ATTACHED-ERROR {
description
"If set, the originator is attached to
another area using the referred metric.";
}
bit ATTACHED-EXPENSE {
description
"If set, the originator is attached to
another area using the referred metric.";
}
bit ATTACHED-DELAY {
description
"If set, the originator is attached to
another area using the referred metric.";
}
bit ATTACHED-DEFAULT {
description
"If set, the originator is attached to
another area using the referred metric.";
}
bit OVERLOAD {
description
"If set, the originator is overloaded,
and must be avoided in path calculation.";
Litkowski, et al. Expires March 24, 2017 [Page 50]
Internet-Draft isis-cfg September 2016
}
}
description
"This leaf describes attributes of the LSP.";
}
container is-neighbor {
list neighbor {
uses neighbor;
description
"List of neighbors.";
}
description
"This leaf describes list of ISIS neighbors.
ISIS reference is TLV 2.";
}
container authentication {
leaf authentication-type {
type string;
description
"This leaf describes the authentication type
to be used.";
}
leaf authentication-key {
type string;
description
"This leaf describes the authentication key
to be used. For security reason, the
authentication key MUST NOT be presented
in plaintext format. Authors recommends
to use MD5 hash to present the authentication-key.";
}
description "This container describes authentication
information of the node. ISIS reference is TLV 10.";
}
container extended-is-neighbor {
list neighbor {
uses neighbor-extended;
description
"List of neighbors.";
}
description
"This container describes list of ISIS extended
neighbors.
ISIS reference is TLV 22.";
Litkowski, et al. Expires March 24, 2017 [Page 51]
Internet-Draft isis-cfg September 2016
}
container ipv4-internal-reachability {
list prefixes {
uses prefix-ipv4-std;
description
"List of prefixes.";
}
description
"This container describes list of IPv4 internal
reachability information.
ISIS reference is TLV 128.";
}
leaf-list protocol-supported {
type uint8;
description
"This leaf describes the list of
supported protocols.
ISIS reference is TLV 129.";
}
container ipv4-external-reachability {
list prefixes {
uses prefix-ipv4-std;
description
"List of prefixes.";
}
description
"This container describes list of IPv4 external
reachability information.
ISIS reference is TLV 130.";
}
leaf-list ipv4-addresses {
type inet:ipv4-address;
description
"This leaf describes the IPv4 addresses of the node.
ISIS reference is TLV 132.";
}
leaf ipv4-te-routerid {
type inet:ipv4-address;
description
"This leaf describes the IPv4 Traffic Engineering
router ID of the node.
ISIS reference is TLV 134.";
Litkowski, et al. Expires March 24, 2017 [Page 52]
Internet-Draft isis-cfg September 2016
}
container extended-ipv4-reachability {
list prefixes {
uses prefix-ipv4-extended;
description
"List of prefixes.";
}
description
"This container describes list of IPv4 extended
reachability information.
ISIS reference is TLV 135.";
}
leaf dynamic-hostname {
type string;
description
"This leaf describes the name of the node.
ISIS reference is TLV 137.";
}
leaf ipv6-te-routerid {
type inet:ipv6-address;
description
"This leaf describes the IPv6 Traffic Engineering
router ID of the node.
ISIS reference is TLV 140.";
}
container mt-is-neighbor {
list neighbor {
leaf MT-ID {
type uint16 {
range "0 .. 4095";
}
description
"This leaf defines the identifier
of a topology.";
}
uses neighbor-extended;
description
"List of neighbors.";
}
description
"This container describes list of ISIS multi-topology
Litkowski, et al. Expires March 24, 2017 [Page 53]
Internet-Draft isis-cfg September 2016
neighbors.
ISIS reference is TLV 223.";
}
container mt-entries {
list topology {
leaf MT-ID {
type uint16 {
range "0 .. 4095";
}
description
"This leaf defines the identifier
of a topology.";
}
leaf attributes {
type bits {
bit OVERLOAD {
description
"If set, the originator is overloaded,
and must be avoided in path
calculation.";
}
bit ATTACHED {
description
"If set, the originator is attached to
another area using the referred metric.";
}
}
description
"This leaf describes attributes of the LSP
for the associated topology.";
}
description
"List of topologies supported.";
}
description
"This container describes the topology supported.
ISIS reference is TLV 229.";
}
leaf-list ipv6-addresses {
type inet:ipv6-address;
description
"This leaf describes the IPv6 interface
addresses of the node.
ISIS reference is TLV 232.";
Litkowski, et al. Expires March 24, 2017 [Page 54]
Internet-Draft isis-cfg September 2016
}
container mt-extended-ipv4-reachability {
list prefixes {
leaf MT-ID {
type uint16 {
range "0 .. 4095";
}
description
"This leaf defines the identifier
of a topology.";
}
uses prefix-ipv4-extended;
description
"List of prefixes.";
}
description
"This container describes list of IPv4
reachability information in multi-topology
environment.
ISIS reference is TLV 235.";
}
container mt-ipv6-reachability {
list prefixes {
leaf MT-ID {
type uint16 {
range "0 .. 4095";
}
description
"This leaf defines the identifier
of a topology.";
}
uses prefix-ipv6-extended;
description
"List of prefixes.";
}
description
"This container describes list of IPv6
reachability information in multi-topology
environment.
ISIS reference is TLV 237.";
}
Litkowski, et al. Expires March 24, 2017 [Page 55]
Internet-Draft isis-cfg September 2016
container ipv6-reachability {
list prefixes {
uses prefix-ipv6-extended;
description
"List of prefixes.";
}
description
"This container describes list of IPv6
reachability information.
ISIS reference is TLV 236.";
}
list router-capabilities {
leaf flags {
type bits {
bit flooding {
position 0;
description
"If the S bit is set(1),
the IS-IS Router CAPABILITY TLV
MUST be flooded across the entire routing domain.
If the S bit is
not set(0), the TLV MUST NOT be leaked between levels.
This bit MUST NOT be altered during the TLV leaking.";
}
bit down {
position 1;
description
"When the IS-IS Router CAPABILITY TLV is
leaked from level-2 to level-1, the D bit
MUST be set. Otherwise, this bit MUST
be clear. IS-IS Router capability TLVs
with the D bit set MUST NOT
be leaked from level-1 to level-2.
This is to prevent TLV looping.
";
}
}
description
"Flags associated with router capability.";
}
container node-tags {
if-feature node-tag;
list node-tag {
leaf tag {
type uint32;
Litkowski, et al. Expires March 24, 2017 [Page 56]
Internet-Draft isis-cfg September 2016
description
"Node tag value.";
}
description
"List of tags.";
}
description
"Container for node tags.";
}
leaf binary {
type binary;
description
"This leaf describes the capability of the node.
Format is binary according to the protocol encoding.";
}
description
"This container describes the capabilities of the node.
This container may be extended with detailed
information.
ISIS reference is TLV 242.";
}
}
grouping isis-node-tag-cfg {
description
"ISIS node tag config.";
container node-tag {
if-feature node-tag;
list node-tag {
key tag;
leaf tag {
type uint32;
description
"Node tag value.";
}
description
"List of tags.";
}
description
"Container for node tags.";
}
}
grouping authentication-global-cfg {
choice authentication-type {
case key-chain {
if-feature key-chain;
Litkowski, et al. Expires March 24, 2017 [Page 57]
Internet-Draft isis-cfg September 2016
leaf key-chain {
type key-chain:key-chain-ref;
description
"Reference to a key-chain.";
}
}
case password {
leaf key {
type string;
description
"This leaf describes the
authentication key.";
}
uses key-chain:crypto-algorithm-types;
}
description
"Choice of authentication.";
}
description
"Grouping for global auth config.";
}
grouping metric-type-global-cfg {
leaf value {
type enumeration {
enum wide-only {
description
"Advertise new metric style only
(RFC5305)";
}
enum old-only {
description
"Advertise old metric style only
(RFC1195)";
}
enum both {
description "Advertise both metric
styles";
}
}
description
"This leaf describes the type of metric
to be generated.
Wide-only means only new metric style
is generated,
old-only means that only old style metric
is generated,
and both means that both are advertised.
Litkowski, et al. Expires March 24, 2017 [Page 58]
Internet-Draft isis-cfg September 2016
This leaf is only affecting IPv4 metrics.";
}
description
"Grouping for global metric style config.";
}
grouping default-metric-global-cfg {
leaf value {
type wide-metric;
default "10";
description
"Value of the metric";
}
description
"Grouping for global default metric config.";
}
grouping overload-global-cfg {
leaf status {
type boolean;
description
"This leaf defines the overload status.";
}
description
"Grouping for overload bit config.";
}
grouping overload-max-metric-global-cfg {
leaf timeout {
type uint16;
units "seconds";
description
"This leaf defines the timeout in seconds
of the overload condition.";
}
description
"Grouping for overload-max-metric config.";
}
grouping route-preference-global-cfg {
choice granularity {
case detail {
leaf internal {
type uint8;
description
"This leaf defines the protocol
preference for internal routes.";
}
Litkowski, et al. Expires March 24, 2017 [Page 59]
Internet-Draft isis-cfg September 2016
leaf external {
type uint8;
description
"This leaf defines the protocol
preference for external routes.";
}
}
case coarse {
leaf default {
type uint8;
description
"This leaf defines the protocol
preference for all ISIS routes.";
}
}
description
"Choice for implementation of route preference.";
}
description
"This grouping defines how route preference is configured.";
}
grouping hello-authentication-cfg {
choice authentication-type {
case key-chain {
if-feature key-chain;
leaf key-chain {
type key-chain:key-chain-ref;
description
"Reference to a key-chain.";
}
}
case password {
leaf key {
type string;
description
"This leaf describes the
authentication key.";
}
uses key-chain:crypto-algorithm-types;
}
description
"Choice of authentication.";
}
description
"Grouping for hello authentication.";
}
Litkowski, et al. Expires March 24, 2017 [Page 60]
Internet-Draft isis-cfg September 2016
grouping hello-interval-cfg {
leaf value {
type uint16 {
range "1..65535";
}
units "seconds";
default 10;
description
"This leaf defines the interval of
hello messages.";
}
description
"Interval between
hello messages.";
}
grouping hello-multiplier-cfg {
leaf value {
type uint16;
description
"This leaf defines the number of
hello failed to be received before
declaring the adjacency down.";
}
description
"This grouping defines the number of
hello failed to be received before
declaring the adjacency down.";
}
grouping priority-cfg {
leaf value {
type uint8 {
range "0 .. 127";
}
default 64;
description
"This leaf describes the priority of
the interface
for DIS election.";
}
description
"This grouping leaf describes the
priority of
Litkowski, et al. Expires March 24, 2017 [Page 61]
Internet-Draft isis-cfg September 2016
the interface
for DIS election.";
}
grouping metric-cfg {
leaf value {
type wide-metric;
description
"Metric value.";
}
description
"Grouping for interface metric";
}
grouping lfa-if-cfg {
leaf candidate-disabled {
type boolean;
default false;
description
"Prevent the interface to be used as backup.";
}
leaf enable {
type boolean;
description
"Activates LFA.
This model assumes activation
of per-prefix LFA.";
}
container remote-lfa {
if-feature remote-lfa;
leaf enable {
type boolean;
description
"Activates rLFA.";
}
description
"remote LFA configuration.";
}
description
"Grouping for LFA
interface configuration";
}
grouping isis-global-cfg {
description
"Defines the ISIS global configuration.";
uses admin-control;
Litkowski, et al. Expires March 24, 2017 [Page 62]
Internet-Draft isis-cfg September 2016
leaf level-type {
type level;
default "level-all";
description
"This leaf describes the type of ISIS node.
A node can be level-1-only, level-2-only
or level-1-2.
";
}
leaf system-id {
type system-id;
description
"This leaf defines the system-id of the node.";
}
leaf maximum-area-addresses {
if-feature maximum-area-addresses;
type uint8;
default 3;
description
"Defines the maximum areas supported.";
}
leaf-list area-address {
type area-address;
description
"List of areas supported by the
protocol instance.";
}
container mpls {
leaf ipv4-router-id {
if-feature ipv4-router-id;
type inet:ipv4-address;
description
"Router ID value that would be used in
TLV 134.";
}
leaf ipv6-router-id {
if-feature ipv6-router-id;
type inet:ipv6-address;
description
"Router ID value that would be used in
TLV 140.";
}
container igp-ldp-sync {
Litkowski, et al. Expires March 24, 2017 [Page 63]
Internet-Draft isis-cfg September 2016
if-feature igp-ldp-sync;
description
"This container may be augmented
with global parameters for igp-ldp-sync.";
}
description
"This container handles mpls config.";
}
leaf reference-bandwidth {
if-feature reference-bandwidth;
type uint32;
units "bps";
description
"This leaf defines the bandwidth for calculating
metric.";
}
leaf lsp-mtu {
type uint16;
units "bytes";
default 1492;
description
"This leaf describes the maximum size of a
LSP PDU in bytes.";
}
leaf lsp-lifetime {
type uint16 {
range "1..65535";
}
units "seconds";
description
"This leaf describes the lifetime of the router
LSP in seconds.";
}
leaf lsp-refresh {
if-feature lsp-refresh;
type uint16 {
range "1..65535";
}
units "seconds";
description
"This leaf describes the refresh interval of the
router LSP in seconds.";
}
container graceful-restart {
if-feature graceful-restart;
leaf enable {
Litkowski, et al. Expires March 24, 2017 [Page 64]
Internet-Draft isis-cfg September 2016
type boolean;
description
"Control enabling the feature.";
}
description
"This container activates graceful restart.";
}
uses isis-node-tag-cfg;
container authentication {
uses authentication-global-cfg;
container level-1 {
uses authentication-global-cfg;
description "level-1 specific cfg";
}
container level-2 {
uses authentication-global-cfg;
description "level-2 specific cfg";
}
description "authentication global cfg.
It covers both LSPs and SNPs.";
}
container metric-type {
uses metric-type-global-cfg;
container level-1 {
uses metric-type-global-cfg;
description "level-1 specific cfg";
}
container level-2 {
uses metric-type-global-cfg;
description "level-2 specific cfg";
}
description "Metric style global cfg.";
}
container default-metric {
uses default-metric-global-cfg;
container level-1 {
uses default-metric-global-cfg;
description "level-1 specific cfg";
}
container level-2 {
Litkowski, et al. Expires March 24, 2017 [Page 65]
Internet-Draft isis-cfg September 2016
uses default-metric-global-cfg;
description "level-2 specific cfg";
}
description "Default metric global cfg.";
}
container afs {
list af {
if-feature nlpid-control;
key af;
leaf af {
type identityref {
base rt:address-family;
}
description
"Address-family";
}
leaf enable {
type boolean;
description
"Describes the activation state of the
AF.";
}
description
"This list permits activation
of new address families.";
}
description
"Container for address-families";
}
container preference {
uses route-preference-global-cfg;
description
"This container defines the protocol preference.";
}
container overload {
uses overload-global-cfg;
description
"This container describes if the router is
set to overload state.";
}
container overload-max-metric {
Litkowski, et al. Expires March 24, 2017 [Page 66]
Internet-Draft isis-cfg September 2016
if-feature overload-max-metric;
uses overload-max-metric-global-cfg;
description
"This container describes if the router is
set to overload state using max-metric
advertisement.";
}
}
grouping isis-global-topologies-cfg {
description
"Per topology config.";
container default-metric {
uses default-metric-global-cfg;
container level-1 {
uses default-metric-global-cfg;
description "level-1 specific cfg";
}
container level-2 {
uses default-metric-global-cfg;
description "level-2 specific cfg";
}
description "Default metric per
topology cfg.";
}
uses isis-node-tag-cfg;
}
grouping isis-if-cfg {
description
"Grouping for interface cfg.";
leaf level-type {
type level;
default "level-all";
description
"This leaf defines the associated ISIS
level of the interface.";
}
Litkowski, et al. Expires March 24, 2017 [Page 67]
Internet-Draft isis-cfg September 2016
leaf lsp-pacing-interval {
type uint16;
units "milliseconds";
default 33;
description
"This leaf defines the interval between
LSP transmissions in milli-seconds";
}
leaf lsp-retransmit-interval {
type uint16;
units "seconds";
description
"This leaf defines the interval between
retransmission of LSP";
}
leaf passive {
type boolean;
default "false";
description
"This leaf defines if interface is in
passive mode (ISIS not running,
but network is advertised).";
}
leaf csnp-interval {
type uint16 {
range "1..65535";
}
units "seconds";
default 10;
description
"This leaf defines the interval of CSNP
messages.";
}
container hello-padding {
leaf enable {
type boolean;
default "true";
description
"Status of Hello-padding activation.
By default, the implementation shall
pad HELLOs.";
}
description
"This container handles ISIS hello padding
configuration.";
}
Litkowski, et al. Expires March 24, 2017 [Page 68]
Internet-Draft isis-cfg September 2016
leaf mesh-group-enable {
type mesh-group-state;
description
"Describes the mesh group state of
the interface.";
}
leaf mesh-group {
when "../mesh-group-enable = 'meshSet'" {
description
"Only valid when mesh-group-enable
equals meshSet";
}
type uint8;
description
"Describes the mesh group ID of
the interface.";
}
leaf interface-type {
type interface-type;
description
"This leaf defines the type of adjacency
to be established on the interface.
This is affecting the type of hello
message that would be used.";
}
uses admin-control;
leaf-list tag {
if-feature prefix-tag;
type uint32;
description
"This leaf defines list of tags associated
with the interface.";
}
leaf-list tag64 {
if-feature prefix-tag64;
type uint64;
description
"This leaf defines list of 64bits tags
associated with the interface.";
}
Litkowski, et al. Expires March 24, 2017 [Page 69]
Internet-Draft isis-cfg September 2016
leaf node-flag {
if-feature node-flag;
type boolean;
default false;
description
"Set prefix as a node
representative prefix.";
}
container hello-authentication {
uses hello-authentication-cfg;
container level-1 {
uses hello-authentication-cfg;
description "level-1 specific cfg";
}
container level-2 {
uses hello-authentication-cfg;
description "level-2 specific cfg";
}
description "Authentication type
to be used in hello messages.";
}
container hello-interval {
uses hello-interval-cfg;
container level-1 {
uses hello-interval-cfg;
description "level-1 specific cfg";
}
container level-2 {
uses hello-interval-cfg;
description "level-2 specific cfg";
}
description "Interval between
hello messages.";
}
container hello-multiplier {
uses hello-multiplier-cfg;
container level-1 {
uses hello-multiplier-cfg;
description "level-1 specific cfg";
Litkowski, et al. Expires March 24, 2017 [Page 70]
Internet-Draft isis-cfg September 2016
}
container level-2 {
uses hello-multiplier-cfg;
description "level-2 specific cfg";
}
description "Hello multiplier
configuration.";
}
container priority {
must '../interface-type = "broadcast"' {
error-message
"Priority only applies to broadcast
interfaces.";
description
"Check for broadcast interface.";
}
uses priority-cfg;
container level-1 {
uses priority-cfg;
description "level-1 specific cfg";
}
container level-2 {
uses priority-cfg;
description "level-2 specific cfg";
}
description "Priority for DIS election.";
}
container metric {
uses metric-cfg;
container level-1 {
uses metric-cfg;
description "level-1 specific cfg";
}
container level-2 {
uses metric-cfg;
description "level-2 specific cfg";
}
description "Metric configuration.";
}
container bfd {
if-feature bfd;
leaf enabled {
type boolean;
Litkowski, et al. Expires March 24, 2017 [Page 71]
Internet-Draft isis-cfg September 2016
default false;
description "
Enables BFD on the interface
";
}
description
"BFD configuration.";
}
container afs {
list af {
key af;
leaf af {
type identityref {
base rt:address-family;
}
description
"Address-family";
}
description
"List of AFs.";
}
description
"Container for address-families";
}
container mpls {
container igp-ldp-sync {
if-feature igp-ldp-sync;
leaf enable {
type boolean;
description
"Enable/disable IGP LDP sync.";
}
description
"IGP-LDP sync configuration.";
}
description
"Container for MPLS specific configuration
for ISIS.";
}
}
Litkowski, et al. Expires March 24, 2017 [Page 72]
Internet-Draft isis-cfg September 2016
grouping isis-if-topologies-cfg {
description
"ISIS interface topology cfg.";
container metric {
uses metric-cfg;
container level-1 {
uses metric-cfg;
description "level-1 specific cfg";
}
container level-2 {
uses metric-cfg;
description "level-2 specific cfg";
}
description "Metric configuration.";
}
}
/* */
augment "/rt:routing-state/"
+"rt:ribs/rt:rib/rt:routes/rt:route" {
when "rt:source-protocol = 'isis:isis'" {
description "ISIS-specific route attributes.";
}
uses route-content;
description
"This augments route object in RIB with ISIS-specific
attributes.";
}
augment "/if:interfaces/if:interface"
{
leaf clns-mtu {
type uint16;
description
"Defines CLNS MTU of the interface.";
}
description "ISO interface config.";
}
augment "/rt:routing/rt:control-plane-protocols/"
+"rt:control-plane-protocol" {
when "rt:type = 'isis:isis'" {
Litkowski, et al. Expires March 24, 2017 [Page 73]
Internet-Draft isis-cfg September 2016
description
"This augment is only valid when routing protocol
instance type is isis.";
}
description
"This augments a routing protocol instance with ISIS
specific parameters.";
container isis {
must "count(area-address) > 0" {
error-message "At least one area-address
must be configured.";
description
"Enforce configuration of at least one area.";
}
uses isis-global-cfg;
container fast-reroute {
if-feature fast-reroute;
uses fast-reroute-global-cfg;
description
"IPFRR.";
}
container multi-topology {
if-feature multi-topology;
list topology {
key "name";
leaf enable {
type boolean;
description
"Control enabling of topologies";
}
leaf name {
type leafref {
path "../../../../../../rt:ribs/rt:rib/rt:name";
}
description "RIB";
}
uses isis-global-topologies-cfg;
container fast-reroute {
if-feature fast-reroute;
Litkowski, et al. Expires March 24, 2017 [Page 74]
Internet-Draft isis-cfg September 2016
uses fast-reroute-global-cfg;
description
"IPFRR.";
}
description
"List of topologies";
}
description
"Container for multi-topology";
}
container interfaces {
list interface {
key "name";
leaf name {
type if:interface-ref;
description
"Reference to the interface within
the routing-instance.";
}
uses isis-if-cfg;
container fast-reroute {
if-feature fast-reroute;
uses fast-reroute-if-cfg;
description
"IPFRR.";
}
container multi-topology {
if-feature multi-topology;
list topology {
key name;
leaf name {
type leafref {
path "../../../../../../../../"+
"rt:ribs/rt:rib/rt:name";
}
description
"Name of RIB.";
}
container fast-reroute {
if-feature fast-reroute;
uses fast-reroute-if-cfg;
description
Litkowski, et al. Expires March 24, 2017 [Page 75]
Internet-Draft isis-cfg September 2016
"IPFRR.";
}
uses isis-if-topologies-cfg;
description
"List of topologies.";
}
description
"Container for multi-topology";
}
description
"List of ISIS interfaces.";
}
description
"This container defines ISIS interface specific
configuration objects.";
}
description
"This container defines ISIS specific configuration
objects.";
}
}
augment "/rt:routing-state/"
+"rt:control-plane-protocols/rt:control-plane-protocol" {
when "rt:type = 'isis:isis'" {
description
"This augment is only valid when routing protocol
instance type is isis.";
}
description
"This augments routing protocol instance states with ISIS
specific parameters.";
container isis {
config false;
uses isis-global-cfg;
container fast-reroute {
if-feature fast-reroute;
uses fast-reroute-global-cfg;
uses fast-reroute-global-state;
description
"IPFRR states.";
}
list topologies {
key name;
Litkowski, et al. Expires March 24, 2017 [Page 76]
Internet-Draft isis-cfg September 2016
leaf name {
type leafref {
path "../../../../../"
+"rt:ribs/rt:rib/rt:name";
}
description
"Name of RIB.";
}
container fast-route {
if-feature fast-reroute;
uses fast-reroute-global-cfg;
uses fast-reroute-global-state;
description
"IPFRR states.";
}
description
"List of topologies.";
}
container system-counters {
list level {
key level;
leaf level {
type level-number;
description
"This leaf describes the ISIS level.";
}
leaf corrupted-lsps {
type uint32;
description
"Number of corrupted in-memory LSPs detected.
LSPs received from the wire with a bad
checksum are silently dropped and not counted.
LSPs received from the wire with parse errors
are counted by lsp-errors.";
}
leaf authentication-type-fails {
type uint32;
description
"Number of authentication type mismatches.";
}
leaf authentication-fails {
type uint32;
description
"Number of authentication key failures.";
}
Litkowski, et al. Expires March 24, 2017 [Page 77]
Internet-Draft isis-cfg September 2016
leaf database-overload {
type uint32;
description
"Number of times the database has become
overloaded.";
}
leaf own-lsp-purge {
type uint32;
description
"Number of times a zero-aged copy of the
system's own LSP is received from some
other node.";
}
leaf manual-address-drop-from-area {
type uint32;
description
"Number of times a manual address
has been dropped from the area.";
}
leaf max-sequence {
type uint32;
description
"Number of times the system has attempted
to exceed the maximum sequence number.";
}
leaf sequence-number-skipped {
type uint32;
description
"Number of times a sequence number skip has
occured.";
}
leaf id-len-mismatch {
type uint32;
description
"Number of times a PDU is received with
a different value for ID field length
from that of the receiving system.";
}
leaf partition-changes {
type uint32;
description
"Number of partition changes detected.";
}
leaf lsp-errors {
type uint32;
description
"Number of LSPs with errors we have
received.";
Litkowski, et al. Expires March 24, 2017 [Page 78]
Internet-Draft isis-cfg September 2016
}
leaf spf-runs {
type uint32;
description
"Number of times we ran SPF at this level.";
}
description
"List of supported levels.";
}
description
"The container defines a list of counters
for the IS.";
}
container interfaces {
list interface {
key interface;
leaf interface {
type string;
description
"This leaf describes the name
of the interface.";
}
uses isis-if-cfg;
container fast-reroute {
if-feature fast-reroute;
uses fast-reroute-if-cfg;
description
"IPFRR.";
}
uses adjacency-state;
list topologies {
key name;
leaf name {
type leafref {
path "../../../../../"
+"../../rt:ribs/rt:rib/rt:name";
}
description
"Name of RIB.";
}
uses isis-if-topologies-cfg;
container fast-reroute {
if-feature fast-reroute;
Litkowski, et al. Expires March 24, 2017 [Page 79]
Internet-Draft isis-cfg September 2016
uses fast-reroute-if-cfg;
description
"IPFRR.";
}
uses adjacency-state;
description
"List of topologies.";
}
container event-counters {
leaf adjacency-changes {
type uint32;
description
"The number of times an adjacency state
change has occured on this interface.";
}
leaf adjacency-number {
type uint32;
description
"The number of adjacencies on this
interface.";
}
leaf init-fails {
type uint32;
description
"The number of times initialization of
this interface has failed. This counts
events such as PPP NCP failures.
Failures to form an adjacency are counted
by adjacency-rejects.";
}
leaf adjacency-rejects {
type uint32;
description
"The number of times an adjacency has been
rejected on this interface.";
}
leaf id-len-mismatch {
type uint32;
description
"The number of times an IS-IS PDU with an ID
field length different from that for this
system has been received on this interface.";
Litkowski, et al. Expires March 24, 2017 [Page 80]
Internet-Draft isis-cfg September 2016
}
leaf max-area-addresses-mismatch {
type uint32;
description
"The number of times an IS-IS PDU with
according max area address field
differs from that for
this system has been received on this
interface.";
}
leaf authentication-type-fails {
type uint32;
description
"Number of authentication type mismatches.";
}
leaf authentication-fails {
type uint32;
description
"Number of authentication key failures.";
}
leaf lan-dis-changes {
type uint32;
description
"The number of times the DIS has changed
on this interface at this level.
If the interface type is point to point,
the count is zero.";
}
description
"Provides protocol event counters.";
}
container packet-counters {
list level {
key level;
leaf level {
type level-number;
description
"This leaf describes the ISIS level.";
}
container iih {
leaf in {
type uint32;
description
"Received PDUs.";
}
leaf out {
Litkowski, et al. Expires March 24, 2017 [Page 81]
Internet-Draft isis-cfg September 2016
type uint32;
description
"Sent PDUs.";
}
description
"The number of IIH PDUs received/sent.";
}
container ish {
leaf in {
type uint32;
description
"Received PDUs.";
}
leaf out {
type uint32;
description
"Sent PDUs.";
}
description
"The number of ISH PDUs received/sent.";
}
container esh {
leaf in {
type uint32;
description
"Received PDUs.";
}
leaf out {
type uint32;
description
"Sent PDUs.";
}
description
"The number of ESH PDUs received/sent.";
}
container lsp {
leaf in {
type uint32;
description
"Received PDUs.";
}
leaf out {
type uint32;
description
"Sent PDUs.";
}
description
"The number of LSP PDUs received/sent.";
Litkowski, et al. Expires March 24, 2017 [Page 82]
Internet-Draft isis-cfg September 2016
}
container psnp {
leaf in {
type uint32;
description
"Received PDUs.";
}
leaf out {
type uint32;
description
"Sent PDUs.";
}
description
"The number of PSNP PDUs received/sent.";
}
container csnp {
leaf in {
type uint32;
description
"Received PDUs.";
}
leaf out {
type uint32;
description
"Sent PDUs.";
}
description
"The number of CSNP PDUs received/sent.";
}
container unknown {
leaf in {
type uint32;
description
"Received PDUs.";
}
leaf out {
type uint32;
description
"Sent PDUs.";
}
description
"The number of unknown PDUs received/sent.";
}
description
"List of supported levels.";
}
description
"Provides packet counters per level.";
Litkowski, et al. Expires March 24, 2017 [Page 83]
Internet-Draft isis-cfg September 2016
}
description
"List of interfaces.";
}
description
"The container defines operational parameters
of interfaces.";
}
container spf-log {
list event {
key id;
leaf id {
type uint32;
description
"This leaf defines the event identifier.
This is a purely internal value.";
}
leaf spf-type {
type enumeration {
enum full {
description
"Computation done is a Full SPF.";
}
enum incremental {
description
"Computation done is an
incremental SPF.";
}
enum route-only {
description
"Computation done is a
reachability computation
only.";
}
}
description
"This leaf describes the type of computation
used.";
}
leaf level {
type level-number;
description
"This leaf describes the level affected by the
the computation.";
}
leaf spf-delay {
Litkowski, et al. Expires March 24, 2017 [Page 84]
Internet-Draft isis-cfg September 2016
type uint32;
units "milliseconds";
description
"This leaf describes the SPF delay that
was used for this event.";
}
leaf schedule-timestamp {
type yang:timestamp;
description
"This leaf describes the timestamp
when the computation was scheduled.";
}
leaf start-timestamp {
type yang:timestamp;
description
"This leaf describes the timestamp
when the computation was started.";
}
leaf end-timestamp {
type yang:timestamp;
description
"This leaf describes the timestamp
when the computation was ended.";
}
list trigger-lsp {
key "lsp";
leaf lsp {
type lsp-id;
description
"This leaf describes the LSPID
of the LSP.";
}
leaf sequence {
type uint32;
description
"This leaf describes the sequence
number of the LSP.";
}
description
"This leaf describes list of LSPs
that triggered the computation.";
}
description
"List of computation events.";
}
description
"This container lists the SPF computation events.";
Litkowski, et al. Expires March 24, 2017 [Page 85]
Internet-Draft isis-cfg September 2016
}
container lsp-log {
list event {
key id;
leaf id {
type uint32;
description
"This leaf defines the event identifier.
This is a purely internal value.";
}
leaf level {
type level-number;
description
"This leaf describes the level affected by the
the computation.";
}
container lsp {
leaf lsp {
type lsp-id;
description
"This leaf describes the LSPID
of the LSP.";
}
leaf sequence {
type uint32;
description
"This leaf describes the sequence
number of the LSP.";
}
description
"This container describes the received LSP
, in case of local LSP update the local
LSP ID is referenced.";
}
leaf received-timestamp {
type yang:timestamp;
description
"This leaf describes the timestamp
when the LSP was received. In case of
local LSP update, the timestamp refers
to the local LSP update time.";
}
leaf change {
Litkowski, et al. Expires March 24, 2017 [Page 86]
Internet-Draft isis-cfg September 2016
type bits {
bit refresh {
position 0;
description
"Refresh LSP, nothing has changed.";
}
bit link-down {
position 1;
description
"One or more links are down.";
}
bit link-up {
position 2;
description
"One or more links are up.";
}
bit link-metric-change {
position 3;
description
"One or more links experienced
a metric change.";
}
bit link-other-change {
position 4;
description
"One or more links experienced
a change that does not affect state
or metric.";
}
bit prefix-down {
position 5;
description
"One or more links are down.";
}
bit prefix-up {
position 6;
description
"One or more prefixes are up.";
}
bit prefix-metric-change {
position 7;
description
"One or more prefixes experienced
a metric change.";
}
bit prefix-other-change {
position 8;
description
Litkowski, et al. Expires March 24, 2017 [Page 87]
Internet-Draft isis-cfg September 2016
"One or more prefixes experienced
a change that does not affect state
or metric.";
}
bit other-change {
position 9;
description
"One or more component changed that
is not a prefix or link.";
}
}
description
"This leaf describes the type of change
in the LSP.";
}
description
"List of LSP events.";
}
description
"This container lists the LSP reception events.
Local LSP modification are also contained in the
list.";
}
container database {
list level-db {
key level;
leaf level {
type level-number;
description
"Current level number";
}
list lsp {
key lsp-id;
uses database;
description
"List of LSPs in LSDB.";
}
description
"This container describes the list of LSPs
in the level x database.";
}
description
Litkowski, et al. Expires March 24, 2017 [Page 88]
Internet-Draft isis-cfg September 2016
"This container describes ISIS Link State
databases.";
}
container hostnames {
list hostname {
key system-id;
leaf system-id {
type system-id;
description
"This leaf describes the system-id
associated with the hostname.";
}
leaf hostname {
type string;
description
"This leaf describes the hostname
associated with the system ID.";
}
description
"List of system-id/hostname associations";
}
description
"This container describes the list
of binding between system-id and
hostnames.";
}
description
"This container defines various ISIS states objects.";
}
}
/* RPC methods */
rpc clear-adjacency {
description
"This RPC request clears a particular
set of ISIS adjacencies. If the operation
fails for ISIS internal reason, then
error-tag and error-app-tag should be set
to a meaningful value.";
input {
leaf routing-protocol-instance-name {
type instance-state-ref;
Litkowski, et al. Expires March 24, 2017 [Page 89]
Internet-Draft isis-cfg September 2016
mandatory "true";
description
"Name of the ISIS protocol instance whose ISIS
information is being queried.
If the ISIS instance with name equal to the
value of this parameter doesn't exist, then this
operation SHALL fail with error-tag 'data-missing'
and error-app-tag
'routing-protocol-instance-not-found'.";
}
leaf level {
type level;
description
"ISIS level of the adjacency to be cleared.
If ISIS level is level-1-2, both level 1 and level 2
adjacencies would be cleared.
If the value provided is different from the one
authorized in the enum type, then this
operation SHALL fail with error-tag 'data-missing'
and error-app-tag
'bad-isis-level'.
";
}
leaf interface {
type string;
description
"Name of the ISIS interface.
If the ISIS interface with name equal to the
value of this parameter doesn't exist, then this
operation SHALL fail with error-tag 'data-missing'
and error-app-tag
'isis-interface-not-found'.";
}
}
}
rpc clear-database {
description
"This RPC request clears a particular
ISIS database. If the operation
fails for ISIS internal reason, then
error-tag and error-app-tag should be set
to a meaningful value.";
input {
Litkowski, et al. Expires March 24, 2017 [Page 90]
Internet-Draft isis-cfg September 2016
leaf routing-protocol-instance-name {
type instance-state-ref;
mandatory "true";
description
"Name of the ISIS protocol instance whose ISIS
information is being queried.
If the ISIS instance with name equal to the
value of this parameter doesn't exist, then this
operation SHALL fail with error-tag 'data-missing'
and error-app-tag
'routing-protocol-instance-not-found'.";
}
leaf level {
type level;
description
"ISIS level of the adjacency to be cleared.
If ISIS level is level-1-2, both level 1 and level 2
adjacencies would be cleared.
If the value provided is different from the one
authorized in the enum type, then this
operation SHALL fail with error-tag 'data-missing'
and error-app-tag
'bad-isis-level'.
";
}
}
}
/* Notifications */
notification database-overload {
uses notification-instance-hdr;
leaf overload {
type enumeration {
enum "off" {
description
"The system has left overload condition.";
}
enum "on" {
description
"The system is in overload condition.";
}
Litkowski, et al. Expires March 24, 2017 [Page 91]
Internet-Draft isis-cfg September 2016
}
description
"Describes the new overload state of the instance.";
}
description
"This notification is sent when an ISIS instance
overload condition changes.";
}
notification lsp-too-large {
uses notification-instance-hdr;
uses notification-interface-hdr;
leaf pdu-size {
type uint32;
description
"Size of the PDU";
}
leaf lsp-id {
type lsp-id;
description
"LSP ID.";
}
description
"This notification is sent when we attempt
to propagate an LSP that is larger than the
dataLinkBlockSize for the circuit.
The notification generation must be throttled
with at least a 5 second gap.
";
}
notification corrupted-lsp-detected {
uses notification-instance-hdr;
leaf lsp-id {
type lsp-id;
description
"LSP ID.";
}
description
"This notification is sent when we find
that an LSP that was stored in memory has
become corrupted.
";
}
notification attempt-to-exceed-max-sequence {
uses notification-instance-hdr;
Litkowski, et al. Expires March 24, 2017 [Page 92]
Internet-Draft isis-cfg September 2016
leaf lsp-id {
type lsp-id;
description
"LSP ID.";
}
description
"This notification is sent when the system
wraps the 32-bit sequence counter of an LSP.
";
}
notification id-len-mismatch {
uses notification-instance-hdr;
uses notification-interface-hdr;
leaf pdu-field-len {
type uint8;
description
"Size of the ID length in the received PDU";
}
leaf raw-pdu {
type binary;
description
"Received raw PDU.";
}
description
"This notification is sent when we receive a PDU
with a different value for the System ID length.
The notification generation must be throttled
with at least a 5 second gap.
";
}
notification max-area-addresses-mismatch {
uses notification-instance-hdr;
uses notification-interface-hdr;
leaf max-area-addresses {
type uint8;
description
"Received number of supported areas";
}
leaf raw-pdu {
type binary;
description
"Received raw PDU.";
}
description
Litkowski, et al. Expires March 24, 2017 [Page 93]
Internet-Draft isis-cfg September 2016
"This notification is sent when we receive a PDU
with a different value for the Maximum Area Addresses.
The notification generation must be throttled
with at least a 5 second gap.
";
}
notification own-lsp-purge {
uses notification-instance-hdr;
uses notification-interface-hdr;
leaf lsp-id {
type lsp-id;
description
"LSP ID.";
}
description
"This notification is sent when the system
receives a PDU with its own system ID and zero age.
";
}
notification sequence-number-skipped {
uses notification-instance-hdr;
uses notification-interface-hdr;
leaf lsp-id {
type lsp-id;
description
"LSP ID.";
}
description
"This notification is sent when the system
receives a PDU with its own system ID and
different contents. The system has to reissue
the LSP with a higher sequence number.
";
}
notification authentication-type-failure {
uses notification-instance-hdr;
uses notification-interface-hdr;
leaf raw-pdu {
type binary;
description
"Received raw PDU.";
}
description
"This notification is sent when the system
receives a PDU with the wrong authentication type
Litkowski, et al. Expires March 24, 2017 [Page 94]
Internet-Draft isis-cfg September 2016
field.
The notification generation must be throttled with
at least a 5 second gap.
";
}
notification authentication-failure {
uses notification-instance-hdr;
uses notification-interface-hdr;
leaf raw-pdu {
type binary;
description
"Received raw PDU.";
}
description
"This notification is sent when the system
receives a PDU with the wrong authentication
information.
The notification generation must be throttled with
at least a 5 second gap.
";
}
notification version-skew {
uses notification-instance-hdr;
uses notification-interface-hdr;
leaf protocol-version {
type uint8;
description
"Protocol version received in the PDU.";
}
leaf raw-pdu {
type binary;
description
"Received raw PDU.";
}
description
"This notification is sent when the system
receives a PDU with a different protocol version
number.
The notification generation must be throttled with at least
a 5 second gap.
";
}
notification area-mismatch {
uses notification-instance-hdr;
uses notification-interface-hdr;
Litkowski, et al. Expires March 24, 2017 [Page 95]
Internet-Draft isis-cfg September 2016
leaf raw-pdu {
type binary;
description
"Received raw PDU.";
}
description
"This notification is sent when the system
receives a Hello PDU from an IS that does
not share any area address.
The notification generation must be throttled with at least
a 5 second gap.
";
}
notification rejected-adjacency {
uses notification-instance-hdr;
uses notification-interface-hdr;
leaf raw-pdu {
type binary;
description
"Received raw PDU.";
}
leaf reason {
type string;
description
"The system may provide a reason to reject the
adjacency. If the reason is not available,
the system use an empty string.";
}
description
"This notification is sent when the system
receives a Hello PDU from an IS but does not
establish an adjacency for some reason.
The notification generation must be throttled with at least
a 5 second gap.
";
}
notification protocols-supported-mismatch {
uses notification-instance-hdr;
uses notification-interface-hdr;
leaf raw-pdu {
type binary;
description
"Received raw PDU.";
}
leaf-list protocols {
Litkowski, et al. Expires March 24, 2017 [Page 96]
Internet-Draft isis-cfg September 2016
type uint8;
description
"The list of protocols supported by the
remote system.";
}
description
"This notification is sent when the system
receives a non pseudonode LSP that has no matching
protocol supported.
The notification generation must be throttled with at least
a 5 second gap.
";
}
notification lsp-error-detected {
uses notification-instance-hdr;
uses notification-interface-hdr;
leaf lsp-id {
type lsp-id;
description
"LSP ID.";
}
leaf raw-pdu {
type binary;
description
"Received raw PDU.";
}
leaf error-offset {
type uint32;
description
"If the problem is a malformed TLV,
the error-offset points to the start of the TLV.
If the problem is with the LSP header,
the error-offset points to the suspicious byte";
}
leaf tlv-type {
type uint8;
description
"if the problem is a malformed TLV, the tlv-type is set
to the type value of the suspicious TLV.
Otherwise this leaf is not present.";
}
description
"This notification is sent when the system
receives a LSP with a parse error.
The notification generation must be throttled with at least
a 5 second gap.
";
Litkowski, et al. Expires March 24, 2017 [Page 97]
Internet-Draft isis-cfg September 2016
}
notification adjacency-change {
uses notification-instance-hdr;
uses notification-interface-hdr;
leaf neighbor {
type string;
description
"Describes the name of the neighbor. If the
name of the neighbor is not available, the
field would be empty.";
}
leaf neighbor-system-id {
type system-id;
description
"Describes the system-id of the neighbor.";
}
leaf level {
type level;
description
"Describes the ISIS level of the adjacency.";
}
leaf state {
type enumeration {
enum "Up" {
description
"This state describes that
adjacency is established.";
}
enum "Down" {
description
"This state describes that
adjacency is no more established.";
}
}
description
"This leaf describes the new state of the
ISIS adjacency.";
}
leaf reason {
type string;
description
"If the adjacency is going to DOWN,
this leaf provides a reason for the adjacency
going down. The reason is provided as a text.
If the adjacency is going to UP, no reason is
provided.";
}
Litkowski, et al. Expires March 24, 2017 [Page 98]
Internet-Draft isis-cfg September 2016
description
"This notification is sent when an ISIS adjacency
moves to Up state or to Down state.";
}
notification lsp-received {
uses notification-instance-hdr;
uses notification-interface-hdr;
leaf lsp-id {
type lsp-id;
description
"LSP ID.";
}
leaf sequence {
type uint32;
description
"Sequence number of the received LSP.";
}
leaf received-timestamp {
type yang:timestamp;
description
"This leaf describes the timestamp
when the LSP was received. ";
}
leaf neighbor-system-id {
type system-id;
description
"Describes the system-id of the neighbor
that sent the LSP.";
}
description
"This notification is sent when a LSP
is received.
The notification generation must be throttled with at least
a 5 second gap. ";
}
notification lsp-generation {
uses notification-instance-hdr;
leaf lsp-id {
type lsp-id;
description
"LSP ID.";
}
leaf sequence {
Litkowski, et al. Expires March 24, 2017 [Page 99]
Internet-Draft isis-cfg September 2016
type uint32;
description
"Sequence number of the received LSP.";
}
leaf send-timestamp {
type yang:timestamp;
description
"This leaf describes the timestamp
when our LSP was regenerated. ";
}
description
"This notification is sent when a LSP
is regenerated.
The notification generation must be throttled with at least
a 5 second gap. ";
}
}
<CODE ENDS>
8. IS-IS Segment Routing YANG Module
<CODE BEGINS> file "ietf-isis-sr@2016-09-20.yang"
module ietf-isis-sr {
namespace "urn:ietf:params:xml:ns:"
+ "yang:ietf-isis-sr";
prefix isis-sr;
import ietf-routing {
prefix "rt";
}
import ietf-segment-routing {
prefix "sr";
}
import ietf-isis {
prefix "isis";
}
organization
"IETF ISIS Working Group";
Litkowski, et al. Expires March 24, 2017 [Page 100]
Internet-Draft isis-cfg September 2016
contact
"WG List: <mailto:spring@ietf.org>
Editor: Stephane Litkowski
<mailto:stephane.litkowski@orange.com>
Acee Lindem
<mailto:acee@cisco.com>
Yingzhen Qu
<mailto:yiqu@cisco.com>
Pushpasis Sarkar
<mailto:psarkar@juniper.net>
Ing-Wher Chen
<mailto:ing-wher.chen@ericsson.com>
Jeff Tantsura
<mailto:jeff.tantsura@ericsson.com>
";
description
"The YANG module defines a generic configuration model for
Segment routing ISIS extensions common across all of the vendor
implementations.";
revision 2016-09-20 {
description
"
Align to draft-ietf-netmod-routing-cfg-23.
";
reference "draft-ietf-isis-yang-isis-cfg-09";
}
revision 2016-03-21 {
description "
* Removed routing-instance in path as per
core routing model v21
";
reference "";
}
revision 2015-09-18 {
description "no modif";
reference "";
}
revision 2015-07-02 {
description
"
* Add TILFA and rLFA SR
* Add container to SRGB
Litkowski, et al. Expires March 24, 2017 [Page 101]
Internet-Draft isis-cfg September 2016
";
reference "";
}
revision 2015-05-27 {
description "
* Initialization
";
reference "";
}
/* Identities */
/* Features */
feature remote-lfa-sr {
description
"Enhance rLFA to use SR path.";
}
feature ti-lfa {
description
"Enhance IPFRR with ti-lfa
support";
}
/* Groupings */
grouping adjacency-state {
description
"This group will extend adjacency state.";
list adjacency-sid {
key value;
leaf af {
type identityref {
base rt:address-family;
}
description
"Address-family associated with the
segment ID";
}
leaf value {
type uint32;
description
"Value of the Adj-SID.";
}
Litkowski, et al. Expires March 24, 2017 [Page 102]
Internet-Draft isis-cfg September 2016
leaf weight {
type uint8;
description
"Weight associated with
the adjacency SID.";
}
leaf protection-requested {
type boolean;
description
"Describe if the adjacency SID
must be protected.";
}
description
"List of adjacency Segment IDs.";
}
}
grouping prefix-segment-id {
description
"This group defines segment routing extensions
for prefixes.";
list sid-list {
key value;
leaf flags {
type bits {
bit readvertisment {
position 7;
description
"If set, then the prefix to
which this Prefix-SID is attached,
has been propagated by the
router either from another level
or from redistribution.";
}
bit php {
position 5;
description
"If set, then the penultimate hop MUST NOT
pop the Prefix-SID before delivering the packet
to the node
that advertised the Prefix-SID.";
}
bit explicit-null {
position 4;
description
Litkowski, et al. Expires March 24, 2017 [Page 103]
Internet-Draft isis-cfg September 2016
"If set, any upstream neighbor of
the Prefix-SID originator MUST replace
the Prefix-SID with a
Prefix-SID having an
Explicit-NULL value (0 for IPv4 and 2 for
IPv6) before forwarding the packet.";
}
bit value {
position 3;
description
"If set, then the Prefix-SID carries a
value (instead of an index).
By default the flag is UNSET.";
}
bit local {
position 2;
description
"If set, then the value/index carried by
the Prefix-SID has local significance.
By default the flag is UNSET.";
}
}
description
"Describes flags associated with the
segment ID.";
}
leaf algorithm {
type uint8;
description
"Algorithm to be used for path computation.";
}
leaf value {
type uint32;
description
"Value of the prefix-SID.";
}
description
"List of segments.";
}
}
grouping adjacency-segment-id {
description
"This group defines segment routing extensions
for adjacencies.";
Litkowski, et al. Expires March 24, 2017 [Page 104]
Internet-Draft isis-cfg September 2016
list sid-list {
key value;
leaf flags {
type bits {
bit address-family {
position 7;
description
"If unset, then the Adj-SID refers
to an adjacency with outgoing IPv4 encapsulation.
If set then the Adj-SID refers to an adjacency
with outgoing IPv6 encapsulation.";
}
bit backup {
position 6;
description
"If set, the Adj-SID refers to an
adjacency being protected
(e.g.: using IPFRR or MPLS-FRR)";
}
bit value {
position 5;
description
"If set, then the SID carries a
value (instead of an index).
By default the flag is SET.";
}
bit local {
position 4;
description
"If set, then the value/index carried by
the SID has local significance.
By default the flag is SET.";
}
bit set {
position 3;
description
"When set, the S-Flag indicates that the
Adj-SID refers to a set of adjacencies";
}
}
description
"Describes flags associated with the
segment ID.";
}
Litkowski, et al. Expires March 24, 2017 [Page 105]
Internet-Draft isis-cfg September 2016
leaf weight {
type uint8;
description
"The value represents the weight of the Adj-SID
for the purpose of load balancing.";
}
leaf neighbor-id {
type isis:system-id;
description
"Describes the system ID of the neighbor
associated with the SID value. This is only
used on LAN adjacencies.";
}
leaf value {
type uint32;
description
"Value of the Adj-SID.";
}
description
"List of segments.";
}
}
grouping segment-routing-binding-tlv {
list segment-routing-bindings {
key "fec range";
leaf fec {
type string;
description
"IP (v4 or v6) range to be bound to SIDs.";
}
leaf range {
type uint16;
description
"Describes number of elements to assign
a binding to.";
}
leaf flags {
type bits {
bit address-family {
position 7;
description
"If unset, then the Prefix FEC
carries an IPv4 Prefix.
Litkowski, et al. Expires March 24, 2017 [Page 106]
Internet-Draft isis-cfg September 2016
If set then the Prefix FEC carries an
IPv6 Prefix.";
}
bit mirror {
position 6;
description
"Set if the advertised SID/path
corresponds to a mirrored context.
";
}
bit flooding {
position 5;
description
"If the S bit is set(1),
the IS-IS Router CAPABILITY TLV
MUST be flooded across the entire routing domain.
If the S bit is
not set(0), the TLV MUST NOT be leaked between levels.
This bit MUST NOT be altered during the TLV leaking.";
}
bit down {
position 4;
description
"When the IS-IS Router CAPABILITY TLV is
leaked from level-2 to level-1, the D bit
MUST be set. Otherwise, this bit MUST
be clear. IS-IS Router capability TLVs
with the D bit set MUST NOT
be leaked from level-1 to level-2.
This is to prevent TLV looping.
";
}
bit attached {
position 3;
description
"The originator of the SID/Label Binding
TLV MAY set the A bit in order to signal
that the prefixes and
SIDs advertised in the SID/Label Binding
TLV are directly
connected to their originators.
";
}
}
description
"Flags of the binding.";
}
Litkowski, et al. Expires March 24, 2017 [Page 107]
Internet-Draft isis-cfg September 2016
leaf weight {
type uint8;
description
"Weight of the path for loadbalancing purpose.";
}
container binding {
container prefix-sid {
uses prefix-segment-id;
description
"Binding prefix SID to the range.";
}
leaf ero-metric {
type uint32;
description
"Cost of ERO path.";
}
container ero {
leaf address-family {
type identityref {
base rt:address-family;
}
description
"Address-family.";
}
leaf loose {
type boolean;
description
"Set to true,
if hop is a loose hop.";
}
leaf address {
type string;
description
"IP address of a node on the
path.";
}
description
"Binding ERO path to the range.";
}
container backup-ero {
leaf address-family {
type identityref {
base rt:address-family;
}
description
Litkowski, et al. Expires March 24, 2017 [Page 108]
Internet-Draft isis-cfg September 2016
"Address-family.";
}
leaf loose {
type boolean;
description
"Set to true,
if hop is a loose hop.";
}
leaf address {
type string;
description
"IP address of a node on the
path.";
}
description
"Binding backup ERO path to the range.";
}
container unnumbered-interface-id-ero {
leaf router-id {
type string;
description
"Router ID of the node owning the interface.";
}
leaf interface-id {
type uint32;
description
"Interface ID on which the path is built.";
}
description
"Binding a path over unnumbered interface.";
}
container backup-unnumbered-interface-id-ero {
leaf router-id {
type string;
description
"Router ID of the node owning the interface.";
}
leaf interface-id {
type uint32;
description
"Interface ID on which the path is built.";
}
description
"Binding a backup path over unnumbered interface.";
}
description
Litkowski, et al. Expires March 24, 2017 [Page 109]
Internet-Draft isis-cfg September 2016
"Bindings associated with the range.";
}
description
"This container describes list of SID/Label
bindings.
ISIS reference is TLV 149.";
}
description
"Defines binding TLV for database.";
}
/* Cfg */
augment "/rt:routing/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis" {
when "rt:type = 'isis:isis'" {
description
"This augment ISIS routing protocol when used";
}
description
"This augments ISIS protocol configuration
with segment routing.";
uses sr:controlplane-cfg;
container protocol-srgb {
if-feature sr:protocol-srgb;
uses sr:srgb-cfg;
description
"Per-protocol SRGB.";
}
}
augment "/rt:routing/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:interfaces/isis:interface" {
when "rt:type = 'isis:isis'" {
description
"This augment ISIS routing protocol when used";
}
description
"This augments ISIS protocol configuration
with segment routing.";
uses sr:igp-interface-cfg;
Litkowski, et al. Expires March 24, 2017 [Page 110]
Internet-Draft isis-cfg September 2016
}
augment "/rt:routing/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:interfaces/isis:interface"+
"/isis:fast-reroute" {
when "rt:type = 'isis:isis'" {
description
"This augment ISIS routing protocol when used";
}
description
"This augments ISIS IP FRR with TILFA.";
container ti-lfa {
if-feature ti-lfa;
leaf enable {
type boolean;
description
"Enables TI-LFA computation.";
}
description
"TILFA configuration.";
}
}
augment "/rt:routing/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:interfaces/isis:interface"+
"/isis:fast-reroute/isis:lfa/isis:remote-lfa" {
when "rt:type = 'isis:isis'" {
description
"This augment ISIS routing protocol when used";
}
description
"This augments ISIS remoteLFA config with
use of segment-routing path.";
leaf use-segment-routing-path {
if-feature remote-lfa-sr;
type boolean;
description
"force remote LFA to use segment routing
path instead of LDP path.";
}
}
Litkowski, et al. Expires March 24, 2017 [Page 111]
Internet-Draft isis-cfg September 2016
/* Operational states */
augment "/rt:routing-state/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis" {
when "rt:type = 'isis:isis'" {
description
"This augment ISIS routing protocol when used";
}
description
"This augments ISIS protocol configuration
with segment routing.";
uses sr:controlplane-cfg;
container protocol-srgb {
if-feature sr:protocol-srgb;
uses sr:srgb-cfg;
description
"Per-protocol SRGB.";
}
}
augment "/rt:routing-state/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:interfaces/isis:interface" {
when "rt:type = 'isis:isis'" {
description
"This augment ISIS routing protocol when used";
}
description
"This augments ISIS protocol configuration
with segment routing.";
uses sr:igp-interface-cfg;
}
augment "/rt:routing-state/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:interfaces/isis:interface" +
"/isis:adjacencies/isis:adjacency" {
when "rt:type = 'isis:isis'" {
description
"This augment ISIS routing protocol when used";
}
description
"This augments ISIS protocol configuration
with segment routing.";
Litkowski, et al. Expires March 24, 2017 [Page 112]
Internet-Draft isis-cfg September 2016
uses adjacency-state;
}
augment "/rt:routing-state/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:database/isis:level-db/isis:lsp"+
"/isis:extended-is-neighbor/isis:neighbor" {
description
"This augments ISIS protocol LSDB neighbor.";
uses adjacency-segment-id;
}
augment "/rt:routing-state/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:database/isis:level-db/isis:lsp"+
"/isis:mt-is-neighbor/isis:neighbor" {
description
"This augments ISIS protocol LSDB neighbor.";
uses adjacency-segment-id;
}
augment "/rt:routing-state/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:database/isis:level-db/isis:lsp"+
"/isis:extended-ipv4-reachability/isis:prefixes" {
description
"This augments ISIS protocol LSDB prefix.";
uses prefix-segment-id;
}
augment "/rt:routing-state/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:database/isis:level-db/isis:lsp"+
"/isis:mt-extended-ipv4-reachability/isis:prefixes" {
description
"This augments ISIS protocol LSDB prefix.";
uses prefix-segment-id;
}
augment "/rt:routing-state/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:database/isis:level-db/isis:lsp"+
"/isis:ipv6-reachability/isis:prefixes" {
description
"This augments ISIS protocol LSDB prefix.";
uses prefix-segment-id;
}
Litkowski, et al. Expires March 24, 2017 [Page 113]
Internet-Draft isis-cfg September 2016
augment "/rt:routing-state/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:database/isis:level-db/isis:lsp"+
"/isis:mt-ipv6-reachability/isis:prefixes" {
description
"This augments ISIS protocol LSDB prefix.";
uses prefix-segment-id;
}
augment "/rt:routing-state/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:database/isis:level-db/isis:lsp" {
description
"This augments ISIS protocol LSDB.";
uses segment-routing-binding-tlv;
}
/* Notifications */
}
<CODE ENDS>
9. Security Considerations
Configuration and state data defined in this document are designed to
be accessed via the NETCONF protocol [RFC6241].
As IS-IS is an IGP protocol (critical piece of the network), ensuring
stability and security of the protocol is mandatory for the network
service.
Authors recommends to implement NETCONF access control model
([RFC6536]) to restrict access to all or part of the configuration to
specific users. Access control to RPCs is also critical as RPC
permits to clear protocol datastructures that would definitively
impact the network service. This kind of RPC needs only to be used
in specific cases by well-known experienced users.
Authors consider that all the configuration is considered as
sensitive/vulnerable as well as RPCs. But security teams can decide
to open some part of the configuration to less experienced users
depending on the internal organization, for example:
Litkowski, et al. Expires March 24, 2017 [Page 114]
Internet-Draft isis-cfg September 2016
o User FullWrite: would access to the whole data model. This kind
of profile may be restricted to few experienced people.
o User PartialWrite: would only access to configuration part within
/isis/interfaces/interface. So this kind of profile is restricted
to creation/modification/deletion of interfaces. This profile
does not have access to RPC.
o User Read: would only access to state part /isis-state.
Unauthorized access to configuration or RPC may cause high damages to
the network service.
The /isis-state/database may contain authentication information. As
presented in the description of the /isis-state/database/level-
1/lsp/authentication/authentication-key, the authentication MUST
never be presented in plaintext format for security reason. Authors
recommends the usage of MD5 to present the authentication-key.
Some authentication-key may also be present in the /isis
configuration. When configuring IS-IS using the NETCONF protocol,
authors recommends the usage of secure transport of NETCONF using SSH
([RFC6242]).
10. Contributors
Authors would like to thank Kiran Agrahara Sreenivasa, Dean
Bogdanovic, Yingzhen Qu, Yi Yang for their major contributions to the
draft.
11. Acknowledgements
TBD.
12. IANA Considerations
The IANA is requested to assign two new URIs from the IETF XML
registry ([RFC3688]). Authors are suggesting the following URIs :
URI: urn:ietf:params:xml:ns:yang:ietf-isis
Registrant Contact: IS-IS WG
XML: N/A, the requested URI is an XML namespace
URI: urn:ietf:params:xml:ns:yang:ietf-isis-sr
Registrant Contact: IS-IS WG
XML: N/A, the requested URI is an XML namespace
Litkowski, et al. Expires March 24, 2017 [Page 115]
Internet-Draft isis-cfg September 2016
This document also requests two new YANG modules name in the YANG
Module Names registry ([RFC6020]) with the following suggestion :
name: ietf-isis
namespace: urn:ietf:params:xml:ns:yang:ietf-isis
prefix: isis
reference: RFC XXXX
name: ietf-isis-sr
namespace: urn:ietf:params:xml:ns:yang:ietf-isis-sr
prefix: isis-sr
reference: RFC XXXX
13. Normative References
[I-D.ietf-netmod-routing-cfg]
Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Management", draft-ietf-netmod-routing-cfg-23 (work in
progress), August 2016.
[I-D.ietf-rtgwg-yang-key-chain]
Lindem, A., Qu, Y., Yeung, D., Chen, I., Zhang, Z., and Y.
Yang, "Routing Key Chain YANG Data Model", draft-ietf-
rtgwg-yang-key-chain-09 (work in progress), September
2016.
[I-D.ietf-spring-sr-yang]
Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG
Data Model for Segment Routing", draft-ietf-spring-sr-
yang-03 (work in progress), July 2016.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<http://www.rfc-editor.org/info/rfc5880>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>.
Litkowski, et al. Expires March 24, 2017 [Page 116]
Internet-Draft isis-cfg September 2016
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<http://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, DOI
10.17487/RFC6536, March 2012,
<http://www.rfc-editor.org/info/rfc6536>.
Appendix A. Example: NETCONF <get> Reply
This section gives an example of a reply to the NETCONF <get> request
for a device that implements the data model defined in this document.
The example is written in XML.
<?xml version="1.0" encoding="utf-8"?>
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
<routing-instance>
<name>SLI</name>
<router-id>1.1.1.1</router-id>
<description/>
<default-ribs>
<default-rib>
<address-family>ipv4-unicast</address-family>
<rib-name>default</rib-name>
</default-rib>
</default-ribs>
<interfaces>
<interface>
<name>Loopback0</name>
</interface>
<interface>
<name>Eth1</name>
</interface>
</interfaces>
<routing-protocols>
<routing-protocol>
<name>ISIS</name>
<description/>
<type>isis:isis</type>
<connected-ribs>
<connected-rib>
Litkowski, et al. Expires March 24, 2017 [Page 117]
Internet-Draft isis-cfg September 2016
<rib-name>default</rib-name>
<import-filter/>
<export-filter/>
</connected-rib>
</connected-ribs>
<isis xmlns="urn:ietf:params:xml:ns:yang:ietf-isis">
<instance>
<routing-instance>SLI</routing-instance>
<level-type>level-2</level-type>
<system-id>87FC.FCDF.4432</system-id>
<area-address>49.0001</area-address>
<mpls-te>
<ipv4-router-id>1.1.1.1</ipv4-router-id>
</mpls-te>
<lsp-lifetime>65535</lsp-lifetime>
<lsp-refresh>65000</lsp-refresh>
<authentication>
<key>ThisIsThePassword</key>
<type>plain-text</type>
<level>level-2</level>
</authentication>
<metric-type>
<value>wide</value>
</metric-type>
<default-metric>
<value>111111</value>
</default-metric>
<af>
<af>ipv4-unicast</af>
<enabled>true</enabled>
</af>
<interfaces>
<interface>
<name>Loopback0</name>
<tag>200</tag>
<metric>
<value>0</value>
</metric>
<passive>true</passive>
</interface>
<interface>
<name>Eth1</name>
<level-type>level-2</level-type>
<interface-type>point-to-point</interface-type>
<metric>
<value>167890</value>
</metric>
Litkowski, et al. Expires March 24, 2017 [Page 118]
Internet-Draft isis-cfg September 2016
</interface>
</interfaces>
</instance>
</isis>
</routing-protocol>
</routing-protocols>
</routing-instance>
<ribs>
<rib>
<name>default</name>
<address-family>ipv4-unicast</address-family>
<description/>
<recipient-ribs>
<recipient-rib>
<rib-name/>
<filter/>
</recipient-rib>
</recipient-ribs>
</rib>
</ribs>
<route-filters>
<route-filter>
<name/>
<description/>
<type/>
</route-filter>
</route-filters>
</routing>
<interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces">
<interface>
<name>Loopback0</name>
<description/>
<type/>
<link-up-down-trap-enable/>
<ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip">
<mtu/>
<address>
<ip>1.1.1.1</ip>
<prefix-length>32</prefix-length>
</address>
</ipv4>
</interface>
<interface>
<name>Eth1</name>
<description/>
<type/>
<link-up-down-trap-enable/>
Litkowski, et al. Expires March 24, 2017 [Page 119]
Internet-Draft isis-cfg September 2016
<ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip">
<mtu/>
<address>
<ip>10.0.0.1</ip>
<prefix-length>30</prefix-length>
</address>
</ipv4>
</interface>
</interfaces>
</data>
Authors' Addresses
Stephane Litkowski
Orange
Email: stephane.litkowski@orange.com
Derek Yeung
Cisco Systems
Email: myeung@cisco.com
Acee Lindem
Cisco Systems
Email: acee@cisco.com
Jeffrey Zhang
Juniper Networks
Email: zzhang@juniper.net
Ladislav Lhotka
CZ.NIC
Email: lhotka@nic.cz
Litkowski, et al. Expires March 24, 2017 [Page 120]
