idnits 2.17.1 draft-ietf-lsr-isis-yang-augmentation-v1-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 17, 2021) is 1157 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC5329' is defined on line 732, but no explicit reference was found in the text ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) ** Obsolete normative reference: RFC 6536 (Obsoleted by RFC 8341) ** Obsolete normative reference: RFC 8919 (Obsoleted by RFC 9479) Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet A. Lindem 3 Internet-Draft S. Litkowski 4 Intended status: Standards Track Cisco Systems 5 Expires: August 21, 2021 Y. Qu 6 Futurewei 7 February 17, 2021 9 IS-IS YANG Model Augmentations for Additional Features - Version 1 10 draft-ietf-lsr-isis-yang-augmentation-v1-00 12 Abstract 14 This document defines YANG data modules augmenting the IETF IS-IS 15 YANG model to provide support for IS-IS Minimum Remaining Lifetime as 16 defined in RFC 7987, and IS-IS Application-Specific Link Attributes 17 as defined in RFC 8919. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on August 21, 2021. 36 Copyright Notice 38 Copyright (c) 2021 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 55 1.2. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 3 56 2. YANG Module for IS-IS Minimum Remaining Lifetime . . . . . . 3 57 3. YANG Module for IS-IS Application-Specific Link Attributes . 4 58 4. Security Considerations . . . . . . . . . . . . . . . . . . . 14 59 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 60 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 61 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 62 7.1. Normative References . . . . . . . . . . . . . . . . . . 15 63 7.2. Informative References . . . . . . . . . . . . . . . . . 17 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 66 1. Overview 68 YANG [RFC6020] [RFC7950] is a data definition language used to define 69 the contents of a conceptual data store that allows networked devices 70 to be managed using NETCONF [RFC6241]. YANG is proving relevant 71 beyond its initial confines, as bindings to other interfaces (e.g., 72 ReST) and encodings other than XML (e.g., JSON) are being defined. 73 Furthermore, YANG data models can be used as the basis for 74 implementation of other interfaces, such as CLI and programmatic 75 APIs. 77 This document defines YANG data modules augmenting the IETF IS-IS 78 YANG model [I-D.ietf-isis-yang-isis-cfg], which itself augments 79 [RFC8349], to provide support for configuration and operational state 80 for the following IS-IS features: 82 RFC7987: IS-IS Minimum Remaining Lifetime[RFC7987]. 84 RFC8919: IS-IS Application-Specific Link Attributes[RFC8919]. 86 The augmentations defined in this document requires support for the 87 IS-IS base model[I-D.ietf-isis-yang-isis-cfg] which defines basic IS- 88 IS configuration and state. The IS-IS YANG model augments the ietf- 89 routing YANG model defined in [RFC8349]. 91 1.1. Requirements Language 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 95 "OPTIONAL" in this document are to be interpreted as described in BCP 96 14 [RFC2119] [RFC8174] when, and only when, they appear in all 97 capitals, as shown here. 99 1.2. Tree diagram 101 Tree diagrams used in this document follow the notation defined in 102 [RFC8340]. 104 2. YANG Module for IS-IS Minimum Remaining Lifetime 106 This document defines a YANG module for IS-IS Minimum Remaining 107 Lifetime as defined in [RFC7987]. It is an augmentation of the IS-IS 108 base model. 110 module: ietf-isis-remaining-lifetime 112 notifications: 113 +---n corrupt-remaining-lifetime 114 +--ro routing-protocol-name? -> /rt:routing 115 /control-plane-protocols 116 /control-plane-protocol/name 117 +--ro isis-level? level 118 +--ro lsp-id? isis:lsp-id 120 file "ietf-isis-remaining-lifetime@2021-01-05.yang" 121 module ietf-isis-remaining-lifetime { 122 yang-version 1.1; 123 namespace "urn:ietf:params:xml:ns:yang:ietf-isis-remaining-lifetime"; 125 prefix isis-remaining-lifetime; 127 import ietf-isis { 128 prefix "isis"; 129 } 131 organization 132 "IETF LSR - Link State Routing Working Group"; 134 contact 135 "WG Web: 136 WG List: 138 Author: Yingzhen Qu 139 140 Author: Acee Lindem 141 142 Author: Stephane Litkowski 143 "; 145 description 146 "This YANG module defines the configuration and operational 147 state for IS-IS Minimum Remaining Lifetime feature as defined 148 in RFC 7987. 150 Copyright (c) 2021 IETF Trust and the persons identified as 151 authors of the code. All rights reserved. 153 Redistribution and use in source and binary forms, with or 154 without modification, is permitted pursuant to, and subject 155 to the license terms contained in, the Simplified BSD License 156 set forth in Section 4.c of the IETF Trust's Legal Provisions 157 Relating to IETF Documents 158 (http://trustee.ietf.org/license-info). 160 This version of this YANG module is part of RFC XXXX; 161 see the RFC itself for full legal notices."; 163 reference "RFC XXXX"; 165 revision 2021-01-05 { 166 description 167 "Initial version"; 168 reference 169 "RFC XXXX: A YANG Data Model for IS-IS."; 170 } 172 notification corrupt-remaining-lifetime { 173 uses isis:notification-instance-hdr; 174 leaf lsp-id { 175 type isis:lsp-id; 176 description "LSP ID"; 177 } 178 description 179 "This notification is sent when the system 180 detects correpted lifetime of an LSP."; 181 reference "RFC 7987: IS-IS Minimum Remaining Lifetime"; 182 } 183 } 184 186 3. YANG Module for IS-IS Application-Specific Link Attributes 188 This document defines a YANG module for IS-IS Application-Specific 189 Link Attributes [RFC8919]. It is an augmentation of the IS-IS base 190 model. 192 module: ietf-isis-link-attr 193 augment /rt:routing/rt:control-plane-protocols 194 /rt:control-plane-protocol/isis:isis/isis:interfaces 195 /isis:interface: 196 +--rw isis-link-attr 197 +--rw (link-attr-op-mode) 198 +--:(legacy) 199 | +--rw legacy? empty 200 +--:(transition) 201 | +--rw transition? empty 202 +--:(app-specific) 203 +--rw app-specific? empty 204 augment /rt:routing/rt:control-plane-protocols 205 /rt:control-plane-protocol/isis:isis/isis:database 206 /isis:levels/isis:lsp/isis:extended-is-neighbor 207 /isis:neighbor/isis:instances/isis:instance: 208 +--ro application-specific-link-attributes-sub-tlvs 209 +--ro asla-sub-tlvs* [] 210 +--ro l-flag? boolean 211 +--ro sabm-length? uint8 212 +--ro r-flag? boolean 213 +--ro udabm-length? uint8 214 +--ro sabm 215 | +--ro sabm-bits* identityref 216 +--ro udabm 217 +--ro unknown-tlvs 218 +--ro unknown-tlv* [] 219 +--ro type? uint16 220 +--ro length? uint16 221 +--ro value? yang:hex-string 222 augment /rt:routing/rt:control-plane-protocols 223 /rt:control-plane-protocol/isis:isis/isis:database 224 /isis:levels/isis:lsp/isis:mt-is-neighbor/isis:neighbor 225 /isis:instances/isis:instance: 226 +--ro application-specific-link-attributes-sub-tlvs 227 +--ro asla-sub-tlvs* [] 228 +--ro l-flag? boolean 229 +--ro sabm-length? uint8 230 +--ro r-flag? boolean 231 +--ro udabm-length? uint8 232 +--ro sabm 233 | +--ro sabm-bits* identityref 234 +--ro udabm 235 +--ro unknown-tlvs 236 +--ro unknown-tlv* [] 237 +--ro type? uint16 238 +--ro length? uint16 239 +--ro value? yang:hex-string 241 augment /rt:routing/rt:control-plane-protocols 242 /rt:control-plane-protocol/isis:isis/isis:database 243 /isis:levels/isis:lsp: 244 +--ro application-specific-srlg-tlv 245 +--ro as-srlg-tlvs* [] 246 +--ro neighbor-system-id? isis:system-id 247 +--ro pseudo-node-id? uint8 248 +--ro l-flag? boolean 249 +--ro sabm-length? uint8 250 +--ro r-flag? boolean 251 +--ro udabm-length? uint8 252 +--ro sabm 253 | +--ro sabm-bits* identityref 254 +--ro udabm 255 +--ro length-of-sub-tlvs? uint8 256 +--ro link-id-sub-tlvs 257 | +--ro link-local-remote-ids 258 | | +--ro link-local-id? union 259 | | +--ro link-remote-id? union 260 | +--ro ipv4-interface-addr 261 | | +--ro ipv4-int-addr? inet:ipv4-address 262 | +--ro ipv4-neighbor-addr 263 | | +--ro ipv4-neighbor-addr? inet:ipv4-address 264 | +--ro ipv6-interface-addr 265 | | +--ro ipv6-int-addr? inet:ipv6-address 266 | +--ro ipv6-neighbor-addr 267 | +--ro ipv6-neighbor-addr? inet:ipv6-address 268 +--ro srlgs 269 +--ro srlg* uint32 271 file "ietf-isis-link-attr@2021-01-05.yang" 272 module ietf-isis-link-attr { 273 yang-version 1.1; 274 namespace "urn:ietf:params:xml:ns:yang:ietf-isis-link-attr"; 276 prefix isis-link-attr; 278 import ietf-inet-types { 279 prefix inet; 280 reference "RFC 6991 - Common YANG Data Types"; 281 } 283 import ietf-routing { 284 prefix "rt"; 285 } 287 import ietf-isis { 288 prefix "isis"; 290 } 292 organization 293 "IETF LSR - Link State Routing Working Group"; 295 contact 296 "WG Web: 297 WG List: 299 Author: Yingzhen Qu 300 301 Author: Acee Lindem 302 303 Author: Stephane Litkowski 304 "; 306 description 307 "This YANG module defines the configuration and operational 308 state for IS-IS application specific link attributes feature as 309 defined in RFC 8919. 311 This YANG model conforms to the Network Management 312 Datastore Architecture (NMDA) as described in RFC 8242. 314 Copyright (c) 2021 IETF Trust and the persons identified as 315 authors of the code. All rights reserved. 317 Redistribution and use in source and binary forms, with or 318 without modification, is permitted pursuant to, and subject 319 to the license terms contained in, the Simplified BSD License 320 set forth in Section 4.c of the IETF Trust's Legal Provisions 321 Relating to IETF Documents 322 (http://trustee.ietf.org/license-info). 324 This version of this YANG module is part of RFC XXXX; 325 see the RFC itself for full legal notices. 327 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL 328 NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 329 'MAY', and 'OPTIONAL' in this document are to be interpreted as 330 described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, 331 they appear in all capitals, as shown here."; 333 reference "RFC XXXX"; 335 revision 2021-01-05 { 336 description 337 "Initial version"; 339 reference 340 "RFC XXXX: A YANG Data Model for IS-IS."; 341 } 343 identity sabm-bit { 344 description 345 "Base identity for sabm bits."; 346 reference "RFC 8919: IS-IS Application-Specific Link Attributes"; 347 } 349 identity rsvp-te-bit { 350 base sabm-bit; 351 description 352 "R bit, RSVP-TE."; 353 } 355 identity sr-policy-bit { 356 base sabm-bit; 357 description 358 "S bit, Segment Routing Policy."; 359 } 361 identity lfa-bit { 362 base sabm-bit; 363 description 364 "F bit, Loop Free Alternate (LFA). Includes all LFA types."; 365 } 367 grouping application-identifier-bit-mask { 368 description 369 "Identification of the set of applications associated with link 370 attribute advertisements"; 372 leaf l-flag { 373 type boolean; 374 description 375 "Legacy Flag. When set, all of the applications 376 specified in the bit mask MUST use the legacy 377 advertisements."; 378 } 379 leaf sabm-length { 380 type uint8; 381 description 382 "Standard Application Identifier Bit Mask Length in 383 octets."; 384 } 385 leaf r-flag { 386 type boolean; 387 default false; 388 description 389 "Reserved."; 390 } 391 leaf udabm-length { 392 type uint8; 393 description 394 "User Defined Application Identifier Bit Mask Length 395 in octets."; 396 } 397 container sabm { 398 leaf-list sabm-bits { 399 type identityref { 400 base sabm-bit; 401 } 402 description 403 "SABM bits list. This list will contain 404 identities for the bits which are set in the 405 SABA bits."; 406 } 407 description 408 "Standard Application Identifier Bit Mask."; 409 } 410 container udabm { 411 description 412 "User Defined Application Identifier Bit Mask. 413 This container is to be augmented by user defined 414 applications."; 415 } 416 } 418 grouping application-specific-link-attributes-sub-tlv { 419 description 420 "Grouping for specification of the applications and 421 application-specific attribute values."; 423 container application-specific-link-attributes-sub-tlvs { 424 list asla-sub-tlvs { 425 uses application-identifier-bit-mask; 426 uses isis:unknown-tlvs; 427 description 428 "List of application specific link attributes sub-tlvs."; 429 } 430 description 431 "Application specific link attributes sub-tlv."; 432 } 433 } 434 grouping application-specific-srlg-tlv { 435 description 436 "Grouping of a TLV to advertise application-specific 437 SRLGs for a given link."; 438 container application-specific-srlg-tlv { 439 list as-srlg-tlvs { 440 leaf neighbor-system-id { 441 type isis:system-id; 442 description 443 "Neighbor System-ID."; 444 } 445 leaf pseudo-node-id { 446 type uint8; 447 description 448 "Pseudo-node ID."; 449 } 450 uses application-identifier-bit-mask; 451 leaf length-of-sub-tlvs { 452 type uint8; 453 description 454 "Length of sub-tlvs."; 455 } 457 container link-id-sub-tlvs { 458 description 459 "Link Identifier sub-TLVs."; 460 container link-local-remote-ids { 461 description 462 "Link local/remote identifier sub-tlv."; 463 leaf link-local-id { 464 type union { 465 type inet:ipv4-address; 466 type uint32; 467 } 468 description 469 "Local identifier of the link. 470 It could be an IPv4 address or a local identifier."; 471 } 472 leaf link-remote-id { 473 type union { 474 type inet:ipv4-address; 475 type uint32; 476 } 477 description 478 "Remote identifier of the link. 479 It could be an IPv4 address or a remotely learned 480 identifier."; 481 } 483 } 484 container ipv4-interface-addr { 485 leaf ipv4-int-addr { 486 type inet:ipv4-address; 487 description 488 "IPv4 address for the interface."; 489 } 490 description 491 "IPv4 interface address sub-tlv."; 492 } 493 container ipv4-neighbor-addr { 494 leaf ipv4-neighbor-addr { 495 type inet:ipv4-address; 496 description 497 "IPv4 address for a neighboring router 498 on this link."; 499 } 500 description 501 "IPv4 neighbor address sub-tlv."; 502 } 503 container ipv6-interface-addr { 504 leaf ipv6-int-addr { 505 type inet:ipv6-address; 506 description 507 "IPv6 address for the interface."; 508 } 509 description 510 "IPv6 interface address sub-tlv."; 511 } 512 container ipv6-neighbor-addr { 513 leaf ipv6-neighbor-addr { 514 type inet:ipv6-address; 515 description 516 "IPv6 address for a neighboring router 517 on this link."; 518 } 519 description 520 "IPv6 neighbor address sub-tlv."; 521 } 522 } 524 container srlgs { 525 description "List of SRLGs."; 526 leaf-list srlg { 527 type uint32; 528 description 529 "SRLG value of the link."; 530 } 532 } 534 description 535 "List of application specific SRLG tlvs."; 536 } 537 description 538 "Application specific SRLG tlv."; 539 } 540 } 542 augment "/rt:routing/" + 543 "rt:control-plane-protocols/rt:control-plane-protocol"+ 544 "/isis:isis/isis:interfaces/isis:interface" { 545 when "/rt:routing/rt:control-plane-protocols/"+ 546 "rt:control-plane-protocol/rt:type = 'isis:isis'" { 547 description 548 "This augment ISIS routing protocol when used."; 549 } 550 description 551 "This augments ISIS protocol configuration 552 with TE attributes per application."; 554 container isis-link-attr { 555 choice link-attr-op-mode { 556 mandatory "true"; 557 leaf legacy { 558 type empty; 559 description 560 "Only send legacy advertisements."; 561 } 562 leaf transition { 563 type empty; 564 description 565 "Send both application-specific and legacy advertisements."; 566 } 567 leaf app-specific{ 568 type empty; 569 description 570 "Only send application-specific advertisements."; 571 } 572 description 573 "Link attributes mode"; 574 } 575 description 576 "Link attributes operation mode."; 577 } 578 } 579 /* TLV 22 */ 580 augment "/rt:routing/" + 581 "rt:control-plane-protocols/rt:control-plane-protocol"+ 582 "/isis:isis/isis:database/isis:levels/isis:lsp"+ 583 "/isis:extended-is-neighbor/isis:neighbor"+ 584 "/isis:instances/isis:instance" { 585 when "/rt:routing/rt:control-plane-protocols/"+ 586 "rt:control-plane-protocol/rt:type = 'isis:isis'" { 587 description 588 "This augment ISIS routing protocol when used"; 589 } 590 description 591 "This augments ISIS protocol LSDB TLV22."; 593 uses application-specific-link-attributes-sub-tlv; 594 } 596 /* TLV 223 */ 597 augment "/rt:routing/" + 598 "rt:control-plane-protocols/rt:control-plane-protocol"+ 599 "/isis:isis/isis:database/isis:levels/isis:lsp"+ 600 "/isis:mt-is-neighbor/isis:neighbor"+ 601 "/isis:instances/isis:instance" { 602 when "/rt:routing/rt:control-plane-protocols/"+ 603 "rt:control-plane-protocol/rt:type = 'isis:isis'" { 604 description 605 "This augment ISIS routing protocol when used"; 606 } 607 description 608 "This augments ISIS protocol LSDB TLV22."; 610 uses application-specific-link-attributes-sub-tlv; 611 } 613 /* application-specific SRLG TLV 238 */ 614 augment "/rt:routing/" + 615 "rt:control-plane-protocols/rt:control-plane-protocol"+ 616 "/isis:isis/isis:database/isis:levels/isis:lsp" { 617 when "/rt:routing/rt:control-plane-protocols/"+ 618 "rt:control-plane-protocol/rt:type = 'isis:isis'" { 619 description 620 "This augment ISIS routing protocol when used"; 621 } 622 description 623 "This augments ISIS protocol LSDB router capability."; 625 uses application-specific-srlg-tlv; 626 } 628 } 629 631 4. Security Considerations 633 The YANG modules specified in this document define a schema for data 634 that is designed to be accessed via network management protocols such 635 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 636 is the secure transport layer, and the mandatory-to-implement secure 637 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 638 is HTTPS, and the mandatory-to-implement secure transport is TLS 639 [RFC5246]. 641 The NETCONF access control model [RFC6536] provides the means to 642 restrict access for particular NETCONF or RESTCONF users to a pre- 643 configured subset of all available NETCONF or RESTCONF protocol 644 operations and content. 646 There are a number of data nodes defined in the modules that are 647 writable/creatable/deletable (i.e., config true, which is the 648 default). These data nodes may be considered sensitive or vulnerable 649 in some network environments. Write operations (e.g., edit-config) 650 to these data nodes without proper protection can have a negative 651 effect on network operations. These correspond to the following 652 schema nodes: 654 /isis:isis/isis:interfaces/isis:interface/isis-link-attr - 655 Modification of link attributes operation mode could result in 656 traffic being redirected or DoS attack. 658 Some of the readable data nodes in the modules may be considered 659 sensitive or vulnerable in some network environments. It is thus 660 important to control read access (e.g., via get, get-config, or 661 notification) to these data nodes. The exposure of the Link State 662 Database (LSDB) will expose the detailed topology of the network. 663 This may be undesirable since both due to the fact that exposure may 664 facilitate other attacks. Additionally, network operators may 665 consider their topologies to be sensitive confidential data.These 666 correspond to the following schema nodes: 668 /isis:isis/isis:database/isis:levels/isis:lsp/isis:mt-is- 669 neighbor/isis:neighbor/isis:instances/isis:instance/application- 670 specific-link-attributes-sub-tlvs 672 /isis:isis/isis:database/isis:levels/isis:lsp/application- 673 specific-srlg-tlv 675 5. IANA Considerations 677 This document registers URIs in the IETF XML registry [RFC3688]. 678 Following the format in [RFC3688], the following registrations is 679 requested to be made: 681 URI: urn:ietf:params:xml:ns:yang:ietf-isis-remaining-lifetime 682 Registrant Contact: The IESG. 683 XML: N/A, the requested URI is an XML namespace. 685 URI: urn:ietf:params:xml:ns:yang:ietf-isis-link-attr 686 Registrant Contact: The IESG. 687 XML: N/A, the requested URI is an XML namespace. 689 This document registers the YANG modules in the YANG Module Names 690 registry [RFC6020]. 692 name: ietf-isis-remaining-lifetime 693 namespace: urn:ietf:params:xml:ns:yang:ietf-isis-remaining-lifetime 694 prefix: isis-remaining-lifetime 695 reference: RFC XXXX 697 name: ietf-isis-link-attr 698 namespace: urn:ietf:params:xml:ns:yang:ietf-isis-link-attr 699 prefix: isis-link-attr 700 reference: RFC XXXX 702 6. Acknowledgements 704 This document was produced using Marshall Rose's xml2rfc tool. 706 The YANG model was developed using the suite of YANG tools written 707 and maintained by numerous authors. 709 7. References 711 7.1. Normative References 713 [I-D.ietf-isis-yang-isis-cfg] 714 Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L. 715 Lhotka, "YANG Data Model for IS-IS Protocol", draft-ietf- 716 isis-yang-isis-cfg-42 (work in progress), October 2019. 718 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 719 Requirement Levels", BCP 14, RFC 2119, 720 DOI 10.17487/RFC2119, March 1997, 721 . 723 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 724 DOI 10.17487/RFC3688, January 2004, 725 . 727 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 728 (TLS) Protocol Version 1.2", RFC 5246, 729 DOI 10.17487/RFC5246, August 2008, 730 . 732 [RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed., 733 "Traffic Engineering Extensions to OSPF Version 3", 734 RFC 5329, DOI 10.17487/RFC5329, September 2008, 735 . 737 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 738 the Network Configuration Protocol (NETCONF)", RFC 6020, 739 DOI 10.17487/RFC6020, October 2010, 740 . 742 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 743 and A. Bierman, Ed., "Network Configuration Protocol 744 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 745 . 747 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 748 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 749 . 751 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 752 Protocol (NETCONF) Access Control Model", RFC 6536, 753 DOI 10.17487/RFC6536, March 2012, 754 . 756 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 757 RFC 7950, DOI 10.17487/RFC7950, August 2016, 758 . 760 [RFC7987] Ginsberg, L., Wells, P., Decraene, B., Przygienda, T., and 761 H. Gredler, "IS-IS Minimum Remaining Lifetime", RFC 7987, 762 DOI 10.17487/RFC7987, October 2016, 763 . 765 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 766 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 767 . 769 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 770 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 771 May 2017, . 773 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 774 Routing Management (NMDA Version)", RFC 8349, 775 DOI 10.17487/RFC8349, March 2018, 776 . 778 [RFC8919] Ginsberg, L., Psenak, P., Previdi, S., Henderickx, W., and 779 J. Drake, "IS-IS Application-Specific Link Attributes", 780 RFC 8919, DOI 10.17487/RFC8919, October 2020, 781 . 783 7.2. Informative References 785 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 786 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 787 . 789 Authors' Addresses 791 Acee Lindem 792 Cisco Systems 793 301 Midenhall Way 794 Cary, NC 27513 796 EMail: acee@cisco.com 798 Stephane Litkowski 799 Cisco Systems 801 EMail: slitkows.ietf@gmail.com 803 Yingzhen Qu 804 Futurewei 805 2330 Central Expressway 806 Santa Clara, CA 95050 807 USA 809 EMail: yingzhen.qu@futurewei.com