--- 1/draft-ietf-isis-yang-isis-cfg-30.txt 2019-01-21 03:13:10.638318919 -0800 +++ 2/draft-ietf-isis-yang-isis-cfg-31.txt 2019-01-21 03:13:10.826323442 -0800 @@ -1,25 +1,25 @@ IS-IS Working Group S. Litkowski Internet-Draft Orange Intended status: Standards Track D. Yeung -Expires: July 22, 2019 Arrcus, Inc +Expires: July 25, 2019 Arrcus, Inc A. Lindem Cisco Systems J. Zhang Juniper Networks L. Lhotka CZ.NIC - January 18, 2019 + January 21, 2019 - YANG Data Model for IS-IS protocol - draft-ietf-isis-yang-isis-cfg-30 + YANG Data Model for IS-IS Protocol + draft-ietf-isis-yang-isis-cfg-31 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 @@ -35,21 +35,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on July 22, 2019. + This Internet-Draft will expire on July 25, 2019. Copyright Notice Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -57,66 +57,66 @@ 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 . . . . . . . . . . . . . . . . 9 + 2.2. Multitopology Parameters . . . . . . . . . . . . . . . . 10 2.3. Per-Level Parameters . . . . . . . . . . . . . . . . . . 10 - 2.4. Per-Interface Parameters . . . . . . . . . . . . . . . . 11 - 2.5. Authentication Parameters . . . . . . . . . . . . . . . . 18 - 2.6. IGP/LDP synchronization . . . . . . . . . . . . . . . . . 18 - 2.7. ISO parameters . . . . . . . . . . . . . . . . . . . . . 18 - 2.8. IP FRR . . . . . . . . . . . . . . . . . . . . . . . . . 19 - 2.9. Operational States . . . . . . . . . . . . . . . . . . . 19 - 3. RPC Operations . . . . . . . . . . . . . . . . . . . . . . . 20 - 4. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 20 - 5. Interaction with Other YANG Modules . . . . . . . . . . . . . 21 - 6. IS-IS YANG Module . . . . . . . . . . . . . . . . . . . . . . 22 - 7. Security Considerations . . . . . . . . . . . . . . . . . . . 102 - 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 103 - 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 103 - 10. Change log for ietf-isis YANG module . . . . . . . . . . . . 103 - 10.1. From version -29 to version -30 . . . . . . . . . . . . 103 - 10.2. From version -28 to version -29 . . . . . . . . . . . . 104 - 10.3. From version -27 to version -28 . . . . . . . . . . . . 104 - 10.4. From version -26 to version -27 . . . . . . . . . . . . 104 - 10.5. From version -25 to version -26 . . . . . . . . . . . . 104 - 10.6. From version -24 to version -25 . . . . . . . . . . . . 104 - 10.7. From version -22 to version -24 . . . . . . . . . . . . 105 - 10.8. From version -21 to version -22 . . . . . . . . . . . . 106 - 10.9. From version -20 to version -21 . . . . . . . . . . . . 106 - 10.10. From version -19 to version -20 . . . . . . . . . . . . 106 - 10.11. From version -18 to version -19 . . . . . . . . . . . . 106 - 10.12. From version -17 to version -18 . . . . . . . . . . . . 106 - 10.13. From version -16 to version -17 . . . . . . . . . . . . 106 - 10.14. From version -15 to version -16 . . . . . . . . . . . . 107 - 10.15. From version -14 to version -15 . . . . . . . . . . . . 107 - 10.16. From version -13 to version -14 . . . . . . . . . . . . 107 - 10.17. From version -12 to version -13 . . . . . . . . . . . . 107 - 10.18. From version -09 to version -12 . . . . . . . . . . . . 108 - 10.19. From version -08 to version -09 . . . . . . . . . . . . 108 - 10.20. From version -07 to version -08 . . . . . . . . . . . . 108 - 10.21. From version -05 to version -07 . . . . . . . . . . . . 108 - 10.22. From version -03 to version -05 . . . . . . . . . . . . 108 - 10.23. From version -02 to version -03 . . . . . . . . . . . . 109 - 10.24. From version -01 to version -02 . . . . . . . . . . . . 109 - 10.25. From version -00 to version -01 . . . . . . . . . . . . 109 - 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 110 - 11.1. Normative References . . . . . . . . . . . . . . . . . . 110 - 11.2. Informative References . . . . . . . . . . . . . . . . . 114 - Appendix A. Example of IS-IS configuration in XML . . . . . . . 114 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 116 + 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 + 6. IS-IS YANG Module . . . . . . . . . . . . . . . . . . . . . . 23 + 7. Security Considerations . . . . . . . . . . . . . . . . . . . 104 + 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 105 + 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 105 + 10. Change log for ietf-isis YANG module . . . . . . . . . . . . 105 + 10.1. From version -29 to version -30 . . . . . . . . . . . . 105 + 10.2. From version -28 to version -29 . . . . . . . . . . . . 106 + 10.3. From version -27 to version -28 . . . . . . . . . . . . 106 + 10.4. From version -26 to version -27 . . . . . . . . . . . . 106 + 10.5. From version -25 to version -26 . . . . . . . . . . . . 106 + 10.6. From version -24 to version -25 . . . . . . . . . . . . 106 + 10.7. From version -22 to version -24 . . . . . . . . . . . . 107 + 10.8. From version -21 to version -22 . . . . . . . . . . . . 107 + 10.9. From version -20 to version -21 . . . . . . . . . . . . 107 + 10.10. From version -19 to version -20 . . . . . . . . . . . . 108 + 10.11. From version -18 to version -19 . . . . . . . . . . . . 108 + 10.12. From version -17 to version -18 . . . . . . . . . . . . 108 + 10.13. From version -16 to version -17 . . . . . . . . . . . . 108 + 10.14. From version -15 to version -16 . . . . . . . . . . . . 108 + 10.15. From version -14 to version -15 . . . . . . . . . . . . 108 + 10.16. From version -13 to version -14 . . . . . . . . . . . . 109 + 10.17. From version -12 to version -13 . . . . . . . . . . . . 109 + 10.18. From version -09 to version -12 . . . . . . . . . . . . 109 + 10.19. From version -08 to version -09 . . . . . . . . . . . . 109 + 10.20. From version -07 to version -08 . . . . . . . . . . . . 110 + 10.21. From version -05 to version -07 . . . . . . . . . . . . 110 + 10.22. From version -03 to version -05 . . . . . . . . . . . . 110 + 10.23. From version -02 to version -03 . . . . . . . . . . . . 110 + 10.24. From version -01 to version -02 . . . . . . . . . . . . 111 + 10.25. From version -00 to version -01 . . . . . . . . . . . . 111 + 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 112 + 11.1. Normative References . . . . . . . . . . . . . . . . . . 112 + 11.2. Informative References . . . . . . . . . . . . . . . . . 115 + Appendix A. Example of IS-IS configuration in XML . . . . . . . 116 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 118 1. Introduction This document defines a YANG ([RFC7950]) data model for IS-IS routing protocol. The data model covers configuration of an IS-IS routing protocol instance as well as operational states. A simplified tree representation of the data model is presented in @@ -410,21 +410,21 @@ +---n lsp-generation +--ro routing-protocol-name? -> /rt:routing/control-plane-protocols/control-plane-protocol/name +--ro isis-level? level +--ro lsp-id? lsp-id +--ro sequence? uint32 +--ro send-timestamp? yang:timestamp 2.1. IS-IS Configuration - The IS-IS configuration container is divided in: + The IS-IS configuration is divided in: o Global parameters. o Per interface configuration (see Section 2.4). Additional modules may be created to support any additional parameters. These additional modules MUST augment the ietf-isis module. The model implements features, thus some of the configuration @@ -907,21 +907,21 @@ As IS-IS protocol is based on ISO protocol suite, some ISO parameters may be required. This module augments interface configuration model to support ISO configuration parameters. The clns-mtu can be defined under the interface. 2.8. IP FRR - This YANG model supports LFA (Loop Free Alternates) ([RFC5286]) and + This YANG module supports LFA (Loop Free Alternates) ([RFC5286]) and remote LFA ([RFC7490]) as IP FRR techniques. The "fast-reroute" container may be augmented by other models to support other IPFRR flavors (MRT, TILFA ...). The current version of the model supports activation of LFA and remote LFA at interface only. The global "lfa" container is present but kept empty to allow augmentation with vendor specific properties like policies. Remote LFA is considered as a child of LFA. Remote LFA cannot be @@ -971,23 +971,23 @@ 4. Notifications The "ietf-isis" module introduces some notifications : database-overload: raised when overload condition is changed. lsp-too-large: raised when the system tries to propagate a too large PDU. - if-state-change: raise when the state of an interface changes. + if-state-change: raised when the state of an interface changes. - corrupted-lsp-detected: raised when the system find that an LSP + corrupted-lsp-detected: raised when the system finds that an LSP that was stored in memory has become corrupted. attempt-to-exceed-max-sequence: This notification is sent when the system wraps the 32-bit sequence counter of an LSP. id-len-mismatch: This notification is sent when we receive a PDU with a different value for the System ID length. max-area-addresses-mismatch: This notification is sent when we receive a PDU with a different value for the Maximum Area @@ -1026,23 +1026,23 @@ 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-generation: This notification is sent when a LSP is regenerated. 5. Interaction with Other YANG Modules - The "isis" configuration container augments the "/rt:routing/ - rt:control-plane-protocols/control-plane-protocol" container of the - ietf-routing [RFC8349] module by defining IS-IS specific parameters. + 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. The "isis" operational state container augments the "/rt:routing- state/rt:control-plane-protocols/control-plane-protocol" container of the ietf-routing module by defining IS-IS specific operational states. Some IS-IS specific routes attributes are added to route objects of @@ -1052,28 +1052,33 @@ The modules defined in this document use some groupings from ietf- keychain [RFC8177]. The module reuses types from [RFC6991] and [RFC8294]. To support BFD for fast detection, the module relies on [I-D.ietf-bfd-yang]. 6. IS-IS YANG Module - file "ietf-isis@2019-01-18.yang" + 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-isis@2019-01-21.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)"; } import ietf-inet-types { prefix inet; reference "RFC 6991 - Common YANG Data Types"; } @@ -1147,21 +1151,21 @@ "; 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. - This YANG model conforms to the Network Management + 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 set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents @@ -1170,21 +1174,21 @@ This version of this YANG module is part of RFC XXXX; 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-18 { + revision 2019-01-21 { description "Initial revision."; reference "RFC XXXX"; } /* Identities */ identity isis { base rt:routing-protocol; description "Identity for the IS-IS routing protocol."; @@ -3561,22 +3561,23 @@ description "minimum LSP bandwidth."; } leaf indication { type uint8; description "The indication whether the interface supports Standard or Arbitrary SONET/SDH."; } } container psc-specific { - when "../switching-capability >= 1 and ../switching-capability -<= 4"; + when "../switching-capability >= 1 and + +../switching-capability <= 4"; description "Switching Capability-specific information applicable when switching type is PSC1,PSC2,PSC3 or PSC4."; leaf minimum-lsp-bandwidth { type rt-types:bandwidth-ieee-float32; description "minimum LSP bandwidth."; } leaf mtu { type uint16; @@ -4971,21 +4975,21 @@ 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 The IANA is requested to assign two new URIs from the IETF XML registry ([RFC3688]). Authors are suggesting the following URI: URI: urn:ietf:params:xml:ns:yang:ietf-isis - Registrant Contact: IS-IS WG + Registrant Contact: The IESG XML: N/A, the requested URI is an XML namespace This document also requests one new YANG module name in the YANG Module Names registry ([RFC6020]) with the following suggestion: name: ietf-isis namespace: urn:ietf:params:xml:ns:yang:ietf-isis prefix: isis reference: RFC XXXX @@ -5360,24 +5364,20 @@ 2008, . [RFC5306] Shand, M. and L. Ginsberg, "Restart Signaling for IS-IS", RFC 5306, DOI 10.17487/RFC5306, October 2008, . [RFC5308] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308, DOI 10.17487/RFC5308, October 2008, . - [RFC5443] Jork, M., Atlas, A., and L. Fang, "LDP IGP - Synchronization", RFC 5443, DOI 10.17487/RFC5443, March - 2009, . - [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, . [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, DOI 10.17487/RFC5881, June 2010, . [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for @@ -5473,40 +5473,45 @@ Back-Off Delay Algorithm for Link-State IGPs", RFC 8405, DOI 10.17487/RFC8405, June 2018, . [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, . 11.2. Informative References + [RFC5443] Jork, M., Atlas, A., and L. Fang, "LDP IGP + Synchronization", RFC 5443, DOI 10.17487/RFC5443, March + 2009, . + [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, . Appendix A. Example of IS-IS configuration in XML This section gives an example of configuration of an IS-IS instance on a device. The example is written in XML. SLI 1.1.1.1 ISIS-example - + isis:isis true level-2 87FC.FCDF.4432 49.0001 @@ -5550,23 +5556,25 @@ Loopback0 - + ianaift:softwareLoopback + enabled
192.0.2.1 32
2001:DB8::1 @@ -5570,23 +5578,25 @@
2001:DB8::1 128
Eth1 - + ianaift:ethernetCsmacd + enabled
198.51.100.1 30
2001:DB8:0:0:FF::1