< draft-ietf-isis-yang-isis-cfg-05.txt   draft-ietf-isis-yang-isis-cfg-06.txt >
ISIS Working Group S. Litkowski ISIS Working Group S. Litkowski
Internet-Draft Orange Internet-Draft Orange
Intended status: Standards Track D. Yeung Intended status: Standards Track D. Yeung
Expires: March 13, 2016 A. Lindem Expires: March 21, 2016 A. Lindem
Cisco Systems Cisco Systems
J. Zhang J. Zhang
Juniper Networks Juniper Networks
L. Lhotka L. Lhotka
September 10, 2015 CZ.NIC
September 18, 2015
YANG Data Model for ISIS protocol YANG Data Model for ISIS protocol
draft-ietf-isis-yang-isis-cfg-05 draft-ietf-isis-yang-isis-cfg-06
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 ISIS protocol on network elements. It also defined an and manage ISIS protocol on network elements. It also defined an
extension module for segment routing configuration and operation. extension module for segment routing configuration and operation.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 1, line 43 skipping to change at page 1, line 44
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 March 13, 2016. This Internet-Draft will expire on March 21, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 3
2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3 2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3
2.1. ISIS Configuration . . . . . . . . . . . . . . . . . . . 10 2.1. ISIS Configuration . . . . . . . . . . . . . . . . . . . 10
2.2. Multitopology Parameters . . . . . . . . . . . . . . . . 10 2.2. Multitopology Parameters . . . . . . . . . . . . . . . . 10
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. ISO parameters . . . . . . . . . . . . . . . . . . . . . 13 2.5. ISO parameters . . . . . . . . . . . . . . . . . . . . . 13
2.6. IP FRR . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.6. IP FRR . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.7. Operational State . . . . . . . . . . . . . . . . . . . . 13 2.7. Operational State . . . . . . . . . . . . . . . . . . . . 14
3. RPC Operations . . . . . . . . . . . . . . . . . . . . . . . 14 3. RPC Operations . . . . . . . . . . . . . . . . . . . . . . . 14
4. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 14 4. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 15
5. Segment Routing . . . . . . . . . . . . . . . . . . . . . . . 18 5. Segment Routing . . . . . . . . . . . . . . . . . . . . . . . 19
5.1. Segment Routing activation . . . . . . . . . . . . . . . 21 5.1. Segment Routing activation . . . . . . . . . . . . . . . 22
5.2. Advertising mapping server policy . . . . . . . . . . . . 21 5.2. Advertising mapping server policy . . . . . . . . . . . . 22
5.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 22 5.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 22
6. Interaction with Other YANG Modules . . . . . . . . . . . . . 22 6. Interaction with Other YANG Modules . . . . . . . . . . . . . 22
7. ISIS YANG Module . . . . . . . . . . . . . . . . . . . . . . 22 7. ISIS YANG Module . . . . . . . . . . . . . . . . . . . . . . 23
8. ISIS Segment Routing YANG Module . . . . . . . . . . . . . . 97 8. ISIS Segment Routing YANG Module . . . . . . . . . . . . . . 98
9. Security Considerations . . . . . . . . . . . . . . . . . . . 110 9. Security Considerations . . . . . . . . . . . . . . . . . . . 111
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 111 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 112
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 112 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 112
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 112 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 112
13. Normative References . . . . . . . . . . . . . . . . . . . . 112 13. Normative References . . . . . . . . . . . . . . . . . . . . 112
Appendix A. Example: NETCONF <get> Reply . . . . . . . . . . . . 112 Appendix A. Example: NETCONF <get> Reply . . . . . . . . . . . . 113
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 115 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 116
1. Introduction 1. Introduction
This document defines a YANG data model for ISIS routing protocol. This document defines a YANG data model for ISIS routing protocol.
The data model covers configuration of an ISIS routing protocol The data model covers configuration of an ISIS routing protocol
instance as well as operational states. instance as well as operational states.
1.1. Tree diagram 1.1. Tree diagram
skipping to change at page 3, line 42 skipping to change at page 3, line 49
are augmenting the "routing-protocol" lists in ietf-routing module are augmenting the "routing-protocol" lists in ietf-routing module
with specific ISIS parameters. with specific ISIS parameters.
One container contains the writable parameters, while the other One container contains the writable parameters, while the other
contains the operational states. contains the operational states.
The figure below describe the overall structure of the isis YANG The figure below describe the overall structure of the isis YANG
module: module:
module: ietf-isis module: ietf-isis
augment /rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes augment /rt:routing-state/rt:routing-instance/rt:ribs/rt:rib
/rt:route: /rt:routes/rt:route:
+--ro metric? uint32 +--ro metric? uint32
+--ro tag* uint64 +--ro tag* uint64
+--ro route-type? enumeration +--ro route-type? enumeration
augment /rt:fib-route/rt:output/rt:route: augment /rt:fib-route/rt:output/rt:route:
+--ro metric? uint32 +--ro metric? uint32
+--ro tag* uint64 +--ro tag* uint64
+--ro route-type? enumeration +--ro route-type? enumeration
augment /if:interfaces/if:interface: augment /if:interfaces/if:interface:
+--rw clns-mtu? uint16 +--rw clns-mtu? uint16
augment /rt:routing/rt:routing-instance/rt:routing-protocols augment /rt:routing/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol: /rt:routing-protocol:
+--rw isis +--rw isis
+--rw enable? boolean {admin-control}? +--rw enable? boolean {admin-control}?
+--rw level-type? level +--rw level-type? level
+--rw system-id? system-id +--rw system-id? system-id
+--rw maximum-area-addresses? uint8 {maximum-area-addresses}? +--rw maximum-area-addresses? uint8 {maximum-area-addresses}?
+--rw area-address* area-address +--rw area-address* area-address
+--rw mpls +--rw mpls
| +--rw ipv4-router-id? inet:ipv4-address {ipv4-router-id}? | +--rw ipv4-router-id? inet:ipv4-address {ipv4-router-id}?
| +--rw ipv6-router-id? inet:ipv6-address {ipv6-router-id}? | +--rw ipv6-router-id? inet:ipv6-address {ipv6-router-id}?
| +--rw igp-ldp-sync {igp-ldp-sync}? | +--rw igp-ldp-sync {igp-ldp-sync}?
skipping to change at page 5, line 22 skipping to change at page 5, line 29
| +--rw default-metric* [level] | +--rw default-metric* [level]
| | ... | | ...
| +--rw node-tag {node-tag}? | +--rw node-tag {node-tag}?
| | ... | | ...
| +--rw fast-reroute {fast-reroute}? | +--rw fast-reroute {fast-reroute}?
| ... | ...
+--rw interfaces +--rw interfaces
+--rw interface* [name] +--rw interface* [name]
... ...
augment /rt:routing-state/rt:routing-instance/rt:routing-protocols augment /rt:routing-state/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol: /rt:routing-protocol:
+--ro isis +--ro isis
+--ro enable? boolean {admin-control}? +--ro enable? boolean {admin-control}?
+--ro level-type? level +--ro level-type? level
+--ro system-id? system-id +--ro system-id? system-id
+--ro maximum-area-addresses? uint8 {maximum-area-addresses}? +--ro maximum-area-addresses? uint8 {maximum-area-addresses}?
+--ro area-address* area-address +--ro area-address* area-address
+--ro mpls +--ro mpls
| +--ro ipv4-router-id? inet:ipv4-address {ipv4-router-id}? | +--ro ipv4-router-id? inet:ipv4-address {ipv4-router-id}?
| +--ro ipv6-router-id? inet:ipv6-address {ipv6-router-id}? | +--ro ipv6-router-id? inet:ipv6-address {ipv6-router-id}?
| +--ro igp-ldp-sync {igp-ldp-sync}? | +--ro igp-ldp-sync {igp-ldp-sync}?
skipping to change at page 11, line 25 skipping to change at page 11, line 37
model. model.
Each interface has interface-specific parameters that may have a Each interface has interface-specific parameters that may have a
different value per level as described in previous section. An different value per level as described in previous section. An
interface-specific parameter always override an ISIS global parameter interface-specific parameter always override an ISIS global parameter
. .
Some parameters like BFD and hello-padding are defined as containers Some parameters like BFD and hello-padding are defined as containers
to permit easy extension by vendor specific modules. to permit easy extension by vendor specific modules.
+--rw interfaces +--rw interfaces
+--rw interface* [name] +--rw interface* [name]
+--rw name if:interface-ref +--rw name if:interface-ref
+--rw level-type? level +--rw level-type? level
+--rw lsp-pacing-interval? uint16 +--rw lsp-pacing-interval? uint16
+--rw lsp-retransmit-interval? uint16 +--rw lsp-retransmit-interval? uint16
+--rw passive? boolean +--rw passive? boolean
+--rw csnp-interval? uint16 +--rw csnp-interval? uint16
+--rw hello-padding +--rw hello-padding
| +--rw enable? boolean | +--rw enable? boolean
+--rw mesh-group-enable? mesh-group-state +--rw mesh-group-enable? mesh-group-state
skipping to change at page 19, line 10 skipping to change at page 19, line 23
The IS-IS SR YANG module requires the base segment routing module The IS-IS SR YANG module requires the base segment routing module
([I-D.litkowski-spring-sr-yang]) to be supported as there is a strong ([I-D.litkowski-spring-sr-yang]) to be supported as there is a strong
relationship between those modules. relationship between those modules.
The figure below describe the overall structure of the isis-sr YANG The figure below describe the overall structure of the isis-sr YANG
module: module:
module: ietf-isis-sr module: ietf-isis-sr
augment /rt:routing/rt:routing-instance/rt:routing-protocols augment /rt:routing/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol/isis:isis: /rt:routing-protocol/isis:isis:
+--rw segment-routing +--rw segment-routing
+--rw enabled? boolean +--rw enabled? boolean
+--rw srgb-list
| +--rw srgb* [lower-bound upper-bound]
| +--rw lower-bound uint32
| +--rw upper-bound uint32
+--rw bindings +--rw bindings
+--rw advertise +--rw advertise
| +--rw policies* string | +--rw policies* string
+--rw receive? boolean +--rw receive? boolean
augment /rt:routing/rt:routing-instance/rt:routing-protocols augment /rt:routing/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol/isis:isis/isis:interfaces/isis:interface: /rt:routing-protocol/isis:isis/isis:interfaces/isis:interface:
+--rw segment-routing +--rw segment-routing
+--rw adjacency-sid +--rw adjacency-sid
+--rw advertise-adj-group-sid* [group-id] +--rw advertise-adj-group-sid* [group-id]
| +--rw group-id uint32 | +--rw group-id uint32
+--rw advertise-protection? enumeration +--rw advertise-protection? enumeration
augment /rt:routing/rt:routing-instance/rt:routing-protocols augment /rt:routing/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol/isis:isis/isis:interfaces/isis:interface /rt:routing-protocol/isis:isis/isis:interfaces/isis:interface
/isis:fast-reroute: /isis:fast-reroute:
+--rw ti-lfa {ti-lfa}? +--rw ti-lfa {ti-lfa}?
+--rw enable? boolean +--rw enable? boolean
augment /rt:routing/rt:routing-instance/rt:routing-protocols augment /rt:routing/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol/isis:isis/isis:interfaces/isis:interface /rt:routing-protocol/isis:isis/isis:interfaces/isis:interface
/isis:fast-reroute/isis:lfa/isis:remote-lfa: /isis:fast-reroute/isis:lfa/isis:remote-lfa:
+--rw use-segment-routing-path? boolean {remote-lfa-sr}? +--rw use-segment-routing-path? boolean {remote-lfa-sr}?
augment /rt:routing-state/rt:routing-instance/rt:routing-protocols augment /rt:routing-state/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol/isis:isis: /rt:routing-protocol/isis:isis:
+--ro segment-routing +--ro segment-routing
+--ro enabled? boolean +--ro enabled? boolean
+--ro srgb-list
| +--ro srgb* [lower-bound upper-bound]
| +--ro lower-bound uint32
| +--ro upper-bound uint32
+--ro bindings +--ro bindings
+--ro advertise +--ro advertise
| +--ro policies* string | +--ro policies* string
+--ro receive? boolean +--ro receive? boolean
augment /rt:routing-state/rt:routing-instance/rt:routing-protocols augment /rt:routing-state/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol/isis:isis/isis:interfaces/isis:interface: /rt:routing-protocol/isis:isis/isis:interfaces/isis:interface:
+--ro segment-routing +--ro segment-routing
+--ro adjacency-sid +--ro adjacency-sid
+--ro advertise-adj-group-sid* [group-id] +--ro advertise-adj-group-sid* [group-id]
| +--ro group-id uint32 | +--ro group-id uint32
+--ro advertise-protection? enumeration +--ro advertise-protection? enumeration
augment /rt:routing-state/rt:routing-instance/rt:routing-protocols augment /rt:routing-state/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol/isis:isis/isis:interfaces/isis:interface /rt:routing-protocol/isis:isis/isis:interfaces/isis:interface
/isis:adjacencies/isis:adjacency: /isis:adjacencies/isis:adjacency:
+--ro adjacency-sid* [value] +--ro adjacency-sid* [value]
+--ro af? identityref +--ro af? identityref
+--ro value uint32 +--ro value uint32
+--ro weight? uint8 +--ro weight? uint8
+--ro protection-requested? boolean +--ro protection-requested? boolean
augment /rt:routing-state/rt:routing-instance/rt:routing-protocols augment /rt:routing-state/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol/isis:isis/isis:database/isis:level-db /rt:routing-protocol/isis:isis/isis:database/isis:level-db
/isis:lsp/isis:extended-is-neighbor/isis:neighbor: /isis:lsp/isis:extended-is-neighbor/isis:neighbor:
+--ro sid-list* [value] +--ro sid-list* [value]
+--ro flags? bits +--ro flags? bits
+--ro weight? uint8 +--ro weight? uint8
+--ro neighbor-id? isis:system-id +--ro neighbor-id? isis:system-id
+--ro value uint32 +--ro value uint32
augment /rt:routing-state/rt:routing-instance/rt:routing-protocols augment /rt:routing-state/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol/isis:isis/isis:database/isis:level-db /rt:routing-protocol/isis:isis/isis:database/isis:level-db
/isis:lsp/isis:mt-is-neighbor/isis:neighbor: /isis:lsp/isis:mt-is-neighbor/isis:neighbor:
+--ro sid-list* [value] +--ro sid-list* [value]
+--ro flags? bits +--ro flags? bits
+--ro weight? uint8 +--ro weight? uint8
+--ro neighbor-id? isis:system-id +--ro neighbor-id? isis:system-id
+--ro value uint32 +--ro value uint32
augment /rt:routing-state/rt:routing-instance/rt:routing-protocols augment /rt:routing-state/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol/isis:isis/isis:database/isis:level-db /rt:routing-protocol/isis:isis/isis:database/isis:level-db
/isis:lsp/isis:extended-ipv4-reachability/isis:prefixes: /isis:lsp/isis:extended-ipv4-reachability/isis:prefixes:
+--ro sid-list* [value] +--ro sid-list* [value]
+--ro flags? bits +--ro flags? bits
+--ro algorithm? uint8 +--ro algorithm? uint8
+--ro value uint32 +--ro value uint32
augment /rt:routing-state/rt:routing-instance/rt:routing-protocols augment /rt:routing-state/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol/isis:isis/isis:database/isis:level-db /rt:routing-protocol/isis:isis/isis:database/isis:level-db
/isis:lsp/isis:mt-extended-ipv4-reachability/isis:prefixes: /isis:lsp/isis:mt-extended-ipv4-reachability/isis:prefixes:
+--ro sid-list* [value] +--ro sid-list* [value]
+--ro flags? bits +--ro flags? bits
+--ro algorithm? uint8 +--ro algorithm? uint8
+--ro value uint32 +--ro value uint32
augment /rt:routing-state/rt:routing-instance/rt:routing-protocols augment /rt:routing-state/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol/isis:isis/isis:database/isis:level-db /rt:routing-protocol/isis:isis/isis:database/isis:level-db
/isis:lsp/isis:ipv6-reachability/isis:prefixes: /isis:lsp/isis:ipv6-reachability/isis:prefixes:
+--ro sid-list* [value] +--ro sid-list* [value]
+--ro flags? bits +--ro flags? bits
+--ro algorithm? uint8 +--ro algorithm? uint8
+--ro value uint32 +--ro value uint32
augment /rt:routing-state/rt:routing-instance/rt:routing-protocols augment /rt:routing-state/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol/isis:isis/isis:database/isis:level-db /rt:routing-protocol/isis:isis/isis:database/isis:level-db
/isis:lsp/isis:mt-ipv6-reachability/isis:prefixes: /isis:lsp/isis:mt-ipv6-reachability/isis:prefixes:
+--ro sid-list* [value] +--ro sid-list* [value]
+--ro flags? bits +--ro flags? bits
+--ro algorithm? uint8 +--ro algorithm? uint8
+--ro value uint32 +--ro value uint32
augment /rt:routing-state/rt:routing-instance/rt:routing-protocols augment /rt:routing-state/rt:routing-instance/rt:routing-protocols
/rt:routing-protocol/isis:isis/isis:database/isis:level-db /rt:routing-protocol/isis:isis/isis:database/isis:level-db/isis:lsp:
/isis:lsp:
+--ro segment-routing-bindings* [fec range] +--ro segment-routing-bindings* [fec range]
+--ro fec string +--ro fec string
+--ro range uint16 +--ro range uint16
+--ro flags? bits +--ro flags? bits
+--ro weight? uint8 +--ro weight? uint8
+--ro binding* +--ro binding*
+--ro prefix-sid +--ro prefix-sid
| +--ro sid-list* [value] | +--ro sid-list* [value]
| +--ro flags? bits | +--ro flags? bits
| +--ro algorithm? uint8 | +--ro algorithm? uint8
skipping to change at page 22, line 36 skipping to change at page 23, line 7
Some ISIS specific routes attributes are added to route objects of Some ISIS specific routes attributes are added to route objects of
the ietf-routing module by augmenting "/rt:routing- the ietf-routing module by augmenting "/rt:routing-
state/rt:ribs/rt:rib/rt:routes/rt:route" and "/rt:fib- state/rt:ribs/rt:rib/rt:routes/rt:route" and "/rt:fib-
route/rt:output/rt:route". route/rt:output/rt:route".
The module uses some groupings from ietf-keychain, routing-policy and The module uses some groupings from ietf-keychain, routing-policy and
ietf-bfd modules. ietf-bfd modules.
7. ISIS YANG Module 7. ISIS YANG Module
<CODE BEGINS> file "ietf-isis@2015-09-10.yang" <CODE BEGINS> file "ietf-isis@2015-09-18.yang"
module ietf-isis { module ietf-isis {
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";
} }
skipping to change at page 24, line 9 skipping to change at page 24, line 28
&lt;mailto:yiqu@cisco.com&gt; &lt;mailto:yiqu@cisco.com&gt;
Jeff Tantsura Jeff Tantsura
&lt;mailto:jeff.tantsura@ericsson.com&gt; &lt;mailto:jeff.tantsura@ericsson.com&gt;
"; ";
description description
"The YANG module defines a generic configuration model for "The YANG module defines a generic configuration model for
ISIS common across all of the vendor implementations."; ISIS common across all of the vendor implementations.";
revision 2015-09-18 {
description
" * Reissuing draft.";
reference "draft-ietf-isis-yang-isis-06";
}
revision 2015-09-10 {
description
" * 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 { revision 2015-06-22 {
description description
" * Segment routing is part os a separate module."; " * Segment routing is part os a separate module.";
reference "draft-ietf-isis-yang-isis-03"; reference "draft-ietf-isis-yang-isis-03";
} }
revision 2015-03-03 { revision 2015-03-03 {
description description
" * Reviewed config and op state groupings. " * Reviewed config and op state groupings.
* Add default value to lfa candidate-disabled * Add default value to lfa candidate-disabled
* Add enable leaf to isis container to reflect admin state * Add enable leaf to isis container to reflect admin state
skipping to change at page 97, line 20 skipping to change at page 98, line 4
description description
"This notification is sent when a LSP "This notification is sent when a LSP
is regenerated. is regenerated.
The notification generation must be throttled with at least The notification generation must be throttled with at least
a 5 second gap. "; a 5 second gap. ";
} }
} }
<CODE ENDS> <CODE ENDS>
8. ISIS Segment Routing YANG Module 8. ISIS Segment Routing YANG Module
<CODE BEGINS> file "ietf-isis-sr@2015-09-10.yang" <CODE BEGINS> file "ietf-isis-sr@2015-09-18.yang"
module ietf-isis-sr { module ietf-isis-sr {
namespace "urn:ietf:params:xml:ns:" namespace "urn:ietf:params:xml:ns:"
+ "yang:ietf-isis-sr"; + "yang:ietf-isis-sr";
prefix isis-sr; prefix isis-sr;
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
} }
skipping to change at page 98, line 23 skipping to change at page 99, line 5
Jeff Tantsura Jeff Tantsura
&lt;mailto:jeff.tantsura@ericsson.com&gt; &lt;mailto:jeff.tantsura@ericsson.com&gt;
"; ";
description description
"The YANG module defines a generic configuration model for "The YANG module defines a generic configuration model for
Segment routing ISIS extensions common across all of the vendor Segment routing ISIS extensions common across all of the vendor
implementations."; implementations.";
revision 2015-09-18 {
description "no modif";
reference "";
}
revision 2015-07-02 { revision 2015-07-02 {
description description
" "
* Add TILFA and rLFA SR * Add TILFA and rLFA SR
* Add container to SRGB * Add container to SRGB
"; ";
reference ""; reference "";
} }
revision 2015-05-27 { revision 2015-05-27 {
skipping to change at page 116, line 18 skipping to change at page 117, line 4
Acee Lindem Acee Lindem
Cisco Systems Cisco Systems
Email: acee@cisco.com Email: acee@cisco.com
Jeffrey Zhang Jeffrey Zhang
Juniper Networks Juniper Networks
Email: zzhang@juniper.net Email: zzhang@juniper.net
Ladislav Lhotka Ladislav Lhotka
CZ.NIC
Email: lhotka@nic.cz Email: lhotka@nic.cz
 End of changes. 38 change blocks. 
52 lines changed or deleted 78 lines changed or added

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