draft-ietf-isis-yang-isis-cfg-25.txt   draft-ietf-isis-yang-isis-cfg-26.txt 
IS-IS Working Group S. Litkowski IS-IS Working Group S. Litkowski
Internet-Draft Orange Internet-Draft Orange
Intended status: Standards Track D. Yeung Intended status: Standards Track D. Yeung
Expires: May 30, 2019 Arrcus, Inc Expires: June 7, 2019 Arrcus, Inc
A. Lindem A. Lindem
Cisco Systems Cisco Systems
J. Zhang J. Zhang
Juniper Networks Juniper Networks
L. Lhotka L. Lhotka
CZ.NIC CZ.NIC
November 26, 2018 December 04, 2018
YANG Data Model for IS-IS protocol YANG Data Model for IS-IS protocol
draft-ietf-isis-yang-isis-cfg-25 draft-ietf-isis-yang-isis-cfg-26
Abstract Abstract
This document defines a YANG data model that can be used to configure This document defines a YANG data model that can be used to configure
and manage IS-IS protocol on network elements. and manage IS-IS protocol on network elements.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 30, 2019. This Internet-Draft will expire on June 7, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 28 skipping to change at page 2, line 28
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3 2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3
2.1. IS-IS Configuration . . . . . . . . . . . . . . . . . . . 9 2.1. IS-IS Configuration . . . . . . . . . . . . . . . . . . . 9
2.2. Multitopology Parameters . . . . . . . . . . . . . . . . 9 2.2. Multitopology Parameters . . . . . . . . . . . . . . . . 9
2.3. Per-Level Parameters . . . . . . . . . . . . . . . . . . 10 2.3. Per-Level Parameters . . . . . . . . . . . . . . . . . . 10
2.4. Per-Interface Parameters . . . . . . . . . . . . . . . . 11 2.4. Per-Interface Parameters . . . . . . . . . . . . . . . . 11
2.5. Authentication Parameters . . . . . . . . . . . . . . . . 17 2.5. Authentication Parameters . . . . . . . . . . . . . . . . 18
2.6. IGP/LDP synchronization . . . . . . . . . . . . . . . . . 17 2.6. IGP/LDP synchronization . . . . . . . . . . . . . . . . . 18
2.7. ISO parameters . . . . . . . . . . . . . . . . . . . . . 17 2.7. ISO parameters . . . . . . . . . . . . . . . . . . . . . 18
2.8. IP FRR . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.8. IP FRR . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.9. Operational States . . . . . . . . . . . . . . . . . . . 18 2.9. Operational States . . . . . . . . . . . . . . . . . . . 19
3. RPC Operations . . . . . . . . . . . . . . . . . . . . . . . 19 3. RPC Operations . . . . . . . . . . . . . . . . . . . . . . . 19
4. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 19 4. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 20
5. Interaction with Other YANG Modules . . . . . . . . . . . . . 20 5. Interaction with Other YANG Modules . . . . . . . . . . . . . 21
6. IS-IS YANG Module . . . . . . . . . . . . . . . . . . . . . . 21 6. IS-IS YANG Module . . . . . . . . . . . . . . . . . . . . . . 22
7. Security Considerations . . . . . . . . . . . . . . . . . . . 100 7. Security Considerations . . . . . . . . . . . . . . . . . . . 101
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 101 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 102
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 101 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 102
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 101 10. Change log for ietf-isis YANG module . . . . . . . . . . . . 102
11. Change log for ietf-isis YANG module . . . . . . . . . . . . 101 10.1. From version -25 to version -26 . . . . . . . . . . . . 102
11.1. From version -24 to version -25 . . . . . . . . . . . . 101 10.2. From version -24 to version -25 . . . . . . . . . . . . 103
11.2. From version -22 to version -24 . . . . . . . . . . . . 102 10.3. From version -22 to version -24 . . . . . . . . . . . . 104
11.3. From version -21 to version -22 . . . . . . . . . . . . 102 10.4. From version -21 to version -22 . . . . . . . . . . . . 104
11.4. From version -20 to version -21 . . . . . . . . . . . . 103 10.5. From version -20 to version -21 . . . . . . . . . . . . 104
11.5. From version -19 to version -20 . . . . . . . . . . . . 103 10.6. From version -19 to version -20 . . . . . . . . . . . . 104
11.6. From version -18 to version -19 . . . . . . . . . . . . 103 10.7. From version -18 to version -19 . . . . . . . . . . . . 104
11.7. From version -17 to version -18 . . . . . . . . . . . . 103 10.8. From version -17 to version -18 . . . . . . . . . . . . 104
11.8. From version -16 to version -17 . . . . . . . . . . . . 103 10.9. From version -16 to version -17 . . . . . . . . . . . . 104
11.9. From version -15 to version -16 . . . . . . . . . . . . 103 10.10. From version -15 to version -16 . . . . . . . . . . . . 105
11.10. From version -14 to version -15 . . . . . . . . . . . . 104 10.11. From version -14 to version -15 . . . . . . . . . . . . 105
11.11. From version -13 to version -14 . . . . . . . . . . . . 104 10.12. From version -13 to version -14 . . . . . . . . . . . . 105
11.12. From version -12 to version -13 . . . . . . . . . . . . 104 10.13. From version -12 to version -13 . . . . . . . . . . . . 105
11.13. From version -09 to version -12 . . . . . . . . . . . . 104 10.14. From version -09 to version -12 . . . . . . . . . . . . 106
11.14. From version -08 to version -09 . . . . . . . . . . . . 105 10.15. From version -08 to version -09 . . . . . . . . . . . . 106
11.15. From version -07 to version -08 . . . . . . . . . . . . 105 10.16. From version -07 to version -08 . . . . . . . . . . . . 106
11.16. From version -05 to version -07 . . . . . . . . . . . . 105 10.17. From version -05 to version -07 . . . . . . . . . . . . 106
11.17. From version -03 to version -05 . . . . . . . . . . . . 105 10.18. From version -03 to version -05 . . . . . . . . . . . . 106
11.18. From version -02 to version -03 . . . . . . . . . . . . 106 10.19. From version -02 to version -03 . . . . . . . . . . . . 107
11.19. From version -01 to version -02 . . . . . . . . . . . . 106 10.20. From version -01 to version -02 . . . . . . . . . . . . 107
11.20. From version -00 to version -01 . . . . . . . . . . . . 106 10.21. From version -00 to version -01 . . . . . . . . . . . . 107
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 107 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 108
12.1. Normative References . . . . . . . . . . . . . . . . . . 107 11.1. Normative References . . . . . . . . . . . . . . . . . . 108
12.2. Informative References . . . . . . . . . . . . . . . . . 109 11.2. Informative References . . . . . . . . . . . . . . . . . 111
Appendix A. Example of IS-IS configuration in XML . . . . . . . 109 Appendix A. Example of IS-IS configuration in XML . . . . . . . 112
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 112 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 114
1. Introduction 1. Introduction
This document defines a YANG ([RFC7950]) data model for IS-IS routing This document defines a YANG ([RFC7950]) data model for IS-IS routing
protocol. protocol.
The data model covers configuration of an IS-IS routing protocol The data model covers configuration of an IS-IS routing protocol
instance as well as operational states. instance as well as operational states.
A simplified tree representation of the data model is presented in A simplified tree representation of the data model is presented in
skipping to change at page 13, line 49 skipping to change at page 13, line 49
| +--rw level-1 | +--rw level-1
| | +--rw candidate-enable? boolean | | +--rw candidate-enable? boolean
| | +--rw enable? boolean | | +--rw enable? boolean
| | +--rw remote-lfa {remote-lfa}? | | +--rw remote-lfa {remote-lfa}?
| | +--rw enable? boolean | | +--rw enable? boolean
| +--rw level-2 | +--rw level-2
| +--rw candidate-enable? boolean | +--rw candidate-enable? boolean
| +--rw enable? boolean | +--rw enable? boolean
| +--rw remote-lfa {remote-lfa}? | +--rw remote-lfa {remote-lfa}?
| +--rw enable? boolean | +--rw enable? boolean
+--ro adjacencies
| +--ro adjacency* []
| +--ro neighbor-sys-type? level
| +--ro neighbor-sysid? system-id
| +--ro neighbor-extended-circuit-id?
extended-circuit-id
| +--ro neighbor-snpa? snpa
| +--ro usage? level
| +--ro hold-timer?
rt-types:timer-value-seconds16
| +--ro neighbor-priority? uint8
| +--ro lastuptime? yang:timestamp
| +--ro state? adj-state-type
+--ro event-counters
| +--ro adjacency-changes? uint32
| +--ro adjacency-number? uint32
| +--ro init-fails? uint32
| +--ro adjacency-rejects? uint32
| +--ro id-len-mismatch? uint32
| +--ro max-area-addresses-mismatch? uint32
| +--ro authentication-type-fails? uint32
| +--ro authentication-fails? uint32
| +--ro lan-dis-changes? uint32
+--ro packet-counters
| +--ro level* [level]
| +--ro level level-number
| +--ro iih
| | +--ro in? uint32
| | +--ro out? uint32
| +--ro ish
| | +--ro in? uint32
| | +--ro out? uint32
| +--ro esh
| | +--ro in? uint32
| | +--ro out? uint32
| +--ro lsp
| | +--ro in? uint32
| | +--ro out? uint32
| +--ro psnp
| | +--ro in? uint32
| | +--ro out? uint32
| +--ro csnp
| | +--ro in? uint32
| | +--ro out? uint32
| +--ro unknown
| +--ro in? uint32
| +--ro out? uint32
+--rw topologies {multi-topology}? +--rw topologies {multi-topology}?
+--rw topology* [name] +--rw topology* [name]
+--rw name -> +--rw name ->
../../../../../../../../rt:ribs/rib/name ../../../../../../../../rt:ribs/rib/name
+--rw metric +--rw metric
+--rw value? wide-metric +--rw value? wide-metric
+--rw level-1 +--rw level-1
| +--rw value? wide-metric | +--rw value? wide-metric
+--rw level-2 +--rw level-2
+--rw value? wide-metric +--rw value? wide-metric
skipping to change at page 21, line 10 skipping to change at page 22, line 7
The modules defined in this document use some groupings from ietf- The modules defined in this document use some groupings from ietf-
keychain [RFC8177]. keychain [RFC8177].
The module reuses types from [RFC6991] and [RFC8294]. The module reuses types from [RFC6991] and [RFC8294].
To support BFD for fast detection, the module relies on To support BFD for fast detection, the module relies on
[I-D.ietf-bfd-yang]. [I-D.ietf-bfd-yang].
6. IS-IS YANG Module 6. IS-IS YANG Module
<CODE BEGINS> file "ietf-isis@2018-11-26.yang" <CODE BEGINS> file "ietf-isis@2018-12-04.yang"
module ietf-isis { module ietf-isis {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-isis"; namespace "urn:ietf:params:xml:ns:yang:ietf-isis";
prefix isis; prefix isis;
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference "RFC 8349 - A YANG Data Model for Routing reference "RFC 8349 - A YANG Data Model for Routing
skipping to change at page 22, line 7 skipping to change at page 23, line 4
prefix "rt-types"; prefix "rt-types";
reference "RFC 8294 - Common YANG Data Types for the reference "RFC 8294 - Common YANG Data Types for the
Routing Area"; Routing Area";
} }
import iana-routing-types { import iana-routing-types {
prefix "iana-rt-types"; prefix "iana-rt-types";
reference "RFC 8294 - Common YANG Data Types for the reference "RFC 8294 - Common YANG Data Types for the
Routing Area"; Routing Area";
} }
import ietf-bfd-types { import ietf-bfd-types {
prefix "bfd-types"; prefix "bfd-types";
reference "RFC XXXX - YANG Data Model for Bidirectional reference "RFC YYYY - YANG Data Model for Bidirectional
Forwarding Detection (BFD).Please replace YYYY with Forwarding Detection (BFD).
published RFC
number for draft-ietf-bfd-yang."; -- Note to RFC Editor Please replace YYYY with published RFC number for
draft-ietf-bfd-yang.";
} }
organization organization
"IETF LSR Working Group"; "IETF LSR Working Group";
contact contact
"WG List: &lt;mailto:lsr@ietf.org&gt; "WG List: &lt;mailto:lsr@ietf.org&gt;
Editor: Stephane Litkowski Editor: Stephane Litkowski
&lt;mailto:stephane.litkowski@orange.com&gt; &lt;mailto:stephane.litkowski@orange.com&gt;
skipping to change at page 22, line 49 skipping to change at page 23, line 47
Yingzhen Qu Yingzhen Qu
&lt;mailto:yiqu@cisco.com&gt; &lt;mailto:yiqu@cisco.com&gt;
Jeff Tantsura Jeff Tantsura
&lt;mailto:jefftant.ietf@gmail.com&gt; &lt;mailto:jefftant.ietf@gmail.com&gt;
"; ";
description description
"This YANG module defines the generic configuration and "This YANG module defines the generic configuration and
operational state for the IS-IS protocol. operational state for the IS-IS protocol.
It is intended that the module It is intended that the module
will be extended by vendors to define vendor-specific will be extended by vendors to define vendor-specific
IS-IS configuration parameters and policies, IS-IS configuration parameters and policies,
for example route maps or route policies. for example route maps or route policies.
This YANG model conforms to the Network Management This YANG model conforms to the Network Management
Datastore Architecture (NDMA) as described in RFC 8242. Datastore Architecture (NDMA) as described in RFC 8242.
Copyright (c) 2018 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; This version of this YANG module is part of RFC XXXX;
see the RFC itself for full legal notices."; see the RFC itself for full legal notices.";
revision 2018-11-26 { revision 2018-12-04 {
description description
"Initial revision."; "Initial revision.";
reference "RFC XXXX"; reference "RFC XXXX";
} }
/* Identities */ /* Identities */
identity isis { identity isis {
base rt:routing-protocol; base rt:routing-protocol;
description "Identity for the IS-IS routing protocol."; description "Identity for the IS-IS routing protocol.";
skipping to change at page 24, line 4 skipping to change at page 24, line 49
"Identity used when the LSP log reason is "Identity used when the LSP log reason is
a refresh LSP received."; a refresh LSP received.";
} }
identity content-change { identity content-change {
base lsp-log-reason; base lsp-log-reason;
description description
"Identity used when the LSP log reason is "Identity used when the LSP log reason is
a change in the content of the LSP."; a change in the content of the LSP.";
} }
/* Feature definitions */
/* Feature definitions */
feature poi-tlv { feature poi-tlv {
description "Support of Purge Originator Identification."; description "Support of Purge Originator Identification.";
reference "RFC 6232 - Purge Originator Identification TLV reference "RFC 6232 - Purge Originator Identification TLV
for IS-IS"; for IS-IS";
} }
feature ietf-spf-delay { feature ietf-spf-delay {
description description
"Support for IETF SPF delay algorithm."; "Support for IETF SPF delay algorithm.";
reference "RFC 8405 - SPF Back-off algorithm for link reference "RFC 8405 - SPF Back-off algorithm for link
state IGPs"; state IGPs";
skipping to change at page 29, line 28 skipping to change at page 30, line 26
typedef system-id { typedef system-id {
type string { type string {
pattern pattern
'[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}'; '[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}';
} }
description description
"This type defines IS-IS system-id using pattern, "This type defines IS-IS system-id using pattern,
An example system-id is 0143.0438.AEF0"; An example system-id is 0143.0438.AEF0";
} }
typedef extended-system-id { typedef extended-system-id {
type string { type string {
pattern pattern
'[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}\.[0-9][0-9]'; '[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}\.[0-9][0-9]';
} }
description description
"This type defines IS-IS system-id using pattern. The extended "This type defines IS-IS system-id using pattern. The extended
system id contains the pseudonode number in system id contains the pseudonode number in addition to the
addition to the system id.
system id.
An example system-id is 0143.0438.AEF0.00"; An example system-id is 0143.0438.AEF0.00";
} }
typedef wide-metric { typedef wide-metric {
type uint32 { type uint32 {
range "0 .. 16777215"; range "0 .. 16777215";
} }
description description
"This type defines wide style format of IS-IS metric."; "This type defines wide style format of IS-IS metric.";
} }
skipping to change at page 56, line 32 skipping to change at page 57, line 29
uses metric-cfg; uses metric-cfg;
description "level-2 specific configuration"; description "level-2 specific configuration";
} }
description "Metric configuration."; description "Metric configuration.";
} }
container bfd { container bfd {
if-feature bfd; if-feature bfd;
description "BFD Client Configuration."; description "BFD Client Configuration.";
uses bfd-types:client-cfg-parms; uses bfd-types:client-cfg-parms;
reference "draft-ietf-bfd-yang-xx.txt: reference "RFC YYYY - YANG Data Model for Bidirectional
YANG Data Model for Bidirectional Forwarding Forwarding Detection (BFD).
Detection (BFD)";
-- Note to RFC Editor Please replace YYYY with published RFC number for
draft-ietf-bfd-yang.";
} }
container address-families { container address-families {
if-feature nlpid-control; if-feature nlpid-control;
list address-family-list { list address-family-list {
key address-family; key address-family;
leaf address-family { leaf address-family {
type iana-rt-types:address-family; type iana-rt-types:address-family;
description "Address-family"; description "Address-family";
} }
description "List of AFs."; description "List of AFs.";
skipping to change at page 70, line 43 skipping to change at page 71, line 41
"List of 32-bit tags associated with the IPv4 prefix."; "List of 32-bit tags associated with the IPv4 prefix.";
} }
leaf-list tag64 { leaf-list tag64 {
type uint64; type uint64;
description description
"List of 32-bit tags associated with the IPv4 prefix."; "List of 32-bit tags associated with the IPv4 prefix.";
} }
uses prefix-attributes-extension; uses prefix-attributes-extension;
} }
/* TLVs and subTLVs for neighbors */ /* TLVs and subTLVs for neighbors */
grouping neighbor-link-attributes { grouping neighbor-link-attributes {
description description
"Grouping for link attributes as defined "Grouping for link attributes as defined
in RFC5029"; in RFC5029";
leaf link-attributes-flags { leaf link-attributes-flags {
type uint16; type uint16;
description description
"Flags for the link attributes"; "Flags for the link attributes";
} }
}
grouping neighbor-gmpls-extensions {
description
"Grouping for GMPLS attributes of a neighbor as
defined
in RFC5307";
leaf link-local-id {
type uint32;
description
"Local identifier of the link.";
}
leaf remote-local-id {
type uint32;
description
"Remote identifier of the link.";
}
leaf protection-capability {
type uint8;
description
"Describes the protection capabilities
of the link. This is the value of the
first octet of the sub-TLV type 20
value.";
}
container interface-switching-capability {
description
"Interface switching capabilities of
the link.";
leaf switching-capability {
type uint8;
description
"Switching capability of the
link.";
}
leaf encoding {
type uint8;
description
"Type of encoding of the LSP
being used.";
}
container max-lsp-bandwidths {
description "Per priority max LSP
bandwidths.";
list max-lsp-bandwidth {
leaf priority {
type uint8 {
range "0 .. 7";
}
description "Priority
from 0 to 7.";
}
leaf bandwidth {
type
rt-types:bandwidth-ieee-float32;
description "max LSP
bandwidth.";
}
description
"List of max LSP
bandwidths for different
priorities.";
}
}
container tdm-specific {
when "switching-capability = 100";
description
"Switching Capability-specific
information applicable
when switching type is TDM.";
leaf minimum-lsp-bandwidth { }
type grouping neighbor-gmpls-extensions {
rt-types:bandwidth-ieee-float32; description
description "minimum LSP "Grouping for GMPLS attributes of a neighbor as defined
bandwidth."; in RFC5307";
} leaf link-local-id {
leaf indication { type uint32;
type uint8; description
description "Local identifier of the link.";
"The indication whether }
the interface supports Standard or Arbitrary leaf remote-local-id {
SONET/SDH."; type uint32;
} description
} "Remote identifier of the link.";
container psc-specific { }
when "switching-capability >= 1 and leaf protection-capability {
switching-capability <= 4"; type uint8;
description description
"Switching Capability-specific "Describes the protection capabilities
information applicable of the link. This is the value of the
when switching type is first octet of the sub-TLV type 20 value.";
PSC1,PSC2,PSC3 or PSC4."; }
container interface-switching-capability {
description
"Interface switching capabilities of the link.";
leaf switching-capability {
type uint8;
description
"Switching capability of the link.";
}
leaf encoding {
type uint8;
description
"Type of encoding of the LSP being used.";
}
container max-lsp-bandwidths {
description "Per priority max LSP bandwidths.";
list max-lsp-bandwidth {
leaf priority {
type uint8 {
range "0 .. 7";
}
description "Priority from 0 to 7.";
}
leaf bandwidth {
type rt-types:bandwidth-ieee-float32;
description "max LSP bandwidth.";
}
description
"List of max LSP bandwidths for different
priorities.";
}
}
container tdm-specific {
when "switching-capability = 100";
description
"Switching Capability-specific information applicable
when switching type is TDM.";
leaf minimum-lsp-bandwidth { leaf minimum-lsp-bandwidth {
type type rt-types:bandwidth-ieee-float32;
rt-types:bandwidth-ieee-float32; description "minimum LSP bandwidth.";
description "minimum LSP }
bandwidth."; leaf indication {
} type uint8;
leaf mtu { description
type uint16; "The indication whether the interface supports Standard
units bytes; or Arbitrary SONET/SDH.";
description
"Interface MTU";
}
}
}
} }
}
container psc-specific {
when "switching-capability >= 1 and switching-capability <= 4";
description
"Switching Capability-specific information applicable
when switching type is PSC1,PSC2,PSC3 or PSC4.";
grouping neighbor-extended-te-extensions { leaf minimum-lsp-bandwidth {
description type rt-types:bandwidth-ieee-float32;
"Grouping for TE attributes of a neighbor as description "minimum LSP bandwidth.";
defined }
in RFC7810"; leaf mtu {
type uint16;
units bytes;
description
"Interface MTU";
}
}
}
}
container unidirectional-link-delay { grouping neighbor-extended-te-extensions {
description description
"Container for the average delay "Grouping for TE attributes of a neighbor as defined
from the local neighbor to the remote in RFC7810";
one.";
leaf flags {
type bits {
bit A {
position 7;
description
"The A bit
represents the Anomalous (A) bit.
The A bit is
set when the measured value of
this parameter
exceeds its configured
maximum
threshold.
The A bit is
cleared when the measured value
falls below its
configured reuse threshold.
If the A bit is
clear,
the value
represents steady-state link performance.";
}
}
description
"Flags.";
}
leaf value {
type uint32;
units usec;
description
"Delay value expressed in
microseconds.";
}
}
container min-max-unidirectional-link-delay {
description
"Container for the min and max delay
from the local neighbor to the remote
one.";
leaf flags {
type bits {
bit A {
position 7;
description
"The A bit
represents the Anomalous (A) bit.
The A bit is
set when the measured value of
this parameter
exceeds its configured
maximum
threshold.
The A bit is
cleared when the measured value
falls below its
configured reuse threshold.
If the A bit is
clear,
the value
represents steady-state link performance.";
}
}
description
"Flags.";
}
leaf min-value {
type uint32;
units usec;
description
"Minimum delay value expressed
in microseconds.";
}
leaf max-value {
type uint32;
units usec;
description
"Maximum delay value expressed
in microseconds.";
}
}
container unidirectional-link-delay-variation {
description
"Container for the average delay
variation
from the local neighbor to the remote
one.";
leaf value {
type uint32;
units usec;
description
"Delay variation value
expressed in microseconds.";
}
}
container unidirectional-link-loss{
description
"Container for the packet loss
from the local neighbor to the remote
one.";
leaf flags {
type bits {
bit A {
position 7;
description
"The A bit
represents the Anomalous (A) bit.
The A bit is
set when the measured value of
this parameter
exceeds its configured
maximum
threshold.
The A bit is
cleared when the measured value
falls below its
configured reuse threshold.
If the A bit is
clear,
the value
represents steady-state link performance.";
}
}
description
"Flags.";
} container unidirectional-link-delay {
leaf value { description
type uint32; "Container for the average delay
units percent; from the local neighbor to the remote one.";
description leaf flags {
"Link packet loss expressed as type bits {
a percentage bit A {
of the total traffic sent over position 7;
a configurable interval."; description
} "The A bit represents the Anomalous (A) bit.
} The A bit is set when the measured value of
container unidirectional-link-residual-bandwidth { this parameter exceeds its configured
description maximum threshold.
"Container for the residual bandwidth The A bit is cleared when the measured value
from the local neighbor to the remote falls below its configured reuse threshold.
one."; If the A bit is clear,
leaf value { the value represents steady-state link performance.";
type rt-types:bandwidth-ieee-float32; }
units Bps;
description
"Residual bandwidth.";
}
}
container unidirectional-link-available-bandwidth {
description
"Container for the available bandwidth
from the local neighbor to the remote
one.";
leaf value {
type rt-types:bandwidth-ieee-float32;
units Bps;
description
"Available bandwidth.";
}
}
container unidirectional-link-utilized-bandwidth {
description
"Container for the utilized bandwidth
from the local neighbor to the remote
one.";
leaf value {
type rt-types:bandwidth-ieee-float32;
units Bps;
description
"Utilized bandwidth.";
}
}
} }
description
"Flags.";
}
leaf value {
type uint32;
units usec;
description
"Delay value expressed in microseconds.";
}
}
container min-max-unidirectional-link-delay {
description
"Container for the min and max delay
from the local neighbor to the remote one.";
leaf flags {
type bits {
bit A {
position 7;
description
"The A bit represents the Anomalous (A) bit.
The A bit is set when the measured value of
this parameter exceeds its configured
maximum threshold.
The A bit is cleared when the measured value
falls below its configured reuse threshold.
If the A bit is clear,
the value represents steady-state link performance.";
}
}
description
"Flags.";
}
leaf min-value {
type uint32;
units usec;
description
"Minimum delay value expressed in microseconds.";
}
leaf max-value {
type uint32;
units usec;
description
"Maximum delay value expressed in microseconds.";
}
}
container unidirectional-link-delay-variation {
description
"Container for the average delay variation
from the local neighbor to the remote one.";
leaf value {
type uint32;
units usec;
description
"Delay variation value expressed in microseconds.";
}
}
container unidirectional-link-loss{
description
"Container for the packet loss
from the local neighbor to the remote one.";
leaf flags {
type bits {
bit A {
position 7;
description
"The A bit represents the Anomalous (A) bit.
The A bit is set when the measured value of
this parameter exceeds its configured
maximum threshold.
The A bit is cleared when the measured value
falls below its configured reuse threshold.
If the A bit is clear,
the value represents steady-state link performance.";
}
}
description
"Flags.";
}
leaf value {
type uint32;
units percent;
description
"Link packet loss expressed as a percentage
of the total traffic sent over a configurable interval.";
}
}
container unidirectional-link-residual-bandwidth {
description
"Container for the residual bandwidth
from the local neighbor to the remote one.";
leaf value {
type rt-types:bandwidth-ieee-float32;
units Bps;
description
"Residual bandwidth.";
}
}
container unidirectional-link-available-bandwidth {
description
"Container for the available bandwidth
from the local neighbor to the remote one.";
leaf value {
type rt-types:bandwidth-ieee-float32;
units Bps;
description
"Available bandwidth.";
}
}
container unidirectional-link-utilized-bandwidth {
description
"Container for the utilized bandwidth
from the local neighbor to the remote one.";
leaf value {
type rt-types:bandwidth-ieee-float32;
units Bps;
description
"Utilized bandwidth.";
}
}
}
grouping neighbor-te-extensions { grouping neighbor-te-extensions {
description description
"Grouping for TE attributes of a neighbor as "Grouping for TE attributes of a neighbor as defined
defined in RFC5305";
in RFC5305"; leaf admin-group {
type uint32;
leaf admin-group { description
type uint32; "Administrative group/Resource Class/Color.";
description }
"Administrative group/Resource container local-if-ipv4-addrs {
Class/Color."; description "All local interface IPv4 addresses.";
} leaf-list local-if-ipv4-addr {
container local-if-ipv4-addrs { type inet:ipv4-address;
description "All local interface IPv4 description
addresses."; "List of local interface IPv4 addresses.";
leaf-list local-if-ipv4-addr { }
type inet:ipv4-address; }
description container remote-if-ipv4-addrs {
"List of local interface IPv4 description "All remote interface IPv4 addresses.";
addresses."; leaf-list remote-if-ipv4-addr {
} type inet:ipv4-address;
} description
container remote-if-ipv4-addrs { "List of remote interface IPv4 addresses.";
description "All remote interface IPv4 }
addresses."; }
leaf-list remote-if-ipv4-addr { leaf te-metric {
type inet:ipv4-address; type uint32;
description description "TE metric.";
"List of remote interface IPv4 }
addresses."; leaf max-bandwidth {
} type rt-types:bandwidth-ieee-float32;
} description "Maximum bandwidth.";
leaf te-metric { }
type uint32; leaf max-reservable-bandwidth {
description "TE metric."; type rt-types:bandwidth-ieee-float32;
} description "Maximum reservable bandwidth.";
leaf max-bandwidth { }
type rt-types:bandwidth-ieee-float32; container unreserved-bandwidths {
description "Maximum bandwidth."; description "All unreserved bandwidths.";
} list unreserved-bandwidth {
leaf max-reservable-bandwidth { leaf priority {
type rt-types:bandwidth-ieee-float32; type uint8 {
description "Maximum reservable bandwidth."; range "0 .. 7";
} }
container unreserved-bandwidths { description "Priority from 0 to 7.";
description "All unreserved bandwidths."; }
list unreserved-bandwidth { leaf unreserved-bandwidth {
leaf priority { type rt-types:bandwidth-ieee-float32;
type uint8 { description "Unreserved bandwidth.";
range "0 .. 7";
}
description "Priority from 0 to
7.";
}
leaf unreserved-bandwidth {
type
rt-types:bandwidth-ieee-float32;
description "Unreserved
bandwidth.";
}
description
"List of unreserved bandwidths
for different
priorities.";
}
}
} }
description
"List of unreserved bandwidths for different
priorities.";
}
}
}
grouping neighbor-extended { grouping neighbor-extended {
description description
"Grouping for attributes of an IS-IS extended neighbor."; "Grouping for attributes of an IS-IS extended neighbor.";
leaf neighbor-id { leaf neighbor-id {
type extended-system-id; type extended-system-id;
description "System-id of the extended neighbor."; description "System-id of the extended neighbor.";
} }
container instances { container instances {
description "List of all adjacencies between the local description "List of all adjacencies between the local
skipping to change at page 89, line 51 skipping to change at page 90, line 51
list interface { list interface {
key "name"; key "name";
leaf name { leaf name {
type if:interface-ref; type if:interface-ref;
description description
"Reference to the interface within "Reference to the interface within
the routing-instance."; the routing-instance.";
} }
uses interface-config; uses interface-config;
uses interface-state;
container topologies { container topologies {
if-feature multi-topology; if-feature multi-topology;
list topology { list topology {
key name; key name;
leaf name { leaf name {
type leafref { type leafref {
path "../../../../../../../../"+ path "../../../../../../../../"+
"rt:ribs/rt:rib/rt:name"; "rt:ribs/rt:rib/rt:name";
} }
skipping to change at page 101, line 19 skipping to change at page 102, line 20
Some of the RPC operations in this YANG module may be considered Some of the RPC operations in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control access to these operations. The OSPF YANG important to control access to these operations. The OSPF YANG
module support the "clear-adjacency" and "clear-database" RPCs. If module support the "clear-adjacency" and "clear-database" RPCs. If
access too either of these is compromised, they can result in access too either of these is compromised, they can result in
temporary network outages be employed to mount DoS attacks. temporary network outages be employed to mount DoS attacks.
8. Contributors 8. Contributors
Authors would like to thank Kiran Agrahara Sreenivasa, Dean Authors would like to thank Kiran Agrahara Sreenivasa, Dean
Bogdanovic, Yingzhen Qu, Yi Yang for their major contributions to the Bogdanovic, Yingzhen Qu, Yi Yang, Jeff Tanstura for their major
draft. contributions to the draft.
9. Acknowledgements
TBD.
10. IANA Considerations 9. IANA Considerations
The IANA is requested to assign two new URIs from the IETF XML The IANA is requested to assign two new URIs from the IETF XML
registry ([RFC3688]). Authors are suggesting the following URI: registry ([RFC3688]). Authors are suggesting the following URI:
URI: urn:ietf:params:xml:ns:yang:ietf-isis URI: urn:ietf:params:xml:ns:yang:ietf-isis
Registrant Contact: IS-IS WG Registrant Contact: IS-IS WG
XML: N/A, the requested URI is an XML namespace XML: N/A, the requested URI is an XML namespace
This document also requests one new YANG module name in the YANG This document also requests one new YANG module name in the YANG
Module Names registry ([RFC6020]) with the following suggestion: Module Names registry ([RFC6020]) with the following suggestion:
name: ietf-isis name: ietf-isis
namespace: urn:ietf:params:xml:ns:yang:ietf-isis namespace: urn:ietf:params:xml:ns:yang:ietf-isis
prefix: isis prefix: isis
reference: RFC XXXX reference: RFC XXXX
11. Change log for ietf-isis YANG module 10. Change log for ietf-isis YANG module
11.1. From version -24 to version -25 10.1. From version -25 to version -26
o Modify BFD reference descriptions.
o Fix indentation.
o "uses interface-state" was missing.
10.2. From version -24 to version -25
o RPC clear-adjacency uses now an interface reference instead of a o RPC clear-adjacency uses now an interface reference instead of a
string. string.
o Use expanded "address-family" rather than "af" in the model. o Use expanded "address-family" rather than "af" in the model.
o Fix pattern for area-address. o Fix pattern for area-address.
o Removed unnecessary identities. o Removed unnecessary identities.
skipping to change at page 102, line 43 skipping to change at page 104, line 5
OSPF. OSPF.
o Added some link attributes (GMPLS, TE, extended TE, SRLGs) in the o Added some link attributes (GMPLS, TE, extended TE, SRLGs) in the
LSDB. LSDB.
o Added extended-system-id typedef which contains the systemid plus o Added extended-system-id typedef which contains the systemid plus
the pseudonode number. the pseudonode number.
o Add support of POI Purge Originator Identification. o Add support of POI Purge Originator Identification.
11.2. From version -22 to version -24 10.3. From version -22 to version -24
o Fix revision date of the module. o Fix revision date of the module.
11.3. From version -21 to version -22 10.4. From version -21 to version -22
o TE router-id modeling alignment with OSPF. o TE router-id modeling alignment with OSPF.
o Add max-ecmp + feature in spf-control container (alignment with o Add max-ecmp + feature in spf-control container (alignment with
OSPF). OSPF).
11.4. From version -20 to version -21 10.5. From version -20 to version -21
o Model revision date fix o Model revision date fix
11.5. From version -19 to version -20 10.6. From version -19 to version -20
o Moved to Yang 1.1 o Moved to Yang 1.1
o Lower case enumerations o Lower case enumerations
o Add RFC references to features o Add RFC references to features
o Remove segment-routing feature o Remove segment-routing feature
o Modified BFD activation modeling o Modified BFD activation modeling
11.6. From version -18 to version -19 10.7. From version -18 to version -19
o Align with draft-ietf-netmod-rfc8022bis. o Align with draft-ietf-netmod-rfc8022bis.
o Modify address family types as per draft-ietf-rtgwg-routing-types- o Modify address family types as per draft-ietf-rtgwg-routing-types-
17. 17.
11.7. From version -17 to version -18 10.8. From version -17 to version -18
o NMDA compliancy. o NMDA compliancy.
o Set some default values. o Set some default values.
o Align with iana-rt-types module. o Align with iana-rt-types module.
11.8. From version -16 to version -17 10.9. From version -16 to version -17
o Cosmetic fixes. o Cosmetic fixes.
o Use of rt-types model. o Use of rt-types model.
11.9. From version -15 to version -16 10.10. From version -15 to version -16
o Alignment with last IETF key chain model. o Alignment with last IETF key chain model.
o lsp-log "change" leaf moved as an identity. o lsp-log "change" leaf moved as an identity.
o Incremental SPF removed from spf-log types. o Incremental SPF removed from spf-log types.
11.10. From version -14 to version -15 10.11. From version -14 to version -15
o Alignment with OSPF model done: o Alignment with OSPF model done:
* Added spf-control container with IETF SPF delay algorithm as a * Added spf-control container with IETF SPF delay algorithm as a
feature. feature.
* Added graceful-restart options. * Added graceful-restart options.
* Added nsr as a feature. * Added nsr as a feature.
skipping to change at page 104, line 32 skipping to change at page 105, line 40
* Added auto-cost container. * Added auto-cost container.
* Moved reference-bandwidth under auto-cost container. * Moved reference-bandwidth under auto-cost container.
* Added IS-IS local RIB as operational state. * Added IS-IS local RIB as operational state.
* Added decode-completed and raw-data leaves in the LSDB model. * Added decode-completed and raw-data leaves in the LSDB model.
* Modified the notification header. * Modified the notification header.
11.11. From version -13 to version -14 10.12. From version -13 to version -14
o Segment Routing extensions are now in a separate document. o Segment Routing extensions are now in a separate document.
11.12. From version -12 to version -13 10.13. From version -12 to version -13
o Move feature nlpid-control to container rather than list. o Move feature nlpid-control to container rather than list.
o Rename multi-topology to topologies to align with OSPF. o Rename multi-topology to topologies to align with OSPF.
o Rename bfd/enabled to bfd/enable for consistency reason. o Rename bfd/enabled to bfd/enable for consistency reason.
o Add support for NSR with a feature. o Add support for NSR with a feature.
11.13. From version -09 to version -12 10.14. From version -09 to version -12
o Rename node-tag container to node-tags. o Rename node-tag container to node-tags.
11.14. From version -08 to version -09 10.15. From version -08 to version -09
o Added container before af list. o Added container before af list.
o Added container before topology list. o Added container before topology list.
o Aligned LFA if per level cfg. o Aligned LFA if per level cfg.
o Align to draft-ietf-netmod-routing-cfg-23. o Align to draft-ietf-netmod-routing-cfg-23.
11.15. From version -07 to version -08 10.16. From version -07 to version -08
o Remove selector from system-id type. o Remove selector from system-id type.
o Add some default values. o Add some default values.
o Moved lists to containers+groupings for per level configuration. o Moved lists to containers+groupings for per level configuration.
o remove routing-instance as per core routing model v21. o remove routing-instance as per core routing model v21.
o added BFD leaf (no more BFD protocol model). o added BFD leaf (no more BFD protocol model).
o changed keychain module reference. o changed keychain module reference.
11.16. From version -05 to version -07 10.17. From version -05 to version -07
o Move Overload config from list to container. o Move Overload config from list to container.
o Move Overload-max-metric config from list to container. o Move Overload-max-metric config from list to container.
o Move preference config from list to container. o Move preference config from list to container.
o Add Node flag in config. o Add Node flag in config.
o Removed BFD config => moved to isis-bfd module. o Removed BFD config => moved to isis-bfd module.
o Remove call to routing policy model. o Remove call to routing policy model.
11.17. From version -03 to version -05 10.18. From version -03 to version -05
o Correct invalid references to previous versions of core routing o Correct invalid references to previous versions of core routing
model. model.
o Remove BFD config and replace by groupings from ietf-bfd. o Remove BFD config and replace by groupings from ietf-bfd.
o Adding routing-policy support through routing-policy model. o Adding routing-policy support through routing-policy model.
11.18. From version -02 to version -03 10.19. From version -02 to version -03
o Reviewed config and op state groupings. o Reviewed config and op state groupings.
o Add default value to lfa candidate-disabled. o Add default value to lfa candidate-disabled.
o Add enable leaf to isis container to reflect admin state. o Add enable leaf to isis container to reflect admin state.
o Move to VRF centric only. o Move to VRF centric only.
o Segment routing is part os a separate module. o Segment routing is part os a separate module.
11.19. From version -01 to version -02 10.20. From version -01 to version -02
o Adding IPFRR. o Adding IPFRR.
o Adding igp-ldp-sync. o Adding igp-ldp-sync.
o Adding segment-routing. o Adding segment-routing.
o Adding instance reference to operational states. o Adding instance reference to operational states.
o Move AF type from string to identity. o Move AF type from string to identity.
skipping to change at page 106, line 43 skipping to change at page 107, line 45
o Added modification information in lsp-log. o Added modification information in lsp-log.
o Removing igp-ldp-sync timer in IS-IS. o Removing igp-ldp-sync timer in IS-IS.
o Defining hierarchy for operational states. o Defining hierarchy for operational states.
o Adding clns-mtu. o Adding clns-mtu.
o Adding key-chain. o Adding key-chain.
11.20. From version -00 to version -01 10.21. From version -00 to version -01
o Interface metric move from af container to interface container. o Interface metric move from af container to interface container.
o Hello-padding on interface moved to hello-padding-disable with o Hello-padding on interface moved to hello-padding-disable with
empty type. empty type.
o three-way-handshake removed. o three-way-handshake removed.
o route preference changed to a choice. o route preference changed to a choice.
skipping to change at page 107, line 24 skipping to change at page 108, line 26
o Change hello-padding to container. o Change hello-padding to container.
o Change bfd to container. o Change bfd to container.
o Make BFD a feature. o Make BFD a feature.
o Create mpls-te container and put router-id inside. o Create mpls-te container and put router-id inside.
o Remove GR helper disable and timers. o Remove GR helper disable and timers.
12. References 11. References
12.1. Normative References 11.1. Normative References
[I-D.ietf-bfd-yang] [I-D.ietf-bfd-yang]
Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and
G. Mirsky, "YANG Data Model for Bidirectional Forwarding G. Mirsky, "YANG Data Model for Bidirectional Forwarding
Detection (BFD)", draft-ietf-bfd-yang-17 (work in Detection (BFD)", draft-ietf-bfd-yang-17 (work in
progress), August 2018. progress), August 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
skipping to change at page 107, line 49 skipping to change at page 109, line 5
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi [RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi
Topology (MT) Routing in Intermediate System to Topology (MT) Routing in Intermediate System to
Intermediate Systems (IS-ISs)", RFC 5120, Intermediate Systems (IS-ISs)", RFC 5120,
DOI 10.17487/RFC5120, February 2008, DOI 10.17487/RFC5120, February 2008,
<https://www.rfc-editor.org/info/rfc5120>. <https://www.rfc-editor.org/info/rfc5120>.
[RFC5130] Previdi, S., Shand, M., Ed., and C. Martin, "A Policy
Control Mechanism in IS-IS Using Administrative Tags",
RFC 5130, DOI 10.17487/RFC5130, February 2008,
<https://www.rfc-editor.org/info/rfc5130>.
[RFC5286] Atlas, A., Ed. and A. Zinin, Ed., "Basic Specification for [RFC5286] Atlas, A., Ed. and A. Zinin, Ed., "Basic Specification for
IP Fast Reroute: Loop-Free Alternates", RFC 5286, IP Fast Reroute: Loop-Free Alternates", RFC 5286,
DOI 10.17487/RFC5286, September 2008, DOI 10.17487/RFC5286, September 2008,
<https://www.rfc-editor.org/info/rfc5286>. <https://www.rfc-editor.org/info/rfc5286>.
[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic
Engineering", RFC 5305, DOI 10.17487/RFC5305, October
2008, <https://www.rfc-editor.org/info/rfc5305>.
[RFC5306] Shand, M. and L. Ginsberg, "Restart Signaling for IS-IS",
RFC 5306, DOI 10.17487/RFC5306, October 2008,
<https://www.rfc-editor.org/info/rfc5306>.
[RFC5443] Jork, M., Atlas, A., and L. Fang, "LDP IGP [RFC5443] Jork, M., Atlas, A., and L. Fang, "LDP IGP
Synchronization", RFC 5443, DOI 10.17487/RFC5443, March Synchronization", RFC 5443, DOI 10.17487/RFC5443, March
2009, <https://www.rfc-editor.org/info/rfc5443>. 2009, <https://www.rfc-editor.org/info/rfc5443>.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<https://www.rfc-editor.org/info/rfc5880>.
[RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881,
DOI 10.17487/RFC5881, June 2010,
<https://www.rfc-editor.org/info/rfc5881>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>. <https://www.rfc-editor.org/info/rfc6020>.
[RFC6119] Harrison, J., Berger, J., and M. Bartlett, "IPv6 Traffic
Engineering in IS-IS", RFC 6119, DOI 10.17487/RFC6119,
February 2011, <https://www.rfc-editor.org/info/rfc6119>.
[RFC6232] Wei, F., Qin, Y., Li, Z., Li, T., and J. Dong, "Purge
Originator Identification TLV for IS-IS", RFC 6232,
DOI 10.17487/RFC6232, May 2011,
<https://www.rfc-editor.org/info/rfc6232>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<https://www.rfc-editor.org/info/rfc6991>. <https://www.rfc-editor.org/info/rfc6991>.
[RFC7490] Bryant, S., Filsfils, C., Previdi, S., Shand, M., and N. [RFC7490] Bryant, S., Filsfils, C., Previdi, S., Shand, M., and N.
So, "Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)", So, "Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)",
RFC 7490, DOI 10.17487/RFC7490, April 2015, RFC 7490, DOI 10.17487/RFC7490, April 2015,
<https://www.rfc-editor.org/info/rfc7490>. <https://www.rfc-editor.org/info/rfc7490>.
[RFC7794] Ginsberg, L., Ed., Decraene, B., Previdi, S., Xu, X., and
U. Chunduri, "IS-IS Prefix Attributes for Extended IPv4
and IPv6 Reachability", RFC 7794, DOI 10.17487/RFC7794,
March 2016, <https://www.rfc-editor.org/info/rfc7794>.
[RFC7810] Previdi, S., Ed., Giacalone, S., Ward, D., Drake, J., and
Q. Wu, "IS-IS Traffic Engineering (TE) Metric Extensions",
RFC 7810, DOI 10.17487/RFC7810, May 2016,
<https://www.rfc-editor.org/info/rfc7810>.
[RFC7917] Sarkar, P., Ed., Gredler, H., Hegde, S., Litkowski, S.,
and B. Decraene, "Advertising Node Administrative Tags in
IS-IS", RFC 7917, DOI 10.17487/RFC7917, July 2016,
<https://www.rfc-editor.org/info/rfc7917>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
skipping to change at page 109, line 24 skipping to change at page 111, line 34
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface [RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>. <https://www.rfc-editor.org/info/rfc8343>.
[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", RFC 8349, Routing Management (NMDA Version)", RFC 8349,
DOI 10.17487/RFC8349, March 2018, DOI 10.17487/RFC8349, March 2018,
<https://www.rfc-editor.org/info/rfc8349>. <https://www.rfc-editor.org/info/rfc8349>.
[RFC8405] Decraene, B., Litkowski, S., Gredler, H., Lindem, A.,
Francois, P., and C. Bowers, "Shortest Path First (SPF)
Back-Off Delay Algorithm for Link-State IGPs", RFC 8405,
DOI 10.17487/RFC8405, June 2018,
<https://www.rfc-editor.org/info/rfc8405>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
12.2. Informative References 11.2. Informative References
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
Appendix A. Example of IS-IS configuration in XML Appendix A. Example of IS-IS configuration in XML
This section gives an example of configuration of an IS-IS instance This section gives an example of configuration of an IS-IS instance
on a device. The example is written in XML. on a device. The example is written in XML.
 End of changes. 62 change blocks. 
450 lines changed or deleted 489 lines changed or added

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