--- 1/draft-ietf-isis-yang-isis-cfg-33.txt 2019-01-24 10:13:19.961200028 -0800 +++ 2/draft-ietf-isis-yang-isis-cfg-34.txt 2019-01-24 10:13:20.153204657 -0800 @@ -5,21 +5,21 @@ Expires: July 25, 2019 Arrcus, Inc A. Lindem Cisco Systems J. Zhang Juniper Networks L. Lhotka CZ.NIC January 21, 2019 YANG Data Model for IS-IS Protocol - draft-ietf-isis-yang-isis-cfg-33 + draft-ietf-isis-yang-isis-cfg-34 Abstract This document defines a YANG data model that can be used to configure and manage IS-IS protocol on network elements. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and @@ -57,21 +57,21 @@ 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 2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3 2.1. IS-IS Configuration . . . . . . . . . . . . . . . . . . . 9 - 2.2. Multitopology Parameters . . . . . . . . . . . . . . . . 10 + 2.2. Multi-topology Parameters . . . . . . . . . . . . . . . 10 2.3. Per-Level Parameters . . . . . . . . . . . . . . . . . . 10 2.4. Per-Interface Parameters . . . . . . . . . . . . . . . . 12 2.5. Authentication Parameters . . . . . . . . . . . . . . . 19 2.6. IGP/LDP synchronization . . . . . . . . . . . . . . . . 20 2.7. ISO parameters . . . . . . . . . . . . . . . . . . . . . 20 2.8. IP FRR . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.9. Operational States . . . . . . . . . . . . . . . . . . . 21 3. RPC Operations . . . . . . . . . . . . . . . . . . . . . . . 21 4. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 21 5. Interaction with Other YANG Modules . . . . . . . . . . . . 23 @@ -432,45 +432,46 @@ The model implements features, thus some of the configuration statement becomes optional. As an example, the ability to control the administrative state of a particular IS-IS instance is optional. By advertising the feature "admin-control", a device communicates to the client that it supports the ability to shutdown a particular IS- IS instance. The global configuration contains usual IS-IS parameters such as lsp- mtu, lsp-lifetime, lsp-refresh, default-metric... -2.2. Multitopology Parameters +2.2. Multi-topology Parameters - The model supports multitopology (MT) IS-IS as defined in [RFC5120]. + The model supports multi-topology (MT) IS-IS as defined in [RFC5120]. The "topologies" container is used to enable support of MT extensions. The "name" used in the topology list should refer to an existing RIB of the device. Some specific parameters could be defined on a per topology basis both at global level and at interface level: for example, an interface metric can be defined per topology. Multiple address families (like IPv4 or IPv6) can also be activated - within the default topology. This can be achieved using the "afs" - container (requiring "nlpid-control" feature to be advertised). + within the default topology. This can be achieved using the address- + families container (requiring "nlpid-control" feature to be + advertised). 2.3. Per-Level Parameters Some parameters allow a per level configuration. In this case, the parameter is modeled as a container with three configuration locations: - o a top level container: corresponds to level-1-2, so the + o a top-level container: corresponds to level-1-2, so the configuration applies to both levels. o a level-1 container: corresponds to level-1 specific parameters. o a level-2 container: corresponds to level-2 specific parameters. +--rw priority | +--rw value? uint8 | +--rw level-1 | | +--rw value? uint8 @@ -484,21 +485,21 @@ 100 200 An implementation SHOULD prefer a level specific parameter over a level-all parameter. As example, if the priority is 100 for the - level-1, 200 for the level-2 and 250 for the top level configuration, + level-1, 200 for the level-2 and 250 for the top-level configuration, the implementation should use 100 for the level-1 and 200 for the level-2. Some parameters like "overload bit" and "route preference" are not modeled to support a per level configuration. If an implementation supports per level configuration for such parameter, this implementation SHOULD augment the current model by adding both level-1 and level-2 containers and SHOULD reuse existing configuration groupings. @@ -522,38 +523,38 @@ } container level-2 { uses isis:overload-global-cfg; description "Level 2 configuration."; } } If an implementation does not support per level configuration for a parameter modeled with per level configuration, the implementation - SHOULD advertise a deviation to announce the non support of the + 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. 2.4. Per-Interface Parameters The per-interface section of the IS-IS instance describes the interface specific parameters. The interface is modeled as a reference to an existing interface defined in the "ietf-interfaces" YANG model ([RFC8343]. Each interface has some interface-specific parameters that may have a different per level value as described in previous section. An - interface-specific parameter always override an IS-IS global + interface-specific parameter always overrides an IS-IS global parameter. Some parameters like hello-padding are defined as containers to allow easy extension by vendor specific modules. +--rw interfaces +--rw interface* [name] +--rw name if:interface-ref +--rw level-type? level +--rw lsp-pacing-interval? @@ -1013,32 +1014,32 @@ 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. protocols-supported-mismatch: This notification is sent when the - system receives a non pseudonode LSP that has no matching protocol + 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. + receives an LSP with a parse error. adjacency-state-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-received: This notification is sent when an LSP is received. - lsp-generation: This notification is sent when a LSP is + lsp-generation: This notification is sent when an LSP is regenerated. 5. Interaction with Other YANG Modules The "isis" container augments the "/rt:routing/rt:control-plane- protocols/control-plane-protocol" container of the ietf-routing [RFC8349] module by defining IS-IS specific parameters. The "isis" module augments "/if:interfaces/if:interface" defined by [RFC8343] with ISO specific parameters. @@ -1061,21 +1062,21 @@ [I-D.ietf-bfd-yang]. 6. IS-IS YANG Module The following RFCs, drafts and external standards are not referenced in the document text but are referenced in the ietf-isis.yang module: [ISO-10589], [RFC1195], [RFC5029], [RFC5130], [RFC5305], [RFC5306], [RFC5308], [RFC5880], [RFC5881], [RFC6119], [RFC6232], [RFC7794], [RFC7810], [RFC7917], [RFC8405]. - file "ietf-ospf@2019-01-23.yang" + file "ietf-ospf@2019-01-24.yang" module ietf-isis { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-isis"; prefix isis; import ietf-routing { prefix "rt"; reference "RFC 8349 - A YANG Data Model for Routing Management (NMDA Version)"; @@ -1120,53 +1121,53 @@ Forwarding Detection (BFD). -- Note to RFC Editor Please replace YYYY with published RFC number for draft-ietf-bfd-yang."; } organization "IETF LSR Working Group"; contact - "WG List: <mailto:lsr@ietf.org> + "WG List: Editor: Stephane Litkowski - <mailto:stephane.litkowski@orange.com> + Derek Yeung - <mailto:derek@arrcus.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:jefftant.ietf@gmail.com> + "; description "This YANG module defines the generic configuration and operational state for the IS-IS protocol. It is intended that the module will be extended by vendors to define vendor-specific IS-IS configuration parameters and policies, - for example route maps or route policies. + for example, route maps or route policies. This YANG module conforms to the Network Management Datastore Architecture (NDMA) as described in RFC 8242. Copyright (c) 2018 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License @@ -1178,21 +1179,21 @@ see the RFC itself for full legal notices. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. "; - revision 2019-01-23 { + revision 2019-01-24 { description "Initial revision."; reference "RFC XXXX"; } /* Identities */ identity isis { base rt:routing-protocol; description "Identity for the IS-IS routing protocol."; @@ -1461,21 +1462,21 @@ description "This type defines the area address format."; } typedef snpa { type string { length "0 .. 20"; } description "This type defines the Subnetwork Point - of Attachement (SNPA) format. + of Attachment (SNPA) format. The SNPA should be encoded according to the rules specified for the particular type of subnetwork being used. As an example, for an ethernet subnetwork, the SNPA is encoded as a MAC address like '00aa.bbcc.ddee'."; } typedef system-id { type string { pattern @@ -1557,21 +1558,21 @@ leaf interface-name { type if:interface-ref; description "IS-IS interface name"; } leaf interface-level { type level; description "IS-IS level of the interface."; } leaf extended-circuit-id { type extended-circuit-id; - description "Eextended circuit-id of the interface."; + description "Extended circuit-id of the interface."; } } /* Groupings for IP Fast Reroute */ grouping instance-fast-reroute-config { description "This group defines global configuration of IP Fast ReRoute (FRR)."; container fast-reroute { @@ -2069,21 +2070,21 @@ } enum "short-wait" { description "SHORT_WAIT state"; } enum "long-wait" { description "LONG_WAIT state"; } } config false; description - "Current SPF backoff algorithm state."; + "Current SPF back-off algorithm state."; } leaf remaining-time-to-learn { type rt-types:timer-value-milliseconds; units "msec"; config false; description "Remaining time until time-to-learn timer fires."; } leaf remaining-hold-down { type rt-types:timer-value-milliseconds; @@ -2182,21 +2183,21 @@ } enum both { description "Advertise both metric styles"; } } default wide-only; description "Type of metric to be generated: - wide-only means only new metric style is generated, - - old-only means that only old style metric + - old-only means that only old-style metric is generated, - both means that both are advertised. This leaf is only affecting IPv4 metrics."; } description "Grouping for global metric style config."; } grouping default-metric-global-cfg { leaf value { @@ -2687,21 +2688,21 @@ } description "IS-IS hello padding configuration."; } leaf mesh-group-enable { type mesh-group-state; description "IS-IS interface mesh-group state"; } leaf mesh-group { when "../mesh-group-enable = 'mesh-set'" { description - "Only valid when mesh-group-enable equals meshset"; + "Only valid when mesh-group-enable equals mesh-set"; } type uint8; description "IS-IS interface mesh-group ID."; } leaf interface-type { type interface-type; default "broadcast"; description "Type of adjacency to be established on the interface. This dictates the type of hello messages that are used."; @@ -2938,21 +2939,21 @@ 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."; + occurred."; } leaf id-len-mismatch { type uint32; description "Number of times a PDU is received with a different value for the ID field length than that of the receiving system."; } leaf partition-changes { type uint32; @@ -2978,21 +2979,21 @@ description "System counters grouping."; } grouping event-counters { container event-counters { config false; leaf adjacency-changes { type uint32; description "The number of times an adjacency state change has - occured on this interface."; + occurred on this interface."; } leaf adjacency-number { type uint32; description "The number of adjacencies on this interface."; } leaf init-fails { type uint32; description @@ -3129,21 +3130,21 @@ type uint32; description "Received unknown PDUs."; } leaf out { type uint32; description "Sent unknown PDUs."; } description "Number of unknown PDUs received/sent."; } description - "List of packet counter for supported llevels."; + "List of packet counter for supported levels."; } description "Packet counters per IS-IS level."; } description "Grouping for per IS-IS Level packet counters."; } /* Groupings for various log buffers */ grouping spf-log { container spf-log { @@ -3272,21 +3273,21 @@ description "This container lists the LSP log. Local LSP modifications are also included in the list."; } description "Grouping for LSP log."; } /* Groupings for the LSDB description */ - /* Unknown TLV and subTLV description */ + /* Unknown TLV and sub-TLV description */ grouping tlv { description "Type-Length-Value (TLV)"; leaf type { type uint16; description "TLV type."; } leaf length { type uint16; description "TLV length (octets)."; @@ -3303,34 +3304,34 @@ unknown sub-TLVs."; container unknown-tlvs { description "All unknown TLVs."; list unknown-tlv { description "Unknown TLV."; uses tlv; } } } - /* TLVs and subTLVs for prefixes */ + /* TLVs and sub-TLVs for prefixes */ grouping prefix-reachability-attributes { description "Grouping for 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."; + description "Re-advertisement flag."; } leaf node-flag { type boolean; description "Node flag."; } } grouping prefix-ipv4-source-router-id { description @@ -3486,21 +3487,21 @@ "List of 32-bit tags associated with the IPv4 prefix."; } leaf-list tag64 { type uint64; description "List of 32-bit tags associated with the IPv4 prefix."; } uses prefix-attributes-extension; } - /* TLVs and subTLVs for neighbors */ + /* TLVs and sub-TLVs for neighbors */ grouping neighbor-link-attributes { description "Grouping for link attributes as defined in RFC5029"; leaf link-attributes-flags { type uint16; description "Flags for the link attributes"; } @@ -3894,21 +3895,21 @@ description "IS-IS error metric supported"; } description "IS-IS error metric container"; } description "Instance of a particular adjacency as defined in ISO10589."; } } } - /* Top level TLVs */ + /* Top-level TLVs */ grouping tlv132-ipv4-addresses { leaf-list ipv4-addresses { type inet:ipv4-address; description "List of IPv4 addresses of the IS-IS node - IS-IS reference is TLV 132."; } description "Grouping for TLV132."; } @@ -4120,30 +4121,30 @@ "SRLG attribute of a link."; } description "List of links with SRLGs"; } } /* Grouping for LSDB description */ grouping lsp-entry { - description "IS-IS LSP database entry groupting"; + description "IS-IS LSP database entry grouping"; leaf decoded-completed { type boolean; description "IS-IS LSP body fully decoded."; } leaf raw-data { type yang:hex-string; description - "The hexadecial representation of the complete LSP in + "The hexadecimal representation of the complete LSP in network-byte order (NBO) as received or originated."; } leaf lsp-id { type lsp-id; description "LSP ID of the LSP"; } leaf checksum { type uint16; description "LSP checksum"; } @@ -4283,39 +4284,39 @@ type uint16 { range "0 .. 4095"; } description "Multi-topology (MT) identifier"; } uses prefix-ipv4-extended; uses unknown-tlvs; description "List of extended prefixes."; } description - "IPv4 multi-topolgy (MT) extended reachability + "IPv4 multi-topology (MT) extended reachability information container - IS-IS reference is TLV 235."; } container mt-ipv6-reachability { list prefixes { leaf MT-ID { type uint16 { range "0 .. 4095"; } description "Multi-topology (MT) identifier"; } uses prefix-ipv6-extended; uses unknown-tlvs; description "List of IPv6 extended prefixes."; } description - "IPv6 multi-topolgy (MT) extended reachability + "IPv6 multi-topology (MT) extended reachability information container - IS-IS reference is TLV 237."; } container ipv6-reachability { list prefixes { uses prefix-ipv6-extended; uses unknown-tlvs; description "List of IPv6 prefixes."; } description @@ -4574,21 +4575,21 @@ } 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 5 seconds betweeen successive + with at least 5 seconds between successive notifications."; } notification if-state-change { uses notification-instance-hdr; uses notification-interface-hdr; leaf state { type if-state-type; description "Interface state."; @@ -4629,41 +4630,41 @@ 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 5 seconds betweeen successive + with at least 5 seconds between successive notifications."; } 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 "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 5 seconds betweeen successive + with at least 5 seconds between successive notifications."; } notification own-lsp-purge { uses notification-instance-hdr; uses notification-interface-hdr; leaf lsp-id { type lsp-id; description "LSP ID"; } @@ -4674,85 +4675,85 @@ 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 reoriginate the LSP with a higher sequence + system has to originate 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 field. The notification generation must be throttled - with at least 5 seconds betweeen successive + with at least 5 seconds between successive notifications."; } 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 - with at least 5 seconds betweeen successive + The notification generation must be throttled + with at least 5 seconds between successive notifications."; } 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 5 seconds betweeen successive + with at least 5 seconds between successive notifications."; } notification area-mismatch { 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 Hello PDU from an IS that does not share any area address. The notification generation must be throttled - with at least 5 seconds betweeen successive + with at least 5 seconds between successive notifications."; } notification rejected-adjacency { uses notification-instance-hdr; uses notification-interface-hdr; leaf raw-pdu { type binary; description "Received raw PDU."; @@ -4764,41 +4765,41 @@ description "The system may provide a reason to reject the adjacency. If the reason is not available, an empty string will be returned. The expected format is a single line text."; } 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 5 seconds betweeen successive + throttled with at least 5 seconds between successive notifications."; } notification protocols-supported-mismatch { uses notification-instance-hdr; uses notification-interface-hdr; leaf raw-pdu { type binary; description "Received raw PDU."; } leaf-list protocols { type uint8; description "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 protocols supported. The notification generation must be throttled - with at least 5 seconds betweeen successive + with at least 5 seconds between successive notifications."; } notification lsp-error-detected { uses notification-instance-hdr; uses notification-interface-hdr; leaf lsp-id { type lsp-id; description "LSP ID."; } @@ -4817,21 +4818,21 @@ 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 an LSP with a parse error. The notification generation must - be throttled with at least 5 seconds betweeen successive + be throttled with at least 5 seconds between successive notifications."; } notification adjacency-state-change { uses notification-instance-hdr; uses notification-interface-hdr; leaf neighbor { type string { length "1..255"; } @@ -4886,21 +4887,21 @@ description "Timestamp when the LSP was received."; } leaf neighbor-system-id { type system-id; description "Neighbor system-id of LSP sender"; } description "This notification is sent when an LSP is received. The notification generation must be throttled with at - least 5 seconds betweeen successive notifications."; + least 5 seconds between successive notifications."; } notification lsp-generation { uses notification-instance-hdr; leaf lsp-id { type lsp-id; description "LSP ID"; } leaf sequence { @@ -4909,21 +4910,21 @@ } leaf send-timestamp { type yang:timestamp; description "Timestamp when our LSP was regenerated."; } description "This notification is sent when an LSP is regenerated. The notification generation must be throttled with at - least 5 seconds betweeen successive notifications."; + least 5 seconds between successive notifications."; } } 7. Security Considerations The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure @@ -4952,31 +4953,31 @@ sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. The exposure of the Link State Database (LSDB) will expose the detailed topology of the network including authentication parameters. Implementations MUST NOT provide a configured authentication key in a clear text format in response to any request (e.g., via get, get-config). For IS-IS authentication, configuration is supported via the specification of key-chain [RFC8177] or the direction specification - of key and authentication algorithm. Hence, authentification + of key and authentication algorithm. Hence, authentication configuration using the "auth-table-trailer" case in the "authentication" container inherits the security considerations of [RFC8177]. This includes the considerations with respect to the local storage and handling of authentication keys. Some of the RPC operations in this YANG module may be considered sensitive or vulnerable in some network environments. It is thus important to control access to these operations. The OSPF YANG module support the "clear-adjacency" and "clear-database" RPCs. If - access too either of these is compromised, they can result in + access to either of these is compromised, they can result in temporary network outages be employed to mount DoS attacks. 8. Contributors Authors would like to thank Kiran Agrahara Sreenivasa, Dean Bogdanovic, Yingzhen Qu, Yi Yang, Jeff Tanstura for their major contributions to the draft. 9. IANA Considerations @@ -5024,21 +5025,21 @@ o In FRR stats, "prefix" is now encoded as inet:ip-prefix rather than a string. "alternate" is now encoded as ip-address. 10.2. From version -28 to version -29 o Fixed area-address type pattern. The authorized number of bytes was wrong. 10.3. From version -27 to version -28 - o Fixed non accurate description of level-type leaf. + o Fixed inaccurate description of level-type leaf. 10.4. From version -26 to version -27 o Fixed XPATH to switching-capability leaf in "when" statement of psc-specific and tdm-specific containers. 10.5. From version -25 to version -26 o Modify BFD reference descriptions. @@ -5073,27 +5074,27 @@ associated typedef. o Revised some groupings and their names (alignment with OSPF). o Some description alignment with OSPF. o auto-cost container alignment with OSPF. o MT-ID leaf in database description renamed (lower-case) mt-id. - o In lsp-log grouping, leaf change is renamed reason to align with - OSPF. + o In the lsp-log grouping, leaf change is renamed reason to align + with OSPF. o Added some link attributes (GMPLS, TE, extended TE, SRLGs) in the LSDB. - o Added extended-system-id typedef which contains the systemid plus + o Added extended-system-id typedef which contains the system-id plus the pseudonode number. o Add support of POI Purge Originator Identification. 10.7. From version -22 to version -24 o Fix revision date of the module. 10.8. From version -21 to version -22 @@ -5201,23 +5202,24 @@ o Aligned LFA if per level cfg. o Align to draft-ietf-netmod-routing-cfg-23. 10.20. From version -07 to version -08 o Remove selector from system-id type. o Add some default values. - o Moved lists to containers+groupings for per level configuration. + o Moved lists to containers and 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 changed keychain module reference. 10.21. From version -05 to version -07 o Move Overload config from list to container. o Move Overload-max-metric config from list to container. @@ -5242,21 +5244,21 @@ 10.23. From version -02 to version -03 o Reviewed config and op state groupings. o Add default value to lfa candidate-disabled. o Add enable leaf to isis container to reflect admin state. o Move to VRF centric only. - o Segment routing is part os a separate module. + o Segment routing is part of a separate module. 10.24. From version -01 to version -02 o Adding IPFRR. o Adding igp-ldp-sync. o Adding segment-routing. o Adding instance reference to operational states. @@ -5312,21 +5314,21 @@ 11.1. Normative References [I-D.ietf-bfd-yang] Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and G. Mirsky, "YANG Data Model for Bidirectional Forwarding Detection (BFD)", draft-ietf-bfd-yang-17 (work in progress), August 2018. [ISO-10589] ISO, , "Intermediate System to Intermediate System intra- - domain routeing information exchange protocol for use in + domain routing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service (ISO 8473)", International Standard 10589: 2002, Second Edition, 2002. [RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and dual environments", RFC 1195, DOI 10.17487/RFC1195, December 1990, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119,